I am running AREV 2.12, NLM 1.5 on a Novell 4.11 network. On one particular workstation running Windows 95 and Novell Client 3.10 when trying to initiate AREV the whole workstation locks up (can't even soft boot). This happens both when trying to initiate through a desktop shortcut, and when manually initiating in DOS. In DOS I can load the LHIPXTSR.exe (with the /p /r32 parameter), but when I enter the AREV command statement it throws up the blue screen "initialization process" window and completely locks up.

I've checked the Windows settings (Allow Screen saver - off, no write-behind caching, suspend mode - off, etc.) but everything is as it should be. I have this problem with NO other workstation.

This is a Gateway E series workstation. The only thing unique on our network about this workstation is that it is running ADP payroll SQL software, and is connected to an ADP Hand-punch time clock. Any suggestions? thanks

Sounds like a protocol problem. Check your IPX/SPX parameters for the IPX/SPX protocol. Make sure the frame type is correct for your server - 802.3 is the Netware 4.1x default. Specifically, disable the auto-detect frame option. Do you have multiple protocols loaded on this workstation (NETBUI, TCP/IP, etc)?

Don Miller

C3 Inc.

Don, thanks for your response. Unfortunately the protocol config. seems to be correct. Our server is running frame 802.2, as are all the workstations. I have no protocols loaded on that machine except the IPX/SPX protocols. I don't have the Frame Auto-Detect set either…it's set to 802.2.

First thing you want to do is install the ARev 2.12 patches. After that, chck on your EMS memory. Try running with the /O comand line option (that's a letter O, not the number 0) and see if that makes a difference.

[email protected]

Sprezzatura Group

View this thread on the forum...