# @(#)README	1.30 20/11/21 Copyright 1996-2018 J. Schilling

This is Version 3.02 of cdrecord

Cdrecord allows you to create CD's on a CD-Recorder.
Cdrecord runs on:

SunOS 4.1.3 or later:	m68k sparc
Solaris 2.3 or later:	sparc x86 ppc.

Linux:			alpha x86 IA-64 m68k mips mipsel parisc parisc64 ppc s390 sparc sparc64 strongarm

FreeBSD:		alpha arm IA-64 powerpc sparc sparc64 x86 x86-64
NetBSD:			alpha amiga x86 m68k sparc
OpenBSD:		x86

AIX:			rs6000
AmigaOS			m68k
Apollo Domain/OS	m68k ???
Apple Rhapsody:		ppc, x86
Apple MacOS X:		ppc
Apple Darwin:		ppc
BeOS:			m68k x86
BSD/OS (BSDi):		sparc x86
Caldera OpenUnix:	x86
HP-UX:			hppa
GNU HURD:		x86
NeXt Step:		mc68xxx x86 and hppa
OS/2:			x86
OSF1:			alpha
SCO Openserver 5.x:	x86
SCO Unixware 2.x:	x86
SCO Unixware 7.x:	x86
SGI IRIX:		mips
Win95:			x86
Win98:			x86
WinME:			x86
WinNT:			x86
WinNT-5 (aka Win2000):	x86
WinNT-5.1 (aka WinXP):	x86
VMS:			*VAX alpha
QNX:			x86 (coming soon)


To learn how to compile and install cdrecord, read README.compile

To compile on currently unknown platforms you definitely need 'smake'
from https://sourceforge.net/projects/s-make/files/ or
https://sourceforge.net/projects/schilytools/files/
GNUmake is too dumb to do this job as it does not include automake features
like 'smake' does.

For multi session please read README.multi

In general, it is a good idea to read all README's and check whether
they may apply for your needs/problems.

Cdrecord runs without problems on a loaded Solaris system.
On Solaris, cdrecord uses the SVr4 priocntl() call to establish
SVr4 real-time scheduling which grants to run cdrecord in a even higher
priority than all kernel processes. On system that provide POSIX real-time
scheduling the result may be slightly worse as not all POSIX RT implementations
grant decent real time behaviour.

The cdrtools distribution contains a SCSI user level transport library
called libscg. The SCSI library is suitable to talk to any SCSI device without
having a special device specific driver for it.
Cdrecord may be easily ported to any system that has a generic SCSI device
driver similar to the scg driver.

On SunOS/Solaris:
You *need* the SCSI general driver 'scg' in order to run cdrecord.

SunOS 4.1.3 only:
	The 'scg' driver is Copyright 1986-1995 J�rg Schilling,
	it is supplied binary in a loadable format.
	There is no future support, there is no non loadable support.

Solaris only:
	The 'scg' driver is Copyright 1986-1995 J�rg Schilling,
	it is supplied binary in pkgadd(1m) format and is tested
	on Solaris 2.3, Solaris 2.4 & Solaris 2.5 (sparc).

Solaris only:
	It is _nice to have_ the 'fbk' driver to mount files that contain
	images of file systems. Fbk means File simulates Block Device.

	The 'fbk' driver is Copyright 1988-1995 J�rg Schilling,
	it is supplied binary in pkgadd(1m) format and is tested
	on Solaris 2.3, Solaris 2.4 & Solaris 2.5 (sparc).

On other OS, libscg uses the SCSI drivers that are present on the system.

Cdrecord-1.3 or later adopts the right BUF_SIZE for each architecture.
This is to reduce some performance problems on Solaris x86.
It may be that the reason for this performance problems is that
the PC-architecture has no IO-MMU and therefore is not able to do DVMA.
If this points out to be the reason, I have to
change the scg driver & cdrecord, but this would
be needed on Linux anyway.

Cdrecord is currently maintained with the following drives:

	Plextor PX-W4824A
	Plextor PX-W4012A
	Plextor PX-W2410A
	Plextor PX-W1210S
	Plextor PX-W1210A
	Plextor PX-W124
	Plextor PX-W8220
	Plextor PX-W4220
	Plextor PX-R820
	Plextor PX-R412C
	Yamaha F-1
	Yamaha CRW-2200S
	Yamaha CRW-2200A
	Yamaha CRW-2100S
	Yamaha CRW-4416
	Yamaha CDR-400
	Ricoh MP-7040A
	Ricoh MP-7040S
	Ricoh MP-7060S (available only to Thomas Niederreiter and Heiko Ei�feld)
	Ricoh MP-7063A
	Ricoh MP-7080A
	Ricoh MP-7083A
	Ricoh MP-9060A
	Ricoh MP-7163A
	Ricoh DVD+RW MP5125	(DVD+ writing not yet supported)
	HP DVD-200i		(DVD+ writing not yet supported)
	Philips DVD-RW 1208	(DVD+ writing not yet supported)
	TEAC CD-R55S
	TEAC CD-R58S
	TEAC CD-W54E
	TEAC CD-W28E
	Sanyo CDR-Bp2
	Sanyo CDR-Bp3A
	Sony CDU948S
	Sony CRX-145E
	Sony CRX-200E		(DDCD writing not supported)
	COMPRO/Matsushita/Panasonic CW-7502
	COMPRO/Matsushita/Panasonic CW-7586
	Philips CDD-2000
	Philips PCRW-804
	Goldstar LG 8080
	AOPEN CRW-4048
	Cyberdrive CW-038D
	Cyberdrive CW-078D
	Pioneer DVD-R A03

It should run also on:

	All SCSI-3/mmc compliant drives
	All ATAPI/mmc compliant drives

	NOTE:

	It seems that all drives that have been initially released in 1999
	or later are MMC compliant. If a recent drive does not work with
	cdrecord, you most likely found a firmware bug in this drive.
	Contact your drive vendor in this case.

Drives that have been reported to work or should work because
Andy MCFadden (see also http://www.fadden.com/cdrfaq/faq05.html) listed
them to be identical to working drives. Note that this list may be outdated

	ACER CR-1420C
	ACER CDRW 6206A
	AOPEN CRW9420 (Re-writable)
	BTC BCE 621E
	COMPRO CW-7502
	COMPRO/Matsushita/Panasonic CW-7586
	Dysan CR-622 ???? See Wearnes 622
	Dysan CR-1622
	DynaTec CDM-240J (see Pinnacle RCD-4x4)
	DynaTec CDM-240  (use cdrecord driver=yamaha_cdr100 and report inquiry)
	DynaTec CDM-400  (use cdrecord driver=yamaha_cdr100 and report inquiry)
	Grundig CDR-100
	Hewlett Packard 4020i
	Hewlett Packard 6020i
	HP C4324/C4325 (HP SureStore 4020i/6020i)
	HP 7100
	HP 7110
	HP 7200
	HP 8100
	HP 8210
	HP CD-Writer+ M820
	Hi-Val CD-R (see Pinnacle RCD-4x4)
	IMATION CD-RW IMW040420
	JVC XR-W2001 (uses TEAC code - see below - audio not working)
	JVC XR-W2010 (uses TEAC code - see below - audio not working)
	JVC XR-W2020 (uses TEAC code - see below - audio not working)
	JVC XR-W2080 (first MMC drive from JVC)
	Kodak PCD-200 or Kodak PCD-200 Plus
	Kodak PCD-225
	Kodak PCD-240
	Kodak PCD-600
	Matsushita CW-7502
	Matsushita CW-7503
	Matsushita CW-7582
	Matsushita CW-7586
	Memorex CR-622 ???? See Wearnes 622
	Memorex CR-1622
	Memorex CRW-1622
	Microboards PlayWrite 2000 (use cdrecord driver=sony_cdu924 and report inquiry)
	Microboards PlayWrite 4000 (use cdrecord driver=yamaha_cdr100 and report inquiry)
	Microboards PlayWrite 4001RW
	MicroNet MasterCD Plus 4x4 (use cdrecord driver=yamaha_cdr100 and report inquiry)
	MicroNet MasterCD Plus 4x6
	Mitsubishi MCA-CDRW 226
	Mitsumi CR-2401-TS
	Mitsumi CR-2600-TE
	Mitsumi CR-2801-TE
	Mitsumi CR-4801-TE
	Mitsumi CR-4802-TE ???
	Nomai 680.rw
	Olympus CDS615E
	Olympus CDS620E (use cdrecord driver=sony_cdu924   and report inquiry)
	Olympus CD-R2x6 (use cdrecord driver=sony_cdu924   and report inquiry)
	Optima Dis Kovery 650 CD-R
	OTI CDRW 965
	OTI-975 Socrates 1.0 (CDRW)
	Panasonic CW-7502
	Panasonic CW-7503
	Panasonic CW-7582
	Panasonic CW-7586
	Philips CDD 521 (CDD521/02  Revision: 2.06 has bad firmware - seems not to work)
	Philips CDD 521 (upgraded units only: ID: CDD521/10  Revision: 2.07)
	Philips CDD 522
	Philips CDD 2000
	Philips CDD 2600
	Philips CDD 3600
	Philips CDD 3610
	Philips CDRW400
	Philips Omniwriter 26
	Philips Omniwriter 26A
	Philips CDD4201 CD-RW
	Philips PCRW-804
	Pinnacle Micro RCD-1000 (see TEAC/JVC): Need to upgrade firmware to 2.35
	Pinnacle Micro RCD-5020 (see TEAC/JVC - audio not working)
	Pinnacle Micro RCD-5040 (see TEAC/JVC - audio not working)
	Pinnacle Micro RCD-4x4
	Pioneer DW-S114X
	Plasmon CDR 4220
	Plasmon RF-4100
	Plasmon RF-4102
	Plasmon CDR 4400 (use cdrecord driver=yamaha_cdr100 and report inquiry)
	Plasmon CDR 480
	Plextor PX-R24CS (use cdrecord driver=ricoh_ro1420c and report inquiry)
	Plextor PX-R412C
	Plextor PX-R820
	Plextor PX-W4220
	Plextor PX-W8220
	Plextor PX-W124
	Plextor PX-W1210S
	Plextor PX-W1210A
	Procom PCDR 4 (use cdrecord driver=yamaha_cdr100 and report inquiry)
	Ricoh RO-1420C
	Ricoh MP-6200
	Ricoh MP-6200I
	Ricoh MP-6201
	Ricoh MP-7040A
	Ricoh MP-7040S
	Ricoh MP-7060S
	Ricoh MP-7063A
	Ricoh MP-7080A
	Ricoh MP-7083A
	Ricoh MP-9060A
	Sanyo CDR-Bp2
	Sanyo CDR-Bp3
	Smart & Friendly CD-R1002 (use cdrecord driver=sony_cdu924   and report inquiry)
	Smart & Friendly CD-R1004 (use cdrecord driver=yamaha_cdr100 and report inquiry)
	Smart & Friendly CD-R2004 (use cdrecord driver=sony_cdu924   and report inquiry)
	Smart & Friendly CD-R2006 PLUS
	Smart & Friendly CD-R2006 PRO
	Smart & Friendly CD-R4000 (use cdrecord driver=yamaha_cdr100 and report inquiry)
	Smart & Friendly CD-R4006
	Smart & Friendly CD-R4012
	Smart & Friendly CD-RW226
	Smart & Friendly CD-R8020
	Sony CDU920S
	Sony CDU924S
	Sony CDU926S
	Sony CDU928S
	Sony CDU940S
	Sony CDU948S
	Sony CRX-100
	Sony CRX-140
	Sony CRX-145
	Taiyo Yuden CD-WO EW-50
	TEAC CD-R50S
	TEAC CD-R55S
	TEAC CD-R56S
	TEAC CD-R58S
	TEAC CD-W54E
	That's Write CDR-N820S
	Traxdata CDRW-2260EL-PRO
	Traxdata CDR-4120
	Traxdata CDRW-4260
	Turtle Beach 2040R (use cdrecord driver=ricoh_ro1420c and report inquiry)
	WAITEK WT2036
	Wearnes CD-R622
	Wearnes CD-R632P
	Yamaha CDR-100
	Yamaha CDR-102
	Yamaha CDR-200
	Yamaha CDR-400(Firmware revision 1.0d and up otherwise upgrade)
	Yamaha CDR-401
	Yamaha CRW-4001
	Yamaha CRW-2260
	Yamaha CRW-2261
	Yamaha CRW-4260
	Yamaha CRW-4261
	Yamaha CRW-4416
	Yamaha CRW-6416
	Yamaha CRW-8424
	Yamaha CRW-2100

Multi-session has not been tested with the Plasmon RF-4100

All companies that support me with SCSI command reference manuals and drives
will get (continued) support in the following releases.

The following drives will never be supported by cdrecord because they are too old:

	JVC XR-W1001
	Pinnacle Micro RCD-202
	Ricoh RS-9200CD

The following drives are currently not supported because I don't get specs:
(some of them may partially work: see above)

	Creative Labs CDR 4210
	JVC XR-W2001
	JVC XR-W2010
	JVC XR-W2020
	Pinnacle Micro RCD-1000
	Pinnacle Micro RCD-5020
	Pinnacle Micro RCD-5040
	Plasmon CDR-4240
	Sony CDW-900E

The following drives may get support soon (If I get time to do so):

	Panasonic CW-7501
	Ricoh RS-1060C

If you understang German, it makes sense to have a look at http://www.dchlb.de/
and http://www.brennmeister.com/ for additional information.

To install get:

Solaris only:
	SCHILYscg.sparc.tar.Z	The scg driver in pkgadd format (sparc).
	SCHILYfbk.sparc.tar.Z	The fbk driver in pkgadd format (sparc).
	SCHILYscg.i386.tar.Z	The scg driver in pkgadd format (x86).
	SCHILYfbk.i386.tar.Z	The fbk driver in pkgadd format (x86).

Note that the fbk driver packet is for Solaris 2.4 and not system independent.

All Systems:
	cdrtools-2.0.tar.gz	The cdrtools for source distribution.

NOTE:	All these tar archives are 100% ansi compatible. Solaris 2.x tar and GNU
	tar may get some minor trouble.

WARNING: Do not use 'mc' to extract the tar file!
	All mc versions before 4.0.14 cannot extract symbolic links correctly.

To unpack the archive use:

		gzip -d < cdrtools-2.0.tar.gz | tar -xpf -

	Replace 'cdrtools-2.0' by the actual archive name.

	If your Platform does not support hard links or symbolic links, you
	first need to compile "star" and then call:

		star -xpz -copy-links < cdrtools-2.0.tar.gz

	If your platform does not support hard links but supports
	symbolic links, you only need to call the command above once.
	If your platform does not support symbolic links, you need to call
	the command twice because a symbolic link may occur in the archive
	before the file it points to.





The files are located on:

https://sourceforge.net/projects/cdrtools/files/ ...
https://sourceforge.net/projects/schilytools/files/kernel/scg/ ...
https://sourceforge.net/projects/schilytools/files/kernel/fbk/ ...

Only use the mkisofs that is contained in this release.
All other mkisofs versions are too buggy.


Installation Process:

Solaris only:
	1) scg driver
			untar SCHILYscg.tar:
			su
			Password: xxxxx
			cd /tmp
			zcat SCHILYscg.tar | tar -xvf -
			pkgadd -d .
			reboot -- -r

	2) fbk driver
			similar to scg driver (see above)

	3) Switch the CD-Writer to an unused target id (2 should do it)


NOTE:
	Be very careful. pkgadd does not check for the right target
	architecture. Do not install drivers for intel on sparc
	and vice versa. You will get a corrupt system.

	You need to be root because you need access to /dev/scg? and to be
	able to put cdrecord into the real-time scheduling class.

All Systems:

The SCSI transport library has been taken from the sformat program.
Sformat is the first SCSI disk formatting/analyzing/repairing that runs on
SunOS/Solaris. The first release of sformat has been made for SunOS 3.0
(two years before Sun introduced their format utility). Sformat source
including 10 years of competence in SCSI disk handling is available
on:
	https://sourceforge.net/projects/schilytools/files/sformat/
	https://sourceforge.net/projects/schilytools/files/schily-*

I am interested to hear if someone is interested in a kernel based
filesystem for Solaris that uses packet writing on the CD-Recorder.
The filesystem will create a single session CD that may be finally converted
to a hybrid filesystem that allows to be read as
ISO-9660 with Rock Ridge extensions too.
Please mail suggestions to: joerg@schily.net

If you want to use the CD-recorder as CD-ROM device, have a look at

Solaris only:
https://sourceforge.net/projects/schilytools/files/kernel/sd/

Current information on cdrecord may be found on:

	http://cdrecord.org/private/cdrecord.html


	Joerg Schilling

	(really J�rg Schilling if you have ISO-8859-1)

If you have questions mail to:

	joerg@schily.net

# @(#)README.ATAPI	1.7 20/11/21 Copyright 1997-2004 J. Schilling

People (with a Linux only background) often ask me why do you depend on
"ATAPI-SCSI emulation", why don't you support generic IDE?

First a note: there is no SCSI emulation on Linux, but there has been
some kind of SCSI integration. To explain the difference between SCSI emulation
and SCSI integration let us look at an Operating system that implements both,
Windows NT:

Win NT implements SCSI integration, if you open "\\\\.\\SCSI%d:", BusNo,
you will be able to send generic SCSI commands to any SCSI speaking drive
on that bus. ATAPI drives just show up on a specific Busnumber, SCSI drives
that use a 50 or 68 pin connector show up on different Bus numbers.
Note that Microsoft obviously did copy my ideas I did implement in August 1986
for SunOS-3.0 :-)

Win NT implements SCSI emulation by not only showing drives that natively
talk SCSI on the ATA/IDE cable, if you send generic SCSI commands via ioctl's
to "\\\\.\\SCSI%d:", BusNo. Win NT also shows you plain ATA drives that do not
understand SCSI commands in firmware. Win NT allows you to send SCSI
commands to the kernel and the kernel translates the SCSI commands to ATA
commands with the same meaning, so Win NT emulates SCSI for ATA drives.

Linux does not emulate SCSI command transport for vanilla ATA drives, so there
is definitely no SCSI emulation in Linux.


	You need to believe me: There is no single IDE burner out!
	Even a CD-ROM cannot be used decently if you use only IDE/ATA commands.
	Opening/closing the door, playing audio and similar things
	cannot be done using vanilla IDE commands - you will need SCSI commands
	to do this. But how do we do this with a drive that uses an IDE
	interface?

		ATAPI stands for ATA Packet Interface

	The ATAPI standard describes method of sending SCSI commands over IDE
	transport with some small limitations to the "real" SCSI standard.
	SCSI commands are send via IDE transport using the 'ATA packet'
	command. There is no SCSI emulation - ATAPI drives include native
	SCSI command support. For this reason, sending SCSI commands to ATAPI
	drives is the native method of supporting ATAPI devices. Just imagine
	that IDE is one of many SCSI low level transport mechanisms.

	This is a list of some known SCSI transports:

	-	Good old Parallel SCSI 50/68 pin (what most people call SCSI)
	-	SCSI over fiber optics (e.g. FACL - there are others too)
	-	SCSI over a copper variant of FCAL (used in modern servers)
	-	SCSI over IEEE 1394 (Fire Wire)
	-	SCSI over USB
	-	SCSI over IDE (ATAPI)

	As you now see, the use of the naming convention "ATAPI-SCSI emulation"
	is a little bit misleading. It should rather be called:
		"IDE-SCSI host adapter emulation"

Some naming explanations:

	ATA	Attachment Adapter
	IDE	Integrated Drive Electronics (A Drive that includes ATA)
	ATAPI	ATA Packet Interface

When cdrecord has problems with ATAPI drives on Linux this usually is a Linux
kernel problem. The Linux kernel maintainers unfortunately refuse to correct
their current IDE driver system setup which does not support ATAPI by default.
ATAPI _is_ SCSI over IDE transport. It is hard to understand why Linux still
uses a default driver setup that is designed for IDE CD-ROM drives made
before 1994 (using a IDE compat mode that only allows to use the drive
read-only) and does not handle to send SCSI commands to ATAPI drives by
default. This makes it hard for people who just started with Linux to do
CD-writing on Linux if they own an ATAPI drive. Both Linus Torvalds and
Alan Cox admit that they don't own a CD/DVD writer, how should they know about
the problems?

There are bugs with the DMA implementation that are known for many years
but they don't get fixed.

/*--------------------------------------------------------------------------*/
Which Operating systems support ATAPI

-	AIX: Status unknown! Please report your experience...

-	Apple Mac OS X (Darwin): Supported

-	BeOS (libscg maps ATAPI to SCSI bus # >= 8

-	BSD/OS: Status unknown! Please report your experience...

-	FreeBSD:
		-	YES for the latest default kernel.
			It includes finally ATAPI-Cam

		-	NO for the older kernels.
			Yes, if you install a kernel patch from
			Thomas Quinot <thomas@cuivre.fr.eu.org>
			See http://www.cuivre.fr.eu.org/~thomas/atapicam/
			and README.FreeBSD

-	HP-UX: It looks like ATAPI does not work correctly due to kernel bugs.

	New information:
	HP supports a HP A7853A B/C class machine (s700_800) with HP-UX-11.x
	You need to install a patch:

	Patch Name: PHKL_27224 Patch Description: s700_800 11.00 IDE/ATAPI
	cumulative patch


-	Linux (unfortunately not in the default configuration)

	-	It works more or less if you include ide-scsi

	-	Linux-2.4.xx includes a CDROM Packet interface in the
		IDE CD driver. For this driver libscg now includes
		support in pre-alpha status. Use cdrecord dev=ATAPI -scanbus
		to check for drives and e.g. cdrecord dev=ATAPI:0,0 ....
		for writing. Note that this interface is not integrated into
		the standard libscg device naming scheme. Support for
		this interface has been included because it is the only
		way to use a PCCARD/PCMCIA writer - trying to use ide-scsi
		on a PCATA interface will cause a Linux kernel panic
		or will block all ATAPI drives.

	-	Starting with Linux-2.5.45, there is a new experimental
		ATAPI interface initiated by Linus Torvalds. Unfortunately,
		this interface does not fit well into the rest of the Linux
		SCSI kernel transport naming scheme. Cdrecord allows to
		use this interface by calling e.g. cdrecord dev=ATA:1,0,0 ...

	All Linux ATAPI transport implementations do not support DMA.
	Current exceptions are:

	-	ide-scsi with block size 2048 and if DMA has been enabled

	-	The new experimental ATAPI interface starting with Linux-2.5.45
		allows DMA if DMA has been enabled and the sector size is a
		multiple of 4. This allows to use DMA for audio CDs and
		when writing any type of CD in RAW mode.

		Note that is a bad idea to first implement a new kernel
		interface that also implements the named DMA implementation
		bugs and later fix the DMA bug _only_ for this new
		interface. It looks like the Linux kernel folks are not
		very cooperative :-(

	RAW mode is needed for many new and cheap drives that have bugs when
	writing in cooked mode. If there is no DMA, you cannot write faster
	than approx 16x.


-	NetBSD (releases 1.3 and newer)

-	NeXT: Status unknown! Please report your experience...

-	OpenBSD: (release 2.6 and newer)

-	OS/2 (you need to fetch and install ATAPI support first)
	see: http://www.leo.org/pub/comp/os/os2/leo/drivers/dasd/daniatapi.zip/

-	OSF-1 / True64 Status unknown! Please report your experience...

-	SCO-OpenServer: Supported with 5.0.6 and non-public patch or with
			5.0.7. I don't know whether you need a patch for 5.0.7

-	SCO-UnixWare: partial support with UnixWare 7.1.3 - some SCSI commands
			that are needed for cdda2wav and DVD writing are blocked.
			7.1.4 will have full ATAPI support.

-	SGI/IRIX: Status unknown! Please report your experience...

-	Solaris (you may need to use the USCSI transport interface to address
	ATAPI if the IDE hostadapter idriver implementation does not follow
	Sun's internal standards).

	ATAPI works fine on Solaris 7 sparc and on Solaris 7/8 intel.

	On Solaris 8 (intel) and newer, the ATAPI/SCSI subsystem is integrated
	correctly according to Sun's SCSA white paper, so the 'scg' driver works.
	This is not true for Solaris on sparc where the ATAPI driver do not conform
	to Sun's internal structuring rules. You need to use the USCSI interface
	on for ATAPI drives on Solaris sparc for this reason.

	Solaris 8 sparc has a ATA DMA bug that prevents cdrecord from working at all.
	There is a fix from Sun available: the patch 108974-16
	Solaris 9 sparc works again, it has the fix for the ATA DMA bug included.

	Newer versions of Solaris 9 disable DMA for CD-ROM drives on IDE.
	Read README.solaris-x86-ATAPI-DMA to learn how this may be circumvented.

-	VMS: works on recent versions!

-	Win32 using a recent ASPI Layer supports ATAPI
	You nay need to exclude mini port drivers (see README.win32).

	Newer cdrecord versions also support the SPTI (SCSI Pass through ioctl).
	Libscg uses SPTI by default if you are running NT-5.x or newer and are
	administrator. With NT-4.x it may be possible to run cdrecord dev=SPTI:1,0.0 ...
	But there are reports for blue screens (kernel crashes).

-	DOS DOS-7 from win98 includes a ATAPI aware aspi
	For other versions have a look at README.msdos and use e.g. "oakaspi".

/*--------------------------------------------------------------------------*/
General hints:

***********************
NOTE: IDE/ATAPI doesn't have disconnect/reconnect! you cannot expect the needed
	performance for CD-writing if you connect source and destination drive
	to the same IDE cable.
***********************

If you never like to directly write a CD from CD-ROM source, this configuration
seems to be the best:

IDE 0	MSTR	->	HD1
IDE 0	SLAV	->	HD2

IDE 1	MSTR	->	CD-writer
IDE 1	SLAV	->	CD-ROM

If you like to write from both HD source and CD-ROM source, you should have
the following configuration:

IDE 0	MSTR	->	HD1	(does _not_ hold CD mastering data)
IDE 0	SLAV	->	CD-Writer

IDE 1	MSTR	->	HD2	(holds CD mastering data)
IDE 1	SLAV	->	CD-ROM

If cou cannot set up a decent cabling (e.g. because you use a notebook)
you may try to use cdrecord -immed ...
It runs slow commands in quick (immediate) return background mode and
tries to wait between the write commands to allow to free the IDE cable
so the cdrecord read process may fill the FIFO from the other drive
on the same IDE cable.

/*--------------------------------------------------------------------------*/
The rest of this file is only valid for Linux!

This was taken out of mails from From: Dave Cohen <dcohen@richmond.infi.net>
and From: Gadi Oxman <gadio@netvision.net.il>
(slightly modified marked ***JS *** except typo corrects)

As all actual Linux versions have ATAPI support for cdrecord,
I removed the patch section. If you are running a Linux version
that does not support ATAPI<->SCSI command transport, please upgrade.

The basic driver design in Solaris would also allow to use ATAPI
drives but unfortunately, Sun made a mistake in the mid-level design.
If you want to use ATAPI drives with Solaris, ask Sun why they don't
support SCSI passthrough to IDE although they are using a common driver
concept.

Please use cdrecord-1.6 final or later (if available), it includes the
modifications needed for ATAPI drives and is still working with other
SCSI drives. Older revisions of cdrecord do not support ATAPI drives.

If you are using Linux Kernel version prior to 2.1.73 or prior to
2.0.35, please upgrade before you try to compile and use cdrecord.

In any case, you need to configure a kernel with ATAPI/SCSI hostadapter
emulation. Read carefully the following instructions:

In any case, you need to disable generic IDE/ATAPI CDROM support in
order to make ATAPI SCSI emulation working.

Many people ask why I use ATAPI-SCSI emulation.

	The use of the naming convention "ATAPI-SCSI emulation" is a
	little bit misleading. It should rather be called:
		"SCSI host adapter emulation"

	The ATAPI standard describes method of sending SCSI commands over IDE
	with some small limitations to the "real" SCSI standard.
	For this reason ATAPI-SCSI emulation is the native method of
	supporting ATAPI devices.

If you have problems to talk to the device when it is jumpered as "slave"
try to use it  as "master". If you connect a hard disk to the same IDE
cable as the CD writer or if you try to read/write data from another drive
that is connected to the same IDE cable as the CD writer you may get
problems too.

NOTICE:

With the newer 2.1.x or 2.2.x kernels it seems to be possible to run
SCSI/ATAPI hostadapter emulation and generic IDE at the same time by
selectively telling the kernel what to use for which drive.  However,
this would not be needed if the Linux SCSI CD-ROM driver would be more
up to date and supports standard conforming drives.

J�rg Schilling <joerg@schily.net>

--------------------------------------------------
Here is a hint from Alan Brown <alanb@manawatu.gen.nz>:

To allow ATAPI cd and ide-scsi support on the same machine, add
`hd<x>=ide-scsi` to the lilo.conf append entry, or use
`hd<x>=ide-scsi` at the bootup lilo prompt.

I have my HP-7200 RW drive as the primary drive on the second IDE
bus, so the statement used is "hdc=ide-scsi"

--------------------------------------------------

Hope that the following  is helpful to you.

I recently purchased a HP-7110i CD-RW, which is the U.S. only version of
what you have. The HP 7100 and 7110  CD rewritables use the ATAPI
standard. Originally, the drives were not supported under Linux (due to
some inconsistencies with SCSI translations between the kernel and the
CD), but that problem has just recently been fixed. There are some kernel
and cdrecord patches that have been made to support this device that have
yet to be officially incorporated into cdwrite and the kernel. In order to
get your drive supported under Linux, you will have to do the following:

1. Get the proper version of cdrecord.

As of this writing, I am just getting ready to test Joerg's new cdrecord.
I am currently operational on cdrecord-1.5, so I know that works, and I
have attached patches for that version.

If you are in a hurry, you can download ver. 1.5, apply patches, and
rock-n-roll. You may want to wait, though.  Up to you ;). The version with
ATAPI support is cdrecord-1.6alpha5. I'm not sure if the current kernel
patches are valid for this version, but i'll know soon enough.
**** They are valid **** JS

BTW, the new version of xcdroast now supports cdrecord - this version
is in beta testing, too (currently uses cdrecord-1.5 but cdrecord-1.6a5
should work with the actual xcdroast too).

2. Upgrade to kernel version 2.0.31

IDE/SCSI translation was first added in this kernel. Because your CD-RW is
an ATAPI device, it will support SCSI command sets.  The translation
allows you to map the device as a SCSI generic device. This will allow
cdrecord to recognize it as a SCSI device.
**** 2.0.31 still needs patches, get 2.0.35 or later **** JS

3. Get the patches and apply them

Attached find kernel patches for kernel sources ide.h and ide-scsi.c, and
cdrecord source scsi_cdr.c (version 1.5 only).
**** Get cdrecord-1.6 or later **** JS

3. Recompile kernel with SCSI emulation support

If you do a "make menuconfig" or "make xconfig", select SCSI emulation
under the category "Floppy, IDE, and other block devices".

WARNING:
Do not install SCSI support as a module - there is a bug in the makefile
structure that will cause the compile to fail.  Compile directly into the
kernel.

4. WARNING: Disable generic IDE/ATAPI CDROM support	*** JS ***

If you don't do this, the SCSI emulation will not work  *** JS ***

5. This is important too:
You also need to enable SCSI and SCSI generic support   *** JS ***

6. Make sure that /dev/sg* exists.
If they are missing, create them.

Dave Cohen
dcohen@richmond.infi.net
(Patch instructions below)

-----------------------------------------------------------------
From: Danilo Fiorenzano <shade@juliet.gppsd.ab.ca>

Anyway, here's what I did, using kernel version 2.0.33  I believe this
is the proper way to get an HP-7100i to work (and as far as I can tell,
any other IDE CD-writer unit):

1) patch the kernel as described by README.ATAPI

2) save your current kernel config to an alternate file, then run
   "make mrproper"

3) run 'make menuconfig' or 'make xconfig', then choose "load config
   from alternate file" to restore the original configuration

4) In "Floppy, IDE and other block devices", disable "IDE/ATAPI CD-ROM
   support" and enable instead "scsi emulation"

5) in "SCSI support" enable "SCSI support", "SCSI CD-ROM support" and
   "SCSI generic support", everything directly in the kernel.

6) compile, install kernel/modules, reboot.  Now, if everything went
   fine, your CDROM units should show up with a message like:
 "hdb: HP CD-Writer+ 7100, ATAPI CDROM drive - enabling SCSI emulation"

7) run "cdrecord -scanbus" to make sure cdrecord can see the unit and
   talk to it.  The end.

Don't forget that now -all- of your CD drives are seen as -SCSI- units
by all programs (/dev/scd0 etc.), so you might want to relink
/dev/cdrom to the proper scd<n> in order to get xcdplay or whatever to
work again.


-------------------------------------------------------------------------------
NOTE:

1)	Actual cdrecord releases support ATAPI

2)	Linux 2.0.35 or Linux 2.1.73 or later include ATAPI support
-------------------------------------------------------------------------------
From whampton@staffnet.com Fri Jan 14 05:21:34 2000
From: "W. Wade, Hampton IV" <whampton@staffnet.com>

You may wish to include/append these notes to your ATAPI notes....

I have my 4X Acer CD-R/RW ATAPI drive working with Linux.   My platform
is
RedHat 6.1 with kernel 2.2.14.  My first ATAPI CD device is a DVD with
the second
the CD-R.  I made the following changes:

Steps:

1.  Identify which device is the CD-R -- in my case the fourth ATAPI
device, /dev/hdd.

2.  Compile the kernel to include ATAPI CDROM and SCSI emulation:

     Under the block devices menu:
                Y or M     Include IDE/ATAPI CDROM support
                Y or M     SCSI emulation

3.  Build and install the upgraded kernel.

4.  If you selected modules, add them to the /etc/conf.modules file.

5.  In the /etc/lilo.conf file add an append line for ide-scsi, in my
case:
        append = "hdc=ide-scsi hdd=ide-scsi"

6.  Reboot to the new kernel and make sure the ide-scsi module is loaded

        /sbin/lsmod | grep ide-scsi

7.  Make a link from the proper SCSI device to a symbolic, e.g.,
/dev/cdrom:
      In my case the DVD is the first CD, hence appears as /dev/scd0 to
scd7
      (cat /proc/scsi/scsi to get a full list of devices -- the first
CD-ROM will
      appear as scd0, etc.)  With the current ATAPI-SCSI module, each CD

      device appears as 8 SCSI devices (different logical units).  If
you have
      two devices, like I do, you may have to make a node for the second
device.
      In my case I had to make scd8:

            cd /dev
            mknod scd8 b 11 8

        Then make links, in my case:

            ln -s scd0 cdrom
            ln -s scd8 cdr

        Note, many CD-ROM player programs expect the audio CD drive to
        be located at /dev/cdrom (xplaycd, etc.), hence this link is
recommended.

        If you try to use /dev/hdc (or wherever your CD or CD-R is)
after loading
        the ide-scsi module, you may not be able to mount CD's or play
audio
        discs -- you have to use the new SCSI names for the device.

8.  Fix your /etc/fstab file to mount the /dev/cdrom and /dev/cdr


/*--------------------------------------------------------------------------*/
From: Eduard Bloch <edi@gmx.de>

Situation:
   Linux: Kernel 2.2.15 (Debian package kernel-image-2.2.15)
   Distribution: Debian Potato (deep freeze), i386
   Devices: one CDRW-Writer, one CDROM-drive, both ATAPI

1. Become root, try "grep hd.: /var/log/kern.log" to find out where your
   ATAPI-devices are connected to (hd?-names).
2. Edit your boot configuration file, eg. /etc/lilo.conf if you use
   lilo or the batch-file if you boot via loadlin.
3. Find a line where you can append additional kernel parameters, eg.
   "append=" in lilo.conf or the loadlin-line in the batch file.
4. Append sth. like this: "hdb=ide-scsi hdc=ide-scsi max_scsi_luns=1"
   The hdX-parameters defines devices that should be mapped to SCSI
   latter. You may do it with non-writers too, since the emulation layer
   is almost complete, or let them out so the devices will use their
   native drivers.
5. Save the file, reinstall the bootloader (ie. running "/sbin/lilo")
6. Call "modconf", load "sg" and "ide-scsi" from the SCSI-section
7. Reboot Debian, watch while booting, you should see a line like this
   "Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0".
   Your old ATAPI devices virtually don't exist any longer, use the
   SCSI equivalents instead.
8. Become root, setup devices:
      cd /dev
      MAKEDEV sg scd
      ln -s scd0 cdrom # NOTE: or cdrw, first check which drive is here
      ln -s scd1 cdrw  # NOTE: see above, maybe cdrom
   Check the new SCSI settings:
      cdrecord -scanbus
   Setup cdrecord's environment - edit /etc/default/cdrecord:
      CDR_DEVICE=cdrw
      cdrw=1,0,0        4       8m
      cdrom=1,2,0       0       0m
   Input the right values, the fields are described in the manpage
   of cdrecord. Alternatively, you may use this values as
   cdrecord-parameter or take a frontend with an own configuration
   scheme, then you don't need to modify /etc/default/cdrecord.
9. It's done! Insert a CD and try "cdrecord -v -toc"
/*--------------------------------------------------------------------------*/
He had constant buffer underrun problems:

From: "Trenton D. Adams" <trenton.adams@telusplanet.net>

I enabled DMA, and 32-bit mode on the CD-Writer using "hdparm".
This fixed the writing problem.

/*--------------------------------------------------------------------------*/
From: "Mario Moder" <clay-man@freenet.de>
-----
TEAC CD-W54E

I recently installed a TEAC CD-W54E (an ATAPI CD-RW-Recorder) and I had
problems with buffer underruns and other errors when burning a CD (with
Linux and Windows 2000). My system has an old ASUS P/I-P55T2P4 Pentium
mainboard with Intel PCI-Bus-Master-IDE (I think the chipset is an Intel
430HX and the IDE controller is an 82371SB). The harddisk is the master on
the primary IDE channel, and the CD-Recorder is the master on the secondary
IDE channel.

After turning off DMA for the CD-Recorder AND the harddisk, the drive had no
longer problems with burning a CD. You can try the following things to make
it work, if you have similar problems with a similar hardware configuration:

For Linux (Kernel 2.2.19):
Turn off "Enable DMA by default" in the kernel (and then compile a new
kernel), if you had it turned on or use "hdparm" to turn of DMA for both the
CD-Recorder and the harddisk

For Windows 2000:
In the Device Manager go to "IDE ATA/ATAPI-Controller" and open the
properties for the first and second IDE channel. There you change the mode
of the devices from DMA to PIO.
-----

/*--------------------------------------------------------------------------*/

Hints for the Linux Packet code in ide-cdrom.c:

	WARNING! It seems that this driver does not allow to send all
	SCSI commands. A command that definitely fails is READ FULL TOC.
	For this reason, you cannot read those 'defective' audio CDs
	with broken TOC when you use this interface.

	Thanks to Alexander Kern <alex.kern@gmx.de> for the idea and first
	code fragments for supporting the CDROM_SEND_PACKET ioctl() from
	the cdrom.c kernel driver. Please note that this interface in principle
	is completely unneeded but the Linux kernel is just a cluster of
	code and does not support planned orthogonal interface systems.
	For this reason we need CDROM_SEND_PACKET in order to work around a
	bug in the linux kernel that prevents to use PCATA drives because
	the kernel panics if you try to put ide-scsi on top of the PCATA
	driver.

	The code is currently in "status nascendi" but usable with some trade offs.

	To use: call e.g.

		cdrecord -scanbus dev=ATAPI:

		cdrecord -dao -v speed=24 dev=ATAPI:0,0 ....

	Be careful! This code is only needed in order to be able to use
	PCATA CD-writers on notebooks because there is a severe kernel bug.
	Unfortunately, this bug causes the kernel to hang (and force you
	to reboot) if you try to call:

		cdrecord -scanbus

	without the dev=ATAPI: option.

	In this case cdrecord will hang infintely and unkillable
	in open("/dev/sg1", 2) => you need to reboot :-(

	Repeat by: Insert a PCATA CD-Writer in a Sony VAIO notebook and run
			cdrecord -scanbus.

New driveropts= option "tattoofile=". Use together with -checkdrive
to write an image of the right size to disk.

	DiskT@2 hints:

	In order to have "DISKTATTOO" listed in the "Driver flags",
	the disk currently inserted must be usable for the DiskT@2 feature.
	This means that there needs to be enough space on it.

	You need an B&W image with 3744 pixels per line

	Best start with a 3744 x 320 pixel image.
	The correct size may be retrieved with
		cdrecord driveropts=tattooinfo -checkdrive

	To get RAW image data:

	-	Take 'xv' and save the image in PBM/PGM/PPM (raw) mode

	-	use a binary aware (must support unlimited linelength)
		editor such as 'ved' and remove the header lines.
		These lines look like:

		P5
		# CREATOR: XV Version 3.10a  Rev: 12/29/94 (PNG patch 1.2)
		# CREATOR: XV Version 3.10a  Rev: 12/29/94 (PNG patch 1.2)
		3744 144
		255

		Now you should have (in case of the file above) a file that
		has exactly 539136 Bytes.

	-	Note that the tattoo image must be left to right flipped
		(a mirror image).

From a hint from "E. Robert Bogusta" <rob23@tmr.com>:

Take an image, and do:

  djpeg myface.jpg | ppmtopgm | pnmflip -lr |
    pnmscale -xsi 3744 -ysi 320 | sed '1,/255/d' >myface.tattoo

So:
  djpeg extracts ppm from a jpeg. Use your favorite other way of getting
this far is you wish.

  ppmtopgm changes color to grey scale

  pnmflip -lr flips left to right, the small image is faster

  pnmscale makes it 3644x320 regardless of starting size. This may make it
look really odd on the CD if it doesn't start off the right size. More on
this after I try it.

  sed strips from the first line to the line containing 255, which is the
last header line.

Note that it would be better to use the actual height of the applicable image instead
of the maximum value of 320 and it would be even more correct to create an
image that has the right width/height ratio for the target on CD in order
get an undistorted view of the image on CD.

For best visibility, use black text on light background.

CD-R drives are anything but WORM drives, but older drives identify themselves
as WORM drives.
A Worm drive is able to write each sector once at any time without preparation.
A CD-R drives is not and never will be able to do this.
However some old drives identify as WORM drives.

For this reason the SCSI-3 standard tells CD-R drives simply CD drives
with multi media extensions.

Why do I hear only noise from my first audio CD?

You may have a byte swapping problem, try cdrecord -swab
but note that is is most unlikely that you need to use the -swab
option from cdrecord unless your input files are broken.
It makes more sense to find out why the inout files are not OK.

Cdrecord assumes Motorola/Network byte order (big-endian) on input
regardless of the byte order of the CD-Recorder. If Cdrecord
encounters a .wav file, byte order is corrected to match the byte order
of the .wav file.

Cdrecord by default uses Track at once. This always gives 2 seconds
pause between two audio tracks and loweres the audio quality.

For best audio CD quality, use cdrecord -dao (to write in Session At Once)
ot cdrecord -raw (to write in RAW mode). Note that there are a lot of drives
notably from Lite-ON that have defective firmware and will write defective
CDs if you use either TAO or SAO mode. In RAW mode, cdrecord has the
full control over the complete CD and the chance that the CD is OK
is much higher.

The 2 seconds pause between two audio tracks is the CD ***standard***

The standard says:
	Each track starts with 2 seconds of silence
	followed by at least 4 seconds of audio data.

For that reason the 2 second pause is generated by the CD-R drive in
Track at once (TAO) mode.

CD's that have no pause between two tracks are illegal (compared to RED BOOK).
These illegal disks may be made with Disk At Once (DAO) only.
In DAO mode the writing software needs to send the 2 seconds pause as
binary zeroes and therefore is able to create illegal disks by
sending audio data instead.

Some drives don't accept to write illegal disks even in SAO mode.
In this case, use the RAW mode. In RAW mode, the drive does not even
"know" what is going on and thus cannot prevent you from writing such
a disk.

This audio data (the last two seconds of a track in this case)
however are part of the next track from viewing the TOC of the disk.
Digital Audio Extraction programs that work correctly (as intended by the
CD standard) split the content of a CD into files by including the
pre-gap (usually holding 2 seconds of pause) at the end of the previous
track.

Joerg Schilling

Cdrecord allows you to create multi-session CD's with all
supported drives. Cdrecord comes with a hacked mkisofs
that allows you to that on even on systems that don't support
a sectorsize 2048 Bytes (e.g. SGI IRIX and old versions of Solaris)
or systems that don't support raw device access (e.g. OS/2 W95/W98/WNT).
This is possible because current versions of mkisofs may
use my scg driver to read the old session from the CD-Recorder.

According to www.cd-info.com, a CD+ is a CD with two sessions.
The first session is an audio session, the second session a data
session.

Creating a CD+ is first writing an audio session in
multi session mode and then writing a data session.

If you like to append a filesystem to a audio CD, first extract the
CD by calling:

	cdda2wav -B -vall

This first audio session may be written in TAO mode with the command

	cdrecord -multi -audio file1 ....

or in DAO mode with the command

	cdrecord -dao -multi -useinfo -audio file1 ....

To add the second session that contains the data track, you need
to create an ISO-9660 file system that starts not at sector 0.

With the current mkisofs, you must use the following method:


-	First call cdrecord -msinfo for your prepared multi-session audio CD.

	you will get something like 0,12345

-	Now call mkisofs:

	mkisofs -o fs.raw -C 0,12345 root_directory_for_new_cd

	replace 0,12345 with your actual cdrecord -msinfo output.

the image in fs.raw may now be written with cdrecord as second session.

See my README.multi for more info on how to create multi session CD's


The procedure again in short form:

	cdda2wav -vall -B

	cdrecord -multi -audio audio_tracks ....
or
	cdrecord -dao -useinfo -multi -audio audio_tracks ....

	cdrecord -msinfo ....
	(output is e.g. 0,12345)

	mkisofs -R -o cd_plus.raw -C 0,12345 root_dir_of_fs

	cdrecord -data cd_plus.raw
or
	cdrecord -multi cd_plus.raw

Note that most drives do not support to append the data session in SAO mode.
For this reason, it is recommended to add the -tao option to the cdrecord
command line that appends cd_plus.raw to the audio session.

Note: If you want to create an HFS hybrid as the data track, then you must
use the '-part' option to mkisofs. Otherwise, the data track will be mounted
as an ISO9660/Joliet CD when used on a Mac.

J�rg

Using CD-RW media Mini Howto FAQ

CD-RW drives usually support packet writing, but as there
is currently no usable UDF filesystem support you may only use
the simple cdrecord approach.

Cdrecord writes to CD-RW media in exactly the same way as it
does with CD-R.

You may erase a complete disk in preparation to reuse it.
Check the man page entry for the blank= option of cdrecord.
Not all drives support all blanking modes. Usually
blank=fast or blank=full are working.

CD-Text Usage (to copy CD-Text from master CD):

	cdda2wav -D 6,0 -vall -B	# To extract audio information
	cdrecord dev=6,0 -vv -toc	# To extract CD-Text information

	and then

	cdrecord dev=6,0 -v -dao textfile=cdtext.dat -useinfo *.wav
	or
	cdrecord dev=6,0 -v -raw96r textfile=cdtext.dat -useinfo *.wav

	If the CD-Text information contains more CRC errors than
	cdrecord can correct, you need to reload the CD and to
	re-read the CD-Text information from the master disk.

	Writing of CD-Text is supported for all drives that support
	CD-Text in SAO write mode and for all drives that support
	to write in RAW/RAW96R mode (use -raw96r in this case).

	NOTE: not all writers that support MMC SAO mode support
		to write CD-Text in this write mode.
		If you have a drive that does not support CD-Text
		but supports RAW/RAW96R mode use this mode as
		in RAW/RAW96R mode the drive does not need to know
		about CD-Text. This way even old drives like the
		Plextor PX-R 412C will write CD-Text.

	NOTE that cdda2wav will read CD-Text and fill in the
	CD-Text fields in the *.inf files if vou use -vall.

	The new cdda2wav option cddb= allows you to tell cdda2wav to
	retrieve CDDB information from freedb.freedb.org.
	cddb=0 means ask if ambiguous, cddb=1 means take first entry.
	The information in this case is filled into the fields
	in the *.inf files.

Creating a CD with CD-Text based on CDDB information from freedb.freedb.org:

	Tell cdda2wav to fetch data from freedb.freedb.org, call

	cdda2wav -D 6,0 -vall -B cddb=1	# To extract audio information/fetch CDDB data

	and then call

	cdrecord dev=6,0 -v -dao -text -useinfo *.wav
	or
	cdrecord dev=6,0 -v -raw96r -text -useinfo *.wav


If you like to create your own CD-text data for a CD use the
following method:

	First extract all tracks with cdda2wav -vall (see above),

	then edit the *.inf Files and add album and song titles.

	Now call cdrecord as if the *.inf files contain CD-Text
	information.

	Note that it is recommended to use less that 160 characters
	for a single string.

Hints for how to copy a CD using the clone method:

Step 1 (read master CD):

	Call "readcd dev=b,t,l -clone f=somefile" and the files

	somefile
	and
	somefile.toc

	will be generated.

	If the disk contains many sectors that are unreadable by intention,
	call "readcd dev=b,t,l -clone -nocorr f=somefile"


Step 2 (write copy):

	Call "cdrecord dev=b,t,l -raw96r -clone -v somefile"

If cdrecord complains that your drive does not support -raw96r, but the
drive is able to do clone writing at all, then cdrecord will propose you
a different write mode that works with the drive.

Ho to copy CD's and CD-R/CD-RW's

Copying audio CD's:

If you want to copy audio CD's, look for 'cdda2wav'. Be sure tu use use
at least a cdda2wav-0.95beta or later. Older releases will not read correctly
from SCSI-3/mmc compliant drives.

Copying data CD's:

The best way to copy a data disk is to copy the raw data on the master CD.
This may be done by reading the data from the raw device by using 'readcd'.


NOTE:	All CD-R's written in Track At Once mode end in two unreadable
	run-out sectors. If the disk has been written with a Yamaha CD-R100
	or with a Yamaha CD-R102, there are even more run-out sectors.

For this reason, you will not be able to read such a CD correctly with 'dd'.

I recommend to write all disks in Disk at Once mode if your drive
is supported in DAO mode with cdrecord. In addition, you may wish to
add padding (see cdrecord / mkisofs man pages).

If you want to copy such a CD directly with cdrecord, you may call:

	cdrecord -v dev=... -isosize /dev/rdsk/c0t6d0s0

But this may fail if the master gives read errors. To copy such a CD to a file
you may use the program 'readcd' from this package

Call 'readcd [target] [lun] [scsibusno]' and select function 11.
Or call readcd -help to get alternate usage.
To prevent readcd from reading the run-out sectors, reduce the
number of sectors to copy by 2.

Recent readcd versions may be called: readcd dev=b,t,l f=outfile
To reduce the numbers of sectors to copy you may use the sectors= option.

If the master disk is made of several partitions (like a Solaris boot CD),
the best way to copy a CD is to use the program 'readcd'. It ignores
the partition info and does raw SCSI reads.

If you like to copy audio CD's in a way that preserves as much accuracy as
possible, use:

cdda2wav -vall -D... -B
cdrecord -v dev=... -dao -useinfo *.wav

This will preserve pre-gap sizes, indices ...

Creating multi-session CD's Mini Howto FAQ

Multi-session filesystems are a trick that comes from the Kodak photo CD.
The OS mounts the last session that contains the sum of the current session
and all previous sessions.

To test (with Linux):

Create a iso-9660 filesystem image with mkisofs-1.10 or later.
mkisofs is included in the cdrecord release (including
SunOS/Solaris multi-session support)
Use the -R flag to add Rock Ridge extensions (this is important).

Assuming that the CD-R drive is connected to target 2 on the SCSI bus.

Write the first session with:

cdrecord -v speed=2 dev=2,0 -eject -multi isoimage.raw

Note that all Sony drives do no support XA2 disks in firmware - read README.sony
for more information.

This must be a iso9660 image with Rock Ridge extensions (see above)

Note the number of sectors written and check the disk, it should be mountable.

Next step is to check if cdrecord is able to retrieve the following data:

	1) The first block (sector) number in the first track of the last session
	   This must be '0' in our case.

	2) The next writable address in the unwritten session following the current.
	   This should be the number of sectors written in the first
	   run + ~ 11400 sectors for about 22MB lead out/in

	   For the first additional session this is 11250 sectors lead-out/lead-in
	   overhead + 150 sectors for the pre-gap of the first track after the
	   lead-in = 11400 sectors.

	   For all further session this is 6750 sectors lead-out/lead-in
	   overhead + 150 sectors for the pre-gap of the first track after the
	   lead-in = 6900 sectors.

To get this information type:

cdrecord -msinfo dev=2,0

The output should be two numbers separated by a comma.

	e.g.: 0,204562

The first number is (1), the second number is (2).

Create the image for the next session with mkisofs-1.12 or later.
It is included in the cdrecord distribution.

2nd session:
You should create a directory that contains a second directory with data in it
for this purpose.

	e.g.:
		first_dir/
			second_dir/
				file_1
				file_2
				...

call:

On Linux:
mkisofs -o isoimage_2.raw -R  -C xx,yy -M /dev/cdwriter_blk_dev  first_dir

On SunOS:
mkisofs -o isoimage_2.raw -R  -C xx,yy -M target,lun first_dir

Note that the name "first_dir" is not important.

If you still keep the old raw image of the first session and there is only
one previous session on the CD you may also call:

mkisofs -o isoimage_2.raw -R  -C xx,yy -M isoimage.raw first_dir


The argument of -C is the output of cdrecord -msinfo
-	On Linux, the argument of -M is a device that would allow you to mount
	the current CD in the CD-writer
-	On SunOS, target and lun refer to the SCSI target and lun of the
	CD-R device with the same notation as for cdrecord dev=xxx,yyy .


If you want to check, whether mkisofs make everything right, you should create
another image by using the following command line.

On Linux:
mkisofs -o isoimage_2.raw -R  -C xx,0 -M /dev/cdwriter_blk_dev  first_dir

On SunOS:
mkisofs -o isoimage_2.raw -R  -C xx,0 -M target,lun first_dir

Where xx is the first number of the pair returned by cdrecord -msinfo

You may check ***this** image by mounting it with my "fbk" on Solaris
or the loopback driver on Linux.

On Linux type:
	mount isoimage_2.raw -r -t iso9660 -o loop /mnt

On SunOS type:
	mount -r -F fbk -o type=hsfs /dev/fbk0:isoimage_3.raw /mnt

For Solaris 8 and later you may also use the Sun lofi driver (see README.sun-lofi)

If you list /mnt, you should see all directories that have been in the first
session and the directory "second_dir". If you try to read a file from the
first session, you will get an I/O error or bad data (depending on the
block address), don't worry about that. If you try to read a file from
the second session, you will see everything correctly.

To write the second session to CD, call:

cdrecord -v speed=2 dev=2,0 -eject -multi isoimage_2.raw

If you mount this CD, you should see the first session and the second directory
from 2nd session added to the root directory of the CD.


Additional check:

call:

cdrecord -msinfo dev=2,0

The first number should be the first writable address which was retrieved by the
first call to cdrecord -msinfo after creating the first session.
The second number should be the first number + number of sectors of the second session
+ ~ 11400 sectors.

Note: The first lead-out is 1:30 (6750 sectors) the lead-in is 1:00 (4500 sectors)
All following sessions need only 0:30 for lead-out (2250 sectors), the lead-in
is also 1:00. So in theory, the can be 44 sessions on s 74 minute disk if you
take into account that the minimum track size is 4 seconds.

The total amount of the overhead is 11250 + 150 sectors for the first additional
session and 6750 + 150 sectors for all subsequent sessions.
The 150 additional sectors are the pre-gap sectors for the first track after
the current session.

Some notes on multi-session CD's that contain only Joliet but no Rock Ridge:

Joliet is a really bad idea in general:

-	There is no way to find a relation between a ISO-9660 name and a Joliet
	name. If the file has a size, you may try to match the starting sector #
	but if the size in 0 it's impossible.


-	Joliet does not allow long filenames (it limits names to 64 chars).

-	Joliet does not allow all (usually used) characters in filenames.

	All code points between (00)(00) and (00)(1F), inclusive. (Control Characters)
		(00)(2A) '*'(Asterisk)
		(00)(2F) '/' (Forward Slash)
		(00)(3A) ':' (Colon)
		(00)(3B) ';' (Semicolon)
		(00)(3F) '?' (Question Mark)
		(00)(5C) '\' (Backslash)

	While '/' is not a real problem ;-) other characters may cause trouble.

All notes above prevent you from doing reliable multi-session if the CD does
only contain Joliet but des not contain Rock Ridge attributes.

In addition, please read README.joliet in the mkisofs directory.

This is the answer to a commonly asked question is why can't I continue a
multisession CD that has been started on a Microsoft system using mkisofs.


Note: It is not possible to create a multi-session HFS CD. If you create
a multi-session CD using any of the HFS options, then each new HFS
session will ignore HFS files from any previous sessions. A warning will
be printed if you attempt this. However, if you use the '-part' option to
mkisofs for each session you create, then each session will appear as
separate volumes when mounted on a Mac. In this case, it is worth using the
'-V' or '-hfs-volid' option to give each session a unique volume name,
otherwise each "volume" will appear on the Desktop with the same name.


Joerg Schilling

This file is intended to help with ATAPI <-> Parallel Port devices on Linux

Before you start, read

	http://www.torque.net/parport/paride.html

Make sure that your parallel port device is set up to EPP mode
from within the BIOS. In many cases it is best to set the PP delay to 0.

Here is a short explanation how to make the FreeCom Traveller work
in 4x speed on a notebook:

1.) Set BIOS for parallel port to 'EPP'.

2.) Load drivers in default mode:

   # modprobe paride
   # modprobe <driver for parallel port adaptor>
   # modprobe pg

in case of a FreeCom Traveller this is:

   # modprobe paride
   # modprobe friq
   # modprobe pg

3.) Check kernel log for paride messages:

   # dmesg
   ...
   paride: version 1.04 installed
   paride: friq registered as protocol 0
   ...
   parport0: PC-style at 0x378 [SPP,PS2,EPP]
   parport0: no IEEE-1284 device present.
   ...
   pg: pg version 1.02, major 97
   pg0: Sharing parport0 at 0x378
   pg0: friq 1.01, Freecom IQ ASIC-2 adapter at 0x378, mode 4 (EPP-32), delay 1
   pg0:  CD-R/RW RW8040A, master
   ...

4.) load module again but use different parameters:
	'drive0=IO-Port,Protocol,Unit,Mode,Master/Slave,Delay drive1=...'
	if you have only one drive at the parallel port
	'drive0=IO-Port,0,0,-1,-1,Delay' e.g. for Delay = 0:

   # modprobe -r pg
   # modprobe pg drive0=0x378,0,0,-1,-1,0

5.) Check for optimum delay using for maximum speed using cdrecord -dummy

6.) Use the file rc.pp and modify for your needs

7.) Your CD drive now appears as /dev/pcd?

Tips for MMC RAW mode writing.

	This allows to do disk at once recording on Philips drives that
	do not support SAO.

	You may write audio tracks in RAW mode. There are some new
	and most likely transient options:

	-raw16		Write 2352 Bytes sectors + P+Q Subchannel

	-raw96r		Write 2352 Bytes sectors + P+W Subchannel (R-W in raw mode)

	-raw96p		Write 2352 Bytes sectors + P+W Subchannel (R-W in packed mode)

	NOTE that the MMC standard does not allow -dummy in RAW mode.
	There may be drives which allow it but don't bother if it does not work.

	Indices are fully supported in RAW mode.

	MCN & ISRC are not yet supported in RAW mode, they are silently discarded.

	If you find other problems in RAW mode or if you find
	new bugs introduced in old write modes, please send a bug report.

	Cdrecord now checks the properties of the writer. If a specific write
	mode is not supported by the writer, cdrecord warns you and makes
	a suggestion for a similar alternate write mode.

	With the curent structure of cdrecord, it is not possible to silently
	e.g. change the write mode from -dao to -raw96r

	MMC compliant drives are automatically scanned for supported write modes.
	This should help to make cdrecord work without manual static configuration.
	My hope is still to have no need to know all drive properties in
	advance, so new drives will continue to work as long as they
	are standard compliant enough for cdrecord.

EXAMPLES:

	cdrecord dev=1,0 -v -raw96r *.wav

	will write a audio CD in raw mode using (computed) 2448 byte sectors
	with raw P-W subchannels. This works e.g. with Plextor drives.


	cdrecord dev=1,0 -v -raw16 *.wav

	will write a audio CD in raw mode using (computed) 2368 byte sectors
	with raw P+Q subchannels. This works e.g. with Philips drives.


	NOTE: The input sector size always is 2352 bytes for audio.

IMPORTANT:

	-	if the drive supports RAW/R96R among with other raw write modes,
		use -raw96r

	-	if the drive does _only_ supports RAW/R16, use -raw16

	-	... else if the drive supports RAW/R96P, use -raw96p

		The packed raw mode (RAW/R96P) is buggy in Plextor drives and
		the RAW/R16 mode is buggy in TEAC drives. Plextor creates
		unreadable disks and TEAC hangs the drive.

		For this reason, it is important to select the raw writing
		mode accoding to the notes above.

The Remote-SCSI protocol gives you SCSI-Anywhere features.

There are three possible ways to control access to the remote users:

	-	Let the remote scsi lib log in as a standard user.
		In this case rscsi will be called via sh -c /opt/schily/sbin/rscsi
		NOTE: In this case, rscsi must be installed suid root.
		--- This would need to allow any valid local user to access SCSI ----
		It could be a security problem.

	-	Log in as root and call rscsi via sh -c /opt/schily/sbin/rscsi
		NOTE that this will fore you to allow remote logins as root
		which is considered to be a security hole.

	-	Create one or more special user(s) that have /opt/schily/sbin/rscsi
		as login shell with their own home directory.
		You then may create special .rhosts files for each user.
		NOTE: In this case, rscsi must be installed suid root.
		**** This is the preferred method ****

		The FreeBSD port automatically installs the rscsi binary suid
		root and creates the user "rscsi".

To enable remote SCSI via the login shell method you should do the following:

	-	Make sure that there is an entry for rshd(8) in /etc/inetd.conf
		and inetd(8) is running.

	-	Edit /usr/local/rscsi/.rhosts to allow access to all users you
		like.

	-	Edit /usr/local/etc/rscsi and define access rights.
		Without this file, rscsi will not work at all.

		The template for this file is: /usr/local/etc/rscsi.sample

RSCSI Security:

-	When rscsi starts, it checks if /etc/default/rscsi exists.
	If not, it dies.

-	If rscsi is not called by a user listed in /etc/default/rscsi
	it dies.

-	To access a SCSI target there must be an entry that lists the user
	rcsi hast been started from, the hostname and the SCSI target.

	rscsi compares the hostname field in /etc/default/rscsi
	to the peername retrived from STDIN:

	- legal host name		IP connection
	- "ILLEGAL_SOCKET"		Not an IP socket
	- "NOT_IP"			Not a socket

RSCSI Security hints:

-	Do not generally allow other users to see your boot disk via RSCSI.
	All people who see this disk may edit your passwd file.

-	If you are in doubt, only export CD-ROM drives, scanners and similar
	devices that are not directly security sensitive.

If anybody sees a security hole in my security precautions, please send me a mail!

RSCSI usage:

-	To use remote SCSI devices you need to know how to access a specific remote
	SCSI target.

	-	dev=REMOTE:host: or dev=REMOTE:host
		will allow you to do SCSI bus scanning while you log in as yourself

	-	dev=REMOTE:user@host: or dev=REMOTE:user@host
		will allow you to do SCSI bus scanning while you log in as "user"

		If you use the setup described above, you should use:

			dev=REMOTE:rscsi@babbel:

		to do SCSI Bus scanning on host babbel

	-	To access a specific SCSI device, you must specify
		dev=REMOTE:host:<target spec> or dev=REMOTE:user@host:<target spec>
		<target spec> is the SCSI target specification as it is needed
		on the remote host

			dev=REMOTE:rscsi@babbel:1,3,0

		Will let you log in as rscsi on host babbel and open Target 3 lun 0
		on SCSI bus #1

	-	If you use cdrecord -vv ...., cdrecord will on startup print some
		information about the remote libscg version used for the connection.

-	To be able to use the remote SCSI client code from win32 you need to create
	a file /etc/passwd with a correct entry for the user you are on win32.
	Call 'id' to get the right user id.
	Note that remote SCSI has not yet been tested on Win32.

RSCSI speed:

-	On a Ultra-10 running Solaris 8, the command overhead time is 400 usec.
	You may achieve up to 9900 kB/s via a 100MB/s ethernet connection
	between two of such machines.

-	With 100 MB/s, 12x recording should be no problem.

-	With 10 MB/s, 4x recording is the maximum. Do tests before!

-	Logging into a remote machine and running cdrecord on the remote machine
	causes the buffer cache on that machine to be trashed. The main user
	is disturbed.

-	Doing cdrecording via Remote SCSI causes only the rscsi command with less
	than 200kB to be needed on the remote machine hosting the CD recorder.
	The main user on that machine is not disturbed.
	The buffer cache of the machine running cdrecord is trashed.

-	It is desirable to use a Burn-Proof recorder to make sure that network
	load will not cause buffer underruns.


-	USER= test and test for hostname are using a pattern matcher.

A tip from From: Juergen Keil <jk@tools.de>

Solaris 9 x86 will not allow DMA for ATAPI CD/DVD-ROM drives even if
the eeprom command shows:

	atapi-dma-enabled=1

Here is a patch to the file /platform/i86pc/kernel/drv/ata
that allows you to use DMA again. Note that you need to be extremely careful
when applying the patch because it may completely break your installation
if you don't do it right.

% adb /platform/i86pc/kernel/drv/ata
ata_init_drive_pcidma,10?ia
ata_init_drive_pcidma: pushl %ebp
ata_init_drive_pcidma+1: movl %esp,%ebp
ata_init_drive_pcidma+3: subl $4,%esp
ata_init_drive_pcidma+6: movl +8(%ebp),%eax
ata_init_drive_pcidma+9: cmpb $1,+0x1ad(%eax)
ata_init_drive_pcidma+0x10: jne +0x111 <ata_init_drive_pcidma+0x121>
ata_init_drive_pcidma+0x16: movl +0xc(%ebp),%eax
ata_init_drive_pcidma+0x19: movl +0x204(%eax),%eax
ata_init_drive_pcidma+0x1f: andl $1,%eax
ata_init_drive_pcidma+0x22: je +0x1a <ata_init_drive_pcidma+0x3c>
ata_init_drive_pcidma+0x24: movl +0xc(%ebp),%eax
ata_init_drive_pcidma+0x27: movzwl +4(%eax),%eax
ata_init_drive_pcidma+0x2b: sarl $8,%eax
ata_init_drive_pcidma+0x2e: andl $0x1f,%eax
ata_init_drive_pcidma+0x31: cmpl $5,%eax
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is the check for a type 5 ATAPI device
ata_init_drive_pcidma+0x34: jne +8 <ata_init_drive_pcidma+0x3c>
ata_init_drive_pcidma+0x36:

Here's a patch that replaces the "cmpl $5" with a "cmpl $55", so
that all ATAPI devices will perform DMA transfers:

# cd /platform/i86pc/kernel/drv
# cp ata ata-orig
# echo 'ata_init_drive_pcidma+0x31?W 7555f883' | adb -w ata

Note that the exact position of the instruction that needs to be patched
may vary depending on the version of Solaris you use. Be extremely careful
when applying the patch.

	IMPORTANT NOTE FOR AMD64 Systems

cd /platform/i86pc/kernel/drv/amd64
cp ata ata.orig
adb -w ata
ata_init_drive_pcidma,17?ia
0x50f0:         pushq  %rbp
0x50f1:         xorl   %edx,%edx
0x50f3:         movq   %rsp,%rbp
0x50f6:         subq   $0x20,%rsp
0x50fa:         movq   %rbx,-0x18(%rbp)
0x50fe:         movq   %r12,-0x10(%rbp)
0x5102:         movq   %rdi,%rbx
0x5105:         movq   %r13,-0x8(%rbp)
0x5109:         movq   $0x0,0x0(%rip)
0x5114:         movq   %rsi,%r12
0x5117:         cmpb   $0x1,0x321(%rdi)
0x511e:         je     +0x12    <0x5130>
0x5120:         movq   -0x18(%rbp),%rbx
0x5124:         movq   -0x10(%rbp),%r12
0x5128:         movl   %edx,%eax
0x512a:         movq   -0x8(%rbp),%r13
0x512e:         leave
0x512f:         ret
0x5130:         testb  $0x1,0x208(%rsi)
0x5137:         je     +0xe     <0x5145>
0x5139:         movzbl 0x9(%rsi),%eax
0x513d:         andl   $0x1f,%eax
0x5140:         cmpl   $0x5,%eax
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is the check for a type 5 ATAPI device

0x5140?W7455f883       					<<< This changes the code
0x5140:         0x7405f883      =       0x7455f883
?i
0x5140:         cmpl   $0x55,%eax

If you have a IBM IDE hard disk on Solaris x86 and did enable DMA for ata,
then your system may hang after a reboot due to a firmware bug in the IBM
drive. On Solaris 9 you may edit the config file /platform/i86pc/kernel/drv/ata.conf
see also man ata.

On earlier versions, you need to patch the ata driver (see below):

Juergen Keil <jk@tools.de>

Bruce posted a patch for this problem some time ago:

http://groups.google.com/groups?q=solaris+DMA+IBM+timeout&hl=en&lr=&safe=off&site=groups

http://groups.google.com/groups?hl=en&safe=off&th=28213cb0f9e4067b,8&seekm=wywvaq7dvy.fsf%40tools.de#p

/*--------------------------------------------------------------------------*/

> >> "Bruce Adler" <bruce.NxOxSxPxAxMx.adler@acm.org> writes:
> >> ...
> >> > Here's a patch that will change the Solaris 8 FCS ata driver's 0xCC
> >> > command into a 0x66:
> >> >
> >> > cd /platform/i86pc/kernel/drv
> >> > cp ata ata.SAVE
> >> > adb -w ata<<EOF
> >> >     ata_devo_reset+0x54?w 0xaa68  ;; was 0xcc68
> >> > EOF
> >>
> >> Small typo, that should be
> >>
> >>   ata_devo_reset+0x54?w 0x6668
> >>
> >> > This should change the "pushl 0xcc" into a "pushl 0xaa" just before
> >> > the call to ata_set_feature().
> >>
> >> Indeed, changing the "pushl 0xcc" into a "pushl 0x66" fixes the reboot
> >> problem!
/*--------------------------------------------------------------------------*/
ata_devo_reset,50?ai
ata_devo_reset:
ata_devo_reset: pushl   %ebp
ata_devo_reset+1:               movl    %esp,%ebp
ata_devo_reset+3:               subl    $4,%esp
ata_devo_reset+6:               pushl   %ebx
ata_devo_reset+7:               pushl   %esi
ata_devo_reset+8:               pushl   %edi
ata_devo_reset+9:               cmpl    $0,+0xc(%ebp)
ata_devo_reset+0xd:             je      +0xb            <ata_devo_reset+0x18>
ata_devo_reset+0xf:             xorl    %eax,%eax
ata_devo_reset+0x11:            popl    %edi
ata_devo_reset+0x12:            popl    %esi
ata_devo_reset+0x13:            popl    %ebx
ata_devo_reset+0x14:            movl    %ebp,%esp
ata_devo_reset+0x16:            popl    %ebp
ata_devo_reset+0x17:            ret
ata_devo_reset+0x18:            pushl   +8(%ebp)
ata_devo_reset+0x1b:            call    +1              <ata_devo_reset+0x1c>
ata_devo_reset+0x20:            addl    $4,%esp
ata_devo_reset+0x23:            pushl   %eax
ata_devo_reset+0x24:            pushl   0
ata_devo_reset+0x2a:            call    +1              <ata_devo_reset+0x2b>
ata_devo_reset+0x2f:            addl    $8,%esp
ata_devo_reset+0x32:            movl    %eax,%edi
ata_devo_reset+0x34:            testl   %edi,%edi
ata_devo_reset+0x36:            je      +0x8d           <ata_devo_reset+0xc3>
ata_devo_reset+0x3c:            movl    $1,-4(%ebp)
ata_devo_reset+0x43:            xorl    %esi,%esi
ata_devo_reset+0x45:            nop
ata_devo_reset+0x46:            nop
ata_devo_reset+0x47:            nop
ata_devo_reset+0x48:            movl    %esi,%eax
ata_devo_reset+0x4a:            shll    $6,%eax
ata_devo_reset+0x4d:            movl    +0xc(%edi,%eax),%ebx
ata_devo_reset+0x51:            testl   %ebx,%ebx
ata_devo_reset+0x53:            je      +0x4d           <ata_devo_reset+0xa0>
ata_devo_reset+0x55:            movl    +0x204(%ebx),%eax
ata_devo_reset+0x5b:            andl    $2,%eax
ata_devo_reset+0x5e:            je      +0x13           <ata_devo_reset+0x71>
ata_devo_reset+0x60:            pushl   $0
ata_devo_reset+0x62:            pushl   $0x66		<<<======== War vorher pushl $0xcc
ata_devo_reset+0x67:            pushl   %ebx
ata_devo_reset+0x68:            pushl   %edi
ata_devo_reset+0x69:            call    +0x1846         <ata_set_feature>
ata_devo_reset+0x6e:            addl    $0x10,%esp
ata_devo_reset+0x71:            movl    +0x204(%ebx),%eax
ata_devo_reset+0x77:            andl    $1,%eax
ata_devo_reset+0x7a:            je      +0x11           <ata_devo_reset+0x8b>


Note that the exact position of the instruction that needs to be patched
may vary depending on the version of Solaris you use. Be extremely careful
when applying the patch.

The Sony CDU-924 was the first drive that has no hardware support
for CDROM XA2 mode 1. If you want to create a multi session disk,
you need to switch back to -data (plain CD-ROM)

If you have a Sony drive that gives you problems with multi session disks,
please always check the following:

	For some Sony drives you may need to call cdrecord -multi -data
	if you like to create multi-session CD's.

	Some Sony drives do not allow to write XA2 tracks with
	hardware support of the drive.

There is currently a bug in the Sony code (for _old_ non MMC drives)
of cdrecord that does not allow you to have different track types
in one session.

All Sony drives that have CDUxxx type names are _old_ non MMC drives.
	Here I expect that no XA support is in the firmware.

All Sony drives that have CRXxxx type names are MMC compliant.
	These drives should support XA-mode2-form1 as it is mandatory with MMC.

NOTE: many HP CD-writers are nased on Sony OEM drives.


NOTE: As for 18.5.2001, a fix was introduced that prevented cdrecord
	to do multi session with new MMC compliant Sony drives.

Starting with Solaris 8 (2000), Sun introduced a lofi driver which is
very similar to my fbk driver from 1988.

The lofiadm command seems to implement the basic idea of my fbkset program.

# lofiadm -a /var/tmp/image.iso
/dev/lofi/1
# mount -F hsfs -o ro /dev/lofi/1 /mnt
# ls /mnt
etc.

To remove this, you need to:
# umount /mnt
# lofiadm -d /dev/lofi/1

The /dev/lofi/.. string may change depending on how many other loopback
devices you have configured.

It is explained quite clearly in the man page, but you may wish to update
the README and cdrecord man page to reflect the new way of doing this.

Mini-Howto for verifying a selfmade CD

1) verifying the data layer

	To verify if all data on the disk can be read,
	use SCSI verify. This can be done with the
	sformat utility.

	use: sformat -verify [target] [lun] [scsibus]

	If the CD-R device is connected to target 2 on SCSI bus 0
	sformat -verify 2  0

	sformat can be found on

	https://sourceforge.net/projects/schilytools/files/sformat/
	or
	https://sourceforge.net/projects/schilytools/files/schily-*

	NOTE: Not all CD-ROm drives support verifying
	NOTE: All TAO tracks end in 2 unreadable run-out sectors

2) verifying the filesystem layer

	A quick check is to mount the CD and to use star to read
	all files on the filesystem.

	mount -r /dev/cdrom /cdrom      (modify for your OS)
	cd /cdrom
	star -cPM . >/dev/null

	If no errors can be found, all files are readable.

	star can be found on

	http://sourceforge.net/projects/s-tar/files/


	You also may want to compare the filesystem on the CD
	with the original data. This can be done with star too.


	(cd /master_for_cd; star -cPM .)|(cd /cdrom; star -diff -v)

2a) verifying the iso image before creating the CD

	You may check the filesystem image by mounting it with my
	"fbk" on Solaris or the loopback driver on Linux.

	On Linux type:
		mount isoimage.raw -r -t iso9660 -o loop /mnt

	On SunOS type:
		mount -r -F fbk -o type=hsfs /dev/fbk0:isoimage.raw /mnt

For Solaris 8 and later you may also use the Sun lofi driver (see README.sun-lofi)

	The check the filesystem with:

		(cd /master_for_cd; star -cPM .)|(cd /mnt; star -diff -v)


When doing this you have to know about the bugs in Linux/Solaris

Mkisofs before 1.10 and Linux have a bug with timezones.
If you are using mkisofs-1.10 and newer on Linux, you need to disable
comparing times:

(cd /master_for_cd; star -cPM .)|(cd /cdrom; star -diff -v diffopts=!times)

The same is needed if you are using mkisofs pre-1.10 on Solaris

Solaris has a bug with hardlinks. It generates different inode numbers
for the hardlinks to a file. This makes it impossible for star to
check hard links. Use

(cd /master_for_cd; star -cPM .)|(cd /cdrom; star -diff -v diffopts=!hardlink)

in this case.

NOTE: Some operating systems have a read ahead bug that causes I/O errors for
the last file(s) on a CD. This seems at least to be true for all Linux versions
and for Solaris 7 FCS. For Solaris 7 there is a patch (107465-02) that you should
install. This I/O error problem does not occur with DAO disks and with TAO disks
that have been written with cdrecord -pad.

Joerg Schilling

If you are on NeXT-Step/Apple Rhapsody,
you must disable volume management before creating a CD.
On older Solaris versions, you may also need to disable the volume management.

This is needed because newer drives identify themselves correctly
as CD-ROM drives. Unfortunately, the volume management daemon from
Sun/Apple does not grok, that there may be a recordable medium in the drive.

You do this on Solaris permanently by editing /etc/vold.conf
NeXT-Step/Apple Rhapsody will only work correctly if you reboot while
the CD-R drive is powered off.

On Solaris you need to stop the volume management if you like to use the USCSI
fallback SCSI transport code. Even things like cdrecord -scanbus
will not work if the volume management is running.

If the Solaris version you are running is recent enough, libscg will try to
interace with the volume management. However, Solaris does not allow you to
access a drive that is maintained by the volume management but does not
include a medium. Cdrecord will mark this fact by printing a '?' during
a -scanbus run.

Cdrecord-ProDVD-Clone 2.01a23 (i386-pc-solaris2.9) Copyright (C) 1995-2003 J�rg Schilling
scsidev: 'USCSI:'
devname: 'USCSI'
scsibus: -1 target: -1 lun: -1
Warning: Using USCSI interface.
Warning: Volume management is running, medialess managed drives are invisible.
Using libscg version 'schily-0.7'.
scsibus1:
        1,0,0   100) ?
        1,1,0   101) 'HP      ' 'DVD Writer 200j ' '1.36' Removable CD-ROM
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *

If you insert a medium and close the tray, the medium becomes visible again.
Note that for this reason, it is impossible to use cdrecord with automated
scripts if the volume manager is configured to include a CD/DVD writer
as it is impossible to close the door of the drive.

#ident @(#)readme.mk	1.1 07/06/13
###########################################################################
# Sample makefile for installing non-localized auxiliary files
###########################################################################
SRCROOT=	..
RULESDIR=	RULES
include		$(SRCROOT)/$(RULESDIR)/rules.top
###########################################################################

INSDIR=		share/doc/cdrecord
TARGET=		README
#XMK_FILE=	Makefile.man

###########################################################################
include		$(SRCROOT)/$(RULESDIR)/rules.aux
###########################################################################