VOGONS

Search

Common searches

Windows 1.x - 3.x

Topic actions

First post, by DosFreak

Posted on 
User metadata
Rank l33t++
Rank
l33t++

DosBox CVS 1/17/2005

Windows 1.0
Drops back to DOS during install, probably corrupted copy.

Windows 1.01

The following happens during installation:

Get write 0 to rom at ff904
write 0 to rom at ff900
write 1 to rom at ff903

Freezes dosbox.

Windows 1.02
Setup halts during installation, no indication of falied install, installation just halts while copying files.

Output in console:

14697: FILES:file open command 0 file CITOH.DRV
15208: FILES:file open command 0 file COURA.FON
15364: FILES:file open command 0 file COURB.FON
15520: FILES:file open command 0 file COURC.FON

Windows 1.03
setup just repeats screen.

Windows 1.04
setup just repeats screen.

Windows 2.03
Install finishes.
When run win.com, logo flashes for split-second then drops back to DOS.

Get this in console:

87209: FCB:DOS:29:FCB Parse Filename, result:al=0
87210: EXEC:Execute C:\WINDOWS\21386\WIN200.BIN 0
87210: FILES:file open command 0 file C:\WINDOWS\21386\WIN200.BIN
87210: EXEC:Illegal header
87236: INT10:Set Video Mode 3
87236: VGA:Blinking 8
87243: VGA:H total 100, V Total 449
87243: VGA:H D End 80, V D End 400
87243: VGA:Width 640, Height 400, fps 70.309021
87243: VGA:normal width, normal height aspect 1.000000

Windows 2.1 (286)

Install finishes.
When run win.com, logo flashes for split-second then drops back to DOS.

Get this in console:

90460: FCB:DOS:29:FCB Parse Filename, result:al=0
90461: EXEC:Execute C:\WINDOWS\21286\WIN200.BIN 0
90461: FILES:file open command 0 file C:\WINDOWS\21286\WIN200.BIN
90461: EXEC:Illegal header
90487: INT10:Set Video Mode 3
90487: VGA:Blinking 8
90494: VGA:H total 100, V Total 449
90494: VGA:H D End 80, V D End 400
90494: VGA:Width 640, Height 400, fps 70.309021
90494: VGA:normal width, normal height aspect 1.000000

Windows 2.1 (386)

When run win86.com, logo flashes for split-second then drops back to DOS.

Get this in console:

87209: FCB:DOS:29:FCB Parse Filename, result:al=0
87210: EXEC:Execute C:\WINDOWS\21386\WIN200.BIN 0
87210: FILES:file open command 0 file C:\WINDOWS\21386\WIN200.BIN
87210: EXEC:Illegal header
87236: INT10:Set Video Mode 3
87236: VGA:Blinking 8
87243: VGA:H total 100, V Total 449
87243: VGA:H D End 80, V D End 400
87243: VGA:Width 640, Height 400, fps 70.309021
87243: VGA:normal width, normal height aspect 1.000000

Windows 3.00
Works!

Windows 3.1

Setup locks up when it reached the screen where you enter Name, Computer Name, and workgroup.
Error on console:
a
3792860: KEYBOARD:Buffer full, dropping code

Windows 3.1 for Workgroups

Dynamic Core:
Setup locks up when it reached the screen where you enter Name, Computer Name, and workgroup.
Error on console:

3792860: KEYBOARD:Buffer full, dropping code

Windows 3.11 for Workgroups

Locks up where you enter name, company, product number:

Console:

1654131: KEYBOARD:Buffer full, dropping code

Full Core:

Keyboard works during install but mouse doesn't.

The following sums it up:

Windows 1.0 - Might be corrupt copy.
Windows 1.01 - Dynamic: Freezes dosbox during install. Full: Same
Windows 1.02 - Installation halts while copying files.
Windows 1.03 - Installation screens repeat, might be corrupt copy.
Windows 1.04 - Installation screens repeat, might be corrupt copy.
Windows 2.03 - Install finishes, Windows will not start.
Windows 2.1 (286) - Dynamic: Install finishes, Windows will not start. Full: Same
Windows 2.1 (386) - Dynamic: Install finishes, Windows will not start. Full: Same
Windows 3.00 - Works
Windows 3.1 - Dyamic: Setup freezes on Name, computer name, workgroup screen.
Full : keyboard works.
Windows 3.1 for Workgroups - Dynamic: Setup freezes on name screen. Full: keyboard works
Windows 3.11 for workgroups - Dynamic: Setup freezes on name screen. Full: Keyboard works but mouse doesn't.

Windows 1x - Not sure what's going on there. I would say corrupted copies but all but 1 of my Windows 1x copies came from images. The way I installed them in Dosbox is I extracted the images to one directory and then installed from there by mounting the directory as an A drive. I would like to install straight from the images but I am unsure how to do so under DosBox.

Windows 2x - Weird. Installation finishes but when I execute windows the logo flashes and then backt to DOS. The only thing I see in the output is an illegal header error after win.com executes win200.bin

Windows 3.x - It looks like keyboard doesn't work in dyanmic core sometimes and mouse doesn't work at all. when you execute FULL core the keyboard works and mouse still doesn't work.

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

Reply 1 of 12, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

earlier versions of windows use some dta fields i recall with fcbs.

input devices don't work in dynamic mode due to virtualisation.
mouse does work in win3.x enhanched mode. (be sure to use the cvs)

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 12, by mirekluza

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Windows 1.x - 2.x were never really targeted (so they have never ever worked in DOSBOX).
As for cores - standard core is "normal" not full. "Normal" should be the most compatible. Dynamic is most problematic (though it improves).

Nevertheless something was broken: In CVS from yesterday, using "normal" core, the installations of both W3.1 and WFW 3.11 crash the whole DOSBOX (see below). The setup starts, copies files but just when starting to GUI it crashes (I wonder - was not something broken by the recent exception handling update in CPU.CPP? - just guessing):

CONFIG:Loading settings from config file dosbox.conf
MIDI:Opened device:win32
XGA: Read from port e2e0, len 1
XGA: Read from port 92e8, len 2
Exit to error: RET:SS selector type no writable data segment

Mirek

Reply 3 of 12, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

hmm well the error message is clearly from cpu.cpp.
a bit odd as It works at my place I think.

wd will probably know more about it.

Water flows down the stream
How to ask questions the smart way!

Reply 4 of 12, by mirekluza

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

I compiled a new version yesterday, there was a bit different error, but it crashed at the same place (before booting GUI in installer):

104507733: CPU:Illegal Unhandled Interrupt Called 5C
104507872: EXEC:Execute C:\AA14\SYSTEM\krnl386.exe 0
104507872: FILES:file open command 0 file C:\AA14\SYSTEM\krnl386.exe
104507872: EXEC:Illegal header
104562513: DOSMISC:DOS:Unhandled call DC al=44. Set al to default of 0
104563231: FILES:file open command 0 file CON
104563636: FILES:file open command 0 file CON
104564041: FILES:file open command 0 file CON
104564446: FILES:file open command 0 file CON
104564851: FILES:file open command 0 file CON
104601660: FILES:file open command 0 file C:\AA14\SYSTEM\KRNL386.EXE
104632890: CPU:Illegal/Unhandled opcode F
Exit to error: RET:rpl<CPL
Press enter to continue

I was able to install W3.1 in CVS from 14th January (using the same installation files). Just the current CVS is broken.
Is anyone able to reproduce it? It happens *DURING INSTALLATION*. The previously installed Windows work ok.

Mirek

Reply 5 of 12, by wd

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

No windows <3.x (especially 1.x is too odd), is there any need for it?

Don't know about the invalid SS selector (does it change when
you use vga??), but the RET:rpl<CPL needs to be added for the
setup (they adjust the priviledge level themselfes). Thanks
for noticing it.

If cpu.cpp exits, please note if it works when you use
CPU_CHECK_EXCEPT (somewhere at the top of cpu.cpp, qbix added
some info there) or with CPU_CHECK_IGNORE.
There are more checks done in cpu.cpp when using a debug
build, and they'll exit dosbox if they fail so it can be taken care of.

wd

Reply 6 of 12, by mirekluza

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator
wd wrote:
Don't know about the invalid SS selector (does it change when you use vga??), but the RET:rpl<CPL needs to be added for the setu […]
Show full quote

Don't know about the invalid SS selector (does it change when
you use vga??), but the RET:rpl<CPL needs to be added for the
setup (they adjust the priviledge level themselfes). Thanks
for noticing it.

"Invalid SS selector" is the crash reason when running the DOSBOX compiled without debugger, "RET:rpl<CPL" is the crash reason when running the debugger enabled version.
I did not try changing anything in CPU.CPP yet.

Mirek

Reply 7 of 12, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

well the regular version (without debugger) is with check_ignore.
so mirek tested both.
if I add that rpl test then it's added for both version and should work for both.
Will add it.

Water flows down the stream
How to ask questions the smart way!

Reply 8 of 12, by DosFreak

Posted on 
User metadata
Rank l33t++
Rank
l33t++
wd wrote:

No windows <3.x (especially 1.x is too odd), is there any need for it?

Curiosity? 😀

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

Reply 10 of 12, by mirekluza

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Well, running Windows 1.x or 2.x would be just an interesting achievement (I also tried them in DOSBOX 😀 😀 ),but there is not much practical use for it (unlike W3.x - this is important).
So I quite understand that WD (who probably did most things concerning running of Windows in DOSBOX) sees it as not worth the effort.

As far as Windows are concerned: I think that support for win32s programs in W3.x would be more practically usefull, than trying to make W1.x or W2.x work.

Mirek

Reply 11 of 12, by Snover

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Of course; practicality is always important. But pointing out that things like Windows versions 0-2 don't run just reminds us that there's a long way to go to get everything emulated perfectly 😀

Yes, it’s my fault.

Reply 12 of 12, by DosFreak

Posted on 
User metadata
Rank l33t++
Rank
l33t++

I just tested them for fun and because I hadn't seen a Windows 1.x or 2.x post yet at VOGONS. 😀

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

Go to top of page Go to top of page
Back to DOSBox Games/Apps
Close window
Close window