VOGONS


Old Windows versions

Topic actions

First post, by RX9

User metadata
Rank Newbie
Rank
Newbie

I have been playing around with emulating old versions of Windows within DOSBox with some success. Both 3.0 and 3.1 run fine, and I have actually gotten some programs to run that I had to give up on many years ago when I upgraded from my old 486. Windows 1.01 and 2.03, however, are a different matter. Both can be run from a pure DOS boot on my 98SE system (the former requiring an update to the SETVER table), but neither run within DOSBox. They both provide a brief color splash followed by a crash. Does anyone have any ideas?

Reply 1 of 12, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

win2 should start up if you set the reported dos version to 4.0 (i think).
win1 can be made to install and start up, but it's unstable so better
leaving it at "uninstallable".

Reply 2 of 12, by RX9

User metadata
Rank Newbie
Rank
Newbie

Is there a command line switch for selecting DOS version? I went through the dosbox.conf file for examples, but I couldn't find any.

Reply 3 of 12, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Type
"ver"
then
"ver set 4"
then
"ver"

Reply 4 of 12, by RX9

User metadata
Rank Newbie
Rank
Newbie

Once again, WD, you are the man with the answers.

Reply 5 of 12, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Windows 1x and 2x are so small they can even be booted from a 1.44mb floppy in DosBox. I tested this a couple of months ago and they worked. I want to say 2x crashed doing something in Windows though.

How To Ask Questions The Smart Way
Make your games work offline

Reply 6 of 12, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

They have nice crazy display modes iirc, some didn't even work 😀

Reply 7 of 12, by dh4rm4

User metadata
Rank Oldbie
Rank
Oldbie

Yeah we're talking pre VESA for sure...

Reply 8 of 12, by RX9

User metadata
Rank Newbie
Rank
Newbie

I found the following thread on the net to help me get Windows 1.01 working on a clean DOS boot several weeks ago:

http://www.computing.net/windows31/wwwboard/forum/11819.html

The "C:\> SETVER WIN100.BIN 3.40" command followed by a reboot resulted in perfect display and functionality where there had been none before. Is there any way that this info might help DOSBox execution, or are we still at square one?

Reply 9 of 12, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Dunno, think that .bin file is a regular executable so it should work
with the "set ver x" thing. But working means mostly "will start up",
might not be usable at all.

Reply 10 of 12, by RX9

User metadata
Rank Newbie
Rank
Newbie

I have discovered a bootable disk image of Windows 1.01 on line at this location, which is usable with DOSBox:

http://toastytech.com/guis/win101disk.zip

It is necessary to use the "boot" command, and toggle "Num Lock" for everything to work properly, but there don't seem to be any stability issues.

Question: is there a way to force DOSBox to close upon exit, as the standard "-exit" command doesn't seem to work in this mode?

Reply 11 of 12, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Once something is booted there's no way out besides closing dosbox
the "hard" way. If you type exit at the real-dos prompt it just ignores it
at the outer command.com instance, so it's not helpful (same for the
-exit parameter, only useful in the dosbox-internal command prompt).

Reply 12 of 12, by RX9

User metadata
Rank Newbie
Rank
Newbie

Well, it's a small price to pay compared with the overall result. Thanks for the reply.