I have already submitted my issue as a bug report (https://sourceforge.net/tracker/index.php?func=detail&aid=1668493&group_id=41019&atid=429579). Arjun sent me a couple of e-mails, but because of his questions I do not think we are on the same page. I appreciate his help, but I wanted to get your opinion (in case you have not seen it yet).
I updated Password Safe to v3.06 from v3.05.02. V3.06 fails to open and spawns two consecutive error/debug windows. The following Application error reports appear in the Event Viewer:
For more information, see Help and Support Center at
(http://go.microsoft.com/fwlink/events.asp).
Both error reports contain additional lines of "Data," but I am not sure if it divulges any private information so I did not post it.
I have done some investigating and the error appears to be related to pwsafe.cfg. I
found that setting the "Remember last X number databases" field to 0 (zero) under Manage > Options > System > Recent PasswordSafe Databases, prevents Password Safe from opening. As such, If I delete pwsafe.cfg or do not select the zero option, the program operates normally. I confirmed this behavior by repeatedly reselecting the 0 after deleting pwsafe.cfg. V3.05.02 works fine. Maybe it is just my system, but I hope this helps.
Incidentally, where should bug reports go? Submitting it under the bug tracker seems to make the most sense, but the general discussions boards seem to receive more feedback. I do not wish to make things difficult for you or flout convention, I just wish to help.
Thank you as always for the excellent work.
Monster
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Rony:
I have already submitted my issue as a bug report (https://sourceforge.net/tracker/index.php?func=detail&aid=1668493&group_id=41019&atid=429579). Arjun sent me a couple of e-mails, but because of his questions I do not think we are on the same page. I appreciate his help, but I wanted to get your opinion (in case you have not seen it yet).
I updated Password Safe to v3.06 from v3.05.02. V3.06 fails to open and spawns two consecutive error/debug windows. The following Application error reports appear in the Event Viewer:
Error #1
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2/24/2007
Time: 9:32:26 PM
User: N/A
Computer: Computer Name
Description:
Faulting application pwsafe.exe, version 3.6.0.1259, faulting module
pwsafe.exe, version 3.6.0.1259, fault address 0x00021eed.
For more information, see Help and Support Center at
(http://go.microsoft.com/fwlink/events.asp).
Error #2
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2/24/2007
Time: 9:32:33 PM
User: N/A
Computer: Computer Name
Description:
Faulting application pwsafe.exe, version 3.6.0.1259, faulting module
ntdll.dll, version 5.1.2600.2180, fault address 0x00043345.
For more information, see Help and Support Center at
(http://go.microsoft.com/fwlink/events.asp).
Both error reports contain additional lines of "Data," but I am not sure if it divulges any private information so I did not post it.
I have done some investigating and the error appears to be related to pwsafe.cfg. I
found that setting the "Remember last X number databases" field to 0 (zero) under Manage > Options > System > Recent PasswordSafe Databases, prevents Password Safe from opening. As such, If I delete pwsafe.cfg or do not select the zero option, the program operates normally. I confirmed this behavior by repeatedly reselecting the 0 after deleting pwsafe.cfg. V3.05.02 works fine. Maybe it is just my system, but I hope this helps.
Incidentally, where should bug reports go? Submitting it under the bug tracker seems to make the most sense, but the general discussions boards seem to receive more feedback. I do not wish to make things difficult for you or flout convention, I just wish to help.
Thank you as always for the excellent work.
Monster
Rony, thanks for the fix in 3.07. Some excellent new features, too! Please know that your efforts are much appreciated. :)
T.