I've been looking through the mounds of threads on the the old boot media map error stuff. I've tried many of the suggestions, but I still have a problem.

The setup is as such

Novell 5.0 Service Pack 6a (had the same problem with 2a)

NLM 1.5a (yes Ver 5.0)

Windows 98

Arev 3.12

"Unable to open boot media map" (No FS Numbers)

If we use an old client32 (I think it is 2.2, but there is no number on the properties), we can successfully log into Arev.

If we use Client32 3.1.0.0 we get the boot media map error

If we use Client32 3.30.0.0 we get the boot media map error

We "HAVE" to use Client32 3.1 or greater as the user need to utilise PC Anywhere which falls over with the earlier client32.

I've checked the frame so it just sits on 802.2

I've tried re-loading the NLM in case it was corrupt

Is there a specific Client32 that works with this combination, oh yes we also have a Windows 2000 PC with the latest client32 which works ok (a bit slow, but I'll have some fine tuning to do on that yet)

I've put this one off for months but it eventually creeps up on you.

Is there a difinitive matrix (or even AMV) that says :

if you are using Novell XXX then you need client XXX with NLM XXX

You need to set X to Y etc.

The threads throughtout this forum a scattered with various ideas but it is a bit of a junble.

Any help greatly appreciated

Regards

Claude

Claude,

The official support matrix is found here. However, my favorite Matrix is found here.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

C,

The rule of thumb for Novell clients as of 05/18/01 is as follows:

For: Use:

Win95 Client 3.3

Win98 Client 3.3

WinME Client 3.3

WinNT Client 4.8

Win2000 Client 4.8

They will work with both Arev and OpenInsight, and On Netware 4.x and 5.x (do a search on 'Connectivity' to find the specific SP's that have trouble).

The rule of thumb for the Revelation NLM is:

Revelation NLM 5.0 is for Netware 5.x

Revelation NLM 1.5 is for Netware 4.x and 3.x

I have seen situations where the MS client will connect to a Netware server and allow the NLM to run fine, but this is the exception more than the rule. The 3.3 should work, but there may be a setting that is off.

Have checked through the NLM follow up tips and knowledgebase articles? They contain information that should point you in the right direction.

Be sure to check that you have the IPX protocol stacked higher than TCP/IP.

Be sure that IPX is the preferred protocol over IP.

Hope this helps,

Kevin

Don-

An OpenInsight Powered Matrix is Here.

Mike

Kevin,

We have tried your suggestions. In fact we went further and removed all Microsoft Network and TCP/IP protocols.

We set IPX as the first load

We have it on a frame of 802.2

I am assuming something subtle has to be adjusted, but exactly what it is - I just don't know.

Same error

Please throw ideas in this direction

Claude

Claude,

  Can we isolate your problem to a single Workstation or are we talking about all your 98 Workstations? If it only one machine, then I would switch out the NIC and the patch cable to see if the changes make a difference. Also, check and see if you can connect through a DOS prompt. Manually load the TSR (don't forget the /p switch-it is neccesary with Win98) and then the arev executable. Your expanded memory is enabled? Make sure. 

Still no go? Try loading the TSR with the /r switch bumped up to 30 or higher.

If no connections yet, reinstall the Novell client but do the custom install and choose where IPX is all you have installed (or at least preferred over IP).

At this point if you get no joy, try loading the MS client for Netware. See if it has any luck connecting. If you don't, or even if you do (which would be more frustrating because you don't want it), email me at Kevin@revelation.com. Then we get down to the nitty gritty.

Kevin

View this thread on the forum...