| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2110.1 | X0.1.0 not X0.0.10 | NETCAD::FORINO | | Thu Mar 16 1995 15:26 | 4 |
| Note that this beta test kit reports itself as X0.1.0 and not X0.0.10
as my previous note had said.
John
|
| 2110.2 | Not under Windows95 | DELBOY::stus.olo.dec.com::HATTOS | It's simple - but it's not easy | Sat Mar 18 1995 14:14 | 5 |
| Hubloader won't install under Windows95 M7.
It starts to install then falls over with a GPF in ~tmp262c.exe.
Stuart
|
| 2110.3 | Not supported | NETCAD::FORINO | | Mon Mar 20 1995 11:52 | 2 |
| Windows9? isn't supported right now.
John
|
| 2110.4 | 8*) | DELBOY::stus.olo.dec.com::HATTOS | It's simple - but it's not easy | Mon Mar 20 1995 14:09 | 1 |
|
|
| 2110.5 | X0.2.0 available | NETCAD::FORINO | | Wed Apr 12 1995 16:00 | 9 |
| A beta version X0.2.0 is now available. Same spot as described in .0.
This version has a few bug fixes and some minor enhancements. For
example,
- better status messages
- flexbility to install NetRider loader where you want when
installing
- non "public" community string will work in SHOW operation
|
| 2110.6 | DECagent90, now packetprobe, what's next! | SLUGER::DAVIDSON | | Fri Apr 14 1995 23:04 | 40 |
| Hello,
I would like to get a copy of the HUBloader program to run at a
customer site if possible. Just a second! The customer is a loyal
purchaser of Digital's network equipment, has over 50 DEChub90's
throughout their WAN which spans the US. I would not not take it without
asking for permission here, but I have recently had to deal with an
extremely irate customer who was put through the ringer to get DECNDU.
He was told to pay extra, although should have been included with his
HUBwatch 3.0 kit?
I just spent the past 2 weeks on/off helping him upgrade 23 DECagent90
modules. Over the past year, most have either smoked, lose their
brains, (IP address resets to 0, become unuseable, V 1.0 firmware),
or been at rev 2.0.16, and still couldn't upgrade! I went onsite and
replaced the last of the DECagent90's that wouldn't respond (6 this
week) I had to grab a new SDDF.STP file off the net so that they/we
could even upgrade the agents they had (The .STP file that was part of
the DECNDU distribution kit did not include DECagent support. The
customer, although not sophisticated, but definately not stupid spent
more than entire day to resolve this upgrade problem. CSC was of little
help to them, not pot-shots intended, but conveying what transpired.)
Now, they have 7 or 8 DECpacketprobe's at version 1.0, that are
useless!!! I get the same SDDF.STP garble, don't know anything about
those guys, when trying to run #$^&%&*@# DECNDU. AAARRRGGGHHH!!!!
=> Is there a newer SDDF.STP file which includes support
for DECpacketprobe?
=> Should I take suggestions from related notes on this
problem, and struggle through it? (adding TFTP/PC server's
IP addr, option #10, etc...)
=> Provide the customer w/HUBloader (better mousetrap, GUI
interface. They will be 1st in line for HUBwatch 4.0
when available)
Sorry to ramble, although a P.I.T.A. to go through this in a pretty
valueable learning experience.
Thanks - Lenny
|
| 2110.7 | an update to my prevoius note...still broke! | SLUGER::DAVIDSON | | Tue Apr 18 1995 17:12 | 12 |
| Just an update...
I was back onsite this morning to verify my findings on updating the
DECpacketprobe 90. I went armed with the instructions from note #
1753.9
I am able to successfully get to step 3, and no further. After issuing
the command "decndup /u/f 1.0.0.70 (probe's IP) c:\firmware\ns3210.s"
PC responds with " DEVICE information not found in SDDF.STP"
Is there a later version of this file which includes support for the
packetprobe?
Lenny
|
| 2110.8 | No direct support of the DECpacketprobe 90 from DECndu Plus | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Apr 19 1995 12:08 | 6 |
| You cannot use DECndu Plus to directly load a DECpacketprobe 90. The probe does
not respond to the normal mechanism for triggering a load from a remote host.
The probe must initiate the load. DECndu Plus can be setup to be a TFTP server.
There are notes in this conference which describe this.
...Roger...
|
| 2110.9 | exit | SLUGER::DAVIDSON | | Fri Apr 21 1995 22:59 | 10 |
| Yes!!!
Armed with a copy of note #1753.9, I spent a couple of hours and
actually did get this to work. As it states, the step to erase the
flash ROM took more than a couple of minutes on my network. I ended
up adding the DECNDUP /u /f... line to STRTNDIS.BAT 4 or 5 times and
it finally managed to take. You will have to enter option 12 at the
probe end to reset the agent afterwards, this will indicate "New boot"
and display the new version of firmware on the Packetprobe.
Lenny
|
| 2110.10 | HUBloader and WIN32 TCP/IP | ANGLIN::SCHWEIZER | | Wed Apr 26 1995 01:22 | 9 |
| I'm trying to get EZloader running with WIN32 TCP/IP from our buddies
at Microsoft. No luck. It starts fine, but when you run HUBloader it
responds [ERROR]Problem initializing socket {get}. HUBLoader does the
same thing if EZload is not started. Seems like EZloader running with
no place to go. Version WIN32 TCP/IP 3.11a and HUBloader X.0.1.0. By
the way HUBwatch works fine with WIN32 TCP/IP. Thanks in advance if
anyone can shed some light on this.
Scott
|
| 2110.11 | Some clarification | NETCAD::FORINO | | Mon May 01 1995 16:40 | 6 |
| RE. .10
To clarify what you're saying it is the HUBLoader that always is reporting
this error message whether or not the EZloader is running.
John
|
| 2110.12 | X0.3.0 available | NETCAD::FORINO | | Mon May 01 1995 16:42 | 5 |
| A beta version X0.3.0 is now available. Same spot as described in .0.
This version has a few bug fixes.
John
|
| 2110.13 | Install won't | SOUPER::COOPER | Ron Cooper | Fri May 12 1995 13:12 | 3 |
| When I try to install the latest kit, I get an ERROR IN SCRIPT LINE 0, Invalid
file header, then a general protection fault. I got another copy of the kit, in
the event that the xfer trashed it, but the same results.
|
| 2110.14 | Some info? | NETCAD::FORINO | | Mon May 15 1995 12:57 | 3 |
| Can you give us some information about your PC setup?
John
|
| 2110.15 | Check for LOAD020.INF on Diskette 1 | NETCAD::WAGNERCOFFIL | | Mon May 15 1995 14:07 | 2 |
| Is there an .INF file(LOAD020.INF) on the first diskette??
Barb
|
| 2110.16 | Official Standalone HUBloader V1.0.0 available | NETCAD::FORINO | | Fri May 26 1995 14:38 | 96 |
|
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
To: HUBLOADER_FT.DIS DATE: May 26, 1995
FROM: John Forino
DEPT: Networks Engineering/
HUB Product Engineering
DTN: 226-7585
LOC: LKG2-2/Y10
NETMAIL: NETCAD::FORINO
SUBJ: HUBloader for Windows V1.0.0 Standalone kit is available
The SSB version of the HUBloader for Windows V1.0.0 standalone
kit is now available for use. This product will perform firmware
load upgrades of hub modules, hubs and the GIGAswitch/FDDI.
The other HUBloader developers and myself would like to thank
everyone who participated in field testing this utility for
their time and feedback.
This standalone version of HUBloader for Windows will be
available through SSB as part of the DEChub Consolidated Firmware
kit. The HUBloader software will also be bundled in as part of
HUBwatch for Windows V4.0 kit.
(One minor nit:
The HUBloader READ_ME_.TXT included in the HUBwatch kit
has one note referring to a system error concerning
the AUX device. The READ_ME_.TXT included in the
standalone HUBloader kit does not contain this note.
This note was a mistake - please disregard it.)
For those of you who have been field testing this product
PLEASE REPLACE YOUR FIELD TEST KITS !!!
(signified by a version 'X') with this new kit.
The kit can be obtained by anonymous ftp on bhub. The files
that make up the kit are
hubloader/DISK.ID
hubloader/HUBLD100.001
hubloader/INSTALL.EXE
hubloader/LOAD100.INF
hubloader/LOGO.BMP
hubloader/READ_ME_.TXT
The IP addresses of bhub is 16.21.16.156. For those of you
who need DECnet access bhub has address 55.91 and the above
files can be found at /var/users/ftp/hubloader. If using
ftp to obtain the files please copy the files over in binary mode.
If you have any problems accessing the files, please send mail
to me at NETCAD::FORINO.
If you have functional problems with the product, report it through
official channels or put a note in the NETCAD::HUB_MGNT notesfile.
============================================================================
IMPORTANT FOR FIRST TIME USERS
- No hardcopy documentation of HUBloader will be available.
Therefore, the only other documentation available is a
READ_ME_.TXT file as part of the HUBloader kit for
release notes and to explain installation. There is also
online help to explain the HUBloader functionality and its
interface.
READ THE READ_ME_.TXT FILE !!!!
let me say it again
READ THE READ_ME_.TXT FILE !!!!
- Loading modules requires a TFTP Server to perform the actual
file loads. The TFTP Server we provide is a seperate utility
from the HUBloader utility and must be up and running before you
attempt a load from the HUBloader utility. This is different
than what people who use NDU are familiar with.
This misunderstanding caused a lot of people trouble during
field test, so read the READ_ME_.TXT and online help to make
sure you have this utility running first.
|
| 2110.17 | | SSSAXP::LEMONS | And we thank you for your support. | Sat Jun 03 1995 02:41 | 24 |
| Hi
I noticed (in the file hubloader.release_notes):
" o HUBloader only supports loads of devices that
utilize TFTP.
It does not support MOP loading. Therefore, HUBloader
will
not support loading of the following hub devices:
1. DECbridge 90/90FL
2. DECagent 90 V1.1 or earlier"
Yet, the /usr/kits/HUBwatch/dcffiles.dat file contains this line:
DECbridge 90, 90FL/V3.9/dewgb390.sys/
Why have an entry for something that can't be loaded? Or am I missing
something?
Thanks for the help!
tl
|
| 2110.18 | | CRONIC::LEMONS | And we thank you for your support. | Tue Jun 06 1995 14:16 | 12 |
| I want to use HUBloader to upgrade my DEChub 900 from firmware V3.1 to
V4.0. I've installed the new Consolidated Firmware kit, and have
installed HUBwatch V4.0, and have added in my DEChub 900. I'm doing
all this on Digital UNIX, by the by.
I've configured the DEChub 900 with an IP address, and have also
designated a DECbridge 900MX as it IP services module. I have not
configured this DECbridge with its own IP address. Must I do that, in
order for HUBloader to upgrade the DEChub 900?
Thanks!
tl
|
| 2110.19 | Don't need own IP address | NETCAD::FORINO | | Wed Jun 07 1995 15:50 | 6 |
| Re 18.
No - you do not have to give the DECbridge its own IP address.
Just use the IP address of the DEChub 900.
John
|
| 2110.20 | Completeness | NETCAD::FORINO | | Wed Jun 07 1995 15:53 | 8 |
| Re. 17.
The DCF kit is a complete kit of all the firmware that can be
upgradable whether the upgrades uses MOP or TFTP. So for the sake
of completeness there are entries in the dcffiles.dat that HUBloader
would not use - for the MOP loadable devices.
John
|
| 2110.21 | See note 2114.5 | NETCAD::FORINO | | Thu Jun 22 1995 19:20 | 4 |
| re .10
Would note 2114.5 help solve your problem?
John
|