Hey guys,

i got something curious happening here with my DOSBox, i can't explain myself. I've got a larger batch file, which initiate some values, starts the DOSBox for evaluation and in the end handle the output files generated inside DOSBox. For simplicity i will not post exactly this script, but i wrote some kind of substitutional script, which do more or less the same. Here it comes.

1@echo off
2:: Relative path to DOSBox folder
3set dosboxpath="..\..\DOSBox-0.74"
4
5:: Loop 25 times
6for /l %%a in (1,1,25) do (
7	path %dosboxpath%
8
9        :: Starting DOSBox.exe, initiating the user specific config file with an file link DB.lnk
10        :: Echoing "hello world" to the file "log"
11        :: Closing DOSBox and return to parent batch file
12	DB.lnk -c "echo hello world > %cd%\log" -c "exit"
13	
14        :: create a folder with the name of the current run from 1...25
15	mkdir %cd%\%%a
16        :: Move the log file, created by DOSBox, inside the new folder
17	move %cd%\log %cd%\%%a
18)
19:: EOF

In fact, not a difficult task. Open DOSBox, create a file, create a subfolder, move file into subfolder, repeat.

Everything works fine, until, i switch off the monitor! No, really! If i'm switching off the monitor after starting the batch, all the files and folders up to the "switch off moment" were created perfectly. But than, nothing seems to happen after it. In my cmd-console a failure occures, which tell me, that no file could be found. This means, DOSBox didn't started properly.

I don't get it, what's the relation between my monitor switching button and the proper execution of my DOSBox?!? This phenomena is so curious to me...

Best regard