-
I found the very old following Microsoft problem description:
================
File Names Truncated When Using SHFileOperation
Q186152
SYMPTOMS
When you use SHFileOperation to copy or move files, the destination file names are truncated to the 8.3 file name format. For example, the file name "New Document.temp" will be truncated to "NewDocum.tem".
CAUSE
The default behavior of...
2009-11-09 21:28:54 UTC by c-273
-
*Very* odd. As you can see if you play around with the Manage->Options->Backup settings, the closest that pwsafe can get to such filenames is something like pwsafe_001.ibak. The underscore followed by 3 digits followed by .ibak is hardcoded, and something has to be really sick for this to change in the code. For this to change in the code without the app crashing is **very** unlikely.
I can...
2009-11-09 21:28:27 UTC by ronys
-
SUMMARY: Fully expanded Nested Tree view opens scrolled to bottom of list.
DESIRED BEHAVIOR: Either (a) set scroll and selection to top of list or (b)
remember selection per database.
ACTUAL RESULT: Fully expanded Nested Tree view opens with window scrolled to bottom or list with first item in window selected.
STEPS TO REPRODUCE:
1. Open database with enough items to greatly exceed...
2009-11-09 20:44:57 UTC by jnavas
-
@ikxcsshcm7
I don't have any .cfg files in the Password Safe directory 3.19. The 3.10 directory has one I renamed to .cfgX last July.
@anyone
The command string I'm using to start is:
G:\Util\PWSafe319\pwsafe.psafe3 -u JWG -h usbHost.
2009-11-09 19:51:28 UTC by greenley
-
@greenley
Have you tried my suggestion above dated 2009-06-13 03:07:20 GMT ?
@rony
I've seen this happen a number of times in the past on various XP systems. I do not know what is the cause, perhaps the OS is falling back to 8.3 filename convention.
2009-11-09 19:36:14 UTC by ikxcsshcm7
-
Truncation is probably a good hypothesis, but it's most likely in the code. Note that the FileMon log had no problems reporting activity to the pwsafe.psafe3 file without truncating (See last 10 lines of log). Below is a directory listing showing the .psa files that I've accumulated while I've been testing this.
Directory of G:\stor\backup
11/09/2009 10:53 AM .
2009-11-09 19:00:55 UTC by greenley
-
Hi,
PasswordSafe's database files end with .psafe3. My guess is that filemon truncates the suffix it displays to 3 letters, for historical reasons.
Trust me (or better yet, review the code) - PasswordSafe reads and write .psafe3 files, not .psa files.
Cheers,
Rony.
2009-11-09 18:04:41 UTC by ronys
-
Hi,
Indeed the current version of PasswordSafe is derived from the original 1.7, way back when...
As to the error, you're the first user to report such a problem. My first suspect would be a corrupt download. Could you try to download again, perhaps from another mirror, and seeing if this solves the problem?
Another possibility would be to download the '.msi' installer file, and install...
2009-11-09 17:55:47 UTC by ronys
-
I am using Password Safe 1.7 and recently found your product. It appears it had been grown from the Password Safe I am using. I have tried to install it on the laptop with Vista Home Premium and getting the error message listed in Summary (see attached picture). Please advise what would be procedures to install the software in my case. Thanks.
2009-11-09 17:41:02 UTC by johnd46
-
PassWord Safe **IS** creating .psa files. Please see FileMon log below. It looks as if it starts to write an ibak, encounters something and defaults to .psa.
PassWord Safe is being run from a USB Drive [G:] in a Windows XP Professional (SP3) machine. At this time, I am running Password Safe 3.19, but this behavior was happening in 3.10 as well.
Please let me know what additional...
2009-11-09 17:36:28 UTC by greenley
