I don't see anything wrong with "not emulating DOS". Keeping the faith can be protected from additions to functionality like this by requiring a command line parameter when launching the program, e.g. DOSBox.exe -AllowExtensions If this wasn't present then DOSBox would behave as it does now. …

Yep, seems to work here. I'm working on getting it so that it returns error level 0-255. Also, a useful addition to DOSBox would be for it to set an environment variable to the errorlevel.

@Qbix I disagree. When you are using DOSBox essentially as a 32-bit command processor emulator for a single command line, then it makes the emulation more complete. I'm not suggesting it become a permanent feature, but a DOSBox.exe command line option like -SetErrorLevel . @Malvineous I like your …

Many thanks, that seems to have fixed the problem (so far...)

I feel a feature request coming on...

I have DOSBox set up so that I can pass it command lines which previously were called directly from batch files (I call it from a wrapper batch file that checks to see if the platform is 64-bit - if it isn't, it just executes the command line, otherwise it fires up DOSBox and passes the command line …

Yes, Windows 10. I tried all the output options (none, surface , overlay , opengl , openglnb , ddraw ) and the result was the same in all cases. The effect doesn't happen immediately all the time, sometimes you need to switch between windows a couple of times to get it to trigger, but the effect is …

I have the following problem: I start DOSBox I Alt-Tab to another window I Alt-Tab back to DropBox window At this point, the prompt will show a rapid succession of filenames - what is actually happening is that DosBox is imagining the TAB key is being pressed repeatedly - I have verified this by …

I think I was confused. The window that is displaying is the status window, and for some reason the main DOSBox window wasn't displaying at all. I had just looked at the window displayed, couldn't see a ">" prompt, and assumed it had snagged during startup. Other edits I had made to the batch file …

It used to run under W8.1, but it now seems broken. This is as far as it gets: DosBox.png and that is all that seems to get written to the log file. The DOS window is unresponsive - i.e. keys typed when it has focus have no effect. The "X" on the window title bay closes the window works, as does …

DOSBox has proved a lifesaver for me when maintaining legacy 16-bit DOS apps under 64-bit Windows, but one thing I miss is having window sizes greater than 25x80 - is there any provision for specifying the number of lines and columns as there is for "normal" DOS prompts? TIA R

Two backslashes didn't work, one forward slash did. Strange that the CD command doesn't need that syntax, but I guess its because the mount command is a "special" i.e. not handled by the same command processor that the DOS internal commands are handled by. Thanks for your help.

I have this command for invoking DOSBox "%DBEXE%" -userconf ^ -c "mount c c:\" ^ -c "path=C:\projects\tools;C:\projects\toolsrc" ^ -c C: ^ -c "cd %CD%" ^ -c "%*" The carets are DOS batch continuation lines. %DBEXE% points to the DOSBox.exe executable. DOSBox starts OK - the unravelled command …

Obvious when I think of it! Many thanks for the quick reply.

Is there any clean way of setting an environment variable on the command line that starts DOSBox? I ca'n see anything mentioned in the command-line parameters. What I want is something like: DOSBox C:\Folder -setenv name=fred -c MyCommand.bat such that I can reference %Name% within the DOSBox …

I have installed DOSBox and it looks pretty robust. However my main reason for installing was to enable me to run some batch builds that depended on some MS-DOS 16 bit apps that it is not worth porting to 32-bit. These batch files run fine on Windows XP, but I have just ported to a WIndows 8 64-bit …