From: "Tim Drury" <tdrury@siliconmotorsports.com>
To: <linux-mtd@lists.infradead.org>
Subject: RE: DFORMAT ERROR " IPL block is bad."on DiskOnChip 2000?
Date: Wed, 27 Aug 2003 09:42:07 -0400 [thread overview]
Message-ID: <000001c36ca1$02237b00$f546a8c0@SIMOTORSPORTS> (raw)
In-Reply-To: <000501c36968$ceadd580$3301a8c0@SIMOTORSPORTS>
For the sake of the archives, I'll answer my own question. M-systems
tech support says my DOC is bad and needs to be replaced.
-tim
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org
> [mailto:linux-mtd-bounces@lists.infradead.org] On Behalf Of Tim Drury
> Sent: Saturday, August 23, 2003 7:22 AM
> To: linux-mtd@lists.infradead.org
> Subject: DFORMAT ERROR " IPL block is bad."on DiskOnChip 2000?
>
>
> Did the original poster of the error message below ever get
> a solution to this problem? I seem to be having the same problem.
>
> -tim
>
>
> >When I use the DOC5.1.4 DOS utilities'
> >DFORMAT /WIN:DC00 /S:DOC514.EXB /FIRST
> >
> >ERRORS
> >
> >DiskOnChip 2000 found in 0xdc000.
> >64M media, 16K unit
> >Virgin card rebuilding unit map.
> >Media has been scanned
> >ERROR - IPL block is bad.
> >Error formatting DiskOnChip.
> >Status code is 119 (flUnknow status) received from
> >flFormatPhysicalDrive. Format failed.
> >
> >What's the matter with it?
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/li> nux-mtd/
>
next prev parent reply other threads:[~2003-08-27 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 11:22 DFORMAT ERROR " IPL block is bad."on DiskOnChip 2000? Tim Drury
2003-08-27 13:42 ` Tim Drury [this message]
[not found] <E19sKVX-0005o4-Uv@pentafluge.infradead.org>
2003-08-29 3:01 ` Kien Phung Chi
-- strict thread matches above, loose matches on Subject: below --
2003-04-19 9:48 lhl
2003-04-21 19:24 ` Edward A. Hildum
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='000001c36ca1$02237b00$f546a8c0@SIMOTORSPORTS' \
--to=tdrury@siliconmotorsports.com \
--cc=linux-mtd@lists.infradead.org \
/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.