[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

2613.0. "Cannot executed hubwatch 3.1 " by ZPOVC::YICKPENG () Fri Aug 04 1995 13:21

    Hi,
    
    I was configuring hubwatch 3.1 for windows to a
    DECHUB 900MS.Installation is successful without error.I can even ping
    to other hosts but when I clip the hubwatch icon,the mouse pointer will
    change to a hour glass and then back to a to the mouse pointer again
    but no menu appear for me to proceed further.
    
    The ethernet card I am using is a 3COM509 etherlink III.
    The Dechub 900MS firmware version is 2.1.Hub manager for dechub 900 is
    configured for it IP address and slot.
    
    My question is do I need to upgrade the DECHUB 900 firmware to 3.1
    before I can use hubwatch or is there any thing that I might have left
    out.
    
    I had tried the ethernet driver provided by hubwatch and 3COM vendor
    but still the same.

T.R	Title	User	Personal Name	Date	Lines
2613.1	should work	PRSSOS::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Mon Aug 07 1995 07:59`	5
	do you check if the path for Hubwatch is correctly defined ? i think , it should work with the V2.1 of MAM, but an upgrade to the last version (4.0) will be the best.
2613.2	Stone Age!	TOOK::MILLBRANDT	answer mam	`Mon Aug 07 1995 15:28`	9
	Many many new features and fixes have been made since MAM V2.1. Why not start on the right foot? The latest MAM version is V4.0.2 (which is identical to V4.0.0 except for a diagnostic used for manufacturing). See note 2.0 for all the latest versions, and watch out for the OpenVMS caveat in note 2.1. Dotsie
2613.3	Problem solved Thankyou	ZPOVC::YICKPENG		`Tue Aug 08 1995 04:52`	6
	Thank you for responding to my query,I had found out that the problem was caused by Windows for Workgroup 3.11 is installed on the PC instead of Windows 3.1. SYP
2613.4	HUBwatch runs in WFW and Windows	NETCAD::WAGNERCOFFIL		`Tue Aug 08 1995 13:24`	2
	HUBwatch runs in both Windows 3.1 and Windows for Workgroups 3.11. Barb