Using HKLM to hold document class info?

[Colin Odden]

Hi. I'm deploying Textpad to my department (site license) and am going to perform an unattended installation with some preloaded document classes. Installing the software via a startup script and copying .syn files to c:\program files\textpad 4\system is no problem.

However, document classes are registered in HKEY_CURRENT_USER\software\helios\... . Since I want settings to stick to the machine, I made the document classes I wanted, exported the HKCU settings, changed them around to HKLM, and imported the registry file. Textpad ignores the stuff in HKLM, and if I delete the HKCU document class info Textpad recreates it for me with some default stuff.

So, is there any way to set document classes and other preferences per-machine?

Many thanks for any advice, flames, etc.

Colin Odden
The Ohio State University

[bbadmin]

A preloaded configuration should be created under the following key:

HKEY_USERS\.DEFAULT\Software\Helios\TextPad 4

However, TextPad only looks there the first time it is run, when it clones that node to HKEY_CURRENT_USER. "First time" is defined as when the following key does not exist:

HKEY_CURRENT_USER\Software\Helios\TextPad 4\Docking

If you delete that key, TextPad will recreate it, with its default GUI layout.

Keith MacDonald
Helios Software Solutions