cdrtools-3.02a07.tar.gz

========================================== Cdrtools Version 2.01 (2.01.01a22) for VMS ========================================== ======================================================================== Functional changes for VMS. 2006-11-13 SMS. -------------------------------------------- ------------------------------------------------------------------------ This kit includes MMS/MMK product builders which are new for cdrtools version 2.x. Objects, object libraries, executables, and any other system-specific files should now be placed into system-specific subdirectories in the source tree, such as [.ALPHA], [.IA64], or [.VAX]. If the large-file option is specifed (non-VAX), [.ALPHAL] or [.IA64L]. (See below for details.) Command-line case is preserved by all programs if SET PROCESS /PARSE_STYLE = EXTENDED is in effect (non-VAX, where C run-time library support exists). This obviates quoting upper-case options. All programs now have an exit handler to restore process base priority ("nice(0)"). CDRECORD (and CDDA2WAV?) normally raise it (where privileges allow), but did not previously restore it. The priority-raising scheme is now a build-time option, which may be specified in the VMS section of [.INCLUDE.SCHILY]XMCONFIG.H. Older cdrtools versions always used "nice(-20)". Now, an OS-specific nice() value may be selected, or an actual VMS process base priority value may be specified. The current default is to set the priority to 16, the lowest real-time priority value on VMS. CDDA2WAV, CDRECORD, MKISOFS, and READCD now use some VMS-specific parameters on open operations for major files. This typically enables double buffers, read-ahead, write-behind, and larger extend quantities. Users who do not override the RMS defaults (SET RMS_DEFAULT) should see significant I/O speed improvements. Users may override the new default parameters using SET RMS_DEFAULT explicitly to set different ones. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MKISOFS Changes --------------- - New "-E" option to show ISO 9660 header (Environment) information. This shows, for example, ".mkisofsrc" file data not explicitly specified on the command line. The "-v" option now also shows whether ".mkisofsrc" was used. These changes are enabled by defining the C macro "SMS", which is done by the by the VMS builders. (Look for "SMS" in [.MKISOFS]DESCRIP_SRC.MMS.) - ODS5 extended file name support (not well tested). - Various bug fixes. (See below for details.) - The new MKISOFS option, "-find", must be enabled at build time. See notes below. MKISOFS "-find" --------------- The new MKISOFS option, "-find" has not been well tested. It is enabled at build time by defining the MMS/MMK macro FIND. See comments in [.VMS]DESCRIP.MMS. - The "-exec" operator does not work, as its implementation involves fork(). - The "-name" pattern matching code is UNIX-oriented, so it's case sensitive, and there's no default for version numbers. For example, "-name ab.*" will _not_ match "AB.C;1" (case), and "-name *.C" will not match "AB.C;1" (version). A name pattern like "[aA][bB].C;*" would match any version of "ab.C", "aB.C", "Ab.C", or "AB.C". On an ODS2 file system, specifying all-upper-case names is sufficient to deal with this case sensitivity, but more care is needed for ODS5. - The unusual implementation of inodes in the VMS C RTL will probably defeat inode-related features ("-inum", "%i"). Beginning with VMS V8.2 or so, building with the MMS macro STD_STAT defined may help by switching to a more POSIX-compatible inode implementation, but enabling this feature may change the behavior of the stat() function in all programs in this collection, so it could cause problems anywhere. Also, STD_STAT probably requires large-file support (LARGE), and is not available on VAX. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MKISOFS Diagnostic Programs --------------------------- There are some diagnostic programs related to ISO-9660 file systems hidden in the [.MKISOFS.DIAG] directory. Executables for the working ones should be created in the same directory as MKISOFS.EXE, and suitable foreign-command symbols may be created for them, if desired. (See Foreign-Command Symbols, below.) The working ones are: - isodebug print mkisofs debug info from ISO-9660 image. - isoinfo perform directory like listings of iso9660 images. - isovfy verify the integrity of an iso9660 image. Not yet working (due to UNIX screen handling, at least) are the more interactive programs: - isodump display the contents of iso9660 images. - devdump display the contents of device or filesystem images. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - VMS CD/DVD Device Specification ------------------------------- In this release, a CD/DVD drive may be specified using a normal VMS device name (physical or logical). For example, "dev=dkb500" or "dev=cdrw" (where "cdrw" is a logical name which has been defined to identify an appropriate device). As in previous cdrecord/cdrtools versions, the old standard cdrecord/cdrtools "bus,target,lun" format is also allowed (with some changes to the mapping from previous releases). That is, "dev=bus,tgt,lun" (where "bus", "tgt", and "lun" are integers), rather than a simple VMS device name. The "dev=bus,tgt,lun" specification is translated into a VMS device name as shown below. bus: 0 1 2 3 4 5 6 7 dka dkb dkc dkd gka gkb gkc gkd (SCSI disk, SCSI generic) 8 9 10 11 12 13 14 15 dqa dqb dqc dqd dqe dqf dqg dqh (ATAPI) 16 17 18 19 20 21 22 23 dna dnb dnc dnd dne dnf dng dnh (USB) tgt: SCSI ID (always zero for ATAPI devices) lun: SCSI LUN (normally 0 for SCSI, zero or one for ATAPI) For example, "dev=1,5,0" specifies DKB500, and "dev=8,0,0" specifies DQA0. If a SCSI adapter beyond "D" is needed, the simplest method would be to specify the actual VMS device name instead of using the "bus,tgt,lun" scheme. However, to use the "bus,tgt,lun" scheme in such a case, one could specify some nonexistent GK device (like "dev=7,1,1"), and then define a logical name to redirect the phony device name (here, GKD101) back to the real device. For example, if the CD/DVD drive were DKF300: $ define GKD101 DKF300 $ cdrecord dev=7,1,1 -prcap - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - GKDRIVER -------- Some VAX systems (with older hardware and/or older VMS versions) will need to use (or work better if they use) the GKDRIVER generic SCSI driver for the CD/DVD drive, instead of the usual DKDRIVER SCSI disk driver. The indicating symptom might be an I/O failure like this: cdda2wav: invalid argument. Cannot send SCSI cmd via ioctl %SYSTEM-?-BADPARAM, bad parameter value or many (recoverable) errors like this: cdda2wav: not owner. ReadCD MMC 12: scsi sendcmd: retryable error One way to select an alternate device driver involves editing SYS$MANAGER:SYCONFIG.COM to control which driver is used for the CD/DVD device. The suggested changes shown below do three things: 1. Prevent all the system devices from being automatically configured (because that would connect the CD/DVD device using the default DKDRIVER), 2. Arrange to specify GKDRIVER for the CD/DVD device(s), and then 3. Automatically configure all the other devices. The first change is to uncomment this line in SYCONFIG.COM: $! STARTUP$AUTOCONFIGURE_ALL == 0 This prevents SYS$STARTUP:VMS$DEVICE_STARTUP.COM from configuring any devices. Then (also in SYCONFIG.COM), add the appropriate SYSG