Last update 14.11.99

Q1a: The -scanbus command does not work. cdrecord says 'Can't lock memory'.
A: This is a bug in the OS/2 version of cdrecord 1.8a8. It's partly fixed in V1.8a15. Get a recent release for a fixed version.

Q1b: The -scanbus command does not work. Cdrecord repeats the last found device on every bus.
A: This is a bug in the OS/2 version of cdrecord. It's fixed with V1.8a23.

Q1c: The -scanbus command does not work. Cdrecord beeps and throws out some strange characters.
A: This is a bug in the OS/2 version of cdrecord. It's fixed with V1.8a23.

Q2: The -fifo command seems not to work.
A: That's right for all versions up to V1.8a23. This feature is supported with V1.8a24 and above.

Q3: What's about the wildcards mentioned in the manual?
A: They are not working with versions before V1.8a19. You should upgrade to a more recent release.

Q4: I want to copy a CD. cdrecord dev=1,0 speed=2 -isosize /dev/scd0 does not work. If I provide a drive letter or a directory I get the message 'no read access' or 'permission denied'.
A: You can't mount a CD as an ISO-image with OS/2. So you have to use mkisofs or mkhybrid to create such an image prior to burning. You can tie mkisofs and cdrecord together using pipes:

mkisofs -l -L -R x:/ | cdrecord dev=1,0 -data -

So there is no image file necessary. I highly recommend to raise the priority of the mkisofs process to prevent buffer underruns:

spe t28 mkisofs -l -L -R x:/ | cdrecord dev=1,0 -data -

Important: Use the version of mkisofs which is included in the cdrecord/2 distribution when working with pipes! Other versions may have got a bug which causes opening of stdout in textmode. Also use cdrecord V1.8a15 or above only.

Cdrecord/2 V1.8a15 runs with timecritical priority 31. The priority of mkisofs must be <=30 to ensure cdrecord gets the necessary processor time. V1.8a8 runs with normal priority 0. The versions V1.8a22 and above have got a dynamic priority scheme with a maximum of timecritical 31. Depending on your system you may adjust the priority of mkisofs.

As an alternative solution you may use READCD.EXE of V1.8a24 to get the image of the CD. Then write it on your CD-R.

Q5: How do I create an image file with mkisofs?
A: Use the following command line:

mkisofs -l -L -R -o image.raw x:/dir_with_data

Q6: How do I create an image of my whole partition?
A: Use the following command line:

mkisofs -l -L -R -o image.raw x:/

Q7: I can't read the documentation.
A:The documents are postscript files. Get ghostview/ghostscript from Hobbes or LEO. It's a free postscript renderer to view and print those files.

Q8: If I click the drives icon in the Warpcenter while burning my machine hangs.
A:Cdrecord writes to the CDR without telling OS/2 anything about it. It uses directly the SCSI-Bus on a rather low level. When opening the drives folder the Warpcenter checks every drive. When doing so the write requests of cdrecord and the read requests of the Warpcenter collide and the system gets confused.

Q9: I've got OS/2 Warp 3 (red) on floppy disks and want to create an installation CD.
A: An installation CD may be done by simply copying the disks on the CD. Create for every disk a directory and name it

DISK_0	DISK_1	DISK_2	DISK_3	DISK_4
DISK_5	DISK_6	DISK_7	DISK_8	DISK_9
DISK_10	DISK_11	DISK_12	DISK_13
DISP_1	DISP_2	DISP_3	DISP_4
PMDD_1	PMDD_2	PMDD_3

On disk 1 of your floppy installation boot disks modify the config.sys in the following way:

SET OS2_SHELL=sysinst2.exe x:\disk_root_dir_on_CD

The same way you may install from a HD partition.

Q10: I only see the first session of a multisession disk with my SCSI-drive.
A: Seems to be a problem with the way SCSI-drives access the second session. There're AFAIK different methods to do that and if the OS2*.DMD doesn't know the name of the drive you're lost. I've read in a newsgroup that's possible to patch the *.DMD so it knows the right name afterwards to solve this problem. But I don't know how to do that exactly. You can usualy read the disk with an IDE-drive without problems.

Q12: How do I get the ISO-image of a CD?
A: Use READCD.EXE included in V1.8a24 to read the contents of the CD into an image file. See AN-1.8a19 for a description. The versions in V1.8a22/V1.8a23 are buggy so you can't use them.

Q13: How do I make a 1:1 copy of a CD?
A: Use READCD.EXE included in V1.8a24 to read the contents of the CD into an image file. See AN-1.8a19 for a description. The versions in V1.8a22/V1.8a23 are buggy so you can't use them.

Q14: OS/2 traps with a Yamaha CRW4416s
A: This problem is fixed with V1.8a24b.

Q15: CDRecord/2 throws out an error in -dummy mode with a Symbios Logic host adapter
A: Upgrade to V1.8a24b.
If this doesn't work try a driver version prior to V4.09/V4.10. V4.06 works well and I had reports that V4.00 and V4.01 also work without problems.

Q16: cdd2wav does not work with my writer and a Symbios Logic host adapter
A: See answer for Q15.

Q17: CDRecord/2 can't allocate filehandles for more than about 13 tracks
A: Should be fixed with V1.8a15 and above!. Put the following statement in your config.sys:

SET EMXOPT=-h255

Q18: There's a SIGTERM message every time I burn a CD!
A: The message is coming from the FIFO process being killed when CDRecord/2 is exiting. Since the CD is already burned nothing happens except this message. The CD is not damaged! This is normal behaviour with the current implementation.

Q19: CDRecord/2 complains about a wrong EMX option.
The following line is found in config.sys:

SET EMXOPT= -C -N -H1024

A: Change the H to h.