Hi,
does anybody know howto write more than 1 session onto a DVD with
cdrecord-ProDVD.
(I know it's possible with growisofs)
Many thanks for a hint
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
--
To UNSUBSCRIBE, email to [EMAIL
Hi Jörg,
This mail is mostly for you as you are the only one who can solve the
problem.
The most recent cdrecord-ProDVD version is an alpha binary and is more
than one year old. Hence it has expired now! That this is the case can
be seen from berlios ftp server listing:
-rwxrwxr-x 1
there is a new key up now.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
will wrote:
there is a new key up now.
Thanks for the notification.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
it's 2005 Oct 22 21:27:16 and my copy of cdrecord-ProDVD went
on strike (Alarm clock).
I read in ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README :
As I am not sure if people will follow my licensing rules, so these
keys are time limited and will expire on 2005 Oct 22 18:53:20
I will continue
Hi all,
after numerous trials and studying the READMEs and mailing-lists
concerning cdrecord-prodvd I haven't succeeded burning my DVDs with
cdrecord-prodvd . So I switched to growisofs. growisofs is
relatively simple and has not such a rich flavour of features like
cdrecord-prodvd has
Hi all,
I use a notebook running Debian-woody (kernel 2.4.26). Attached to it
via USB is an external DVD writer (LG, GSA-5163D) . DVD+RWs and CDs can
be mounted and read, but writing doesn't work. The software I use for
writing is the binary cdrecord-prodvd-2.01.01-i686-pc-linux-gnu
Hello Bill
Sorry for the late reply.
Bill Davidsen [EMAIL PROTECTED] writes:
On the chance that I was unclear with my question:
mount -r /dev/hdc /mnt/cdrom
cd /mnt/cdrom
find . -type f -print0 | xargs -0 md5sum | grep FAIL
obviously modified to fit you device and mountpoint names.
Bill Davidsen [EMAIL PROTECTED] writes:
The only thing which comes to mind on that is that the directory
structure might still be in memory. Seems unlikely, but there's no
reason why it should work only until eject. If you force a read of all
files, like an md5sum or such, are they all
Dominique Dumont wrote:
Bill Davidsen [EMAIL PROTECTED] writes:
The only thing which comes to mind on that is that the directory
structure might still be in memory. Seems unlikely, but there's no
reason why it should work only until eject. If you force a read of all
files, like
The only thing which comes to mind on that is that the directory
structure might still be in memory. Seems unlikely, but there's no
reason why it should work only until eject. If you force a read of all
files, like an md5sum or such, are they all readable?
The other thing which comes to
One of my coworkers recently noticed the infamous Alarm clock error
from cdrecord-ProDVD on our HP-UX workstations. She's been using
cdrecord-ProDVD 2.01a27 which is the newest version available on the
berlios FTP site for HP-UX. Apparently, this alpha release is expired,
and there is no 2.01
On Fri, May 13, 2005 at 04:17:35PM +0200, [EMAIL PROTECTED] wrote:
i resolved my alarm clock by downloading only
the current wrapper script
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/cdrecord-wrapper.sh
which obviously contains the new license key.
(Saying: Key Expires --- 2005 Oct 22 18:53
The alpha releases have built-in expiration dates
Oops. Then it's about time i get the newer 2.01 binary.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Volker Kuhlmann [EMAIL PROTECTED] writes:
This sounds like an incompatability between your burner and your media.
No software will fix that, other than a firmware fix in the burner.
You're probably right. I've upgraded the firmware to no avail.
The only way to be sure is to try my burner with
Dominique Dumont [EMAIL PROTECTED] writes:
TOC Type: 1 = CD-ROM
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
Following Maik Zumstrull's advice, I've setup ide-scsi on Linux 2.6
for cdrecord-prodvd.
Unfortunately, I still cannot write to dvd due to the following error:
cdrecord-pro-dvd: Input
Note that growisofs is able to write the dvd, but I've a lot of
trouble to read them afterwards.
This sounds like an incompatability between your burner and your media.
No software will fix that, other than a firmware fix in the burner.
Switch to different media which your burner can handle.
Dominique Dumont [EMAIL PROTECTED] writes:
In dummy mode everything looks fine. But, dvd-record failed to write
in readl mode: I ended with a mountable dvd with no data ?!?!?!
I have to add a small correction: cdrecord has written the beginning
of the iso image: I have the directory content
.iso
Cdrecord-ProDVD-Clone 2.01b31 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg
Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for:
private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI
, Alexander Noe' wrote:
Rodney Gordon II wrote:
I recently picked up a NEC ND-3520A and I am having speed problems with
this drive under linux. A quick just to make sure test in WinXP shows
that these errors are indeed specific to cdrecord-prodvd and growisofs.
NEC 35x0 drives report crap
Ismail Donmez wrote:
mode_sense page 2A vs get_performance
Wonder if Joerg and/or Andy will comment on this? Like using get_performance
instead of mode_sense would work all devices? Does it have any drawbacks?
Maybe a link to RTFM? :)
Plextor PX-712, Fw 1.06
- reports broken lists on *both*
Rodney Gordon II wrote:
I recently picked up a NEC ND-3520A and I am having speed problems with this
drive under linux. A quick just to make sure test in WinXP shows that these
errors are indeed specific to cdrecord-prodvd and growisofs.
NEC 35x0 drives report crap answers on mode_sense page 2A
On Saturday 19 March 2005 07:17 am, Alexander Noe' wrote:
Rodney Gordon II wrote:
I recently picked up a NEC ND-3520A and I am having speed problems with
this drive under linux. A quick just to make sure test in WinXP shows
that these errors are indeed specific to cdrecord-prodvd
Title: Re: cdrecord-prodvd don't work with BTC 1004
I'm having the same problem. The os is redhat linux 9. I was using version cdrecord-prodvd-2.01a27-i686-pc-linux-gnu until the binary expired.
I tried downloading cdrecord-prodvd-2.01.01-i686-pc-linux-gnu (and also cdrecord-prodvd-2.01b31
Hi all,
I recently picked up a NEC ND-3520A and I am having speed problems with this
drive under linux. A quick just to make sure test in WinXP shows that these
errors are indeed specific to cdrecord-prodvd and growisofs.
The media I am using MID is PRODISC/R03 and I can burn this media
philips that is certified for 8x), but
cdrecord-ProDVD always writes the DVDs at 6x speed.
Here is the output of the program; tell me if I can supply additional
debugging data.
newdeal:/mnt# cdrecord-dvd -dev=/dev/hdc -speed=4 -dao -data guida.iso
Cdrecord-ProDVD-Clone 2.01b31 (i686-pc-linux-gnu
Hi,
I have a NEC 3500 Dvd Writer.
I have problems with the recording speed.
I tried two different brand of dvd-r (one from princo that is certified
for 4x recording, and one from philips that is certified for 8x), but
cdrecord-ProDVD always writes the DVDs at 6x speed.
Here is the output
Tomasz B Mloduchowski wrote:
Hi all,
I noticed that -tao mode is no longer working on my hardware since
cdrecord-prodvd-2.01b31-i686-pc-linux-gnu
Everything worked fine with a previous version. Here is my system:
P3 933MHz running gentoo (current).
Linux bytecruncher 2.6.8-gentoo-r10 #1 Wed Oct 20
Hi all,
I noticed that -tao mode is no longer working on my hardware since
cdrecord-prodvd-2.01b31-i686-pc-linux-gnu
Everything worked fine with a previous version. Here is my system:
P3 933MHz running gentoo (current).
Linux bytecruncher 2.6.8-gentoo-r10 #1 Wed Oct 20 16:42:31 EDT 2004 i686
I'm getting the infamous Alarm clock error during the countdown
when trying to burn with cdrecord-ProDVD. I've got the key from
the README file (ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README)
which was updated on 2004-01-26... and it's only May. Is this key
expired already?
Once again, what's
On Mon, May 03, 2004 at 09:23:23AM -0600, Ashish Rangole wrote:
I wonder if anybody has ever had any success in getting
one from Joerg. Please let me know if anybody has.
A colleague of mine has also attempted to get permanent keys from Joerg,
without success. He's with a commercial entity
Once again, what's the procedure for getting a *real* (non-expiring)
key? We'd be willing to buy one for our organization if necessary.
In order to get a permanent key one has to request Joerg Schilling,
the author. I would also like to have a key for cdrecord-ProDVD for
Linux system. I
to get a permanent key one has to request
Joerg Schilling,
the author. I would also like to have a key for
cdrecord-ProDVD for
Linux system. I wonder if anybody has ever had any
success in getting
one from Joerg. Please let me know if anybody has.
Joerg, I wonder if you can respond
From [EMAIL PROTECTED] Sun Apr 11 18:08:09 2004
Can one criticize dvd+rw-tools for so to say sweeping the bug under the
carpet, which might have indirectly complicated life for other
applications and their developers? Well, one could *if* it was done
silently. But it wasn't. Thorough problem
From: Julien Gabel [EMAIL PROTECTED]
Ok. The media I bought are as follow:
- TDK DVD-RW single-sided Data/Video 4.7GB 1-2x;
- TDK DVD-R single-sided Data/Video 4.7GB 1-4x.
Is there anything wrong whith these types of media? Advices?
The medium quality should be OK. So it should become
From: Geoffrey [EMAIL PROTECTED]
Your message is not helpful at all! Why did you send it?
Because you are harsh to everyone, whether they are new to the list, old
to the list, have any expertise or none. The purpose of my posting was
to urge the poster to continue to pursue his problems,
Joerg Schilling wrote:
From: Geoffrey [EMAIL PROTECTED]
Your message is not helpful at all! Why did you send it?
Because you are harsh to everyone, whether they are new to the list, old
to the list, have any expertise or none. The purpose of my posting was
to urge the poster to continue to
On Tue, Apr 13, 2004 at 01:24:51PM -0400, Geoffrey wrote:
That being said, I'll not take up any more of your precious time with
further responses to this thread.
Would people _please_ stop picking on Joerg.
It should be quite obvious that if
a) people don't read documentation, or
b)
most likely means that your media is poorly supported by your firmware.
Then 3/11/05 L-EC UNCORRECTABLE ERROR doesn't make much sense
either... What media is it anyway (see dvd+rw-mediainfo output for Media
ID)? Poor media support manifests itself in most bizarre ways. There
were reports that
Can one criticize dvd+rw-tools for so to say sweeping the bug under the
carpet, which might have indirectly complicated life for other
applications and their developers? Well, one could *if* it was done
silently. But it wasn't. Thorough problem analysis was presented to the
public on a FreeBSD
From: Andy Polyakov [EMAIL PROTECTED]
If you did know about the bug before I did, I may well critisize you:
Why didn't you send a bug report
I'm ready to accept criticism as soon as somebody can point out what was
it in the referred post, which discredits it as as a bug report? Note
that
Ok. The media I bought are as follow:
- TDK DVD-RW single-sided Data/Video 4.7GB 1-2x;
- TDK DVD-R single-sided Data/Video 4.7GB 1-4x.
Is there anything wrong whith these types of media? Advices?
The medium quality should be OK. So it should become usable by cdrecord
after you did run
From [EMAIL PROTECTED] Sun Apr 11 18:08:09 2004
Can one criticize dvd+rw-tools for so to say sweeping the bug under the
carpet, which might have indirectly complicated life for other
applications and their developers? Well, one could *if* it was done
silently. But it wasn't. Thorough problem
From: Julien Gabel [EMAIL PROTECTED]
Ok. The media I bought are as follow:
- TDK DVD-RW single-sided Data/Video 4.7GB 1-2x;
- TDK DVD-R single-sided Data/Video 4.7GB 1-4x.
Is there anything wrong whith these types of media? Advices?
The medium quality should be OK. So it should become
From: Geoffrey [EMAIL PROTECTED]
Your message is not helpful at all! Why did you send it?
Because you are harsh to everyone, whether they are new to the list, old
to the list, have any expertise or none. The purpose of my posting was
to urge the poster to continue to pursue his problems,
Joerg Schilling wrote:
From: Geoffrey [EMAIL PROTECTED]
Your message is not helpful at all! Why did you send it?
Because you are harsh to everyone, whether they are new to the list, old
to the list, have any expertise or none. The purpose of my posting was
to urge the poster to continue to
On Tue, Apr 13, 2004 at 01:24:51PM -0400, Geoffrey wrote:
That being said, I'll not take up any more of your precious time with
further responses to this thread.
Would people _please_ stop picking on Joerg.
It should be quite obvious that if
a) people don't read documentation, or
b)
most likely means that your media is poorly supported by your firmware.
Then 3/11/05 L-EC UNCORRECTABLE ERROR doesn't make much sense
either... What media is it anyway (see dvd+rw-mediainfo output for Media
ID)? Poor media support manifests itself in most bizarre ways. There
were reports that
Can one criticize dvd+rw-tools for so to say sweeping the bug under the
carpet, which might have indirectly complicated life for other
applications and their developers? Well, one could *if* it was done
silently. But it wasn't. Thorough problem analysis was presented to the
public on a FreeBSD
Ok. The media I bought are as follow:
- TDK DVD-RW single-sided Data/Video 4.7GB 1-2x;
- TDK DVD-R single-sided Data/Video 4.7GB 1-4x.
Is there anything wrong whith these types of media? Advices?
The medium quality should be OK. So it should become usable by cdrecord
after you did run
_not_possible_ to write (or rewrite or blank etc.) a DVD-RW.
Here is the exact version of software I try to use:
# portversion -v | grep -i dvd+rw-tools
dvd+rw-tools-5.19.4.9.7
# cdrecord -version
Cdrecord 2.00.3 (i386-unknown-freebsd5.2.1) Copyright (C) 1995-2002 Jörg
Schilling
# cdrecord-prodvd
Schilling
# cdrecord-prodvd -version
Cdrecord-ProDVD-Clone 2.01a24 (i386-unknown-freebsd5.2) Copyright (C)
1995-2004 Jörg Schilling
# dvdrtools -version
It does not seem that you really used cdrecord-ProDVD!
If you don't use it and give error messages, it is hard to help
It is absolutely
to write (or rewrite or blank etc.) a DVD-RW.
Here is the exact version of software I try to use:
# portversion -v | grep -i dvd+rw-tools
dvd+rw-tools-5.19.4.9.7
# cdrecord -version
Cdrecord 2.00.3 (i386-unknown-freebsd5.2.1) Copyright (C) 1995-2002 Jörg
Schilling
# cdrecord-prodvd -version
From: Julien Gabel [EMAIL PROTECTED]
It does not seem that you really used cdrecord-ProDVD!
If you don't use it and give error messages, it is hard to help
Ok, sorry for the _bad_ information. Here is what I get if I try to use
cdrecord-ProDVD (obtained from ftp://ftp.berlios.de/pub/cdrecord
problem here... Are you?
# ./cdrecord-wrapper.sh -v -blank=all dev=3,0,0
Cdrecord-ProDVD-Clone 2.01a24 (i386-unknown-freebsd5.2) Copyright (C)
1995-2004 Jörg Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for:
private/research/educational_non
V ne, 11. 04. 2004 v 13:47, Joerg Schilling pe:
If you need information about FreeBSD kernel bugs, ask the
FreeBSD kernel team!
You definitely need to replace your kernel with a working one!
There was a deficiency in kernel that it does not provided sense codes
automatically, as required by
version of cdrecord-ProDVD which match the OS version with wich
I get a problem, I just ask what is wrong. Maybe providing the different
information/configuration used to buid this particular program may help
me to found what I misunderstood?
Thanks a lot for your replies,
--
-jpeg
provide a
binary version of cdrecord-ProDVD which match the OS version with wich
I get a problem, I just ask what is wrong. Maybe providing the different
information/configuration used to buid this particular program may help
me to found what I misunderstood?
Thanks a lot for your replies,
If you're
mode detected.
* blanking .:-[ READ TRACK INFORMATION failed with SK=3h/ASC=11h/ACQ=05h]
:Input/output error
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
The help here
From: Geoffrey [EMAIL PROTECTED]
If you're new to the list, you'll find that Joerg is quite vocal
regarding OS's that are not his favorite... Unfortunately, inspite of
I don't have favorite OS, but I don't like kernel teams that piss at you
which is only the case for Linux!
FreeBSD
From: Julien Gabel [EMAIL PROTECTED]
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
The help here is not easy. I'd suggest you to upgrade to -CURRENT, if
you're ready to face
.:-[ READ TRACK INFORMATION failed with SK=3h/ASC=11h/ACQ=05h]
:Input/output error
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
I'm not absolutely sure but I guess only
If you're new to the list, you'll find that Joerg is quite vocal
regarding OS's that are not his favorite... Unfortunately, inspite of
I don't have favorite OS, but I don't like kernel teams that piss at you
which is only the case for Linux!
FreeBSD developers usually take care about
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
The help here is not easy. I'd suggest you to upgrade to -CURRENT, if
you're ready to face all the possible problem of running
descriptor.
* 4.7GB DVD-RW media in Sequential mode detected.
* blanking .:-[ READ TRACK INFORMATION failed with
SK=3h/ASC=11h/ACQ=05h]
:Input/output error
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong
From: Julien Gabel [EMAIL PROTECTED]
Why do you like to stay with a broken OS and as a result not being able
to use youe hardware?
Because this is a _release_, and running the -CURRENT (CVS) version
seems to me more dangerous than staying with this version. Note that
the release may be buggy
TEAC DV-W22E R.0A
But it seems _not_possible_ to write (or rewrite or blank etc.) a DVD-RW.
dvd+rw-tools-5.19.4.9.7
1/ For example, when I try to blank a DVD-RW in sequential mode, I get:
# dvd+rw-format -blank=full /dev/cd0
* DVD±RW format utility by [EMAIL PROTECTED], version 4.9.
:-(
dvd+rw-tools were teached to obtain sense information from kernel
manually, so they fully work on 5.2.1. cdrecord relies on working
autosense and thus don't work on 5.2.1.
I would call this behavior of dvd+rw-tools a bug as the CAM standard
requires auto-sense to work. If FreeBSD is fixed, the
Joerg Schilling wrote:
Your message is not helpful at all! Why did you send it?
Because you are harsh to everyone, whether they are new to the list, old
to the list, have any expertise or none. The purpose of my posting was
to urge the poster to continue to pursue his problems, inspite of the
_not_possible_ to write (or rewrite or blank etc.) a DVD-RW.
Here is the exact version of software I try to use:
# portversion -v | grep -i dvd+rw-tools
dvd+rw-tools-5.19.4.9.7
# cdrecord -version
Cdrecord 2.00.3 (i386-unknown-freebsd5.2.1) Copyright (C) 1995-2002 Jörg
Schilling
# cdrecord-prodvd
Schilling
# cdrecord-prodvd -version
Cdrecord-ProDVD-Clone 2.01a24 (i386-unknown-freebsd5.2) Copyright (C)
1995-2004 Jörg Schilling
# dvdrtools -version
It does not seem that you really used cdrecord-ProDVD!
If you don't use it and give error messages, it is hard to help
It is absolutely
to write (or rewrite or blank etc.) a DVD-RW.
Here is the exact version of software I try to use:
# portversion -v | grep -i dvd+rw-tools
dvd+rw-tools-5.19.4.9.7
# cdrecord -version
Cdrecord 2.00.3 (i386-unknown-freebsd5.2.1) Copyright (C) 1995-2002 Jörg
Schilling
# cdrecord-prodvd -version
From: Julien Gabel [EMAIL PROTECTED]
It does not seem that you really used cdrecord-ProDVD!
If you don't use it and give error messages, it is hard to help
Ok, sorry for the _bad_ information. Here is what I get if I try to use
cdrecord-ProDVD (obtained from ftp://ftp.berlios.de/pub/cdrecord
problem here... Are you?
# ./cdrecord-wrapper.sh -v -blank=all dev=3,0,0
Cdrecord-ProDVD-Clone 2.01a24 (i386-unknown-freebsd5.2) Copyright (C)
1995-2004 Jörg Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for:
private/research/educational_non
If you need information about FreeBSD kernel bugs, ask the
FreeBSD kernel team!
You definitely need to replace your kernel with a working one!
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
V ne, 11. 04. 2004 v 13:47, Joerg Schilling pe:
If you need information about FreeBSD kernel bugs, ask the
FreeBSD kernel team!
You definitely need to replace your kernel with a working one!
There was a deficiency in kernel that it does not provided sense codes
automatically, as required by
version of cdrecord-ProDVD which match the OS version with wich
I get a problem, I just ask what is wrong. Maybe providing the different
information/configuration used to buid this particular program may help
me to found what I misunderstood?
Thanks a lot for your replies,
--
-jpeg.
From: Pav Lucistnik [EMAIL PROTECTED]
If you need information about FreeBSD kernel bugs, ask the
FreeBSD kernel team!
=20
You definitely need to replace your kernel with a working one!
There was a deficiency in kernel that it does not provided sense codes
automatically, as required by
provide a
binary version of cdrecord-ProDVD which match the OS version with wich
I get a problem, I just ask what is wrong. Maybe providing the different
information/configuration used to buid this particular program may help
me to found what I misunderstood?
Thanks a lot for your replies,
If you're new
From: Geoffrey [EMAIL PROTECTED]
If you're new to the list, you'll find that Joerg is quite vocal
regarding OS's that are not his favorite... Unfortunately, inspite of
I don't have favorite OS, but I don't like kernel teams that piss at you
which is only the case for Linux!
FreeBSD
From: Julien Gabel [EMAIL PROTECTED]
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
The help here is not easy. I'd suggest you to upgrade to -CURRENT, if
you're ready to face
If you're new to the list, you'll find that Joerg is quite vocal
regarding OS's that are not his favorite... Unfortunately, inspite of
I don't have favorite OS, but I don't like kernel teams that piss at you
which is only the case for Linux!
FreeBSD developers usually take care about
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
The help here is not easy. I'd suggest you to upgrade to -CURRENT, if
you're ready to face all the possible problem of running
descriptor.
* 4.7GB DVD-RW media in Sequential mode detected.
* blanking .:-[ READ TRACK INFORMATION failed with
SK=3h/ASC=11h/ACQ=05h]
:Input/output error
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong
V ne, 11. 04. 2004 v 15:40, Julien Gabel pe:
Because this is related to a bug, is it not possible to integrate a
patch for this in the security advisories and other critical fixes
branch for RELENG_5_2?
No. This branch is now closed for anything except fixes of security
flaws.
--
Pav
From: Julien Gabel [EMAIL PROTECTED]
Why do you like to stay with a broken OS and as a result not being able
to use youe hardware?
Because this is a _release_, and running the -CURRENT (CVS) version
seems to me more dangerous than staying with this version. Note that
the release may be buggy
TEAC DV-W22E R.0A
But it seems _not_possible_ to write (or rewrite or blank etc.) a DVD-RW.
dvd+rw-tools-5.19.4.9.7
1/ For example, when I try to blank a DVD-RW in sequential mode, I get:
# dvd+rw-format -blank=full /dev/cd0
* DVD±RW format utility by [EMAIL PROTECTED], version 4.9.
:-( failed
If I can understand the problem relating to the internal bug with the
FreeBSD kernel (and not using cdrecord-proDVD), what may be wrong here?
Am I missing something?
I'm not absolutely sure but I guess only growisofs accounts for the
kernel deficiency and not dvd+rw-format. Andy?
*All* dvd+rw
dvd+rw-tools were teached to obtain sense information from kernel
manually, so they fully work on 5.2.1. cdrecord relies on working
autosense and thus don't work on 5.2.1.
I would call this behavior of dvd+rw-tools a bug as the CAM standard
requires auto-sense to work. If FreeBSD is fixed, the
Because the three software I try seems not working, I tend to think that
this particular writer is not (yet?) supported.
Is there something I can do in order to make it working?
The fact that you see failed to locate Quick format descriptor alone
most likely means that your media is poorly
Joerg Schilling wrote:
Your message is not helpful at all! Why did you send it?
Because you are harsh to everyone, whether they are new to the list, old
to the list, have any expertise or none. The purpose of my posting was
to urge the poster to continue to pursue his problems, inspite of the
Why do you like to stay with a broken OS and as a result not being
able to use youe hardware?
Because this is a _release_, and running the -CURRENT (CVS) version
seems to me more dangerous than staying with this version. Note that
the release may be buggy for some part (as for the point
Hello,
sorry for the missing description and the HTML mail (Lotus Notes ;-) ).
I had:
$ ./cdrecord-wrapper.sh dev=0,0,0 -driveropts=help -checkdrive
Cdrecord-ProDVD-Clone 2.01a27 ??? (i686-pc-linux-gnu) Copyright (C) 1995-2003
Jörg Schilling
:
:
Device type: Removable CD-ROM
Old-Return-Path: [EMAIL PROTECTED]
Hello,
does this problem perhaps apply to the LiteOn 811S, too?
If you don't write a description of your problem, you should not expect help.
Joachim WERNER
Wiesbaden
Germany
--=_alternative 00359DE4C1256E5A_=
Content-Type: text/html; charset=us-ascii
Hello,
does this problem perhaps apply to the LiteOn 811S, too?
Best regards,
Joachim WERNER
Wiesbaden
Germany
Old-Return-Path: [EMAIL PROTECTED]
Hello,
does this problem perhaps apply to the LiteOn 811S, too?
If you don't write a description of your problem, you should not expect
help.
Joachim WERNER
Wiesbaden
Germany
--=_alternative 00359DE4C1256E5A_=
Content-Type: text/html; charset=us-ascii
From: Marcello V. Mansueto [EMAIL PROTECTED]
Either broken firmware or this medium has already been written to.
The media was blank.
In which way the firmware is broken? Can you provide me more
information? I want to contact a BTC employer to have some help, but
Linux is not officially
On Tue, 2 Mar 2004 13:13:42 +0100 (CET)
Joerg Schilling [EMAIL PROTECTED] wrote:
cdrecord uses the official write method for DVD-R. This includes
first sending a reserve track/zone command,
If this does not work for a emty medium, the drive seems to be broken.
Ok, thank you very much!
--
From: Marcello V. Mansueto [EMAIL PROTECTED]
Either broken firmware or this medium has already been written to.
The media was blank.
In which way the firmware is broken? Can you provide me more
information? I want to contact a BTC employer to have some help, but
Linux is not officially
On Tue, 2 Mar 2004 13:13:42 +0100 (CET)
Joerg Schilling [EMAIL PROTECTED] wrote:
cdrecord uses the official write method for DVD-R. This includes
first sending a reserve track/zone command,
If this does not work for a emty medium, the drive seems to be broken.
Ok, thank you very much!
--
1 - 100 of 227 matches
Mail list logo
