| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2679.1 | PING?; check stack | NETCAD::WAGNERCOFFIL | | Thu Aug 24 1995 17:55 | 9 |
| Using the DEC IP stack, can you ping the HUB in Windows
from a DOS prompt?
If no can you ping yourself?
Does the stack load correctly when you reboot?
Barb
|
| 2679.2 | Works Running Pathworks V5 STack, and HUBwatch SLIP | MSDOA::REED | John Reed @CBO = Network Services | Fri Aug 25 1995 00:48 | 5 |
| I am using HUBwatch V4, on a 425SL with 8Megs. It works nicely, if you
don't have too many modules inthe hub, or too many entries in the
DECagent tables.
JR (who's wishing for a HiNote)
|
| 2679.3 | OK on a 425SLC/e | HERON::virenq.vbo.dec.com::HEMMINGS | Lanterne Rouge | Fri Aug 25 1995 07:17 | 3 |
| I have a 425SLC/e (the Olivetti) with 8Mb and it's OK - I can run either over
a Xircom adaptor or via the Netrider package. Not overpoweringly speedy, but
it's OK ...
|
| 2679.4 | Have exactly the same problem ... | MFRNW1::SCHUSTER | Karl Schuster @RTO OMS Munich Germany | Fri Aug 25 1995 08:40 | 6 |
| I have a HiNote Ultra Notebook - and get exactly the same error:
"System Error"
PING to the HUB works, but not HUBwatch !
Karl
|
| 2679.5 | HUBWATCH_SYSTEM logical pointer | NETCAD::GORDON | | Fri Aug 25 1995 08:43 | 5 |
| Just a guess...
Do you still have an entry HUBWTACH_SYSTEM set ?
If so, the v4.0 hubwatch doesn't modify this entry in your autoexec.
You have to do that manually.....
|
| 2679.6 | check WINSOCK.DLL; check Conventional memory | NETCAD::WAGNERCOFFIL | | Fri Aug 25 1995 10:55 | 41 |
| >> Do you still have an entry HUBWTACH_SYSTEM set ?
>> If so, the v4.0 hubwatch doesn't modify this entry in your autoexec.
>> You have to do that manually.....
HUBwatch V4.0.1 will comment out (REM HUBWATCH_SYSTEM) in your AUTOEXEC.BAT.
If you choose not to have your AUTOEXEC.BAT modified by the installation,
if you do not REM out this line, and if the HUBWATCH_SYSTEM points to a
different location then you will have a problem.
***************************************************************************
Getting back to the SYSTEM ERROR...
Search your local disk/s for WINSOCK.DLL.
The WINSOCK.DLL should be in the directory that your stack is in.
WINSOCK.DLL should NOT be in \WINDOWS or \WINDOWS\SYSTEM.
**If you have multiple occurences of WINSOCK.DLL MAKE SURE that the one**
**in your stack directory APPEARS IN YOUR PATH STATEMENT BEFORE ANY OTHER.**
The WINSOCK.DLL path must occur in the PATH statement.
i.e. Using PATHWORKS V5.1 TCP/IP stack
>SEARCH
c:\pw\WINSOCK.DLL
c:\hubwatch\IPSTACK\WINSOCK.DLL
c:\windows\winsock.dll --> WRONG, should not be here but say it is for
the example.
>PATH
PATH=C:\WINDOWS;C:\PW;....
Problem is that HUBwatch will use the first occurrence of the WINSOCK.DLL
in the path, in this case the one in \WINDOWS. It should be using the
one in C:\PW.
The invocation of HUBwatch TCP/IP satck (C:\HUBWATCH\IPSTACK\STRTNDIS)
always puts the C:\HUBWATCH\IPSTACK as the first path in the PATH statement.
Also check conventional memory used.
Barb
|
| 2679.7 | 425SE laptop also... | NETCAD::WAGNERCOFFIL | | Fri Aug 25 1995 12:25 | 7 |
| BTW...
I have a 425SE laptop, 8 MEG of RAM, Windows for Workgroups 3.11,
HUBwatch IP stack and PW IP stack, XIRCOM(PE3), and HUBwatch V4.0.1.
Can be a little slow, but overall not too bad.
Barb
|