It is the easiest way to find these registry entries by examinating one's own PC's registry and to use these entries to write the script.
But there is a big problem:
Some registry entries are enumerations.
Sample: in the RAMdisk script there is an entry made into the driver's class list.
The code:
RegWrite,HKLM,0x1,"WB-Setup\ControlSet001\Control\Class\{FFA1C341-4539-11D3-B88D-00C04FAD5172}","Class","RamDisk"
RegWrite,HKLM,0x1,"WB-Setup\ControlSet001\Control\Class\{FFA1C341-4539-11D3-B88D-00C04FAD5172}",,"RAM Disk"
RegWrite,HKLM,0x1,"WB-Setup\ControlSet001\Control\Class\{FFA1C341-4539-11D3-B88D-00C04FAD5172}\0001","ProviderName","Unknown"
RegWrite,HKLM,0x1,"WB-Setup\ControlSet001\Control\Class\{FFA1C341-4539-11D3-B88D-00C04FAD5172}\0001","MatchingDeviceId","ramdriv"
RegWrite,HKLM,0x1,"WB-Setup\ControlSet001\Control\Class\{FFA1C341-4539-11D3-B88D-00C04FAD5172}\0001","DriverDesc","Ramdisk"
The red coloured 0001 is an index which is automatically increased when the next driver is added (Should start with 0000).
Imagine a second script will follow using also the 0001: here it is:
Currently the projects are very small and the propability for such a coincidence is very small, too.
But when the projects increase, getting more and more drivers ... ???
Here is the reason that I alreadey asked Nuno for the RegGetNext command and I hope that it will be included in the script engine soon.
After we got it: @.script developers: Revise your scripts and use RegGetNext where applicable.
BTW: The go2pdf script has the same issue.