... other commands ... key: Groups\ value: GroupName - STRING - "GroupName" key: Loader\ value: MODULE - STRING - "Full PATHNAME to the ARX file on the hard-drive" key: Name\ value: AppName - STRING - "Description string" Sample: HKEY_LOCAL_MACHINE\Software\DcgCompany\DcgApplication\Commands\ _MYCOMMAND - "MACOMMANDE" _MY2NDCMD - "MA2NDCMD" HKEY_LOCAL_MACHINE\Software\DcgCompany\DcgApplication\Groups\ DCGGROUP - "DCGGROUP" HKEY_LOCAL_MACHINE\Software\DcgCompany\DcgApplication\Loader\ MODULE - "c:\Program Files\DcgCompany\DcgApplication\DcgApp.arx" HKEY_LOCAL_MACHINE\Software\DcgCompany\DcgApplication\Name\ DcgApp - "This is my favorite Dcg Application" In R14.x releases the group sub-section is not used, but it will be in future. The Commands sub-section is used only if the application is registered for demand loading on command invocation. And the Name sub-section is used only if the application is registered for demand loading in load request. - HKEY_CURRENT_USER The HKEY_LOCAL_MACHINE seen before, can be manipulated at installation or running time by a third party. But his is possible only if the login user has the right permissions to do this. Most of the time, if using the correct settings, anybody can read and write in that section. For the HKEY_CURRENT_USER section this is the same. However, that section is accessible only by the login user, and might not be accessible at installation time by the computer administrator or example. This restriction applies only for NT users, as Windows 95/98 does not have the multiple user feature. But as AutoCAD runs on all above platform, your applications should work fine on all of them as well. So to work on all platform, and to be sure your application will work fine for a new NT login user, your installer should create entries in the HKEY_LOCAL_MACHINE only. And you application should be able to initialize itself at startup time using these entries to create and/or modify the AutoCAD entries and profiles (ie solutions 1583, and 1564). |