

	Software
	Release
	Announcement
	

CTOS III
R1.3.1
B25V10









To order additional copies of this document
	United States customers, call Unisys Direct at 18004481424.
	All other customers, contact your Unisys Sales Office.
	Unisys personnel, use the Electronic Literature Ordering (ELO) system.
	
Distribution lists:
SA, SN, SU, SW, PR5
System:	CTOS
Release:	R1.3.1
	October 1995
Part Number:	43597434004
>>>The previous page break contains special footer information.  Do not delete it.
The names, places, andor events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise.  Any similarity or likeness of the names, places, andor events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional.
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT.  Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of duly executed agreement to purchase or lease equipment or to lease software.  The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement.  Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special or consequential damages.
You should be very careful to ensure that the use of this information andor software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice.  Revisions may be issued to advise of such changes andor additions.
RESTRICTED RIGHTS LEGEND.  Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.2277013  and FAR 52.22714 for commercial computer software
Copyright  1995 Unisys Corporation
All Rights Reserved
Unisys is a registered trademark of Unisys Corporation
Context Manager, Generic Print System, TeleCluster, and XBus are trademarks of Convergent Technologies, Inc.
CTOS and SuperGen are registered trademarks of Convergent Technologies, Inc.
BTOS is a trademark of Unisys Corporation.
OFIS is a registered trademark of Unisys Corporation.
Apple, LaserWriter, and Macintosh are registered trademarks of Apple Computer, Inc.  AT, IBM, IBM PC, and OS2 are registered trademarks of International Business Machines Corporation.  Common User Access, IBM PCAT, IBM PCXT, and IBM PS2 are trademarks of International Business Machines Corporation.  Intel is a registered trademark of Intel Corporation.  Lotus 123 is a registered trademark of Lotus Development Corporation.  GWBASIC, MSDOS, and Microsoft are registered trademarks of Microsoft Corporation.  Presentation Manager and Windows are trademarks of Microsoft Corporation.  UNIX is a registered trademark of ATT.  XVT is a trademark of XVT, Inc.
Contents
Section 1	
General Description		1
1.1	File Naming Conventions		1
1.2	Preconfigured Operating Systems		2
1.3	Standards		3
Section 2	
Release Functionality		5
2.1	Hardware Support		5
2.1.1	Support For Adaptec AHA15XX SCSI Card		5
2.2	CTOS and NT Integrated Server		6
2.3	System Configuration File		6
2.3.1	LptWaitForBusy		7
2.3.2	SuppressCommDMABufferCheck		7
2.3.3	fSuppressDMARemote		7
2.4	Status Codes		8
Section 3	
Product Interdependencies		9
3.1	Software		9
3.1.1	Required Software		9
3.1.2	OS Memory Sizing		9
3.2	Hardware		11
3.2.1	Required Hardware		11
3.2.2	Recommended Additional Hardware		11
3.3	Software Compatibility Matrix		12
Section 4	
Migration Requirements		17
4.1	Compatibility with Previous Versions		17
4.2	Hardware Configuration Changes Required		17
4.3	Software Configuration Changes Required		17
4.4	Application Compatibility		18
Section 5	
Corrections		19
Section 6	
Restrictions and Known Limitations		23
6.1	Known Limitations		23
6.1.1	CTOS 		23
6.1.1.1	Configuration File Parameters		23
6.1.1.2	File System		23
6.1.1.3	Debugger		24
6.1.1.4	Keyboard		24
6.1.2	Supported Products		24
6.1.3	System Configuration		24
6.1.3.1	SG4000		24
6.1.3.2	SG60007000		24
6.2	General Information		24
6.2.1	System Administration		24
6.2.1.1	Videoless Server Workstations		24
6.2.1.2	SG1000SG1200 Keyboard		25
6.2.1.3	ICC Block Allocation		25
6.2.1.4	Updates to Configuration File Entries		25
6.2.1.5	Updating the Configuration File		25
6.2.1.6	Configuring with 128MB of Memory		26
6.2.1.7	Adjusting Sysgen parameters		26
6.2.1.8	IO Port Conflict with the ClientCard		26
6.2.1.9	SG1000 and SG1200 Setup Option		27
Section 7	
Support		29
7.1	Introduction		29
7.2	Warranty		29
7.3	Support Category		29
7.4	Support Discontinuance		31
7.5	Product Assistance		31
7.5.1	Instructions		31
7.5.2	Environment		31
7.5.3	Software Components		32
7.5.4	Hardware Components		32
7.5.5	Circumstances		33
Section 8	
Customer Product Information		35
8.1	Overview		35
8.2	CTOS User Documentation		35
8.3	Recommended Additional User Documentation		36
8.4	CTOS Programming Documentation		36
8.5	Documentation Corrections		37
Section 9	
List of Files on Product Media		45
9.1	Contents of the Distribution Diskettes		45
9.2	Required Files		48
Section 10	
Ordering Procedure		49
Section 1	
General Description	
This Software Release Announcement (SRA) describes CTOS III R1.3.1.  It provides a highlevel product feature description and information about support and how to order CTOS III R1.3.1.
CTOS III is a realtime multitasking, messagebased operating system.  It provides a multiuser environment, sophisticated virtual memory management, comprehensive file management, and shared resource processing over the CTOS cluster.
This release of CTOS III introduces support for the CTOS and NT Integrated Server and provides bug fixes for a number of problems.
As this CTOS release is an evolution of the CTOS III R1.2.0 release, it continues to provide full support for the hardware products supported by release R1.2.0.  These include:
	 Multiprocessor operation on the SG4000 and SG6000 80486 based models, and SG7000 Pentium EISA processor models, using the looselycoupled multiprocessor architecture that first debuted on the CTOSXE platform.
	 Support of the SG25003500 ISA based client workstations.  These are highly cost effective CTOS Client cluster workstations based upon industry standard hardware architectures.
	 Support for the SG10001200, the CTOS notebook computers.  These units are supported in both 386 and 486 microprocessor versions with either color or monochrome displays.
	 Continued support for the 80386 based Unisys BSeries of modular CTOS workstations, and their Convergent cousins.
1.1	File Naming Conventions	
This CTOS III release is both a server and a workstation release and is comprised of a variety of files whose names describe the functionality and contents of the file.  The following tables indicate the components from which operating system file names are constructed.
Table 11.  OS Family Type
	
OS Type	Description
	
vSrvr	Virtual memory multiprocessor server operating system
vClstr	Virtual memory client workstation operating system
vClstrlfs	Virtual memory client workstation with local file system operating 
	system
vStnd	Virtual memory standalone or singleprocessor server operating 
	system
Table 12.  OS File Type
	
File Suffix	Description
	
.img	Bootable system image, output of the PMake command
.run	Run file, output of the Linker, input to the PMake command
.sym	Symbol file, output of the Linker
.map	Map of run file content, output of the Linker
.gdt	System image report, output of PMake
.fls	Object list file, input to the Linker
.asm	Sysgen prefix file, input to the Assembler

An operating system file name is formed by the concatenation of a type and suffix from the tables above.  For example, vClstrLfs.img is the name of the bootable system image of a virtual memory client workstation operating system with a local file system.

1.2	Preconfigured Operating Systems	
This release contains four preconfigured virtual memory operating systems.  They are vClstr, vClstrLfs, vStnd, and vSrvr.
vClstr and vClstrLfs are the client workstation operating systems.  vStnd is the standalone OS which may optionally load either the Server Agent or Client Agent to become a vSrvr (singleprocessor) or vClstrLfs OS.  The vSrvr OS is the multiprocessor version of CTOS III which is loaded in the master processor and IOPs in a multiprocessor server.  The vSrvr OS is the only OS which supports multiprocessor operation.  It is suggested that singleprocessor servers boot the vStnd OS and configure it to install the Server Agent.
1.3	Standards	
This release of the CTOS III operating system conforms to and supports the CTOSOpen standard.
Section 2	
Release Functionality	
The following sections present an overview of the new functionality, status codes, and configuration options provided by CTOS III R1.3.1.
2.1	Hardware Support	
2.1.1	Support For Adaptec AHA15XX SCSI Card	
CTOS III R1.3.1 includes support for the Adaptec SCSI card AHA15XX which Unisys sells with the SG2500 machine.  This card also can be installed on EISA machines with Adaptec AIC7770 SCSI controllers on their motherboards.  These include the SG4X00, SG6X00, and SG7X00.
The card will need switch setting changes from the default given in the documentation that was received.  A summary of the changes are listed below:
	Jumper Block J5
		BT  no jumper
	Jumper Block J6
		IC changed from OI to IO which changes the IRQ from 11 to 10.
	Jumper Block J9
		I2, I1, I0, I9 changes from I1 to I0.  Changes the IRQ from 11 to 10.
		BE  no jumper
Care must be taken to assure that port address range and BIOS address location are not used by other boardsresources on the system.  Typically IRQ10 is used by the CTOS Video card (SG260V).  This should not be an issue because most servers will have greater than 12Mb of memory so the CTOS Video card will not be installed.
2.1.2	Support for SG103A SCSI Card (Adaptec AHA1520A)	
CTOS III R1.3.1 includes support for the SG103A SCSI card which previously was available with the SG2500 product.  This card now can be installed on EISA machines which are equipped with  Adaptec AIC7770 SCSI controllers on their motherboards.  This include the SG4X00, SG6X00, and SG7X00 products.  Only one SG103A card can be installed, and only in an EISA based system mentioned above.  The SG103A provides an external SCSI connector, which is not available otherwise on the EISAbased servers, and allows for an additional seven SCSI devices to be connected via this second controller.  The first (integrated) SCSI controller will be the only one which will be used to boot the processor from hard disk.
2.2	CTOS and NT Integrated Server	
This release of CTOS III introduces support for the CTOS and NT Integration Software R1.0.0.  The CTOS and NT Integration Software contains Windows NT drivers, services, and utilities which support the CTOS operating environment on a Windows NT workstation with at least one CTOS IOP card.  The CTOS and NT Integrated Server is a single box solution which supports both the Windows NT and CTOS operating environments simultaneously.  It is implemented as an extension to the looselycoupled, multiprocessor architecture of CTOS III R1.3.1.
2.3	System Configuration File	
The system configuration file parameters are read from the Config.sys file by the operating system during its bootup initialization sequence at each workstation or server.
See the CTOS System Administration Guide for a complete description of all Config.sys entries.
This release of CTOS III adds three new configuration parameters.
2.3.1	LptWaitForBusy	
As a final fix for the slow printing problems on EISA workstations, the following token has been added which can be used to tune the parallel port driver for individual printers.  If your parallel printer seems to be printing slowly, you may raise or lower this value (in increments of 200, but do not set the value below 500).
:LptWaitForBusy: number
where
number is an integer between 500 and 65500
Default: 1500
Example:
:LptWaitForBusy: 1500
2.3.2	SuppressCommDMABufferCheck	
In order to run 64K bits per second on a Comm IOP board, add the following line to your Config.sys file.
:SuppressCommDMABufferCheck: yes
Default: no
Example:
:SuppressCommDMABufferCheck: yes
2.3.3	fSuppressDMARemote	
To allow programs which filter file system requests (such as CTOS NFS) to run on machines with IOP's, the following entry must be made in the IOP processor section where the requests will originate.
:fSuppressDMARemote: yes
Default: no
Example:
:fSuppressDMARemote: yes
2.4	Status Codes	
This release of CTOS III does not add or update any status codes.  See the CTOS Status Codes Reference Manual or the Status Code Reporter utility for detailed information on all status codes.
Section 3	
Product Interdependencies	
3.1	Software	
CTOS III R1.3.1 supports protected and real mode application programs.
3.1.1	Required Software	
CTOS III R1.3.1 systems require Standard Software R12.3.0 or later and VAM R4.2.0 or later.
The Standard Software R12.3.0 (or later) installation media may contain a R1.1.0 release of CTOS III for installation purposes.  The R1.3.1 version of CTOS III will be installed when you install the CTOS III operating system from the Installation Manager menu.  The diskette package, B25VOS, contains the R1.3.1 operating systems.
3.1.2	OS Memory Sizing	
The CTOS III R1.3.1 sizes given below are based on the default configurations provided in the Sysgen prefix files.  These sizes are based upon a 8MB SGS3400 system and do not include memory used by the Paging Service (ps_v.sys) and the standard VGA video driver (vdm_StdVga.run).  No system services, request files, Context Manager or Debugger are installed.
An approximation of the minimum operating system size can be obtained by adding up the size of the operating system, the paging service, and the video code.
All sizes are in kilobytes and are approximate.
The Paging Service (ps_v.sys) varies in its memory usage based upon the amount of free memory it controls.  In approximate terms, the Paging Service uses an additional 4K for each 100k of additional free memory. 
	Component			Memory Used

	vSrvr (vStnd and Srvr.sys)	1396K
	vStnd	1271K
	vClstr	852K
	vClstrLfs	1110K

	vSrvr* (master processor)	2130K
	vSrvr* (Cluster IOP)	1100K

	Debugger	150K
	video	250500K
	Paging Service	220K
*  In a multiprocessor system the amount of memory used depends on the number and size of the transfer blocks defined.  See the CTOS Administration Guide for more information.
3.2	Hardware	
3.2.1	Required Hardware	
A 8038680486 processor is required (e.g. B38CP003, B39386i, SG2000, SG5000).  Additional hardware supported by CTOS III R1.3.1 includes the SG1X00, SG2X00, SG3X00, SGS3X00, SG4X00, SG6X00, and SG7X00 systems.
Minimum RAM for diskless client workstations: 2MB
Recommended RAM for client workstations: 4MB
Recommended RAM for server workstations: 8MB
Note:  On B38 workstation servers with 4MB RAM and all singleprocessor workstation servers, the vStnd CTOS III with the loadable Server Agent is recommended.
3.2.2	Recommended Additional Hardware	
A minimum of 8MB of RAM is recommended.
A 40MB or larger system (hard) disk is recommended.  Unisys systems with a built in system disk will have significantly higher capacity than this minimum.
3.3	Software Compatibility Matrix	
Table 1 notes the minimum versions of software products that are compatible with CTOS III R1.3.1 running on the SuperGen Server Family (SGS3X00, SG4X00, SG6X00 and SG7X00) and other Unisys CTOS workstations.  For minimum versions of Software qualified on the Integrated Server, please reference the SRA for CTOS and NT Integration Software, part number (46194270000)
Table 1.  CTOS Products
	
		SG4X00	
Product	Version	SG6X00	SGS3X00	Other
		SG7X00
				

Access Control	2.0	Y	Y	Y
Access User Management	2.0	Y	Y	Y
Ally Development  Runtime	3.0.4	Y,4	Y	Y
Asynchronous Terminal Emulator	5.7	Y	Y	Y
Batch Manager II 	2.4	Y	Y	Y
BLAN 	3.1	N	N	Y
BSC RJE	6.2	Y	Y	Y
BMulti	10.4	Y,6	Y	Y
BTOS BNA	11.7	Y,7	Y,7	Y
BNA STI	1.0.1	Y	Y	Y
BNet II	3.1	Y	Y	Y
BTE	3.1	Y,1,3	Y1,3	Y,1,3
C Compiler	1.2	Y	Y	Y
Cobol Compiler and Runtime	5.4	N	N	N
Cobol2 Runtime and Compiler 	1.2.5	Y	Y	Y
Context Manager II	5.0	Y,4	Y,2	Y,2
CTOS Presentation Manager	1.1	Y	Y	Y
Data Availability Service	1.0.3	Y,4	Y	Y
Desktop Plus	1.0.0	Y	Y	N
DTS 	5.05.1	N	N	N
DCA Transport	4.3	Y	Y	Y
Device Server	6.2	Y	Y	Y
Device Service	7.3.1	Y	Y	Y
EMS	1.0.0	Y	Y	Y
Enhanced BSC 3270	8.1.3	Y	Y	Y
Enhanced Multiplan	2.2.4	Y	Y	Y
Enhanced SNA 3270 Terminal Emulator	10.0	Y,2	Y,2	Y,2
File Transfer	3.2	Y	Y	Y
Font Designer	6.3	Y	Y	Y
Forms 	6.4	Y	Y	Y
	
		SG4X00	
Product	Version	SG6X00	SGS3X00	Other
		SG7X00
				

FSAFinesse	5.0.2	Y	Y	Y
FSAFinesse	4.0.2	Y	Y	Y
FSAFinesse	2.1.14	Y	Y	Y
Generic Print System (GPS)	2.7.0	Y	Y	Y
Info Connect TCPIP Access	1.0.0	Y	Y	N
ISAM III	1.2.0	Y	Y	Y
ISAM II	1.2.0	Y	Y	Y
Integrated Event Monitor	2.3	Y	Y	Y
IDMSS	5.2.0	NA	NA	6
ISBTOS	1.0.4	Y	Y	Y
ISDN Service	1.0	Y	N	Y
LANceLM	1.1	Y	Y	Y
LANceNW	1.0	Y	Y	Y
LANcePC	1.1	Y	Y	Y
Mapper	4.1.3	Y,2,4	Y,2	Y,2
Message Control System	4.6	Y	Y	Y
Message Control System II	2.0.0	Y	Y	Y
Microsoft C	6.1	Y	Y	Y
Microsoft Macro Assembler	5.1	Y	Y	Y
Mobile OFIS Mail	1.0.0	Y	Y	Y
Modem Service	5.3	Y	Y	Y
Multi Gateway Server	1.2	Y	Y	Y
Network File System	1.1.3	Y	Y	Y
OFIS Access TelexTwx	2.2	Y	Y	Y
OFIS Access X.400	1.1	Y	Y	Y
OFISBridge DCA Translator	1.2	Y	Y	Y
OFIS DCADEF	2.0.2	Y	Y	Y
OFIS Dictionaries	3.0	Y	Y	Y
OFIS Dictionaries	4.0	Y	Y	Y
OFIS Document Designer	3.1	Y,2	Y,2	Y,2
OFIS Document Writer	1.1	Y	Y	Y
OFIS Graphics	3.0	Y,2	Y,2	Y,2
OFIS Mail	8.2	Y	Y	Y
OFIS Spreadsheet	2.1.0	Y	Y	Y
Oracle 6.0	6.0.3	Y,4	Y	Y
	
		SG4X00	
Product	Version	SG6X00	SGS3X00	Other
		SG7X00
				

OSI FTAM	1.1.1	Y	Y	Y
OSI MHS Mail Manager	1.2	Y	Y	Y
OSI MHS Mail Server	1.2	Y	Y	Y
OSI Session	2.0	Y	Y	Y
OSI Transport LAN	2.4	Y	N	Y
OSI Transport WAN	2.0	Y	Y	Y
Pascal Compiler	7.0.1	Y	Y	Y
PEM Server	6.2	NA	N	5
Phone Memo Manager	1.2	Y	N	Y
Picture Library	2.1	Y,2	N	Y,2
PollSelect Terminal Interface	4.6	Y	Y	Y
Remote Access Facility	3.2	Y,4	Y,2	Y
Raster FontIcon Designer	10.0	Y,2	Y,2	Y,2
Scaling Font Service	1.0	Y	Y	Y
Screen Font Database	1.4	Y	Y	Y
SNA BNet Transport Service	1.0	N	N	N
SNA LUIS	3.1.0	Y	Y	Y
SNA LU 6.2	6.0	Y	Y	Y
SNA Distribution Services	1.0.3	Y	Y	Y
SNANM Distribution Manager	1.0	Y	Y	Y
SNANM Entry Point Service	1.0.3	Y	Y	Y
SNA RJE	3.3.1	Y	Y	Y
SNA Transport	3.0	Y	Y	Y
SNAT (SDLC)	3.0	Y	Y	Y
SNAT (SNA X.25)	3.0	Y	Y	Y
SNAT (Token Ring)	3.0	Y	N	Y
Software Distribution	4.0.0	Y	Y	Y
Standard Software	12.3.0	Y,9	Y	Y,9
System Service Monitor	1.1	Y,4	Y	Y
TCPIP	2.2	Y	Y	Y
UPS Service	1.12.3	N	N	Y
UTS Emulator	1.3.2	Y	Y	Y
Video Access Method	4.2	Y	Y	Y
Version Control	1.1	Y,4	Y	Y
Virtual Terminal Emulator	2.2	Y	Y	Y
CTOSVpc	1.3	Y	Y	Y
CTOSVpc	2.0	Y	Y	Y
X.21 Circuit Switching Service	1.2.10	N	Y	5,8
X.25 Network Gateway	10.0.9	Y	Y	Y
XVTCH System Service	2.1.8	Y	Y	Y
NOTES:
Y	The product runs on the indicated hardware.
N	The product does not run on the indicated hardware.
NA	The product is not intended for the indicated hardware.
1	Printing not supported on the asynchronous port.
2	Requires CTOS VideoCard (SG260V) for CTOS graphics support on pcbased SuperGen hardware.
3	Requires CTOS VideoCard (SG260V) for CTOS character map support on pcbased SuperGen hardware (attributes, character fonts).
4	Does not run on IOP Cards.
5	Only runs on B3x hardware.
6	TDI is only supported on the main processor of the SG467000 servers.  TDI is not supported on IOPs.
7	BNA supported only over X.25 on SG467000 servers.
8	X.21 requires B25ID2 module on NGen workstations.
9	The following Standard Software services do not run on IOP boards:
	Sequential Access Service	CDROM Service
	MCR Service	DCX (Data Comm) Service
	Screen Print Service	Mouse Service
	The following Standard Software services do not run on any SuperGen workstations:
	CFA Server Service	CFA Workstation Agent
	CFA File Filter	XBif Service
	XC002 Service 
Section 4	
Migration Requirements	
4.1	Compatibility with Previous Versions	
CTOS III R1.3.1 is compatible with CTOS I 3.4, CTOS II 3.4, CTOS III 1.01.11.2, and CTOSXE 3.4 at the cluster (work group) level.
4.2	Hardware Configuration Changes Required	
CTOS III requires, as a minimum, an 80386 processor with at least 4MB of RAM.  On the SG400060007000, 8MB is recommended for multiprocessor server workstations.
4.3	Software Configuration Changes Required	
The system configuration file has two new options in this release.  See Section 2.3 of this document for more information.
R12.3.0 or greater Standard Software is required in order to overwrite run files (e.g. via LCopy) of currently executing programs.  This is necessary because the Paging Service keeps run files open in modeRead.  R12.3.0 Standard Software uses new file system operations that support this feature.
4.4	Application Compatibility	
The following changes have been made which could affect an application program:
	The Vf structure has been expanded to describe additional features which are supported in this release.  The documentation for those flags which may be useful to the user follows:
		Offset	Flag Name	Meaning if flag is true
		44	fPentium	Executing on a Pentium (tm) processor.
	45	fXpress	Executing on an SG41xx61xx71xx 
			processor.
	47	fNThost	Host processor (motherboard) running 
			WindowsNT.
	The internal version number of CTOS has been updated for this release.  The major revision is thirteen (13) decimal, the minor is three (3) decimal.  These numbers can be obtained via the CurrentOsVersion procedural interface call.
Section 5	
Corrections	
The following problem items have been closed with this release:
PLE 16221805	GetUserStatus does not return node name.
PLE 16229121	Erc 80 with bidirectional parallel scanner in OFIS Imager.
PLE 16230197	Context Manager erc 80 when swapping contexts.
PLE 16271934	QuerySwitchsDAI gets erc 7 on vSrvr and vClstr, works on vClstrLfs.
PLE 16288993	GetUCB crashes if passed an Allocated User Number.
PLE 16290769	ReadStatusLPT gives different results on different processors.
PLE 16290947	GetUserStatus returns erc 33 on GP00 (XE) or EP00 (IOP).
PLE 16293211	GP fault in QuietProcess when the user presses ACTION+FINISH.
PLE 16323586	CODENEXT PAGE can leave the executive unuseable.
PLE 16324744	XBlock size of 12K results in too many cluster errors.
PLE 16324752	Poor cluster response from SGS3400 server.
PLE 16325481	Large number of REJECTs on CommIOP running X.25 at 64KBPS.
PLE 16327212	Realmode programs often terminate with erc 400.
PLE 16336505	Erc 13960 occurs frequently when doing a print job from Word for Windows 6.0.
PLE 16359688	SG350066Mhz SCSI disk as D0, system does not boot after crash dump.
PLE 16379212	AgentCache not functional.
PLE 16394602	B38CPU with vSrvr 1.2.10 keyboard locked up when traffic on cluster line.
PLE 16394769	CTOS Volume password required to access DOS partition.
PLE 16395927	Slow parallel printing on SG7100, SG6000, and other EISA servers.
PLE 16399965	ReadKbdDirect works differently on CTOS III vs CTOS II.
PLE 16410586	Accessing remote files is impossible for clustered workstations.
PLE 16415588	GetUserStatus for user 1 (primary partition) returns erc 33 on vSrvr.img.
PLE 16418323	Error B4 when cluster workstation booting.
PLE 16418471	Slow printing on s1.2.21 CTOS III.
PLE 16424331	Keyboard LEDs get out of sync when bad parameters are entered.
PLE 16436259	Fatal crash Erc 404 in scheduler using large @ file with wild card directories.
PLE 16438979	Problems getting parallel printer online if connected to SG2500.
PLE 16448877	s1.2.22 cannot print large documents  characters are dropped.
PLE 16457591	SG3500 Parallel port does not initialize correctly.
PLE 16461946	ReadHardID occasionally returns an incorrect erc 696.
PLE 16472549	Cannot boot SG3500 with CTOS III s1.2.24 Srvr.sys and x2.2.0 firmware.
PLE 16472689	Crash when booting using s1.2.22 Srvr.sys.
PLE 16482153	Slow printing on parallel port with CTOSIII 1.2.24.
PLE 16495531	Keyboard unencoded state does not recover LED state after emulation.
PLE 16495557	Paging Service crash during OS initialization.
PLE 16478351	Erc 405 with realmode program under CTOS III s1.2.24.
PLE 16229539	Occasional erc 91 from NULL process.
PLE 16491012	Erc 80 crash in MassIo.
PLE 16261858	Cluster status displays wrong size for XBlocks.
PLE 16445860	Cannot see server tape drives if cluster system has local tape drive.
PLE 16505013	Crash Erc 12 caused by LPT interrupt service routine.
PLE 16376591	Documentation correction, see section 8.5.
PLE 16285901	Documentation correction, see section 8.5.
PLE 16296066	Documentation correction, see section 8.5.
PLE 16300853	Documentation correction, see section 8.5.
PLE 16281743	Documentation correction, see section 8.5.
PLE 16502901	Documentation correction, see section 8.5.
PLE 16536687	Produced a double character on the numeric key pad of the German SG102K keyboard.
PLE 16455865	Erc. 19 crash when switching contexts.
PLE 16090204	Cannot Disable Cluster from a SG4000 client.
PLE 16568121	 System crash caused by fix for erc 19
PLE 16465402	Numerous problems with stale data after the cluster line goes downup.
PLE 16565296	File system does not accumulate totals for SCSI disk errors.
PLE 15908033	Keyboard hangs after invoking VPC and entering the CTOS debugger.
PLE 16539741	Context Manager hangs in CMInvoker recovering from downed cluster
PLE 16576549		Erc 1114 when loading DLLs even with sLoaderHeap=65500
PLE 16583421	The erc 19 crash occur again with s1.2.31 OS.	
PLE 16585386	Unable to boot 128 Ctos diskless workstations	
Section 6	
Restrictions and Known Limitations	
6.1	Known Limitations	
6.1.1	CTOS 	
For this release there may be less real mode memory available for real mode applications.  This is due to the trade for increased functionality.  Real mode memory availability is also greatly determined by the operating system and hardware configuration.  It is strongly advised that all applications be ported to protected mode.
6.1.1.1	Configuration File Parameters	
The :ClusterTimeOut: parameter, if defined in the Config.Sys file, is not read properly and remains set to the default value in the vClstrLfs version of the operating system.  It is read and set  properly in the vStnd version when the Client Agent is loaded through the Config.Sys file.
The :OSNameSrvr: parameter, if defined in the Config.Sys file, must not have an operating system version string that is greater than 49 characters.  Strings longer than this may cause a Status Code 501 to occur during system initialization or while signing on to the system.
6.1.1.2	File System	
Under some conditions where the SCSI bus is heavily loaded and several SCSI devices are being concurrently exercised, the B25DDS module may encounter a status code 389 (SCSI timeout).  This exception has a high MTBF, occurs only on heavily loaded systems, and should rarely be encountered in the course of normal system operation.  However, should this error be experienced, reducing the load on the SCSI bus (by exercising fewer SCSI devices simultaneously) should correct the problem.
6.1.1.3	Debugger	
When using the CTOS debugger on EISAISA workstations without the CTOS Video Card, the use of the Debugger command CodeI is not supported.
6.1.1.4	Keyboard	
The following limitations apply to any machine equipped with an SG260A IBus converter.
The count of bytes sent to WriteIBusDevice is limited to 32.
6.1.2	Supported Products	
BNet II 3.1 is required for loading run files and DLLs over the network.
6.1.3	System Configuration	
6.1.3.1	SG4000	
In an SG4000 that has a 66 MHz CPU board, an IOP board will not fit in slot 6 next to the CPU board.
6.1.3.2	SG60007000	
IOP boards are not supported in slot 8 of an SG60007000 as it is not a bus master slot.
6.2	General Information	
6.2.1	System Administration	
6.2.1.1	Videoless Server Workstations	
This release of CTOS III R1.3.1, along with VAM R4.2.0 and Standard Software R12.3.0, supports headless server operation.  This means that a server workstation can run without a monitor and keyboard.  See the chapter on Implementing System Security in the System Administration Guide for instructions on configuring a headless system.
RKVS is loaded when VAM has detected that the system is headless.  There are some configurations in which VAM cannot detect the absence of a monitor.  If RKVS is not loaded automatically, then it can be loaded through [Sys]<Sys>SysInit.Jcl.  See the VAM R4.2.0 SRA for the headless restrictions.
6.2.1.2	SG1000SG1200 Keyboard	
The default keyboard tables for the SG1000 and SG1200 have been modified to define the '\' (backslash) key as the GO key.  The current ALTENTER sequence is also supported.  ALT used in combination with the '\' key produces '\' (backslash) character and ALTSHIFT with the '\' produces the '|' (bar) character. 
6.2.1.3	ICC Block Allocation	
The ICC transfer blocks for outgoing requests (e.g. zblockOut) for each IOP are allocated in the master processor's memory.  In a system with a large number of IOPs the user may want to configure the number of blocks in the Config.Sys file to reflect each IOP's need for outgoing ICC blocks.  Use the Multiprocessor Statistics utility for statistics on system block usage.  See the System Administration Guide for configuration information.
6.2.1.4	Updates to Configuration File Entries	
The following configuration file entry defaults have been updated for this release: 
    :SuppressPmDefault: defaults to yes on the IOP.
    :LibrarySearchPath: defaults to [Sys]<PMDLL>, [Sys]<Sys>
6.2.1.5	Updating the Configuration File	
When modifying the Config.sys file, it is recommended that the user first modify a copy of the configuration file and use the new Bootstrap command to test it before overwriting [Sys]<Sys>Config.sys.
6.2.1.6	Configuring with 128MB of Memory	
On SG400060007000 with 128MB of memory, it may be necessary to modify the system CMOS so that the 1Mb video aperture is disabled.  The system CMOS is modified by booting the System Configuration Utility (SCU) diskette that comes with the system.  Once in the SCU, select the Configure Computer option and then the View or Edit Details option.  Select the Embedded System Display, and then disable it in the Graphics Engine Memory Aperture selection.  Save the configuration in CMOS.
6.2.1.7	Adjusting Sysgen parameters	
You may need to use the Mini Customizer utility to adjust some Sysgen configuration parameters:
	When configuring a single processor workstation as a
	server using the vStnd operating system, you may need to
	increase the number of File Allocation Blocks if status code
	213 occurs.
	When booting a vStnd operating system with Clstr.sys to form a
	vClstrLfs system, the operating system will be larger than an 
	actual vClstrLfs.  This is because the vStnd Sysgen parameters
	have been chosen to work effectively for both a server and a client
	workstation configuration.  You can reduce some of the extra 
	memory used by using the Mini Customizer utility, or you can 
	directly change the Sysgen parameters and rebuild the operating 
	system.
The Customizer utility, Customizer.run, is fully described in the CTOS System Administration Guide.
6.2.1.8	IO Port Conflict with the ClientCard	
On the SG400060007000 systems the communications port B can be configured to be controlled by the 85C30 serial communications controller (:ECOM:RS232).  The IO addresses used by the 85C30 (100h11fh) conflict with the default IO addresses used by the ClientCard.  So, if both the ClientCard and :ECOM:RS232 are to be used, the ClientCard IO addresses have to be changed.  This is done by changing the switch settings on the ClientCard.  See the hardware installation guide for details.
6.2.1.9	SG1000 and SG1200 Setup Option	
Some versions of the SG1000 and SG1200 firmware BIOS have an option, in the Setup utility, to enable an external floppy diskette drive B.  If this option is set to other than none, a delay of up to two minutes will be introduced when CTOS is booting.
Section 7	
Support	
7.1	Introduction	
This section describes Unisys warranty, support category, and assistance provided by CTOS III R1.3.1.
7.2	Warranty	
CTOS III R1.3.1 is a warranted Unisys software product.
Unisys warrants that CTOS III R1.3.1, in its unaltered form, will substantially conform to Unisys current published functional specifications when used in Unisys supported configurations.  The customer is responsible for reporting suspected deviations using the User Communication Form (UCF) process within ninety (90) days following delivery.  The product is neither field repairable nor field modifiable.  Corrections to reported deviations are provided to the user via updated code files.
This standard warranty is not a substitute for Unisys Service Agreement offerings.
7.3	Support Category	
CTOS III R1.3.1 is fully supported by Unisys.
Support services for CTOS III R1.3.1 are offered under the SURETY (United States) or Ala Carte (International) support programs and are consistent with the support services offered for the entire CTOS Hardware and Software family of products.
Unisys SureNet is an electronic bulletin board service, providing customers in the United States access to technical information seven days a week, 24 hours a day.  SureNet Technical Information Services are available at no additional cost to customers with a current Unisys service agreement or software license and include access to system alerts, customer technical bulletins, and online UCF entry.  Registration is required.  SureNet Support Services are available on an annual subscription basis.  For more information, contact Unisys Direct at 18004481424, prompt 5.  You may register for Technical Information Services andor Support Services either online by dialing 18008288796 (8 data bits, 1 stop bit, no parity, asynchronous, VT100 emulation) or by calling Unisys Direct.
If you need further assistance or information regarding support services, please contact your Unisys representative or your local Unisys office.
7.4	Support Discontinuance	
Support for CTOS III releases prior to R1.3.1 will be as follows:
	CTOS III R1.2.x will be supported until the next major release
	of CTOS III.  Priority A problems will be responded to as
	usual and maintenance releases will be provided to correct
	Priority B problems.
	CTOS III R1.1.x will be supported for six (6) months following
	the release of CTOS III R1.3.1.  Priority A problems will be 
	responded to as usual.  No maintenance release will be produced
	for correction of Priority B problems; Priority B problems will be
	addressed by providing CTOS III R1.3.x maintenance releases.
	CTOS III R1.0 is no longer supported.
7.5	Product Assistance	
The following sections describe how to get assistance if you need help and list information you should provide if you experience a problem.
7.5.1	Instructions	
Should you encounter a problem with a Unisys product, please contact your local Customer Service Center.  Your Customer Service Center representative will have a more definitive set of problem reproduction requirement guidelines specific to the application you are running .  So that your questions may be answered in a timely manner, please collect all information which applies to your problem.  A guideline for gathering information is listed below or you may reference the Product Validation Profile (PVP) in the PRIMUS database for more product specific UCF submission requirements.
7.5.2	Environment	
To assist us in determining the nature of your problem, please be prepared to describe the system environment in which the problem occurs.
7.5.3	Software Components	
If you suspect the problem is software related, be prepared to answer the following questions concerning the software being used:
1.	The version number of the software in which the problem occurs.
2.	The version of the operating system software.
3.	Installation parameters used for the failing software.
4.	Configuration files used.
5.	Other software installed at the time of failure.
6.	Recent changes to the system software (updates, other).
7.	Any messages associated with the failure that appear in the system log file (accessed through the Plog command).
8.	The connectivity of the software (is your system part of a network?).
9.	The hardware configuration.
7.5.4	Hardware Components	
If you suspect the problem is hardware related, be prepared to answer the following questions concerning your hardware platform:
1.	The type of processor being used (B38, B39, SG2000, SG5000, other).
2.	The workstation components (hard drives, communication modules, CDROM drive, other).
3.	Any peripherals attached to the workstation (printers, scanners, modems, plotters, other).
4.	The connectivity of the hardware (is your system part of a network?).
5.	Recent changes to the hardware platform.
6.	The amount of memory installed.
7.5.5	Circumstances	
Be prepared to describe the circumstances under which the failure occurs.  The description should include:
1.	Is the problem reproducible?
2.	What are the exact steps required to reproduce the problem?
3.	Under what circumstances does the problem not occur?
Section 8	
Customer Product Information	
8.1	Overview	
A complete set of operating system user documentation is shipped with each copy of the CTOS Standard Software media you purchase.  The same set of documentation is used for CTOS III, the real mode and protected mode versions of the CTOS II workstation operating system, and for the CTOSXE shared resource processor operating system, when they run Standard Software R12.3.
A complete set of programming documentation for CTOS III R1.3.1 is shipped with the R12.3 Development Utilities software media package.  The Development Utilities package contains the programming tools and libraries for the CTOS realmode, protectedmode, and virtualmemory workstation operating systems and for the shared resource processor operating system.  The same set of documentation is used for the virtual memory CTOS III operating system, the protectedmode versions of the CTOS II workstation operating system, the CTOSXE shared resource processor operating system, and the realmode CTOS I operating system.
8.2	CTOS User Documentation	
This subsection lists the user titles for CTOS III R1.3.1.  For descriptions of the manual contents see the CTOS Standard Software Software Release Announcement.
Additional copies of the complete CTOS Standard Software Library, which consists of all the titles listed below, are available through ELO using a single order number, 4357 7725301.
Part Number	Manual Name
4357 4516301	CTOS Operating System Documentation Directory
4357 4581301	CTOS System Software Installation Guide
4357 6248000	CTOS Media User's Guide
4357 4391000	CTOS Executive User's Guide
4357 4540300	CTOS Executive Reference Manual
4357 4599301	CTOS System Administration Guide
4358 6940201	CTOS Cluster and Network Hardware Installation Guide
The CTOS III Interactive Tutorial:  Introducing the Executive is overpacked with the CTOS III operating system media package.  The tutorial works on any workstation running CTOS I 3.4, CTOS II 3.4, CTOS III R1.1 or CTOS III R1.2.0 or CTOS III R1.3.1.  It is not separately orderable.
8.3	Recommended Additional User Documentation	
You can use the Status Codes Reporter command on your workstation to view the description of any status code known at the time of this release.  Boot errors formerly included in the CTOS Status Codes Reference Manual are described in an appendix in the CTOS System Administration Guide.
If you want to, you can also order the CTOS Status Codes Reference Manual using part number 4164 1366200.  It is not included with the software.
8.4	CTOS Programming Documentation	
This subsection lists the programming titles for CTOS III R1.3.1.  For descriptions of the manual contents see the CTOS Development Utilities Software Release Announcement.
Additional copies of the CTOS Development Utilities and Programming Library, which consists of all the titles listed below, can be ordered using a single order number, 4357 7733201.
Part Number	Manual Name
4585 9493000	CTOS Programming Utilities Reference Manual:  Installation and Command Overview
4359 4951000	CTOS Programming Utilities Reference Manual:  Assembler 
4359 4969100	CTOS Programming Utilities Reference Manual:  Building Applications
4586 3966000	CTOS Programming Utilities Reference Manual:  Customization
4357 9523102	CTOS Debugger User's Guide
4357 4524100	CTOS Editor User's Guide
4120 5154800	CTOS SortMerge Programming Reference Manual
4357 9507200	CTOS Operating System Concepts Manual
4357 9515100	CTOS Programming Guide
4357 4342200	CTOS Procedural Interface Reference Manual
4586 3933000	CTOSOpen Programming Practices and Standards, Application Design, Draft 2.0
8.5	Documentation Corrections	
PLE 16281743  The CTOS Procedural Interface Manual, Volume 3, page 31497 shows a table of values which are used to turn various signals ON and OFF.  The entry for the signal DTR is reversed.
	To turn DTR ON, the value is 0.
	To turn DTR OFF, the value is 1000h.
PLE 16285901  In the CTOS Procedural Interface Manual, Volume 1, page 3486, the documentation shows that the length for the Partition Descriptor is 33 bytes.  But in Volume 4, page 4195, which shows the layout of the Partition Descriptor, the length is 41 bytes.  Volume 4 is correct, so page 3486 should be changed.  Also, the documentation (4194) indicates that the only field in the Partition Descriptor that is valid for protected or virtual OS's is the sbPartitionName.  This is not the case.  The wording should read:
For protected and virtual mode OS's, the following fields are not maintained, and are therefore not valid:
	Bytes 415  segment addresses are not maintained and are not valid.
	Bytes 3841  segment addresses are not maintained.
All other fields are valid and maintained by both CTOS II and CTOS III.
PLE 16296066  The CTOS Programming Guide, Volume 2, on page 1710 refers the reader to an archive on a diskette which is distributed with the manual for some example programs that can be restored.  There is no diskette distributed with the programming guide.
PLE 16300853  The documentation (page 1621) in the CTOS System Administration Guide does not correctly or thoroughly describe the :ECOM: parameter, and has led to some confusion.
The :ECOM: parameter can be set to one of three values:
:ECOM: (no value, or parameter omitted)  specifies that the [comm]B port will be treated as an industry standard ASYNChronous port.
:ECOM: TDI  specifies that the [comm]B port will be treated as a Burroughs twowire direct port.  There are also some jumpers which must be set to use the port in this fashion.
:ECOM: RS232  specifies that the OS software will use the INTEL 8530 communications controller chip to control [comm]B.  This option is required for SYNChronous communications, and also for some ASYNChronous packages such as BMULTIPSTI.
The parameter must be specified in the :Processor: Default section of Config.sys or anywhere outside the processorspecific sections.  If it is placed in the :Processor: EP00 section, then the value specified will only apply when the server OS is booted.  For the vClstrLfs OS, you must place the :ECOM: parameter in either the :Processor: Default section or outside the processorspecific sections.
PLE 16376591  Some of the offsets for the Volume Home Block have been documented incorrectly, the correct VHB offsets are as follows:
Offset	Field	Size (bytes)
	0	checksum	2
	2	lfaSysImageBase	4
	6	cPagesSysImage	2
	8	lfaBadBlkBase	4
	12	cPagesBadBlk	2
	14	lfaCrashDumpBase	4
	18	cPagesCrashDump	2
	20	volName	13
	33	volPassword	13
	46	lfaVhb	4
	50	lfaInitialVhb	4
	54	creationDT	4
	58	modificationDT	4
	62	lfaMfdBase	4
	66	cPagesMfd	2
	68	lfaLogBase	4
	72	cPagesLog	2
	74	currentLogPage	2
	76	currentLogByte	2
	78	lfaFileHeadersBase	4
	82	cPagesFileHeaders	2
	84	altFileHeaderPageOffset	2
	86	iFreeFileHeader	2
	88	cFreeFileHeaders	2
	90	clusterFactor	1
	91	bECC	1
	92	defaultExtend	2
	94	allocSkipCnt	2
	96	lfaAllocBase	4
Offset	Field	Size (bytes)
	100	allocPageCnt	2
	102	lastAllocPg	2
	104	lastAllocWd	2
	106	lastAllocBit	2
	108	cFreePages	4
	112	iDev	2
	114	oMfdFcb	2
	116	seekStepRate	1
	117	gapSize	1
	118	writePrecompCylinder	1
	119	devType	1
	120	spiralFactor	1
	121	startingSector	1
	122	interleaveFactor	1
	123	verifyCode	1
	124	rgbVhbEx	95
	219	magicWd	2
	221	bootBaseSector	1
	222	bootBaseHead	1
	223	bootBaseCyl	2
	225	bootMaxPageCount	2
	227	badBlkBaseSector	1
	228	badBlkBaseHead	1
	229	badBlkBaseCyl	2
	231	badBlkMaxPageCount	2
	233	crashDumpBaseSector	1
	234	crashDumpBaseHead	1
	235	crashDumpBaseCyl	2
	237	crashDumpMaxPageCount	2
	239	bytesPerSector	2
	241	sectorsPerTrack	2
	243	tracksPerCylinder	2
	245	cylindersPerDisk	2
	247	volumeCapacity	4
	251	reserved	5
PLE 16376591, cont'd
On page 4343 of Volume 4 of the Procedural Interface Manual the following fields should also have a ** by them to indicate that they are nonzero only if the VHB is for a physically addressed device:

bytesPerSector, sectorsPerTrack, tracksPerCyl and cylindersPerDisk
PLE 16502901  Some of the offsets for the Communications Status Buffer (returned from the GetClusterStatus request) were documented incorrectly, the correct fields and offsets are as follows:
Server Workstation Information
Offset	Field	Size (bytes)
	0	fDisableCluster	1
	1	revisionLevel	1
	2	nWsActive	2
	4	nWsTotal	2
	6	nXBlocksFree	1
	7	nXBlocksSmallFree	1
	8	nCrcError	2
	10	nOverrunError	2
	12	nSequenceError	2
	14	nProtocolError	2
	16	nAddressError	2
	18	nLengthError	2
	20	nTimeout	2
	22	nWsDownTimeout	2
	24	nWsDownErrors	2
	26	nWsBootRequest	2
	28	nWsBootComplete	2
	30	nWsAccessLinkRequest	2
	32	nWsDumpRequest	2
	34	nWsDumpComplete	2
	36	maxTicksBetweenPolls	2
	38	nSnrm	4
	42	nSnrmReply	4
	46	nSnrmErrorReply	4
	50	nFalseTimeout	2
	52	nXBlockWaits	4
	56	nXBlockSmallWaits	4
	60	nIFramesRrIn	4
	64	nIFramesRnrIn	4
	68	nIFramesRrOut	4
	72	nIFramesRnrOut	4
	76	nPagesRead	4
Offset	Field	Size (bytes)
	80	nPagesWritten	4
	84	statIdleTicksLastSec	2
	86	statIdleTicksLast10Sec	2
	88	statsSecondsLow	2
	90	statsSecondsHigh	2
	92	ntimespolled	4
	96	nRnrInLow	2
	98	nRnrInHigh	2
	100	nRrInLow	2
	102	nRrInHigh	2
	104	nRnrOutLow	2
	106	nRnrOutHigh	2
	108	nRrOutLow	2
	110	nRrOutHigh	2
	112	statsfHighSpeed	1
	113	statsSbVerRun	31
	144	ticksPerSecond	2
	146	ticksSinceLastPoll	2
	148	timelastpolled	4
	152	nXBlocksTotal	2
	154	nXBlocksSmallTotal	2
	156	saPerXBlockNoHdr	2
	158	saPerSmallRq	2
	160	nXBlockBoundary	2
	162	nXBlockSmallBoundary	2
	164	fCountersReset	1
	165	lastSnrmSent	1
	166	ppMeterBuffer	4
	170	pMasterStats	4
	174	oRgDct	2
	176	filler	2
	178	nYBlksMax	2
	180	nYBlksMin	2
	182	nYBlksAvail	2
	184	nZBlksMax	2
	186	nZBlksMin	2
	188	nZBlksAvail	2
Offset	Field	Size (bytes)
	190	n4ByteRnr	2
	192	fResetCounters	1
	193	nRcvError	2
	195	nUnderrun	2
	197	syncC	2
	199	sMasterStats	2
Cluster Workstation Information
Offset	Field	Size (bytes)
	0	rgbWsUserName	31
	32	next	2
	34	prev	2
	36	oLcb	2
	38	logicalLineNumber	1
	39	userNumber	1
	40	station	1
	41	lineState	1
	42	shActivePoll	1
	43	frameState	1
	44	saXBlockOut	2
	46	saXBlockIn	2
	48	nOutstandingRq	1
	49	nOutstandingSmallRq	1
	50	pollSequenceNumber	4
	54	erc	2
	56	NR	1
	57	NS	1
	58	fh	2
	60	lfa	4
	64	revisionLevel	1
	65	osType	1
	66	actionCode	1
	67	nRepollActive	1
	68	nCrcError	2
Offset	Field	Size (bytes)
	70	nOverrun	2
	72	nSequenceError	2
	74	nProtocolError	2
	76	nAddressError	2
	78	nLengthError	2
	80	nTimeout	2
	82	wsnCrcError	2
	84	wsnOverrun	2
	86	wsnSequenceError	2
	88	wsnProtocolError	2
	90	wsnAddressError	2
	92	wsnLengthError	2
	94	wsnTimeout	2
	96	dctWsSumSimpleRqTime	4
	100	dctnSimpleRq	4
	104	dctWsMaxSimpleRqTime	2
	106	dctWsSumGetDtRqTime	4
	110	dctnGetDtRq	2
	112	dctWsMaxGetDtRqTime	2
	114	dctWsSumBlockRqTime	4
	118	dctWsnBlockRq	4
	122	dctWsMaxBlockRqTime	2
	124	dctWsnTicksPerSecond	2
	126	nIFrames	4
	130	nPagesRead	4
	134	nPagesWritten	4
	138	nTicksSinceLastPoll	2
	140	nTicksMax	2
	142	pollSystime	4
	146	nTimesPolled	4
	150	DAINumber	1
	151	sioClock	1
Section 9	
List of Files on Product Media	
9.1	Contents of the Distribution Diskettes	
The CTOS III R1.3.1 distribution diskettes are your master copy and have been writeprotected.  The contents of the diskettes can not be overwritten unless the writeprotect tabs are removed.  Do not remove the writeprotect tabs and do not use these diskettes as your working copy.
Distribution Diskette 1 contains:
	<Clstr>Ws092>SysImage.sys
	<Clstr>Ws212>SysImage.sys
	<Clstr>Ws219>SysImage.sys
	<ClstrLfs>Ws090>SysImage.sys
	<ClstrLfs>Ws210>SysImage.sys
	<ClstrLfs>Ws211>SysImage.sys
	<ClstrLfs>Ws213>SysImage.sys
	<ClstrLfs>Ws220>SysImage.sys
	<CTOS>vClstr.img
	<CTOS>vClstrLfs.img
	<OsInstall>unb0010.cfg
	<OsInstall>unb0018.cfg
	<OsInstall>unb0020.cfg
	<OsInstall>unb0028.cfg
	<OsInstall>AllClstrCopy.fls
	<OsInstall>Config.sys
	<OsInstall>NlsKbd.sys
	<OsInstall>ps_v.sys
	<Sys>Install.ctrl
	<Sys>SysImage.sys
	<Sys>vClusterLfsOs>Install.ctrl
	<Sys>vClusterLfsOs>Install.jcl
	<Sys>vClusterLfsOs>InstallMsg.bin
	<Sys>vClusterOs>Install.ctrl
	<Sys>vClusterOs>Install.jcl
	<Sys>vClusterOs>InstallMsg.bin
	<Sys>vDebugger>Install.cmds
	<Sys>vDebugger>Install.ctrl
	<Sys>vDebugger>Install.jcl
	<Sys>Virtual Mode OS Diskette 1 of 3 (B25V101)
	<Sys>vServerOs>Install.ctrl
	<Sys>vServerOs>Install.jcl
	<Sys>vServerOs>InstallMsg.bin
	<Sys>vStndOS>Install.ctrl
	<Sys>vStndOS>Install.jcl
	<Sys>vStndOS>InstallMsg.bin
Distribution Diskette 2 contains:
	<CTOS>vSrvr.img
	<CTOS>vStnd.img
	<OsInstall>unb0010.cfg
	<OsInstall>unb0018.cfg
	<OsInstall>unb0020.cfg
	<OsInstall>unb0028.cfg
	<OsInstall>Clstr.sys
	<OsInstall>Config.sys
	<OsInstall>NlsKbd.sys
	<OsInstall>ps_v.sys
	<OsInstall>srvr.sys
	<OsInstall>SrvrCopy.fls
	<OsInstall>StndCopy.fls
	<Sys>Install.ctrl
	<Sys>Virtual Mode OS Diskette 2 of 3 (B25V102)
	<Sys>vServerOs>Install.ctrl
	<Sys>vServerOs>Install.jcl
	<Sys>vServerOs>InstallMsg.bin
	<Sys>vStndOs>Install.ctrl
	<Sys>vStndOs>Install.jcl
	<Sys>vStndOs>InstallMsg.bin

Distribution Diskette 3 contains:
	<CTOS>Debugger3.3.sys
	<DebugFile>DebugFile.run
	<DebugFile>Debugger3.3.help
	<DebugFile>DebuggerRqNames.bin
	<DebugFile>DebuggerStruct.txt
	<Sys>vDebugger>Install.cmds
	<Sys>vDebugger>Install.ctrl
	<Sys>vDebugger>Install.jcl
	<Sys>Virtual Mode OS Diskette 3 of 3 (B25V103)
9.2	Required Files	
The following is a list of required files necessary to boot the CTOS III operating system from disk.  The files are installed automatically for you when you use the installation procedure described in the CTOS System Software Installation Guide.
These files must reside in the [Sys]<Sys> path:
	SysImage.sys is the bootable operating system image (.img) file you wish to boot.  This will be vStnd.img, vClstrLfs.img, or vSrvr.img.
	ps_v.sys is the CTOS III virtual memory page service.
	Request.sys is the CTOS III request set definition file.
	Config.sys is the system configuration file.
	InstallVdm.run is a program that determines the type of video hardware present and then loads the correct video service:
Vdm_CH.run is the character map video service.
Vdm_BM.run is the bit map video service.
Vdm_VGA.run is the VGA video service for the B25VGX, the GC004, the SG2000, and the SG5000 systems.
Vdm_StdVGA.run is the VGA video service for CTOS machines with standard VGA hardware, such as the SG1X00, SG2X00, SG3X00, SG4X00, SG6X00, and SG7X00.
Vdm_VGAWei.run is the VGA video service for CTOS machines with the SG260V video card.
Vdm_Dmy.run is a dummy video service which is only used during an extended crash dump operation.
	T1Sys.font is the font file for the character map video.
1024x768_80Sys.font is a font file for VGA video.
640x480_80Sys.font is a font file for PC style VGA video.
720x348_80Sys.font is a font file for BTOSCTOS character map compatible VGA video.
	NlsKbd.sys and Nls.sys contains the keyboard translation and character set definition tables.
	SignOn.run and SignOnMsg.bin are for the logon program.
	Exec.run and ExecMsg.bin are for the CTOS Executive program.
	xxxx.user is the user signon and configuration file.
Section 10	
Ordering Procedure	
Please complete and return the attached Update Service Request (USR) form to order this product.  Media provided by Unisys Corporation may not be returned for credit.
You can order manuals from the following address:
Unisys Corporation
Publications Distribution Center
13250 Haggerty Road North
Plymouth, Michigan 48170