T.R | Title | User | Personal Name | Date | Lines |
---|
2983.1 | C:\HUBWATCH\IPSTACK should be in PATH | NETCAD::WAGNERCOFFIL | | Fri Nov 17 1995 12:39 | 11 |
|
>> I can ping the hubs after I load the hubwatch IP stack and after I
>> start windows. But when I start hubwatch I get a SYSTEM ERROR. If I
>> start up the hubloader in gives a failed to initialize socket. and
>> when I try to startup the TFTP loader it say that Windows socket
>> library not available.
Is C:\HUBWATCH\IPSTACK in your PATH statement?? It should be and it should
occur before any other possible TCPIP stack directory(if you have multiple).
Barb
|
2983.2 | Path statement is fine | OTOOA::MMCGREGOR | Network Services - Ottawa, Ontario | Tue Nov 21 1995 13:31 | 1 |
| Yes it is the first pointer in the path statement.
|
2983.3 | Check READ_ME.TXT and note 1886.7 | NETCAD::WAGNERCOFFIL | | Mon Nov 27 1995 13:22 | 3 |
| Check the READ_ME.TXT, refer to note 1886.7.
Barb
|
2983.4 | | KAOT01::R_HARPER | This space unavailable, Digital has it now | Thu Nov 30 1995 12:54 | 5 |
| Sound like the DOS apps are ok but the Window's apps are not.
Do you have DECPW.386 under the [network] section of system.ini?
|