Very strange.
I've been using INNO to build a script to deploy SQL 2012 Express as a quiet installer - ie install without user interaction. It worked just fine.
But I decided to try a /HIDECONSOLE parameter that i'd read about on msdn. But typed it incorrectly. I gave /HIDECONSOLE=true which is wrong and the installer threw an error. No problem. By then I'd decided that I didn't want that parameter anyway so removed it again.
But now each time I run my installer it throws the error about /HIDECONSOLE even though /HIDECONSOLE is no longer in the script. In fact I can now make any command line errors I want but it still throws that error about /HIDECONSOLE. It's as if setup.exe has remembered the previous bad command line and is now completely ignoring any new commands.
Is there a tmp file where that bad command line is stored ?
I've been using INNO to build a script to deploy SQL 2012 Express as a quiet installer - ie install without user interaction. It worked just fine.
But I decided to try a /HIDECONSOLE parameter that i'd read about on msdn. But typed it incorrectly. I gave /HIDECONSOLE=true which is wrong and the installer threw an error. No problem. By then I'd decided that I didn't want that parameter anyway so removed it again.
But now each time I run my installer it throws the error about /HIDECONSOLE even though /HIDECONSOLE is no longer in the script. In fact I can now make any command line errors I want but it still throws that error about /HIDECONSOLE. It's as if setup.exe has remembered the previous bad command line and is now completely ignoring any new commands.
Is there a tmp file where that bad command line is stored ?