Finally a Patch that works!
http://www.menaro.info/ss/
Penis Growth Extreme
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> On many servers now I use DVD+RW media for backup purposes just like the
> old tape drives, sequential in format using the tar command and written
> using sdd with 32k blocks.
It is probable that the read-ehad error doesn't show on DVD+RW if the
area just following the last block which you wan
On Friday 13 May 2005 20:07, James Finnall wrote:
> On Friday 13 May 2005 14:34, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > > I would have expected that what was true of CDs would be true with
> > > DVDs.
> >
> > So let us assume for now that DVDs are still safe
> > in that aspect. At least no real
On Friday 13 May 2005 14:34, [EMAIL PROTECTED] wrote:
> Hi,
>
> > I would have expected that what was true of CDs would be true with
> > DVDs.
>
> So let us assume for now that DVDs are still safe
> in that aspect. At least no real problems have
> been reported. (Nevertheless i pad 300 kB)
>
If y
> > I would have expected that what was true of CDs would be true with
> > DVDs.
>
> So let us assume for now that DVDs are still safe
> in that aspect.
Oh n way! I have had the end-of-recording read errors on DVDs as
well, though can't quite remember exactly when it was and therefore
which k
Hi,
>> - or to compare the data image on DVD with a checksum
> > which was made when that image was written to DVD.
>
> First time heard about this method. How to actually obtain the DVD checksum?
If you got the image stored on disk you may use
program md5sum.
If you generate and burn the ima
Thanks for the comprehensive explanation,
> Hi,
>
> > what is the indicator that the burn process was only 95% completed?
>
> The only reliable indicator seems to be checkreading
> by all drives which shall be able to read the DVD.
>
> This would mean either
>
> - to compare each file on the DVD w
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 w
Hi,
> I would have expected that what was true of CDs would be true with
> DVDs.
So let us assume for now that DVDs are still safe
in that aspect. At least no real problems have
been reported. (Nevertheless i pad 300 kB)
> My (likely outdated) experience passing a CD-sized chunk of bytes over
You're Invited
Thanks to a private nomination, there are potentially three deals that will be
offered to you.
Notice - past credit history is NOT a factor for this promotion as long as we
recieve word from you within 36 hours.
In accordance with our terms please verify your information on
| From: [EMAIL PROTECTED]
| Are there really such errors with DVD now ?
| With CD there is an embarrassing tradition for that.
I'm not sure that it happens with a DVD. I know it happens with CDs.
I would have expected that what was true of CDs would be true with
DVDs.
My one experiment (burning
| From: Volker Kuhlmann <[EMAIL PROTECTED]>
| Completely forget all your this-year's redhat references. This problem
| existed at least with kernels 2.2 and 2.4, and is probably as old as
| Linux (see references to it for kernels 1.3 in older mkisofs/cdrecord
| source around the -pad option). In 2
> 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]
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
Hi,
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:20")
I did not have to get a new cdrecord-ProDVD binary.
(still
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 r
Hi,
> what is the indicator that the burn process was only 95% completed?
The only reliable indicator seems to be checkreading
by all drives which shall be able to read the DVD.
This would mean either
- to compare each file on the DVD with its original
on hard disk (if the files on disk did n
> I used verbose option and clearly see that the burn process was completed and
> the session was closed.
> what is the indicator that the burn process was only 95% completed?
The burn was 100% completed at 95% quality. ;)
That's putting it colloquially of course. The burner is maladjusted to
th
>>I've successfully burnt data (4 GB, around
1 files) to a DVD. >>I saw that all the files have been burnt
to DVD with exact size.>>However, I couldn't read some of the files
(corrupted ?) and this happened randomly (i.e. I burnt another ten DVDs with the
same contents and the corruption
19 matches
Mail list logo
