-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.win32
185 lines (127 loc) · 6.22 KB
/
README.win32
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
# @(#)README.win32 1.3 01/03/05 Copyright 2000 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-1.10.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:
ftp://ftp.fokus.gmd.de/unix/smake/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:
ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/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://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/man/cdrecord.html
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 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.
You need a special ASPI driver version on NT-5.0 (Win2000)
You may get one by downloading
http://www.poikosoft.com/writer/download.html
and unpacking the file mightywriter121.exe using unzip.
after you renamed ntaspi32.dll to wnaspi32.dll, cdrecord should work.
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.