Re: Installation Assistance

Peter Bell <[email protected]>
Newsgroups gmane.os.netbsd.ports.acorn32
Message-ID <[email protected]>
In message <[email protected]>
          James Holtom <[email protected]> wrote:

 [Snip]

> Many moons ago I had RiscBSD running on my RiscPC

Same here, around 1.2, IIRC.
> -- although most of my computing since then has been on x86 FreeBSD. Anyway
> I've put my RiscPC back together again, having remembered I've got RISC OS 4,
> and have found a nice big 15GB IBM disc for it.

Rigt, well I'm building a box with RO3.7, SA (revT) and 44GB IBM disc
on an APDL ideA.  I'm trying to use the whole of the 44GB, with RO on
the original 205MB.

> The bb_netbsd program for creating the NetBSD partition is behaving oddly:
> (CVS tag: $NetBSD: bb_netbsd,v 1.1 2001/02/19 14:09:01 reinoud Exp $
> 
> I used !HForm (2.52 01 Dec 1999) and allowed it to use longfilenames.
> HForm says the disc is 16383/16/63 C/H/S, but with LBA revises this to
> 29795/16/63. I formatted the RISC OS partition as 13315 cylinders.
> Unfortunately bb_netbsd thinks I've got -3328 cylinders running from 0
> to -3329... argh... I haven't let it proceed to mash my disc...

When I run bb_netbsd, I get 0--3977 cylinders.  Since I haven't got
anything on the drive I didn't care so just went ahead.  bb_netbsd
completes *very* quickly.

> I am wondering if:
> a) the disc is too big for it

I guess that this might be correct.

> b) the 'longfilenames' option I selected has used a whacky format, the
> bootblock for-which is not understood by bb_netbsd, or worse is not at
> 0xC00 ...

Being on 3.7, I'm not using longfilenames

> Can someone tell me what to do / reassure me 'it will just work'...?

Not me.  I'm just as lost as you!

> I note from the archives that there were issues with the bootloader, but
> I haven't got that far yet, and didn't see anything about disc
> partitioning :-(

!BtNetBSD reports 'Bad disklabel' on my disc.

-- 
Peter Bell - [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.