Well, Here I am again with an old topic. One of my installations is again getting output from PDisked reports in tvarious LH files. It has been the LISTS file but TOday it was one of their major data files. This has been on ongoing problem that has plagued us for a number of years on DOS only single user machines, to DOS netware multi-user systems, to WIN3.1 Netware multi-user machines to now netware systems running Win95 clients.

Since it is happening across such a wide range of clients I have to conclude that it is either with NETWARE or wint in AREV. Some suggetions from the past post has been to increase FILES= in config.sys to changing $SETPTR. The most recent problems started last week after a month of quiet and is on a Netware 2.11 system running AREV 2.1 with Win95 client. I increased the cleint machines files from 100 to 190 but that has made no difference (maybeing even worse but that maybe my frustration talking). I thought all of my installations had the same $SETPTR routine since all are running AREV V2.1.

However, here is what I found:

SYSTEM NETWARE size(bytes) version (obtained by editing it)

———— ——- ———– ——————————-

developement 2.12 132 V1

PF " 177 19:14:09 22 Aug 1988 Arev1.1.8

CRS 2.11 178 16:18:37 23 Apr 1990 Arev2.0.25

AREV3.0 2.12 195 10:50:46 6 Aug 1991 Arev2.11.46

The system having problems is CRS. My gut feeling is V1 has been the most reliable but I do not run reports all the time and using that version runs counter to suggetions to upgrade to a newer version. For all of you experts, Other than 2.0.25, which version should I use. Are there any known problems with each of these versions?

For the moment I have set the CRS system to use the SetPtr from AREV3.0.

Thanks - ed

I apologize for the table in the original post not saving correctly.

ed

Ed,

I am rusty on this, but I feel you may need to

(a) increase the netware server buffers

(b) increase the files not in config.sys, but check

your Netware manual on how to do it via NET.CFG, as

the netware file handles operate independently to the

DOS ones.

© Use the VLM.exe version 1.20B or later on each

workstation.

(d) check that the CLIB.NLM and STREAMS.NLM is the

latest patch from Novell on the server.

Hope this helps,

Steve

The error occurs because of a confusion in the file handles. Part of the problem is in DOS and part of the problem is in the $SETPTR program. Starting with ARev 2.12, the ARev side of the problem was removed. You can copy the $SETPTR program from a later version in a pre 2.12 copy. This still leaves the DOS side to contend with.

Upping file handles depends on the system you're running on. If the output is going onto local files, you need to up the DOS FILES in CONFIG.SYS. If the output is going into network files, you need to up the FILE HANDLES statement in your NET.CFG.

apk@sprezzatura.com

Sprezzatura, Inc.

Thanks for your response. lets see if I have this correct:

1. I can use the $SETPTR from my AREV3.0 system. The module is

  dated-10:50:46 6 Aug 1991 Arev2.11.46   and

  is 195 bytes long.

2. If I am running DOS ONLY and using local drive for output set FILES=in config.sys higher say 100.

3. If I am using DOS ONLY and using the NETWARE drive for output then make sure FILES= in the NET.CFG is set higher say 100

4. If I am using WIN 3.1 then follow 2 and 3 above depending on the location of the output file.

5. If I am using WIN95 client for Netware then set FILES= int CONFIG.SYS high say 200 because WIN95 manages files for both local and network drives. (Someone said this was the case)

6. If I am using Novell CLIENT32 - do I do the same as WIN95?

thank you all

ed

1. I can use the $SETPTR from my AREV3.0 system. The module is dated-10:50:46 6 Aug 1991 Arev2.11.46 and is 195 bytes long.

Yes, and I'll take your word on the size and dates.

2. If I am running DOS ONLY and using local drive for output set FILES=in config.sys higher say 100. 3. If I am using DOS ONLY and using the NETWARE drive for output then make sure FILES= in the NET.CFG is set higher say 100 4. If I am using WIN 3.1 then follow 2 and 3 above depending on the location of the output file.

Personally, if Netware is active, even if ARev is running locally, I'd up the NET.CFG values anyway.

If you're running Netware under DOS (inc. Win 3.x) then the sum total of FILES and File Handles should be about 200 or so. No more than 210, no less than 180.

Start with them both about 100 and adjust as needed, moving from one to the other as your needs dictate. Higher local file use then take from NET.CFG, higher network file use, then take from CONFIG.SYS.

Remember, the NET.CFG value is File Handles not FILES.

5. If I am using WIN95 client for Netware then set FILES= int CONFIG.SYS high say 200 because WIN95 manages files for both local and network drives. (Someone said this was the case)

Yes, this is correct.

6. If I am using Novell CLIENT32 - do I do the same as WIN95?

If memory serves, there is an option for files in the Client32 somewhere. If so, follow the FILES and File Handles rule from 2-4. If not, follow 5.

apk@sprezzatura.com

Sprezzatura, Inc.

Thanks a lot fot he help. Hopefully, this will SQUISH that pesky bug

once and for all!!!

ed

View this thread on the forum...