Post by Stefan on Apr 26, 2017 7:04:51 GMT -5
Observed using Windows 10 Pro Version 1607, 64-bit. and SPFLite Version 8.5.7027
Example:
In C:\Program Files (x86)\SPFLite there is a file called "Changes.txt". If I load it with Notepad, modify the file and try to save it, I'm (effectively!) told "Access Denied". Same thing happens when I try "Save As" with a new name of "ChangesNew.txt".
If I do the same via SPFLite, the modification is saved. Subsequently, the file appears under File Manager's RECENT tab. This is also true when I use CREATE to make a new file, e.g. ChangesNew.txt. No error. The hiccup is....
... when looking at folder "C:\Program Files (x86)\SPFLite\" with Windows Explorer, Notepad shows that file "Changes.txt" remains
unaltered and file "ChangesNew.txt" does not exist. Yet via SPFLite File Manager both files, including the modified text, can be accessed. Issuing WDIR against either file will not open to "C:\Program Files (x86)\SPFLite" but shows "This PC" instead supporting the view that as far as Windows is concerned, the files are not where SPFLite implies they should be. So where did SPFLite squirrel away the modified file and the new file, if not in the original directory?
Example:
In C:\Program Files (x86)\SPFLite there is a file called "Changes.txt". If I load it with Notepad, modify the file and try to save it, I'm (effectively!) told "Access Denied". Same thing happens when I try "Save As" with a new name of "ChangesNew.txt".
If I do the same via SPFLite, the modification is saved. Subsequently, the file appears under File Manager's RECENT tab. This is also true when I use CREATE to make a new file, e.g. ChangesNew.txt. No error. The hiccup is....
... when looking at folder "C:\Program Files (x86)\SPFLite\" with Windows Explorer, Notepad shows that file "Changes.txt" remains
unaltered and file "ChangesNew.txt" does not exist. Yet via SPFLite File Manager both files, including the modified text, can be accessed. Issuing WDIR against either file will not open to "C:\Program Files (x86)\SPFLite" but shows "This PC" instead supporting the view that as far as Windows is concerned, the files are not where SPFLite implies they should be. So where did SPFLite squirrel away the modified file and the new file, if not in the original directory?
