Conference netcad::hub_mgnt

Same here on a DECstation 320 with 6MB memory and DEPCA Ethernet
adapter. While it runs next door on a DECpc 466MT with 4MB and a 
EtherWorks III... 

*Robert

    
    Make that 3 on a DECpc 466D2 MTE with 16MB and a DEPCA.
    
    Bob

    Make that 4 on a DECpc 333c with 8MB and a DEPCA.
    
    Dave

    Check to be sure the following line is in your autoexec.bat:
    
    set WSAVERS=1.1
    
    Our installation program should have put this in there for you. If you
    used our installation program properly and it didn't add that line to
    your autoexec.bat, please let us know.
    
    Thanks,
    Jim

    
    It was placed into autoexec.bat.
    
    Bob

    I forgot to mention that it needs to be BEFORE any line that starts
    windows. Our install program can add lines at the end or at the
    beginning or a file. We chose to put that line at the end. If your
    autoexec.bat starts windows before it gets to the WSAVERS=1.1 line,
    hubwatch will fail. We'll probably insert our line at the beginning
    of autoexec.bat. That should take care of that particular situation.
    
    Jim
    

That was it! We make extensive use of the boot menu facility in DOS 6 to
boot a variety of configurations. We added a special item for HUBwatch
but didn't notice that the two SET statements in AUTOEXEC.BAT never got
executed. 

HINT*HINT*HINT: It would be very nice if HUBwatch could use a default 
for those two environment variables or if this isn't feasible *please* 
give a message that the variables are missing instead of GPFing.

*Robert

This install program did add the line. I just had to put it at the
start of my autoexec.bat before windows.

thanx d.j.

Well .... the install failed to add wsavers=1.1 in my autoexec.bat


so i put it in at the start

its now there as an env variable, but the application just (briefly) 
fires up then goes away. There was no error message.....


prior to the wsavers being there, i got a protection error as mentioned 
in previous replies ....


hope this info helps investigate/resolve the problem

any ideas?


.regards
dave

    .9 is an unrelated problem. The "wsavers" gets you past the gpf. 
    
    Remember, this code is very much pre-release so there's still some
    gotcha's. 
    
    I would recommend using the installation program and accepting all the
    defaults. If you install in a directory other than \hubwatch I think
    you may come across some new bugs. We're working on it :-)
    
    .9 may also indicate that the agent is unreachable. Be sure to specify
    an agent on the command line such as:
    
    hubwatch -x 16.11.22.33
    
    Jim
                           

    also see note 656. Be sure to specify your the hub's ip address with a
    lowercase x
    
    hubwatch -X 16.11.22.33 will fail
    
    hubwatch -x 16.11.22.33 will work correctly.
    
    Jim

I failed installation HUBwatch for windows 2.0 FT

Ping works(after I ran startnet.bat file),
but when I start HUBwatch,HUBwatch displayed the message:

" No response from agent". 

I added  correct IP address to command line.

***
hard: 
DECpc466D2 lp ,8MG memory 
DE200(DEC EtherWorks)

I configured the NDIS driver. 
 

Thank you ,Regards

    RE on .12
    
    Did you move the software to another PC ?
    I had the same experience after copying the software to another PC and
    I forgot to take the DECPW.386 and PCSA.DRV files from the windows
    directory.
    
    
    Best Regards 
    Peter Folker
    MCS Eindhoven