SCOPE/Hustler Initial Deadstart

Getting SCOPE/Hustler running on a completely new, uninitialized system is a painstaking multistep affair.  This document describes exactly how to do it.  And better yet, at the bottom of the page are links to preinitialized disk images for DtCyber.  Using these will make it unnecessary to do your own initial deadstart.

Important:  Deadstarting SCOPE/Hustler, even with properly initialized disk packs, still requires a deadstart tape image.  Unfortunately, the deadstart tape images we have cannot be distributed freely, due to copyright restrictions.  Therefore, the information on this page is pretty worthless to everyone except those few who have received permission to use CDC software from the copyright holders.

Multiple deadstarts

Initializing SCOPE/Hustler on an empty system requires several special deadstarts.  After you have done these deadstarts once, you should never have to do them again on your PC: normal deadstarts should suffice.

The philosophy behind what we are doing is described by Ken Hunter on his Hustler Startup page on the ControlFreaks TWiki.  (Unfortunately, this site is password-protected.)  The document you are reading now is for people who are more interested in getting SCOPE/Hustler installed than in understanding the process.

In the following walkthrough, characters you type are in the left column, and responses are on the right.  (I have not included every word of the response screens.)  All entries are terminated with the Enter key.  The explicit word "Enter" means to press the Enter key on an empty line. 

First deadstart

This is known as a Systems Initial Deadstart.

You type SCOPE/Hustler displays
  FL IN CPU 0 WAS ZERO
Enter  
  DUMP/DIAGNOSTIC CONTROL
1.N
2.N
Enter
 
  main deadstart screen (no title)
1.N
3.C
Enter
 
  WARNING COLDSTART OPTION SELECTED
45=06140127555555555555
GO
 
  NO LABEL ON DISK PACK. TYPE -NEWLBL- TO LABEL
NEWLBL  
  DO YOU WANT TO USE THE DEFAULT INITIALIZING SEQUENCE
YES  
  NO LABEL ON DISK PACK. TYPE -NEWLBL- TO LABEL
NEWLBL  
  - LABEL INITIALIZATION -
DEV15
ALL (I am not sure that ALL is really implemented, though.)
  NO LABEL ON DISK PACK. TYPE -NEWLBL- TO LABEL
NEWLBL  
  NO LABEL ON DISK PACK. TYPE -NEWLBL- TO LABEL
NEWLBL  
  NO LABEL ON DISK PACK. TYPE -NEWLBL- TO LABEL
NEWLBL  
  NO LABEL ON DISK PACK. TYPE -NEWLBL- TO LABEL
NEWLBL  
  - LABEL INITIALIZATION -
DEV15
ALL  
  INITIALIZING COMPLETED
NOW DEADSTART REGULAR TAPE

Second deadstart

This is known as an Operations Initial Deadstart.

You type SCOPE/Hustler displays
  FL IN CPU 0 WAS ZERO
Enter  
  DUMP/DIAGNOSTIC CONTROL
1.N
2.N
Enter
 
  main deadstart screen (no title)
1.N
3.C
Enter
 
  WARNING COLDSTART OPTION SELECTED
45=20060450200603555555
GO
 
  DO YOU WANT TO USE THE DEFAULT INITIALIZING SEQUENCE
YES  
  - LABEL INITIALIZATION -
DEV15
WR  
  PFD/RBTC INITIALIZATION (this takes a while)
- LABEL INITIALIZATION -
DEV33
WR  
  - LABEL INITIALIZATION -
DEV34
WR  
  - LABEL INITIALIZATION -
DEV35
WR  
  - LABEL INITIALIZATION -
DEV36
WR  
  PFD/RBTC INITIALIZATION  (this takes a while)
On my Athlon 64 2 GHz, the PC does about 500 KB/sec disk I/O during this time.

INITIALIZING COMPLETED
NOW DEADSTART REGULAR TAPE

Third deadstart

The third deadstart is almost the same as the deadstarts you'll normally do, but it also creates an authorization file.

You type SCOPE/Hustler displays
  FL IN CPU 0 WAS ZERO
Enter  
  DUMP/DIAGNOSTIC CONTROL
1.N
2.N
Enter
 
  main deadstart screen (no title)
1.N
2.A
3.C
Enter
I'm not sure the 2.A is necessary
  WARNING COLDSTART OPTION SELECTED
GO  
  Now you see several screens in succession:
PFD/RBTC CHECKING - this takes a long time.
Eventually you see Mickus Mouse briefly.
PRELOADING
SYSTEM LOADING - this takes a long time
ENTER DATE AND TIME
DATE 01/28/96
TIME 18.41.00
 
  As soon as you enter the time, the X and B displays come up.
Control point 3 is running LOADAF and on the B display it says:
NO SEQUENCE NUMS,LOAD BY HAND.
3.GO  
  Control point 3 says NEED ( AFDMP ) LBL 1600
3.ON SWITCH 1
3.DROP
 
  The job at control point 3 reprieves, catalogs
MSU AUTHORIZATION FILE, and quits.

Normal deadstarts

Subsequently, you can deadstart like this:

You type SCOPE/Hustler displays
  FL IN CPU 0 WAS ZERO
Enter  
  DUMP/DIAGNOSTIC CONTROL
1.N
2.N
Enter
 
  main deadstart screen (no title)
1.N
Enter
 
  Now you see several screens in succession:
ECS QUEUE PARTITION VALIDATION
PFD/RBTC CHECKING - this takes a long time.
Eventually you see Mickus Mouse briefly.
PRELOADING
SYSTEM LOADING - this takes a long time
ENTER DATE AND TIME
DATE 01/29/96
TIME 09.40.00
  As soon as you enter the time, the X and B displays come up.
Control point 3 is running LOADAF and on the B display it says:
NO SEQUENCE NUMS,LOAD BY HAND.  
After a few deadstarts, this file gets created and you don't have to deal with this step.  Possibly submitting a job causes the file to be created.
3.GO  
  LOADAF exits
AUTO.
ATTENDED.
OFFAAF.
OFFADF.
 

Downloadable files

If you use the files below, you don't have to do an initial deadstart, and hence can ignore everything that's written above.

cyber.ini is the initialization file I used.  It assigns only those disk packs that are used by the usual SCOPE/Hustler deadstart tape, sys398e.tap.  The deadstart panel specifies that this is machine 0, the CYBER 750.  (On this deadstart tape, FREND turned off for machine 0 to avoid problems caused by FREND not being implemented yet in the released version of DtCyber.)  To start DtCyber with this configuration, type: dtcyber cyber.hustler

disks-after-third-ds.zip (11MB). is the six disk pack container files used by cyber.ini, zipped.  It unzips to 806 MB.  This should be unzipped in the disks subdirectory from where you run dtcyber (assuming you use the above cyber.ini).

cm-ecs-after-third-ds.zip (0.5 MB) is the msuds.cm and msuds.ecs files that contain CM and ECS.  Unzip these into the same directory as cyber.ini.

Back to main page

/mrr  28 January 2006  Last updated 21 Sep 2010 10:31:12 AM