6 replies to this topic

[bbergstr]

I develope installs on a Win2k Pro box with 6.31, and have been for years. Suddenly now when I use SdShowMessage I see this wierd problem on my development box -- iKernel stays running, even on very simplw installs. Take the following script for example:

program
MessageBox ("Start", INFORMATION);
SdShowMsg("test SdShowMsg", TRUE);
Delay(2);
SdShowMsg("", FALSE);
MessageBox("End", INFORMATION);
endprogram


After running this IKernel.exe stays in memory. If I comment out the SdShowMessage lines, it behaves normally.

Can anyone tell me what is going on here?

Thanks,
--BB
*******************************************************
** NOTE: I cannot receive exe attachments at
this address, please ZIP the file before sending.
**
Brian C. Bergstrom
Software Development Engineer
Stellent, Inc.
http://www.stellent.com
*******************************************************

[Taco Bell]

Does it matter if you run it as a regular install instead of through the debugger?

[bbergstr]

Nope, it happens whether I'm using the debugger or not.

[Taco Bell]

Hmm, I don't know what's causing this problem then. I develop on W2K & XP and support installs on NT4, W2K, & XP, but have never seen this issue.

Maybe your iKernel was overwritten or its installation is corrupt, so try completely uninstalling & reinstalling IS. If so, you could do the following to try and confirm this:
- Look at your project's Script Files\Setup.map for the following entry:
"ISRT._SdShowMsg isrt.obl(SDSMSG.obs)"
- Compare your project's media report files for any unusual changes along these lines (i.e. different sizes, date/timestamps, CRC values, etc.).

Worst case, I suppose it may be time to re-do your whole PC and reinstall everything from scratch. Over time odd problems like this can start to crop in Windows.

Good luck then, and sorry I couldn't be more helpful.

[Ozone]

I cannot duplicate it on my PC, but I'll put in my two cents.
Try adding one or both of these commands at the end of your script.

SdShowMsg("", FALSE); // Forces the msg to go away

exit; // Forces program termination.

[Ozone]

I have accidentally duplicated your results. The setup program will remain in memory when I am running Compuware’s QARun quality control program at the same time. I suspect a conflict with a running program or some recently installed software on your PC could be the culprit. (My prior suggestions do not work when the setup remains in memory).

[bbergstr]

Thanks for the thoughts. Seeing as it *only* happens on my system, I'm just going to rebuild the system. This system is approaching the 1year mark anyway, so it's time.

I also thought it might be some screwy conflict, but rather than try to track it down now, I'll just get a clean build.

Thanks.
--BB