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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1819.0. "Need 5.3 and 2.0 help!" by WFOFAC::BILL () Thu Nov 30 1989 13:16

    
    
    I just installed the new VMS 5.3 and DECwindows 2.0.  It installed
    fine but I have lots of questions.
    
    1) I do not know if this is apropriate to ask here, but I will give
    it a shot.  My vax-vms license is not installed.  Where can I get
    the PAK that will work for this?  The PAK'S and VTX do not work
    with it, it comes up with "Checksum not valid" when I try to register.
    
    2) Will decwindows work with a Microvax with vcb02 and 8 Plane graphics
    modules installed?  If so, what configuration do I need in the file
    DECW$PRIVATE_SERVER_SETUP.TEMPLATE to make this work?

                                                         
    I have a microvax II with a MAyfair I cpu, and 16 meg of memory.
    I also have the vcb02 graphics set (m7169, and 2 m7168's).  I am
    running 1 vr290 monitor and 1 mouse.
    
    Any configuration help and or pointers to other notes files would
    be much appreciated.
    
    Thanks in advance.
T.RTitleUserPersonal
Name		DateLines
1819.1QUARK::LIONELFree advice is worth every centThu Nov 30 1989 15:215
I have had no problem with the PAK given by VTX.  But you should rename or
delete SYS$SYSTEM:LMF$SYSTEM.LDB before rebooting, as it will have an old
PAK in it.

			Steve
1819.2WFOFAC::BILLThu Nov 30 1989 16:465
    
    
    Thank you for the info.  I will try this suggestion.
    
    -Bill
1819.3WFOFAC::BILLThu Nov 30 1989 18:3420
      
    
    .1's reply did not work, it still said "checksum error".  I went
    to vtx to get another PAK and installed that one and it worked.
          
    Now when I start the Microvax with the VCB02 module set in the bus,
    I get a message that says the following:
    
    "License was not loaded for VAX-VMS"
    "Attempted usage exceeds active license limits"
    "Dec VAX-VMS usage not authorized on this node"
    
    This happens only when I boot with the vcb02 module set in the bus.
    When I boot without it, the license loads fine.
    
    Do I need some other license to be installed for the VCB02 module
    set?
    
    Any help will be appreciated.
1819.4STAR::MCLEMANJeff McLeman, VMS DevelopmentFri Dec 01 1989 07:363
Well, it sounds like you have the multi-user cpu in you WS. And the license
is getting upset, because you have a WS configuration. Have you tried
a single use cpu? (VAXserver/VAXstation cpu)
1819.5WFOFAC::BILLFri Dec 01 1989 09:419
    
    I tried it with a KA630 microvax cpu and it still fails.  This config
    SHOULD work.  What licenses do I need to make this work?  I know
    of a few configurations like mine that run the same software.
                                                            
    I tried it on a vaxstation 2000 and it did not error.  I would like
    to use it on a microvax since I have more memory there.
    
    Any suggestions??
1819.6Try a KA650-BA instead of a KA650-AAJGL::JLENIHANByte TwiddlerFri Dec 01 1989 10:5117
    
    FWIW ...
    
    I had a problem something like what seems to be happening to you...it
    was also a converted GPX with a Mayfair CPU. Certain strange things
    seemed to happen ..for instance black patches would appear on the
    Graphics screen and I would get random problems mounting disks with the
    RQDX controller. It turned out to be the following...
    
    If you put a multi-user CPU (KA650-AA) in with VCB02 boards on GPX, the
    whole configuration seems to be unstable. I had ordered a KA650-BA but
    because of bad markings had been shipped a KA650-AA. On switching the
    boards....everything worked perfectly. One of the ways that this
    problem manifested itself is that the system stalled halfway when it
    was asked to load all the MDM Diagnostics...
    
    � J.
1819.7WFOFAC::BILLFri Dec 01 1989 11:594
    
    Thanks for the advise, I will try anything at this point.
    
    -Bill