[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

2670.0. "Install HUBwatch ONLY & can't find strtndis?" by TENNIS::KAM (Kam USDS (714)261-4133 (DTN 535) IVO) Wed Aug 23 1995 19:36

    We already have PWV5.x working and loaded HUBwatch V2.0, they layered
    3.1 ove that.  During the installation it asked if you want to install
    the Network and HUBwatch, just HUBwatch, etc.  We choose to just
    install HUBwatch as we already got a network running.
    
    In the installation manual it indicates to start HUBwatch run:
    	c:\whatever\ipstack\strtndis
    
    After completion of the installation we noticed that there isn't a
    directory or this file anywhere.  We are able to start HUBwatch in
    Windows and we thought able to configure the DEChub 90.  It appears to
    be working.
    
    Our system is a DECstation 320sx, 4MB memory, Digital ISA WaveLAN
    Wireless adapter.
    
    Also, every time we start HUBwatch the agent dialog box appears.  It
    requires the DECagent 90's name and address.  It is correct?  I felt it
    a bit much to have to remember the mac address every time I want to use
    HUBwatch.
    
    	Regards,
    
    	 kam
    
    
T.RTitleUserPersonal
Name
DateLines
2670.1disregard STRTNDIS; check min. h/w reqNETCAD::WAGNERCOFFILThu Aug 24 1995 11:1434
    
>>    In the installation manual it indicates to start HUBwatch run:
>>    	c:\whatever\ipstack\strtndis
I do not know what version of the installation manual you have, but the
current version clearly indicates to execute the above command 
ONLY IF YOU DO NOT HAVE A TCP/IP NETWORK.
In your case you have a network therefore disregard this statement.

>>    After completion of the installation we noticed that there isn't a
>>    directory or this file anywhere.  
Since you did not install the network, you do not have this file to start
the network.
    
>>    Our system is a DECstation 320sx, 4MB memory, Digital ISA WaveLAN
>>    Wireless adapter.
HUBwatch 3.1 REQUIRES AS A MINIMUM 386 PROCESSOR AT 33 MEGAHERTZ AND 8 
MEGABYTES OF RAM. You may be OK since you are managing a DECagent 90 which
does not require a lot of memory. Beware!
    
>>    Also, every time we start HUBwatch the agent dialog box appears.  It
>>    requires the DECagent 90's name and address.  It is correct?  I felt it
>>    a bit much to have to remember the mac address every time I want to use
>>    HUBwatch.
You should not have to enter the MAC address. The IP address or if set up 
correctly in the Community Table, just the name.    
This has been totally modified in V4.0.1, the agents you request are 
remembered from session to session. 

You are running old software on a system that does not meet the minimum
requirements!

Barb

2670.2TENNIS::KAMKam WWSE 714/261.4133 DTN/535.4133 IVOThu Aug 24 1995 13:3020
    Thanks for the update.
    
    We have SSB V2.0 media and doc.  We loaded that then we got the 3.1 kit 
    from the net and update.  Therefore, we're still using the 2.0 doc set.
    We order the latest 4.x, hopefully that will arrive in 7-10 days and we
    can be in the ballpark.
    
    Regarding my system - you got to make do.  It appears to run OK.  The
    PAINTs are slow but we can at least use the features and capabilities
    of the applications.  We have Business Partners that stop by from time
    to time and I'd rather have something showing rather than nothing. 
    We're trying to get something better.
    
    The prompt always goes to the Agent Name and yes just providing that
    worked.  We should have noticed that as soon as you start entering the
    Agent Name the OK button becomes active.
    
    	Regards,
    
    	 kam
2670.3A tipCGOOA::PITULEYDIGITAL=DEC: ReClaim TheNameThu Aug 24 1995 17:084
    Re:  Request for agent name when starting Hubwatch
    
    Please see note 2034.0