From: Sam Ducksworth <sam@ducksworth.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] installation problems
Date: Wed, 5 Dec 2001 08:31:59 -0600 [thread overview]
Message-ID: <Pine.BSF.4.33.0112050825001.58539-100000@lucifer.ducksworth.com> (raw)
In-Reply-To: <S8aP7.27857$WC1.2915253@newsread2.prod.itd.earthlink.net>
i have also ran into a similar problem. i ended up resetting
the bios to defaults and restarting the installation again.
i am not exactly sure what i did to cause the problem, but i
think it had something to do with changes that i made to the
pci/isa and pnp configuration options to get another os to
work on that board. hope that helps
--sam
On Wed, 5 Dec 2001, josh d wrote:
>
> I'm having trouble installing Plan9 on my x86. Keep in
> mind that I've switched out both the installation CD as well as the target
> hard drive, and the problem remains the same.
>
> When the installation program is unpacking the file system to disk, it
> gets around 99% done and gives me this error: "write /n/kfs/386/bin si: copy
> error; copy ran out of input".
>
> It continues on, and when i get to the prompt to create a boot floppy,
> right before that choice it prints:
>
> "addint file /386/9load length 14560 cp: can't stat /n/kfs/386/9pcdisk:
> file does not exist"
>
> Then i create the boot disk and when I boot from it, it says "operating
> system not found". Super duper. Anyone know what's going on?
>
> thanks
> josh
>
--sam
next prev parent reply other threads:[~2001-12-05 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 9:56 josh d
2001-12-05 14:09 ` Matt Senecal
2001-12-05 14:31 ` Sam Ducksworth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 14:48 [9fans] Installation Problems jmk
2002-03-13 10:05 rob pascual
1999-01-27 9:15 forsyth
1999-01-26 6:56
1997-09-25 15:04 FRANKLIN
1997-09-25 13:43 Markus
1997-09-25 13:32 rsc
1997-09-25 12:50 FRANKLIN
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=Pine.BSF.4.33.0112050825001.58539-100000@lucifer.ducksworth.com \
--to=sam@ducksworth.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).