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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

446.0. "a200 won't boot after upgrade to v7.1" by AXCL04::LAGIOIA (We do ...the best) Thu Apr 10 1997 12:31

    Hello!
    
    Our customer has updated their axp's from openvms v6.2-1h3 to v7.1.
    without problems.
    
    When booting satellites a3000 a200, he can see these problems:
    
    1) a3000 decwindows motif doesn't start during the boot. The customer
    has to insert in the systartup_vms "$ submit sys$startup:decw$startup"
    
    2) a200 don't want boot. They produce a bugcheck procgone. They do not
    have decram.
    
    The problem n�2 is very urgent and we need an answer. the customer is
    down. For the problem n�1 he can wait an answer.
    
    Thanks for any help
    Domenico 
T.RTitleUserPersonal
Name
DateLines
446.1Notes Is Not For "Urgent" Problems -- Use IPMTXDELTA::HOFFMANSteve, OpenVMS EngineeringThu Apr 10 1997 12:5440
    
:    1) a3000 decwindows motif doesn't start during the boot. The customer
:    has to insert in the systartup_vms "$ submit sys$startup:decw$startup"

   This is best asked in the DECwindows conference.

   There is no need to manually start DECwindows.

   What DECwindows version?

   The DECwindows Motif patch kit -- for V1.2-3 or V1.2-4 -- should be
   acquired and installed, if this has not already done so.
    
:    2) a200 don't want boot. They produce a bugcheck procgone. They do not
:    have decram.

   There is nowhere near enough information here to even begin to try
   to resolve this problem...

   You will need to check the PALcode version, and confirm that it is
   a version that is supported with V7.1.  You will need to indicate
   how far through the system bootstrap the system has gotten before
   the bootstrap.  You will need to try to localize cause of the problem,
   if this is occuring somewhere in the system startup.  You will need to
   obtain the CLUE output from the crashdump -- if a dump is written --
   and use the information in note 233.* to use CANASTA to determine if
   this problem is already known, and to find -- if any -- suggestions,
   fixes, or workarounds.  You will need to determine if all installed
   products are compatible with V7.1.  You will also need to include a
   copy of the crashdump with the IPMT (if the dump is available), if
   you cannot determine the cause of the problem and resolve it...
    
:    The problem n�2 is very urgent and we need an answer. the customer is
:    down. For the problem n�1 he can wait an answer.

   "Urgent" means "log an IPMT".  *Not* Notes...

   Hopefully, the customer followed the directions around performing the
   system BACKUP before performing the OpenVMS upgrade...
    
446.2FoundAXCL04::LAGIOIAWe do ...the bestMon Apr 21 1997 05:438
    Hello!
    In fact the customer has modified before the upgrade the modparams.dat 
    giving a high freegoals, and has changed others system parameters without 
    checking by running autogen.
    
    Thanks
    Domenico