Path: utzoo!attcan!uunet!timbuk!cs.umn.edu!msi.umn.edu!src.honeywell.com!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!djbpitt
From: djbpitt@unix.cis.pitt.edu (David J Birnbaum)
Newsgroups: comp.windows.ms
Subject: Re: 386 enhanced mode
Message-ID: <57852@unix.cis.pitt.edu>
Date: 7 Nov 90 13:55:03 GMT
References: <7017@hub.ucsb.edu>
Reply-To: djbpitt@unix.cis.pitt.edu (David J Birnbaum)
Distribution: comp.windows.ms
Organization: Univ. of Pittsburgh, Comp & Info Services
Lines: 28

In article <7017@hub.ucsb.edu> 6600bori@ucsbuxa.ucsb.edu (Boris Burtin) writes:

>I'm running Windows 3.0 on my 25mhz 386 with 2 megs, and I had some 
>questions about this so-called enhanced mode.  When I type just "win"
>at the command prompt, Windows throws me into STANDARD mode with 907k
>RAM.  The manual says that with my configuration, it should default to
>enhanced....
>Is it normal for Windows not to default to enhanced mode? 

I don't know about normal, but I get the same results.  I am running 
Windows 3.0 on a 386sx with 2M.  When I type 'win', it starts in *real*
mode.  If I type 'win/3' it starts in 386 mode.  As I understand the
internal 'best guess' approach, Windows should default to 386 mode for
my system.  No big deal; I just start it with the '/3' switch.

One reason may be that I use 4dos, rather than command.com.  One in-
teresting consequence is that Windows refuses to run in standard
mode; if I type 'win/s', it dumps be back at the command line and tells
me that I am doing something wrong.  This doesn't happen under
command.com.

As I said, typing 'win/3' solves all my problems.  But I am curious
about why I should have to do this.

--David
=======================================================================
David J. Birnbaum         djbpitt@vms.cis.pitt.edu [Internet]
                          djbpitt@pittvms.bitnet   [Bitnet]