From: Mark Meade <mark@lakeshoremicro.com>
To: scohen@atlanticpositioners.com, <linux-mtd@lists.infradead.org>
Subject: Re: Corrupted DOC 2000 and Tools Building Problems
Date: Fri, 23 May 2003 20:10:37 -0400 [thread overview]
Message-ID: <200305232001.01206.mark@lakeshoremicro.com> (raw)
In-Reply-To: <001201c32081$b4e2d360$1d28a8c0@flpalmharbor>
On Thursday 22 May 2003 12:46 pm, Stephen D. Cohen wrote:
> If anyone can suggest a method to revive my scrogged DOC, I will greatly
> appreciate it.
I've had more than a few times when I've thought my DOC was completely dead,
and I've always been able to revive it with an older M-Sys utility called
"docpmap.exe". I recall that this command could be dangerous - it had the
ability to completely erase the DOC, including the bad block table.
I don't think this utility is available anymore, but similar functionality may
be available through command line options to DFORMAT.
It's also possible that eraseall and nftl_format under Linux could fix things
up, but that may trash the BBT as well.
prev parent reply other threads:[~2003-05-25 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 16:46 Corrupted DOC 2000 and Tools Building Problems Stephen D. Cohen
2003-05-24 0:10 ` Mark Meade [this message]
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=200305232001.01206.mark@lakeshoremicro.com \
--to=mark@lakeshoremicro.com \
--cc=linux-mtd@lists.infradead.org \
--cc=scohen@atlanticpositioners.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox