Installing Using the Above configuration -

Workstation :

1) Windows 98 Client

2) Netware Client 2.7

3) Config.sys - included files=155

Server :

1) Novell 5

2) NLM 5

3) AREV 2.1 - Revelation Files marked RW Shareable

I run LHIPXTSR then Arev, got the message

Unable to open boot media map.

right away. So I unloaded the NLM and start AREV, no problem this time.

BTW before I change the Frame Type, I get FS472, so I changed the setting accordingly. Now no more FS472, but Arev won't start either.

Anyone experiencing same problem.

Richard

Just checking. Are you running the IPX driver from within Arev (change with AREV BUMP in 2.x)

Tony

What happens if you try the 3.1 client?

Steve (thinking out aloud)

Do you have a REVPARAM file which says Serveronly=1? Make sure this file exists in all directories containing the Linear Hash files.

Does this problem only take place on WIN 98 machines?

Try to re-do the AREV BUMP process/procedure for selecting/running the IPX/SPX Advanced Netware Driver.

Thanks for your response.

I did setup the revparam file according to the manual.

ServerOnly=True

However I didn't seem to work, so I removed it. I thought RevParam is only used to control access to rev files.

I also changed the Driver to Advance IPX/SPX Drv 2.1 using Arev Bump.

Richard,

I've never encountered Novell's Client32 v.2.7. I'd suggest upgrading to v.3.10, which has been tested successfully with the 5.0 NLM's, ARev and Win98. I'd also suggest stacking IPX at the top of your Protocol Preferences (within your Control Panel's Network -] Novell client settings).

-Stephen

Richard–

There is one more detail as well.  If you are going to stick with the 2.7 version of Client 32 in the Properties of the AREV shorcut set the XMS to None.

Rob

Revelation

Using token ring by any chance?

akaplan@sprezzatura.com

Sprezzatura Group

I upgraded to Netware Client32 3.1, but the problem remains the same.

unable to open boot media map

I tried the following steps :

1) move IPX to the top of the Protocol Preference

2) remove IP from the Protocol Reference

3) Set XMS to none, in fact I switched around different memory settings.

4) removing and creating REVPARAM

5) restored old copy of Arev and reInstalled NLM Client

6) Frame Type :

IPX Binding Ethernet 802.2

IP Binding Ethernet II

I set IPX/SPX FrameType to Ethernet 802.2, enable and disable NETBIOS on IPX/SPX.

Nothing worked.

However as I was trying different configurations ( I cant remember the exact sequence of commands I used), I got AREV to work with the NLM ( I checked with NLM_STATS ). So I closed the DOS session and rebooted.

When I restarted, AREV stopped working again !!!

I tried to follow through the prior commands I used, AREV just doesn't work. The commands used are doskey, lhipxtsr, flag, xcopy, purge.

Any Suggestions ?

Actually the problems seems to be caused by drive mapping.

As long as I map the server drive in dos I can access Arev NLM and if

I do not unmap the drive before returning to windows, the next time round I can't access arev NLM although I can still see the drive.

So I used a batch file that essentially

map k:= FS/SYS:APPLICAT

k:

cd arev21

lhipxtsr

arev

lhipxtsr /u

map del k:

Everything seems to be working now.

I changed the IPX Driver using Arev Bump

Yes I am having similar problems and I have tried all of suggestions here with no luck. The only way I can get AREV to run is to use an old Client32 2.2. I have changed frame types, upgraded to NLM 5, map the drive through DOS but nothing is working. If anyone has any other suggestions I would appreciate them.

Phil,

My working configuration is as follows :-

Client : win98, NW Client 3.1

Server : Novell 5, NLM 5, Arev 2.1

Yes that is the same configuration that I am using and I have checked the frame types, checked the primary board unchecked the primary board but nothing seems to help except running the old client.

Phil,

It seems we have the same basic configuration. Maybe it will help if I mention the other configurations :-

Network Configuration

IPX 32 bit for netware client32 - set frametype

IPX/SPX compatible protocol - set frametype

enabled NetBios over IPX/SPX 

set to default protocol

Netware client32

protocol preference - set IPX first

DOS box setting :

memory setting all auto, except XMS set to NONE

Arev directory structure

f:\applicat\arev

since I can't use the default network drive. I have to map in DOS

map k: FS\SYS:\applicat

k:

cd arev

lhipxtsr

arev

This is all I did and it worked and apparently the speed is quite impressive, a traffic intensive process takes 4 minutes instead of 30 minutes (pre NLM version).

BTW what error message did you get.

Thank you for those settings.

I had set the frame types and netware protocal preference

I had not enabled NetBios nor set it to my default protocol.

And I had not turned off XMS

After I made those changes it now works. Thanks

The error message I was getting was:

Linear hash IPX Driver

Revmedia open error: FS472

Unable to open boot media map

Thank you for your help

View this thread on the forum...