i am having problems with a client running

arev 2.1 & revelation nlm in a windows 95 nt environment. i am not sure if there is a configuration setup problem but response times are very slow especially when filecopy or displaying windows. any help or suggestions on (1) how can i really tell if everything is setup properly, (2) any suggestions to make things run smoother would greatly be appreciated. unfortunately i am not very familiar with the product and revelation doesn't seem very supportive of its older releases. thanks.

here is a section of the tcl who :

release version =2.1

account name=sysprog

math processor=80387

available memory=227148

descriptions used=1733

expanded memory=active

network information

vendor/type=all networks drv. 1.1.1.0

maximmum users=20

expanded memory info

em used=338,994

em allocated=8,338,608

memory region

16k em window=3000 (192k)

64k overflow buffer 1=d400 (848k)

64k overflow buffer 2=3400 (208k)

J,

What version of the NLM are you using. What is the

Novell server version, and when you said Win 95 NT

Does that mean that these are the two types of workstations

that you are using.

          The network driver that should be used for 

the NLM is the IPX/Advanced Netware driver. You should not

be using the NPP(All Networks Driver)if you are running

the Revelation NLM. This could be a major problem.

With a little more information we should be able to get you

running smoothly.

1. DaveRevelation

dave,

i am running in a windows 95 nt environment only - no novell network. it is running with the nlm or network performance pack or whatever was told that we needed to install. if there is a simple way to check what is running i don't know how to get to it to give momre info.

John,

   First of the NLM is for use with a Novell 

Network only. It sounds like you are running with

an NT server and windows95 workstations.

   Some things you can do is load AREV with these

Command line switches /x /m4096. This will decrease the

amount of EMS allocated to 4096. This is the recommended

settings for AREV.

   Also check to see what network protocols you are 

using. If you are using ipx/spx see if you can get

away without it using. You can check this by checking the

network properties. The best on to use would be TCP/IP.

   Also how many users do you have using AREV? You

may want to consider getting the NT Service.

1. DaveRevelation

I have seen NT running slowly with AREV 3.12 and without use of the NT Service (most of our users could not afford to even think about buying it). I think that the reason came down to a lack of locks allowed for a workstation or a lack of files e.g. can only have 20 files open when you need 100. In the latter case I think that they have to be juggled making the system very slow.

I am sorry not to be more specific than this, but I do know that several customers have overcome the problems like this.

DAVE,

THE CLIENT THAT WE HAVE HAS PURCHASED THE NETWORK PERFORMANCE UPGRADE – WE HAD INSTALLED THE SYSTEM AND THEN THEY HAD A USER BUMP UP TO 20 USERS. HOW DO I KNOW IF THE NETWORK PERFORMANCE THING IS WORKING, IS THERE SOME SORT OF TCL COMMAND TO SHOW WHAT IS HAPPENING? WE ARE USING THE AREV 2.1 VERSION. THANKS .

John

My understanding is that the network performance pack just implements a form of locking that works properly on non-Novell platforms (and I believe I am right in saying should also prevent GFEs due to Win95 cacheing). The instances I have of slow operation on NT did not use this, they were only using the old MSDOS 3.1+ driver. The only way I know of checking for the network performance pack is to see if the Revlocks file is getting used by workstations (should be able to see this with the NT Server Control Panel).

Dave, if you are saying the NPP prevents GFEs then somehow the NPP is not working since they had gotten a GFE earlier this week. I don't know what to do to turn the NPP on/off on the server. Do you use an AREV /something?

John, the NPP is just an alternative to the other network drivers available. The method of turning it off (assuming that you are not using the NT service as well) is to run AREV BUMP and change to a different driver e.g. MSDOS 3.1 plus. However, that driver does not support Coordinated locking (if my memory serves me correctly). The NPP will not necessarily prevent GFEs it is just suppose to prevent one guaranteed method of getting GFEs in Windows 95 where files get cached locally when they should not according to the way that they are opened. If you get a crash then a GFE may result, also all the other usual methods of getting GFEs may still apply.

Working or loaded? To tell if it is loaded, use the GETCONFIGURE function. See Using GETCONFIGURE for information on determining system configuration.

To tell if locking is working, try and edit the same record on 2 workstations.

I'm not sure what else you're looking for in a response.

apk@sprezzatura.com

Sprezzatura Ltd

View this thread on the forum...