public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Stephen Herzog" <mtd@sdesign.com>
To: <cabcam@optusnet.com.au>, <linux-mtd@lists.infradead.org>
Subject: Re: Recovery of crashed DoC???
Date: Tue, 17 Jul 2001 05:32:28 -0700	[thread overview]
Message-ID: <003b01c10ebc$8a7ef0a0$160aa8c0@gumby> (raw)
In-Reply-To: 000901c10e92$eca169e0$4c418990@adsl

Greetings,

Assuming the OS is not the data you really, really, need, you could try 
the following:  Remove the DoC and attach a regular IDE drive to the 
SBU 4825 and boot from IDE first. Next compile a kernel on it with 
DoC support. You will have to install your kernel on a floppy disk 
however to get it to boot rather than from DoC. Now put the DoC back
in the SBU, boot from floppy/linux-kernel try mounting the DoC. Perhaps
you can get some of the data that way. 

I don't think you want to use the DINFO.EXE utility.  That tool places
a dos bios patch on the nftl layer that allows the computer to boot 
from the DoC. 

Good luck,

Stephen Herzog

----- Original Message ----- 
From: "Colin Durey" <cabcam@optusnet.com.au>
To: "MTD List Admin (E-mail)" <linux-mtd@lists.infradead.org>
Sent: Tuesday, July 17, 2001 12:34 AM
Subject: Recovery of crashed DoC???


> I have a 40mb DoC which contains critical information that I really, really,
> need to get hold of.
> Linux fails to boot after discovering damaged blocks. The DoC is set as the
> boot device on an embedded SBU (Advantech 4825).
> 
> Plugging in a floppy and booting DOS, then using the DoC utility DINFO.EXE
> returns the following info:
> Drive Name:  C:
> Disk Size 40,072 kb
> Software Version 1.10
> TrueFFS Compatibility 3.3.2
> Firmware size 48kb
> 
> which suggest that the chip is still alive, at least.
> 
> Is there any way in which to read the data files from the DoC?  I have been
> told to use the utility DUPDATE.EXE to change the drive name to D: or
> something other than C:, so that I can then connect another HD and boot it
> as C: and then mount the DoC as a secondary drive and subsequently recover
> the precious files. DUPDATE.EXE doesn't seem to want to let me do that.
> 
> Anyone know what to do?
> 
> Colin Durey
> Cabcam - Tech Division
> +61-2-96984711 (T)  +61-2-96984674 (F)
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

      reply	other threads:[~2001-07-17 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17  7:34 Recovery of crashed DoC??? Colin Durey
2001-07-17 12:32 ` Stephen Herzog [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='003b01c10ebc$8a7ef0a0$160aa8c0@gumby' \
    --to=mtd@sdesign.com \
    --cc=cabcam@optusnet.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox