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

Conference clarid::dasc

Title:DASC Tool, Problems & Suggestions
Notice: Latest kit: see note 85.0
Moderator:CLARID::KREYER
Created:Mon Mar 26 1990
Last Modified:Fri May 23 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:208
Total number of notes:848

206.0. "DASC 4.1 Report Problem with 10240.00Mb in Turbo Laser" by COLES1::AHRENS () Tue May 20 1997 20:14

    The Node Information of the DASC$REPORT.TXT has not the Correct
    info
    
            -- Node Information --
    
    Node Name:              MSDP09
    CPU Type:               AlphaServer 8400 Model EV56/440
    Active/Configured CPUs: 8/8
    Memory Size:            ???? Mbytes
    OS Version:             VMS V6.2-1H3
    Booted from:            DSA0:[SYS9.]
     
    The system has 10 GByte (10240.00Mb) Main Memory. I thing the memory
    size is to large for the info.
    
    The DASC Version is V4.1-1. Is a newer version on the EASY Net.
    
    regards R�diger Ahrens (Digital MCS)
T.RTitleUserPersonal
Name		DateLines
206.1A few options...CLARID::KREYERAndre KREYER, Sophia Antipolis (FR)Wed May 21 1997 09:4317
>    Memory Size:            ???? Mbytes
	As you found out, DASC only cares about 4 characters for the
	memory size field (like 9.999 TeraBytes max).
	
	DASC V4.1-1 is the current official kit. Now there are 2 solutions
	that I can offer:
	1) I can build a modified DASC$MAIN_A.OBJ that would contain the
	   required fix.
	2) You could use a pre-field test version of V5.0 which would
	   contain that fix.
	The new limit will be 6 digits or 999 TeraBytes. If that seems
	unreasonable, please let me know...

	Whichever solution you are interested in, please let me know.

							.Andre.