
CONVERGENT TECHNOLOGIES

RELEASE NOTICE FOR
1.0 Standard SoftwareII (SAA2000)

Revised June 26, 1986

SECTION   TITLE	PAGE
	1.0	Description of Programs 	 2
	2.0	Changes from Prior Version 	 6
		2.1  SPRs Closed in This Release 	 6
		2.2  Changes from Prior Release 	 8
	3.0	Contents of Distribution Diskettes 	 14
	4.0	Software Installation 	 21
		4.1  Required Hardware 	 21
		4.2  Theory of Installation 	 21
		4.3  Installation Procedures 	 23
		4.4  Entering Disk Drive Parameters
		     and Bad Spot Information 	 41
	5.0	System Software Compatibility 	 46
		5.1  Workstation Environment 	 46
		5.2  SRP Environment 	 46
	6.0	Required 	 47
		6.1  Files for NGEN Bootable Media 	 47
		6.2  Files for SRP Bootable Media 	 48
	7.0	Hardware Information 	 49
		7.1  Hardware Configurations Supported 	 49
	8.0	Resource RequirementsUtilization 	 50
		8.1  Memory RequirementsUtilization 	 50
		8.2  Disk RequirementsUtilization 	 51
	9.0	Supplementary Information 	 52
		9.1  Native Language Support 	52
		9.2  Creating a Bootable Backup Floppy 	 54
		9.3  Merged SRP and Workstation 
		     Utilities 	 56
		9.4  Miscellaneous Information 	 58
	10.0	Documentation Updates 	 60
	11.0	Known Errors and Omissions 	 65

NOTE
This Release Notice contains installation procedures for CTOSII Operating Systems and Standard SoftwareII.  The bulk of this Release Notice, however, covers ONLY Standard SoftwareII.  Detailed Operating System information is contained in a separate Release Notice for the CTOSII Operating System.

1.0	DESCRIPTION OF PROGRAMS
This Release Notice describes Standard SoftwareII version 1.0.  This section and the sections that follow provide a description of the product, contents of the Distribution Diskettes, installation procedures, and other information pertinent to this release of Standard SoftwareII.
Standard SoftwareII version 1.0 is intended for use on NGEN's and SRP's.  There is no installation of Standard SoftwareII provided for AWS's or IWS's directly.  However, a Remote update is provided to update any master  SRP, NGEN, IWS, or AWS.  (The current release of Standard Software for AWS's and IWS's is 10.2 with a 10.3 Update.)
Version 1.0 Standard SoftwareII Distribution Diskettes consists of: 
o	2 NGEN Initialization diskettes
o	1 SRP Qic Installation Tape
o	1 SRP Syquest Installation Cartridge
o	7 Standard Software Utilities diskettes
o	2 Software Development diskettes
o	2 NGEN Operating System diskettes 
o	2 SRP Operating System diskettes
o	3 Operating System Build diskettes 
{Version 1.0 Standard SoftwareII includes the following programs:
Assembler.run	System assembler
ATE.run	Asynchronous Terminal Emulator
BackupVolume.run	Disk volume archive utility}
Batch.run	Foreground batch processor
Bootstrap.run	System bootstrap utility
CheckConfig.run	NGEN XBus configuration reporter
ChgVolName.run	Disk volume name utility
ClusterStatus.run	Cluster status utility
CmdFileEditor.run	System command file editor
Command.run	System command file utility for adding a command
CreateConfig.run	Serial and parallel port configuration utility
CreateMsgFile.run	Utility for making a binary message file from text file
DebugFile.run	Run file or crash dump file debugging utility
DisableCluster.run	Utility for disabling cluster operation
Dump.run	Hexadecimal file dump utility
EditorII.run	Text editor
Exec.run	System command interpreter
Files.run	File listing utility
FloppyCopy.run	Floppy copy utility
Format.run	Formatted listing utility
InstallQMgr.run	Queue manager installation utility
InstallSpl.run	Printer spooler system service
IVolume.run	Disk volume initialization utility
LCopy.run	File copying utility
Librarian.run	System library utility
Linker.run	System linking utility
LInstall.run	Software installation utility
MathServer.run	Allows multiple programs to use the 80287 math coprocessor
PartitionStatus.run	Partition status utility
PLog.run	System errorstatus log reporter
Print.run	Printer spooler printing utility
QueueMgr.run	Queue manager
Restore.run	File archive restoration utility
ResumeCluster.run	Utility for resuming cluster operation
SelectiveBackup.run	File archive utility
SetDirectoryProtection.run
Directory protection utility
SetTime.run	Time utility
SignOn.run	User login utility
SpoolerStatus.run	Spooler status utility
SubCmd.run	Submit file invocation utility
Submit.run	Submit file processor
Sync.run	Allows an SRP JCL file to be synchronized on different boards
SyncStatus.run	Allows the user to monitor the synchronization of the boards on an SRP
SysInit.run	System initialization utility
UserFileEditor.run	User configuration file editor
VolumeStatus.run	Disk volume status utility
Version.run	Displays version numbers of run files
XBif.run	NGEN XBus system service
XC002Server.run	NGEN XC002 communications module system service
Wrap.run	Wraps data into object files

2.0	CHANGES FROM PRIOR VERSION
2.1	SPRs CLOSED SINCE STANDARD SOFTWARE 10.210.3
A513		LCopy ignoring password protection.
A1084		Separators in date on Signon screen are incorrect for international customers.
A1290		Specifying '[ptr]b' as the log file to Backup Volume cuases an error 905, no such queue.  (Fixed in 10.2)
A1389		Floppy copy command form incorrectly reflects defaults 
A1406		Plog shows an unlisted error type 65528 and cannot format this entry.
A1607		Swapper does not handle NEAR returns in overlays correctly.  Infinite loops occur.
A1703		The XC002 Server does not work correctly on a Singlepartition Operating System.  (Also A3016)
A1800		Librarian cannot properly handle large model objects produced by Fortran 86.
A1828		Wildcarding routines do not work correctly over CTNet.
A1831		An Iop master is shown as master version on an SRP system.  
A1834		Using the Files command with a wild card and an invalid password reports nothing.
A1835		Command File Editor returns Access Denied (status code 219) when attempting to write a file opened with mode read.
A1850		SetPartitionName works incorrectly on SRP when user number 0 is specified.
A1865		Using a function key to invoke a submit file will sometimes roport an erc 210.  Executive II 1.0 now opens a file longlived rather than shortlived.
A1879		IVolume incorrectly calculates the logical sector number of bad spots on Winchester drive.
A1915		Running ClusterStatus.run when the cluster is down sometimes results in a Debugger call
A1943		When installing a spooler at a workstion without a printer, the station locked up.
A1980		Nonwildcarded file names are not treated as an error condition in Files if they do not exist.
A1981		(also A1829, A3004) The Files command no longer gives a full (or partial) path when listing explicit files with details on.  The path portion of a file name is stripped when an explicit file name with a path is given, but appears when wildcarded file names are used. 
A2014		Signon fails when a Disable Cluster specifying a time limit has been done.
A2023		In programs using Communications Byte Streams, when CTS handshaking is used, receiving system does not drop RTS line before bufferfull condition; program terminates with erc 2346.
A2050		The List command does not report an error on files in the file list which are nonexistent.
A3007		When a PD001 (mouse) is connected, the debugger gets input on every mouse motion.  These events are treated as spurious keystrokes.
01566		MBackupVolume will not backup to a password protected volume.  Error 219 is returned.  
02046		ATE duplicates bytes when receiving files (F6 key).  Buffer pointers wrap around after 64K bytes received.
{02834		Installation of the 10.0 Queue Manager on an SRP dies with an erc 911 if the last line of the Queue.index file does not end with a new line character.} 
10023		Linker crashes with erc 27 if there are more than 18 libraries specified.
01171		MVolumeRestore and MVolumeBackup require a 2nd archive file when backuping up a cartridge that has been MIvolumed with the minimum parameters.  The MIvolume results in disk free space of 9730 blocks which exceeds the archive file size.
10183		When LCopy detects an input error, specifically a 203, the message is displayed requesting Go, Cancel, Finish or F1.  When the  file is made available, in this case the floppy was changed, and F1 is pressed, LCopy returns to the executive without copying the file, as if Finish was pressed.  If F1 is pressed agin (in the executive) to restart LCopy the file is sucessfully copied.  the F1 key in LCopy works as advertised for output errors, eg Erc 230.
2.2  CHANGES FROM STANDARD SOFTWARE 10.010.210.3
{A.	Loadable request utilities: In CTOSII, all loadable requests are contained in a single loadable request file, Request.sys, instead of in multiple Request.n.sys and MRequest.n.sys files.  Two new utilities, List Request Set and Make Request Set, can be used to create the merged binary request file from a simplified text file and to translate a binary file back into text form.  See the ExecutiveII Manual for more details on these two new utilities.}
{B.	Install command: Because of the change in loadable requests, there is now a new way to install applications software packages.  In the past, one could install a new package by inserting a diskette and submitting the file, [f0]<Sys>HdInstall.sub.  This is no longer allowed.

You must now use the Install command to install software.

The Install command invokes a series of submit files which have been specifically designed to update the proper loadable request file(s).  If the Install command is not used, an erc 31 will generally result when an attempt is made to use the new package.

The new Install command takes an optional parameter, the floppy drive from which to install.  If you are writing installation submit files, you can now check the first parameter for the device name.  The device name received will include the device brackets [ and ], e.g., [f0].}
{C.	Native Language Support: Many of the Standard SoftwareII run files have been modified for native language support.  Messages are contained in a separate file, ExecMsg.bin.  The corresponding text file, ExecMsg.txt contains comments which allow for easy editing andor translation.  The utility, Create Message File, is used to convert the text file into its binary form.  Use of Native Language Support is described in Section 9, Supplementary Information, below.}
{D.	EditorII:  A new text editor, EditorII, is provided.  This multiwindow editor is documented in the EditorII Manual.  AwsEditor.run, IwsEditor.run, Editor.run, and t1Editor.run can be safely deleted as EditorII.run completely replaces all previous versions of the Editor.  The command Edit may also be removed.

Note:  The old editor will not work on the new GC003 graphics module, you must use EditorII.}
{E.	Files command: The Files utility has been completely rewritten.  Files now displays a sorted list in multiple columns and also permits use of exclusionary wildcards.  See the ExecutiveII Manual for details.}
{F.	Merged SRP and workstation utilities: Utilities that formerly had separate run files for SRP and workstation environments have been merged.  For example, mCreatePartition.run is now called CreatePartition.run.  Details are discussed in Section 9, Supplementary Information, below, and in the ExecutiveII Manual.}
{G.	Ctos.lib: The diskette labelled Software Development Utilities 1 of 2 contains the CTOS library, Ctos.lib.  This library reflects a merge of the workstation and the SRP versions of Ctos.lib.}
{H.	Math Server: There is a new Math Server, MathServer.run.  It allows multiple programs to make use of the 80287 math coprocessor chip available on 80286 NGEN's.  The server is installed automatically by the Operating System at boot time.}
{I.	Assembler: The Assembler now supports the new instructions introduced with the Intel 80186 and 80286 processors.  See the iAPX 286 Programmer's Reference Manual for more details.}
{J.	Debugger: The Debugger, when running on a 286 NGEN with more than 1 Megabyte of memory, with PMOS installed allows debugging in protected mode.  Information of debugging in protected mode is contained in the Engineering Update for PMOS which is included in the CTOS Programmer's Guide.}
{K.	Background Batch: As of CTOSII 1.0, the Background Batch facility is no longer supported.  No new run files are supplied, and old versions will not work.  Foreground Batch is still supported.  See the CTOSII CTOSII CTOSII System Administator's Guide for details.}
{L.	Exec command table: The capacity of the Exec command table has doubled.  The Exec automatically doubles the space reserved for commands in the command file when it is necessary to use the larger file.}
{M.	Communications Nub:  The Comm Nub has been moved from Ctos.lib into the OS.  If a communication program is to run on CTOSII only, it is suggested that it be relinked with the new Ctos.lib as it results in smaller application code and faster performance.}
{N.	Linking Communications software: The 10.0 release of Standard Software introduced new Communications Byte Streams.  The details of these are documented in the obsolete Engineering Update for Standard Software 10.0.  The same documentation appears as the Communications Programming chapter in the CTOS Programmers Guide and the procedures are documented in the CTOS II Reference Manual.}
{	These documents discuss how to link a program if you want it to be used on preCTOS 10.0 versions of the OS.  This method of linking actually applies to CTOS versions before 9.4.}
{	In Standard SoftwareII versions 1.0, the defaults for linking have been reversed.  That is, by default, if you specify nothing on your link, your program gets communications code that is compatible back to CTOS 9.4.  To get compatibility with versions of CTOS before 9.4, you must now explicitly link with the Pre10 object modules.}
	{The following table summarizes the changes in placement of the communications modules:

Object Module	Old     	New	

CommStatus_Pre10	Ctos.lib	External
CommNub_Pre10	Ctos.lib	External
InitComm_Pre10	Ctos.lib	External
InitComm_Pre10Stub	External	Ctos.lib}
{O.	Sync and SynchStatus for the SRP:  Two new Utilities, SyncStatus.run and Sync.run are available.  These utilities allow you to build initialization JCL files on an SRP which synchronize the installation of servers on different boards.  Details can be found in the CTOSII System Administrator's Guide.}
{P.	Sys and SlvAdminAgents on the SRP: Multiple administrative agents are no longer supported.  If you wish to continue using SysAdminAgent.run and SlvAdminAgent.run from a prior release, you may do so, but they are entirely unsupported.} 
{Q.	Tape utilities: A great deal of work has been done on the tape utilities.  Refer to the CTOSII System Administrator's Guide for details.

a) All tape utilities for workstation and SRP have been merged.  This includes Tape Backup, Tape Restore, and Tape Selective Backup.  QIC tape on the SRP can be used to back up workstation files directly.  Multivolume Tape Backup, Restore, and Selective Backup work on the SRP.}

{b) In order to save disk space when installing Standard Software II on a cluster workstation, the tape run files are not copied and the commands refer to run files at the master.  If you wish, you can copy these run files to your local hard disk and use the Command File Editor to modify the run file names to refer to your local hard disk.}

{c) When using QIC tape on an NGEN, the tape utilities now attempt to use the local QIC drive(s) first.  If there is no local tape drive or it is in use, then the master's tape drive is used.  This is the reverse of previous releases of QIC tape software.}

{d) If you wish to use the Standard SoftwareII QIC tape utilities on a preCTOSII version of the OS, you must install the QicServer first.}

{e) The naming convention for the halfinch tape configuration files has been changed.  The files MWS>TapeConfig.sys and CWS>TapeConfig.sys are no longer used.  The new names of the type TapexyConfig.sys, where 'x' is the SRP board number or zero for IWS, and 'y' is the daisychain number starting with zero.}

{f) If you are at a cluster station with a QIC tape server installed and you want to use the half inch drive at the master, you must deinstall the local server first in order to use the master's tape drive.}
3.0	CONTENTS OF DISTRIBUTION DISKETTES
The Standard SoftwareII Distribution Diskette set is your master copy, and has been shipped writeprotected.  It should not be writeenabled, nor should it be used as a working copy.
{SRP QIC TAPE and SYQUEST:
SRPCp.sys	SRPSp.sys
SRPDp.sys	SRPTp.sys
SRPFp.sys	SysImage.sys

Bootstrap.run	mIvolume.run
ChgVolNamei.run	mIvolumei.run
CLI.run	QicErasei.run
Copy.run	RemoveDirectory.run
CreateDirectory.run	Restore.run
Delete.run	TapeBackupi.run
MakeBootTape.run	TapeRestorei.run
Menu.run	WsAdminAgent.run
MfAdminAgent.run	

Config.sys	IvMaxtor53.cnf
CP00.cnf	IvMicro52.cnf
DP00.cnf	IvMicropolis85.cnf
FP00.cnf	IVSyQuest6.cnf
ExecMsg.bin 	Master.cnf
IvAtasi46.cnf	QicTable.txt
IvBall100.cnf	RemoteInit.sub
IvCdc300.cnf	RemoteInit.user
IvCdc340.cnf	SignOn.txt
IvCdc675.cnf	SRPInit.jcl
IvFujitsu80.cnf	Sys.cmds 
IvHitachi51.cnf	TapeConfig.sys
IvHitachi85.cnf	TapeTable.txt
IvMaxtor143.cnf	.user}
{NGEN INITIALIZATION DISKETTE 
Diskette 1 of 2, <Sys> directory
.user	LInstall.run
1024x768_80sys.font 	Remote.user
720x348_80sys.font  	Signon.run
Bootstrap.run  	Signon.txt
Exec.run   	sys.cmds
ExecMsg.bin  	t1Sys.font
Hdinstall.sub  	Vdm_BM.run
Init.user   	Vdm_CH.run
InstallVdm.run  	Update.user

NGEN Initialization Diskette 1 of 2}
{Diskette 2 of 2, <Sys> directory
.user           	InstallVdm.run
1024x768_146LocSys.Icon  	IVolume.run
1024x768_146Sys.font    	LCopy.run
1024x768_80LocSys.Icon   	LInstall.run
1024x768_80Sys.font    	Remote.sub
720x348_80LocSys.Icon   	Remote.user
720x348_80Sys.font     	Remote.Reboot.sub
Bootstrap.run       	Signon.run
Config.sys         	Signon.txt
Continue.txt        	SrpAte.sub
ContinueInit.sub      	SrpAte.user
ContinueUpdate.sub     	Submit.run
Exec.run          	Sys.cmds
ExecMsg.bin        	t1Sys.font
HdInstall.fls       	Update.sub
HdInstallFont.fls     	Update.user
Init.sub          	UpdateReboot.sub
Init.user         	Vdm_BM.run
Initreboot.sub       	Vdm_CH.run
InstallConfig.sys}
{STANDARD SOFTWAREII UTILITIES DISKETTES
Diskette 1 of 7, <Sys> directory
ClusterCmds.sub	MCmds.sub
CmdsUpdate.sub	QueueCmds.sub
Command.run	Settime.run
ContinueInstall.sub	Signon.txt
ContinueInstall.sub	StdSS1
CreateBackupFloppy.sub	Subcmd.run
EditorII.run	Sys.cmds
Files.run	Sys.cmdsinitial
Format.run	Sysinit.run
HdInstall.fls	Sysinit.txt
Install.sub	UserFileTemplate.sys
InstallNewRequest.sub	VolumeStatus.run
LocalTapeCmds	WsAdminAgent.txt
MakeCmd.sub	Xbif.run
MasterCmds.sub	XC002Server.run
MasterTapeCmds.sub

Standard Software Diskette 1 of 7}
{Diskette 2 of 7, <Sys> directory
BackupVolume.run	HdInstall.fls
ClusterStatus.run	MakeRqSet.run
CmdFileEditor.run	PartitionStatus.run
DisableCuster.run	Plog.run
DisableCluster.run	ResumeCluster.run
FloppyCopy.run	UserFileEditor.run

SetDirectoryProtection.run
Standard Software Diskette 2 of 7}
{Diskette 3 of 7, <Sys> directory
BadSpotReport.run	PtrbConfig.sys
CheckConfig.run	Queue.index
CreateConfig.run	QueueMgr.run
DeInstallqmgr.run	Restore.run
HdInstall.fls	SelectiveBackup.run
HdInstallConfig.fls	SplbConfig.sys
Installqmgr.run	SplCnfg.sys
InsatllSpl.run	SplConfig.sys
Installqmgr.run	SpoolerStatus.run
ListRqSet.run	Version.run
LptConfig.sys	WsAdminAgent.run
MathServer.run	

StandardSoftwareDiskette 3 of 7}
{Diskette 4 of 7, <Sys> directory
DailyBackup.sub	TapeBackupVolume.run
DeinstallQicserver.run	TapeConfig.sys
HdInstall.fls	TapeCopy.run
NgenQicServer.run	TapeRestore.run
QicErase.run	TapeSelectiveBackup.run
QicRetension.run	WeeklyBackup.sub

Standard Software Diskette 4 of 7}
{Diskette 5 of 7, <Sys> directory
HdInstall.fls	MQicServer.run
MfAdminAgent.run	MSpoolerMgr.Run
MHisto.run	MSpoolerStatus.Run
Histoproc.run	MTapeServer.run
MInstallproc.run	SlvAdminAgent.Run
MInstallServer.run	SysAdminAgent.Run
MIvolume.run	TapeConfigure.run
MPartitionStatus.run	WsAdminAgent.run

Standard Software Diskette 5 of 7}
{Diskette 6 of 7, <Sys> directory
Append.run	LoadPrimaryTask.run
Copy.run	RemoveDirectory.run
CreateDirectory.run	RemovePartition.run
CreatePartition.run	Rename.run
Delete..Run	SetFileProtection.run
HdInstall.fls	VacatePartition.run

Standard Software Diskette 6 of 7}
{Diskette 7 of 7, <Sys> directory
ATE.run	HdInstall.fls
Batch.run	Print.run
Cdtio.run	Request.2.sys
ChgVolName.run	Request.9.sys
CLI.run	Request.sys
cmvp.run	Request.x.sys
CreateMsgFile.run	Sync.run
ExecMsg.txt	SyncStatus.run

Standard Software Diskette 7 of 7}
{STANDARD SOFTWARE DEVELOPMENT DISKETTES
Diskette 1 of 2, <Sys> directory
Assembler.run	HdInstall.sub
Ctos.lib	Librarian.run
Developcmds.sub	Linker.run
HdInstall.fls	

Software Development Diskette 1 of 2}
{Diskette 2 of 2, <Sys> directory
CommNub_pre10.obj	Nls.asm
CommStatus_pre10.obj	Nls.mdf
Debugfile.run	RequestTemplate.txt
DebuggerN.sys	Samgen.mdf
Dump.run	Samgenall.asm
HdInstall.fls	Samgenall.obj
InitComm_pre10.obj	Wrap.run

Software Development Diskette 2 of 2

Diskette 2 of 2, <ReleaseNote> directory

ReleaseNotice}
{CTOSII OPERATING SYSTEM KIT DISKETTES
NGEN OS KIT
Diskette 1 of 2,
  <Sys> Directory:
    1	InstallOS
    2	HdInstall.sub
    3       
  <CT> Directory:

    nStnd.run	nMstr.run}
{Diskette 2 of 2, 
  <Sys> directory:
    1	4
    2	InstallOS
    3	HdInstall.sub
  <CT> directory:

    nClstr.run	nClstrLfs.run}
{CTOSII OPERATING SYSTEM KIT DISKETTES
SRP OS KIT
Diskette 1 of 2,
  <Sys> Directory:
    HdInstall.sub
  <CT> Directory:

    SrpCp.sys	SrpSp.sys
    SrpTp.sys}
{Diskette 2 of 2, 
  <Sys> directory:
    HdInstall.sub
  <CT> directory:

    SrpDp.sys	SrpSp.sys}
{CTOSII OPERATING SYSTEM BUILD DISKETTES
Disk 1 of 3, <Sys> directory
   HdInstall.sub	LinkCtos.sub
   LinkCtosCmd.sub}
Disk 2 of 3, <Gen> directory
   Clstr.lib
   Dbg.lib	Init.lib
   nls.asm	nls.mdf
   RqLabl.obj	RqLablAlt.obj
   SourceDbgNub.lib
Disk 3 of 3, <Gen> directory
   OS.lib
Disk 3 of 3, <ReleaseNote> directory
   ReleaseNotice
{Disk 1 of 3, <Gen> directory
   kbd.asm	Kbd.mdf
   Kbd.obj	nClstr.asm
   nClstr.link	nClstr.obj	
   nClstrLfs.asm	nClstrLfs.link
   nClstrLfs.obj	nMstr.asm
   nMstr.link	nMstr.obj
   nStnd.asm	nStnd.link
   nStnd.obj	Request.asm
   Request.mdf	Request.obj
   Request_MF.asm	Request_MF.mdf
   Request_MF.obj	SrpCp.asm
   SrpCp.link	SrpCp.obj
   SrpCpDeb.asm	SrpCpDeb.link
   SrpCpDeb.obj	SrpDp.asm
   SrpDp.link	SrpDp.obj
   SrpDpDeb.asm	SrpDpDeb.link
   SrpDpDeb.obj	SrpDpTape.link
   SrpFp.asm	SrpFp.link
   SrpFp.obj	SrpFpDeb.asm
   SrpFpDeb.link	SrpFpDeb.obj
   SrpFpQic.link	SrpSp.asm
   SrpSp.link	SrpSp.obj
   SrpSpDeb.asm	SrpSpDeb.link
   SrpSpDeb.obj	SrpTp.asm
   SrpTp.link	SrpTp.obj
   SrpTpDeb.asm	SrpTpDeb.link
   SrpTpDeb.obj	SrpXp.asm
   srpXp.link	SrpXp.obj
   sysgen.asm	sysgen.mdf}
4.0	INSTALLATION PROCEDURES
{4.1  REQUIRED HARDWARE
Installation is performed in one of four modes: INIT, UPDATE, REMOTE, or SrpATE.  Section 4.2 supplies the details of these different modes.
On an NGEN workstation:
  o	Init:    Require hard and floppy drive.
  o	Update:  Require hard and floppy drive.
  o	Remote:  Require floppy attached to master 
		    via cluster cable.
On an SRP:
  o	SrpAte:  SRP must have a QIC or Sysquest 
		    drive and an NGEN with a floppy 
		    drive attached via cluster cable and 
		    attached via RS232 crossed cable.
  o	Remote:  Requires an NGEN  with a floppy 
		    drive attached to master via cluster 
		    cable.
*** IMPORTANT ***
A minimum of a 20 megabyte hard disk is recommended for installation of Standard SoftwareII.  All Operating Systems will fit in a SysImage of 512K.}
4.2	THEORY OF INSTALLATION
Installation Modes:  Init, Update, Remote and SrpATE
Installation of Standard SoftwareII either initializes or updates a system volume.
Use Init when you want to initialize a new disk as your system volume or when you intend to discard all the information currently on your system volume.  The intent is to copy all new software from the floppy disks to the local hard disk.  The Init mode installation for an SRP starts from QIC tape or Syquest, then proceeds with a Remote installation from floppies.
{Use Update when your system volume contains valid information.  The intent is to update an existing local hard disk with new software.}
{Use Remote to update Standard Software at the master from a cluster workstation.  Remote installation is useful when the master has no floppy disk  for example, an SRP master.  The intent of the REMOTE installation is to copy new software from a local floppy to the master's hard disk.}
Use SrpATE to initialize an SRP.  The installation begins by booting the SRP off a QIC tape or Syquest and giving commands via a NGEN workstation running the Asynchronous Terminal Emulator (ATE).  The installation initializes the hard disk of the SRP and copies a minimal set of Standard Software to the hard disk.  The installation then proceeds via the Remote mode.
Installation Steps
Standard SoftwareII installation consists of the following steps.  Section 4.3 below gives detailed steps that you can follow to install your software.
Step 1: for SRP Initialization only.  If you wish to initialize the hard disk of an SRP, boot the SRP from the QIC tape or Syquest.  You then initialize the hard disk and copy a subset of Standard Software to the hard disk.  (Within Section 4.3, Step 1a discusses QIC tape and Step 1b discusses Syquest.)
Step 2: for SRP Update only.  If your SRP is currently running some version of CTOS, you need to update the OS's on the SRP before installing Standard Software.
Step 3: installation uses the Initialization floppy diskette as a system volume and initializes or updates the hard disk to function as a system volume for workstaions and SRPs.
Step 4: the workstation reboots and copies Standard SoftwareII onto the system volume.
Optional steps:
{Step 5: the installation of the Standard Software Development Utilities.  You should install these utilities if you plan to do any software development on your system.}
{Step 6: the installation of a different Operating System or OS's.  For example, the installation leaves a cluster local file system version of the Operating System on your hard disk.  If you wish to run a standalone version of the OS, it can be copied on at this point.}
Step 7: the installation of the CTOSII Build diskettes.  This set of diskettes allows you to build any version of CTOSII.  It also makes it possible for you to modify SysGen parameters if you want to customize your OS.
{4.3  INSTALLATION PROCEDURES
The installation procedure described below is appropriate for NGEN workstations and SRP's.
Installation may display error messages while creating directories, copying files, deleting files, or renaming files.  You may disregard these error messages.}
There are three modes of installation; Init, Update, and Remote.  The Init and Update modes of installation are intended for NGEN's with a local hard disk.  The Remote installation is intended for updating the hard disk of the master, be it an SRP or NGEN.

_________________________________________________
	IMPORTANT NOTE:
	BEFORE DOING AN UPDATE INSTALLATION
If you intend to do an Update installation, it is strongly suggested that you delete any unneeded files before proceeding with the installation.  For example, you may wish to delete all files in the temporary (dollar sign) directories, all old files, all .tmp files, and any other files that you do not use.  This should be done to ensure that enough disk space has been cleared to allow the installation to run through to completion.
Standard Software II 1.0 requires a minimum of a 20 megabyte hard disk for the System volume.
In fact, when updating from SRP Ctos3.x or CTOS9.x to CTOSII, it is strongly recommended that you do the following.  First, delete all unneeded files.  Then backup the hard disk to floppies or tape.  On a separate floppy, save away an additional copy of your command file (Sys.cmds), SignOn.txt, and any specially modified config files.  Proceed with an Init installation as described below.  Then perform a Restore specifying no for the parameter [Overwrite OK?].  Finally, copy back your saved command files, SignOn.txt, etc.
Give a Files command specifying [Sys]<Sys>SysImage.sys in the [Filename] parameter and specifying yes to the [Details?] parameter.  This will tell you how much space is reserved on your hard disk for the Operating System.  If the value for Sectors is less than 512 (presumably 384) then you MUST perform the above procedure.  As of CTOSII, you must have 512 sectors reserved on your system volume for the OS.  It will no longer fit in 384.
It is always a good idea to keep a backup of your hard disk.  Also, the Backup, IVolume, Restore procedure reduces fragmentation of the hard disk.
_________________________________________________

Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in uppercase.	

STEP 1 a)  SRP INITIALIZATION FROM QIC TAPE
	The equipment required for SRP initialization is an SRP (which is defined as a system with a master processor, either a File Processor or Data Processor, and at least one Cluster processor) and an NGEN workstation with at least one floppy drive.
{A.	Connect an RS232 crossed cable from channel 3 of CP00 of the SRP to port B of the workstation.  Connect an RS422 cable from line 1 of CP00 to the workstation.  Place a terminator on the free cluster connector of the workstation.  Also, place a terminator on the other port of Line 1 of the SRP.}
{B.	Insert the NGEN Initialization Diskette 1 of 2 into the floppy drive.  Press the reset button.  After the SignOn screen appears, remove the first diskette and insert the NGEN Initialization Diskette 2 of 2.  Log on with the user name of SrpATE.  When prompted, insert the Standard Software Diskette 7 of 7 and press the GO key.  The screen will clear and the ATE banner will be displayed.  The third line contains a double bar running the width of the screen.  The screen underneath the double bar will remain empty until step E.}
C.	Load the 1.0 CTOSII Initialization QIC tape in the drive.
{D.	Power up the SRP if it is not on already.  Turn the key on the front panel of the SRP to the off position, then to the manual position.  This initiates the booting process.  Wait until the number 20 is displayed on the front panel of the SRP.  Now check the lights on CP00 (to do this you must walk around to the rear of the SRP and open the rear door of the enclosure which contains CP00.)  The lights should appear as follows:

	TOP:	Off
		On
		Off
		On
		Off
		Off
		Off
		Blinking}
{E.	A menu will appear on the screen of the workstation after 3 to 5 minutes.  Type the numeral 1 to initialize the system volume.

You need to answer the prompts presented.  Press RETURN after answering each.  Mistakes can be corrected by pressing the BACKSPACE key.  If you notice that you have made a mistake in a previous field, you can simply press the RETURN key enough times such that the entire menu cycles through again.}

{If you are booting from QIC tape (your primary enclosure is called a C box), the device name and device password are the two characters d1.}

{Although this installation is not packaged for it, if you were booting from HalfInch tape your primary enclosure is called an E box, the device name and device password would the two characters s0.}
{	If this is the first time you are initializing a hard disk, you should read the discussion of initializing volumes in the Systems Administrator's Guide.  The values given below as answers to the Maximum number of ... prompts, are appropriate for a forty megabyte disk.  You may wish to alter them if you have a larger disk.  For the rest of the prompts, the recommended values are as follows:

  System Image Sectors: 512
  Log File Sectors: 32
  Crash File Sectors: 1536
  Maximum number of directories on volume: 50
  Maximum number of files on volume: 4000
  Maximum number of files in SYS directory: 
           400
  Surface tests: 8
  Bad Spots:  
           For information on bad spot 
           formats, see section 4.4 of
           this release notice.

After you have filled out the form, press the GO key on the workstation.}

{When you specify many surface tests, the initialization of the volume can take a long time.  For example, a forty megabyte drive running eight surface tests can take up to 45 minutes.  It is strongly recommended that you run eight surface tests when initializing for the first time.  If the disk is already initialized you should run at least one surface test.}

{After completion of the volume initialization, press the RETURN key to reload the menu program.}
{F.	After the menu reappears, type the numeral 2 to restore files to the volume.  Then answer the prompts as follows (for any prompt not specifically listed here, respond by just pressing RETURN):

  Archive file: 6
  File list from: <*>*
  To File list: <Sys>*
  Overwrite OK?: yes
  Confirm each?:  Press GO


After completion of file restoration, press the RETURN key to reload the menu program.  The 6 above refers to the sixth file archived on the tape.}
{G.	After the menu reappears, type the numeral 2, again, to restore another file to the volume.  Then answer the prompts as follows (for any prompt not specifically listed here, respond by just pressing RETURN):

  Archive file: 7
  File list from: <*>*
  To File list: <Cmd>*
  Overwrite OK?: yes}
H.	After completion of file restoration, unload the tape from the drive.
I.	Press the reset key on the front panel of the SRP.

	Continue with Step 3 below using Remote Installation.
STEP 1 b)  SRP INITIALIZATION FROM SYQUEST
	The equipment required for SRP initialization is an SRP (which is defined as a system with a master processor, either a File Processor or Data Processor, and at least one Cluster processor) and a workstation with at least one floppy drive.
{A.	Connect an RS232 crossed cable from channel 3 of CP00 of the SRP to port B of the workstation.  Connect an RS422 cable from line 1 of CP00 to the workstation.  Place a terminator on the free cluster connector of the workstation.  Also, place a terminator on the other port of Line 1 of the SRP.}
{B.	Insert the NGEN Initialization Diskette 1 of 2 into the floppy drive.  Press the reset button.  After the SignOn screen appears, remove the first diskette and insert the NGEN Initialization Diskette 2 of 2.  Log on with the user name of SrpATE.  When prompted, insert the Standard Software Diskette 7 of 7 and press the GO key.  The screen will clear and the ATE banner will be displayed.  The third line contains a double bar running the width of the screen.  The screen underneath the double bar will remain empty until step E.}
C.	Load the 1.0 CTOSII Initialization Syquest cartridge in the drive.
D.	Power up the SRP if it is not on already.  Turn the key on the front panel of the SRP to the off position, then to the manual position.  This initiates the booting process.  Wait until the number 20 is displayed on the front panel of the SRP.  Now check the lights on CP00 (to do this you must walk around to the rear of the SRP and open the rear door of the enclosure which contains CP00.)  The lights should appear as follows:

	TOP:	Off
		On
		Off
		On
		Off
		Off
		Off
		Blinking
E.	Depress the RETURN key on the workstation.  A dollar sign ($) should appear.  Type the word SrpInit followed by the RETURN key.
{F.	A series of prompts will appear on the screen of the workstation.  You need to answer the prompts presented.  Press RETURN after answering each.  Mistakes can be corrected by pressing the BACKSPACE key.  If you notice that you have made a mistake in a previous field, you can simply press the RETURN key enough times such that the entire menu cycles through again.}

{When you boot from a Syquest cartridge, your primary enclosure is called an A box.  The device name and device password are the two characters d1.}
{	If this is the first time you are initializing a hard disk, you shoud read the discussion of initializing volumes in the CTOSII Systems Administrator's Guide.  The values given below as answers to the Maximum number of ... prompts, are appropriate for a forty megabyte disk.  You may wish to alter them if you have a larger disk.  For the rest of the prompts, the recommended values are as follows:

  System Image Sectors: 512
  Log File Sectors: 32
  Crash File Sectors: 1536
  Maximum number of directories on volume: 50
  Maximum number of files on volume: 4000
  Maximum number of files in SYS directory: 
           400
  Surface tests: 8
  Bad Spots:  
           For information on bad spot 
           formats, see section 4.4 of
           this release notice.

After you have filled out the form, press the GO key on the workstation.}

{When you specify many surface tests, the initialization of the volume can take a long time.  For example, a forty megabyte drive running eight surface tests can take up to 45 minutes.  It is strongly recommended that you run eight surface tests when initializing for the first time.  If the disk is already initialized you should run at least one surface test.}

{After completion of the volume initialization, press the RETURN key to reload the menu program.}
G.	After volume initialization, the SRP will copy the necessary files to drive [d1].  The last file to be copied is WSAdminagent.txt.
H.	After completion of the copying, remove the Syquest cartridge from the drive.
I.	Press the reset key on the front panel of the SRP.
	Continue with Step 3 below using Remote Installation.

STEP 2  SRP UPDATE ONLY
	If you have an SRP that is already running some version of CTOS, you must update the Operating System before installing Standard Software.
	For this installation, you must have connected to the SRP an NGEN workstation with at least a floppy drive.
A.	Insert the disk labelled SRP OS Kit 1 of 2 in the floppy drive of the NGEN.  Type:

   Install  GO
B.	Insert disk 2 of 2 when prompted to do so.
{C.	This installation places new versions of Master.cnf on your disk and copies the existing one to Save>Master.cnf.  Note that the names of the OS's have changed from the previous releases.  You should edit the new Master.cnf to match your hardware configuration as in the saved copy.}
D.	Reboot the SRP.
	Continue with Step 3 using Remote Installation.

STEP 3  INIT, UPDATE, or REMOTE INSTALLATION:
A.	If the workstation is not already on, turn the power on.
{B.	Place the Standard SoftwareII diskette labeled NGEN Initialization 1 of 2 into floppy drive [f0].}
{C.	Press the small hardware RESET button located on the upper left rear of the NGEN processor module.}
{D.	After a short time, the SignOn form appears.  Enter a user name, password, and datetime as described below.
User Name.  Enter the user name Init if you are installing software for the first time or if you plan to reinitialize your hard disk.}
{		
CAUTION:
Initializing the hard disk erases all existing files.
		
}
{	Enter the user name Update if you are updating Standard SoftwareII.  You must be running CTOS version 9.1 or later (or 9.5 or later on a 286 NGEN) to perform an Update installation.
	Enter the user name Remote if you are updating Standard SoftwareII on the master from a cluster workstation or if you signed on as SrpATE before.  Also, execute the Logout command at the master workstation and on all workstations that are booted from the master.}
{Password.  A password is optional.
	Enter a password if you are going to password protect your hard disk during initialization or if you are updating a hard disk that is already password protected.}
{		
NOTE:
Volume and <Sys> directory passwords are required in order to enable CTOSII file system security.
		
}
{	If the system volume is protected, failure to enter the correct password will result in error 219 (access denied) during installation.}
{DateTime.  If you have just powered up the workstation, the datetime that is displayed is incorrect (an incorrect datetime is signified by a flashing dim display of the time in the upper right hand corner of the screen).
	You may correct the datetime by entering it in the format Mon Jul 7 1986 8:00 am.  You can enter any part of this field that is incorrect, and in any order.
Press GO to continue.}
{E.	The next step enables installation to copy only files and commands that are appropriate for your configuration.
	A form containing the supported software configurations appears.  Use the cursor keys, the RETURN key, or the NEXT key to select the appropriate configuration.}
	The supported configurations are as follows:
NGEN Standalone.  A workstation with a local hard disk to be run in standalone mode.
NGEN Cluster Local File System.  A workstation with a local hard disk which is to be connected via an RS422 communications line to a nonSRP Master.
NGEN Cluster Local File System on SRP Master.  A workstation  with a local hard disk which is to be connected via an RS422 communications line to an SRP Master.
NGEN Master.  A workstation with a local hard disk which is to be used as a master workstation.
REMOTE SRP MASTER.  An NGEN workstation with at least a floppy drive, connected to an SRP master.
REMOTE NONSRP MASTER.  An NGEN workstation with at least a floppy drive, connected to an SRP master.  This master would be either an NGEN, IWS, or AWS.
{		
NOTE:
This step does NOT cause installation of the corresponding operating system:  it only ensures that the Standard Software you install is compatible with the configuration you choose here.  After Standard Software installation, you can install the desired operating system using the prebuild Operating Systems contained on the OS Kit Diskettes.
		}

	After selecting the appropriate installation type, press GO to continue.
F.	If you entered user name Init or Update, a Path command form appears.  If you wish to initialize or update a system volume other than [d0], fill in the [Volume] field with the appropriate device name (for example, [d2]).
	Press GO to continue.
{		
NOTE:
If you wish to designate hard disk drives [d1], [d2], or [d3] as the system drive, all preceding drives must be nonbootable drives.  For example, if you wish [d1] to be your bootable system volume, then [d0] must be nonbootable  that is, contain no operating system in SysImage.sys.
You can make an NGEN hard disk nonbootable by overwriting its SysImage.sys with a nonexecutable file, such as a text file.
		
}
{G.	If you entered user name Init, the following IVolume command form appears.  Note that the period in the Device name field means the current pathed volume.}
{	IVolume
  Device name                     .
  [Device password]               
  Volume name                     Win
  [Volume password]
  [System Image (default = 0]     512
  [Log file (default = 0)]        12
  [Crash file (default = 0)]      0 or 3000
  [Max. directories]
  [Max. files on volume]
  [Primary file headers only?]
  [Max. files in Sys Directory]
  [Sys Directory password]        Sys
  [Write protect Sys Directory?]  yes
  [Suppress format of medium?]
  [Surface tests]
  [Debug?]
  [Log file]
  [Extended floppy tracks?]
  [NGEN hard disk type code]
  [Bad spots (See Documentation)]}}
{	You are not required to enter any additional information.  However, consider optionally changing the following fields.}
Volume Name.  You may enter a 12character volume name of your choice.  Volume names must be chosen to be unique within a workstation and between a workstation and the master.
[Volume password].  To enable CTOS file system security, enter the password that you wish to be associated with the volume being intialized.
{[Crash file (default = 0)].  This parameter determines the size of the file CrashDump.sys.  This file is used by the Context Manager and the Operating System to be the default swap file.  The recommended size is 3000 sectors.  If this is to be your swap file and you enter less than 3000, you will later need to edit the file, [Sys]<Sys>Config.sys and modify the entry SwapFileSize: to indicate the size you pick.  See the CTOSII System Administrator's Guide for details.}
{[Sys Directory password].  You may enter a Sys directory password of your choice.  This password is used only if a [Volume password] is also entered.}
{	If the hard disk has previously been initialized, IVolume obtains drive parameters and bad spot information from the hard disk.  If this information is not on the disk, IVolume prompts you to enter it.  See Section 4.4, Entering Disk Type Code and Bad Spot Information, for details.
	Volume initialization may take up to 45 minutes depending on the number of surface tests.  It is strongly recommended that you run eight surface tests when initializing for the first time.  If the disk is already initialized you should run at least one surface test.
	Press GO to continue.}

STEP 4  COPY STANDARD SOFTWAREII
A.	After the various files are copied to the hard disk, the workstation automatically reboots and the SignOn form appears.
	Enter the same user name and password that you entered into the SignOn form at the beginning of installation.  Enter the correct datetime if desired.
	Press GO to continue.}
B.	When prompted, insert Standard SoftwareII Utilities diskettes 1 through 7 into floppy drive [f0].
	After inserting the requested diskette, press GO to continue.
{		
NOTE:
If you are not performing a Remote installation to an SRP, diskettes 5 and 6 will will not actually install anything.  However, they must be inserted and removed at the appropriate times to insure successful installation in all modes.
		}

	After the contents of these diskettes have been installed, installation of Standard SoftwareII itself is complete, and users can run the Executive and the utilities that have been installed, as well as various applications programs.}
{C.	The last step in the installation of standard software is the merging of all loadable request files into [Sys]<Sys>Request.sys.  This is done by using the List Request Set utility to convert all existing loadable request files, along with the version of Request.sys on disk 7 of 7 into one text file, [Scr]<$>Request.txt.  Then, Make Request Set is used to convert the text file into the single loadable request file.  In the process of doing this, the contents (the actual definition of the loadable requests) are merged.  If a loadable request is defined in more than one of the original loadable request files, and the definitions do not agree, then the Make Request Set utility cannot do the merge.  Instead, an error message is displayed for each request definition which has duplicate andor conflicting definitions.  See the CTOSII System Administrator's Guide for details on List Request Set and Make Request Set.  If no error messages appear, proceed with step 5 below.}
{	In order to procede with a correct CTOSII installation, these conflicting definitions must be resolved.  To do this, you should first, write down the numbers of the request codes for which you receive error messages.  Then you must edit the text file, [Scr]<$>Request.txt.  Within this file you need to locate the multiple definitions of all offending requests.  When you find the definition look backwards in the file to a line which says something like:

   ;*** Request.n.sys

This entry tells you the original loadable request file that defined that request.  A full list of Convergent supplied loadable request files appears in section 9.4 of this Release Notice.  If can determine which definition is in error, you should delete the incorrect definition(s).  If you cannot determine which is in error, you may need to call Technical Support.}
{	Once you have edited [Scr]<$>Request.txt, you must then use the Make Request Set Utility to convert the text file into the single loadable request file, [Sys]<Sys>Request.sys.  Then continue on with the installation.}

{STEP 5  SOFTWARE DEVELOPMENT (OPTIONAL)
A.	After installation of Standard SoftwareII, you may optionally do a separate installation of the Standard SoftwareII Software Development Utilities.  These utilities include the Linker, the Librarian, the Assembler, the Debugger, CTOS.lib, etc.  You need to install these diskettes if you want to do any software development on this workstation, including building a custom CTOSII operating system.}
{	If you entered the user name Remote to update a remote NGEN master, you must deactivate the Debugger at the master workstation and at all workstations booted from the master running a preCTOSII version of the OS.  To deactivate the Debugger, press ACTIONA.  If you hear a beep, the Debugger is already deactivated.  Otherwise, press CODEK twice, then press GO.}
{	Install the diskette labelled Standard SoftwareII Software Development Utilities 1 of 2 and type:
	    Install  GO
	Insert diskette 2 of 2 when prompted and press GO to continue.}

{STEP 6  INSTALL A DIFFERENT OS (OPTIONAL)
A.	The Init and Update modes of Installation leave a Cluster Local File System version of the Operating System (nClstrLfs) on the hard disk of the NGEN.  If you wish, you can change this to be a standalone or master version of the OS.  To install a different version of the OS, insert the NGEN OS Kit diskette 1 of 2 and type:
	    Install  GO
	A prompt will appear asking you which version of the Operating System you wish to install.  Enter a digit which represents your choice and press GO.  Insert diskette 2 of 2 if prompted to do so.}
	The second diskette also gives you the capability to set up a master workstation to have cluster workstations booted from them.  To copy these operating systems, insert the diskette labelled NGEN OS Kit diskette 2 of 2 into the floppy drive of the master or a cluster station and type:
	    Install  GO
{	A prompt will appear asking you whether you are installing from the master or from a cluster station.  Enter a digit which represents your choice and press GO.}

STEP 7  CTOSII BUILD ENVIRONMENT (OPTIONAL)
A.	This set of diskettes contain all of the CTOSII Build libraries which allow you to build any version of CTOS.  It also makes it possible for you to modify SysGen parameters to customize your OS.  (The prebuilt versions of the Operating System in the previous step were built from these files without changing any SysGen parameters.) To install the build environment, path to the appropriat volume and insert the CTOSII Build Kit diskette 1 of 3 and type:
	    Install  GO
	Insert the remaining diskettes when prompted to do so.  This installation creates a <Gen> directory and copies all files into that directory.
	See the CTOSII Operating System Release Notice for details on building a customized version of the Operating System.

A NOTE ON INIT INSTALLATION
	If you have backed up your hard disk prior to performing an Init installation to upgrade from CTOS 9.x to CTOSII, then you should follow these steps.  
A.	Give a Restore or Tape Restore command specifying no to the parameter [Overwrite OK?].  This will copy back all application and personal files.
B.	Copy back your Sys.cmds, and other specially modified config files.
C.	Submit the file, [Sys]<Sys>CmdsUpdate.sub.  This will update your command file to include new commands for Standard SoftwareII.
D.	If you are running a Standalone or Cluster Local File System version of the Operating System and don't plan to return to CTOS 9.x, delete the following files, Request.2.sys, Request.X.sys, and Request.9.sys.  These files contain loadable requests for standard software utilities.  The information contained in these files is now contained in the file Request.sys.  If you are running a master workstation, you should keep these files around if you are booting diskless workstations from your master that are running preCTOSII versions of the Operating System.
E.	Finally, you must merge any application's loadable requests into  [Sys]<Sys>Request.sys.  Give the following command to perform this step:

Install New Request
  File list  [Sys]<Sys>Request.?.sys GO
F.	Reboot the workstation.
{		
          NOTE ON THE CONTEXT MANAGER:
If you wish to run the Context Manager on CTOSII, you must install Context ManagerII.  No prior versions of the Context Manager will work.
		}

{4.4	ENTERING DISK TYPE CODE AND BAD SPOT 
INFORMATION
If the hard disk has previously been initialized, the IVolume utility reads the disk type code (on NGEN) and bad spot information from the hard disk.
However, if this information is missing, you must enter it in the appropriate fields of the IVolume command form or interactively when prompted by IVolume.}
{On NGEN hard disks, a report showing the drive type code and bad spots is attached to the bottom of the disk module.  After a disk has been initialized and Standard SoftwareII has been installed, you can give the new Bad Spot Report command to obtain a listing of the bad spots on the disk.}
{		
NOTE:
If your disk drive contains bad spots, you MUST enter bad spot information in order for your disk to function correctly.
		
}
{NGEN Hard Disk Type Code
A disk type code is a letter (for example, A, B, C) that designates a particular disk drive.  It is located on the bad spot report, which is attached to the bottom of the disk module.}
{IVolume uses the disk type code to determine drive parameters such as number of cylinders, number of heads, and number of sectors per track.}
{Enter the disk type code when prompted to do so by the IVolume utility.  Optionally, you may enter the disk type code into the [NGEN hard disk type code] field of the IVolume command form.}
{The supported disk type codes are summarized in the table below.  Note that the Size field is unformattedformatted capacity.}
{Code  Vendor        Size      Cyl  Heads Sectors
A	Tandon	12.710 Mb	306	4	16
B	Seagate	12.710 Mb	306	4	16
C	reserved
D	Atasi	46.537 Mb	645	7	16
E	Quantum	42.732 Mb	512	8	16
F	MiniScribe	2620 Mb	612	4	16
G	Seagate	2620 Mb	612	4	16
H	reserved
J	reserved
K	Micropolis	8567 Mb	1024	8	16
L	reserved
M	reserved
}
{If your disk drive is not supported by a disk type code, you may enter the actual drive parameters when prompted to enter the code.  Enter the parameter data as cylindersheadssectors.
For example, if your drive parameters are 1024 cylinders, 4 heads, and 16 sectors per track, enter the parameter data as follows:
1024416}
{Bad Spot Information
Enter bad spot information when prompted to do so by the IVolume utility.  Optionally, you may enter this information in the [Bad spots (see documentation)] field of the IVolume command form.  Separate entries with spaces.  An entry must be contained entirely on a line.  If there are many bad spots an atfile may be created through the Editor and used.  See the Executive II Manual for details.}
Depending on the manufacturer of the disk drive, bad spot information is in one of the formats below.
{Format 1
				
	    CYLINDER   HEAD   BFI SECTOR

       84       1       4
      241       2      13
				
}
{For units with bad spot information as above, enter a bad spot entry as:
	8414
If there is no sector number, but there is a BFI (bytes from index), then enter the bad spot entry as:

	8414   (leave the pound sign off)}
{Format 2
				
	     TRK HD    BYTE COUNT    LENGTH(BITS)
             
     084 1       02646            04
     241 2       08130            39
				
}
or
{Format 3
				
	                       DISPLACEMENT    LENGTH
    CYLINDER   HEAD      IN BYTES      IN BITS

      84 54     1       2646 A56        4 4
     241 F1     2       81301FC2       3927
				

For units with bad spot information as in the two examples above, enter a bad spot entry as:
	84126464}

{Format 4
				
	    CYLINDER   HEAD     BYTE OFFSET     DEGREE

      84 54     1       2646 A56        81
     241 F1     2       81301FC2       263
				

For units with bad spot information as in the last example above, enter a bad spot entry as:
		8412646}

{5.0	SYSTEM SOFTWARE COMPATIBILITY
5.1	WORKSTATION ENVIRONMENT
Standard SoftwareII version 1.0 is intended for use with CTOSII version 1.0.  However, Standard SoftwareII version 1.0 is backward compatible for use on diskless workstations booted off of NGEN or SRP masters, or with an IWS or AWS master.  To work correctly in these environments, the workstation must be running the following versions of CTOS:

	IWS	9.1
	AWS	9.1
	NGEN (186)	9.1 or later
	NGEN (286)	9.5 or later}
Versions of CTOS prior to 9.1 (or 9.5 if required) return status code 247 when running version 1.0 Standard SoftwareII.
When running CTOSII, Restore.run version 10.2 or later must be used.  Previous versions of Standard Software will return status code 207.  It is recommended however, to use Restore.run versionII1.0.
5.2	SRP ENVIRONMENT
Version 1.0 Standard SoftwareII can be installed on an SRP master from a cluster workstation.  It is intended for use on CTOSII and will not work on any prior SRP version of CTOS.
{6.0	REQUIRED FILES
6.1	Files for NGEN Bootable Diskette
	The following files are needed on a disk or diskette in order for it to be bootable on a NGEN.  All files must reside in the <Sys> directory.
Files needed to boot:

SysImage.sys	The CTOS system image
InstallVdm.run	Installs the video
Signon.run	First user visible program
.user	User file that allows the 
	user to sign on}
{Video:

Character map NGEN's:

Vdm_CH.run	Character map video
t1Sys.font	Character map font

Bit map NGEN's:

Vdm_BM.run	Bit map video
1024x768_80sys.font
	High resolution bit map font
720x348_80sys.font
	Low resolution bit map font}
{Files needed to run the Exec:

Exec.run	Executive run file
ExecMsg.bin	Executive message file
sys.cmds	Executive command file
Signon.txt	Initial message displayed 
	for user (optional)}
{Files created by initialization (IVoluming):

<Sys>crashDump.sys
<Sys>fileHeaders.sys
<Sys>log.sys
<Sys>mfd.sys
<Sys>badBlk.sys
}
{6.2	Files for SRP Bootable Media
	The following files are needed on a media in order for it to be bootable on an SRP.  All files must reside in the <Sys> directory.}
{Files needed to boot:

SysImage.sys	The CTOS system image
       For A and C boxes:    SrpFp.sys
       For E boxes:          SrpDp.sys}

CLI.sys	Command Line Interpreter

For A and C boxes:
FP00.cnf	Master file processor 
	configuration file

For E boxes:
DP00.cnf	Master data processor 
	configuration file

SrpCp.sys	The system image for a 
	cluster processor
CP00.cnf	The configuration file for 
	the cluster processor

Master.cnf	Master Configuration file

  Master.cnf must have at least the following   
  entries:

  Cp       [Sys]<Sys>SrpCp.sys
  Include  [Sys]<Sys>CP00.cnf}
{Files created by initialization (IVolume):

crashDump.sys
fileHeaders.sys
log.sys
mfd.sys
BadBlk.sys}
{7.0	HARDWARE INFORMATION
7.1	HARDWARE CONFIGURATIONS SUPPORTED
Version 1.0 Standard SoftwareII supports the following NGEN hardware modules:
CWS Workstations
CM002	512 Kb
CM003	1024 Kb}
NGEN Modules
CP0018	8 Mhz 80186 processor
CP0019	8 Mhz 80186 processor
CP002	8 Mhz 80286 processor
CP002287	8 Mhz 80286 processor with 80287 
	numerical processor
VM001	12 monochrome monitor
VM002	14 monochrome monitor
VM003	14 monochrome bitmap monitor
VC001	15 color monitor
GC001	graphics controller
GC003	graphics controller
KM001	keyboard
TM001	voice processor (with modem)
VP001	voice processor (without modem)
XC002	RS232 port expander
XE001	Ethernet module
PC001	PC compatibility module
HB001	quarterinch tape module
FD001	dual floppy disk
FD0A1	dual floppy disk
HD002	10 Mb floppyhard disk
HD003	20 Mb floppyhard disk
HD006	20 Mb hard disk upgrade
HD011	32 Mb hard disk upgrade
HD020	85 MB hard disk upgrade
HD0A1	20 Mb floppyhard disk
HX002	10 Mb hard disk expansion
HX003	20 Mb hard disk expansion
HX011	32 Mb hard disk expansion
HX020	85 Mb hard disk expansion
{8.0	RESOURCE REQUIREMENTSUTILIZATION
8.1	MEMORY REQUIREMENTSUTILIZATION
The table below indicates the memory requirements of interactive programs included in Standard Software.}
{When two numbers are given, the first indicates the minimum memory requirement and the second indicates the maximum amount of memory that the program can use.}
Assembler.run	 95K	127K
ATE.run	 83K	127K
BackupVolume.run	104K	259K
Batch.run	 44K
Bootstrap.run	 33Kplus size of
	     the bootstrap
	     runfile
CheckConfig.run	 28K
ChgVolName.run	 41K
ClusterStatus.run	 46K
CmdFileEditor.run	 73K
Command.run	 42K
CreateConfig.run	 42K
DebugFile.run	 87K
DeInstallTapeServer.run	 45K
DisableCluster.run	  4K
Dump.run	 39K
EditorII.run	250K
Exec.run	102K	166K
Files.run	 66K	130K
FloppyCopy.run	153K
Format.run	 58K	122K
IVolume.run	101K	151K
LCopy.run	140K
Librarian.run	121K	587K
Linker.run	136K	968K
LInstall.run	 90K
MaintainFile.run	120K
PartitionStatus.run	 26K
PLog.run	 59K
Restore.run	 96K	251K
ResumeCluster.run	  4K
SelectiveBackup.run	 97K	191K
SetDirectoryProtection.run	 26K
SetTime.run	 26K
Signon.run	 50K
SubCmd.run	 50K	 74K
Submit.run	 44K	108K
SysInit.run	 28K
QicErase.run	 88K
QicRetension.run	 48K
TapeBackupVolume.run	235K	all
TapeCopy.run	150K	all
TapeRestore.run	181K	all
TapeSelectiveBackup.run	235K	all
UserFileEditor.run	 80K
VolumeStatus.run	131K	165K
{The table below indicates the memory requirements of installed system services.
XBif System Service
  XBif.run	  4K
XC002 System Service
  XC002Server.run	  8K
Queue Manager
  InstallQMgr.run
  QueueMgr.run	 18K
Spooler
  InstallSpl.run	 43K
Tape Servers
  NgenQicServer.run	 78K
  mQicServer.run	 84K
  MTapeServer.run	 37K	all}
{8.2  DISK REQUIREMENTSUTILIZATION
The table below indicates the number of disk sectors required by Standard SoftwareII Utilities for various configurations.
NGEN Standalone	5000 sectors 
NGEN Cluster Lfs	4500 sectors
NGEN Master	5200 sectors
SRP Master	7000 sectors
The table below indicates the number of disk sectors required by Standard SoftwareII Development Utilities for various configurations.
Master	2100 sectors
Standalone or Cluster LFS	2100 sectors}
{9.0  SUPPLEMENTARY INFORMATION
9.1  NATIVE LANGUAGE SUPPORT
The following Standard SoftwareII run files offer native language support  that is, they obtain all of their messages from a message file:
CmdFileEditor.run
Command.run
Exec.run	
Files.run
Format.run
LInstall.run
SetDirectoryProtection.run
SetTime.run
SignOn.run
SubCmd.run
Submit.run
SysInit.run
VolumeStatus.run}
{The message file appears in two different forms; ExecMsg.txt is the text message file which contains the humanreadable text strings, and ExecMsg.bin which is the binary form that is actually used by these programs.  The new utility, Create Message File is used to convert this text file into its binary form.  See the CTOSII System Administrator's Guide for details on Create Message File command.}
{The strings in ExecMsg.txt can be edited, using the Editor, to be customized andor translated to another language.  Although the message text file can be edited in the Word Processor or Document Designer, it is not advisable to do so as these programs insert page breaks (formfeed characters) automatically.  An inadvertent page break may cause undesired results.}
{A comment at the beginning of the ExecMsg.txt explains its format and some special capabilities for using macros.  Colons must be used as delimiters for a message number or erc number.  Double quotation marks have been used as the string delimiter for the text strings.  However, any character can be used as delimeters for the text string as long as beginning and ending delimiters match.  If the character  appears in the string, you must use another charcter, such as , as the delimiter.  Comments can be inserted into the message file by starting the line with a semicolon.}
{It is advisable to copy ExecMsg.txt to another file and make any edits to the new file.  After all edits have been made, use the command Create Message File to produce a new binary message file.  The name [Sys]<Sys>ExecMsg.bin should be specified as the output file since, at this time, there is no facility for use of alternate binary message files.}
{Note that the file ExecMsg.bin must not be in use (for example, by a run file in another context) when you give this command, or status code 220 (file in use) results.}
If you have made editing errors such as leaving unbalanced delimiters, CreateMsgFile.run reports the first error encountered and shows the line in which it occurs before exiting.  (In such a case, ExecMsg.bin remains unchanged.)
When CreateMsgFile.run exits, the Executive is reloaded and immediately accesses the new ExecMsg.bin  No reboot is necessary.
If the Executive or most of the other named programs cannot access the message file or a message within the file, they exit either to the Context Manager or (if the Context Manager is not running) to SignOn with the message:
  Cannot access or use message file. (Error 13506)
This message is not available for editing.
If this error condition occurs during initialization of the Executive, it is necessary to reboot the system from a bootable floppy disk in order to gain access to an Executive on the floppy disk, from which any necessary changes can be made.
{Signon.run, SysInit.run, and ClusterStatus.run, however, retain a full set of English messages within their own code.  In the event of a message file failure, these programs revert to their internal messages and continue execution.}
{In a mixed CTOSII and preCTOSII clustered environment there is an unusual sideeffect.  For example, if a clustered IWS were to give a command to run one of these nationalized programs, and the command file pointed to the hard disk of the master (e.g. Cluster Status), the run file would be loaded, but it would then look for the message file on the local hard disk.  It is therefore recommended that the file, ExecMsg.bin, be copied to [Sys]<Sys> on the hard disk of all cluster workstations.}
{9.2  CREATING A WORKSTATION BOOTABLE BACKUP FLOPPY
A bootable backup floppy allows you to boot from floppy disk and invoke the backup utility to back up your hard disk.  The same floppy can later be used to restore your disk.  As of CTOSII, you now need a pair of floppies to perform the backup or restore.  The first floppy allows you to boot and the second one contains the actual back up and restore run files.}
{As the boot floppy you can use the NGEN Initialization diskette 1 of 2.  To create the backup floppy, path to [Sys]<Sys>, then submit CreateBackupFloppy.sub.}
{Command  Submit
Submit
  File list          CreateBackupFloppy.sub  GO
  [Parameters]
  [Force Expansion?]
  [Show Expansion?]}

{Making a backup floppy for use with QIC tape.

The procedure is almost identical.  Submit CreateBackupFloppy.sub to create the same floppy.  Delete BackupVolume.run and Restore.run from the floppy.  Then, copy TapeBackup.run and TapeRestore.run onto the floppy.  This floppy can also be used to change the volume name of a hard disk.  The file, XBif.run is also placed on the disk since it is needed to be run before using the tape module.  You also need to copy Request.sys onto the boot diskette.  You can copy the one from [Sys]<Sys> on your hard disk, or use the one on disk 7 of 7 of Standard Software.  Request.sys is needed since it supplies the definition of the requests used by the tape module.}
{The following are the steps to using the backup floppy set:
Insert the NGEN Initialization diskette 1 of 2 in the floppy drive.}
Press the reset button at the back of the workstation to reboot.
When the SignOn screen appears, replace the diskette with the backup diskette in drive [f0].
If the upper right hand corner of the screen says, No time date set, enter in a timedate.
Press GO  that is, leave the user name field blank.
{The Executive's Command prompt will appear.  At this point, you have the option of entering any of the following backuprestore commands:

Change Volume Name    IVolume
Backup Volume         Tape Backup Volume
Restore               Tape Restore}
Be sure to run XBif.run if planning to use the Tape backuprestore commands.
{9.3  MERGED SRP AND WORKSTATION UTILITIES
Utilities that formerly had separate run files for SRP and workstation environments have been combined.  The following utilities are affected:}
Append.run
Assembler.run
BadSpotReport.run (formerly MVolReport.run)
BackupVolume.run
BatchStatus.run
ChgVolName.run
Copy.run
CreateDirectory.run
CreatePartition.run (formerly 
                       mCreatePartition.run)
Delete.run
DisableCluster.run
Dump.run
Files.run
LCopy.run
LoadPrimaryTask.run
PLog.run
RemoveDirectory.run
RemovePartition.run
Rename.run
Restore.run
ResumeCluster.run
SelectiveBackup.run
SetDirectoryProtection.run
SetFileProtection.run
SetTime.run
VacatePartition.run
VolumeStatus.run
Commands that invoke these combined utilities are described in the ExecutiveII Manual and the CTOSII System Administrator's Guide.
If your system previously contained SRP versions of the above files with the prefix M, such as MCopy, installation of Standard SoftwareII version 1.0 does not delete these old files.  You can delete them if you wish.
{	                                            
CAUTION
On the SRP, the process of installation renames your old command file and <Cmd>WSAdminAgent.txt file, to <Cmd>Save>WsAdminAgent.txt.  The new file reflects the merged utilities.  For example, the MCopy command now invokes Copy.run instead of MCopy.run

It is suggested that you edit the file so as to enter any specialized commands which may have been in the saved WsAdminAgent.txt into the new one.
	                                            
}
9.4  MISCELLANEOUS INFORMATION
A.	Partition Status:  As of CTOSII, the Operating System supports code sharing.  The best explanation of this is by example.  Suppose you install the Context Manager.  From the CM screen, you invoke Partition Status, and note how much memory is available.  Then you invoke a program, foo, from the CM screen.  You switch back to Partition Status and press the f10 key to update the display.  You find that foo took 100K to run, so the amount of available memory is decreased by 100K.  Then, you invoke a second copy of foo.  Again you return to Partition Status and press the update key.  You will find the amount of memory available does not decrease by 100K, but by less than 100K.  This is because when CTOSII loads a second copy of a run file, only a second copy of the data is loaded, not the code.  So, in this case, 100K is not used up, only the space associated with data for the program, foo.
	When you run Partition Status on CTOSII, you will notice that the names of run files are not displayed for System Services.  This is because of a change in CTOSII  space was saved in the Operating System by elimination the system structure which kept the name of the run file.
B.	Temporary directory:  As of CTOSII, all temporary or dollar sign directories have been combined into one temporary, or the dollar sign directory.  This has many good effects and one bad one. The good side is that a separate dollar sign directory is no longer needed for each user number.  This ensures that any program which uses or creates files in temporary directories will work correctly.

The only shortcoming of this change is in attempting to use wildcarded file specifications in the dollar sign directory.  For example, suppose you go into the Editor and create a file using the file spec, <$>foo.  Further assume that you are running as user number 5.  When you finish out of the editor you would expect to be able to give a Type command giving as a parameter, <$>f*.  However, this will not work.  The reason is that CTOS maps your given file spec into the following file spec, <$>00005>foo.  So, you must do a files command on the <$> directory to find out the real name of the file before you can use a wildcard to abbreviate for the file name.  Programs that give the unexpanded spec will continue to work, however.
C.	ScreenTimeOut:  There is a new keyword that is recognized by SignOn within user configuration files.  You can enter, :SignOnScreenTimeOut:nMinutes, where nMinutes is an integer from 0 to 109.  When you sign on, the SignOn program will read this entry and set the screen time out appropriately.
D.	PLog messages:  The way SRP versions of the half and QIC tape servers log error and installation messages has been changed.  Plog has been changed to reflect this.  This means that Plog will improperly report old tape server messages.  Note, however, that these old messages will not remain in log.sys for very long, since this is a circular log file  the old messages will soon be overwritten with new, properly formatted messages.
	Note also that there is only one version of Plog.run (no mPlog.run.)  This run file will properly report both workstation and SRP log messages and will execute on either workstations or processor boards on the SRP.  There is no reason to make a command mPlog because no speed advantage is gained.  Simply run Plog from a workstation and designate sys in the Volume Name field to get a listing of the SRP's log. 
	The message code formerly written to the log file (log.sys) by the tape servers conflicted with another message code.  With preCTOSII versions of these servers, tape messages had log type FFF8;  They now have type FFF6.
{E.	EditorII:  The algorithm for placing the cursor in EditorII may seem strange when creating a new file and when the cursor is at the end of a file at the end of a line.}
{	The cursor is always placed to the right of the last character entered.  When you use the Editor to create a new file, the cursor appears on the trailing end of file marker (a dashed line).  The cursor will remain there as you enter characters since it continues to be to the right of the last character entered.  Be assured that characters are being entered normally and that this is a normal function.}
{	A similar thing happens when a carriage return is the last character in a file.  In this case the cursor does not wrap to the next line, but instead stays on the same line.  However, the next character entered will cause line wrap and will appear on the next line.} 
F.	Loadable request files:  As mentioned before, CTOSII loads only a single loadable request file, [Sys]<Sys>Request.sys.  When a software package it installed from floppies, its loadable request file(if it has one) is merged into Request.sys by the Install command.  However, for completeness, here is a list of all assigned loadable request files:

	Request.0.Sys*	Unallocated
	Request.1.Sys	Mouse
	Request.2.Sys**	XC002, Tape, Spa, PMOS
	Request.3.Sys	Windows
	Request.4.Sys**	Communications
	Request.5.Sys	PT
	Request.6.Sys	Telephone
	Request.7.Sys	CM and ICMS
	Request.8.Sys	Mail
	Request.9.Sys**	Generic Print

Request.A.Sys through Request.Z.Sys reserved for OEM use except for the following:

	Request.A.Sys	Answering Machine
	Request.I.Sys	ISAM
	Request.M.Sys	Math Server
	Request.P.Sys	PC001
	Request.X.Sys**	XBus
	Request.T.Sys	Telephone Server
	* All future application loadable requests will supplied in Request.0.sys.
	** The request definitions in Request.2, .4, .9, and .X have all been merged into the official Request.sys found on disk 7 of 7 of Standard Software.
G.	For the SRP, a bootable halfinch tape can be made by copying (actually Restoring then Backing up) the files found on the bootable QIC tape.  Once created, it will function exactly the same as the QIC tape for SRP's with halfinch tape drives.
10.0  DOCUMENTATION UPDATES
The following manuals document the new features of version 1.0 Standard SoftwareII.
ExecutiveII Manual, First Edition
EditorII Manual, First Edition
Status Codes Manual, Second Edition
CTOSII System Administrator's Guide, Engineering Update
CTOSII Reference Manual, First Edition

Version 1.0 Standard SoftwareII adds the following status codes:
13500	No such nationalization table
13501	Bad message file signature
13502	Not a message file
13503	Message not found
13504	Message file not open
13505	Message file is corrupt
13506	Cannot access message file

There are three new commands whose documentation should be added to the Executive manual:
Install New Request
Version
Wrap
An explanation of each of these commands is found on the following pages.

__________________________________________________

Install New Request

__________________________________________________
Install New Request is used to merge the contents of a loadable request file or files to the loadable request file, [Sys]<Sys>Request.sys, which is loaded by the Operating System when the system is booted.
Install New Request performs a List Request Set to convert binary loadable requests into text form.  Then it performs a Make Request Set to merge the textual requests back into thier binary loadable form.
This command is implemented by SubCmd.run.

COMMAND FORM
Install New Request
  Binary Request File(s)  ________________________
PARAMETER FIELDS
Binary Request Files(s) Enter the name(s) of the binary loadable request file(s) that you wish to be merged.
__________________________________________________

Version

__________________________________________________
The Version command is used to display the version number(s) of run files.
This command is implemented by Version.run.

COMMAND FORM
Version
  File list  ___________________________________
PARAMETER FIELDS
File list	Enter a list of run files whose versions you wish to determine.
__________________________________________________

Wrap

__________________________________________________
The Wrap command is used to convert data into an object file.  See below for details.
This command is implemented by Wrap.run.

COMMAND FORM
Wrap
  Data  filename     _____________________________
  [Object filename]  _____________________________
  [Module name]      _____________________________
  [Segment name]     _____________________________
  [Public name]      _____________________________
  [Class name]       _____________________________
  [Public]           _____________________________

PARAMETER FIELDS
Data filename	Enter the name of the data file whose contents you wish to wrap.
[Object filename]	      Default: DataFileName.obj
Enter the name of the object file where the wrapped data is to be placed.
[Module name]	          Default: DataFileName
Enter a name to be used as the internal module name.  See the description below.
[Segment name]	          Default: DataFileName
Enter a name to be used as the internal segment name.  See the description below.
[Public name]	          Default: DataFileName
Enter a name to be used as the internal public name.  See the description below.
[Class name]	          Default: DataFileName
Enter a name to be used as the internal class name.  See the description below.
[Public?]	                    Default: No
Enter yes if you wish the resulting module have a public segment name.

Description
The Wrap command is used in place of writing an assembly language program.  If you were writing in assembly language, you could start your source with the following two statements:

segmentname SEGMENT [PUBLIC] [classname]
            PUBLIC  [publicname]
            data file
The names given the the parameters: [Segment name] and [Class name] correspond to the names on the SEGMENT statement.   The name given to the [Molule name] prompt is the name used by the Librarian to refer to the module.  The name given to the [Public name] parameter can be used as the address of the first byte of the data by specifying this name as External in other modules.
{11.0	KNOWN ERRORS AND OMISSIONS

A.	Debugger leaves symbols off if CODED is canceled.  Workaround is to turn symbols back on using CODEF (A104).}
{B.	The Print command [Align form?] option may cause incorrect output.}
{C.	Assembler emits incorrect segment length for ??SEG if no other segments are declared.  Workaround is always to declare at least one segment.}
{D.	Assembler may emit an object that causes Illegal segment reference type 4 at link time.  Workaround is to insert one or more NOP instructions at the location of the illegal segment reference.}
{E.	Spooler supports a maximum of six printers.}
{F.	Queue Manager terminates with Access Denied if [Sys] volume is protected and Queue.index does not include passwords.}
{G.	Command File Editor returns to Executive after encountering any error condition.}
{H.	The Print command [Confirm each?] option does not work from a submit file.}
{I.	Files: The new exclusionary wildcards have a bug.  The exclusionary character tilda (), has an implied wildcard asterisk following it.  For example, if you give a Files command with the following file list:

  * .run

with the intent of listing all files except the specific file, .run, the file list will instead be interpreted as:

  * *.run

that is, all files except those ending in .run.}
{J.	If you run Cluster Status on a master NGEN that has no cluster workstations attached, you will experience an odd behavior.  If you press the f1 key (the Meter function), the master will appear to hang.  If you get into this condition, press Action + Finish to get out of Cluster Status.}
{K.	If you have an NGEN with a graphics module, GC001 or GC003, you can give a Screen Setup command and answer yes to the optional parameter, [Reverse video], to turn the screen into reverse mode.  However, whenever the Executive repaints the full screen (e.g., coming out of the Editor, Word Processor, or Document Designer) the screen will return to the normal video.}
{L.	Partition Status has a limit of 15 partitions.  If you run Partition Status on a workstations which is running more than 15 programs (which is possible if you are running many servers on a master workstation), Partition Status will exit with an erc 3705.}  
{M.	User files: All user configuration files must end with at least one trailing carriage return or the last entry may not be parsed correctly.}
{N.	GPS Installation: The following is a typical segment of a SysInit.jcl file for GPS installation:

$RUN [Sys]<Sys>InstallQMgr.run,y,20
$RUN [Sys]<Sys>GpsRs.run,Anything
$RUN [Sys]<Gps>GpsInstall.run

Note that you must add a parameter to the line where the GPS routing switch is installed.  Failure to do this results in GPS exiting with an error code 4578.  This parameter is the workstation prefix.  In the example Anything was used.}
{O.	If you are running the Executive (or other nationalized Standard Software run file) on a diskless cluster workstation  and the master goes down, messages containing garbled text may appear instead of the message Master not running (error 6).  When the master is brought back up, you need to press Action + Finish to reestablish the message file from the master.}
{P.	If you attempt to use the Command File Editor to create a new command file, when you try to add the first command, you will receive an error message saying that the command file is full.  The workaround is to copy an existing command file and use the Command File Editor to modify it.}
{Q.	The Finish key is interpreted as the Cancel key in Selective Backup and Tape Selective Backup when [Confirm each?] is answered yes.}
{R.	The tape name [QICn] (where n is 0 or 1) is not accepted.}
{S.	If CloseByteStream is called on a communications or printer byte stream subsequent to reception of an XOFF character and before the output buffer is empty, the last few characters of the buffer may never be transmitted.  This situation can be avoided by explicitily calling CheckPointBs.}
{T. 	Pressing ACTIONFINISH while in the Debugger sometimes does either nothing  or causes a system crash.  If the Debugger is permanently resident (:ResidentDebugger:Yes in [Sys]<Sys>Config.sys), this condition does not occur.}
{U.	The Xbif server only allocates the use of the XINTR4 XBUS interrupt, but not XINTR0 and XINTR1.  The PC001 PC emulator and XC002 port expander modules utililize the XINTR0 and XINTR1 levels without any attempt to prevent duplicate use of an interrupt level.  Thus a PC001 may not be installed on a system where an XC002 is also installed.  A future version of Xbif will support allocation of XINTR0 and XINTR1.}
{V.	Signon.run keeps the file ExecMsg.bin open.  This means that an Update to a Remote Master cannot be performed on a system which is already running CTOS II.  To Update the master, perform an UPDATE installation at the master, or turn all cluster workstations off and place the Master in a program such as Create Configuration File, (any program which does not use ExecMsg.bin or create a file in the <$> directory).
W.	Large, complicated macros may cause the Assembler II 1.0 to enter an infinite loop.
X.	Crash messages are scrolled off of the screen at Signon.  These messages may be viewed by looking into Plog.