Ralph;
Oh boy - here we go.
It seems especially hard for me to believe that a program written for DOS could know how to detect if it was running in a DOS session under Windows. That first choice is badly mis-worded!! [angry]
It's really the other way around - it's to prevent the Windows kernel from monitoring the DOS session, other than to give some slice of time to the process. (Slicing the processor's time among various apps is called multi-tasking, but you already knew that, right?) Well, if you've been around computers for more than a few days, you'll recall that we used to have "real mode' and "protected mode". Which mode is used for your progroam (your DOS session) is dictated by the first choice under the Advanced tab.
By checking "Prevent.....", you've told Windows to monitor the DOS session for signs of finished activity, and if so, end the session. Left unchecked, this would tell Windows to
not monitor the session for activity, and there's the root of your problem. In terms of modes, real mode is the unchecked choice, and is unmonitored. Protected mode is the checked choice, and it's monitored for activity.
'Nuff of that nonsense.
What you've done is good, as far as it goes. However, which was easier - playing hit and miss with Windows settings, or editing a batch file? More to the point, if the batch file has the command "exit" on the last line, would you even have to play with your settings? (Hint: The answer contains only two letters.
) Now imagine how you would tell someone else to make the DOS session close automatically, no matter what. See my point? Thought so.
Gotta run, hope this helped explain why your solution worked, and why I didn't offer it in the first place. Wouldn't want you to think I didn't know about that stuff, now would I? [lol]
Oddysey
[lol] 