[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

257.0. "When will HUBwatch for windows work wiTH Pathworks TCP/IP?" by BOSNET::COLUMBUS () Wed Jun 02 1993 20:34

I just tried to use BETA 14 version of hubwatch for windows and found that 
it doesn't support Pathworks TCP/IP. It looks like there is some conflict. 
When will this be possible? I'd like to use it under Pathworks TCP/IP, 
and I suspect there will be a few customers who want to do this also.

T.R	Title	User	Personal Name	Date	Lines
257.1	DEcember 1993	EMDS::SEAVER	Bill Seaver, HUBwatch Mktg	`Mon Jun 14 1993 02:37`	10
	From: NAC::DELNI::FORREST "Jack Forrest LKG2-2 Pole Z5 226-7392" 4-JUN-1993 14:27:28.89 To: BOSNET::COLUMBUS CC: NAC::SEAVER Subj: will be possible in 2.0 in December; both HUBwatch and Pathworks have to go to V5.0 Pathworks 5.0 will support the Winsock API in its TCP/IP stack; HUBwatch 2.0 will support that API. Today, Pathworks 4.1 uses the 3com stack, and hubwatch uses its own stack, and both expect to handle all the ip traffic.
257.2	TCP/IP stack?	EZLCHZ::EZZELL	Mike Ezzell	`Mon Jul 19 1993 19:36`	4
	Does this mean that if I have a Pathworks (DECNET) client PC that wants to run HUBwatch, this will work? HUBwatch provides its own TCP/IP stack? This is what would work best for my customer.
257.3		NAC::FORREST		`Wed Jul 21 1993 21:48`	5
	That is correct - you should be able to run HUBwatch on a PATHWORKS DECnet client, as long as you're using the NDIS driver. This was documented in the HUBwatch V1.0 Release Notes. jack