Hi,
I have a question regarding registry key handling. When I want to write registry keys I formerly had put the initial values in a .reg file and had only handled the keys with variable file path values via the launcher.ini. Later I noticed that some portable apps handle every registry key in the .ini file without initially having a .reg file (which gets created after the fist run).
An example with an external .reg file:
portable.reg:
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Intel\Indeo\5.0\Decoder] "Scalability Levels"=dword:00000000
launcher .ini:
[RegistryValueWrite] HKLM\SOFTWARE\Arkane Studios\Installed Apps\arx fatalis\Folder=REG_SZ:%PAL:AppDir%\Arx Fatalis\ HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\Hansa (TrueType)=REG_SZ:%PAL:AppDir%\Arx Fatalis\misc\Arx.ttf
New approach with handling in .ini file only:
launcher .ini:
[RegistryValueWrite] HKLM\SOFTWARE\Arkane Studios\Installed Apps\arx fatalis\Folder=REG_SZ:%PAL:AppDir%\Arx Fatalis\ HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\Hansa (TrueType)=REG_SZ:%PAL:AppDir%\Arx Fatalis\misc\Arx.ttf HKCU\Software\Intel\Indeo\5.0\Decoder=REG_SZ:Scalability Levels=dword:00000000
Now my question:
When the last registry entry will be changed by the application does it now get overwritten by the value still set in the launcher.ini everytime the app is started? Or does the value set by the application during running stay the same it was after the app has closed?
Please enlighten me. Thanks.
The
[RegistryValueWrite]
section overwrites the values on every run.Previously known as kAlug.
Thank you for this clarification. So I should only put the path handling keys in the launcher.ini. Ok, I need to go back one step with my launchers
Cheers
Gremlin