mw@beach.cis.ufl.edu (Michael Wohlgemuth) (11/20/89)
I have been having tremendous problems getting the BYU packet drivers to work
on Zenith XT's (Z-151,Z-158,Z-159). We have a roughly equal mix of 3Com 3C503
and Western Digital WD8003E ethernet boards in the machines.
Here's a summary of the problem:
1. In most of the machines, only one of the ethernet boards will work. This
isn't too big a problem, only disconcerting. It would be nice to put a
board in a machine with a fair degree of certainty that it would work.
Also, the conflict seems only to occur when using the packet driver.
But, the code for the two boards is almost identical, so I have no idea
where the conflict is occuring. And besides, the conflicts don't happen
consistently with either board, only on certain machines.
2. Well, after we get a working board in the machine (working in the sense
that the Novell software runs most of the time) strange things begin to
happen. Most confilcts seem to occur between the packet drivers and
drivers loaded in config.sys.
For example, we have a Z-151 with a 3c503 board and an Exerex EV165A
Maxi Magic expanded memory board. When you turn on the machine, the
first time that you try to load the packet driver, the system hangs.
Hit ctrl-alt-del, and the packet driver will load fine, and continue
to load fine no matter how many times you warm boot. Turn the machine
off, however, and the system will hang the next time you try to load
the packet driver.
On another machine (a Z-159 with Zenith expanded memory and a WD8003E),
the first time after turning on the machine, the networking software
loads fine, but when you try to use the expanded memory, the system
hangs. Hit ctrl-alt-del to reboot, and EMM.SYS will no longer be able
to find the expanded memory board, but the network software will run
fine. I used mapmem from TurboPower Software before and after the warm
boot and this is what it looked like:
After cold boot:
owner hooked vectors
--------- ------------------------------
config
command 22 2E F3 F5 F7
N/A 0B 60 <--This is the packet driver
IPX 2F 64 7A
NET3 10 17 1B 20 21 24 27 FB
After warm boot:
owner hooked vectors
---------- -------------------------------
config
command 22 2E
N/A 0B 60 F3 F5
IPX 2F 64 7A F7
NET3 10 17 1B 20 21 24 27 FB
Has anyone else had similar problems, or does anyone have any idea what
might be causing this? Any help would be greatly appreciated.
Mike Wohlgemuth