Path: utzoo!attcan!uunet!samsung!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!usc!apple!agate!linus!linus!mwunix.mitre.org!jcmorris
From: jcmorris@mwunix.mitre.org (Joe Morris)
Newsgroups: comp.windows.ms
Subject: Re: help - windows and disk manager problem ??
Message-ID: <121435@linus.mitre.org>
Date: 27 Sep 90 15:33:52 GMT
References: <12787@encore.Encore.COM> <26860@boulder.Colorado.EDU>
Sender: usenet@linus.mitre.org
Reply-To: jcmorris@mwunix.mitre.org (Joe Morris)
Organization: The Mitre Corporation
Lines: 24

In a recent article scholes@snoopy.Colorado.EDU (Marty Scholes) writes:
>
>On my machine (generic 386-20), Win3 locks up at the title screen if I
>try to run enhanced mode.  It runs standard and real just fine.  

One of our people here had that problem.  It turned out that the user had
just upgraded from a PS/2-50 to a -50 SX (i.e., '286 to '386) and had
copied over the entire fixed disk contents intact.  The solution was to
reload Windows.

In this case the Windows system runs on a Novell network (i.e., the user's
machine has only a few K of files) but I don't think that is significant.

Although I didn't follow up to verify the analysis it appears that if you
install Windows in a '286 environment the system.ini file doesn't get
set up properly.  In this case, for example, there was no program named
in the [boot] section of system.ini on the '386grabber' line.

Ah...would someone in Microsoft please ask the Windows development people
to check at Windows startup to verify that the minimum set of files exist
before committing the system to Windows?  (Assuming, of course, that this
really *is* the problem.)

Joe Morris