Please enhance documentation regarding --install about px

[genotrance]

So --install only runs Px at startup, it doesn't do anything with the config. You would need to do any configuration with a config file or use --save to generate one with the command line. I'll make this more clear in the documentation.

[DrVanScott]

And where does Px expect the configuration? User home? Folder containing px.exe?

[genotrance]

Px looks for px.ini at the same folder as the executable. When you use --save, it saves the config in this same location.

You can change the config file location with --config but if you run --install, it expects that default location.

[genotrance]

This has been updated in the README.

[DrVanScott]

Your commit defenitly helped , but unfortunately I am still not clear about that:

• I have installed px in C:\Program Files\px\
• open cmd
• cd "C:\Program Files\px"
• px --proxy=someproxy --save
• PX is telling me, that it has

Saved config to C:\Program Files\px\px.ini

• But there is no such file in that folder. Instead of this, it created/updated a file in %APP_DATA%\Local\VirtualStore\Program Files\px\px.ini

I also used "--install" to register automatic startup of px. As i cannot find any persistened config elsewhere on my system, i assume the automatically started instance of px is also using the file %APP_DATA%\Local\VirtualStore\Program Files\px\px.ini ?

[genotrance]

This is most interesting and first I'm hearing of it. Turns out this is a feature introduced by Microsoft back in Vista.

https://docs.microsoft.com/en-us/previous-versions/technet-magazine/cc138019(v=msdn.10)

Basically, all files are created in your profile account since the process is running as a standard user.