diff --git a/CDC1700/CDC1700-MSOS.txt b/CDC1700/CDC1700-MSOS.txt index f1e17379..b0d46738 100644 --- a/CDC1700/CDC1700-MSOS.txt +++ b/CDC1700/CDC1700-MSOS.txt @@ -39,6 +39,68 @@ converters/cosy 3. Installation +3.1 Quick Installation Using Scripts + + There are 2 scripts provided as part of the distribution for quickly +installing and running MSOS 5.0: + + - msosInstall.simh + + This script can be used to install MSOS 5.0 on a 1733-2 disk unit + (2 logical drives) from the standard installation tape as described + above. To perform an installation change to the directory you want + the install the install to occur in and copy MSOS5_SL136.tap to this + directory. If you want to install from a different tape, its name + can be passed on the command line: + + cdc1700 msosInstall.simh install.tap + + Start up the CDC1700 simulator using msosInstall.simh as the + configuration. The script will automatically supply the date of + installation for the initializer and the date/time for MSOS 5.0 + when requested. The time, month and day will be set to their + current values from the host system. The year will be set to a + 20th century year which has the same calendar as the current year + (MSOS 5.0 is not Y2K compliant). + + While running this script the O/S will reboot twice and a log of + installation will be left in MSOSinstall.lpt. The final section of + the installation will be to run the installation verification + procedure. This will generate 3 errors: + + 1. Partition set up error + + The verification procedure checks that partition 0 starts + below 0x8000. All of the installation tapes on bitsaver.org + that I've checked have partition 0 starting above 0x8000. + + 2. File Manager sequential file error + + The installation procedure only creates disk images for a + single disk unit. The O/S is configured with 4 disk units + and a drum. This procedure will attempt to write to all + direct-access configured in the system and so will fail. + + 3. Fortran formatted I/O error + + This error has not been investigated. + + - msosRun.simh + + Once installation is complete, this script may be used to run the + resulting system. It will use the same disk images created by + msosInstall.simh and will create a unique file for line printer + output based on the current date and time. Like the installation + script it will set the date/time for MSOS 5.0 to the current values + from the host system with the year set to a 20th century year with + the same calendar as the current year. As part of the start up + sequence it will patch MSOS so that the 1728 Card Reader/Punch and + 1752 Drum are not accessible to programs since the simulator has + no support for these devices. + + +3.2 Full Installation By Hand + Installation of MSOS 5 occurs in 2 phases: - Phase 1 diff --git a/CDC1700/msosInstall.simh b/CDC1700/msosInstall.simh new file mode 100644 index 00000000..8c913249 --- /dev/null +++ b/CDC1700/msosInstall.simh @@ -0,0 +1,59 @@ +# Script to install MSOS5 onto cartridge disks +# Requires: +# Installtion tape Default is MSOS5_SL136.tap which can +# be copied from bitsavers.org. This +# can be overridden by specifying the +# installation tape on the command line: +# +# cdc1700 msosInstall.simh install.tap +# +# Creates: +# MSOS5-A.dsk and MSOS5-B.dsk installation disks +# MSOSinstall.lpt installation log +# +set env CDD0=MSOS5-A.dsk +set env CDD1=MSOS5-B.dsk +set env MT0=%2 +if "%MT0%"=="" set env MT0=MSOS5_SL136.tap +set env LPT=MSOSinstall.lpt +set cpu instr=basic +set cpu mode65k,64k +set throttle 50% +set mt type=1732-3 +set lp type=1742 +att lp %LPT% +att cdd0 %CDD0% +att cdd1 %CDD1% +att -r mt0 %MT0% +set env DATE1=%DATE_MM%/%DATE_DD%/%DATE_19XX_YY% +set env DATE2=%DATE_MM%%DATE_DD%%DATE_19XX_YY% +echo MSOS 5.0 Installation +echo +echo Requires %MT0% in the current directory. +echo Creates %CDD0%, %CDD1% and %LPT% in the current directory. +echo +echo This script will set the installation date to %DATE1% +echo (This has the same calendar as %DATE_YYYY%). +echo +echo This script will start the installation and eventually boot MSOS 5.0. +echo The date/time will be set to the current time on %DATE1% and the batch +echo system will be initiated to complete the installation. Following +echo installation, MSOS 5.0 will be rebooted, the date/time will be set and +echo the installation verification procedure will be run. It will detect +echo 3 errors: +echo +echo 1. Partition setup error +echo 2. File Manager sequential file error +echo 3. Fortran Formatted I/O error +echo +expect "DATE MM/DD/YY \r\r\r\r\n" send "%DATE1%\r"; c +expect -p "DATE/TIME MMDDYYHHMM \n\r\n" send "%DATE2%%TIME_HH%%TIME_MM%\r"; c +expect "Q\r\r\r\r\n" send "*i,3\r"; c +expect "Q\r\r\r\r\n" send "*V\r"; c +expect -p "YOU MAY AUTOLOAD" step 100000; autoload cdd; go 0 +expect "SET PROGRAM PROTECT \r\n" set cpu protect; c +expect -p ":00 " send after=100000,"\007"; c +expect "MI\r\n" send "*BATCH\r"; c +expect "MI\r\n" send "VERIFY\r"; c +expect "TESTS COMPLETE." step 100000 +boot mt0 diff --git a/CDC1700/msosRun.simh b/CDC1700/msosRun.simh new file mode 100644 index 00000000..58023d91 --- /dev/null +++ b/CDC1700/msosRun.simh @@ -0,0 +1,28 @@ +# Script to start up MSOS 5.0 previously installed via msosInstall.simh +# Requires: +# MSOS5-A.dsk and MSOS5-B.dsk installation boot disks +# Creates: +# %DATETIME%.lpt unique LPT output file for this run +# +# MSOS 5.0 date/time will be set to the current time, month and day. The +# year will be set to a 19XX year with the same calendar as the current year. +# +set env CDD0=MSOS5-A.dsk +set env CDD1=MSOS5-B.dsk +set cpu instr=basic +set cpu mode65k,64k +set throttle 30% +set mt type=1732-3 +set lp type=1742 +att lp %DATETIME%.lpt +att cdd0 %CDD0% +att cdd1 %CDD1% +set env DATEANDTIME=%DATE_MM%%DATE_DD%%DATE_19XX_YY%%TIME_HH%%TIME_MM% +# +# The following command will patch out unimplemented devices (1728 card +# reader/punch and 1752 drum) +# +expect "SET PROGRAM PROTECT" set cpu protect; d 056D 0649; d 057E 0649; d 0589 0649; d 057C 0649; c +expect "DATE/TIME MMDDYYHHMM \n\r\n" send "%DATEANDTIME%\r"; c +autoload cdd +run 0