From: Matt Senecal <msenecal@logicon.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Update: Valiant but vain efforts
Date: Tue, 20 Nov 2001 18:27:43 +0000 [thread overview]
Message-ID: <9te6s8$s35$1@newpoisson.nosc.mil> (raw)
In-Reply-To: <50ecc828.0111192021.3c68ac23@posting.google.com>
I first tried re-formatting and re-partitioning the two hard drives attached
to the system. That didn't work. I verified both disks the long way, and
they both check out.
I copied the files from the installation floppy to both HDs, booted from the
installation floppy, and when prompted to select my boot device, tried
booting from both drives (fdC0!dos!plan9.gz, fdC0!dos!plan9.ini, etc.).
Still no go.
Any other ideas?
The system in question is a '486 AMD with 48MB RAM, a 350MB HD, a 160MB HD
(contains Plan 9 installation files, will be removed after installation), NE
2000 NIC, SB16 Value, some kind of I/O card, and a Cirrus Logic VESA Video
card (the exact model escapes me).
"Matt Senecal" <msenecal@logicon.com> wrote in message
news:50ecc828.0111192021.3c68ac23@posting.google.com...
> When installing onto a '486 terminal, I get the following
> error message at boot:
>
> PBS...Plan 9 From Bell Labs
> ELCR: 0000
> Using fd0!dos!plan9.ini
> <<Hard drives listed here>>
> no such FAT partition fd0!dos
>
> I'm then given the option of selecting my boot device.
>
> Does anyone know what might be causing this error? The disk I made was
> from an image downloaded from Bell Labs. I've checked the integrity of
> the disk, and it's in (supposedly) perfect shape.
next prev parent reply other threads:[~2001-11-20 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 9:38 [9fans] "No such FAT partition" error on setup Matt Senecal
2001-11-20 18:27 ` Matt Senecal [this message]
2001-11-20 20:09 ` [9fans] Update: Valiant but vain efforts Martin Harriss
2001-11-21 10:07 ` Matt Senecal
2001-11-22 9:56 ` Matt Senecal
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='9te6s8$s35$1@newpoisson.nosc.mil' \
--to=msenecal@logicon.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).