Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!comp.vuw.ac.nz!am.dsir.govt.nz!marcamd!tcnz1!ross
From: ross@tcnz1.tcnz.co.nz (ross Keatinge)
Newsgroups: comp.windows.ms
Subject: Re: Windows 3.0 386 mode
Message-ID: <580@tcnz1.tcnz.co.nz>
Date: 2 Apr 91 01:24:20 GMT
References: <91087.100905WALMSLEC@QUCDN.QueensU.CA>
Reply-To: ross@tcnz.co.nz (ross Keatinge)
Organization: Thomas Cook NZ Head Office, Auckland, NZ
Lines: 33

In article <91087.100905WALMSLEC@QUCDN.QueensU.CA> WALMSLEC@QUCDN.QueensU.CA (Chris Walmsley) writes:
>I am having a problems getting Windows 3.0 to work in either
>Standard mode or 386 enhanced mode.
>
>The machine is a PS/2 model 70 with 8 megs of extended, running
>PC-DOS 4.01.  No matter what combination of memory drivers/managers
>I use, Windows wont go into either Standard or 386 mode.

We had some similar problems. Are you running SHARE.EXE ?

I know others have mentioned about share but what I discovered is that 

SHARE DOESN'T HAVE TO BE EXPLICITLY INVOKED IN AUTOEXEC.BAT OR
CONFIG.SYS TO CAUSE A PROBLEM - THE MERE EXISTENCE OF SHARE.EXE
IN THE ROOT DIRECTORY OF THE DISK YOU BOOT FROM UPSETS WINDOWS.

This is my config.sys file for a PS/2 Model 70 with 4 Mb total RAM
running with Novell 386.
The /M:2 on the himem.sys line is important (see the readme.txt which
came with Windows).
The shell command is to increase the environment space.

files = 30
buffers = 2
device=himem.sys /M:2
device=smartdrv.sys 2048 512
shell=command.com /e:1024 /p


-- 
Jifong Chen, Systems Engineer (jifong@tcnz.co.nz)
Thomas Cook N.Z. Limited, PO Box 24, Auckland CPO, New Zealand, Ph (09)-793920
Disclaimer : I am not an official spokesperson for Thomas Cook