From: hansolofalcon@worldnet.att.net (Gregg C Levine)
To: linux-mtd@lists.infradead.org
Subject: New problem with DoC
Date: Mon, 17 Mar 2003 14:56:19 -0500 [thread overview]
Message-ID: <000201c2ecbf$47ab1be0$88a7580c@who5> (raw)
In-Reply-To: <A05D1A08-587E-11D7-ADC7-000393AD6294@regolith.co.uk>
<Please see below! Jasmine you too!>
> -----Original Message-----
> From: Jasmine Strong [mailto:jasmine at regolith.co.uk]
> Sent: Monday, March 17, 2003 8:45 AM
> To: Gregg C Levine
> Subject: Re: New problem with DoC
>=20
>=20
> On Monday, Mar 17, 2003, at 02:42 Europe/London, Gregg C Levine
wrote:
>=20
> > Hello from Gregg C Levine
> > It seems to be my day for problems with this configuration. Using
the
> > "doc_loadbios" program found in the util directory of the mtd
> > collection, I've managed to write the firmware to the DoC, one was
the
> > one labeled "DOC2.FFF", and the other one was "doc42.exb", both
were
> > copied from the disk provided by M-SYS that's version 4.2 of their
> > series of tools.
>=20
> Uh. last I saw, doc_loadbios didn't understand .exb files.
>=20
> You should be using the Grub firmware anyway.
>=20
> -Jas.
Hello again from Gregg C Levine
Thanks folks. That worked. Funny thing, these devices, the solutions
suggested by the manufacturer didn't work. Which is what I expected.=20
Whereas the MTD method for reviving it, or even a new one for
installing the Grub Firmware worked. It still looks for the /boot
directory, and the menu.lst file. But at least it works.=20
Next question, how do I put that one, the /boot directory, and the
menu.list as when I would use a normal Grub booting arrangement in to
the DoC? Oh, and a custom kernel as well.
-------------------
P.S. David is my message formatting acceptable?
-------------------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
next parent reply other threads:[~2003-03-17 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A05D1A08-587E-11D7-ADC7-000393AD6294@regolith.co.uk>
2003-03-17 19:56 ` Gregg C Levine [this message]
2003-03-17 20:31 ` New problem with DoC Russ Dill
2003-03-17 20:49 ` Charles Manning
2003-03-17 21:13 ` Russ Dill
2003-03-17 2:42 Gregg C Levine
2003-03-17 7:05 ` Henrik Nordstrom
2003-03-17 11:31 ` Gregg C Levine
2003-03-17 13:30 ` Henrik Nordstrom
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='000201c2ecbf$47ab1be0$88a7580c@who5' \
--to=hansolofalcon@worldnet.att.net \
--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