VOGONS

Windows 3.0 refuses to run in standard or enhanced mode

Topic actions

First post, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member

Hi,

I know that Windows 3.1 will run in DOS 7.1, and I'm trying to get Windows 3.0 working as well. It runs fine in real mode, but when I try standard mode, I get this:

SCREEN01.jpg

And when I try enhanced mode, it just goes back to the command prompt.

Windows for Workgroups 3.11 and 98 run fine in enhanced mode, so there's nothing wrong with my dos setup or my hardware or anything like that.

I also cannot get Windows 2.1 working in enhanced mode, but that's probably for another thread.

The wina20.386 file is in C:\win30. The same happens with it in the root directory.

config.sys:

[Menu]
menuitem=NoNetwork
menuitem=Network


[common]
switches=/f /e /w
device=C:\windows\himem.sys /testmem:off /cpuclock:off /v
device=C:\windows\emm386.exe noems
dos=high,umb,auto
devicehigh=C:\oak\oakcdrom.sys /D:mscd001
devicehigh=C:\windows\setver.exe
;DEVICE=C:\windows\CTCM.EXE
device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=044,850,C:\WINDOWS\COMMAND\country.sys
;devicehigh=C:\windows\command\ansi.sys
FILES=45
BUFFERS=30,0
;devicehigh=C:\usbaspi.sys
;devicehigh=C:\di1000dd.sys
;device=C:\NETWORK\ifshlp.sys
LASTDRIVE=Z
;DEVICE=C:\WIN3\SMARTDRV.EXE /DOUBLE_BUFFER

;DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /WIN95 /BLASTER=A:220 I:5 D:1 H:5 
;DEVICE=C:\SB16\DRV\CTMMSYS.SYS

[network]
Stacks=9,256
;DEVICE=C:\windows\CTCM.EXE
DEVICE=C:\dos\power.exe
DEVICE=C:\WIN3\IFSHLP.SYS
DEVICE=C:\windows\command\smartdrv.exe /double_buffer
install=C:\share.exe

[NoNetwork]
Stacks=64,512
devicehigh=C:\windows\ifshlp.sys





autoexec.bat:

rem SET CTCM=C:\CTCM
echo off
rem C:\WIN3\net start
SET BLASTER=A220 I5 D1 H5 P330 E620 T6 
SET MGA=C:\MGA\SETUP\
mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys
SET SOUND=C:\SB16
SET MIDI=SYNTH:1 MAP:G MODE:0

rem C:\SB16\AWEUTIL /S

rem SET PATH=%PATH%;C:\PROGRA~1\BORLAND\DELPHI5\BIN;C:\PROGRA~1\BORLAND\DELPHI5\PROJECTS\BPL

rem PATH=C:\WIN3;%PATH%

GOTO %config%

:Network
set screenthief=C:\st /com-
path=C:\win3;C:\network
C:\dos\power
lh C:\windows\command\smartdrv.exe /v
command /c C:\windows\dosstart.bat
C:\windows\CTCU /S /W=C:\WIN3
C:\SB16\DIAGNOSE /S /W=C:\WIN3
C:\SB16\MIXERSET /P /Q
command /c C:\windows\startnet.bat




:NoNetwork











Any ideas?

Thanks

Reply 1 of 14, by Davros

Posted on 
User metadata
Rank l33t
Rank
l33t

1: try reming out himem.sys and emm386 lines
2: try an earlier version of dos

Guardian of the Sacred Five Terabyte's of Gaming Goodness

Reply 2 of 14, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member

Windows complains about missing himem.sys if it's not loaded.

Unfortunately, I can't try an earlier version of DOS as the hard disk is FAT32.

I probably should have mentioned that I'm using the "Network" configuration.

I added d=48 to the emm386 line as suggested by the readme, but it didn't work.

I also disabled ifshlp.sys, and when I tried enhanced mode, I got this:

"The conventional memory in your system is fragmented and Windows cannot run in 386 enhanced mode;

please reboot your computer and try again or else run Windows in real mode by typing win /r."

I couldn't take a screenshot because I got a different error with screenthief loaded.

I also noticed that DOS tries to load Windows 98's ifshlp.sys even when using the "Network" configuration. Is there any way to stop it from doing this?

Thanks

Reply 3 of 14, by Gamecollector

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
AdamP wrote:

I also noticed that DOS tries to load Windows 98's ifshlp.sys even when using the "Network" configuration. Is there any way to stop it from doing this?

DOS=NOAUTO in the config.sys.

Reply 4 of 14, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member
Gamecollector wrote:
AdamP wrote:

I also noticed that DOS tries to load Windows 98's ifshlp.sys even when using the "Network" configuration. Is there any way to stop it from doing this?

DOS=NOAUTO in the config.sys.

I changed the auto in the dos= line to noauto and that seems to have worked. Thanks

I discovered here that standard mode is incompatible with emm386 and umbs. I disabled both, and I no longer get the error message, but now it freezes at the splash screen (I didn't try enhanced mode).

I'm also wondering if any of this has anything to do with the swap file. According to Windows Setup, there is no swap file. Does anyone know how to set up a Windows 3.0 swap file?

system.ini:

[boot]           
network.drv=
language.dll=langeng.dll
sound.drv=sound.drv
comm.drv=comm.drv
keyboard.drv=keyboard.drv
system.drv=system.drv
286grabber=vgacolor.gr2
386grabber=vga.gr3
fixedfon.fon=vgafix.fon
oemfonts.fon=vga850.fon
fonts.fon=vgasys.fon
display.drv=vga.drv
shell=progman.exe
mouse.drv=mouse.drv
[keyboard]
keyboard.dll=kbduk.dll
subtype=
type=4
oemansi.bin=xlat850.bin
[boot.description]

network.drv=No Network Installed
language.dll=English (International)
system.drv=MS-DOS or PC-DOS System
display.drv=VGA
keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
mouse.drv=Microsoft, or IBM PS/2
[386Enh]
network=*vnetbios,*dosnet
ebios=*ebios
EGA80WOA.FON=EGA80850.FON
EGA40WOA.FON=EGA40850.FON
CGA80WOA.FON=CGA80850.FON
CGA40WOA.FON=CGA40850.FON
display=*vddvga
device=C:\win30\wina20.386
device=lanman10.386
keyboard=*vkd
mouse=*vmd
device=*vpicd
device=*vtd
device=*reboot
device=*vdmad
device=*vsd
device=*v86mmgr
device=*pageswap
device=*dosmgr
device=*vmpoll
device=*wshell
device=*vhd
device=*vfd
device=*vpd
device=*parity
device=*biosxlat
device=*vcd
device=*vmcpd
device=*combuff
device=*cdpscsi
local=CON
…Show last 16 lines
FileSysChange=off
EMMEXCLUDE=C400-C7FF
noemmdriver=true
EMMSize=65,536
MaxPagingFileSize=512
Paging=yes
PagingDrive=C

[standard]
Int28Filter=10
NetHeapSize=8
PadCodeSegments=0
ReservedLowMemory=0

[NonWindowsApp]

Thanks

Reply 5 of 14, by Jorpho

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

I know that Windows 3.1 will run in DOS 7.1

It does?

There's a little third-party patching utility named OSR2FIX that I thought was necessary to get Windows 3.1 running under Windows 95 OSR2 and later (i.e. including Windows 98). Perhaps it will help with this Windows 3.0 problem?

Reply 6 of 14, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member

I used 3xstart to get 3.1 running on DOS 7.1. I don't know if it's necessary for 3.0. For Windows 1.x and 2.x, setver can be used to get them running on newer versions of DOS.

Reply 7 of 14, by SquallStrife

Posted on 
User metadata
Rank l33t
Rank
l33t
AdamP wrote:

I know that Windows 3.1 will run in DOS 7.1,

Can run. I don't know that it's a great idea.

The artificial lockouts are one thing, but Windows 3.xx wasn't designed to be run on filesystems other than FAT12/16, and wasn't designed to suit the way that DOS 7.xx doesn't lock the logical volumes for R/W operations as earlier versions did.

I wonder if it's worth adding "lock c:" to the autoexec.bat...

VogonsDrivers.com | Link | News Thread

Reply 8 of 14, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member

I just tried running Windows 3.0 in enhanced mode on another PC running a standalone installation of DOS 7.1, and it worked.

autoexec.bat:

SET MIDI=Synth:1 Map:E Mode:0
SET BLASTER=A220 I5 D1 H5 P330 T6
SET CTSYN=C:\sbdos
SET WINBOOTDIR=C:\WINDOWS\
path=C:\dos71
@ECHO OFF
PROMPT $P$G
MODE CON RATE=32 DELAY=1
MODE CON CODEPAGE PREPARE=((850) C:\DOS71\EGA.CPI)
MODE CON CODEPAGE SELECT=850
KEYB UK,,C:\DOS71\KEYBOARD.SYS
rem LH KILLER
LH C:\WINDOWS\MSCDEX.EXE /D:IDE-CD /V
rem LH C:\dos71\CTMOUSE
C:\mouse\mouse
rem C:\dos71\smartdrv.exe /v /x 1024
C:\sbdos\sbeinit
ECHO.
REM For locking volumes to enable "direct disk access":
REM CALL LOCKDRV.BAT
ECHO Now you are in MS-DOS 7.10 prompt. Type 'HELP' for help.
ECHO.
path=C:\NET;C:\dos71



rem C:\WINDOWS\ASP4DOS.COM

rem C:\NET\netbind.com
rem C:\NET\nwlink
rem C:\NET\umb.com
rem C:\NET\tcptsr.exe
rem C:\NET\tinyrfc.exe
rem C:\NET\nmtsr.exe
rem C:\NET\emsbfr.exe
C:\WINDOWS\net start

Config.sys:

rem DEVICE=C:\DOS71\ECHO.SYS W/e/l/c/o/m/e /t/o MS-DOS 7.10...
rem DEVICE=C:\DOS71\ECHO.SYS C/o/p/y/r/i/g/h/t M/i/c/r/o/s/o/f/t C/o/r/p. A/l/l /r/i/g/h/t/s /r/e/s/e/r/v/e/d.
DEVICE=C:\dos71\HIMEM.SYS /testmem:off /v
DOS=HIGH,UMB,AUTO
DEVICEHIGH=C:\DOS71\EMM386.EXE noems 
DEVICEHIGH=C:\DOS71\SETVER.EXE
;DEVICEHIGH=C:\DOS71\POWER.EXE
DEVICEHIGH=C:\DOS71\VIDE-CDD.SYS /D:IDE-CD
DEVICEHIGH=C:\DOS71\DISPLAY.SYS CON=(,,1)
DEVICE=C:\windows\ifshlp.sys
;DEVICEHIGH=C:\DOS71\ANSI.SYS
rem devicehigh=C:\oakcdrom.sys /D:mscd001
COUNTRY=044,,C:\DOS71\COUNTRY.SYS
SHELL=COMMAND.COM /P /E:640
;FCBS=4,0
FILES=90
rem FILES=24
BUFFERS=30,0
;LASTDRIVE=D
STACKS=9,256
;SET PATH=C:\DOS71;..;
;DEVICE=C:\windows\SMARTDRV.EXE /double_buffer
rem DEVICEHIGH=C:\WINDOWS\SMARTDRV.EXE
LASTDRIVE=Z

I wonder why it would run on a standalone version of DOS 7.1 but not on Windows 98's version? Could it have something to do with FAT/FAT32?

Reply 9 of 14, by sklawz

Posted on 
User metadata
Rank Member
Rank
Member

lo

just a guess, it may be something to do with
file control blocks which afaik don't exist
in fat32 (wikipedia seems to confirm it). win3.0
may be trying to access FCBs via one of the
myriad of software interrupts, which one, i have
no idea.

bye

Reply 11 of 14, by fronzel

Posted on 
User metadata
Rank Member
Rank
Member

Okay, here's my thought:

To run swapfile.exe you will need to run in real mode. You can't change swap file settings in standard or enhanced mode. So having a swap file or not should not influence the booting of windows 3.0. It should run perfectly fine with or without any swap file in any memory mode.

Your processor is definitely Okay. I tried to run win 3.0 on an NEC V30 (a better 8086/8088 clone) and it will not even try to boot standard/enhanced mode, so you can rule out problems with the processor i think.

Memory: By default you need to have an absolute minimum of a 286 and 1 MB of RAM. Keep in mind not all early boards actually remapped memory between 640KB and 1 MB, so they virtually only have 640KB which is not sufficient to run anything but real mode. With 2 MB RAM you should be fine though.

File System: Initially Windows 3.0 comes from a time where FAT12 was still around everywhere and FAT16 was fairly new. FAT32 was unknown at that time. From logic the memory mode should not be connected to the file system in any way, but from your observations something probably is. I'd format it FAT16 and simply see if that fixes the problem - then you know for sure.

Why you actually wanna run Windows 3.0 on a FAT32 system is beyond my understanding. Just out of curiousity i would like to ask why you don't use windows 3.1 - I must admit i don't know any single app that will run on Windows 3.0 but on Windows 3.1, so for your system i fail to see the benefit.

I run Windows 3.0 on my HP 200LX - but simply because the 8086 processor will not support windows 3.1 - Actually windows 3.0 is the last windows version to support 8086 and clones. Obviously on the HP i can only run in real mode due to the processor.

On a side note - there was also "Windows 3.0 with multimedia extensions", actually just windows 3.0 with the media player and MCI support. Ironically the whole multimedia package will not run in real mode, so from the viewpoint of a HP 200LX that version is just a waste of disk space. Maybe it might be interesting with your system though.

Reply 12 of 14, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member

Thanks

I'll try formatting a FAT16 partition when I get a chance. I haven't patched my other Windows 98 system to run Windows 3.x, so I can't tell you if it runs on there.

There's no real reason for running Windows 3.0. I suppose I'm just trying to see what works and what doesn't. Windows 1.x and 2.x apps will run in 3.0 but not 3.1. Windows 1.x and 2.x, and 3.1 also run fine on FAT32, so it's a little strange that 3.0 won't (I haven't tried 3.2, but I assume it will be no different from 3.1).

Reply 13 of 14, by Jorpho

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

Windows 1.x and 2.x apps will run in 3.0 but not 3.1.

How odd. It's apparently quite trivial to hack them so they'll run under Win9x, though.
http://toastytech.com/guis/misc.html

Reply 14 of 14, by AdamP

Posted on 
User metadata
Rank Member
Rank
Member

I think some Windows 1.x and 2.x apps may run in 3.1, but 3.0 was the last version to have full compatibility with them because 3.1 doesn't have real mode.

Go to top of page Go to top of page
Back to Milliways
Close window
Close window