Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!bingvaxu!leah!uwmcsd1!dogie!uwvax!astroatc!nicmad!brown
From: brown@nicmad.UUCP (Mr. Video)
Newsgroups: comp.sys.ibm.pc
Subject: Re: problem with windows 2.0
Message-ID: <2292@nicmad.UUCP>
Date: 31 Dec 87 21:44:32 GMT
References: <285@sarin.UUCP>
Reply-To: brown@nicmad.UUCP (Mr. Video)
Distribution: na
Organization: Mr. Video's Hangout
Lines: 57
Keywords: windows 386 windows 2.0

In article <285@sarin.UUCP> eric@sarin.UUCP (Eric Beser K3UHF) writes:
<I am running windows 386 (or trying to) and have the following difficulty.
<
<First, let me state that I am using the Haupage 386 Motherboard with EGA+ and
<microsoft mouse. The version of windows that I am using was sold with the
<*clear* understanding that this version was not only for the compact but would
<work on IBM and Intel above board products. The salesman at Computerland was
<quite insistant that it would work, and besides, if it didn't, I would be
<able to return it. They neglected to tell me that If I opened the sealed
<envelope, I would not be able to return it.
<
<Now the problem with the software. When invoking windows by typing win86, it
<works. However I cannot get the non-windows applications to work since it 
<tells me that windows is not installed correctly. The manual says I have to
<invoke windows by typing win386. When I do that, the mouse responds nicely,
<but I get no response from the keyboard. I can invoke outside programs (by
<selecting them with the mouse) but no input from the keyboard. Under win86,
<both mouse and keyboard work fine.

First off, I have the Compaq386/16 and got the initial release of Windows386
as part of the package, Version 2.01.  Since you have the MS mouse, that 
version of Windows should work with the mouse ok, which is what you have
discovered.

The Win86 command is to bring up Windows 2.0, not Windows386.  Windows 2.0
wants the extended memory turned into EMS memory, so that Windows 2.0 will
have enough memory to do stuff.  On the other hand, Windows386 DOESN'T want
extended memory turned into EMS memory, as it uses it just as it is.
Windows 2.0 works on non-386 machines, while Windows386 takes advantage
of the 386 processor's virutal86 mode.  So, I suspect that the DOS application
wouldn't run under Win86 because there wasn't enough memory.  Since you have
the 386 processor, I suggest using the Win386 command.

But, that doesn't solve the problem of the keyboard not working.  On my
system the keyboard worked just fine.  Actually I had to use the keyboard
since there weren't any drivers for the Logitech mouse yet.  I would try
doing the set-up again and tell the configuration that there isn't a mouse
attached. See it if works without the mouse.  Be sure and not to autoboot
win386, because if it locks up, you will have to use a diskette to get the
system up again.

Because the software worked for me, I would suspect something wrong with
the BIOS interface to the keyboard.  Windows386 really takes that sucker
over, and if the BIOS isn't right, then it won't work.

I have seen the Windows386 version 2.03 pre-release, and it has the drivers
that I need for the Logitech mouse.  I hope that MS isn't gonna hit me up
for $86 to upgrade (even though I got it free).

The only other thing you can do is take the Windows386 software to a Compaq
computer and make sure that it works there.  If it does, then your 386 board
is indeed bad.
-- 
	       harvard-\	       ihnp4--\
Mr. Video               !uwvax.................!nicmad!brown
	       rutgers-/  terminus-/  decvax--/
"... a can of deodorant that measures nine on the Richter scale?"