Hi! Ken,

On Sat, 08 Feb 03, you wrote to me:

 KH>> "Your pop-up program is ready to run. When you have finished
 KH>> using
 KH>>  it, press Ctrl+C to close this window and return to Windows."
 KH>> I've tried everything I can think of (.PIF settings, .BAT
 KH>> tricks) to prevent the above from occurring; does anyone know 
 KH>> how to stop it?
 PQ>> Geeze, I haven't seen that message in years.  :)
 KH> Great! Now, all we have to do is rediscover what it was that you did,
 KH> back then. :)

Oooh, I'm talkin' about Win 3.0/3.1 - about 10 years ago.  :)  We ran an
IBM 3270 teminal emulator that gave us that "error" message.  I
recall now... we used a DOS printer spooler, to capture output from the
mainframe to a disk file, which ran as a TSR.

 PQ>> How are you manipulating the settings in the .PIFs, mate?
 KH> I've tried changing every setting possible (that would still allow
 KH> the .BATs to function) and I've checked 'close on exit'. I'm also 
 KH> EXITing explicitly, in the respective .BATs. I've tried, among other 
 KH> things, running a command (that I know terminates correctly) via 
 KH> COMMAND /C, just before the EXIT. It's an intermittent, tricky 
 KH> problem; please see
 KH> my reply to Charles Jennings, for more details. He's correct in
 KH> stating that Protected Mode software can be problematic, but I've 
 KH> found that it's not the only cause.

If it were me, I'd start checking the versions of COMMAND.COM you've got
lying about.  Particularly if you've done any updates/patches (the Y2K
update springs to mind).  The version Windows uses to re-load may differ
from the version in your batch's PATH; remember, there is a resident part
of COMMAND.COM that stays while the 'transient' portion is cleared while
executing an external command, even another COMMAND [/C] invocation.

FWIW, I have _never_ used "EXIT" in any batch file.

Cheers,
Paul.

--- Radius/W32 4.009-02.01.03/RC10