Quote: "Quote: "The only thing to note here is that you'll have to replace FPSCreatorCleaner.exe because it refuses to run from anywhere other than the default directory the installer suggests."
Strange. Our "FPSCreatorCleaner.exe" works as it should where we install it. One system runs v1.17, and we have VM systems setup that house v1.18, v1.19, and v1.20. Cleaner works properly in those, and we do not install in the "default directory" (C:\Program Files...)."
The darned thing always throws a
"Program can only be run from the FPS Creator Folder!" at me, even after having performed complete de-installs and fresh re-installs
(so, if registry keys are queried for the path, there should be no confusion).
I was too lazy to trace where it thinks it is running and where it thinks FPSC is installed, so, I wrote my own cleaner (giving me the Option to do a few other checks, such as whether the Serial key is in place etc).
I'm positive that others also have complained about the program's behaviour in this respect.
Lives of great men all remind us we may make our lives sublime