From: Darrell Wright <dwright@beached.dyndns.org>
To: linux-kernel@vger.kernel.org
Cc: root@chaos.analogic.com
Subject: Re: A CD with errors (scratches etc.) blocks the whole system while reading damadged files
Date: 19 Apr 2002 10:28:58 -0400 [thread overview]
Message-ID: <1019226539.31288.2.camel@table.private> (raw)
In-Reply-To: <Pine.LNX.3.95.1020419100917.724A-100000@chaos.analogic.com>
I agree, I frequently find myself getting files off damages cd's that
others running windows cannot access. It takes a while, but I can
usually get everything but the files on the damaged parts and even then
I can get parts of them usually.
Darrell
On Fri, 2002-04-19 at 10:14, Richard B. Johnson wrote:
> On Thu, 18 Apr 2002, Dr. Death wrote:
>
> > Problem:
> >
> > I use SuSE Linux 7.2 and when I create md5sums from damaged files on a
> > CD, the WHOLE system freezes or is ugly slow untill md5 has passed the
> > damaged part of the file !
> >
>
> So what do you suggest? You can see from the logs that the device
> is having difficulty reading your damaged CD. You can do what
> Windows-95 does (ignore the errors and pretend everything is fine),
> or what Windows-98 and Windows-2000/Prof does (blue-screen, and re-boot),
> or you can try like hell to read the files like Linux does. What do you
> suggest?
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
>
> Windows-2000/Professional isn't.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-04-19 14:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 13:13 A CD with errors (scratches etc.) blocks the whole system while reading damadged files Dr. Death
2002-04-19 14:14 ` Richard B. Johnson
2002-04-19 14:22 ` Kent Borg
2002-04-19 14:46 ` Richard B. Johnson
2002-04-19 14:50 ` A CD with errors (scratches etc.) blocks the whole system while reading damaged files Stephen Satchell
2002-04-19 14:28 ` Darrell Wright [this message]
2002-04-19 14:36 ` A CD with errors (scratches etc.) blocks the whole system while reading damadged files dr john halewood
2002-04-19 18:00 ` Oliver Xymoron
2002-04-23 22:34 ` Bill Davidsen
2002-04-24 12:31 ` Richard B. Johnson
2002-04-24 19:16 ` Bill Davidsen
2002-04-24 19:52 ` Richard B. Johnson
2002-04-24 22:58 ` Stephen Samuel
2002-04-25 3:33 ` Bill Davidsen
2002-04-26 4:04 ` Mike Fedyk
2002-04-26 5:42 ` Erik Andersen
2002-04-26 7:35 ` Andre Hedrick
2002-04-25 20:50 ` Pavel Machek
2002-04-28 2:18 ` Andre Hedrick
2002-04-26 15:48 ` Mike Fedyk
2002-04-29 21:46 ` Bill Davidsen
2002-05-02 3:45 ` Mike Fedyk
2002-05-02 8:26 ` Stephen Samuel
2002-05-02 8:49 ` Xavier Bestel
2002-05-02 8:43 ` Zwane Mwaikambo
2002-05-02 9:12 ` Xavier Bestel
2002-05-02 15:48 ` Mike Fedyk
2002-05-03 7:14 ` Xavier Bestel
2002-05-02 15:40 ` Mike Fedyk
2002-05-02 17:15 ` Stephen Samuel
2002-04-26 15:23 ` Stephen Samuel
2002-04-26 10:16 ` Zwane Mwaikambo
2002-04-19 20:01 ` Erik Andersen
2002-04-21 15:18 ` Denis Vlasenko
2002-04-21 22:54 ` Hans-Peter Jansen
2002-04-22 5:38 ` Andre Hedrick
2002-04-22 14:49 ` Roger Larsson
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 21:18 Eric M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1019226539.31288.2.camel@table.private \
--to=dwright@beached.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.