Invalid File Handles (AREV Specific)
At 18 MAR 1999 12:08:16AM Tony LIllyman wrote:
Can anybody help ???
I have a client running:
Novell 3.12, NLM 1.10, mostly Win95/98 Workstations, Token Ring
AREV 2.12, 15 User
BUT on one workstation running DOS6.22 and Windows 3.11, when the
user starts AREV through Windows (either from DOS Prompts PIF or normal PIF, get message "Invalid File Handles" and then AREV
crashes out.
Checked CONFIG.SYS has Files=200
Checked NET.CFG has Files=200
Checked SYSTEM.INI has PerVMFiles=200
so it shouldn't be from a lack of file handles.
Only started to happen recently.
LHIPXTSR is loaded on logging into the LAN before loading Local
Windows 3.11. I'm NOT sure from where. Should be AREV directory
but will check now.
Any ideas??
Thanks
Tony
At 18 MAR 1999 01:44AM Steve Smith wrote:
Tony,
Try reducing the number of file handles
a little. DOS has 255 max. You specify 200,
leaving only 55 for the network redirector (NET.CFG)
to assign. Try juggling these numbers a little.
Steve
At 18 MAR 1999 05:32PM Tony Lillyman wrote:
Steve,
It was set at 30 when the trouble started to appear (out of nowhere I might add)
Would adding protocols to the other Win95/98 machines (name NETBEUI) have any impact on this Win 3.1 ODI machine. (I'm clutching at straws here)
Thanks for your thoughts
Tony
At 18 MAR 1999 08:59PM Jonathan Bird wrote:
Is the message a DOS or Arev message? If Arev, then you may not have a problem related to the CONFIG.SYS, but it could be an AREV file handle screwed up. Any MFSs installed?
J
At 19 MAR 1999 01:54AM Tony Lillyman wrote:
Hi JB
Long time no chat
Re Problem
When logging into AREV gets splash screen then
Invalid File Handles
Best as I can ascertain it is a DOS message
If they DONT log into AREV thru Windows (ie go direct from DOS)
No problems !!
I'm going there on Monday so I'll know more then
and can troubleshoot it more effectively.
I've been trying to troubleshoot long distance, they are over
an hour away across the city.
I'll report on the cause for posterity's sake.
Tony
At 22 MAR 1999 07:00AM Tony Lillyman wrote:
Turns out the problem was in fact a Novell Rights issue.
Apparently, (and I didn't waste too much time identifying the cause)
as part of my Licence Controls I extract some information about the Hard Drive / DOS Version and pipe it to a file (normally on the \AREV Drive). Turns out when this user tried to create the piped file, the OS issued an "Invalid Handle" error message?
When I set the destination for creating the piped file to the local hard drive, the problems dissapeared.
Any ideas why ??
Thanks
Tony