Program seems to insist on writing to a shared network drive
Posted: Wed Mar 23, 2005 10:44 pm
Hi, we purchased 30 copies of Oxygen 5.1 for our labs. It is running on Windows XP Pro. The first lab of 12 machines went smooth.
The other lab I have a slight problem with the install.
All of these machines were given temporary admin privileges on the lab account to install the software. The working lab they were just installed on the local admin account. This may be a reason but I am unsure why that would make the difference.
For some reason when the software is ran, with or without admin privileges, it tries to write and save data into a folder on my server.
I do not want the computer to write to this folder and they cannot when logged in as lab users. However the problem is if it cannot write to this folder then it doesn’t run.
If I make the folder writable then the software runs but they all are all pointing to this same folder. This is obviously not good as then all the software will be overwriting each others config files.
The folder it created is called com.oxygenxml One of the installs must have created it.
The files it creates are:
file.history
options
project.history
I have tried removing and re-installing the software but it always wants to write these files to that folder. The first lab writes this information to the Hard drives local and therefore runs fine. Weird indeed.
Any ideas what keeps telling the software to point to that com.oxygenxml
folder on the shared network drive? Can I make it point to a folder on the C drive?
Is there a condif file or reg key I can change? Any reason one lab would do this and not the other?
I am sure this is very easy to fix and I apologize if it is something very simple. I do not actually use Oxygen myself, I just install it
Thanks.
Jace
The other lab I have a slight problem with the install.
All of these machines were given temporary admin privileges on the lab account to install the software. The working lab they were just installed on the local admin account. This may be a reason but I am unsure why that would make the difference.
For some reason when the software is ran, with or without admin privileges, it tries to write and save data into a folder on my server.
I do not want the computer to write to this folder and they cannot when logged in as lab users. However the problem is if it cannot write to this folder then it doesn’t run.
If I make the folder writable then the software runs but they all are all pointing to this same folder. This is obviously not good as then all the software will be overwriting each others config files.
The folder it created is called com.oxygenxml One of the installs must have created it.
The files it creates are:
file.history
options
project.history
I have tried removing and re-installing the software but it always wants to write these files to that folder. The first lab writes this information to the Hard drives local and therefore runs fine. Weird indeed.
Any ideas what keeps telling the software to point to that com.oxygenxml
folder on the shared network drive? Can I make it point to a folder on the C drive?
Is there a condif file or reg key I can change? Any reason one lab would do this and not the other?
I am sure this is very easy to fix and I apologize if it is something very simple. I do not actually use Oxygen myself, I just install it

Thanks.
Jace