Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uwm.edu!ogicse!pdxgate!eecs!dmatlock
From: dmatlock@eecs.cs.pdx.edu (Delbert Matlock)
Newsgroups: comp.windows.ms
Subject: Re: Help -- Windows 3.0 with 3Com Network
Message-ID: <1089@pdxgate.UUCP>
Date: 9 Jan 91 01:02:54 GMT
References: <1991Jan8.214624.15389@msuinfo.cl.msu.edu>
Sender: news@pdxgate.UUCP
Distribution: usa
Lines: 31

ramchan@buster.cps.msu.edu (J. Sunil Ramchandani) writes:


>VGA Card .  I also have 3COM Ver1.1 installed along with QEMM 5.1.

I thought QEMM was a memory manager?  If it is, remove it.  Windows likes
to do all of it's own memory management.

>Ennced mode : I cacan not use any facility of the network, and also the 
>	response of the system goes down to zero.  Although while using 
>	network system just hangs up.

Somebody recently stated, "LAN Manager 1.1 predates Windows 3.0".  This  
causes all sorts of problems with network access.  Make sure that you log
in before you start Windows.  This is a good way to lock up the system.  Next,
make sure Windows knows that it is talking to a LAN Manager 1.1 network.  This
way it can do linking from within the file manager.

For some reason, Windows is very slow when accessing the network under LM 1.1.
I haven't played with LM 2.0 enough yet to know if they have solved this
problem.  I think it may have something to do with local cache being faster
than network cache.

One thing I wouldn't mind seeing is some network support in the Windows PIF
files.  It would be nice to have Windows establish and remove network links as
needed by a program.

=============================================================================
Delbert Matlock                         Internet:  dmatlock@eecs.cs.pdx.edu
MicroNet Northwest                      
Voice:  (503)228-3071