When the setup is run without the command-line parameter the setup runs without a problem, but when I use setup.exe /s /v/qb. I get the following error
"Error 1406. Could not write value <REGISTY VALUE> to key <KLM\SYSTEM\CurrentControlSet\Enum\.....> Verify that you have sufficient access to that key, or contact your support personnel."
I know if you try and manually add a key to <KLM\SYSTEM\CurrentControlSet\Enum> you get an error "Cannot create key: Error writing to the registry" which is fair enough. but why do the method of running the setup behave differently.
I've also try this on InstallShield 10.5 and have the same results
Has anyone experienced this before?
Edited by richardnorris, 25 April 2005 - 16:49.