🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.windows.ms
Article #365

Re: HELP: Windows 3.1

#365
From: Michael Polen
Date: Tue, 07 Apr 1992 20:45
40 lines
2536 bytes
In article <1992Apr7.051927.21779@cco.caltech.edu>, heathh@cco.caltech.edu (Heath Ian Hunnicutt) writes:
|> bakalov@WFUNET.WFU.EDU (Rudy Bakalov) writes:
|> 
|> 
|> >        Hello everybody:
|> >        I madly need your help. I spent the whole day trying to install
|> >Win 3.1 and I couldn't. It's a real shame-- I used to think my CS degree
|> >has some value.
|> [Windows only comes up in 3.0a /s mode...]
|> >        I am running 386/25MHz, 4Mb, ET4000, Stacker, 386MAX.
|> >        Please, help ASAP. I feel I am missing something very simple, but
|> >I couldn't find it. I tried to install in a new DIR-- same effect.
|> >        I WILL HIGHLY APPRECIATE ANY FEEDBACK.
|> 
|> 	Since you are running Stacker, you have to configure it in some
|> certain manual that I read in setup.txt but don't recall.  Anyway, it's
|> there for you to read.  

Only true if you have swapped the your boot drive to be a stacked drive.  If
so check the documentation.
|> 
|> 	Furthermore, try booting off of a floppy so that EMM386 is installed,
|> not 386MAX.  If possible, do not use Stacker.  (Obviously, you must run
|> Stacker to install on a Stacker drive..)  Win 3.1 should install Ok with
|> a standar setup like this.
|> 
|> P.S. My 3.1 upgrade installed A-OK, and I am running MSDOS 5.0, EMM386,
|> no stacker, tons of TSRs, with a nearly full hard drive, a TSeng 4000
|> Graphics Card, and SETUP just sailed right through it all.  So, my
|> guess is: Stacker or 386MAX is the culprit.
|> 
P.P.S.  My 3.1 upgrade installed A-OK, and I am running MSDOS 5.0, QEMM386,
stacker, tons of TSR's, with a hard drive that would be full if not for
stacker, and a farenheit video card.  No problems. 

Try executing win /3 to see if you car force it to Enhanced mode.  I have
sometimes had problems without the /3 because QEMM memory didn't look 
right to windows to let it know it could go into Enhanced mode.  After
that, everything was OK.  The problem eventually went away, and I don't know
how.  This problem (feature?) may also exist with 386 max.
Technical Details
Message-ID: <ku42fqINNns9@spim.mips.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!mips!mips!gelato.mips.com!mpolen
References: <9204062351.AA27629@ucbvax.Berkeley.EDU> <1992Apr7.051927.21779@cco.caltech.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!mips!mips!gelato.mips.com!mpolen
From: mpolen@gelato.mips.com (Michael Polen)
Newsgroups: comp.windows.ms
Subject: Re: HELP: Windows 3.1
Date: 7 Apr 1992 20:45:46 GMT
Organization: MIPS Computer Systems, Inc.
Lines: 40
Distribution: world
Message-ID: <ku42fqINNns9@spim.mips.com>
References: <9204062351.AA27629@ucbvax.Berkeley.EDU> <1992Apr7.051927.21779@cco.caltech.edu>
NNTP-Posting-Host: gelato.mips.com