Does it work in real dos? In what way does it "jam"?

It is because of that

@ECHO off

at the start. Remove it and you will see what is wrong.

1set /p

not supported in dosbox nor in DOS 6.22

Is there an other option to create a menu for games that is compatible with dosbox?

grtz. netolk

Remove the "set /p" stuff and use something like CHOICE.COM or 4DOS?

You can develop a _real_ menu system with WBAT. I've created a full-blown menu system with all my installed DOS games, and it looks terrific. It's quite a bit of work, though.

http://frontends.dosbox.com/

Yea ADDiCT but when I remove "set /P" then you can't chose a game...

Write a letter to microsoft that it sucks that they didn't have a /p switch for msdos.

The CHOICE command is built into DOSBox, no need to use an external program.

1choice /N /C:12345 Type the number to print text.
2if errorlevel 5 goto Exit
3if errorlevel 4 goto Prehistorik2
4if errorlevel 3 goto Prehistorik
5if errorlevel 2 goto Pacman
6if errorlevel 1 goto Lemmings

It is important to test ERRORLEVEL in descending order for something like this because lower levels test TRUE compared to higher levels.

It is important to test ERRORLEVEL in descending order for something like this because lower levels test TRUE compared to higher levels.

Is this a bug in dosbox?

Same behavior in MS-DOS; apparently it is a less-than-or-equal-to comparison.

Tanks ripsaw8080 it works

grtz. netolk

I have now a other problem... I have 13 games so I tryed with A B C ect. but I doesn't work

can somebody help me?

wd wrote:

http://frontends.dosbox.com/

It should work. You're probably not doing it correctly.

1choice /N /C:ABCDEFGHIJKLM Type the letter to print text.
2if errorlevel 13 goto label13
3if errorlevel 12 goto label12
4...
5if errorlevel 1 goto label1

I used the ellipsis there because I didn't want to type all 13 of them. Did you try to use "errorlevel A"? The ERRORLEVEL is a number, and in the case of the CHOICE command, it corresponds to the number of the choice in the list of possible choices.

However, if you are using this batch as a game launcher, you really will find using a frontend much more capable and accommodating.

ripsaw8080 wrote:

Same behavior in MS-DOS; apparently it is a less-than-or-equal-to comparison.

actually
if errolevel 1
has always coincided with
greater-or-equal-to 1
and not less-than-or-equal-to

in fact if one should write
if errorlevel 0 goto :zero
if errolevel 1 goto :one
that wouldn't do because with errorlevel==1 it would goto :zero as well

IOW if error level 0 always rings TRUE

or, it would have to read
if not errorlevel 1 goto :zero
for it to be correct IMO.

ripsaw8080 wrote:

Did you try to use "errorlevel A"?

I don't think that would work either.

Please don't confuse the issue. It's simply a matter of which terms you place on which side of the equation. It's less than or equal if you're comparing the test value in the batch file to the actual level value in DOS.

In other words: "if the errorlevel is at least <some number> then <do something>"

I used the "errorlevel A" to ask if that was the mistake that was made, obviously it won't work because it's a numeric value.

OK, then, obviously I must have gotten your statement wrong, as if it were somewhat problematic,
but I was just knee-jerk reacting along the old guideline to reassert that between errorlevel and n
a '>=' mark must be always seen etc.

I don't want to confuse any issues 😦

A handy mnemonic device, I suppose, but I wasn't following your guideline in my statement. 😉