[comp.windows.ms] Help -- Windows 3.0 with 3Com Network

dmatlock@eecs.cs.pdx.edu (Delbert Matlock) (01/09/91)

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

ed@odi.com (Ed Schwalenberg) (01/09/91)

In article <1089@pdxgate.UUCP> dmatlock@eecs.cs.pdx.edu (Delbert Matlock) writes:
  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.

QEMM is a (more featureful) replacement for HIMEM.SYS, which Windows uses
to allocate the memory it manages.  It's perfectly reasonable to use QEMM
5.11 or greater with Windows 3.0, provide they're properly configured.
It's possible that QEMM tickles a bug that HIMEM.SYS would not, so it might
be worthwhile to experiment with using HIMEM instead of QEMM.

tporczyk@na.excelan.com (Tony Porczyk) (01/10/91)

In article <1089@pdxgate.UUCP> dmatlock@eecs.cs.pdx.edu (Delbert Matlock) writes:
>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.

I beg to differ. Windows depends on HIMEM.SYS for access to extended memory.
QEMM 5.1 handles all those functions very nicely, PLUS it loads my TSR's into
high memory (okay, so at least some of them). To Windows it makes no difference
whether you use QEMM 5.1 or HIMEM.SYS (I haven't tried both of them at the
same time).

Tony
--Std.Disclaimer--