---------------------------------------------------------------------------- RSJ CD Writer File System Version 3.55 ---------------------------------------------------------------------------- This file contains final information and changes to the documentation of the programs and utilities of the RSJ CD Writer File System. Please read this file carefully before working with the RSJ CD Writer File System. *** IMPORTANT *** IMPORTANT *** IMPORTANT *** IMPORTANT *** IMPORTANT *** We found out that specific problems occur frequently. For that reason, we have added a section called "Tips and Tricks" at the end of this README file. Please read this section before calling the RSJ customer service. Of course, our customer support is still available and will be happy to answer all questions about our products. *** IMPORTANT *** IMPORTANT *** IMPORTANT *** IMPORTANT *** IMPORTANT *** New to version 3.55 --------------------- * Fixed a bug in the MMC driver; for some recorders, it was not possible to set the writing speed properly. Affected recorders always used their maximum speed (ie Yamaha 8824, 2100 and others) * Fixed problem affecting DAO copies of WAV files: the target CD was immediately ejected with nothing copied New to version 3.54 --------------------- * Fixed a problem in key file handling that did not allow to upgrade 3.52 to 3.53 New to version 3.53 ------------------- * English language resources in Control Panel/WPS Class in the German version - fixed * Fixed unavailable controls in ChangeMedia dialog of CopyWizard (hard disk buffered copy) * CopyWizard's DAO option is now unavailable if the source CD is not an audio CD (DAO is for audio CDs, only) New to version 3.52 ------------------- * CopyWizard sometimes failed to delete temporary hard disk image files - fixed. New to version 3.51BETA ----------------------- * DAO * Since so many recorders do not support the write mode we've been using for DAO in previous versions, we added a second method of writing DAO that seems to be widely supported. This new nethod is now the default, the previous write mode is only used if the new write mode fails. If DAO does not work (General Failure during copy, CD Writer Error Log reports Aborted Command or similar), please try to upgrade the recorder's firmware. During our tests, we had to do so for the Plextor PXW8220 (version 1.05 required) and PX-W4220 (1.04 required). As always, success reports are most welcome! So far, we have successfully tested the following recorders: Plextor PX-W8220 (firmware 1.05 req'd) Plextor PX-W4220 (firmware 1.04 req'd) Yamaha CRW2100S Yamaha CRW8824S Yamaha CRW4416S * Installation program * * The installer now performs a version comparison before overwriting an already existing DaniS506.ADD driver * If the DANIATAPI.FLT driver is installed, the user can choose if he wants to install our RSJIDECD.FLT driver, since DANIATAPI provides a similar functionality for enabling write access to IDE recorders. However, *please* read the DANIATAPI documentation *before* skipping installation of RSJIDECD.FLT. It contains information about how it has to be called to provide the functionality that RSJ CD Writer needs. * During an upgrade, the installer checks if the call to LOCKCDR.FLT has been removed from config.sys. If so, and if the DANIATAPI.FLT driver is installed, no new call to LOCKCDR.FLT will be added. Background: DANIATAPI.FLT also has the ability to emulate SCSI devices. Since our LOCKCDR.FLT driver does - among other things - the same, it is possible to not use LOCKCDR.FLT if DANIATAPI is properly installed. Again, please read the information in the DANIATAPI.DOC file to find out how. NOTE: LOCKCDR.FLT performs dynamic recorder detection during boot time. If you do not use it, you have to manually edit the cddrv.inf file. * CopyWizard * * To avoid problems with various display drivers, CopyWizard now supports a "Simple GPI" option in its system menu (main window). If set, the percent numbers in the progress bars are drawn with a gray background. * If a recorder is specified in the form CDR:HA.ID (HA=host adapter index, ID=drive SCSI id), this device string is now stored and presented in the drive combo box for later use. New to Version 3.50BETA ----------------------- Fixes for german language version. New to Version 3.49BETA ----------------------- This beta version contains the long awaited DAO mode for audio CDs. The following applications have been changed to support DAO mode: * CD View * CD View's track list received a new column that allows you to modify the pause time that is added before each track (except for the first one, which always has a dummy 2 second pause). The default is 2 seconds. To modify it, hold down the Alt key while clicking the according entry with the left mouse button (OS/2 standard behaviour) or use one of the commands in the context menu ('Pause Times' submenu). When you're done, click the DAO copy button in CD View's toolbar. There is no need to finalize the session after a DAO copy is complete. To be able to perform a DAO copy operation, the following conditions must be met: * The target CD must be empty * The CD Recorder must support DAO mode * There must be tracks queued for copying (of course :) * All queued tracks are audio tracks In any other case, the DAO copy button is grayed out and the pause time column read only (not editable). NOTE: Pause times are ignored if a TAO mode copy is performed. The parameters available in the 'Audio Options' dialog are only for TAO copies! * Track copy command line utility (trackcpy.exe) * The command line based copy utility supports DAO via its new 'daocopy' command. For a description on how to use it, start the utility and type help daocopy at its prompt. * CopyWizard * CopyWizard has a new check box "DAO mode". If checked, the CD is being copied in DAO mode with a zero pause between tracks (see below). Some notes about pauses between tracks: CD View is the only application that allows you to adjust the pause time that is added before each track. Both trackcpy.exe and CopyWizard use a zero pause time, which means the source CD is copied as is. The pause time that you set in CD View is actually added to the pause time of the source track. In other words, using a zero pause time perserves the source track's pause time. TIP: If you want to copy tracks that do have a pause to a new CD without pause, copy these tracks to your hard disk in TAO mode; then copy them to your recorder in DAO mode (with zero pause times, of course). ** Additional changes: The CD Writer Control application now contains a new page showing LOCKCDR's boot messages and information about recorders that were auto detected during system boot up. This information might be very helpful in case of problems. New to Version 3.07 ------------------- - Fixed a couple of bugs in CopyWizard New to Version 3.06 ------------------- - Fixed incomplete LOCKCDR boot message (occurred only if the parameters -n -i:"..." were used) - CopyWizard used to reset the speed setting to full speed after pressing the "Go!" button - Fixed the "Please reboot before running the installation again" message problem that was reported by some users - Changed registration for the CD Writer WPS class. If the CD Writer class is not active after installation and reboot, please boot the machine another time. To check whether the class is active, attach the recorder and open OS/2's "Drives" folder. You should see a CD-R symbol for your recorder. If the class is inactive, your recorder is displayed with a network drive icon. New to Version 3.05 ------------------- - Fixed load delay and bad response time during diskette installations - LOCKCDR.FLT: removed obsolete message "GetDeviceCaps failed" during detection of non- CDATAPI or CDMMC recorders New to Version 3.04 ------------------- - Fixed a couple of bugs in the installation program - Fixed wrong version number in most modules (3.02 instead of 3.03) Now all modules are set to 3.04 Note: this bug had various severe symptoms (invalid/expired license, file not found, etc.) New to Version 3.03 ------------------- - CopyWizard has a new "copy count" control New to Version 3.02 ------------------- - Fixed various bugs in the installation program - New command line tool CDWFMT.EXE This program is needed on Warp Server for eBusiness or Warp 4 FixPak13 or higher only; these systems do not support the usage of the standard format-utility anymore. CDWFMT.EXE usage: cdwfmt CD-WO drive letter /ERASE for blanking the inserted CD-R/W /UNSEAL for unsealing the inserted medium - LOCKCDR now correctly identifies the TEAC CD-ROM 532S as a CD-ROM drive. - LOCKCDR supports a new option -N to prevent dynamic detection. Caution: the use of -N requires that you explicitly specify your CD recorder ID string with the -I option New to Version 3.01 ------------------- - problem with calling the installer if 3.00 has already been installed fixed - english and french versions 3.00 contained an invalid key file New to Version 3.00 ------------------- - automatic detection of CD recorders that are compatible to the MMC or ATAPI standard; this applies to most current models - LOCKCDR.FLT has a new option -v, which enables diagnostic output during drive detection - CopyWizard: a PM program that copies entire CDs (Track-at-Once mode). More information about CopyWizard can be found in its online help. - Latest version of DaniS506.ADD included - new compression algorithm used within the installer. New to Version 2.84 ------------------- Latest version (Gamma 7) of DaniS506 included New to Version 2.83 ------------------- CID installation now supports the parameter /dani If this parameter is specified the IBM1S506.ADD driver will be replaced by DaniS506.ADD (see below). Otherwise the IBM1S506.ADD remains active. New to Version 2.81 ------------------- IBM1S506.ADD will be replaced by DaniS506.ADD alternatively. In the past, some customers reported traps during system boot on IDE systems. We never could reproduce the problem here and thus had no chance to fix it. However, using an alternate OS/2 IDE driver called DANIS506.ADD instead of IBM's IBM1S506.ADD solves the problem. For this reason, the installation program will replace the original IDE driver with DANIS506 on IDE systems by default. To prevent this, unckeck the "Replace OS/2 ATAPI driver with DANIS506.ADD" button before pressing "Start installation". DaniS506 - Copyright (c) 1999 Daniela Engert. All rights reserved. More information about DaniS501.ADD can be found at ftp://hobbes.nmsu.edu/pub/os2/system/drivers/storage/danis506.zip The latest version of DaniS506.ADD can be found there as well. The installation window was redesigned to contain the check box mentioned above and a "Register Demo" button. This button can be used to easily integrate a retail key file into a demo installation. New to Version 2.72 ------------------- Experimental support for bootable CDs based on the "El Torito" standard. In order to create bootable CDs, you'll have to create a "boot image". This can be as simple as using a bootable DOS floppy. The size of the "boot image" determines how the CD is booted: < 1.2MB: The image contains a "boot loader" (similar to the boot sector of your hard disk) which is loaded and started during the boot sequence. NT 4.0, for example, is booting this way. 1228800 Bytes: The image contains a raw copy of a 1.2MB Diskette (5.25") 1474560 Bytes: The image contains a raw copy of a 1.44MB Diskette (3.5") 2949120 Bytes: The image contains a raw copy of a 2.88MB Diskette (3.5") > 2.88MB: The image contains a raw copy of a hard disk In order to make a CD bootable, we supplied the utility "cdboot". If the image file is already on the CD, "cdboot" can be started simply by specifying the name of the boot image file (including the drive letter, ...): cdboot z:\dos.img In case the image has not been copied to the CD, yet, "cdboot" can create or copy the image file as well. This can be done by specifying the name of the source file (or drive) with the parameter "-s": cdboot z:\dos.img -s a: In this example, the diskette in drive A: will be copied into the image file "z:\dos.img". Once this operation has completed, the file will be registered as boot image. Notes: - "cdboot" can be called anytime (even multiple times); the actual boot information will be written when the CD is detached. - As soon as a CD is considered bootable, the current session will be closed regardless of the mode specified, that is, even if you call "cdattach z: -c", the session will be closed anyway. Otherwise, the boot information would get lost. - Currently, only a single boot image is supported - Although both RSJ and the "El Torito" specification do explicitly support bootable multisession CDs, we have yet to find a BIOS which does support booting from the 2nd session; obviously, the currently available BIOS versions aren't able to deal with multiple sessions. - Booting from a CD seems to be so incredibly complex that it's almost impossible to get it working right away. If, for example, a SCSI CDROM drive is used to boot from a floppy disk image on a CD, the system BIOS must be configured to boot from drive A: since the SCSI adapter will merely emulate a floppy drive from the boot image. Some PCs won't boot from CDs at all, some take an infinite time to go ahead, some don't understand all image types and, for example, can only boot diskette images, ... New to Version 2.70 ------------------- - General IDE support through LOCKCDR.FLT and RSJIDECD.FLT NOTE: RSJIDECD.FLT is a modified version of IBMIDECD.FLT which handles write commands and command timeouts properly. As soon as there's an updated version of IBMIDECD.FLT, it will be removed from the installation archive. On fast systems, especially when using a debug kernel, RSJIDECD.FLT may cause problems. If you don't have an IDE recorder and the system traps during the boot sequence, please open config.sys and replace the line "BASEDEV=RSJIDECD.FLT" with "BASEDEV=IBMIDECD.FLT". - LOCKCDR.FLT now has an additional option, -a, which can be used to force all CD recorder commands to be filtered. This can help in case of timeout problems (e.g. SCSI bus reset when finalizing a session) New to Version 2.59 ------------------- - It's no longer necessary to format new CDs. When using CHKDSK, new CDs seem to have a reserved track (to maintain compatibility), but the track will not be physically reserved until the first file is created on the CD. - RSJSCSI.SYS is now using OS2ASPI.DMD (instead of OS2SCSI.DMD). This should solve many problems we had in the past with some SCSI adapters. New to Version 2.57 ------------------- CD View is now able to copy XA tracks as video tracks even if the first sector in the track is a data sector (2048 bytes) This option is useful to copy XA-CDs which contain video sectors (2336 bytes) although CD View recognizes the CD as a simple data CD (disk symbol instead of movie strip). In order to turn the video mode on or off press the switch with the movie strip in the toolbar. Note: Although all XA tracks can be copied in video mode, they will consume more hard disk space if they are not copied directly to a CD recorder. Furthermore, some recorders (and CDROM drives) tend to become very slow when reading XA tracks in video mode. New to Version 2.54 ------------------- There's now a CID mode for the installation program. The according options are: /cid enter CID mode (installs automatically) Parameters: /s: source path (default = location of installation program) /t: target path (default = c:\cdwfs) /cs: cache size in KB (default = 20000) /bs: buffer size in KB (default = 2048) /cp: cache path (default = temp directory) /tm: track mode (1 = CDROM, 2 = CD-XA, default = 2) /iso: ISO level (default = 3) /spd: speed factor (default = 0, that is, maximum speed) Switches: /emu if specified, turn on emulation write mode /wps if specified, install WPS class and create CD Writer folder /cdwpop if specified, install CD Writer Error Log in Startup folder Example: install /cid /t:d:\cdwfs /bs:4096 /cp:"c:\CDWFS Cache" /iso:1 /spd:2 /wps /cdwpop This example will install the RSJ CD Writer File System in the directory "d:\cdwfs". Additional options: cache path = "c:\CDWFS Cache" ISO Level = 1 speed factor = 2 install CD Writer class install Error Log in Startup folder Please note the quotation marks used to specify directories with blanks. Cache Files ----------- Unfortunately, some of the hard drives (especially older models) are not able to supply enough data throughput to allow writing at 300KB/s or faster. This may force the software to reduce the recording speed. Although you won't lose any data, the partially written track remains on the CD and the occupied medium space is lost. In case of problems, please try the following: - If possible, the cache path sould point to a hard drive which is not otherwise used in the copy process. - If this is not possible, try to prevent accessing the hard drive with other programs while the recorder is writing. Writing multiple files simutaneously increases the hard disk load, too. - If there's enough RAM in the system, the buffer size can be increased as specified above in the section "File System (CDWFS.IFS)" Long Filenames -------------- The long filename support is based on two different standards: - Rock Ridge Extensions This standard is used by most Unix systems to save long filenames along with their Posix file attributes. We're currently supporting about 140 characters for long filenames. The Posix file attributes are always set to default values. Please note that Unix file systems are case sensitive while OS/2 is not. If the RSJ CD Writer File System is used to read Unix CDs, it's possible that a specific file cannot be opened if there's another file in the same directory which differs only in case. This standard is also used as the base standard for CDs. As long as a CD contains Rock Ridge information, it's preferred to "Joliet". - Joliet This standard is mainly used in the Windows environment. However, it supports only 64 characters per filename, so it's usually not used to read existing CDs as long as they contain Rock Ridge information. When a CD is detached, both standards will be written to the CD. Each time a CD is attached, the standard providing the longest filenames will be used to read the directories. Unfortunately, the OS/2 CD filesystem supports neither Rock Ridge nor Joliet. For that reason, the following limitations apply when a CD is read from CDROM drives: - All characters are upper-case - National language characters are replaced by a tidle (~) - Long filenames will be displayed with max. 31 characters Of course, you can always use the RSJ CD Writer File System to read back CDs containing Rock Ridge or Joliet filenames. If the CDs are intended to be used on DOS systems, the ISO level should be set to "1". Optionally, you can also make sure that no file violates the DOS 8.3 convention, that is, as long as all files are 8.3, the ISO level won't change the contents of the ISO directory tree. Notes: - Recent Fixpaks for OS/2 contain an updated driver for the CDROM file system (CDFS.IFS) which, if loaded with the parameter /w, allows using long filenames in Joliet format. - In order to use a fast CDROM drive to read CDs with the CD Writer File System, you can use the "-d" command line parameter to specify the drive letter of the CDROM drive. Example: "cdattach z: -d e:" In most cases the capabilities of the CDROM drives should allow reading the CD without any performance losses. Supported CD Recorders ---------------------- A list of supported recorders can be found in the file "cddrv.inf". Notes/Limitations: Manufacturer Model Notes --------------------------------------------------------- Yamaha CDR100 1) Yamaha CDR102 1) Sony CDU920S 2) Sony CDU924S 2) Sony CDU926S 2) Sony CDU948S 2) Yamaha CDR400 3) Yamaha CDR200 3) Teac CD-R50S 2) 4) Teac CD-R55S 2) NOTES: 1) These recorders don't support detaching a CD without closing the session (that is, never call "cdattach -c") 2) Emulation write mode currently not supported 3) Please make sure you're using firmware version 1.0d or later 4) Firmware version 1.0G is required Tips and Tricks --------------- This section provides an overview over frequent problems together with possible solutions. Please read this section carefully before calling the RSJ customer support. Problem: Weird problems, system traps or other unexpected behavior Solution: 1) Some SCSI adapters must be prevented from starting synchronous transfers. The according option usually contains the words "Sync Transfer" and, depending on the SCSI adapter, can be set either in the BIOS setup (e.g. Ctrl+A with Adaptec products) or by jumpers. This is especially important when Adaptec SCSI adapters are being used; if your SCSI adapter supports disabling the synchronous transfer, it should be disabled in any case. 2) Sometimes, a memory error (RAM) is causing the problems. Most of today's computers don't use parity bits anymore, so a memory error remains undetected until some severe problems show up. If in doubt, try to slow down the memory access with the BIOS setup program. Disabling the 2nd level cache for test purposes can also be useful. 3) In some cases, an updated driver for the SCSI adapter might correct the problem, as well. Here's an address which contains updated OS/2 drivers for all kinds of devices: http://www.europe.ibm.com/psmemea/progserv/device 4) Make sure that the SCSI cables and terminators are OK. Ultra-SCSI adapters need special cables and active terminators. Problem: Writable CDs cannot be read by certain CDROM drives. Solution: Unfortunately, there's no general solution for this kind of problem. The CDROM drives must be able to read CD-XA tracks and multiple sessions. Sometimes, a specific combination of CD recorders and CDROM drives causes problems. For example, the NEC 6x CDROM drive CDR502 can only read the first session if the CD has been created by a Yamaha CDR100 recorder. In rare cases, CDROM drives cannot handle more than about 80 tracks. In this case, try to increase the cache size as mentioned above to reduce the number of tracks on the CD. Problem: Sometimes, a CDROM drive doesn't recognize all sessions on the CD although the manufacturer claims the drives would comply to the multisession standards. Solution: Even though the number of sessions on a CD is not limited by the according standards, some drives cannot handle more than about 10 sessions. In case of problems, try to reduce the number of session to a number below 10. Problem: When copying the last audio track, an error message pops up which claims that there was a read error. However, the audio track appearently has been copied completely. Solution: It's difficult to determine the end of the last audio track. We'll watch this problem and suppress the error message in a later version if we don't find any real errors. Since the target CD was OK in all cases we've heard about, this can be considered a cosmetic problem for now.