| 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 |
My customer (a VAR) is having difficulty setting up a 3C509 card to work
with Hubwatch for windows V2.
He is installing using the Etherworks III option but is having no luck
getting the startnet.bat to recognize the card.
From my previous dealings with NDIS drivers it has been customary to
mess about with the protocol.ini to change IRQ's etc. This has been
done but there is still no joy.
Has anybody had any luck with 3C509 and if so could they supply details
of the setup.
Regards
Neal
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 674.1 | solution | QUIVER::ORSHAW | Mon Jan 31 1994 21:02 | 25 | |
I'm not sure what a 3c509 card is (3com perhaps?) but if it's not an
etherworks III card, then choosing the etherworks III option won't
work.
Here's a workaround:
The maker of the 3c509 card should provide you with an ndis driver and
protocol.ini. If you've played with changing interrupts or other things
like that, you'll have to make the proper changes in the protocol.ini
yourself.
Since you've already chosen the etherworks III card, I'll use that as
an example. Edit the startnet.bat file. REM out the line that says
"ld ewrk3.dos". In it's place, put in the proper ndis driver for your
card. For example, if you have an ndis driver called foo.dos, REM out
the line that says "ld ewrk3.dos" and add a line that says
"ld foo.dos".
Copy the ndis driver and protocol.ini to your \hubwatch\ipstack
directory.
Reboot (just to be safe) and try again.
Jim
| |||||
| 674.2 | exit | BIS5::RUTTENS | Tue Feb 01 1994 07:48 | 14 | |
I tried the same thing for a XIRCOM III adapter and it doesn't work
neither. (the HUBwatch included driver is for XIRCOM II and does not
recognise the XIRCOM III)
I followed the procedure as described in previous answer. Startnet
seems to be ok (no error messages on the screen).
When I try to access a dechub900 I get a "agent is not responding"
message. I also tried to ping some ip-nodes without any luck.
I also would like to try the XIRCOM PC/MCIA NIC. If you know how to do
it let me know.
rgds pr
| |||||
| 674.3 | error using 3c509 controller | CSC32::RA_HALL | Thu Apr 21 1994 15:50 | 24 | |
Customer is getting the following error during boot after installing
Hubwatch for windows V2.0.
MS DOS Lan Manager Protocol Manager v2.0
PRO0004: A parameter does not belong to any logical module
LD0014: Driver failed to initialize
Pathworks Device Driver Loader (LD) Version 5.0.008
then
Loading: ELNK3.DOS
3Com DOS Etherlink III Network Driver v2.0
ERROR: Unable to access Protocol Manager.
ERROR: Initialization failure
If I am not mistaken the first error is from STRTNDIS.BAT the following
line.
ld protman.dos /i:C:\HUBWATCH\IPSTACK.
My first concern is what is the /i parameter, I cannot find it.
He is using a 3c509 3Com Etherlink III adapter.
Ray
| |||||