| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 661.1 | Me too | BIKINI::KRAUSE | European NewProductEngineer for MCC | Wed Jan 26 1994 06:28 | 5 |
| 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
|
| 661.2 | Here Too | LEVERS::DRAGON | | Wed Jan 26 1994 09:16 | 4 |
|
Make that 3 on a DECpc 466D2 MTE with 16MB and a DEPCA.
Bob
|
| 661.3 | Widespread | ALBANY::BARTLEY | | Wed Jan 26 1994 09:40 | 3 |
| Make that 4 on a DECpc 333c with 8MB and a DEPCA.
Dave
|
| 661.4 | solution?? | QUIVER::ORSHAW | | Wed Jan 26 1994 13:21 | 10 |
| 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
|
| 661.5 | It was/is there | LEVERS::DRAGON | | Wed Jan 26 1994 15:19 | 4 |
|
It was placed into autoexec.bat.
Bob
|
| 661.6 | more... | QUIVER::ORSHAW | | Wed Jan 26 1994 15:48 | 9 |
| 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
|
| 661.7 | That's it | BIKINI::KRAUSE | European NewProductEngineer for MCC | Thu Jan 27 1994 03:21 | 10 |
| 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
|
| 661.8 | That did it! | MAADSP::DJAMES | | Thu Jan 27 1994 12:26 | 4 |
| 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.
|
| 661.9 | wsavers=1.1 made a difference, but it still fails! | UNITED::THORND::thorntond | Netware .....thats a Novel network! | Thu Jan 27 1994 12:34 | 20 |
| 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
|
| 661.10 | unrelated bug | QUIVER::ORSHAW | | Thu Jan 27 1994 13:47 | 16 |
| .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
|
| 661.11 | yet more | QUIVER::ORSHAW | | Thu Jan 27 1994 15:54 | 8 |
| 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
|
| 661.12 | Why ? | TKOV51::SATO_TET | Cogito Ergo Sum | Tue Feb 01 1994 09:36 | 18 |
| 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
|
| 661.13 | moved software to another PC ? | HLFS00::FOLKER_P | Magis Futundum Est | Tue Feb 01 1994 11:02 | 11 |
| 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
|
| 661.14 | I edited the system.ini . | TKOV51::SATO_TET | Cogito Ergo Sum | Wed Feb 02 1994 07:46 | 30 |
| > <<< HLFS00::FOLKER_P "Magis Futundum Est" �ˤ��Ρ��� 661.13 >>>
-< moved software to another PC ? >-
> RE on .12
> Did you move the software to another PC ?
No,I did not .
I added a following line in system.ini ,
DEVICE=C:��hubwatch��core��vpktdrvr.386
I corrected the line ..
DEVICE=CC:��windows��DECPW.386
HUBwatch works !
You gave me the hint.
Thank you!
> 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.
Thank you ,Regards.
|