| 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 |
Has anyone installed Hubwatch 3.1 using PCTCP instead of our pathworks?
I'm assuming this is do-able but haven't seen references to it in the
install manual shipped with the software.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1884.1 | OK, Try it. | HGOVC::SIUKEUNGLEE | Fri Jan 13 1995 13:53 | 8 | |
Hi,
I think it should work. I have using MicroSoft TCP/IP, it work fine.
When you install HUBwatch, choose Install HUBwatch only.
Good Luck.
David.
| |||||
| 1884.2 | It works with PCTCP stack! | NCMAIL::MCNALLT | Tom McNall - Rochester NY | Wed Jan 18 1995 14:17 | 7 |
We finally got it to work. We installed "hubwatch only" option and the
screen with the agent name and address wouldn't come up and the machine
hung. We replaced the customer's winsock.dll with a newer version from
another of his PC's. The agent/address screen then came up but we still
couldn't come up. After reading his PCTCP manuals, we discovered that his
\windows\system.ini needed an entry for a file VPCTCP in the [386enh]
section. After editing this in it worked.
| |||||