[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

615.0. "Hubwatch displayed on VXT 2000+, memory required?" by KERNEL::LLOYDA (Don't worry... Be Happy ;^)) Thu Jan 13 1994 12:09

    Hi,
    
    A customer of mine is running Hubwatch V2.0 from a VAX 4000 with 128Meg
    of memory being displayed onto a VXT 2000+ with 4 meg of memory.
    
    It appears that the map displays o.k. but when a module is selected he
    gets insufficient resource errors.
    
    The question is... How much memory do I need for my VXT 2000+ to properly
    display Hubwatch ? Clearly 4 meg isn't enough... how about 8meg or 10
    or even 14 meg ? The SPD states memory requirements on the VAX not the
    VXT.
    
    Anyone have any ideas ?
    
    Alan Lloyd.
    TSC Basingstoke.
T.RTitleUserPersonal
Name		DateLines
615.1Don't know, but would like to know.SLINK::HOODI'd rather be surfingThu Jan 13 1994 12:205
If you find out, can you please post the answer.

Thanks,
Tom Hood
HUBwatch
615.2:*)KERNEL::LLOYDADon't worry... Be Happy ;^)Thu Jan 13 1994 12:369
    Tom,
    
    I had hoped you could tell me !!! I suppose I'll have to go and dig out
    a VXT 2000+ and try it all out on (I suppose I was being lazy).
    
    If anyone else has it running please let me know.
    
    Alan.
615.310 megs maybe?DV780::SMITHRThu Jan 20 1994 09:379
    If it is any help, oone of my customers is running Hubwatch using the
    VXT2000+ with 10 megs of memory.  When he ordered the VXT he was
    informed that 10 megs was minimum for most windowing applications.  I
    don't know how true this is, but we don't have any problems running
    Hubwatch.
    
    For what it is worth,
    
    Rich
615.4solvedKERNEL::LLOYDADon't worry... Be Happy ;^)Thu Jan 20 1994 13:188
    Hi,
    
    Thanks for the reply... it transpires that the customer is using a VAX
    based load on a VXT with only 4Meg of memory. The minimum supported
    amount of memory for a host based load is 10 meg. 4 Meg will work if he
    loads of an infoserver.
    
    Al.
615.5acc vio with 18 meg.COMICS::WARDJThu Jan 27 1994 13:2514
    Hello,
    
    I have a customer with a vxt 2000+ (18meg) and he is getting an access
    violation when running hubwatch.
    
    He creates a Lat x session, fires up hubwatch, double clicks on a
    module and then gets the acc vio.
    
    Anyone got any ideas on what I should be looking for?
    
    Thanks 
    
    Jon
615.6SLINK::HOODI'd rather be surfingThu Jan 27 1994 13:489
Does it crash on all their x terminals?  Does it crash if display is set
to a workstation somewhere?  

If it's repeatable, then please submit a QAR, with as many details about the
display and hub hardware as possible.  Also include instructions on how to
re-create the problem.

Tom Hood
HUBwatch
615.7VASSAR::WADENetwork Systems SupportWed Feb 09 1994 11:215
    re .6
    
    	I'm pretty sure that this customer is running HUBwatch for VMS
    	V1.1.  Is this something that is clearly fixed in V2.0?
615.8Something to keep in mind...SLINK::HOODI'd rather be surfingWed Feb 09 1994 11:2915
The fine print:
--------------
Please keep in mind the X-terminals are not officially supported by
HUBwatch V1.1 and V2.0.  They are *not* listed in the SPD for HUBwatch.  
What this means is that HUBwatch was not tested on them.  While many people 
seem to be able to run with them, it is not a guaranteed configuration.

Otherwise:
---------
V1.1 is pretty old [ by our standards ;-) ].  V2.0 fixed numerous bugs
from 1.1.  As Bill suggested, try the newer version.


Tom Hood
HUBwatch