Marek Pawinski wrote:
I picked this up, i don't know if it pertains to the issue:
Bad Md5sums? (maybe not)
Just burned a CD from an ISO image and the md5sum doesn't match?
The CD may be just fine... what you may be experiencing is padding
which alters the md5sum. Before throwing away the CD and
Marek Pawinski wrote:
I picked this up, i don't know if it pertains to the issue:
Bad Md5sums? (maybe not)
Just burned a CD from an ISO image and the md5sum doesn't match? The
CD may be just fine... what you may be experiencing is padding which
alters the md5sum. Before throwing away the CD and c
John Richard Smith wrote:
Miark wrote:
On Tue, 26 Oct 2004 10:18:17 +0100, John wrote:
ls -l
Divide the size of the ISO image file by 2048 to get the
number of sectors, and record that sum (=n, hereafter)
If it comes out to a decimal, do I round up?
It doesn't.
The sectors in question are t
Miark wrote:
On Tue, 26 Oct 2004 10:18:17 +0100, John wrote:
ls -l
Divide the size of the ISO image file by 2048 to get the
number of sectors, and record that sum (=n, hereafter)
If it comes out to a decimal, do I round up?
It doesn't.
The sectors in question are the number of sectors on t
On Tue, 26 Oct 2004 10:18:17 +0100, John wrote:
> ls -l
>
> Divide the size of the ISO image file by 2048 to get the
> number of sectors, and record that sum (=n, hereafter)
If it comes out to a decimal, do I round up?
> Then, making sure the CD you just burned isn't mounted:
Why not? The fo
Adolfo Bello wrote:
On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote:
Then, making sure the CD you just burned isn't mounted:
in terminal,
dd if=/dev/scd0 bs=2048 count=n | md5sum -
(note the " - " on the end, don't leave it off.
change the /dev/scd0 to whatever device setting your
Miark wrote:
On Tue, 26 Oct 2004 12:09:07 -0500, Tom wrote:
Yes, but in newer Mandrake versions the CD drives are seen
as dev=ATA:0,0,0 I use 0,0,0 for example only,
'cdrecord dev=ATA -scanbus' will return the actual numbers. The
ATA device (burner) is linked to the numbers. EG, on m
On Tue, 26 Oct 2004 12:09:07 -0500, Tom wrote:
> Yes, but in newer Mandrake versions the CD drives are seen
> as dev=ATA:0,0,0 I use 0,0,0 for example only,
> 'cdrecord dev=ATA -scanbus' will return the actual numbers. The
> ATA device (burner) is linked to the numbers. EG, on my syst
On Tue, 2004-10-26 at 20:23 +0100, John Richard Smith wrote:
> dev=ATA:1,0,0 is only for the 2.6 kernels
> where the devices are set up as ATA devices.
>
> dev=1,0,0 is for most 2.4 kernels
> where the device is scsi-emulated.
>
> I use much the same cdrecord Cl as you.
>
> Whilst I'm not agai
Adolfo Bello wrote:
I always use CLI to burn my CDs too.
cdrecord -v -eject speed=8 dev=1,0,0 -dao archivo.iso
What is new to me is the use of "dev=ATA:1,0,0". I'll try it in next
burn. Using Mandrake 10 fully updated.
Thanks,
Adolfo
dev=ATA:1,0,0 is only for the 2.6 kernels
where the devices
On Tue, 2004-10-26 at 12:09 -0500, Tom Brinkman wrote:
> On Tuesday 26 October 2004 04:56 am, Adolfo Bello wrote:
> > On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote:
> > > Then, making sure the CD you just burned isn't mounted:
> > >
> > > in terminal,
> > > dd if=/dev/scd0 bs=2048 cou
On Tue, 26 Oct 2004 05:56:29 -0400, Adolfo wrote:
> On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote:
> > Then, making sure the CD you just burned isn't mounted:
> >
> > in terminal,
> > dd if=/dev/scd0 bs=2048 count=n | md5sum -
> > (note the " - " on the end, don't leave it off.
>
On Tue, 26 Oct 2004 10:18:17 +0100, John wrote:
> OK, simple enough...
Simple? I'll have to try this after work when I have
a half-hour to kill ;-)
Miark
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
On Tuesday 26 October 2004 04:56 am, Adolfo Bello wrote:
> On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote:
> > Then, making sure the CD you just burned isn't mounted:
> >
> > in terminal,
> > dd if=/dev/scd0 bs=2048 count=n | md5sum -
> > (note the " - " on the end, don't leave it of
Miark wrote:
This is exactly what used to work for me. The only difference I
see is that with kernel 2.6 I'm no longer using scsi emulation.
so I'm checking /dev/hdc instead of /dev/scd0. I wonder if that
has anything to do with it.
Miark
Of course, the 2.6 kernels don't use scsi-emulation,
so
On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote:
> Then, making sure the CD you just burned isn't mounted:
>
> in terminal,
> dd if=/dev/scd0 bs=2048 count=n | md5sum -
> (note the " - " on the end, don't leave it off.
>
> change the /dev/scd0 to whatever device setting your
> drive
Miark wrote:
What do you do to verify discs?
Do you still have the iso file ?
Yes.
Miark
OK, simple enough.
First check iso image file md5sum,
you probably know how to do this anyway,but,
In a terminal,
cd enter
md5sum
check the return against the published md5sum.
then you n
On Mon, 25 Oct 2004 22:35:39 +0100, John wrote:
> Miark wrote:
> >
> >One other thing I considered: crappy media. And make no mistake,
> >I'm using Ritek--the crappiest, most god-awful media on planet.
> >But when I burned to a RW this morning, I had the same problem
> >(burning with K3b, with ver
Miark wrote:
One other thing I considered: crappy media. And make no mistake,
I'm using Ritek--the crappiest, most god-awful media on planet.
But when I burned to a RW this morning, I had the same problem
(burning with K3b, with verification checked).
If your burner is modern, 8x is not particula
On Mon, 25 Oct 2004 18:26:35 +0200, Thereidos wrote:
> On Mon, 25 Oct 2004 12:07:32 -0400
> Miark <[EMAIL PROTECTED]> wrote:
>
> > When I burn a CD in MDK 10.0 from the commandline or with
> > K3b, then compare the md5sums of the iso file and /dev/hdc,
> > they are_always_ different, even if the
On Mon, 25 Oct 2004 12:01:42 -0500, Marc wrote:
> On Monday 25 October 2004 11:54 am, John Richard Smith wrote:
> > Miark wrote:
> > >When I burn a CD in MDK 10.0 from the commandline or with K3b,
> > >then compare the md5sums of the iso file and /dev/hdc, they are
> > >_always_ different, even if
On Mon, 25 Oct 2004 17:54:15 +0100, John wrote:
> >When I burn a CD in MDK 10.0 from the commandline or with K3b,
> >then compare the md5sums of the iso file and /dev/hdc, they are
> >_always_ different, even if the CD works fine. Is there something
> >weird with 10.0, or is this a subtle sign of
Marc wrote:
On Monday 25 October 2004 11:54 am, John Richard Smith wrote:
Miark wrote:
When I burn a CD in MDK 10.0 from the commandline or with K3b,
then compare the md5sums of the iso file and /dev/hdc, they are
_always_ different, even if the CD works fine. Is there something
weird with
On Monday 25 October 2004 11:54 am, John Richard Smith wrote:
> Miark wrote:
> >When I burn a CD in MDK 10.0 from the commandline or with K3b,
> >then compare the md5sums of the iso file and /dev/hdc, they are
> >_always_ different, even if the CD works fine. Is there something
> >weird with 10.0,
Miark wrote:
When I burn a CD in MDK 10.0 from the commandline or with K3b,
then compare the md5sums of the iso file and /dev/hdc, they are
_always_ different, even if the CD works fine. Is there something
weird with 10.0, or is this a subtle sign of burner problems to
come, or what?
Miark
Not a
On Mon, 25 Oct 2004 12:07:32 -0400
Miark <[EMAIL PROTECTED]> wrote:
> When I burn a CD in MDK 10.0 from the commandline or with K3b,
> then compare the md5sums of the iso file and /dev/hdc, they are
> _always_ different, even if the CD works fine. Is there something
> weird with 10.0, or is this a
When I burn a CD in MDK 10.0 from the commandline or with K3b,
then compare the md5sums of the iso file and /dev/hdc, they are
_always_ different, even if the CD works fine. Is there something
weird with 10.0, or is this a subtle sign of burner problems to
come, or what?
Miark
___
27 matches
Mail list logo
