[comp.windows.ms] win30-enhanced, ipx, 3c501 performance...

sparkie@picard.cs.wisc.edu (Mark J. Horn) (12/18/90)

Greetings,

This is a proxy post for a co-worker.

============================ Begin Included Message ============================

I've been having problems getting Windows 3.0 to operate on an ethernet based
Novell Netware 3.11 PC LAN.  My PC is a Wang 380 with 512K VGA, 3.5MB memory
(.5 MB used to backfill the motherboard from 512K to 640K), a serial/parallel
port card, something called a Wang Local Office Communications card, 60MB hard
drive, both 1.2M and 720K floppys, coprocessor, and 3c501 ethernet card.

The symptoms: I can bring up windows in real or standard mode after loading the
IPX and NET3 (versions 3.01) and access the LAN.  Accessing network drives is
comparable to accessing my local drive.  However Windows sometimes hangs when
brought up in enhanced mode.  When it does come up, attempts to access a
network drive usually result in the message, "SYSTEM ERROR: CANNOT READ FROM
DEVICE NETWORK".  Occasionally, accessing a network drive will work but it will
take several minutes to display a drive with only five directories and a couple
of files.

I have checked my versions of IPX and NET3 via the 'I' parameter: they are both
version 3.01.  I have run the update utility supplied with the Novell 3.11
upgrade kit against my Windows directory with no effect (no doubt because my
ethernet board is using IRQ 7 rather than 2 or 9).  I have tried excluding
the memory used by the card (base address EC00) via the 'EMMExclude' statement
in the system.ini file.  I have also played with other settings in the
system.ini file all to no avail!  Does anyone have any idea where I should go
with this?  Interestingly, the PS/2s around here aren't having any problems.

============================= End Included Message =============================

Here's some things to note about this question:  I have a PS/2 mod 70 running on
the same ethernet that he's on and my performance is nowhere near as poor as
his.  This rules out the possibility of an over-crowded ethernet.  Also note
that everything works fine if run in real mode.  It only occurs in 386 enhanced
mode.  This rules out the possibility that his card is the bottle-neck.

Because this post is not from me, any e-mail replies are best served by going
directly to him.  His address is:
	kevin.cherek@mail.admin.wisc.edu

As always, TIA,
- sparkie