Scripting

Kofi,

Caesar II is not in listed in the Package KB on this site, nor is it mentioned in any of the message board posts - this is probably because it is a very specialist piece of software and COADE/Intergraph have their own support forums linked off their website where this question would be better posted.

By all means, when you have the solution, add an entry to the Package KB for future reference, but I think that vendor support is the best way to go for this software.

Hope this helps,

Dunnpy

PS - Not sure if this is really related to 'package security' or 'scripting' - 'Package Development' would have been the best place to post. In any case, please do not cross post on the boards.

Yes I have posted it on their forum. If I get anything I will add it to the Package Software.

Thanks
Kofi

Kofi,

I vaguely remember working on Caesar 2 some time ago. If i recall, it was a Custom Action (CA) which popped up a custom dialog box asking the user for metric/imperial measurements etc. If i also recall, the installation routine actually halted until the dialog box was closed. If this was the case, I'd recommend the following:

Install the MSI with logging, eg, msiexec /i {whatever.msi} /l*v c:\caesarlog.log

Click next, next etc, until the dialog box pops up. Then, WITHOUT closing the dialog box, open your log file. The last line may say something similar to:

Action start 18:35:00: configCaesar.

'configCaesar' would be the name of the custom action that you need to stop running. Let's say the CA is indeed called 'configCaesar'. Search for it in the installExecuteSequence and the installUISequence. In the condition column for these rows, put the condition 1=0. This should do the trick.

....and dunmpy's right - this should be in 'Package Development'....

You are completely right. I had the same problem. Thank you for all of your help!