| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1611.1 | Discussed elsewhere in this conference, also | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Oct 25 1994 12:09 | 5 |
| The error is misleading, sort of. The file PWWSOCK.EXE is missing from your
HUBWATCH\IPSTACK directory. The problem has nothing to do with conventional
memory. Read the READ_ME.TXT file.
...Roger...
|
| 1611.2 | Same problem, not resolved. | MAIL2::BLACKMAN | As always..High on Life! | Fri Apr 21 1995 11:18 | 5 |
| Well, my pwwsock.exe is there and I get the same eerror . We are
using WIN3.1 and Hubwatch 3.1 as well. Anyone recognize this problem.?
-jon
|
| 1611.3 | low conventional memory | UTRTSC::GROOT_R | Ronald de Groot | Mon Apr 24 1995 11:16 | 11 |
|
I had the same problem. The problem is only on PC's with Windows 3.1
What you can do is copy pwwsock.exe to the windows\system dir. or
make a path to the hubwatch\ipstack When you start the ipstack with
strtndis.bat the path is normaly set by strtndis.bat. HUBwatch must
also find winsock.dll and decpw.386. The decpw.386 is loaded when
windows startup via system.ini -> network=*etc,decpw.386. The error
messages has nothing to do with low conventional memory. (windows
doesn't matter how must conventional memory you have).
Ronald
|
| 1611.4 | \HUBWATCH\IPSTACK needs to be in PATH | NETCAD::WAGNERCOFFIL | | Wed Apr 26 1995 09:52 | 2 |
| Is \HUBWATCH\IPSTACK in your PATH statement?
Barb
|
| 1611.5 | PATHWORKS IP stack system files clarification | NETCAD::WAGNERCOFFIL | | Wed Apr 26 1995 12:39 | 21 |
| We do not recommend moving IP Stack components out of their
installed directories. This can lead to problems if you are
trying to use multiple stacks.
The proper configuration is to always have the IP stack that
you are using in the PATH. The \HUBWATCH\IPSTACK STRTNDIS.BAT
file should automatically set your PATH to include \HUBWATCH\IPSTACK
as the first occurrence in the PATH statement.
As with PWWSOCK.EXE, WINSOCK.DLL should remain in your IP stack
directory. Note: If you are running WFW 3.11, MS may have installed
a WINSOCK.DLL in the \WINDOWS directory. Make sure your IP stack
is in the PATH before \WINDOWS. For the better solution, rename
the MW \WINDOWS WINSOCK.DLL to .SAV and make sure that your IP
stack directory is in the PATH, that will ensure that you
are using the WINSOCK that is provided with your stack.
DECPW.386 should always be in the \WINDOWS\SYSTEM directory.
Barb
|
| 1611.6 | Thanks... | MAIL1::BLACKMAN | As always..High on Life! | Mon May 01 1995 09:42 | 9 |
| Well, after waisting my time on the clone PC at the customer, I
suggested trying a DECpc thet had there. Loaded Win 3.1, Hubwatch 3.1
rebooted and it worked fine. Still don't know what the other PC's
problem was, all teh software and memory was the same.
Anyway, thanks for your help.
-jon
|