non_windows_folder
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
non_windows_folder [2022/03/31 19:55] jan created |
non_windows_folder [2022/03/31 20:23] jan more splelings |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Non Windows owned folder ===== | + | ===== (Non) Windows owned folder ===== |
| + | |||
| + | Windows does not like writing arbitrary files in arbitrary folders / directories. The Blue Hell tools usually do write things into the same folder as where the executable is, and when that happens to be a folder that is owned by windows things will not work. | ||
| + | |||
| + | The µsoft suggested alternatives are to either use the registry or to use a user specific folder. This is something that I do not want as it almost mandates writing ((or using a 3rd party installation tool)) an installation / de-installation tool. Whereas in the setup that I prefer everything is in one single folder and a deinstallation is as simple as removing a folder. | ||
| + | |||
| + | So, to get things working, one must not install Blue Hell software into folders like ' | ||
| + | |||
| + | For the installation tool itself, windows will notice that the executable file was donloaded from the internet and that at the file was not code signed by a µsoft trusted party. Windows will complain about that - the nag screen that pops up can be ignored though, just click on 'more info' and allow the application to run. I could hide hide that a bit by zipping the executable, but one would then need to unzip it first. | ||
| - | FIXME | ||
non_windows_folder.txt · Last modified: 2022/03/31 20:23 by jan