Please help!
Don't know what is the problem, but after the program ends, there is an endprogram, but setup.exe and ikernel stays in memory.
What and How can I do to prevent it?
Thanks
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
setup.exe and ikernel.exe stays in memory
Started by
nelly
, Jan 26 2005 13:35
11 replies to this topic
Posted 26 January 2005 - 15:59
Exactly what version of InstallShield Professional are you using and what OS/service pack are you observing this behavior?
Posted 26 January 2005 - 16:20
I use ver 6.31. And as fas as I know we don't use service packs.
I've tried to do exit; at the end of the program, this wasn't helpuff niether.
Thanks for reply.
I've tried to do exit; at the end of the program, this wasn't helpuff niether.
Thanks for reply.
Posted 27 January 2005 - 02:41
I'm asking upon which version of Windows, and in turn its service pack level, are you observing this behavior? For example, Windows NT 4.0 SP6a, Windows 2000 SP4, Windows XP SP2, etc. To find out this information on NT-based OSes, run the program "winver.exe".
Also, does this happen on every system or just some of your computers?
Also, does this happen on every system or just some of your computers?
Posted 27 January 2005 - 09:35
Oh, sorry for misunderstanding,
I use Windows XP SP1, and yes it's happenning on all computers.
Thanks again
I use Windows XP SP1, and yes it's happenning on all computers.
Thanks again
Posted 27 January 2005 - 14:46
Were there any recent additions/changes that could account for this such as a custom dialog box?
Posted 27 January 2005 - 15:10
Yes, we do use a lot of custom dialogs, does this can couse the problem.
But I don't think there were addings, only changes.
But I don't think there were addings, only changes.
Posted 28 January 2005 - 02:51
Make sure every call to UseDLL has a matching call to UnUseDLL so that DLLs are not left in memory after they are no longer needed.
Posted 30 January 2005 - 10:09
Thanks for replying, I have checked every UseDLL and it's being closed each time with unUseDLL.
Do you have another suggestion?
Do you have another suggestion?
Posted 31 January 2005 - 11:55
I've found this issue:
"Error installing iKernel.exe" During Debugging
Description:
After you debugged your setup once, when you try to launch the debugger a second time, you get the "Error installing iKernel.exe".
Cause:
Sometimes iKernel.exe stays in memory after you finish the debugging session.
Workarounds:
Use TaskManager to terminate the iKernel process.
Status:
This problem has been reported in the newsgroups for IS 6.01. It could not be reproduced with IS 6.10.
I couldn't find anything wrong in the code, so I suppose that the problem is in Installshield it self.
"Error installing iKernel.exe" During Debugging
Description:
After you debugged your setup once, when you try to launch the debugger a second time, you get the "Error installing iKernel.exe".
Cause:
Sometimes iKernel.exe stays in memory after you finish the debugging session.
Workarounds:
Use TaskManager to terminate the iKernel process.
Status:
This problem has been reported in the newsgroups for IS 6.01. It could not be reproduced with IS 6.10.
I couldn't find anything wrong in the code, so I suppose that the problem is in Installshield it self.
Posted 31 January 2005 - 14:15
How is that your issue when you didn't report seeing that error message, your not debugging the setup, and you're on IS 6.31?
Posted 01 February 2005 - 11:49
Yes you are right,
from some reason I've thought for a min that my Installshield ver is 6.03 and not 6.3. Sorry
from some reason I've thought for a min that my Installshield ver is 6.03 and not 6.3. Sorry