🚀 go-pugleaf

Path: elroy!steve
From: steve@elroy.Jpl.Nasa.Gov (Steve C. Carpenter)
Newsgroups: mod.computers.vax
Subject: VAX CDD installation problems
Message-ID: <3365@elroy.Jpl.Nasa.Gov>
Date: 16 Mar 87 23:05:44 GMT
Distribution: usa
Organization: Image Analysis Systems Grp, JPL
Lines: 60



	Are there any VMS System Managers that might have 
expertise with CDD problems?  The effect of the problem is
access violations when CDD versions 3.1 and up are installed
on my VMS 4.x machine (11/780) during the IVP.  The IVP simply
looks to see if CDD$EXAMPLES exists and then aborts.  The
cause is yet to be known.  The stack dump reports the PC as
28887, the reason mask=01 and the PSL as 3c00000...which is
referencing a non-existent or protected page.

1- I have tried different CDD media.

2- I have reinstalled earlier versions back to 2.3 and up through 
3.1 and it dies at 3.1.  

3- I have verified the microcode for changes between VMS 3.7 and 
VMS 4.2.  I even copied VMB.EXE from my VMS 4.0 distribution tape.

4- I have looked for bad images using ANALYZE/IMAGE and everything
looks good.  

5- I have run CDDV to verify the CDD.DIC file and it is ok.  I even 
did an ANALYZE/RMS on CDD.DIC and it is ok.

6- I have verified executable versions numbers within INSTALL.

7- I do not have FMS, DBMS or anything that would require large
enqlms.  I even increased my lock ID table parameters within authorize
and sysgen to some large value, but that didn't help.

8- I increased my system page file, the SYSGEN virtualpagecnt and 
authorize parameters to 300000 (MAX), but that did nothing but extend 
the blowup_time to a few seconds (though it did work some of the time 
but only once or twice and usually right after a reboot).  I also made
sure the system page file was contiguous.

9- I have eliminated SYSGEN parameters and other layered
software products suspicions by installing a new VMS 4.4 from 
scratch and upgraded to VMS 4.5.  There are ample global pages
and global sections.

10- I have even booted from startup.min to eliminate any hardware 
problems (which is really farfetched anyways).  

11- I made sure I used the system account which has all privs including
BYPASS and has no symbols defined. 

12- And CDD$DICTIONARY is pointing in the correct place - SYS$SYSTEM:.


	The only real clue is that CDD 3.1 is designed for VMS 4.x
and CDD 3.0 is the only version that will work on my system.  Any 
suggestions will be greatly appreciated.



		Steve Carpenter
		...!seismo!cit-vax!elroy!steve
		elroy!steve@csvax.caltech.edu