[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

787.0. "T2.8 showstopper? or do I over react?" by WOTVAX::HATTOS (I think, Therefore I'm paid less) Thu Mar 03 1994 13:35

    I have what I consider to be a serious failing of HW T2.8.
    
    I have a DEC laptop which until now has never had a network installed.
    Quite rightly in my opinion, you supply an IP stack with Hubwatch and
    even supply installation options to configure the IP network
    parameters.
    
    HOWEVER
    
    Hubwatch is a Windows based management tool, using the supplied IP
    stack you cannot get Hubwatch working at all.
    
    I would think the majority of people who have been testing T2.8 have
    installed it on a PC with Pathworks running, this means that the
    network.drv line in SYSTEM.INI points to the right driver, in my case
    on the PC on my desk PATHWRKS.DRV. 
    
    Hubwatch does not supply a network driver for Windows, you are assuming
    I already have Pathworks. Therefore Windows thinks I have no network
    and Hubwatch won't talk over either the serial port for SLIP or the
    Ethernet card.
    
    Is Pathworks a pre-requisite for Hubwatch? If so this could be a major
    drawback. I intend to have Hubwatch loaded on my laptop so that I can
    manage hubs in any office I go to. All I should have to change would be
    my IP address, but I have had to install a product on my laptop which I
    do not want and have no need of, just to get Hubwatch working.
    
    Actually what I have done is hack the SYSTEM.INI and PATHWRKS.INI files
    so that SLIPPY the LAPTOP thinks he is running a network. This was by
    no means easy and took me about 4 hours to figure out.
    
    What is the position on this? I presume you will be selling Hubwatch
    into shops which don't necessarily use Pathworks or any PC networking
    for that matter.
    
    HW is a low cost management tool which deserves to sell well but this
    needs sorting out first.
T.RTitleUserPersonal
Name		DateLines
787.1Pathworks Not NeededLEVERS::DRAGONThu Mar 03 1994 16:204
    
    Pathworks is not needed for HUBwatch for Windows.
    
    Bob
787.2But no Windows driver == No HubwatchDELBOY::HATTOSThu Mar 03 1994 16:275
    Bob,
    
    Then how do people who have no network .. use it?
    
    Stuart
787.3LEVERS::DRAGONThu Mar 03 1994 16:4010
    
    Stuart,
    
    	When you install HUBwatch for Windows you select the installation
        option "Install HUBwatch and network", which will provide you with
        HUbwatch and network files for IP stack. My PC doesn't have
        Pathworks and it works fine over Ethernet.
    
    Bob
787.4Will re-install and see!DELBOY::HATTOSFri Mar 04 1994 07:398
    Bob,
    
    I did just that on my laptop and I got NO network driver for windows...
    
    I will scrub out all the hacking I did and try a re-install from
    scratch of Hubwatch. Will let you know.
    
    Stuart
787.5Usable for other comms too ?LARVAE::HARVEYBaldly going into the unknown...Fri Mar 04 1994 11:008
   Once this is sorted is the TCP stack usable for general networking purposes 
   or is it restricted to HUBwatch use only ?
 
   I want to use HUBwatch and also SLIP for other activities.
 
   Thanks
 
   Rog
787.6Start Net Then WindowsLEVERS::DRAGONFri Mar 04 1994 13:009
    
    RE.4
    
    Stuart,
    
    	Check that the strtndis.bat line in autoexec.bat preceeds the start of 
        Windows (the win line).
    
    Bob
787.7pwtcp.ini needs to be modified after network installLEVERS::P_MCCARTHYFri Mar 04 1994 14:1029
    
    Stuart,
    
        In addition to what Bob Dragon said, I would add the following.
    T2.8 does have the startup files (strtndis.bat/strtslip.bat) for
    NDIS/SLIP startup. In addition, you need to do as Bob stated and
    do the "HUBwatch and Network" installation and make a few changes
    to pwtcp.ini file (supplied by HUBwatch installation).
    
    Changes to pwtcp.ini
    
    [TCPIP Section]
    NetworkType = 2      (vs 0 for Ethernet/NDIS)
    
    [SLIP Section]
    CommPort = COM2      (Com1 has problems starting windows when Pathworks
                          is installed. Use Com1 and you won't run into
                          this problem. This will be added to the release
                          notes for pathworks customers if a pathworks fix
                          is not found.
    
    I would suggest the HUBwatch Installation and Configuration Manual
    which should answer all your questions and eliminate you from your
    own custom modifications.
    
    This should solve your problem...
    
          Pat