[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
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

2983.0. "Hubwatch 4.1.1 and WFW 3.11 problems" by OTOOA::MMCGREGOR (Network Services - Ottawa, Ontario) Thu Nov 16 1995 17:03

    I am trying to install Hubwatch for windows 4.1.1 on a PC running WFW
    3.11 with no network loaded.  I followed the install info and
    configured the network card in WFW first then installed with network
    support HW 4.1.1 and all went fine.
    
    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.
    
    The Readme.txt say that WINSOCK.DLL & PWWSOCK.EXE must be in the 
    c:\hubwatch\ipstack.   Both files are present.
    
    
    What am I missing.
T.RTitleUserPersonal
Name		DateLines
2983.1C:\HUBWATCH\IPSTACK should be in PATHNETCAD::WAGNERCOFFILFri Nov 17 1995 15:3911
    
>>    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.2Path statement is fineOTOOA::MMCGREGORNetwork Services - Ottawa, OntarioTue Nov 21 1995 16:311
    Yes it is the first pointer in the path statement.
2983.3Check READ_ME.TXT and note 1886.7NETCAD::WAGNERCOFFILMon Nov 27 1995 16:223
Check the READ_ME.TXT, refer to note 1886.7.

Barb
2983.4KAOT01::R_HARPERThis space unavailable, Digital has it nowThu Nov 30 1995 15:545
    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?