Hi,
BTW: What happened to FreeBSD User Giacomo and his Samsung DVD writer ?
Any news to report ? A happy ending perchance ?
Bill Davidsen: [about filtering dangerous SCSI commands]
My suggestion would be to add an ioctl, like SET_SCSI_UNFILTERED, which
can only be used as root, and which
Hi,
Joerg Schilling:
I do not
write hacks as other aothors may do but I follow the MMC standard
Just for the records:
libburn is developed according to MMC and i am not aware of
any serious deviations from MMC in dvd+rw-tools either.
libburn still supports some pre-MMC-5 legacies, like mode
Hi,
Craig Harding:
I'm tring to write an iso file to a blank'ed dvd-rw disc and I got this
error. I know that the error msg speaks for itself (medium error), but
just wondering if it could actually be something else besides my dvd as
I've used this disc a few times already. It was burning for
Hi,
Verbatim DVD-R 16x 4.7GB.
This cannot be burned without the failed MODE SELECT command.
drive name: sr1 sr0
...
Can write DVD-R:1 0
Currently i'd count this as a documented case of a
drive lying towards the operating system.
I just tried a noname blank
Hi,
Joerg Schilling:
First an important question: how did you connect that drive?
You used the sg interface but the drive is most likely ATAPI.
Andreas Klauer:
Samsung SH-S183A SATA on VIA VT6420 controller
OS is Linux 2.6.18 Debian Etch,
SATA drives nowadays appear as sg,sr,scd.
Seen from
in very handy for scdbackup.
Joerg:
There is no such mode, what are you talking about?
MMC-5:
5.3.11 Incremental Streaming Writable Feature (0021h)
The Incremental Streaming Writable Feature identifies a Drive that is able
to write data to a contiguous region, and is able to append data
Hi,
Kish Shen:
Anyway, it [mkisofs] again said my file is too large and ignored it.
Even if you can talk some mkisofs into formatting a
file system with a file = 2 GB, even then you might
have difficulties to read that file on arbitrary
computer systems.
You'll have to split your file or use a
come in very handy for scdbackup.
Don't get me wrong. I am sincerely interested in learning
about cdrecord's capabilities.
I just tested with cdrecord-2.01.01a23 on a blank DVD-RW
dd if=/dev/zero bs=1M count=500 | cdrecord -v dev=0,0,0 -packet -
and got
cdrecord: Drive does not support TAO
Hi,
Isaia Luciano wrote:
cd0: TSSTcorp CD/DVDW SH-S182M SB02 device Removable CD-ROM SCSI-0
Google for this type and you will find a surprising
high density of cries for help among all the usual
best-price offers.
If I use the comand whith a dvd+rw : dvd+rw-format /dev/cd0
Input/output
Hi,
be invited to try my program cdrskin, a burn backend for
CD and DVD with a command line interface that is compatible
with cdrecord's main gestures for CD.
System requirements:
Linux with kernel 2.4 or 2.6.
With kernel 2.4 an ATA drive has to be under ide-scsi control,
with kernel 2.6
Hi,
For cdrskin i decided to:
- disallow undefined track size with DVD-R[W] DAO
and demand a recognizable file size or an explicit
track size.
Just for reference, Joerg and I had a discussion of this, related to
doing remote backups where the ISO image is generated on one machine
Hi Joerg,
while exploring DVD burning in theory and practice i
stumbled over some user-confusing behavior of cdrecord
in cases where a DVD-RW media is not in a suitable state.
With written, non-appendable media it begins to issue
error messages about CD and 100 minutes.
With appendable media it
Hi,
I tried cdrecord -scanbus. But I got the following error message.
cdrecord: No such file or directory. Cannot open SCSI driver.
Can you help me please?
Looks like you stirred up other much older quarrels.
These quarrels are the reason why we got some wealth of
cdrecord compatible
Hi,
Bill Davidsen:
I can't replicate the no TAO with a CD,
This is the best outcome we can wish for.
A non-TAO CD burner would be very annoying.
Question: what does -dvd-compat really do?
You mean in growisofs ? That's always interesting
to read :))
On the first hand it sets variables
Hi,
Bill Davidsen:
for some reason cdrecord
thinks the TAO capability is missing. As noted, growisofs has no such
problem,
Joerg Schilling:
DVDs do not support TAO
Indeed. But they constitute a nice freak show of
write modes and usage peculiarities.
DVD-RAM, DVD+RW and DVD-RW
Hi,
I have had growisofs incorrectly find the size of the blank DVD+RW I put
in my burner (it found 2GB+ instead of the 4.7 which they have in
reality). A typical error message looks like this:
:-( /dev/scd1: 2295104 blocks are free, 3589847 to be written!
...
Mounted Media: 1Ah,
Hi,
The more general question is
Are CD / DVD media suitable for backup, at all?
On German TV there has been a warning recently that
a CD (DVD) might get unrecoverable errors even with one year.
This touches two topics:
1) The question about backup suitability.
2) The question about our
Hi,
Bill Davidsen wrote:
When I try to pipe an ISO into the cdrecord program, it complains that
it needs tsize= option to do the burn.
Is it possible you have trouble with this change
as of version cdrtools-2.01.01a20 ?
AN-2.01.01a20:
Cdrecod now default to the write mode -sao in case that
to match
^Disk Is erasable.
It was no problem for me to include the necessary
test in scdbackup. Old installations which get newest
cdrecord will need a new scdbackup, too. That's life.
But: will this text layout persist ?
ATIP info from disk:
Indicated writing power: 3
Reference speed
Hi,
update and probably final report about the setuid problem on
SuSE 9.3 :
Joerg was right: with setuid bit the program is not
running as root but geteuid() returns the UID of
the previous owner of the file thomas.
The problem seems bound to a single ext3 partition and
even there it is not
Hi,
If you (thomas) have been able to chmod u+s on a file owned by root,
then something looks broken.
The procedure is:
- thomas compiles cdrtools
- root copies ./cdrecord/OBJ/athlon-linux-cc/cdrecord to /usr/bin
It shows up as owned by root, group is root. (But somehow isn't.)
- root executes
Hi,
Bill Davidsen wrote:
Does ls -ld show the same thing on both directories?
No setuid on the directory itself, or anything like that?
I am firing up the old machine. (667 MHz and
needs a few minutes of pre-warming before boot)
Beep (is a good sign). Green SuSE jungle.
I hate Firlefanz at
Hi,
Bill Davidsen wrote:
What I was looking for is the setgid bit on a directory in
/home/thomas/usr/bin
Well, there isn't. At least i could not spot.
Copied with cp -p of course? To preserve ownership and permissions?
No. I toggled as root
mkdir /home/thomas/usr
mkdir
Hi,
http://scdbackup.sourceforge.net/cdrskin-0.2.6.pl01.tar.gz
It still does not have a working configure.
If that happens on Linux with a 2.4 or 2.6 kernel
then this is a defeat for our project (and for
autotools, possibly).
I would appreciate a complete log of the failed
configure run.
Hi,
on SuSE 9.3 the problem with
/usr/bin/cdrecord-2.01.01a21-hz100: Permission denied. Cannot open
'/dev/hda'. Cannot open SCSI driver.
is not bound to the binary from SuSE 9.0 but to the
setuid bit:
The locally compiled version does not work any more
as soon as it is treated with chmod u+s
Hi,
Does a suid root binary work in case that there is
#if LINUX_VERSION_CODE = 0x020600
Nope. I test with a simple cdrecord -scanbus :
The binary from 9.0 stumbles over /dev/sg1 :
/usr/bin/cdrecord-2.01.01a21-hz100-suse-9.0:
Permission denied. Cannot open '/dev/sg1'. Cannot open SCSI
Hi,
Permission denied. Cannot open '/dev/sg1'. Cannot open SCSI driver.
cdrecord is not installed suid root or you are not calling as root.
I swear. It only makes trouble after chmod u+s .
-rwsr-xr-x 1 root root 391843 2006-11-29 20:45
/usr/bin/cdrecord-2.01.01a21-hz100
In that state
Hi,
I did never see any problems from a missing HZ definition.
It looks like a bug on this distribution
We discussed it in July 2004. Yes it is a distro bug
which i workaround each time i compile your source
releases. SuSE 9.0 seems to suffer from a mix of 100
and 1000 Hz. Probably the
Hi,
I don't care about libburn, it is so broken that it does not even complete
it's configure run:
checking for a BSD-compatible install... /opt/sfw/bin/ginstall -c
./configure: line 19396: syntax error near unexpected token `in'
./configure: line 19396: `for ac_header in'
That looks much
Hi,
regrettably cdrecord-2.01.01a21 seems to be unusable on my
Linux 2.4 system which has 2 burners under ide-scsi and
1 DVD-ROM not under ide-scsi.
I downloaded
ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-2.01.01a21.tar.gz
made my usual #define HZ 100 in libscg/scsi-linux-sg.c,
Hi,
'/dev/hda'. Cannot open SCSI driver.
This looks to be impossible: If you run cdrecord with the apropriate rights
(root) you should be able to open /dev/hda.
I was root. Via su login, not via setuid.
Blame it on SuSE library configurations.
After all, the binary built on the local
and growisofs.
Number 2:
My project
http://scdbackup.sourceforge.net/main_eng.html
provides multi volume backup in formats ISO-9660, afio or star.
The appropriate commands would be
sdvdbackup_afio .
resp. in star format
export SDVDBACKUP_AFIO=$(scdbackup -where scripts)/star_as_afio_wrapper -acl
Hi,
I wrote:
star -c -acl -link-dirs level=0 . | gzip | growisofs ...
Joerg Schilling wrote:
For backups, I recommend to use star's dump format (created if you
add -dump to the command line).
We discussed this in August 2005 on star-users :
Hi,
DVD backup server. This machine has 96MB memory,
That machine must be several years older than the
DVD burner.
I thought mkisofs is somewhat pipeline process, files comes in, iso
images goes out. I thought the memory needed is not directly related to
the amount of data to make ISO
Hi,
I got a subtree of 2 million empty files where mkisofs
exceeds 2 GB of memory consumption. I never found out
wether it would finally end or crash.
Why? Did you stop it?
I began to fear about the health of my consumer disk.
Hours of extreme disk rattling due to the fight of
stat() and
Hi Joerg,
is it intentional that cdrecord returns exit value 0
after -toc failed quite loudly on a blank CD-RW ?
If yes: i am curious about the particular reason.
The exit value on empty tray is 255.
$ cdrecord -v dev=0,1,0 -toc echo CDRECORD SUCCESS
Cdrecord-ProDVD-Clone 2.01.01a12
Hi,
Joerg Schilling:
Cooperative locking is needed in a way that allows and is based not on
device nodes but on real hardware targets.
Bill Davidsen:
I'm less sure about cooperative locking, any method which fails if any one
program behaves badly is not scalable.
It seems to be a hard
Hi,
Andy:
int grab_sg (int blkfd)
me:
Seems to work well for me and my two drives sr0 and sr1.
Joerg:
Forget about this method. It is known not to work reliably on Linux
and similar moethods will not work at all on other OS.
This is a kind of emergency patch for a particular
problem with
Hi,
int grab_sg (int blkfd)
Seems to work well for me and my two drives sr0 and sr1.
I threw out two of my three functions and made
try_to_lock_linux_sg() using grab_sg() instead.
The call in builtin_dd() has changed a bit:
if (i == 3 fd = 0)
Hi,
Is it possible we define a common locking mechanism for drives
which does not depend on hardly documented Linux O_EXCL ?
Something simple and very portable would be needed.
As for locking, or rather serializing access to [relevant] devices.
Very portable customarily means support
Hi,
Andy Polyakov wrote:
Have you seen resmgrd?
I found this overview of 2006-09-29:
http://forgeftp.novell.com//resmgr/web/README.html
which differs a bit from the impression i got from
the SuSE 9.0 man pages.
One could execute program
resmgr lock /dev/xyz
and then open the device by
Hi,
[EMAIL PROTECTED] wrote:
Very portable almost alwas == equally crippled on all platforms.
I'm so tired of 'very portable' software.
A general locking facility would have to be system
dependent in respect to device identification and
naming.
All other aspects, especially the generic
Hi,
[...] problem with ext3 implementation under 2.4 [...]
It remains mystery why it was not noticed earlier by 2.4 users.
On my 2.4.21 kernel SuSE 9.0 and ext3 based /home there
is no problem with growisofs 7.0 and this command:
growisofs -Z /dev/sr1=/home/fertig.iso
Shrug.
Have a nice
Hi,
this is a request towards all developers of burn backends.
Is it possible we define a common locking mechanism for drives
which does not depend on hardly documented Linux O_EXCL ?
Something simple and very portable would be needed.
Advisory locking would be sufficient, i think.
It should
Hi,
which does not depend on hardly documented Linux O_EXCL ?
Something simple and very portable would be needed.
- Linux has a silly problem caused by device aliasing:
Yeah. But *that* i could circumvent.
The drivers know the SCSI quatruple (Host,Channel,Id,Lun)
and by that i can
Hi,
congrats to new dvd+rw-tools-7.0 .
Runs out of the box.
UBU = unit buffer usage ?
Blu-ray ... BD-RE ... 25 to 50 GB ...
I just got a new DVD DL burner by incident.
Did i miss something ?
Googling for prices ... LG Electronics GBW-H10N ...
you get 2 TB of RAID for that ... Pioneer
Hi,
... now switched to Linux ... multi-session ... CDR ...
I myself am not into multi-session. So a few general
hints. (And a test wether i'd could help myself.)
A bit an outdated HOWTO (google for cdrecord howto or mkisofs howto)
to give the users of scdbackup free choice of
burner programs then i need a place where to i can point
them for cdrecord.
The more simple, the better.
A fixed URL of the currently advised source tarball would
be very helpful for that. Then scdbackup's README can point to
it permanently.
Like:
Get
to be adjusted.
I can hardly evaluate wether -joliet-long did ever bring
positive results. But mkisofs-2.01.01a09 has no problem
with that setup. (scdbackup does not use -J or -joliet-long
by default, because some older mkisofs did not do so well
on -J. Actually i use it in the hope to reproduce
Hi,
@@ -583,6 +583,7 @@
+++ ./getargs.c Sa Sep 9 15:58:33 2006
+ argp = sargp;
... cdrtools-2.01.01a13/libschily/getargs.c ...
For me it is rather line 566.
Now i seem to have a problem with the build dependencies:
$ make
make[2]: Entering directory
the roles which stick to me right now
- developer of scdbackup, who recently asked the Debian
cdrkit project for migration hints about wodim.
(scdbackup uses cdrecord as default, but will support wodim
and already does support cdrskin under their real names.)
- developer of cdrskin which tries
test with scdbackup.
I'll report.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
in the name of my project scdbackup and its CD burning users
i want to thank Joerg Schilling for providing the burn foundation
since my project started in 1999.
I commend Joerg for his software which still is the foundation
of scdbackup's core CD functionality, although i took substantial
Hi,
for subscription:
List-Post: mailto:cdwrite@other.debian.org
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: mailto:[EMAIL PROTECTED]
List-Unsubscribe: mailto:[EMAIL PROTECTED]
probably you fell victim to false addresses on some web site.
Short before end an I/O-Error happens and was
Hi,
I can't write CD-R discs with cdrecord - it objects on the grounds of my
giving it DVD media - but I'm feeding it CD-R blanks.
CD-RW discs work just fine as do DVD-RW with growisofs.
I _used_ to be able to write CD-R - I have several as evidence from a
couple of months ago. Since
Hi,
Joerg Schilling wrote:
Today, I happily announce new features and the release of the DVD-code
into the OpenSource.
Applause for this move !
Did you already decide the future fate of the ProDVD download directory
ftp://ftp.berlios.de/pub/cdrecord/ProDVD ?
It would still be useful for
Hi,
I keep track of the md5sums of all the images I burn.
[...]
So, I rebuilt a new image via mkisofs from the exact same
directory structure used to create the old image. Now, the two images had
the exact same byte count, but, much to my surprise, they differed with
respect to their
Hi,
Michael Shell wrote:
3. mkisofs is embedding the output filename/path or the command line as
it was invoked within the created image
I wrote:
I don't think so.
One can be certain and be wrong.
011 M K I S a t M a y 6 1
0110020 0 : 0
Hi,
I'm trying to run growisofs 6.1 on Nslu2 device (with etch) it's small
device with low power consumption and with only 32M RAM:(
I have tried to recompile debian source with smaller buffer size
WARN=-DDEFAULT_BUF_SIZE_MB=16 but i don't know how to check this buffer
size in complled
Hi,
While going through the changelog of the shell script we're using I
found a note of one of my colleagues which said that in the past (when
we used plain IDE CD_RW drives) we got this problem occasionally. I
thought it was a fluke and promptly changed it back to be strict (the
shell
Hi,
Looks like Joerg is not amused by some bug-or-feature of
your Linux.
Take out the your part :-)
Ok. Neither mine nor yours.
I meant Joerg has problems with linux in general (and I tend to agree
with him as regards to linux scsi infrastructure), not any specific
distributions (mine
Hi,
However, recently I found that in some cases cdrecord, maybe due to the
drive not returning all the info it needs, will not print the erasable
string even if the media is CD-RW (cdrecord can succesfully burn it).
Oops. My own backup tool relies on that same output of
cdrecord -atip and
: http://www.serice.net/shunt/
My scdbackup : http://scdbackup.sourceforge.net/main_eng.html
Be advised to have a look at both projects. They offer quite
different services and results.
scdbackup uses afio or star format but can be talked into
using tar, too. For your purposes the following
Hi,
I do not know wether tar needs a neat EOF from the media
[...]
Actually, if reading from a named pipe instead of the device, it works OK.
Then just put in disc 1, 'cat /dev/dvdrw named-pipe', and on another
terminal 'tar -t -f /named-pipe --multi-volume'. When the output ends
Hi,
I wrote:
I am looking since quite a while for the particular
and substantial security problems which one is said
to have if one allows w-access to a CD/DVD writer.
Matthias Andree wrote:
As far as I understand Jörg, vendor-specific commands are often involved
in CD writing, and if
Hi,
Denis S. wrote:
Subject: growisofs did not exit cleanly :P
Recently I've upgraded to new dvd+rw-tools and got new error which
appear each time k3b finish writing DVD, because of this error K3B is
unable to perform verification of written data,
Here is error message:
growisofs
Hi,
This was not a change made because it would be nice, it was made because
it became public information that anyone who could burn could change the
firmware. Security fixes sometime do have to be done quickly, evil
people do tend to jump on any opening in the time between a
Hi,
My purpose using RockRidge is retaining oringal ownership and
permission of data to solve following problem;
I burnt /home/ of a FC3 box on CDs. /home/ was on its own partition.
Then running LFS LiveCD I copied the CDs on a partition of a new HD
[...] Later I discovered all data after
Hi,
But why did the [DVD-RW] media work in september 2004 and die a quick
and reliable dead in november 2005 ? The same spindles. Two
brands with two different media infos. Wether unused previously
or re-written.
You'd need a useful error rate scan of the media to establish
this.
Hi,
This is the first time i read about a technical reason for those
patches. I always thought it was to keep alive a source-open GPL'd
version of cdrecord which is able to burn DVD.
I don't understand what you like to say here
It is not easy to discuss the cdrecord-ProDVD topic in any
Hi,
Vendor_info: 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-4082B'
Revision : 'A201'
I am not sure about the firmware/laser pule former quality of this
Hitachi Goldstar drive. I recommend to repeat this test with
a drive from Pioneer, Plextor or NEC
30 minutes later
Hi,
I am not aware of computer DVD-ROM drives which refuse
to read successfully verified DVD+RW
Well, my DVD-ROM cannot read any of the DVD-R or DVD+RW disks that I
have tried.
That would be 1 point for the + team and 1 for the - team.
I use TDK and Verbatim media written with a
Hi,
You've merely heard an echo of quasi-technical rumor.
I repeated (my understanding of) the guts of what was said, I don't say
it's technically correct.
Please note that I rather reacted on Thomas' interpretation of the
statement/rumor you've passed on
He interpreted it as if there
, of course:
Curiosity, dark and stormy nights, the will not to give up
on the first serious obstacle, the pride to see it working, ...
Plus, there is the need to give scdbackup development a rest
before the upcoming next stable release. :))
What problem does it solve that cannot be solved
Hi,
This is the first time i read about a technical reason for those
patches.
You've merely heard an echo of quasi-technical rumor.
For me as an application programmer all talk about system,
firmware or hardware is rumor. One learns to live with that.
My -RWs leave me after a few
Hi,
So i have not much reason to try any DVD-patched cdrecords yet.
I actually wonder why they live forth.
I wondered too and questioned that, and got my head bitten off on the
dvdrtools list
Only good we are virtual entities here.
The blood spill would be immense if we met in real
Hi,
Bill Davidsen wrote:
Because growisofs doesn't do CD, cdrecord doesn't do DVD, and -ProDVD
isn't open source. I find it very nice to have a single tool to burn ISO
images, because then I can write the media type fitted to the data size
without needing multiple tools.
Volker
Hi,
I recently introduced a fifo into my growisofs script.
Now it is already obsolete. What a carreer. :))
For a talk I gave on introduction to pthreads I wrote a ring buffer
program with most of the options one could want.
Isn't there anybody in the world who did not make his own fifo
Hi Joerg,
Would there be volunteer testers for a united cdrecord
compatibility wrapper based on libburn for CD and
growisofs for DVD ?
The last time I checked libburn, it was a complete desater.
The first time where a project turned unmaintainable short
after it's creation.
It's not
Hi,
A FIFO allows you to survive a period with low input data rates.
If everything goes faster, you need to increase the size of the FIFO
proportional to the size improvements.
But if *everything* goes faster, why not that period
with low data rates too ?
It's the absolute speed that
Hi,
My suspicion is that this can be done by option
-force
It might be worth a try with the unpatched program.
His problems are just caused by broken DVD support in the DVD
patch applied by Debian.
My DVD needs get served well by original growisofs and
cdrecord-ProDVD.
So i have
Hi,
How come that the time granularity of the backup processing chain
does not get finer as the systems get faster ?
What do you understand by time granularity?
I see a fifo as a method to smoothen out peaks and gaps in a
input function and to bring the output nearer to the input
average.
Hi,
if ((flags F_FORCE) == 0)
- comexit(EX_BAD);
+;//comexit(EX_BAD);
You could achieve the same by causing flags
to have the F_FORCE bit set.
My suspicion is that this can be done by option
-force
It might be worth a try with the unpatched
Hi,
How come that the time granularity of the backup processing chain
does not get finer as the systems get faster ?
What effect did change the shape of our input functions ?
I think the main problem is that hard disk seek times have not
improved anywhere nearly as fast as the
Hi,
Joerg Schilling wrote:
Guess why I recommend to use more than 128MB for the star FIFO
in order to keep the tape streaming.
With current I/O speed, you need current RAM sizes for buffering.
Googling for contemporary speeds ... HP ... 36 MB/s DLT ... 80 MB/s LTO
... well, i'd need a new
Hi,
(The jump between 64 and 128 MB might be a bit coarse.)
My standpoint is that if you get into situation when you consider more
than 64MB, it's likely that bottleneck is abnormal
Or the user is an aberrated personality like me who
streams compressed archives on the fly. :))
and it's
Hi,
My standpoint is that if you get into situation when you consider more
than 64MB, it's likely that bottleneck is abnormal
Or the user is an aberrated personality like me who
streams compressed archives on the fly. :))
Keep in mind that ring buffer harmonizes *variations* in input
Hi,
i nearly gave up the hope to see more growisofs releases.
The release of version 6.0 is good news.
dvd+rw-tools 6.0 are available for download at usual location,
http://fy.chalmers.se/~appro/linux/DVD+RW/. In addition to bug fixes
[most notably for Pioneer units] this version features:
Hi,
this about a discrepancy between the man page and the behavior of cdrecord
when writing multiple data tracks.
After a track is done the padsize= value does not get reset to zero but
obviously to 30k. At least the messages of cdrecord say so.
I have no problem with that behavior and given the
Hi,
I have an NEC 3540A along with Ritek Ridata 8x DVD-R's.
If i burn a DVD iso in windows with nero I get true 8x speed.
When I burn in linux with growisofs, my speeds vary from 1.5x-4x
which is horrible. Is there no 8x support yet?
As far as i know growisofs leaves the speed setting as
Hi,
Thomas Klausner wrote:
On NetBSD-3.99.15/i386, with cdrtools-2.01.01a03, writing
an ordinary FUJI 1-4x CD-RW broke. The same command line,
drive, and medium works with cdrtools-2.01.
The message is
cdrecord: Trying to use ultra high speed+ medium on a writer which is
not
Hi,
/sbin/dump -y -b64 -0 -f - / | flyisofs mbc=2295104 fbc=35 \
| growisofs -speed=4 -Z /dev/hdd=/dev/zero
Not being familiar with flyisofs i think that your growisofs
is not fed via stdin but by an inexhaustible source of 0-bytes.
To pipe stdin to my pseudo
Hi,
It writes CD-Rs and DVD+RW disks properly but not DVD+
It get even worse with DVD-R 8x media
':-[ PERFORM OPC failed with SK=3h/ASC=73h/ACQ=03h]
I get that as final salute from my DVD-RW :
* formatting |:-[ PERFORM OPC failed with SK=3h/ASC=73h/ACQ=03h]:
Input/output error
Typically
Hi,
Helmut Jarausch wrote:
I've tried to search the archive and various FAQs but I more confused
than before.
This impression represents the current state of the art.
Expect any weird behavior of firmware and media.
DVD burner (LG GSA-4167B) [...] which media (format) should I use.
I
Hi,
Running cdrecord underneath a front-end, in automated scripts, it might
be MUCH easier to look at the exit code rather than parse its messages.
No, you can still set an error exit code,
when burnfree is turned on and
burnfree kicked it at least once, and throw that CD if you want.
But
Hi,
I wrote
But only if there is _another_ new option to enable/disable
that fake failure exit.
Matthias Andree wrote :
Using a separate exit code (and documenting exit codes in the first
place!!) would suffice.
Not really.
My project accomodates to original cdrecord from 1.6 to 2.01
Hi,
Using that, I read it with dd if=/dev/cdrom bds=2048 count=595536|md5sum
which gave the wrong answer, so I tried it with 595535 and also got the
wrong answer.
Then I fired up kcalc ... READ DVD STRUCTURE ... Legacy lead-out ...
... 26624 bytes, or 13 2048 byte blocks, is there a std
Hi,
Another approach would be to add some recognizable bytes as
an end mark to the payload data when writing to media.
And that would no doubt require growisofs to be modified in some way to
achive this.
A classical shell pipe is sufficient :
tag_adder image.iso | growisofs ... -Z
Hi,
K3B reports it has written 1160 of 1163 Mbytes each time, but doesn't
seem to have a problem with that.
I just ran growisofs from the cli, and it also gets exactly the same
bad md5sum, not reporting the final write. Here is the cli line end
of burn session reports:
builtin_dd:
Hi,
I didn't know where I have to report the problem. If this is not the
medium please show me the path.
I feel adressed properly. :)
Description of the problem: growisofs doesn't record to the speed
specified. The recorder supports 4x; the media supports 8x. Growisofs
states current
1 - 100 of 222 matches
Mail list logo
