Path: utzoo!mnetor!tmsoft!masnet!canremote!claude.vidal
From: claude.vidal@canremote.uucp (CLAUDE VIDAL)
Newsgroups: comp.windows.ms
Subject: Re: Windows 386 Problems
Message-ID: <89120107514887@masnet.uucp>
Date: 27 Nov 89 13:49:00 GMT
Organization: Canada Remote Systems Limited, Mississauga, ON, Canada
Lines: 32

//]I'm having a problem with Windows 386.  I have a
//]new machine, Club American 333C (AMI Bios) with
//]a Sigma Laserview 19" monitor and an MSC PC Mouse II.
//]
//]I'm configured the right way, I think.  The behavior
//]is this.  I get in directory WIN386.  I start the
//]thing by typing WIN386.  The cursor goes down one
//]line, about a half second passes, and the screen
//]in cleared and I'm back at the DOS prompt (not very
//]useful, eh?).

Can't give you that bottom line answer, but at least some
thoughts...

I believe  the first  thing WIN386.EXE  does is  have its LIM EMS
manager  do   its  thing   (assessing  how   many  K's   of  EMS,
initializing, setting vectors, etc.); all this occurs before  you
even see the (blue) title screen.  So chances are you're  bombing
out during that process; the  286 version doesn't have that  'EMS
manager' front end, as far as I know, which would explain how  it
runs on your system.

Suggest you check for EMS drivers in your config.sys: Windows  is
not  sociable  with  other  EMS  managers.   I presume you're not
running under another protected mode piece of software.

How  did  you  respond  to  the  memory configuration part during
Windows/386 installation?
---
 ~ EZ-Reader 1.21 ~ Windows/386...faut l'faire!

 * QNet 1.04a1: DAT-A-REA - St-Bruno,Quebec (514)441-3229