Page 1 of 1

Windows 3.0 real mode problem - with et4000ax

Posted: Mon 17 Jul, 2017 2:26 pm
by ovctvct
When trying to run Windows 3.0 MME in real mode, with AMI 386DX and ET4000ax, this happens:
Image

I'm using 256 color ET4TURBO drivers for 1024x768 mode if that matters.

Driver linK: http://www.iol.ie/~essentialsoft/win3/et4000-win30.vfd

Re: Windows 3.0 real mode problem - with et4000ax

Posted: Mon 17 Jul, 2017 3:16 pm
by omarsis81
I never heard of that Windows 3.0 release... did you try the same setting with the retail Windows 3.0 standard version?

Re: Windows 3.0 real mode problem - with et4000ax

Posted: Mon 17 Jul, 2017 3:41 pm
by tr.StEalTH
You could try loading with /r or run setup /i Then select the devices instead of trusting Windows to select them.

Re: Windows 3.0 real mode problem - with et4000ax

Posted: Mon 17 Jul, 2017 4:28 pm
by Battler
He said he's running Windows 3.0 in real mode, therefore, with /r. :p

Re: Windows 3.0 real mode problem - with et4000ax

Posted: Mon 17 Jul, 2017 4:59 pm
by omarsis81
ovctvct wrote:When trying to run Windows 3.0 MME in real mode, with AMI 386DX and ET4000ax, this happens:

I'm using 256 color ET4TURBO drivers for 1024x768 mode if that matters.

Driver linK: http://www.iol.ie/~essentialsoft/win3/et4000-win30.vfd
Does it only happen with that et4000ax card? Did you try others?

Re: Windows 3.0 real mode problem - with et4000ax

Posted: Mon 17 Jul, 2017 5:25 pm
by Battler
- omarsis81: It's a bug with a specific set of ET4000AX drivers. The correct solution is to see if it's actually an emulator bug, and if yes, fix it.

Re: Windows 3.0 real mode problem - with et4000ax

Posted: Tue 18 Jul, 2017 4:34 am
by tr.StEalTH
I was thinking he was running /m tho both are force commands Battler. I shouldn't read so fast half the time. I wouldn't think it was a bug being he should be running 386 Enhanced mode for that build.