It seems that some include files that are needed to compile
e.g. the SCSI transport stuff are only present if you install
the kernel building stuff.

If you have problems to compile because some include files are
missing, look into /sys and verify if all files are present or
(if they are symlinks) point to present files.

There is no working mapping between the SCSI bus,target,lun
notation and device node names. To use a SCSI device, you need
to specify dev=devname:@,lun e.g. dev=/dev/rsr0a:@,0

Important notice for ATAPI support on FreeBSD:

A long time it was not possible to decently write CD's using ATAPI drives
on FreeBSD because ATAPI was not supported in an orthogonal way on FreeBSD.

These days (in the mid of november 2001) first ATAPI support for FreeBSD is
available as patch. Please read:

http://www.freebsd.org/cgi/getmsg.cgi?fetch=136602+0+/usr/local/www/db/text/2001/freebsd-current/20011111.freebsd-current

and get the FreeBSD kernel patch from:

http://www.cuivre.fr.eu.org/~thomas/atapicam/

Thanks to Thomas Quinot <thomas@cuivre.fr.eu.org> for the patch.

We tested the patch with a collegue today (23.11.2001), here is the result:

-	From our tests, it compiles with FreeBSD 4.x and FreeBSD current (5.0)
	but does not boot with FreeBSD current so we used 4.x for our tests
	I hope that Thomas Quinot <thomas@cuivre.fr.eu.org> and
	Kenneth D. Merry <ken@kdm.org> will help to make it work with
	FreeBSD current soon.

-	The Author of the patch, Thomas Quinot <thomas@cuivre.fr.eu.org>, observed
	that it runs on *some* -CURRENT machines and hangs on *some* -STABLE
	machines so you may want to test what works best for you.

-	It does not run the SCSI commands in silent mode so the ATAPI low level
	code prints unwanted kernel messages when you start cdrecord.

-	cdrecord runs without problems so far it has been tested!

You need to apply the patch, change your kernel configuration to include

options                ATAPICAM

and then recompile install and boot the new kernel.
Make enough /dev/pass* devices and start testing.....

/*--------------------------------------------------------------------------*/
From shamrock@cypherpunks.to Mon May  3 07:35:50 1999
Received: from pakastelohi.cypherpunks.to (pakastelohi.cypherpunks.to [212.26.192.194])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id HAA18680
	for <schilling@fokus.gmd.de>; Mon, 3 May 1999 07:35:48 +0200 (MET DST)
Received: from localhost (shamrock@localhost)
	by pakastelohi.cypherpunks.to (8.9.1a/8.9.1) with SMTP id HAA26150
	for <schilling@fokus.gmd.de>; Mon, 3 May 1999 07:35:44 +0200 (CEST)
Date: Mon, 3 May 1999 07:35:44 +0200 (CEST)
From: Lucky Green <shamrock@cypherpunks.to>
To: schilling@fokus.gmd.de
Subject: Re: Cdrecord "RR-scheduler not available" (fwd)
Message-ID: <Pine.BSF.3.96.990503073330.26028A-100000@pakastelohi.cypherpunks.to>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: R
Content-Length: 1423

Schily,
Please add the following info to your readme for FreeBSD. Enabling POSIX
scheduling as described below does in fact make the error message go away.

Thanks,
-- Lucky Green <shamrock@cypherpunks.to> PGP v5 encrypted email preferred.

---------- Forwarded message ----------
Date: Sun, 2 May 1999 14:46:57 +0200 (SAT)
From: Khetan Gajjar <khetan@link.freebsd.os.org.za>
Reply-To: Khetan Gajjar <khetan@os.org.za>
To: Lucky Green <shamrock@adsl.cypherpunks.to>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Cdrecord "RR-scheduler not available"

On Sat, 1 May 1999, Lucky Green wrote:

>Having spent a week on trying to get an ATAPI CD burner working, I saw the
>light and purchased a SCSI-based burner. It burns, but I am getting an
>error about the RR-scheduler not being available. What is an RR-scheduler
>and how do I make it available? (If I even need it....)

Enable the Posix scheduling stuff in your kernel; you'll produce
more reliable burns at higher speeds if your machine is busy
(well, that's been my experience)

options         "P1003_1B"
options         "_KPOSIX_PRIORITY_SCHEDULING"
options         "_KPOSIX_VERSION=199309L"
---
Khetan Gajjar       (!kg1779) * khetan@iafrica.com ; khetan@os.org.za
http://www.os.org.za/~khetan  * Talk/Finger khetan@chain.freebsd.os.org.za
FreeBSD enthusiast            * http://www2.za.freebsd.org/
Security-wise, NT is a OS with a "kick me" sign taped to it

NOTE: you should also read README.xxxBSD

Cdrecord now supports ATAPI drives on NetBSD

The sparc hostadapter driver software in NetBSD has a bug:

An internal copy of the SCSI status byte will never be updated.
However, this internal copy is always returned so the
SCSI library always believes that an error occurred.

As this implementation bug makes it impossible to sense
other error/exception conditions the driver needs to be fixed.

As a workaround you can activate a hack in the file scsi-bsd.c
by using

./Gmake COPTX=-DBSD_SCSI_SENSE_BUG

to compile cdrecord

J�rg

On OpenBSD releases between December 11th and December 30th 2002
there is a bug in /usr/include/ctype.h, it #defines EOF ignoring
POSIX rules. As the schily make environment relies on EOF as an
indicator to check whether stdio.h has been included, there may
be problems to compile things. If you find compile problems,
you may try to include

#undef EOF

directly after #include <ctype.h>

Cdrecord has been tested and known to work on OpenBSD, however,
the current OpenBSD port will not be able to scan the SCSI bus
for a CD-Recorder as it does on other operating systems.

In other words, 'cdrecord -scanbus' most likely will not work.

Both regular SCSI and ATAPI devices are supported. For ATAPI support
you need OpenBSD-2.6 or newer.

Libscg sends Generic scsi commands that are only supported for the
"whole disk" partition.  For example, 'cdrecord dev=/dev/rcd0c -checkdrive'.
See the cd(4), atapiscsi(4), and cdrecord(1) manpages for more details.

There are at least two ways to figure out what SCSI CD devices are
on the machine:

  From /var/run/dmesg.boot:
  $ egrep "^cd.+ at scsibus" /var/run/dmesg.boot
  cd0 at scsibus0 targ 0 lun 0: <SONY, CD-RW CRX175E2, S002> SCSI0 5/cdrom removable
  cd1 at scsibus1 targ 0 lun 0: <ATAPI, CD-ROM MARY500, 1.21> SCSI0 5/cdrom removable

  From sysctl:
  $ sysctl hw.disknames
  hw.disknames = wd0,cd0,cd1,fd0

In these examples, 'cd0' and 'cd1' are the SCSI CD devices on the
system, and they should be accessed by '/dev/rcd0c' and '/dev/rcd1c',
respectively.

In December 2002 there have been reports that the atapiscsi(4) driver has
some bugs that may cause cdrecord to hang for a while.  While this is
annoying, it is harmless. The command will eventually timeout (the default
timeout is 40 seconds, but can be changed with timeout=%d).  Trying to kill
the "hung" process may leave the device unusable until the system is rebooted
(which would be another bug of the atapiscsi(4) driver as killing a process
should do all necessary housekeeping for the dead process), so just be patient.

To compile on QNX you will need smake-1.2a3 or later.
It looks like GNUmake has a bug that prevents a compilation
using GNUmake.

You need to use GNUmake or my smake to compile on AIX

Read the file README.compile before compiling.

NOTE:	AIX seems to have a kernel bug in the mmap() part
	that may cause kernel panics.

If you observe this kernel panic, try to add a line:

COPTS += -DUSE_USGSHM

to the file cdrecord/Makefile

or compile the package using:

make COPTX=-DUSE_USGSHM

It seems that SVrx style shared memory does not have this kernel bug
In newer AIX releases, the mmap() kernel problem seems to be fixed.

If you like to create bootable CD's for AIX on the CHRP architecture:

	The /usr/sbin/mkcd command starting shipping with
	AIX 4.3.3 back in Oct 99'. It's installed by default with the system.
	There's more info about it in /usr/lpp/bos.sysmgt/mkcd.README.html.


NOTE:	there is currently no real SCSI generic support for AIX, so
	cdrecord -scanbus will not work.

	/dev/rcd0 is mapped to dev=0,0,0
	/dev/rcd1 is mapped to dev=0,1,0

For CD-Recording please read the README.volmgt too.

Gmake compliance is included for convenience because it may
be found on many systems and most make programs are worse
than gmake.

	***** If you are on a platform that is not yet known by the	 *****
	***** Schily makefilesystem you cannot use GNU make.		 *****
	***** In this case, the automake features of smake are required. *****

The major problem with gmake is that it does not handle the
include directive correctly. The general rule for a make program is
to first try to "make" any object it should look on. Gmake
does not try to "make" any makefile it should include. One result
is many warnings about non-existent files (which you could ignore).
The other problem with gmake and include files is hat gmake
includes the files in the opposite order than expected. The result is
that dependencies may not handled correctly.

If you have problems with the make file system and gmake,
you are out of luck. Gmake has a debug option, but it gives
tons of debug messages. Less than 1% of these debug messages are
useful. Important things are missing in these debug messages.

Gmake has bug with the VPATH= option. Some of the macros are
not expanded correctly. I had to remove all occurrences of
$@ $* and $^ on some places for this reason.

On some platforms (e.g. OSF1), gmake is not able to correctly recognize
the default target. If gmake complains about this, call ./Gmake all

To use GNU make create a file called 'Gmake' in you search path
that contains:

#!/bin/sh
MAKEPROG=gmake
export MAKEPROG
exec gmake "$@"

and call 'Gmake' instead of gmake. On Linux and on Cygwin there is
no gmake, 'make' on Linux and on Cygwin is really a gmake.

'Gmake' and 'Gmake.linux' are part of this distribution.

Note that makefile versions past 98/10/13 are trying to recognize
gmake by assuming that $(MAKE_COMMAND) is only present if you
are running gmake. So it may be worth to try to just call 'gmake'
or even 'make' if your system uses gmake as the default make program.

		I M P O R T A N T

On HP-UX-11.x the maximal data size (allocated data) of a 32 bit program is
64 MB.

One solution is to build a 64 bit binary, for those the default process memory
limit is 1 GB.

64bit binaries can be created with

	cc +DA2.0w
	cc +DD64

if you have the HP C-ANSI-C compiler.

To compile in 64 bit mode, first call ./.clean then call

	make COPTX=+DD64 LDOPTX=+DD64
	make COPTX=+DD64 LDOPTX=+DD64  install


If you have an older GNU gcc, you need a 64bit compiled gcc. Older GNU gcc versions
are not capable of switching, so you need a separate compiler installation for either:

l1:/u/usr/merijn 102 > file /usr/local/pa*/bin/gcc
/usr/local/pa20_32/bin/gcc:     PA-RISC2.0 shared executable dynamically linked -not stripped
/usr/local/pa20_64/bin/gcc:     ELF-64 executable object file - PA-RISC 2.0 (LP64)
l1:/u/usr/merijn 103 >

With a newer GCC, you may call ./.clean then call:

	make COPTX=-mlp64 LDOPTX=-mlp64
	make COPTX=-mlp64 LDOPTX=-mlp64  install


The other way is to alter some kernel parameters which require a reboot.
The default kernel parameter seem to look like:

Kernel param.               Value
maxdsiz                  67108864
maxdsiz_64bit          1073741824
maxfiles                      200
maxfiles_lim                 2048
maxssiz                   8388608
maxssiz_64bit             8388608
maxswapchunks                3250
maxtsiz                  67108864
maxtsiz_64bit          1073741824

The important one is maxdsiz, 64 MB is the default and it is rather low.
There is some information page at http://www.uwsg.iu.edu/hp/hpux-tune.html#maxdsiz
and they recommend to increase it to 1.9 GB. Sounds extreme.

At http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x08afe7613948d5118fef0090279cd0f9,00.html
they recommend 500 MB.

maxssiz shouldn't be a problem either since it has to do with swap and such as
storing arrays and recursion etc.

If you like to know how to create 64 bit binaries on Solaris, please
read README.compile. I hope this helps. If you found the right way for HP-UX,
please send me a mail.



The Schily makefile system usually should be able to find the best C-compiler
on HP-UX automatically. If it does not work, here is a way force to use a different
compiler.


You may compile with the HP ANSI C-Compiler using:

	make CCOM=cc

To compile with the free K&R C-compiler call:

	gmake CCOM=cc 'COPTS= '
or
	smake CCOM=cc 'COPTS= '
/*--------------------------------------------------------------------------*/

HP-UX SCSI hints:

Note that there are no device nodes for userland SCSI on HP-UX,
you have to call the included shell script MKNOD.hpux first.

If you own a HP-9000-800 series machine, you need to install
the file MKNOD.hpux-800 in the /etc init shell script directory
in order to call it after each boot.

This script will create the files in /dev/scsi/... and /dev/rscsi/...
The permissions will be set to read/write for root only.


HP does not handle CD-ROMs as well as it should. On the HP have a look at
the man pages for
    pfs
    pfsd
    pfs_mount
and anymore that they refer too.

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

From:
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)

As of Jun 2002, there are some patches available to HP-UX 11.00 and 11i that
prevent the need for pfs, and these are highly recommended, since Rock-Ridge
extensions are now supported from the kernel level.

For 11.00:

a5:/ 103 # swlist | grep -i rock
  PHCO_26449   1.0  Add Rock Ridge extension to mount_cdfs(1M)
  PHKL_26448   1.0  Y2k; Rock Ridge extension for ISO-9660
  PHKL_26450   1.0  Rock Ridge extension for ISO-9660
a5:/ 104 #

PHKL_26448 is not recommended, but I never had any trouble with it. I still
have to install PHKL_28060 over PHKL_26448

  PHKL_28060   1.0  Y2k; Rock Ridge extension for ISO-9660

For 11i:

  PHKL_28025   1.0  Rock Ridge extension for ISO-9660
  PHKL_26269   1.0  Rock Ridge extension for ISO-9660
  PHCO_25841   1.0  Add Rock Ridge extension to mount_cdfs(1M)

I don't have 11i (yet), so I got this from HP-UX' patch database.

The problem is that they did /not/ enable RR by default, but made it a mount
option. D'uh! But you can add it in /etc/fstab, and never worry again :)

a5:/ 104 # grep cd /etc/fstab
/dev/cd0        /cdrom          cdfs    ro,rr,noauto    0 0
a5:/ 105 #

# @(#)README.install	1.7 20/09/04 Copyright 1997-2020 J. Schilling

To install makefiles, just take the tar archive makefiles.tar
and untar it on the source root of your new project.

The tar file contains:

-	the RULES directory with the main make rules
-	two different DEFAULT directories with predefined project settings
-	a directory containing templates for all purpose
-	a skeleton directory structure for the new project
-	some README files that will be useful for developers and users

If you want to see a better example, please have a look at the "star"
source. It may be found on:

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


Have a look at the manual page, it is included in the distribution.
Install the manual page with

make install first and include /opt/schily/share/man in your MANPATH

Author:

Joerg Schilling
D-13353 Berlin
Germany

Email: 	joerg@schily.net

Please mail bugs and suggestions to me.

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

Linux is the most self incompatible OS I know. If you have any problem,
first carefully read this file.

Linux includes the gnu make program by default but it is called 'make' on linux.
You will definitely need the shell script Gmake.linux to use gmake
on a linux system.

Install it as /usr/bin/Gmake with:

cp Gmake.linux /usr/bin/Gmake

Then compile the system by calling:

/usr/bin/Gmake
or ./Gmake.linux

NOTE for all Linux 2.5.x versions and all Linux versions before 2.6.8:

	Linux did ship with defective kernel include files starting
	with 2.5.x. These defective kernel include files did prevent
	compilation. If you have problems compiling software and see
	error messages related to include/scsi/scsi.h & include/scsi/sg.h
	either upgrade to Linux-2.6.8 or newer or remove /usr/src/linux

NOTE for all Linux versions using libc.so.6:

	Libc.so.6 is definitely a big problem in binary compatibility.
	First you should note that Linux is not a OS but only a kernel.

	Creating a OS from kernel, libraries and applications is done
	by various companies that create "Linux distributions". It seems
	that these companies (e.g. SuSE and Red Hat) are fighting wars
	against each other.

	There is no guarantee that a binary that has been compiled
	on one Linux distribution will run correctly on a different
	release of the same vendor or on a distribution from a different
	vendor. You cannot copy binaries between different Linux
	versions, always compile the sources by yourself.

	We should consider that the name libc.so.6 is burned out for
	these incompatibility reasons. But stop: Don't be too fast.
	The dynamic linker on Linux does not work correctly. It has
	been derived from the SunOS 4.x linker (which worked correctly)
	but  the Linux version does not even warn if it could not
	find a library with the right major version number. Until
	this is fixed it makes no sense to switch to libc.so.7

	See below for more information.


NOTES for S.u.S.E distributions: If the "make" run aborts with strange messages,
then you need to unset an environment variable called PROMPT_COMMAND
It contains illegal values for a make file system.

		I M P O R T A N T

	please carefully read all notes:

Newer Linux kernels (from 2.3.51) moved SVSv shared memory into a filesystem.
If you get messages with error code EINVAL related to shared memory, you
most likely installed a newer kernel on an old system that does not mount
the new shared memory filesystem.
For information on this filesystem please read README.linux-shm

If you have any problems to access a device on the SCSI bus, check your
/dev/sg devices first. Your system should either only have /dev/sga...
or /dev/sg0... The newer Linux kernel use /dev/sg0... so the actual
SCSI transport code checks for /dev/sg0... first. Many Linux installations
have too few /dev/sg* device nodes. This is because of the funny device
mapping. It may be possible that one SCSI device eats up 8 /dev/sg* entries.
I recommend to have at least 20 /dev/sg* device nodes.

In any case: first read the man page for hints how to specify the device.
If nothing helps, first run e.g. cdrecord -scanbus. If this does not find
your device, the problem is in your kernel or system installation.
If scanning the bus finds the device, you are using the wrong device name.
If nothing help try to call e.g. strace cdrecord

Linux ATAPI hints:

Read README.ATAPI to learn how to use ATAPI drives with the SCSI transport
library.

Linux SCSI hints:

If you want to use the user SCSI library on a target that is connected
to a SCSI hostadapter which is not the first, you need to apply a patch
to your Linux kernel code. This patch is located in the file

Linux.scsi-patch

Please chdir to /usr/src, call
patch  < Linux.scsi-patch
and re-compile and re-install your kernel.

Linux kernels past 2.0.30 will probably already have this patch included.

I recommend to use Linux 2.0.35 or later or Linux 2.1.115 or later.
These versions of Linux will include ATAPI support in a way needed by cdrecord.
Linux 2.1.115 or newer will in addition support the Parallel Port / ATAPI
adapters found in some CD-R or CD-RW drives.

IMPORTANT:

-	Linux driver design oddities ******************************************
	Although cdrecord supports to use dev=/dev/sgc, it is not recommended
	and it is unsupported.

	The /dev/sg* device mapping in Linux is not stable! Using dev=/dev/sgc
	in a shell script may fail after a reboot because the device you want
	to talk to has moved to /dev/sgd. For the proper and OS independent
	dev=<bus>,<tgt>,<lun> syntax read the man page of cdrecord.

-	Linux Kernel bug ******************************************************
	In some architectures (at least on sparc / alpha / ppc) kernels prior
	to 2.0.32 are not usable because the call to mlockall() kills cdrecord.

-	You configured you kernel the wrong way *******************************
	If you get a message like:

		cdrecord: Function not implemented. shmget failed

	You need to look for three possible reasons:

	-	You are using a Linux Kernel 2.3.51 or newer.
		Read README.linux-shm

	-	You removed SVSv IPC from your kernel. You need to enable it again.
		Run a Linux kernel config and recompile with SYSv IPC.

	-	The allowed amount of shared memory in the kernel is
		not sufficient. See next main point for a solution:

-	Linux kernel oddities *************************************************
	You may need to edit /usr/src/linux/include/asm*/shmparam.h to allow at least
	4 MB of shared memory for your architecture by modifying SHMMAX
	and re-compile/re-install Linux !
	(note that Linux for Intel by default allows 16 MB)

	Do this by e.g. changing the #define for SHMMAX to:

	#define SHMMAX 0x1000000                /* max shared seg size (bytes) */

	This will allow 16 MB for shared memory.

-	Linux kernel memory management ****************************************
	If you get the message: "Cannot allocate memory. Cannot send SCSI cmd via ioctl"
	Your kernel/include files are inconsistent.

		This seems to be the case with most actual Linux kernels!!!!!!

	Make sure, that the include file /usr/src/linux/include/scsi/sg.h
	reflects the actual kernel. Usually, the files /usr/include/scsi/sg.h
	and /usr/src/linux/include/scsi/sg.h should be identical.

	**** Never change the content of /usr/src/linux/include/scsi/sg.h without
	properly recompiling the kernel. Cdrecord depends on the fact that
	the value of the define SG_BIG_BUFF uses the same value as the actual
	kernel. Use cdrecord -scanbus -debug to get the value of SG_BIG_BUFF
	with cdrecord has been compiled. An output of:

		scsi_getbuf: 32768 bytes

	indicates that cdrecord has been compiled with 32k SG_BIG_BUF

	The Linux 'sg' driver is the worst driver design, I've ever seen.

-	Linux Binary incompatibility *****************************************
	If any of the options that take a equal sign ('=') in the middle does
	not work correctly (e.g. dev= or if=) you are using a binary that
	does not work correctly on your current OS distribution.

	If dev=0,0,0 does not work but -dev=0,0,0 works you found this
	incompatibility. This problem is caused by an incompatibility
	in ctype.h and it seems that there are other compatibility problems
	e.g. with reading /etc/default/cdrecord.

	You cannot copy binaries between different Linux versions,
	always compile the sources by yourself.

	If a hint from a user is correct then even a RPM binary built for
	RH-6.2 did not work on RH-6.2 because of these binary incompatibilities.


Joerg

System V IPC
CONFIG_SYSVIPC
  Inter Process Communication is a suite of library functions and
  system calls which let processes (running programs) synchronize and
  exchange information. It is generally considered to be a good thing,
  and some programs won't run unless you say Y here. In particular, if
  you want to run the DOS emulator dosemu under Linux (read the
  DOSEMU-HOWTO, available from
  http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
  here.

  You can find documentation about IPC with "info ipc" and also in
  section 6.4 of the Linux Programmer's Guide, available from
  http://www.linuxdoc.org/docs.html#guide .

  Shared memory is now implemented using a new (minimal) virtual file
  system, which you need to mount before programs can use shared memory.
  To do this automatically at system startup just add the following line
  to your /etc/fstab:

  none  /var/shm        shm     defaults        0 0

  Saying Y here enlarges your kernel by about 18 KB. Just say Y.

February 25, 2002

MacOS 10.1 driver now in the tree in libscg/scsi-mac-iokit.c.

It supports:
	* Firewire, USB, and ATAPI MMC-3 compliant burners
	* SCSI parallel bus attached burners (requires MacOS X.1.3)

It does not support:
	* Older non MMC-3 burners
	* CD-ROM drives/DVD-ROM drives (i.e. non-burners)

Note that this is a limitation of MacOS X and not of the driver.
See the end of the document if you're curious why.

If you just want to burn ISO images, you may want to consider using Apple's
hdiutil program, but it is not clear how standard compliant this method is.

Building
--------

Note if you installed MacOS X on a HFS+ volume, make install will fail if
there is a file called INSTALL in the directory tree because this Filesystem
is not POSIX compliant. POSIX requires to honor character case but HFS+
ignores the character case. If you like to use "make install" rename
INSTALL to something else. (e.g. INSTALL.txt)


Device Naming
-------------

You need to pass a device name on the command line to the cdrecord utility

CD burners: (probably) IOCompactDiscServices
DVD burners: (probably) IODVDServices

# ./cdrecord dev=IOCompactDiscServices -toc

or if you have multiple drives, you can append a number to differentiate

# ./cdrecord dev=IOCompactDiscServices/2 -toc

That should talk to the second CD-R on the system (NOT TESTED).

Sharing nicely with the Finder
------------------------------

The MacOS 10.1 Finder will offer to burn any blank media you put into
the burner.  However, you don't want to use the Finder, you want to
use cdrecord! So, how do you get around this problem?

When you insert the media, the Finder asks "Do you want to prepare this
disc?". Click on the "Ignore" button.

The Finder will then say "No volumes found. Click Continue to continue
without ejecting".  Click on the "Continue" button.


Common Errors
-------------

No matching device ... found:
Make sure you typed the device names correctly. See above. Use ioreg
-l to find if there is an IOCompactDiscServices or IODVDServices in
the device tree.

Unable to get exclusive access:
Another programs (usually the Finder) has exclusive access to the drive.
See "Sharing Nicely with the Finder"

Unable to get plugin interface:
The SCSI Architecture Family of drivers (supports Firewire, ATAPI, and
USB) has a special module that allows user code like libscg to send
SCSI commands to a device. This module is only attached, though, if
the kernel device driver thinks the device is sufficiently interesting
(e.g. the kernel thinks it's a burner).

You can see if the module is loaded by looking for
SCSITaskUserClientIniter in the output of ioreg -l.

Why doesn't it support my SCSI device?
--------------------------------------

Apple's kernel drivers enforces the rule that application cannot send
SCSI commands to devices for which they feel they have enough kernel
support. This includes hard disks and CD/DVD ROMs. They make an exception
for burners, though.

There are two possible work-arounds, neither of which has been
implemented.  One is to write a kernel driver that wraps the Apple
kernel drivers and exposes a raw SCSI interface, overriding the Apple
kernel drivers. The other is to write a SCSI device emulator at user
mode that translates SCSI commands into the appropriate interface
calls to IOKit.

Bugs
----
Send bugs to: csapuntz@stanford.edu

*********************************************************************************
*										*
*			WARNING							*
*										*
*	This is only valid for OLD MacOS X versions				*
*	This are versions _before_ MacOS X-10.1	(Darwin-1.4)			*
*										*
*										*
*********************************************************************************

If uname -a does print something like:

Darwin HOST 1.4 Darwin Kernel Version 1.4: Sun Sep  9 15:39:59 PDT 2001; root:xnu/xnu-201.obj~1/RELEASE_PPC  Power Macintosh powerpc

or a version > 1.4 then you should rather read  README.macosX

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

Unfortunately, Apple does not deliver a consistent Mac OS-X system
The longer they work on it, the more bugs they introduce...

In addition, there is no visible 'clean' road of development.
Release names (from 'uname') are confusing and don't help to find out what
release they refer to.

/*--------------------------------------------------------------------------*/
	The next hint is for Mac OS X versions up to January 2000 only:

The file <bsd/dev/scsireg.h> tries to include <kern/queue.h> which cannot
be found.

To be able to compile, I suggest to create a symlink:

System/Library/Frameworks/System.framework/Versions/B/Headers/kern -> kernserv

To do this, chdir to:

System/Library/Frameworks/System.framework/Versions/B/Headers/

and call

ln -s kernserv kern

as root.
/*--------------------------------------------------------------------------*/


/*--------------------------------------------------------------------------*/
	This hint is for Mac OS X version starting ~ April 2000:

Apple did remove the generic SCSI transport driver for unknown reasons!
Cdrtools compile, but as there is no SCSI transport, you may only write
CD's connected to other systems using the REMOTE SCSI protocol.
/*--------------------------------------------------------------------------*/

/*--------------------------------------------------------------------------*/
	This hint is for Mac OS X versions starting around March 2001:

If your compile log looks like this:

         ==> MAKING "all" ON SUBCOMPONENT ".../libschily.mk"
         ==> COMPILING "OBJ/powerpc-darwin-cc/cmpbytes.o"
cmpbytes.c: In function `cmpbytes':
cmpbytes.c:49: invalid operands to binary |
make[1]: *** [OBJ/powerpc-darwin-cc/cmpbytes.o] Error 1
make: *** [all] Error 2

You are hit by the Apple developers. Some time ago they started to introduce
a file <inttypes.h> which uses types defines in <sys/types.h>
While the buggy types are ignored in <sys/types.h> they are used if found
in <inttypes.h>.

As a workaround, you may edit

	incs/power-macintosh-darwin-cc/xconfig.h

after it has been created by autoconf and make the lint containing
HAME_INTTYPES_H this way:

/* #undef HAVE_INTTYPES_H */    /* to use UNIX-98 inttypes.h */

This will tell the autoconf using code to ignore the system supplied
<inttypes.h> and use the internal version.

IMPORTANT: Don't forget to tell the Apple support that MacOSX sucks until they
fix such fundamental bugs in the system include files!

In case you are interested in the full details: the reason why cdrecord
does not compile is that MacOS X defines a type

typedef	int *		intptr_t;
typedef	unsigned int *	uintptr_t;

instead of the correct:

typedef	long		intptr_t;
typedef	unsigned long	intptr_t;

... a result of either Apple developers being unwilling to read or unable to
understand simple standards written in English :-(

See: http://www.opengroup.org/onlinepubs/7908799/xsh/inttypes.h.html

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

How to compile:

-	Download (http://www.mingw.org) and install the following Mingw32 packages:

		MinGW-3.1.0-1.exe
		MSYS-1.0.10.exe

-	Set PATH environment variable using command:

		set path=c:\msys\1.0\bin;c:\mingw\bin;%path%

-	enter 'make' command in top level directory of the unpacked project

Cdrtools carries is the official version of mkisofs.

To compile mkisofs correctly on all supported platforms (> 30) you
need to use the Schily makefilesystem to get the systematic portability
support.

Read the file README.multi to learn how to create multi-session
CD-R's with this release of cdrecord and mkisofs.

Read the file README.cdplus to learn how to create CD-plus/CD-extra
CD-R's with this release of cdrecord and mkisofs.

You definitely need this release of mkisofs to
create multi-session CD-R's on SunOS/Solaris/SGI-IRIX OS/2 and Win32.

J�rg Schilling

# @(#)README.msdos	1.2 04/06/07 J. Schilling

You cannot compile this program on DOS directly, you need a win32 environment.
See below for more information. You need DJGPP for a compilation.

The DOS/DJGPP have been made with help from
		Alex Kopylov <reanimatolog@yandex.ru>

You may like to check his Web Page: http://bootcd.narod.ru/index_e.htm too.

Compilation under DJGPP is fully integrated into the Schily Makefile System,
however you need to use 'smake' (version 1.2a20 or newer). It seems that
GNU make and other make programs don't work.

As the file names of a typical UNIX project don't fit into the DOS 8.3 naming
scheme, you must have long names support, i.e. you must use a Windows DOS-box
instead pure DOS

To compile under DJGPP:

-	Unpack the following DJGPP packages into c:\djgpp directory:

	ftp://ftp.delorie.com/pub/djgpp/current/v2/beta/djdev204.zip
	ftp://ftp.delorie.com/pub/djgpp/alpha/v2gnu/bsh205bb.zip
	ftp://ftp.delorie.com/pub/djgpp/alpha/v2gnu/gcc340b.zip
	ftp://ftp.delorie.com/pub/djgpp/alpha/v2gnu/gpp340b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/bnu214b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/dif28b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/fil41b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/grep251b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/gwk311b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/gzip135b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/mak380b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/pat253b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/sed407b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/shl2011b.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/tar112ab.zip
	ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/txt20b.zip

Note that these are the best files on 21.05.2004, things may change in future.

-	Set environment variables using commands:

		set path=c:\djgpp\bin;%path%
		set djgpp=c:\djgpp\djgpp.env

	If you are using an smake version before 1.2a23, you also need:

		set djgpp_sh=c:\djgpp\bin\sh.exe


-	Unpack the source archive using command:

		tar -xpz < package-name.tar.gz

	If you like to use star, you need star-1.5a36 or newer.
	Use a command line like:

		star -xpz < package-name.tar.gz

-	Enter 'smake' command in top level directory of the unpacked project
	(to make 'smake' itself, use a command 'dos_make' instead).

	Note that in case you don't have a 'smake' binary for DOS, you need to
	compile one before or fetch a binary from:

		 http://bootcd.narod.ru/index_e.htm

In order to run commands on MS-DOS that use SCSI commands, you must have an
ASPI manager installed in your config.sys. For example:

	SCSI devices:

		device = aspi2dos.sys (not tested!)
		device = aspi4dos.sys (not tested!)
		device = aspi8dos.sys
		device = aspi8u2.sys (not tested!)

	ATAPI devices:

		device = oakaspi.sys

	USB devices:

		device = usbaspi.sys (not tested!)

The ASPI managers may be fetched from:

		http://bootcd.narod.ru/index_e.htm

For CD-Recording please read the README.volmgt too.

CDRTOOLS compiles without changes on any SCO OpenServer 5.0.4
or later installation having the SCO DevSys or GCC-2.95 and
smake-1.2a04 or later installed.

You can get pre-packaged, custom installable binaries from:

   http://www.sco.com/skunkware/cdrtools

Some general notes on CDRTOOLS are available from:

   http://www.sco.com/skunkware/cdrtools/SCO-NOTES.html


Limitations for CDRTOOLS-1.8 on SCO OpenServer 5:

1) SCO OpenServer 5.0.0 and 5.0.2 are unsupported!

2) There is only support for SCSI devices

3) There no support for AHA 154X scsi controllers

===================================================================
NOTE: cdrecord now supports the -scanbus option. Therefore the
      old addressing methods are NO LONGER AVAILABLE !!!
===================================================================

As there is no real generic SCSI driver, cdrecord uses the pass through
ioctl of the cdrom target driver (Srom).

The correct dev= syntax on SCO Openserver 5 is:

    dev=scsibus,target,lun	(and scsibus is scsibus now!!!)

A sample output from cdrecord -scanbus looks like:

#cdrecord -scanbus
Cdrecord 1.8 (i686-pc-sco3.2v5.0.5) Copyright (C) 1995-2000 J�rg Schilling
Using libscg version 'schily-0.1'
scsibus0:
        0,0,0     0) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,1,0     1) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,2,0     2) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) 'PIONEER ' 'CD-ROM DR-U06S  ' '1.05' Removable CD-ROM
        0,6,0     6) 'TEAC    ' 'CD-R56S         ' '1.0E' Removable CD-ROM
        0,7,0     7) *

The first column showing the triple x,y,z tells you the address to use.

As you can see the TEAC CD-R56S CD-Writer does have the following address:

     dev=0,6,0

===================================================================
           THE OLD ADDRESSING IS NO LONGER AVAILABLE!

         PLEASE ADJUST YOUR /etc/default/cdrecord FILES!
===================================================================

Running cdrecord with the old address method will result in an error!

#cdrecord dev=/dev/rcd1:6,0 -inq
Cdrecord 1.8 (i386-pc-sco3.2v5.0.5) Copyright (C) 1995-2000 J�rg Schilling
scsidev: '/dev/rcd1:6,0'
devname: '/dev/rcd1'
scsibus: 0 target: 6 lun: 0
cdrecord: Invalid argument. Open by 'devname' no longer supported on this OS. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.


MAKE SURE YOU HAVE MEDIA IN YOUR CD-ROM DEVICES, SO THAT CDRECORD CAN
OPEN THE DEVICE FOR PASS-THROUGH ACCESS!


To compile cdrtools, you need 'smake' version 1.2a04 or later from:

   ftp://ftp.sco.com/skunkware/osr5/vols


Please make sure you use smake-1.2a04 or later, cause smake-1.2 versions
before a04 will coredump on the compilation of cdrtools on OpenServer.

Compiling on OS/2:

1)	Install EMX

2)	You need /bin/sh, /bin/rm, /bin/mv

	Create a directory /bin and put /bin/sh into this directory
	mkdir /bin
	cp -p d:/emx/bin/sh.exe /bin
	cp -p d:/emx/bin/rm.exe /bin
	cp -p d:/emx/bin/mv.exe /bin




/*--------------------------------------------------------------------------*/
Note that the Joliet implementation on OS/2 is buggy:

It expects the file in the directories in the wrong order.
While Microsoft wants the files to be in ASCII (binary) order,
OS/2 likes to have the files in lexical order (uppercase and
lowercase together). This makes CD's with Joliet attributes
unreadable on OS/2 if there are files that start the same way
but differ in case.
/*--------------------------------------------------------------------------*/

If your system uses the SVr4 ABI (designed by Motorola), you will only
be able to compile my library files lib/format.c and lib/getargs.c if your
C-compiler supports the macro va_copy() or __va_copy() from stdarg.h.

Mach/Next STep/Apple Rhapsody on ppc use a 'void *' for the type va_list
so you don't need to make changes on these systems.

Solaris/ppc (made in 1992) is the first UNIX implementation for the PPC.
It includes the va_copy() macro that allows you to assign a C object of the
type va_list in a system independent way.

Linux/ppc uses exactly the same construct as Solaris for the type va_list.
You will only be able to compile lib/format.c and lib/getargs.c if your
C-compiler includes the macro va_copy() or __va_copy(). If this is not the
case, you will need to upgrade your C-compiler first. GCC 2.8.0 and later
includes this macro.

Here is what Solaris /usr/include/sys/varargs.h looks like:

/*
 * va_copy is a Solaris extension to provide a portable way to perform
 * a variable argument list ``bookmarking'' function.
 */
#if defined(__ppc)
#define	va_copy(to, from)	((to)[0] = (from)[0])
#else
#define	va_copy(to, from)	((to) = (from))
#endif

To be able to compile my lib/format.c and lib/getargs.c on a OS
implementation that uses an array for va_list, you will need
this va_copy() enhancement too.

The files mentioned above already compile on a PPC Apple Rhapsody system.
But as mentioned before, Rhapsody uses a void * for va_list (maybe because
Apple includes badly designed international printf code from BSD 4.4
that requires va_list to be void * to work).

Notice:	lib/format.c allows a %r format that needs additional features
	in stdarg.h. You need to know whether va_list is an array.
	I hope that GCC will include some definitions in future versions
	that allow to propagate va_list type objects from var args
	in function calls.

GCC
===

If you are not using GCC 2.8.0, you can add the following definition
to va-ppc.h :

/usr/lib/gcc-lib/*-linux-gnulibc1/2.*/include/va-ppc.h

#define	va_copy(to, from)	((to)[0] = (from)[0])

and to all other va-*.h files:

#define	va_copy(to, from)	((to) = (from))

Important: Check before if you don't have a GCC that is already patched.

Joerg

On IRIX there is a program from SGI which is called 'smake' too.
Be sure to call the Schily smake when compiling. The IRIX smake
is too dumb.

SGI apearantly has a bug in its mlock*() implementation.

This shows up as a total system freeze for approx. 60 sec at the startup of cdrecord
if cdrecord uses the FIFO.

It can be fixed by:

-	IRIX 6.2: applying patches  (see  freeware.sgi.com/Installable/cdrecord-1.8.html)

-	IRIX 6.5: Using 6.5.7m or above.

/*--------------------------------------------------------------------------*/
Note:	IRIX 6.2 requires the latest rollup patches for mlockall and for
	POSIX 1003.1b scheduling (patches 3771 and 3704 or their successors).
/*--------------------------------------------------------------------------*/

I am using my SCSI library, you don't need to link the program with -lds

This cdrecord distribution contains a mkisofs that runs on SGI
and allows you th read a filesystem from a CD-R device with 2048 bytes
sector size. This is done with the SCSI user level library.


*** Important: IRIX has problems with drives that do disconnects on the SCSI
after an odd number of transferred bytes. It seems that there is a patch for this
problem. Search google for "wd93" to find pointers.

Never compile anything in a locale other than "C" unless you are sure
that your C-compiler and the program 'nm' has been patched.
This is not needed with Solaris 2.6 or later and with the Workshop 5.0
compiler or later.

Even if you are a recent Solaris version, use locale "C" in case of problems.

To ensure that locale "C"' is set, do

setenv LC_ALL C

in csh
or

LC_ALL=C
export LC_ALL
in sh

before running make. Or simply call

env LC_ALL=C make

The reason:

1)	On Solaris before 2.5.1 'nm' dumps core in any other locale.
	For that reason lorder will not work.
	*** no patch available **** but fixed on Solaris 2.5.1
	according to Sun

2)	The SunPro C-compiler will not convert floating
	point numbers correctly if e.g. in "de" locale (Germany)
	1.3 will be interpreted as 1.0!!!!
	*** patch available ***

3)	/usr/xpg4/bin/tr does not work correctly if locale is not "C"
	Try:
		echo ABC | env LC_ALL=de /usr/xpg4/bin/tr 'A-Z' 'a-z'

	it prints:

	BCD



If you want to do compilations on Solaris, it is best not have /usr/ucb
in your PATH. If you want to have /usr/ucb in the PATH it must be the last
entry. You also should put /usr/ccs/bin/ before /usr/xpg4/bin/ in the PATH
to make sure that /usr/ccs/bin/make is used and not /usr/xpg4/bin/make.

To be able to use 'make' 'as' and 'ld' you need to make sure that
/usr/ccs/bin is in your path.

Avoid /usr/ucb and /usr/xpg4/bin in your PATH if you have problems.

Make sure - even if you use GCC - you don't use GNU as, GNU ld
and GNU tsort/lorder.

For CD-Recording please read the README.volmgt too.

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 you run Solaris 7 FCS, install patch 107465-02 to fix a read ahead bug in the
hsfs code.

If you have problems with 12 byte SCSI commands on Solaris (mainly x86) get
Patch 108779-01

If you have problems with ISO-9660 partitions > 4 GB  where Solaris wraps to
offset mod 4 GB when reading from the FS install patch 113277-04.


		IMPORTANT information for Solaris x86

If have no DMA, you will get problems with buffer underruns and may never use
the maximum write speed of current CD/DVD drives.

For more information, read README.solaris-x86-ata-DMA and README.solaris-x86-ATAPI-DMA
and take care that the locations for patching may change in future versions.

It seems that at there is a structure alignment problem
with the structure scsi_cmd at least with gcc.

If you get a message: 'XXX

If you want to run cdrecord on SunOS 4.x on a sparc system
please make sure that you are using the old Sun cc
by typing:

	make CCOM=cc

CDRTOOLS compiles without changes on any UnixWare 7.0.1 or later installation
having the UnixWare/OpenServer DevKit (UODK) or GCC-2.95 and smake-1.2
installed.

You can get pre-packaged, pkgadd installable binaries from:

   http://www.sco.com/skunkware/cdrtools

Some general notes on CDRTOOLS are available from:

   http://www.sco.com/skunkware/cdrtools/SCO-NOTES.html


Limitations for CDRTOOLS-1.8 on UnixWare:

1) SCO UnixWare 2.1.X and UnixWare 7.0.0 are not supported
   - UW2.1.X will compile/work with little changes
   - UW7.0.0 wasn't tested at all

2) There is only support for SCSI devices

3) UnixWare 7.0.1 requires additional PTF's to enable some
   host bus adapters to work with a logical block size of more than
   512 bytes. (Please see the above SCO_NOTES document for details!)

===================================================================
NOTE: cdrecord now supports the -scanbus option. Therefore the
      old addressing methods are NO LONGER AVAILABLE !!!

      As UnixWare 7.1.1 doesn't allow to open the passthrough
      interface for disks, this is disabled by default.
      cdrecord -scanbus will therefore only list devices other
      than disks. To enable the scanning of disks, you need to
      set an environment variable "LIBSCG_SCAN_ALL".

      Be warned, doing so might lock your disk subsystem!
===================================================================

The correct dev= syntax on UnixWare 7 is:

    dev=scsibus,target,lun	(and scsibus is scsibus now!!!)

A sample output from cdrecord -scanbus looks like:

#cdrecord -scanbus
Cdrecord 1.8 (i586-sco-sysv5uw7.0.1) Copyright (C) 1995-2000 J�rg Schilling
Using libscg version 'schily-0.1'
scsibus0:
        0,0,0     0) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,1,0     1) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,2,0     2) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) 'PIONEER ' 'CD-ROM DR-U06S  ' '1.05' Removable CD-ROM
        0,6,0     6) 'TEAC    ' 'CD-R56S         ' '1.0E' Removable CD-ROM
        0,7,0     7) *

The first column showing the triple x,y,z tells you the address to use.

As you can see the TEAC CD-R56S CD-Writer does have the following address:

     dev=0,6,0

===================================================================
           THE OLD ADDRESSING IS NO LONGER AVAILABLE!

         PLEASE ADJUST YOUR /etc/default/cdrecord FILES!
===================================================================

Running cdrecord with the old address method will result in an error!

#cdrecord dev=/dev/rcdrom/cdrom1:6,0 -inq
Cdrecord 1.8 (i386-pc-sco3.2v5.0.5) Copyright (C) 1995-2000 J�rg Schilling
scsidev: '/dev/rcd1:6,0'
devname: '/dev/rcd1'
scsibus: 0 target: 6 lun: 0
cdrecord: Invalid argument. Open by 'devname' no longer supported on this OS. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.


To compile cdrtools, you need 'smake' from:

   ftp://ftp.sco.com/skunkware/uw7/Packages


or 'gmake'. Smake is preferred as gmake bugs will cause bogus warnings
and may confuse about the state of the make run.

This README was written by Dr. Eberhard Heuser-Hofmann
	vaxinf@chclu.chemie.uni-konstanz.de

If you are looking for a *.zip file instead of the tar archive,
check this address:

ftp://v36.chemie.uni-konstanz.de/cdrecord_vms/

/*--------------------------------------------------------------------------*/
Hi,

this is the OpenVMS Version of J.Schilling's cdrecord-program.

There is a command-procedure called build_all.com in the [.cdrecord] subdir,
that compiles and links the code. The cdrecord-program is been produced in
[.cdrecord.vms] subdirectory.

Define this program as a symbol via

$ cdrecord:==$disk:[dir]cdrecord.exe

$ cdrecord -help gives an idea about the options, that are possible:

cdrecord -help
Usage: cdrecord.exe [options] track1...trackn
Options:
        -version        print version information and exit
        dev=target      SCSI target to use as CD/DVD-Recorder
        gracetime=#     set the grace time before starting to write to #.
        timeout=#       set the default SCSI command timeout to #.
        debug=#,-d      Set to # or increment misc debug level
        kdebug=#,kd=#   do Kernel debugging
        -verbose,-v     increment general verbose level by one
        -Verbose,-V     increment SCSI command transport verbose level by one
        -silent,-s      do not print status of failed SCSI commands
        driver=name     user supplied driver name, use with extreme care
        driveropts=opt  a comma separated list of driver specific options
        -checkdrive     check if a driver for the drive is present
        -prcap          print drive capabilities for MMC compliant drives
        -inq            do an inquiry for the drive and exit
        -scanbus        scan the SCSI bus and exit
        -reset          reset the SCSI bus with the cdrecorder (if possible)
        -overburn       allow to write more than the official size of a medium
        -ignsize        ignore the known size of a medium (may cause problems)
        -useinfo        use *.inf files to overwrite audio options.
        speed=#         set speed of drive
        blank=type      blank a CD-RW disc (see blank=help)
        -load           load the disk and exit (works only with tray loader)
        -eject          eject the disk after doing the work
        -dummy          do everything with laser turned off
        -msinfo         retrieve multi-session info for mkisofs >= 1.10
        -toc            retrieve and print TOC/PMA data
        -atip           retrieve and print ATIP data
        -multi          generate a TOC that allows multi session
                        In this case default track type is CD-ROM XA2
        -fix            fixate a corrupt or unfixated disk (generate a TOC)
        -nofix          do not fixate disk after writing tracks
        -waiti          wait until input is available before opening SCSI
        -immed          Try to use the SCSI IMMED flag with certain long lasting commands
        -force          force to continue on some errors to allow blanking bad disks
        -dao            Write disk in SAO mode. This option will be replaced in the future.
        -raw            Write disk in RAW mode. This option will be replaced in the future.
        -raw96r         Write disk in RAW/RAW96R mode. This option will be replaced in the future.
        -raw96p         Write disk in RAW/RAW96P mode. This option will be replaced in the future.
        -raw16          Write disk in RAW/RAW16 mode. This option will be replaced in the future.
        tsize=#         Length of valid data in next track
        padsize=#       Amount of padding for next track
        pregap=#        Amount of pre-gap sectors before next track
        defpregap=#     Amount of pre-gap sectors for all but track #1
        mcn=text        Set the media catalog number for this CD to 'text'
        isrc=text       Set the ISRC number for the next track to 'text'
        index=list      Set the index list for the next track to 'list'
        -text           Write CD-Text from information from *.inf files
        textfile=name   Set the file with CD-Text data to 'name'
        -audio          Subsequent tracks are CD-DA audio tracks
        -data           Subsequent tracks are CD-ROM data mode 1 (default)
        -mode2          Subsequent tracks are CD-ROM data mode 2
        -xa1            Subsequent tracks are CD-ROM XA mode 1
        -xa2            Subsequent tracks are CD-ROM XA mode 2
        -cdi            Subsequent tracks are CDI tracks
        -isosize        Use iso9660 file system size for next data track
        -preemp         Audio tracks are mastered with 50/15 �s preemphasis
        -nopreemp       Audio tracks are mastered with no preemphasis (default)
        -copy           Audio tracks have unlimited copy permission
        -nocopy         Audio tracks may only be copied once for personal use (default)
        -scms           Audio tracks will not have any copy permission at all
        -pad            Pad data tracks with 15 zeroed sectors
                        Pad audio tracks to a multiple of 2352 bytes
        -nopad          Do not pad data tracks (default)
        -shorttrack     Subsequent tracks may be non Red Book < 4 seconds if in SAO or RAW mode
        -noshorttrack   Subsequent tracks must be >= 4 seconds
        -swab           Audio data source is byte-swapped (little-endian/Intel)
The type of the first track is used for the toc type.
Currently only form 1 tracks are supported.

One important point is how the CDR-device is being selected:

dev=i,j,k

where:
i: 0   1   2   3   4   5   6   7   8   9    ...  32  33
   dka dkb dkc dkd gka gkb gkc gkd dqa dqb  ...  dqy dqz

j: scsi-id
k: sub-lun (usually 0)

As an example:

dev=1,5,2 selects dkb502:

An typical example how to put virtual disk data onto a cd-rom is given here:

$ cdrecord -speed 2 dev=0,4,0 dka200:[000000]vda0.dsk

Additional hints:

1. Due to timeout problems use -immed switch for IDE-burners under OpenVMS 7.3
   or modify the timeout value in the dqdriver source.

2. HP has written a command procedure, that calls cdrecord. You should
   modify this com-file to activate the cdrecord burnproof option:
   "driveropts=burnproof".

Be aware that cdrecord has copyright on it.

Eberhard

===============================================================================

Dr. Eberhard Heuser-Hofmann
Univ. Konstanz
Fakultaet fuer Chemie
Universitaets-Strasse 10
D-78464 Konstanz
Germany
Phone: +49-7531-88-2026, FAX: +49-7531-88-3139
email: vaxinf@chclu.chemie.uni-konstanz.de

===============================================================================

# @(#)README.win32	1.10 14/12/07 Copyright 2000-2014 J. Schilling

cdrecord-1.8a22 or later can be compiled on Win9X/NT4 using Cygnus' cygwin
which is freely available from:

	http://sourceware.cygnus.com/cygwin/
or
	http://sources.redhat.com/cygwin/

To compile on Cygwin, get Cygwin by executing setup.exe

You will need approx. 120 MB to install a full cygwin developer release.

Get the tar'ed cdrtools source and unpack it with 'gnutar' or 'star',

e.g. Start a bash command line window and type:

	star -xpz < cdrtools-3.01.tar.gz

	don't use winzip to unpack the tar archive, it will not
	unpack symlinks correctly.

Then (from the bash command line window) run 'make' ...

If you have problems with GNU make, get 'smake' from:

	http://sourceforge.net/projects/s-make/files/alpha/

/*--------------------------------------------------------------------------*/
A bash window is available from the START -> Programs -> Cygnus Solutions
menu or by clicking at the Cygwin Logo on the desktop.
/*--------------------------------------------------------------------------*/
Pre-compiled current 'cdrtools' Win32 binaries which should run on
W95, W98 and WNT are available from:

	http://sourceforge.net/projects/cdrtools/files/alpha/win32

To use the pre-compiled binary, put the files cygwin1.dll, mount.exe as well
as the files:

cdrecord.exe		- The CD recording program
cdda2wav.exe		- The DAE (Digital Audio Extraction) program
mkisofs.exe		- The ISO-9660/Rock Ridge/Joliet Filesystem formatter
readcd.exe		- A simple program to extract CD-ROM raw data to a file

in your WINDOWS binary directory and from a Command/MS-DOS (or bash) window
type:
	cdrecord -help

for usage, see also:

		http://cdrecord.org/

All programs in this directory are Unix command line utilities and know
nothing about DOS/WIN. They run in a POSIX subsystem that is supplied by
cygwin1.dll. Therefore all directory names are given in Unix (POSIX) format
(i.e. use '/' for a directory separator, not '\'). To access files on another
disks (i.e. floppy, CDROM and network disk), you need to use the supplied "mount"
command e.g.

	mount a: /a
	mount d: /cdrom

i.e. files on the floppy disk are accessed as being in directory /a and
files on the CDROM are accessed as /cdrom (assuming your CDROM is drive d:)

Yu may also use the new /cygpath notation by typing /cygpath/a for
your local floppy.

The notation //a/dir as a replacement for the DOS directory name a:\dir
may not work in future releases of Cygwin.

The following command creates a CD image in the current directory
using a source directories on the CDROM drive, a sub-directory and the
floppy drive:

	mkisofs -o hsfs.iso -J -R /cdrom/subdir dir1 /a

If you use the options noted above, the hsfs.iso image is ISO-9660
compliant and includes both Rock Ridge (IEEE P1282) and
Joliet (Microsoft proprietary) extensions.

If your CD writer is on target 6, type

	cdrecord dev=6,0 -v speed=4 hsfs.iso

to write the image at speed 4 in TAO mode, or

	cdrecord dev=6,0 -v speed=4 -dao hsfs.iso

to write the image in DAO mode.

If you don't like to create the image file 'hsfs.iso' you may use a PIPE
to connect mkisofs's output to cdrecord's input by calling:

	mkisofs -J -R /cdrom/subdir dir1 /a | cdrecord dev=6,0 -v speed=4 -

IMPORTANT NOTE:	If you use PIPE's on Win32, you definitely need a POSIX
		compliant shell to start the programs. Native Win32 PIPE's
		are not POSIX compliant and will not work with POSIX compliant
		programs.

/*--------------------------------------------------------------------------*/
If you don't know which target your CD-writer is, call

	cdrecord -scanbus

This gives output similar to:

Cdrecord-ProDVD sparc-sun-solaris2.4 release 1.8a39 Copyright (C) 1995-2000 J�rg Schilling
Using libscg version 'schily-0.1'
scsibus0:
	0,0,0	  0) 'Quantum ' 'XP34300         ' 'F76D' Disk
	0,1,0	  1) 'SEAGATE ' 'ST11200N        ' '8334' Disk
	0,2,0	  2) *
	0,3,0	  3) 'TOSHIBA ' 'MK537FB/        ' '6258' Disk
	0,4,0	  4) 'WANGTEK ' '5150ES SCSI-36  ' 'ESB6' Removable Tape
	0,5,0	  5) 'EXABYTE ' 'EXB-8500-85QUE  ' '0428' Removable Tape
	0,6,0	  6) 'TOSHIBA ' 'XM-3401TASUNSLCD' '3593' Removable CD-ROM
	0,7,0	  7) HOST ADAPTOR
scsibus1:
	1,0,0	100) 'IBM     ' 'DCAS-34330      ' 'S65A' Disk
	1,1,0	101) *
	1,2,0	102) *
	1,3,0	103) *
	1,4,0	104) 'PLEXTOR ' 'CD-R   PX-W8220T' '1.00' Removable CD-ROM
	1,5,0	105) 'YAMAHA  ' 'CRW4416S        ' '1.0f' Removable CD-ROM
	1,6,0	106) *
	1,7,0	107) HOST ADAPTOR

The numbers on the labels are SCSIbus# * 100 + target#

You then call cdrecord dev=bus#,target#,0

If you e.g. like to talk to the Yamaha drive from the list above, you need to
call:

	cdrecord dev=1,5,0 ......

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

			NOTE

If "cdrecord -scanbus" dumps core (dies from program fault), you have
a broken ASPI driver on your PC.

If you cannot see your drive(s), the following registry changes should make
them visible:

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32]
  "ErrorControl"=dword:00000001
  "Start"=dword:00000001
  "Type"=dword:00000001

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32\Parameters]
  "ExcludeMiniports"=""


If you like to use the tools with SCSI or ATAPI, you need a working
ASPI32 driver and dll on your system. If you don't have it already,
look for 'aspi_me'. You need to set you clock back to a time before
Jan 1st 1999 to be able to install it. Note that 'aspi_me' contains
original Adaptec drivers and is banned from most ftp servers for this
reason.

If you do not have superuser permission which would allow you to use
the SPTI SCSI interface that is similar to a UNIX ioctl interface,
you need a special ASPI driver version on NT-5.0 (Win2000)

You may get one by searching for:

	wnaspi32.dll


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

			IMPORTANT

In order to avoid damaging CD blanks because Win is trying to access
the drive while cdrecord writes to it, you definitely should edit
your registry and set the value of

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom\Autorun

to '0'.

The Registry entry noted above is valid for WNT, I don't know
if you need to do this for W95 or W98, nor do I know the
correct Registry entry for these systems.

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

		For binary only users:

Error messages and help output is directed to stderr. Win32 command
interpreters don't know about stderr. I recommend to install bash.exe
because it is a POSIX compliant shell and allow working PIPE's and
it also gives you a command line history that may be edited using
cursor commands.

Otherwise you may want to install the Cygwin light version which
only includes the user commands.

The current *BSD port will not yet be able to scan the SCSI bus
for a CD-Recorder as it is on other architectures.

User level SCSI seems not be be well tested on *BSD

It would be nice if the kernel hackers of all *BSD flavors could agree in
adding decent and useful SCSI user land transport support.
This would cause the following changes:

	-	Add a driver that is present by default and offeres an
		easy to address interface to the /dev/ namespace.
	-	Create device file entries for this driver by default.
	-	allow to send all commands on this driver even if the main
		driver entry is in use, At least allow:
			INQUIRY
			TEST_UNIT_READY
			REQUEST_SENSE
		to be able to scan the SCSI bus for drives.

NOTE: This changed with FreeBSD/cam cdrecord -scanbus works on FreeBSD/cam

Workaround:

If /dev/su0-0-0 ... does not exist on your system, you may try
to create the devices with the MAKEDEV.su script below.

If /dev/su0-0-0 ... do not work on your system, you may try
use dev=/dev/rcd0a:@,0 od dev=/dev/rcd0a:@
If the CD-Recorder is on /dev/cd0a

Read the man page for more information.

There is no way to get the device node entry from the numerical target
specification on *BSD. You must specify the appropriate device node name:
e.g. dev=/dev/cd0.ctl:6,0 together with the numerical target specification.
A short form is:

	dev=/dev/cd0.ctl:@

But this syntax may not work on all *BSD flavours as not all *BSD flavours
support mapping back the target/lun numbers from a device.

In any case: read the cdrecord man page and try to find the /dev/* entry for
your CD-recorder that allows to be used with ioctl's.

On FreeBSD/cam, you will be able to access the CD-Recorder as on other
systems. If your CD-Recorder is on SCSI Bus 0, Target 2, lun 0
type:

cdrecord dev=0,2,0 .....

J�rg

------------------------- MAKEDEV.su------------------
#!/bin/sh

#
# You must check which minor base is really needed for your system
# The su driver seems not to be well tested on *BSD
#
# If nothing else helps, create a link /dev/scgx to the right
# /dev/ entry (an entry that responds right with /sbin/scsi)
# for your needed device.
#
minorbase="536870912 + 2"
#minorbase="0"
#minorbase="0 + 2"
#minorbase="0 + 3"

mknod /dev/su0-0-0 c 18 `expr $minorbase + 0 '*' 8`
mknod /dev/su0-1-0 c 18 `expr $minorbase + 1 '*' 8`
mknod /dev/su0-2-0 c 18 `expr $minorbase + 2 '*' 8`
mknod /dev/su0-3-0 c 18 `expr $minorbase + 3 '*' 8`
mknod /dev/su0-4-0 c 18 `expr $minorbase + 4 '*' 8`
mknod /dev/su0-5-0 c 18 `expr $minorbase + 5 '*' 8`
mknod /dev/su0-6-0 c 18 `expr $minorbase + 6 '*' 8`
mknod /dev/su0-7-0 c 18 `expr $minorbase + 7 '*' 8`

mknod /dev/su1-0-0 c 18 `expr $minorbase + 1 '*' 64 + 0 '*' 8`
mknod /dev/su1-1-0 c 18 `expr $minorbase + 1 '*' 64 + 1 '*' 8`
mknod /dev/su1-2-0 c 18 `expr $minorbase + 1 '*' 64 + 2 '*' 8`
mknod /dev/su1-3-0 c 18 `expr $minorbase + 1 '*' 64 + 3 '*' 8`
mknod /dev/su1-4-0 c 18 `expr $minorbase + 1 '*' 64 + 4 '*' 8`
mknod /dev/su1-5-0 c 18 `expr $minorbase + 1 '*' 64 + 5 '*' 8`
mknod /dev/su1-6-0 c 18 `expr $minorbase + 1 '*' 64 + 6 '*' 8`
mknod /dev/su1-7-0 c 18 `expr $minorbase + 1 '*' 64 + 7 '*' 8`