Arrgh! "Unable to read SYSOBJ in media map" (Networking Products)
At 24 APR 2001 10:45:21PM Warren wrote:
Okay, I installed the NLM v1.5a on a Netware 3.2 server.
Added all the REVPARAM files, coded a watchdog program to check for the TSR and if the file handle showed the nlm working…etc.
Works fine the on Win98SE workstation with the Novell client32 v3.1.
So I go to the next 4 workstations (all with Win98SE) and remove the v3.3 Netware client32 and install v3.1. Station 2 & 3 work fine. When I get to station 4, ARev 3.12 craps out with "Unable to read SYSOBJ in media map". I reinstall client v3.1. No dice. I LHSTOP/LHSTART. No dice. Workstation 1 works but not 2 & 3. LHSTOP. Shut down all the workstations. LHSTART. Restart all the workstations. Now all of them crap out with "Unable to read SYSOBJ in media map". I check the frame type on the system monitor and force Win98 to that. Still no luck. I went home frustrated at that point.
Any ideas? Yeah I should have downed the server again but was too frustrated to do that.
At 26 APR 2001 12:03AM Warren wrote:
Okay, fooled around with this some more…
DOS workstation works fine, connects to the NLM, TSR confirmed loaded, file handle showing LH NLM is communicating.
Win98 workstation - I got it working briefly, then it would give me the error. I tried all the gimmicks with frame types, bindings, protocol preferences as documented in the KB articles and suggestions on this website with no measurable success. I reinstalled Novell Client 32 v3.10 and even tried v3.30.
Win98 Workstations have 3com or Intel ethernet cards. Nothing strange that I can see unless I'm missing something obvious.
At 01 MAY 2001 05:04PM Warren wrote:
Likes like it may have been a faulty or improperly installed NIC. Keeping my fingers (and eyes) crossed…