| 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 |
I have a customer who has tried to install HUBwatch V3.1 onto a DECpc 455 DX2 running PATHWORKS 5.1 with TCP/IP and Window for Workgroups with out any success. The only support they recieved rfrom Colorado was that sometimes it works and sometimes it doesn't. I guess that's the new Support philosophy!#%& With my endeavors to try and install HUBwatch I found that everything comes up fine we can Ping the hub but when HUBwatch is run it comes up with "No Response from Agent". The only way to get this to work was to configure PATHWORKS with out TCP/IP and to run only TCP/IP, TN, BAPI from STRTNDIS.BAT. This seemed to be the only combination that worked but of course not all of his applications work under that config. According to the READ_ME.TXT for HUBwatch the only thing we needed to worry about was to have a copy of WINSOCK.DLL and PWWSOCK.EXE local on the system, we did that PWWSOCK.EXE in \hubwatch\ipstack and WINSOCK.DLL in \Windows and still no Joy!!! Can anyone help!!! Signed Burnt yet once more!!!
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1900.1 | decpw.386 missing? | KEIKI::WHITE | Wed Jan 18 1995 05:28 | 10 | |
We had to make sure that decpw.386 was in system.ini on the
network= line or hubwatch would flat out not work.
Note - when configuring for ODI drivers in WFWG the decpw.386 gets
deleted. It took us quite a while to get ODI drivers to work with
hubwatch but after adding the decpw.386 back into system.ini and
careful editing of net.cfg hubwatch has been working fine.
Bill
| |||||
| 1900.2 | autre piste | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Wed Jan 18 1995 16:38 | 4 |
other point to check have you the right path defined jean-yves | |||||
| 1900.3 | check these other things... | NETCAD::WAGNERCOFFIL | Wed Jan 18 1995 20:26 | 25 | |
CHECK:
- Maybe a resource issue. Check Conventional memory, files, buffers...
Disable other applications while running HUBwatch.
- network=...,DECPW.386 should be in the [386Enh] section of the
c:\windows\system.ini file. This command runs the PATHWORKS
v5 Windows Virtual Device Driver(VxD). If you are running
HUBwatch with the network(TCP/IP stack) or PW V5.1, in either case,
this command should already be in SYSTEM.INI.
- Make sure that WINSOCK.DLL is NOT in the same directory as
HUBWATCH.EXE. For PW V5.1, WINSOCK.DLL is located in c:\PW and
for HUBwatch in c:\hubwatch\ipstack.
- Make sure your PATH statement includes the directory where the
stack is that you are using. Make sure that the stack that you
are NOT USING is NOT in the PATH statement.
- You may want to try increasing UDPMaxSock and TCPMaxSock in the
[TCPIP] section of the c:\pw or c:\hubwatch\ipstack PWTCP.INI file.
- Take a look at the WFW section in the README.TXT.
Barb
| |||||