Recovering data from duff CDROM ?
Mike Jones
I burned a CDROM a short while back, and now can't get the damn thing to
mount (even though it would have been checked as OK prior to storage). As
its got data on it that is no longer available from source, I'm wondering
if anybody has any favorite tricks they've used to force a mount.
Its a cheapo Memorex thing from some supermarket, and the data was
originally on an ext2 file system. The data is a collection of MP3
lectures, and was burned as data (not as an audioCD) to this CDROM using
Brasero on a Zenwalk-5.2 OS.
I've tried the usual "auto" and "ext2" mount options, and the "-s" sloppy
mount flag, but the best I can manage is a lot of disk spinning, followed
by a report that the resource is read only (its not) and a mount screen
report about "No such file or directory" available.
Just to be sure I'd actually managed a burn in the first place, I dropped
the disk into a burn process in XFburn (the app I'm currently using on
Slackware) and, as expected, got a report that the CDROM disk was full.
There is no visible evidence of damage on the disk itself. Its shiney new.
I'm open to suggestions about now. Clues anyone?
--
*===( http://www.400monkeys.com/God/
*===( http://principiadiscordia.com/
*===( http://www.slackware.com/
philo
try it on another machine
bb
The filesystem on your cdrom is not ext2, it's probably iso9660.
Try to read from the cdrom device, with dd or mk5sum and see if you
get errors.
There is a tool named ddrescue that can continue to read even if you get
block errors, and if you save it to a file, and once you have the file,
try to play it with mplayer to see if there is any hope at all to get the
mp3 files back.
/bb
Bit Twister
>
>
> I burned a CDROM a short while back, and now can't get the damn thing to
> mount (even though it would have been checked as OK prior to storage). As
> its got data on it that is no longer available from source, I'm wondering
> if anybody has any favorite tricks they've used to force a mount.
Just for fun, try
mount -t auto /dev/xxxx /some_mount_point_here
Mike Jones
Done that already.
Mike Jones
Done that already, and 'mount -s -t auto /dev/xxxx /some_mount_point'
Pascal Hambourg
bb a ï¿œcrit :
>
> There is a tool named ddrescue that can continue to read even if you get
> block errors, and if you save it to a file, and once you have the file,
> try to play it with mplayer to see if there is any hope at all to get the
> mp3 files back.
Will mplayer be happy to be fed with a filesystem image ?
If not, you can try to recover files from the filesystem image with
photorec, which is part of the testdisk package.
Mike Jones
> Hello,
>
> bb a écrit :
These look useful, but first I need to get the dvd drive to physically
read something. ATM its just spins a while, then bombs out with a "No
such file or directory" error.
I'll play around with ddrescue, but I don't thing it'll do much until I
can figure out how to read /something/ on the duff disk.
Cheers.
Mike Jones
> Responding to Pascal Hambourg:
>
>> Hello,
>>
>> bb a écrit :
>>>
>>> There is a tool named ddrescue that can continue to read even if you
>>> get block errors, and if you save it to a file, and once you have the
>>> file, try to play it with mplayer to see if there is any hope at all
>>> to get the mp3 files back.
>>
>> Will mplayer be happy to be fed with a filesystem image ? If not, you
>> can try to recover files from the filesystem image with photorec, which
>> is part of the testdisk package.
>
>
> These look useful, but first I need to get the dvd drive to physically
> read something. ATM its just spins a while, then bombs out with a "No
> such file or directory" error.
>
> I'll play around with ddrescue, but I don't thing it'll do much until I
> can figure out how to read /something/ on the duff disk.
>
> Cheers.
Update: Just tried mount -t iso9660 /dev/sr0 /home/user/temp
and got 'mount: /dev/sr0: can't read superblock' as the error.
This is a different error to the others, so maybe the superblock is
barfed on the cdrom disk? If so, maybe its beyond recovery?
Its a read:write disk, so there may be a trick yet?
Vahis
> Responding to Pascal Hambourg:
>
>> Hello,
>>
>> bb a écrit :
>>>
>>> There is a tool named ddrescue that can continue to read even if you
>>> get block errors, and if you save it to a file, and once you have the
>>> file, try to play it with mplayer to see if there is any hope at all to
>>> get the mp3 files back.
>>
>> Will mplayer be happy to be fed with a filesystem image ? If not, you
>> can try to recover files from the filesystem image with photorec, which
>> is part of the testdisk package.
>
>
> These look useful, but first I need to get the dvd drive to physically
> read something. ATM its just spins a while, then bombs out with a "No
> such file or directory" error.
This is attempt to read a filesystem.
Now, ddrescue is different (as is dd)
It doesn't care about file systems, it reads the device.
I have rescued some really badly broken ones with ddrescue.
This takes time (hours or days) to accomplish but something will be
rescued, that's for sure.
You may be better off with creating a raw device and try to read from
that, it's worked here.
Here's one set of instructions:
http://ask.metafilter.com/68265/But-its-just-a-little-scratch
>
> I'll play around with ddrescue, but I don't thing it'll do much until I
> can figure out how to read /something/ on the duff disk.
Your "no such file" is telling me that you haven't tried on device level.
Try ddrescue, it's worth it.
Vahis
--
"Sunrise 7:48am (EET), sunset 4:18pm (EET) at Espoo, Finland (8:30 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
8:10pm up 3 days 1:11, 11 users, load average: 0.20, 0.17, 0.18
Vahis
>
>
> and got 'mount: /dev/sr0: can't read superblock' as the error.
A broken disk can hardly be mounted.
It must be read on device level, unmounted.
>
> This is a different error to the others, so maybe the superblock is
> barfed on the cdrom disk? If so, maybe its beyond recovery?
>
> Its a read:write disk, so there may be a trick yet?
>
I recommend ddrescue warmly.
Vahis
--
"Sunrise 7:48am (EET), sunset 4:18pm (EET) at Espoo, Finland (8:30 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
8:22pm up 3 days 1:23, 11 users, load average: 0.14, 0.17, 0.16
philo
there's a windows utility call iso buster that I've used with good results.
don't know if there is a Linux equiv
Rikishi42
> I burned a CDROM a short while back, and now can't get the damn thing to
> mount (even though it would have been checked as OK prior to storage). As
> its got data on it that is no longer available from source, I'm wondering
> if anybody has any favorite tricks they've used to force a mount.
Once recovered one by forcing the drive to read it at a slow rate (1x speed
or 2x speed).
If I'm not mistaken, I did that by using hdparm:
hdparm -E 2 /dev/cdrom
Mind that you try your reading on a CD-ROM drive, not a DVD drive. Unless it
was burned on a DVD burner, in which case you use that one.
Min CD-ROM speed for a DVD device is 8x, of course.
Good luck.
--
Any time things appear to be going better, you have overlooked
something.
Mike Jones
Hmmm. Interesting ideas there. I shall investigate. Thanks.
Mike Jones
Doubtless. It might be a combination of things called in one commandline
though. I guess I'm going to end up learning it. ;\
Unruh
>Responding to Rikishi42:
>> On 2009-11-02, Mike Jones <N...@Arizona.Bay> wrote:
>>
>>> I burned a CDROM a short while back, and now can't get the damn thing
>>> to mount (even though it would have been checked as OK prior to
>>> storage). As its got data on it that is no longer available from
>>> source, I'm wondering if anybody has any favorite tricks they've used
>>> to force a mount.
>>
>> Once recovered one by forcing the drive to read it at a slow rate (1x
>> speed or 2x speed).
>>
>> If I'm not mistaken, I did that by using hdparm:
>>
>> hdparm -E 2 /dev/cdrom
>>
>> Mind that you try your reading on a CD-ROM drive, not a DVD drive.
>> Unless it was burned on a DVD burner, in which case you use that one.
>>
>> Min CD-ROM speed for a DVD device is 8x, of course.
>>
>>
>> Good luck.
>Hmmm. Interesting ideas there. I shall investigate. Thanks.
The problem with dvds is that they have massive error correction on
them. Thus by the time they crap out, there is a huge error rate
But certainly try reading it slowly, try reading it on different drives,
try on the same drive it was recorded on, etc.
Mike Jones
Would this work in reverse? As in, burning a CDROM in a DVD burner
resulting in a sloppily burned CDROM?
One would think that the things would have become more accurate, not less.
bb
> Hello,
>
> bb a écrit :
Mplayer is amazing, it can mostly play an iso or image of a complete DVD and
with some magic figure out how to play it.
What I mean is that _IF_ mplayer find the data and start to play it, it's also
possible to save the songs as files.
But in any case, a file image of the CD is needed for a recovery, since it can
fail and it's good to keep the original copy for a new try.
/bb
Doug Mitton
I've used CDFS to rescue a friends photos in the past. It doesn't
appear to be supported recently but its located:
http://users.elis.ugent.be/~mronsse/cdfs/
Good luck!
--
-------------------------------------------------
http://www3.sympatico.ca/dmitton
SPAM Reduction: Remove ".invalid" from my domain.
-------------------------------------------------
Mike Jones
Another useful looking tool that relies on something actually booting in
some way.
There does seem to be a few options to look at though. Cheers.
I'm thinking this disk is a write off though, including the data on it.
Doug Mitton
I don't think this requires the disk to "boot" (mount). But it may
not fit your needs. I use it to recover data from a muti-session data
disk that has had a newer session write "junk" over a previous "good"
session. I don't think it relies on the actual master file system.
But, Ive been incorrect before.
jellybean stonerfish
> I'm thinking this disk is a write off though, including the data on it.
What happened when you tried ddrescue?
Pascal Hambourg
>
>>> http://users.elis.ugent.be/~mronsse/cdfs/
>
> I use it to recover data from a muti-session data
> disk that has had a newer session write "junk" over a previous "good"
> session.
Isn't it overkill for this purpose ? You can select the session number
in the mount options when mounting a multisession CD-ROM the usual way.
Mike Jones
> On Tue, 03 Nov 2009 19:46:19 +0000, Mike Jones wrote:
>
>> I'm thinking this disk is a write off though, including the data on it.
>
> What happened when you tried ddrescue?
Not got there yet. Just finished all the "try it in this machine, and now
this drive..." stuff. Next up, the software options.
I did find another CDROM, same batch, with more data on it, that has the
same (I assume, by it's errors) problem. I'm seeing a pattern. something,
some day, was barfing up disks. The strange thing is, they must have
worked back then, as I always check every burn to make sure it "stuck".
There may have been a reason they were so cheap. >:(
Mike Jones
> Doug Mitton a écrit :
I'll settle for a massacre if it gets this data back. ;\
Unruh
>Responding to Doug Mitton:
I have no idea what you mean by "booting" It is not an operating system
disk. It is simply a disk full of files. Did you mean "mounting" rather
than "booting"?
What error messages do you get when you try to mount it? What did you
use to write the data to the disk? Is it and ISO 9660 filesystem?
Can it be read at all? You might try doing dd on it to get the data onto
a file on your system.
dd -if /dev/sdb -of dvd-contents.iso
Mike Jones
Oops! My bad. I did indeed mean "mounting". (Playing with multiple
projects can suffer terminology cross-over.)
So far I can't get anything to read the disk at all. No mounts work, and
#-> dd if=/dev/hda of=/tmp/disk.out
dd: reading `/dev/hda': Input/output error
0+0 records in
0+0 records out
0 bytes (0 B) copied, 1.39585 s, 0.0 kB/s
...is about as far as I've got with this disk.
bb
> #-> dd if=/dev/hda of=/tmp/disk.out
> dd: reading `/dev/hda': Input/output error
> 0+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 1.39585 s, 0.0 kB/s
>
> ...is about as far as I've got with this disk.
>
That looks bad, just as the cdrom never load properly.
If you have cdrdao installed you should get some good
info with the command cdrdao disk-info
I did the same test that you did with my rescue CD,
and the result was:
# dd if=/dev/cdrom of=/tmp/rescuecd.iso
332752+0 records in
332752+0 records out
170369024 bytes (170 MB) copied, 55.2196 s, 3.1 MB/s
# mkdir /x
# mount -o loop,ro /tmp/rescuecd.iso /x
# ls -l /x
total 130510
drwxr-xr-x 2 root root 2048 2007-11-25 19:04 bootdisk
drwxr-xr-x 3 root root 4096 2007-11-30 19:51 isolinux
drwxr-xr-x 2 root root 2048 2007-11-20 22:07 syslinux
-rw-rw-rw- 1 root root 133632000 2007-11-25 19:12 sysrcd.dat
-rw-r--r-- 1 root root 45 2007-11-25 19:12 sysrcd.md5
-rw-r--r-- 1 root root 876 2007-11-16 09:28 usbstick.htm
# umount /x
So that is what you should expect, but try with ddrescue instead.
/bb
Doug Mitton
>Doug Mitton a �crit :
Yes, it may well be overkill BUT when I did a search on the "problem",
that was one of the solutions. It kept me entertained for awhile and
actually worked.
Mike Jones
> Pascal Hambourg <boite-...@plouf.fr.eu.org> wrote:
>
>>Doug Mitton a écrit :
>>>
>>>>> http://users.elis.ugent.be/~mronsse/cdfs/
>>>
>>> I use it to recover data from a muti-session data disk that has had a
>>> newer session write "junk" over a previous "good" session.
>>
>>Isn't it overkill for this purpose ? You can select the session number
>>in the mount options when mounting a multisession CD-ROM the usual way.
>
> Yes, it may well be overkill BUT when I did a search on the "problem",
> that was one of the solutions. It kept me entertained for awhile and
> actually worked.
My problem is that I can't get anything to read the disk.
mount -t iso9660 -o ro /dev/hda /mnt/tmp
mount -t ext2 -o ro /dev/hda /mnt/tmp
mount -t auto -o ro /dev/hda /mnt/tmp
...all bomb out with errors.
From /var/log/syslog
Nov 4 11:12:50 NAME kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error }
Nov 4 11:12:50 NAME kernel: hda: command error: error=0x51 { IllegalLengthIndication LastFailedSense=0x05 }
Nov 4 11:12:50 NAME kernel: ide: failed opcode was: unknown
Nov 4 11:12:50 NAME kernel: ATAPI device hda:
Nov 4 11:12:50 NAME kernel: Error: Illegal request -- (Sense key=0x05)
Nov 4 11:12:50 NAME kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
Nov 4 11:12:50 NAME kernel: The failed "Read 10" packet command was:
Nov 4 11:12:50 NAME kernel: "28 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 "
Nov 4 11:12:50 NAME kernel: end_request: I/O error, dev hda, sector 0
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 0
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 1
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 2
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 3
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 4
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 5
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 6
Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 7
Nov 4 21:22:42 NAME kernel: hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Nov 4 21:22:42 NAME kernel: hda: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
Nov 4 21:22:42 NAME kernel: ide: failed opcode was: unknown
Nov 4 21:22:42 NAME kernel: ATAPI device hda:
Nov 4 21:22:42 NAME kernel: Error: Medium error -- (Sense key=0x03)
Nov 4 21:22:42 NAME kernel: CIRC unrecovered error -- (asc=0x11, ascq=0x06)
Nov 4 21:22:42 NAME kernel: The failed "Read 10" packet command was:
Nov 4 21:22:42 NAME kernel: "28 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 "
Nov 4 21:22:42 NAME kernel: end_request: I/O error, dev hda, sector 64
Nov 4 21:22:42 NAME kernel: isofs_fill_super: bread failed, dev=hda, iso_blknum=16, block=16
Nov 4 21:23:02 NAME kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error }
Nov 4 21:23:02 NAME kernel: hda: command error: error=0x51 { IllegalLengthIndication LastFailedSense=0x05 }
Nov 4 21:23:02 NAME kernel: ide: failed opcode was: unknown
Nov 4 21:23:02 NAME kernel: ATAPI device hda:
Nov 4 21:23:02 NAME kernel: Error: Illegal request -- (Sense key=0x05)
Nov 4 21:23:02 NAME kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
Nov 4 21:23:02 NAME kernel: The failed "Read 10" packet command was:
Nov 4 21:23:02 NAME kernel: "28 00 00 00 00 01 00 00 21 00 00 00 00 00 00 00 "
Nov 4 21:23:02 NAME kernel: end_request: I/O error, dev hda, sector 4
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 1
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 2
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 3
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 4
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 5
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 6
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 7
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 8
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 9
Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 10
Nov 4 21:23:03 NAME kernel: FAT: bogus number of reserved sectors
Nov 4 21:23:03 NAME kernel: GFS2: Unrecognized block device or mount point /dev/hda
Nov 4 21:23:03 NAME kernel: GFS2: gfs2 mount does not exist
Nov 4 21:23:14 NAME kernel: VFS: Can't find an ext2 filesystem on dev hda.
Nov 4 21:27:10 NAME kernel: FAT: bogus number of reserved sectors
Nov 4 21:27:58 NAME kernel: hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Nov 4 21:27:58 NAME kernel: hda: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
Nov 4 21:27:58 NAME kernel: ide: failed opcode was: unknown
Nov 4 21:27:58 NAME kernel: ATAPI device hda:
Nov 4 21:27:58 NAME kernel: Error: Medium error -- (Sense key=0x03)
Nov 4 21:27:58 NAME kernel: CIRC unrecovered error -- (asc=0x11, ascq=0x06)
Nov 4 21:27:58 NAME kernel: The failed "Read 10" packet command was:
Nov 4 21:27:58 NAME kernel: "28 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 "
Nov 4 21:27:58 NAME kernel: end_request: I/O error, dev hda, sector 64
Nov 4 21:27:58 NAME kernel: isofs_fill_super: bread failed, dev=hda, iso_blknum=16, block=16
Vahis
>
> My problem is that I can't get anything to read the disk.
>
>
> mount -t iso9660 -o ro /dev/hda /mnt/tmp
>
> mount -t ext2 -o ro /dev/hda /mnt/tmp
>
> mount -t auto -o ro /dev/hda /mnt/tmp
>
> ...all bomb out with errors.
>
Why do you keep trying to mount it?
It's been said before:_Don't_ mount it. Use ddrescue.
Even better: Make it a raw device, that's helped me sometimes when ddrescue
can't even read normal /dev, I've made it a raw device.
You'll get whatever bits and bytes there are left to recover.
Vahis
--
"Sunrise 7:56am (EET), sunset 4:11pm (EET) at Espoo, Finland (8:15 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
9:26am up 5 days 14:27, 12 users, load average: 0.10, 0.08, 0.08
jellybean stonerfish
> On 2009-11-04, Mike Jones <N...@Arizona.Bay> wrote:
>>
>> My problem is that I can't get anything to read the disk.
>>
>>
>> mount -t iso9660 -o ro /dev/hda /mnt/tmp
>>
>> mount -t ext2 -o ro /dev/hda /mnt/tmp
>>
>> mount -t auto -o ro /dev/hda /mnt/tmp
>>
>> ...all bomb out with errors.
>>
>>
> Why do you keep trying to mount it?
>
> It's been said before:_Don't_ mount it. Use ddrescue.
He says he hasn't tried ddrescue yet. Why, I don't know.
>
> Even better: Make it a raw device, that's helped me sometimes when
> ddrescue can't even read normal /dev, I've made it a raw device.
What do you mean by making it a raw device, and how do you do so?
Mike Jones
>> Why do you keep trying to mount it?
>>
>> It's been said before:_Don't_ mount it. Use ddrescue.
>
> He says he hasn't tried ddrescue yet. Why, I don't know.
Trying to exhaust all other options before installing something.
That, and the disk doesn't seem to even want to be recognised.
It does seem to be a physical problem, happening at the reader itself,
before any software can get a grip on it, though ddrescue might indeed do
the trick.
Vahis
Vahis
--
"Sunrise 7:56am (EET), sunset 4:11pm (EET) at Espoo, Finland (8:15 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
7:23pm up 6 days 0:24, 12 users, load average: 0.25, 0.25, 0.25
jellybean stonerfish
> On 2009-11-05, jellybean stonerfish <stone...@geocities.com> wrote:
>> On Thu, 05 Nov 2009 07:33:21 +0000, Vahis wrote:
>>
>>> Why do you keep trying to mount it?
>>>
>>> It's been said before:_Don't_ mount it. Use ddrescue.
>>
>> He says he hasn't tried ddrescue yet. Why, I don't know.
>>
>>
>>> Even better: Make it a raw device, that's helped me sometimes when
>>> ddrescue can't even read normal /dev, I've made it a raw device.
>>
>> What do you mean by making it a raw device, and how do you do so?
>
> http://tinyurl.com/yl2pfxk
>
> Vahis
Ok, Thanks.
Rikishi42
>> The problem with dvds is that they have massive error correction on
>> them. Thus by the time they crap out, there is a huge error rate But
>> certainly try reading it slowly, try reading it on different drives, try
>> on the same drive it was recorded on, etc.
> Would this work in reverse? As in, burning a CDROM in a DVD burner
> resulting in a sloppily burned CDROM?
>
> One would think that the things would have become more accurate, not less.
That's not experience shows. DVD's are much less reliable over time than
CD-ROM's. And CD-ROm's burned in a DVD burner are of less quality that if
they are in a CD burner. It helps somewhat to slow the burning, but stil...
Mike Jones
I've been getting that idea from my experiences so far.
Looks like I've got another lump of hardware to buy then.
Rikishi42
>> That's not experience shows. DVD's are much less reliable over time than
>> CD-ROM's. And CD-ROm's burned in a DVD burner are of less quality that
>> if they are in a CD burner. It helps somewhat to slow the burning, but
>> stil...
> I've been getting that idea from my experiences so far.
>
> Looks like I've got another lump of hardware to buy then.
Well, it seems that BlueRay would be more reliable. Something to do with a
thicker, or more sturdy, layer. And also an extra layer on the label side.
I'm holding it off until prices drop dramatically, and actual experiences
start showing up on Usenet.
Mike Jones
> On 2009-11-06, Mike Jones <N...@Arizona.Bay> wrote:
>>> That's not experience shows. DVD's are much less reliable over time
>>> than CD-ROM's. And CD-ROm's burned in a DVD burner are of less quality
>>> that if they are in a CD burner. It helps somewhat to slow the
>>> burning, but stil...
>
>> I've been getting that idea from my experiences so far.
>>
>> Looks like I've got another lump of hardware to buy then.
>
> Well, it seems that BlueRay would be more reliable. Something to do with
> a thicker, or more sturdy, layer. And also an extra layer on the label
> side.
>
> I'm holding it off until prices drop dramatically, and actual
> experiences start showing up on Usenet.
I'll be avoiding it like the plague. Remember VHS? Do we /really/ want to
hand defining standards over to Sony again?
--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.