Cannot store license.xml when user home is on different disk

[sage12]

Hi

I just installed <oXygen/> version 8 on my PowerBook running Mac OS X. Since then, <oXygen/> refuses to save my license.xml file (and other preferences). Instead, it says:

Code: Select all

Select all



Cannot save the file. Cannot save license file. Cannot rename license.xml.tmp to /Volumes/home-roel/Library/Preferences/com.oxygenxml/license.xml

I found out that this is because my global "Applications" folder and my "~/Library/Preferences" folder are on different disks: <oXygen/> starts OK when I move the "oxygen" folder to "~/Applications" (the user's application folder).

However, I had exactly the same setup with version 7, and that ran OK. So, I assume this is a bug — <oXygen/> 8 creates a temporary file in its own home folder first, and then try to rename it in order to move it into its preferences folder. Unix "rename" does not allow "from" and "to" to be on different file systems.

Is there a way to fix this?

[adrian]

Hi,

Do note that Oxygen version 8 is 11 years old, so needlessly to say, it's more than a little outdated and it is no longer maintained or supported. This bug was eventually fixed in a more recent version, it was such a rare occurrence that it was not observed at the time.

<oXygen/> 8 creates a temporary file in its own home folder first

It's too old a version to verify what it does, but it's possible it creates the file in the application running folder. If you start Oxygen from its installation folder, then yes the Oxygen folder is the running folder, but you can also start it from another folder and it will most likely create the temporary file there.

Is there a way to fix this?

As you mentioned, the solution is to have the Oxygen running folder on the same file system (Volume) as your home folder. So either move Oxygen to your home folder, or start Oxygen in your home folder. Not sure if double clicking a file does this (use that file's folder as the running folder), again this is a very old version and cannot verify this information. However, starting the sh script (or .app) from the Terminal should use the current folder from the Terminal as the running folder.

Regards,
Adrian