not relevant anymore with Notesbrowser 2 because it installs to the recommended Windows directories
Question:
....................
We have a user who had problems with the VirtualStore path introduced with Windows Vista:
- he had installed Notesbrowser and everything worked well
- then he changed the administrator securities functions, because he wanted to get rid of the many security question
- all Notesbrowser data was appearantly gone
- the recovery of a backup did not change anything
With help of our database finder:
http://www.notesbrowser.com/forum/viewt ... ?f=2&t=178
He could located his database and backup path here:
"C:\Users\HP\AppData\Local\VirtualStore\Program Files\Notesbrowser"
"C:\Users\HP\AppData\Local\VirtualStore\Program Files\Notesbrowser\Backup"
But on his hard disk it looks correct:
C:\Program Files\Notesbrowser\
C:\Program Files\Notesbrowser\Backup
What has happened and what to do?
Answer:
..................
The problem is, that Windows since Vista creates a "VirtualStore" in case the user has not enough rights to write to C:\Program Files and a program wants to write to this location. The idea behind this is, that no program should read or write data to or from C:\Program Files\.
But much programs read/write to it, so what does Windows do?
It internally changes the path:
"C:\Program Files\Notesbrowser" to somewhat
"C:\Users\xyz\AppData\Local\VirtualStore\Program Files\Notesbrowser"
Much programs do read and write in its installation folder, also Notesbrowser can do this. Since the release of Noptesbrowser 2 this is optional (its the USB mode). But many old installations that are migrated to Notesbrowser 2 just saves its database exactly in the same folder where the executable "Notesbrowser.exe" is located. Our idea of the USB mode is to have all data in one single folder (e.g. C:\Program Files\Notesbrowser) - this makes it easy to move Notesbrowser to an flash stick and to have many parallel Notesbrowser installation, etc.
Unfortunately, this is adverse from the Windows concept.
For most users, there is no problem. But if you do not have full rights to write to "C:\Program Files\Notesbrowser" the VirtualStore will be used, probably without your knowledge. Be aware the we suspect that the feature "VirtualStore" maybe has bugs or is not consistent with the way the operation system usually addresses the file system. So it may lead to troubles and the bad behavior explained above.
What to do?
There are three solutions:
- change from USB mode to default mode where Notesbrowser saves in system default folders. Please read the manual how to do it
- give your User full rights to read and write to the installation folder (usually "C:\Program Files\Notesbrowser"):
(See here how to do this http://www.notesbrowser.com/forum/viewt ... ?f=2&t=173 )
- if you can not have full rights or continue to have problems, and want to use the USB mode, move the whole Notesbrowser folder plus its database to a "neutral" path for example C:\Notesbrowser or so where you have full right and Windows cannot mess it up. Be sure you have full rights there. Speak to your Administrator if you have not.
For your Backup path, also select a plain simple path, for example D:\Notesbrowser-Backup. Or use a USB stick.
The Notesbrowser and Backup paths do not need to be on the first folder level, e.g. D:\Backups\Notesbrowser-Backup will perfectly work.
Problems with "VirtualStore" paths
- Dirk Schwenke
- NB-Team
- Posts: 122
- Joined: Thu Dec 29, 2005 11:31 pm
- Location: Hamburg
- Contact:
Re: Problems with "VirtualStore" paths
For Windows 64 bit, I installed an application SyncBack SE for backup to copy the installation https://yumdownload.com/syncback-se files VS from the SSD. So it saved me from trouble with PC.
Re: Problems with "VirtualStore" paths
On the off chance that you can not have full rights or keep on having issues, move the entire Notesbrowser organizer in addition to its database to a "nonpartisan" way, for instance, C:\Notesbrowser or so where you have full right and Windows can't destroy it. Make certain you have full rights there. Address your Manager on the off chance that you have not.
For your Reinforcement way, likewise select a plain basic way, for instance, D:\Notesbrowser-Reinforcement. Or then again utilize a USB stick.
The Notesbrowser and Reinforcement ways don't should be on the principal envelope level, for example, D:\Backups\Notesbrowser-Reinforcement will superbly work.
For your Reinforcement way, likewise select a plain basic way, for instance, D:\Notesbrowser-Reinforcement. Or then again utilize a USB stick.
The Notesbrowser and Reinforcement ways don't should be on the principal envelope level, for example, D:\Backups\Notesbrowser-Reinforcement will superbly work.
Re: Problems with "VirtualStore" paths
Hello,
Windows VirtualStore is being utilized when the User Account Control is dynamic and when endeavors are being made to compose into the Windows ensured registries, for example, %programfiles%, %programdata%, %systemdrive%, or %systemroot%.
At the point when the signed in client isn't a piece of the Administrator gathering, or if the Administrator account is being utilized with higher security settings for the UAC, at that point access to these indexes will be caught by the working framework and diverted to the fitting catalog inside the VirtualStore area.
In any case, this may speak to issues in the event that where the application expects access to one of ensured catalogs, as the record won't be situated at the normal spot.
So as to discover required record, an ABL program can utilize working framework condition factors to develop way to VirtualStore and add that to the SEARCH work, for example :
Characterize VARIABLE cVSpath AS CHARACTER NO-UNDO.
cVSpath = OS-GETENV("LOCALAPPDATA") + "\VirtualStore\Program Files\MyDir\".
PROPATH = cVSpath + "," + PROPATH.
A precedent would be a WebClient application which of course introduces application registry into %programfiles%\WebClientApps .
Another methodology is to keep away from out and out establishment of utilization under one of the ensured indexes. A model is to pick WebClient application establishment index, for example, "C:\WebClientApps" in which case virtualization divert to the VirtualStore won't be utilized.
Thanks...
Windows VirtualStore is being utilized when the User Account Control is dynamic and when endeavors are being made to compose into the Windows ensured registries, for example, %programfiles%, %programdata%, %systemdrive%, or %systemroot%.
At the point when the signed in client isn't a piece of the Administrator gathering, or if the Administrator account is being utilized with higher security settings for the UAC, at that point access to these indexes will be caught by the working framework and diverted to the fitting catalog inside the VirtualStore area.
In any case, this may speak to issues in the event that where the application expects access to one of ensured catalogs, as the record won't be situated at the normal spot.
So as to discover required record, an ABL program can utilize working framework condition factors to develop way to VirtualStore and add that to the SEARCH work, for example :
Characterize VARIABLE cVSpath AS CHARACTER NO-UNDO.
cVSpath = OS-GETENV("LOCALAPPDATA") + "\VirtualStore\Program Files\MyDir\".
PROPATH = cVSpath + "," + PROPATH.
A precedent would be a WebClient application which of course introduces application registry into %programfiles%\WebClientApps .
Another methodology is to keep away from out and out establishment of utilization under one of the ensured indexes. A model is to pick WebClient application establishment index, for example, "C:\WebClientApps" in which case virtualization divert to the VirtualStore won't be utilized.
Thanks...