Client migrated from Netware 3.12 to 4.11 w/NLM. Platform is Win95 OSR2 w/Novell Client32 Shell. The problem is wierd:
Start AREV from desktop w/batch file:
LHIPXTSR/P
AREV ACCTNAME /M4096X
LHIPXTSR/U
The first time the app is loaded all is hunky-dory
Subsequent starts
At bottom of screen a Novell Error:
This device does not exist on the network. reading device
Abort Retry Fail
Any selection other than A entered twice keeps the message on the screen. The app will then start fine without errors. The problem is that the screen is corrputed with the DOS/Novell error.
Has anyone else seen this?
Don Miller
C3 Inc.
Don,
I've seen this once before and in that particular case it was map-rooting issue. Try mapping one directory up or, if that's not possible, move the ARev application directory one below the root. It's worth a shot.
Regards,
Stephen Revelation
Don,
I've also seen this related to sharing on LPT1 or PRN when ARev tries to open up the locked printer port.
akaplan@sprezzatura.com
Aaron,
Yup!! The el-crappo Win95 printer redirection struck again. The physical printer port hadn't been captured so it was printing to a device-less thingie. Even wierder, if you do a SUSPEND EXIT CAPTURE /ENDCAP ] NUL, you sometimes get a funky R6009 message (Not enuf room for environment caca, but it works anyway).
Don