Remember user data location about eddiscovery HOT 5 CLOSED

This was by design, its not a bug yet, i'll have to remember why i designed it this way and retest it.

I think it was because %programfiles% is a write protected folder that can be on any drive (not just c: ) and excluding it on every drive might have been the most error proof way to prevent users from using a directory that wouldn't work.

from eddiscovery.

Looking at the innoscript install script, it looks like the installer only honours the previous data directory if the install directory does not contain "Program Files" - e.g. installing in F:\Programs\EDDiscovery has it honouring the previous install data directory, while installing in F:\Program Files\EDDiscovery does not honour the previous install data directory.

Note that this does not affect any options.txt one might put in the install directory, or any -appfolder option on the command-line (e.g. from a custom shortcut).

from eddiscovery.

This was by design, its not a bug yet, i'll have to remember why i designed it this way and retest it.

from eddiscovery.

My install directory for the executable does contain Program Files, but on the H: drive
I might install it to another directory then.
Thanks.

from eddiscovery.

Going to leave the script alone for now. Do not want to change the script for this use case. Thanks for the report.

from eddiscovery.