[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
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

2955.0. ""Other" NICs and HUBwatch fail!" by CHEFS::BILLERSB () Sun Nov 05 1995 12:21

    Call me thick if you like but I cannot get HUBwatch (V4.1) to pick up
    the driver and protocol.ini from an "other" network adapter. I ahve
    followed all the instructions, tried various combinations and disk
    sources but to no avail. It just comes back every time with "cannot
    find driver/protocol.ini".
    
    There is nothing wrong with the card because I (no I.S. support)
    managed to get it working quite successfully with PW 4.1.
    
    I am not intending to run Hubwatch with PW so have started up my laptop
    without the network. Is that a problem?
    
    Please put me out of my pain.
    
    Bob
T.RTitleUserPersonal
Name		DateLines
2955.1You need a networkSLINK::HOODMy God, what have I done to my spleen?Mon Nov 06 1995 10:1318
>    Call me thick if you like but I cannot get HUBwatch (V4.1) to pick up

	OK.  Hi, Thick!   

>    I am not intending to run Hubwatch with PW so have started up my laptop
>    without the network. Is that a problem?

	If I read your message correctly, this is a problem.  You must have
	an SNMP stack.  HUBwatch 4.1 ships with one, but you can use pretty
	much any popular stack.

	(Disclaimer: Eladio sez I'm too sarcastic in the notesfile. My
	 first reply above is not sarcasm, nor a put-down.  It's just that
	 I can't resist a straight line.  And sometimes adding the ";-)"
	 is just too much work. ;-) )

	Tom Hood
	clearVISN ("the product formerly known as HUBwatch and then some")
2955.2enter location AND driver name separately; use TAB BNETCAD::WAGNERCOFFILMon Nov 06 1995 15:5946
>>    Call me thick if you like but I cannot get HUBwatch (V4.1) to pick up
>>    the driver and protocol.ini from an "other" network adapter. I ahve
>>    followed all the instructions, tried various combinations and disk
>>    sources but to no avail. It just comes back every time with "cannot
>>    find driver/protocol.ini".
I will provide an example.

Before I proceed... The "other" network card adapter selection has a horrible
user interface. Now with that said...

EXAMPLE:
--------
Select the 2nd Option "Install HUBwatch, ..., and network" (or if you have 
already installed HUBwatch, select the 3rd Option "Install and configure 
the network").

The installation copies the appropriate files to appropriate directories.

Enter the Network Configuration Parameters.

Select the NDIS network and Slip option in the Type of Network dialog.

Select the "Other" option in the Type of Network Card dialog.

In the Network Card Adapter Driver Info dialog enter the location AND the 
driver name(in a separate field):
A:\NDIS\DOS\    ** Driver location example **
**Select the TAB key ONLY!! Do NOT USE Carriage Return or Arrows! **
EWRK3.DOS       ** Driver name example **
Select the OK button.

Now follow the instructions in READ_ME.PS or .TXT to merge the installation
generated PROTOCOL.TMP and PROTOCOL.NIC to manually create a PROTOCOL.INI.

It works! It is horrible! 
You will not see it ever again in subsequent releases!
    
>>    I am not intending to run Hubwatch with PW so have started up my laptop
>>    without the network. Is that a problem?
Yes. As Tom indicated you must have a TCP/IP stack to run HUBwatch.
    
>>    Please put me out of my pain.
Sorry, the pain remains.

Barb