So you saw this? Windows 3.1x DOSBox Guide

Haven't tried it myself.

yea, with the ykhwong build i tried the tseng drivers and about everything else in that thread, with no luck, including the svga drivers that come with win31.

In order to be able to use the SVGA drivers from W3.11 in DOSBOX, you must patch them to be VESA compatible.
Go to:
http://japheth.de/dwnload1.html
And download the file SVGAPtch.ZIP (run the program on SVGA driver and it will work in DOSBOX).

If nothing helps - and if you did all you wrote - well, your copy of Windows is probably corrupted... Since it works for other people...

Mirek

@iamthejake2000: Did you switch the DOSBox itself to Tseng emulation first? In dosbox.conf, section [vga], svgachipset should be set to et4k.

mirekluza wrote:

In order to be able to use the SVGA drivers from W3.11 in DOSBOX, you must patch them to be VESA compatible. Go to: http://japhe […]
Show full quote

In order to be able to use the SVGA drivers from W3.11 in DOSBOX, you must patch them to be VESA compatible.
Go to:
http://japheth.de/dwnload1.html
And download the file SVGAPtch.ZIP (run the program on SVGA driver and it will work in DOSBOX).

If nothing helps - and if you did all you wrote - well, your copy of Windows is probably corrupted... Since it works for other people...

Mirek

aah thanks a lot! works like a charm. but is there a way to get windows 3.1 to run in enhanced mode? thanks.

For dosbox 0.65, try ems=false and just type "win" without parameters.

i guess it must be something in my autoexec.bat or config.sys files. i did a fresh install of windows and everything's fine. i've been trying to get into enhanced mode on a setup from a hard drive from a very old computer of mine. i'll mess with the boot files, thanks for all your help!

ah, probably more likely something botched in your system.ini or win.ini (since DosBox doesn't read and execute the boot files (autoexec.bat/config.sys) unless you are booting from an hdd image). If those had some drivers loaded for 32-bit disk and/or file access this would explain a lot. Just compare those two files to your working windows and comment things out (with 😉 until it works 😀
I got my old setup (with Norton Desktop and such things) pretty fast into working order that way.

Tried S3 640x480x16 million color more under Windows 3.1 and it works fine.

Running DOS programs in Windows 3.1 in DosBox crashes DosBox

Just a Collection of Win 3.1 video driver sites:

S3:

http://ranger.s3graphics.com/swlib/?license=accept
http://ranger.s3graphics.com/swlib/764drv/

SVGA.exe:

http://oldfiles.org.uk/powerload/win3x.htm (and Windows 3.11 Update for 3.1)
http://www.winsite.com/bin/Info?500000024307

SVGA VESA Patch:

http://www.japheth.de/dwnload1.html

SciTech SDD + UniVBE + SNAP:

http://www.scitechsoft.com/ftp/sdd/
http://www.scitechsoft.com/ftp/snap/

http://arcadecontrols.com/arcade_downloads.shtml#Drivers

I have a problem with running win 3.1 in 256 color mode:

When it runs in 256 color mode and I start scrolling down a window, dosbox freezes for a moment then it closes. I have this problem in surface and direct3d mode too, and so far I've only encountered it in gulikoza's dosbox. How can I fix this?

It could be a bug in gulikoza's version. Try the official build.

I tried it with the official build, but the problem is still there.

Radinor wrote:

I tried it with the official build, but the problem is still there.

What errors does it give before closing (in the console or the console output file)?

JAL

This is weird. I have a Windows 3.11 setup and I tried to reproduce the problems Radinor is complaining about, but everything works fine here.

Can anyone else try to reproduce the crashes?

It'd be nice to know with whic program that happens.

I've tried some other things like: mounting a different directory as drive C: and installing win 3.1 there, then putting the S3 driver on it, because I thought that maybe something is wrong with the current windows install, but that didn't work. I even tried using the XGA driver and the Paradise card driver, but that didn't work either.

In dosbox.conf, the video memory is set to 2 MB and the system memory is set to 8 MB. I tried turning them up a bit (sys mem: 16 MB, vid mem: 10 MB), but that didn't work either.
And the strange thing is that, it only happens if I use the scrollbar to scroll down, if I use the down arrow key, there's no problem.

I finally found a way to fix this. What I did is that I set the video chipset from s3 to et4000 in gulikoza's dosbox, installed et4000 drivers, and now it works!

A screen shot of Windows 3.1 running in Dosbox
[img]windows.gif
[/img]

oooooooooookay.... a little late in the game 😀