This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
chris_hahn
Level 2
‎Aug 08, 2012 06:44 PM

Debugging past a reboot

Hello,

Installshield 2011 Premiere. An installscript driven installer.

I have been asked to fix a bug in one of our installers. This bug results in
an error pop-up that maps to the screen right after a reboot that the install
requires.

Can I still use the debugger to trace what is going on?

Basically the installer see that the user needs to upgrade his .NET and windows
installer instances and executes these sub-installs fine, but after they are
done a reboot is necessary. When the reboot is complete and the installer
tries to pick up where it left off an error dialog pops up.

It just says "Cannot find C" ....clearly there is a path that is not being
built properly, but I am not sure how I can watch this in the debugger
through the reboot.

Pointers that suggest how to track this via logging will be appreciated.

(sorry for being so new....I will try to post whatever I come up with)

Take care,

Chris
Labels (1)
Labels
0 Kudos
(1) Reply
chris_hahn
Level 2
‎Aug 20, 2012 12:02 PM

Hello all,

I appreciate your patience....my question was your basic RTFM.

I did do the research and have a few answers of my own.

I found FileInsertLine and am using it to write my own log messages.

I read up on the Order of Event Handlers and found where the reboot is being called.

(there seems to be a problem with an API call (GetModuleFileName) but
I will make a new thread for that matter.

Thanks all,

Chris
0 Kudos