problem with b.com on new pcdist?

problem with b.com on new pcdist?

[jmk]

A back-arsed compatibility problem, you already had a partition
hd0dos I bet. First-time installers should not have this problem.

A new disk1 with this fixed is available.
You may want to wait until I fix the ATAPI problem before picking
it up unless your need is great, hopefully some time tomorrow.

------ original message follows ------

>From cse.psu.edu!9fans-outgoing-owner Wed Nov 15 01:22:50 EST 1995
Received: by colossus.cse.psu.edu id <78842>; Wed, 15 Nov 1995 01:18:00 -0500
Received: from interlock.wdni.com ([199.221.59.2]) by colossus.cse.psu.edu with SMTP id <78841>; Wed, 15 Nov 1995 01:17:42 -0500
Received: by interlock.wdni.com id AA29117
  (InterLock SMTP Gateway 3.0 for 9fans@cse.psu.edu);
  Tue, 14 Nov 1995 22:17:38 -0800
Message-Id: <199511150617.AA29117@interlock.wdni.com>
Received: by interlock.wdni.com (Protected-side Proxy Mail Agent-1);
  Tue, 14 Nov 1995 22:17:38 -0800
Date:	Wed, 15 Nov 1995 01:17:20 -0500
From:	Steven Plite <wdni.com!splite>
To:	cse.psu.edu!9fans
Subject: problem with b.com on new pcdist?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: cse.psu.edu!owner-9fans
Precedence: bulk
Reply-To: cse.psu.edu!9fans

Is it just me, or has anyone else been unable to get the latest b.com
(from the 14Nov pcdist) to recognize "hd" as a valid boot device?  I booted
the first floppy which built c:/plan9, then rebooted.  Ran b.com as usual to
continue the floppy install.  It silently ignored the bootfile line in
plan9.ini and booted my old kernel off h!0 instead.  If I try
"b hd!0!/plan9/9dos", it barfs and tells me the only valid devices are h!0 and
s!0.  I got the new pcdist to load by using an old version of b.com.
_______________________________________________________________________________
Steven Plite  <splite@wdni.com>                        The Weyerhaeuser Company

problem with b.com on new pcdist?

[David]

splite@wdni.COM (Steven Plite) writes:

>Is it just me, or has anyone else been unable to get the latest b.com
>(from the 14Nov pcdist) to recognize "hd" as a valid boot device?  I booted
>the first floppy which built c:/plan9, then rebooted.  Ran b.com as usual to
>continue the floppy install.  It silently ignored the bootfile line in
>plan9.ini and booted my old kernel off h!0 instead.  If I try
>"b hd!0!/plan9/9dos", it barfs and tells me the only valid devices are h!0 and
>s!0.  I got the new pcdist to load by using an old version of b.com.

Ah ha.  Maybe that's why I am having trouble installing.  Could someone
make available the old b.com please?

David.

problem with b.com on new pcdist?

[Robbin]

jmk@plan9.ATt.COM wrote:
> 
> A back-arsed compatibility problem, you already had a partition
> hd0dos I bet. First-time installers should not have this problem.
> 
> A new disk1 with this fixed is available.
> You may want to wait until I fix the ATAPI problem before picking
> it up unless your need is great, hopefully some time tomorrow.

...snip...

>> Is it just me, or has anyone else been unable to get the latest b.com
>> (from the 14Nov pcdist) to recognize "hd" as a valid boot device?  I booted
>> the first floppy which built c:/plan9, then rebooted.  Ran b.com as usual to
>> continue the floppy install.  It silently ignored the bootfile line in
>> plan9.ini and booted my old kernel off h!0 instead.  If I try
>> "b hd!0!/plan9/9dos", it barfs and tells me the only valid devices are h!0 and
>> s!0.  I got the new pcdist to load by using an old version of b.com.

I am having a similar problem, but with a fresh install using the almost-new
(Nov. 14th) disks.

One note up front: I run SCO UNIX on this machine most of the time and the
initial boot program run is the SCO bootstrap loader - I enter 'dos' at the boot
prompt prior to running b.com.  In investigating the problem described below, I
have tried running the second stage of the File System Installation by booting
from a floppy instead of from the SCO loader - there is no difference in symptoms
described.

My situation:

I installed the \plan9 tree off of disk1, configured the .ini file via the
gui-ish interface and rebooted.  I took the File System Installation option at
the end of the preliminary install sequence.  I then reboot to dos and ran
\plan9\b at the dos prompt.

Once b.com had started up, it either could not or would not find the 9dos boot
file.  There is no default boot file listed.  I checked the .ini file and it
looks right - sd!0!/plan9/9dos.  I have an 1542C controller and it is configured
correctly as far as I can tell.  There were no reported problems during the
initial load, but I assume that is use the BIOS or something similar to access
the FAT file system.

If I type in the boot file string at the prompt, I just get the Plan 9 boot
prompt back.
-- 
Robbin W. Johnson                                     rjohnson@mpr.ca
MPR Teltech Ltd.                Network Products and Systems Division

problem with b.com on new pcdist?

[Steven]

Is it just me, or has anyone else been unable to get the latest b.com
(from the 14Nov pcdist) to recognize "hd" as a valid boot device?  I booted
the first floppy which built c:/plan9, then rebooted.  Ran b.com as usual to
continue the floppy install.  It silently ignored the bootfile line in
plan9.ini and booted my old kernel off h!0 instead.  If I try
"b hd!0!/plan9/9dos", it barfs and tells me the only valid devices are h!0 and
s!0.  I got the new pcdist to load by using an old version of b.com.
_______________________________________________________________________________
Steven Plite  <splite@wdni.com>                        The Weyerhaeuser Company