| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 193.1 | Pointer | LEMAN::BRUNNER | | Thu Mar 25 1993 07:18 | 5 |
| The latest firmware is at
KALI::sys$public:[wgb.firmware.final]flash.exe
For a VMS load look at 51.2 pointer.
Hope it helps
Walter
|
| 193.2 | It worked... a few changes | BOSNET::COLUMBUS | | Thu Mar 25 1993 16:31 | 17 |
| Thanks for the info...I ended up doing the following
1.
$ copy KALI::sys$public:[wgb.firmware.v3]flash.exe
_To: flash_v3.exe
2.
NCP>set node 63.501 name db90 hard addr 08-00-2b-25-d4-33 serv circ sva-0 -
_ load file flash_v3.exe
NCP>load node db90
The hub loaded and ran hubwatch fine..
John
|
| 193.3 | DB90 v3.1 is protected | HOO78C::TURHAN | | Tue Apr 13 1993 09:51 | 21 |
|
Hi,
The 3.1 kit at KALI is protected. Could you please help to copy it ?
Thanks,
Tankut
Directory KALI::SYS$PUBLIC:[WGB.FIRMWARE.V31]
CRC_TAB.H;3 no privilege for attempted operation
FLASH.EXE;276 no privilege for attempted operation
FLASH.INT;18 no privilege for attempted operation
FLASH.TSK;11 no privilege for attempted operation
FLASHTASK.BLD;1 no privilege for attempted operation
FLASH_ROM.DIR;1 3
IMAGE_BLDR.EXE;1 no privilege for attempted operation
Total of 7 files, 6 blocks.
|
| 193.4 | protection problem should be fixed | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Fri Apr 16 1993 00:02 | 2 |
| Protection problem should be fixed.
|
| 193.5 | V3.1 HUBwatch is not working | HOO78C::STEEG | | Thu Apr 29 1993 09:56 | 13 |
| Hi,
I loaded the bridge with V3.1 firmware.
This is fine, with NCP I can reach the bridge90 and see it is running
with firmware V3.1.
BUT I can't reach the bridge (and the repeaters) with HUBwatch.
What can be the problem?
/-/ Henk.
|
| 193.6 | please check the DENMA console | SLINK::HOOD | Just add water | Thu Apr 29 1993 11:31 | 8 |
| Do the bridge and repeaters show up in the DECagent's "Show Community"
console display?
If so, then HUBwatch *should* see them.
If not, make sure you've added the bridge (either thru the agent's console
or thru HUBwatch) correctly, and have hub management enabled on the bridge.
That should fix the problem.
|