| Try the READ_ME.TXT file. I have pulled the hardware, ULTRIX, VMS, and
Windows sections. This has pointers to the latest kits and also docs.
If you are looking for HUBwatch 1.1, look at VMS_LAUNCH.TXT or
ULTRIX_11.TXT Should be the same file.
***HARDWARE: DECagent, DECbridge, DEChub in general
AGENT_MTBF.TXT= MTBF of DECagent 90
# AGENT_LOAD.TXT= How to load current micro-code on agent
AGENT_MANUAL.PS= DECagent 90 manual
AGENT11_MANUAL.PS= Preliminary 1.1 manual
AGENT_SALES_UPDATE.TXT= See MSU_SALES_UPDATE.TXT for V1.0 of agent
AGENT.SPD= SPD for DECagent 90 V1.0 firmware
AGENT11.SPD= Draft V1.1 SPD
APPLETALK.TXT= AppleTalk protocol numbers for bridge filtering
# BRIDGE_LOAD.TXT= How to load new micro-code on bridge
# BRIDGE_NDU.PS= How to load the DECbridge 500 using DOS NDU. The 90 is
the same, except the "/N{o Management}" switch is required.
DEMO_HUB.TXT= location of a hub on Easy Net that can be managed remotely
HOW_AGENT_WORKS.PS = Diagram of how agent translates protocols. Most customers
ask this question. Also picture of how DEC does management vs
competition
# NOBRIDGE_SALES.TXT= Sales update for version of DECagent that does not need
bridge
# SEEDS.DIS= who has agent seeds
# TOKEN.TXT= overview of token ring modules and their management
WHAT_CAN_BE_MANAGED_ON_REPEATERS.TXT
***ULTRIX: HUBwatch for ULTRIX 1.1 and HUBwatch for MSU 1.0
# ULTRIX20_SALES.TXT= see VMS20_SALES.TXT. HUBwatch for DEChub 900 article.
# ULTRIX_11.TXT= How to load HUBwatch for ULTRIX 1.1
# ULTRIX_11.SPD= Preliminary SPD (&SSA) for HUBwatch for ULTRIX 1.1
# ULTRIX_11_MANUAL.TXT= Pointer to 1.1 Hyperhelp files (main source of
documentation) and installation instructions.
ULTRIX11_SALES_UPDATE- see VMS_SALES.TXT
MSU_MANUAL.PS= HUBwatch for MSU (now ULTRIX) overall manual
MSU_SERVER_MANUAL.PS= HUBwatch for MSU terminal server management manual
MSU_REPEATER_MANUAL.PS= HUBwatch for MSU repeater management manual
MSU_BRIDGE_MANUAL.PS= HUBwatch for MSU bridge management manual
Also see MSU_RELEASE_NOTES.PS for release notes.
MSU_RELEASE_NOTES.PS- V1.0 release notes, including MCC launch instructions.
MSU_SALES_UPDATE.TXT= Sales Update article for DECagent 90 and HUBwatch for MSU
MSU.SPD= HUBwatch for DECmcc MSU SPD
***VMS: HUBwatch for VMS 1.1 and 2.0
#VMS20_SALES.TXT= Start of HUBwatch for DEChub 900 article.
#VMS_LAUNCH.TXT= how to load HUBwatch for OpenVMS 1.1
#VMS MANUALS= see ULTRIX_11_MANUAL.TXT
#VMS_SALES.TXT = VMS and ULTRIX 1.1 sales update
#VMS.SPD= Draft VMS SPD
***WINDOWS: HUBwatch for Windows 1.0
DEC.EXE= HUBwatch for Windows- old demo program. Read
WINDOWS_DEMO_INSTRUCTIONS.TXT for instructions.
MAPS: Background maps for HUBwatch for Windows can be found on the .MAPS
subdirectory. Contact EMDS::SEAVER if you want more.
WINDOWS BACKGROUND MAPS can be found on the .MAPS subdirectory:
EMDS::$1$DUA4:[SMART_HUB90.MANAGEMENT.MAPS]. Contact EMDS::SEAVER
if you want more.
WINDOWS_DEMO_INSTRUCTIONS.TXT= instructions for running HUBwatch for
Windows demo.
# WINDOWS_MANUAL.PS= Draft HUBwatch for Windows manual- THIS IS 52K blocks!!!
WINDOWS_SALES.TXT= Sales UPdate for HUBwatch for Windows 1.0
# WINDOWS_SETUP.TXT= How to load working version of HUBwatch for Windows.
If you can get PING to work, you are thru the difficult part.
This is much more difficult to set up than the demo found in DEC.EXE.
# WINDOWS.SPD= Draft HUBwatch for Windows SPD
|
|
Assuming that this is the latest version of HUBWATCH for VMS, I get a
file protection violation trying to pull the savesets. If it is old,
could someone point to a more recent version or look into the error.
Thanks,
dave
SLINK::DKB0:[HUBWATCH_T118]HUBWATCH_T8011.A;1
SLINK::DKB0:[HUBWATCH_T118]HUBWATCH_T8011.B;1
|