[Advanced] PWB Alternate Configuration Locations

[Scott]

No keys need to be in the INI file as long as the key is located somewhere, either in a INI file, or one of the registry locations, although if you did not specify an INI file on the command line, at least an empty file called PWB.INI needs to be in the same folder as the PWB.EXE file.

When PWB starts, it looks for the INI file and verifies the file exists. PWB looks in the folder where the PWB.EXE is located if an INI was not specified. The INI file location can be specified on the command line or in the registry.

After verifying the INI exists, PWB reads in the configuration, starting with the [Browser] ConfigRegLocation key, then the [AutoRegistration] keys, the [Browser] keys, and so on as the order listed in stock PWB INI file.

The order in which the keys are read from a location is as follows, with each one take precedence over the one before it.

1. INI
2. [HKEY_LOCAL_MACHINE\Software\TeamSoftware Solutions\Public Web Browser v2\"section"] "key"=
3. [HKEY_CURRENT_USER\Software\TeamSoftware Solutions\Public Web Browser v2\"section"] "key"=
4. [HKEY_LOCAL_MACHINE\"ConfigRegLocation"\"section"] "key"=
5. [HKEY_CURRENT_USER\"ConfigRegLocation"\"section"] "key"=

The "section", "key", "ConfigRegLocation" are replaced with the section, key, and key value respectively. For example the HomePage could be located in the following location.

[HKEY_CURRENT_USER\Software\TeamSoftware Solutions\Public Web Browser v2\Browser] HomePage=www.team2s.com

If PWB does not find a key in one of these locations it assigns the default value to the key.

The only key that does not have a default value and needs to be specified is the [Browser] INIFileVersion key.

--Scott