TSX-32 Version 6.02 Release Notes Copyright (c) 1999. S&H Computer Systems, Inc. Table of Contents 1. Updates to version 6.0 . . . . . . . . . . . . . . . . . . . . 1 2. Problems Corrected in Version 6.01 . . . . . . . . . . . . . . 1 3. Changes made for 6.02 . . . . . . . . . . . . . . . . . . . . 1 i 1 1. Updates to version 6.0 This document describes changes in each maintenance release of the 6.0 TSX-32 series. 2. Problems Corrected in Version 6.01 1. System crashes Due to system crashes, some preliminary FAT32 support code has been removed from version 6.01. 2. NFS problems The version 6.00 kernel seemed to cause problems with some NFS installations which are corrected in 6.01. 3. SMTP server did not claim ETRN support The SMTP server had ETRN support but did not indicate this in response to the extended hello command. 4. POPD had a throttle engaged The POP Daemon had a throttle which prevented it from accepting more than 10 connections per second. 5. DISKGEOM did not work with 3rd and 4th disk DISKGEOM would either hang or produce invalid output when more than two IDE disks were in use. This has been corrected. specified for output in the RESTORE command. 3. Changes made for 6.02 1. Partition table processing The majority of the information which has been provided by DISKGEOM over the years is now ignored by default. Starting with version 6.01, partition tables for IDE drives are read during system startup just the same as partition tables have been processed for SCSI drives for some time. It is still necessary to have UNIT statments in the tsx32.gen file but they merely declare the presence of the units and give them dos drive letters. You can disengage partition table processing by using the new /NOPTREAD qualifier on the DEVICE=DH statement. The only reason to do this would be if the automatic processing of the partition tables fails, and you want TSX to use the starting block number and size information from the gen file instead. The hard drive geometry found on the DEVICE=DH statement is now also ignored by default. By default, TSX will now query drives and determine the geometry. This means that /IDENTIFY is not the default and you must specify /NOIDENTIFY to disengage this automatic detection. 2 2. New system event log A new event log is available to track facility locking activity. Programs which are waiting on a facility have the same job state, SFWT, as programs waiting on locked files. The new FACILITY event log complements the FLOCK event log in helping customers diagnose troubles with jobs getting hung in an SFWT state. The facility event log is engaged using the SET EVENT/FACILITY command and disengaged with SET EVENT/NOFACILITY.