| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hi,
I have a customer out at Novell Super Labs in Provo who is
having some problems with HubWatch v3.1. Previously, he has
had HubWatch running over DEC's DEFEA adapters (EISA to FDDI
NICs), but he has switched PCs and now he's having problems.
He has a DEC XL466 with MS-DOS 6.21 and HubWatch will not
allow him to load the DEFEA driver. The message he says
appears on the screen is something like a line number followed
by an error that says HubWatch can't access source code for the
driver.
He has also tried to load HubWatch on machines with our new
DEFPA cards (PCI to FDDI adapters), and says that HubWatch
doesn't list the DEFPA card as an available option, and that
he can't get HubWatch to recognize the sources for the DEFPA
either. He has tried moving the driver sources from sub-directories
to a top level, but this doesn't seem to help.
HubWatch seems to give similar warning messages when it goes to load
the drivers for both adapters. The message being that it can't
access the source code.
Any ideas why HubWatch can't load the drivers? Or why it fails
to recognize the sources?
thanks,
-Brenda
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1943.1 | try sch /ndis in STRTNDIS.BAT | NETCAD::WAGNERCOFFIL | Fri Feb 03 1995 19:03 | 31 | |
Which IPSTACK is the customer using? It sounds like he is using
the stack with HUBwatch which is PATHWORKS for DOS and Windows
TCP/IP stack.
I am also assuming he using NDIS and not Novell's.
If this is also true, have him place /NDIS in the SCH statement
of the STRTNDIS.BAT in C:\HUBWATCH\IPSTACK directory.
i.e. SCH /NDIS
See below.
OTHERWISE, it seems like it could be an error in the PROTOCOL.INI
(for NDIS) or NET.CFG (for ODI). The information to load the
adapters come from these files.
Barb
***************************************************************************
================================================================================
Note 712.1 loading Pathworks over FDDI - DEFEA 1 of 8
JEDI::CAUDILL "Kelly - Net Tech Support - 226-6815" 8 lines 7-APR-1994 18:33
--------------------------------------------------------------------------------
Ahh... A little insight from the DEFEA driver guy... After saying
"noone has ever tested that" he said, "you need to use /N on SCH".
After installing PW to my hard disk - yuch! - I was able to configure
and start and use the DEFEA. And my my CFG file had the /ndis on SCH.
So, does the PW SETUP disk use /N on SCH? If not, maybe that explains
my problems??? Is there any way to change what the setup disk does?
| |||||