(Remind - it works on most systems - but some error out after the app is started - usually OCX instanciation issues are reported during install.)

The projects authorization code is fairly substancial. It present 14 reasons for not allowing access beyond the main screen a a few utilities.

I did notice something in install shield express related to creating a registry key when the program is installed:

Under ISE Help: Creating a Registry Key
A new key is created with the name “New Key-n” (where n is a successive number). Enter a meaningful name now to rename the key, or right-click on the key and select Rename to give it a new name later.

But my project does not use this feature (should it?). Instead the project declares a few kernel functions using these default values:

HKEY_LOCAL_MACHINE = 2147483650   && (HKEY) 0x80000002
SECURITY_ACCESS_MASK = 983103     && SAM value KEY_ALL_ACCESS
FLAG_ICC_FORCE_CONNECTION = 0x01  && Force a connection when attemping internect connect
KEY_READ = 0x020019

Then calls a function before the "Main" form is opened:

* Check for existing registry entry
PROCEDURE R6_isThereAnExistingICBookMark()
lnHKEY=0
lnKeyCanBeOpened=RegOpenKeyEX(HKEY_LOCAL_MACHINE,IC_RegistryKey,0,0x020019,@lnHkey)
RegCloseKey(lnHKey)
RETURN lnKeyCanBeOpened=0 &&When A zero returns a .T.
ENDPROC 
* Does the registry already have a bookmark?
PROCEDURE R6_CanAddICRegistryKey()
nRESULT=0
nDISPLAY=0
llwasKeyCreated=RegCreateKeyEx(HKEY_LOCAL_MACHINE,IC_RegistryKey,0,"REG_SZ",;
                               0,SECURITY_ACCESS_MASK,0,@nRESULT,@nDISPLAY)  && Returns .T. if successful
RETURN llwasKeyCreated AND nDISPLAY=1
ENDPROC 
* It also runs a get log in name. Would this cause an issue on some desktops?
PROCEDURE R6_GetComputerUserName()
LOCAL lcUserName, lnNameLength, lnResult
lnNameLength = 256
lcUserName   = SPACE( m.lnNameLength )
lnResult     = GetLoginName( 0, @lcUsername, @lnNameLength )
lcUserName   = PROPER(LEFT( m.lcUserName, AT( chr(0), m.lcUserName)-1))
RETURN lcUserName
ENDPROC &&GetComputerUserName

Does ISE offer a create registry key because permissions are more liberal during an install than during runtime. Should ISE set the key - that would defeat the purpose since the desire is to prevent the prospect from acquiring an additional evaluation without permission (go around a previous installation marker).

I noticed that ISE had a merge file for XML 3.0 and XML 4.0. The project uses
MSXML2.XMLHTTP - does that mean I need to merge one of the XML modules - or is it a different animal - like ISE's offered "WinHTTP QFE Installer (Platform specific NT or XP)" - DO I need these merge files to assure XMLHTTP or any XML service I use will install. I thought these guys were already inside XP - like out of the box!

Long - but thanks for looking!