add exit to the autoexec.bat

and it is not a bug. Please read the description -exit as commandline parameter in the readme.

How would I add it to the autoexec.bat file? I have it in the autoexec section in dosbox.conf. In fact, here is a copy of the last one I tried.

1[autoexec]
2mount C: ..\System
3C:
4cd C:\Dagger
5dag.bat
6exit

Everything executed, but once I quit playing, it left me in a fullscreen DOSBox window instead of executing the line with "exit" on it.

You need to call the other batch file to continue processing. (e.g. "call dag.bat")

Ah I hadn't thought of trying to use call. Will try it and if I don't report back here, it works and I thank you. However, would I need to call exe and com files as well?

CALL is included inside the command inerpreter, it's not a seperate executable.

The call command only applies when you run one batch file from another.

this is btw not dosbox specific. "real" dos behaves the same with batch files and call

Really? I just tried placing a batch file that would echo "Inside batch file" to the screen and return and a line right below it in the autoexec.bat file that echoed "Outside the batch file" and then pause. Upon booting the machine I got both messages without using "call". I know all about call but have never had to use it before. I tested that batch file on a 486SX using DOS 6.22 and on a P2/233 using the DOS counterpart that comes with 98SE. Both worked without using call.

Test.bat:

1echo off
2echo Inside the batch file!

Autoexec.bat:

1test.bat
2echo Outside the batch file!
3pause

Works fine on both machines. Is this something that was needed back in DOS5? I used DOS5 with DOSShell on an 8086, but I didn't know batch-scripting back then and never used it.

Definitely doesn't work on msdos 6.22. Just re-tested.

1[autoexec]
2mount C: ..\System
3C:
4cd C:\Dagger
5dag.bat
6exit 

Whyt not put "exit" in dag.bat or put the content of dag.bat in the [autoexec] section?

I don't put it in the batch file because many older games came with pre-made batch files, such as Railroad Tycoon. Now if your average user grabs my front-end and selects the batch file and then starts the game up, he or she won't know why the game isn't exiting back to Windows when they're done playing. I want to make this program as idiot-proof and as user-friendly as possible.

It works now anyway, and that is all that matters. I don't know why this is working for me on my older DOS systems and not in DOSBox or for wd. I have multiple systems to test this on dating back to a 286, but it isn't that important. Use call for batch files in DOSBox, that's all a user needs to know when looking over this thread.

However, should I use call when starting an exe or com program, or just with batch files? I want games that use compiled program files to exit when done also, but if call isn't needed, I'll scan for .exe and .com and not plop it in the autoexec if those are found.

I'll say it again, since you ask again: the call command only applies when running one batch file from another; it is not used with executables.

Without CALL, you are transfering control to the other batch file, never to return. I can not explain how you are getting CALL behavior without using the command... it would mean your DOS is not behaving in a DOS-compatible way. 😒

it would mean your DOS is not behaving in a DOS-compatible way

I can second that (maybe using some command.com replacement or so).
The behaviour of batch file calling is documented ever since, and did
really behave like that (if you look at more complex .bat file systems you'll
see a lot of CALLs to other batch files for that reason).

Odd, must have to do with those complex configs I did so I'd get a boot menu when starting the old machines up. Somewhere along the way I did something that caused this. Once I get my new place and have room to setup all my machines, I'll figure it out and post my findings.

Thanks for the help though, my program is working wonderfully with DOSBox now.