| 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 |
HI,
Just want to confirm the IP stack requirement for Window For Workgroup:
With ClearVISN - Chassis Manager (HUBwatch V5.0 for Window), does it
provide IP stack as HUBwatch V.x? Or we have to order/use third party
IP stack?
Secondly, Does ClearVISN - Chassis Manager 'bundle' with its own Ip
stack?
thanks in advance for help
Andrew Chiu - Network services Sydney
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3558.1 | Nope | SLINK::HOOD | Your bad news bear | Tue May 28 1996 11:44 | 5 |
We're out of the stack business. You need to supply your own winsock IP stack. Hmmmm. No, that's not right... We're *in* the MultiStack business. Well, you know. | |||||
| 3558.2 | Just confirm my understanding! | SNOFS1::63496::CHIUANDREW | Tue May 28 1996 19:24 | 10 | |
re .1,
In HUBwatch V4.x, IP stack is 'bundled', does it mean where customer
migrate to WIN 95, Digital will assume they will use Microsoft (or
third party) IP stack? I beleive our ClearVISN products use winsock
compliance IP stack, is it correct?
thanks again for clarification.
Andrew Chiu - Network services Sydney
| |||||
| 3558.3 | WinSock | MXOC00::CSILVA | Carlos@MXO 7296514 Free but focused | Tue May 28 1996 20:01 | 8 |
The IP stack 'bundled' is the PATHworks IP stack, that
complies with Windows Socket v1.1.
What HubWatch and clearVISN products need is any IP stack
WinSock compliant.
Carlos
| |||||