
CONVERGENT TECHNOLOGIES

RELEASE NOTICE FOR
1.0 MetaWare High C
(product number)

Revised Month Day, Year

SECTION   TITLE	PAGE
	1.0	Description of Programs	3
	2.0	Contents of Distribution Diskette	3
2.1	Changes From Prior Versions	3
	3.0	Installation Procedures	5
3.1	StandAlone and Master Hard Disk Systems	5
3.2	MegaFrame SRP Systems	5
3.3	Cluster WorkStations	6
	4.0	Required Files	6
	5.0	System Software Compatibility	7
	6.0	Hardware Information	7
6.1	Hardware Configurations Supported	7
	7.0	Resource RequirementsUtilization	7
7.1	Memory RequirementsUtilization	7
7.2	Disk RequirementsUtilization	7
	8.0	Supplementary Information	8
	9.0	Known Errors and Omissions	12
	10.0	DOS Error Codes	13
	1.0	Description of Programs
This Release Notice describes the MetaWare High C compiler release 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 the compiler.
MetaWare High C is a professional tool that can be used to compile C programs for CTOS.  The compiler is ANSI draft compatable, and provides extensions to accomodate almost any situation.
	2.0	Contents of Distribution Diskettes
The High C compiler Distribution Diskettes are your master copy, and have been shipped writeprotected.  It should not be writeenabled, nor should it be used as a working copy.
The Distribution Diskette 1 of ?? contains the following files in the <CT> directory:
.01
In addition to various standard system files, the Distribution Diskette 1 of ?? contains the following files in the <Sys> directory:
HdInstall.sub	continue.sub
The Distribution Diskette 1 of ?? contains the following file in the <ReleaseNote> directory:
ReleaseNotice
	3.0	Installation Procedures
The High C compiler should only be used on Convergent Information Processing Systems which are equipped with hard disk, or in clusters where the master is equipped with hard disk.
Use the installation procedures described below.  Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in upper case.
Installation can be made to workstation, or a master (either NGEN, series i, or SRP).  The installation process prompts the operator for input to determine the target system.
{3.1	All Hard Disk Systems
A.	Signon and set path at the workstation.  If the Signon form is displayed, fill it in and press GO.  Set the path as follows:
Command   Path  RETURN
Path
  [Volume]	Sys  RETURN
  [Directory]	Sys  RETURN
  [Default file prefix]	RETURN
  [Password]	(if any)  GO
  [Node]
	If your hard disk has a volume password on [Sys], fill this password into the [Password] field before pressing GO.}
B.	Insert the High C compiler Distribution Diskette 1 of ?? into floppy drive [f0].
		Type
	Command   Install   GO
C.	Follow the directions presented at various points during the installation process.  This will include prompting thru the other installation diskettes, questions concerning default directory specifications for C supplementary files (such as include files, sample programs, etc.) and other preferences.
	This section will also ask if the installation will be to the local system, or the master.  Further questions will take into account the target installation system.
	{4.0	Required Files
The High C compiler release diskettes contain all additional files required to run the service on a supported system.}
	{5.0	System Software Compatibility
The  High C compiler will run on CTOS 9.8 or later, and on CTOSSRP 1.3 or later.
	{6.0	Hardware Information
The High C compiler requires at least 1 megabyte of memory to execute properly for most compiles.  Some large source files, or sufficiently complex source that makes extensive use of macros will require more memory to compile.  This is elaborated in the resource requirements section.
6.1	Hardware Configurations Supported
The High C compiler will run on NGEN, Series286i, and SRP hardware.}
	{7.0	Resource RequirementsUtilization
7.1	Memory RequirementsUtilization
The High C compiler requires 1 to 4 megabytes of memory, depending on the particular source file being compiled.  There are trade offs that can be made concerning the compilation speed vs. memory requirements.}
{7.2	Disk RequirementsUtilization
The ClusterShare Service files require the following amount of disk space:
	ClusterShare.run	140
	ClusterShare.sym	40
	ClusterShareMsg.Txt	2
	ClusterShareMsg.Bin	2
	DeInstallCLusterShare.run	52
	Request.S.sys	4}
	8.0	Supplementary Information
{8.1	Expected audience
	The primary users of the ClusterShare Service are anticipated to be DOS users.  It is possible for a CTOS program to be a client of the service by issuing appropriate CTOS requests.  This may be desirable if the CTOS application wishes to take advantage of the record level locking, or data caching abilities of the service.
	{The user interface to the service is severely restricted.  The user only sees the install command, and any error messages that may occur during service initialization.  All user errors are reported by returning an appropriate error status as part of the response to the users request.  Any nonuser error is catastrophic, meaning there has been a breakdown in the driving logic of the program, and may result in a crash.}
	{The error codes returned by the service are not CTOS error codes.  DOS has its own set of error codes documented for use with the redirector and the service uses them.  These codes, along with the DOS requestresponse protocol are documented in Microsoft's document titled 'SERVERREDIRECTOR FILE SHARING PROTOCOL' version 1.5, dated June 11, 1985.}
	{The real interaction that takes place with the service happens when the DOS user runs an application that references a remote volume through the service.  This interaction is described in the appropriate application documentation.}
{8.1	Install ClusterShare Command
	The following command form can be used to install the ClusterShare service.  Each line of the form is described below.
	Important note:  The total size of the first 5 parameters must be less than or equal to 64K bytes.  All of the data structures allocated for these structures are in a single segment.  If the requested parameters will not fit in 64K, the program will exit with erc 400 (not enough memory) regardless of the total amount of memory available.  The last parameter (number of cache buffers) is allocated separately from the others, and has no unusual restrictions.
Install ClusterShare
[Maximum Client Workstations       (default   8)]
[Maximum Network Drive connections (default  16)]
[Maximum file connections          (default  32)]
[Maximum open DOS files            (default  32)]
[Maximum lock ranges               (default 100)]
[Number of Cache Buffers           (default   8)]}
{Maximum workstations:
Enter the maximum number of client workstations that will be allowed to connect to the server.  This number should include NGEN workstations that will run the PC Emulator with each context running DOS on a 386 counting as a separate work station.

Each connection requires six (6) bytes.}
{Maximum tree connections:
Enter the maximum number of DOS network drives and printers that all client workstations can be connected to at any one time.
Each DOS workstation will need at least one.  

Each volume assignment requires 1272 bytes.}
{Maximum file connections:
Enter the maximum number of files that can be open at one time from all client workstations connected.
When two different work stations have the same single file open, it counts as two file connections for this parameter.  

Each file connection requires twenty (20) bytes.}
{Maximum open DOS files:
Enter the maximum number of files that can be opened by the server at any one time.
When two different work stations have the same single file open, it counts as one open file for this parameter.  

Each file control block requires 226 bytes.}
{Maximum lock ranges:
Enter the maximum number of byte ranges that can be locked at any one time.  This number is not per file, but is the total number of locks allowed for all files.  

Each lock range requires sixteen (16) bytes.}
{Number of Cache Buffers:
Enter the number of 2048 byte buffers to be used by the writethrough data cache.
The minimum is one buffer; the maximum depends on the amount of memory on the machine (more than one megabyte can be used when running on a protected mode OS).  The data buffered is 2048 bytes per buffer, but there is additional overhead associated with each buffer.  

Each buffer requires 2064 bytes.}
{8.1	File Naming Conventions.
	The service provides a one to one mapping between DOS files and CTOS files.  The CTOS file name is formed from the complete DOS file name, including backslashes (\). For example, the DOS file D:\foo\file.ext, where D: is mapped to {local}[Sys]<Sys>, is really the CTOS file {local}[Sys]<Sys>foo\file.ext.  Note that the backslash (\) immediately following the D: in the DOS specification is not part of the CTOS file name.}
	{DOS imposes severe restrictions on file names.  A file name is at most eight (8) characters, optionally followed by a dot (.), optionally followed by at most three (3) characters.  Any name that is longer than allowed, or that contains more than one (1) dot (.) is not visible to DOS.}
	{The service is simulating a tree structured directory hierarchy.  Each directory must exist before it can contain files.  Attempts to access a file at an arbitrary point in the tree cause the entire ancestry to be validated before access is allowed.  This means that CTOS file names containing the backslash (\) character are not necessarily visible from DOS.}
	{These restrictions also show that there is a large class of CTOS file names that DOS cannot access.  The service filters these file names out and does not attempt to show them to DOS.  They are not seen by DOS even in wild carded operations.}
	{9.0	Known Errors and Omissions
A.	When using GPS to print from ClusterShare, the 2.1 or later version of GPS is required.}
B.	On a Client Workstation (PC), when RS422.exe is executed and there is not a master or cluster cables are not connected to the master, the Client Workstation hangs.  To workaround this problem be sure there are cluster cables connected to your master and the master is up.
C.	The following paragraph is taken from the Release Notice for 2.1 Generic Print System.  The condition described is not an error in either program, but is a restriction of the certain printers.
	Please not that this condition can now be easily avoided by use of the CSPRINT.CFG file to define a DOS printer name that accesses the printer with the :Defeat_Image_Mode: flag set to Y.
ClusterShare, Network PC, PC's, AT's or AT compatibles submit jobs to GPS printers in binary mode, under the assumption that the logic to translate a document into printerspecific language is imbedded in the application, and the device driver should simply pass the data through.  If an ordinary ASCII file (instead of a job in printerspecific language) is queued in binary mode it will usually print, since most printers will accept ASCII.  However, printers configured for Impress (Imagen) or PostScript will only print jobs which are in the Impress or PostScript page description languages.  These printers typically have a panel setup or a physical switch which configures them into other interpretation modes, such as diablo emulation, which will accept ordinary ASCII.  It will be necessary to reconfigure these printers in order for them to process ASCII files printed in binary mode.  They must be reconfigured again to print Impress or PostScript jobs generated by the device driver or other applications.
	{10.0	DOS Error Codes
Below are listed the DOS errors that may be displayed by the CS.exe command. }
	 1	Invalid function code
	 2	File not found
	 3	Path not found
	 4	Too many open files 
	 5	Access denied
	 6	Invalid handle
	 7	Memory control blocks destroyed
	 8	Insufficient memory
	 9	Invalid memory block address
	10	Invalid environment
	11	Invalid format
	12	Invalid access code
	13	Invalid data
	15	Invalid drive
	16	Attempt to remove the current directory
	17	Not same device
	18	No more files
	19	Disk is writeprotected
	20	Bad disk unit
	21	Drive not ready
	22	Invalid disk command
	23	CRC error
	24	Invalid length (disk operation)
	25	Seek error
	26	Not an MSDOS disk
	27	Sector not found
	28	Out of paper
	29	Write fault
	30	Read fault
	31	General failure
	32	Sharing violation
	33	Lock violation
	34	Wrong disk
	35	FCB unavailable
	3649	RESERVED
	50	Network request not supported
	51	Remote computer not listening
	52	Duplicte name on network
	53	Network name not found
	54	Network busy
	55	Network device no longer exists
	56	Net BIOS command limit exceeded
	57	Network adapter hardware error
	58	Incorrect response from network
	59	Unexpectd network error
	60	Incompatible remote adapt
	61	Print queue full
	62	Queue not full
	63	Not enough space for print file
	64	Network name was deleted
	65	Access denied
	66	Nework device type incorrect
	67	Network name not found
	68	Network name limit exceeded
	69	Net BIOS session limit exceeded
	70	Temporarily paused
	71	Network request not accepted
	72	Print or disk redirection is paused
	7379	RESERVED
	80	File exists
	82	Cannot make
	83	Interrrupt 24 failure
	84	Out of structures
	85	Already assigned
	86	Invalid password
	87	Invalid parameter
	88	Net write fault