PB screen of death (guid unkn), driving me crazy!!

[KrispyKritter]

I think I found out how to do it.

In PB folder, open or make a file called pbcl.cfg.

Into it, I wrote

PB_CDKeyVerAuto 1
pb_logtofile 1

Now, the PB_CDKeyVerAuto is 1 when I connect, even if I unset it in ET with "PB_CDKeyVerAuto 0" or "seta PB_CDKeyVerAuto 0"

I also found the "PB_CDKeyVerAuto 1" in my etconfig files, like you did, but it seems PB won't accept it this way, despite what was in the 5-year-old post. Changed the procedure?

The pb_logtofile seems to save all the PB-related lines you see when you log on, including the GUID. If you still have trouble, you can read the file "pbcl.log" and see if your guid is changed at each logon. You might also see if there are any errors when PB tries to connect to its server. Logging default is to only save severe errors to file, like the "o/s exceptions" I found from 2008. We probably want to turn off the logging when the problem is fixed. I am trying leading //s in the pbcl.cfg file. (Which seems to work).

My PB GUID seems to be the same now as it was when the logfile was created, in June 2008.


(an unseemly number of seems)