In message <47FC6D77BE%ben@laughton.demon.co.uk>
          Ben Laughton <ben@laughton.demon.co.uk> wrote:

> 1. Create a partition in Rapier at the same point and with the same size as
> you want your RiscBSD partition to be.
> 
> 2. Format the partition using Rapier.
> 
> 3. Use bb_riscbsd to create a RiscBSD bootblock on the partition.
> 
> 4. Start the RiscBSD installation and proceed as described in your original
> posting.

OK, I have done something drastic and it works now, part way. I deleted
my Risc OS partition on my Quantumn IDE and used !Rapier to create a
new primary partition on it.  I called it QUANTUM1.  I then formatted
QUANTUM0 to ATAFS and alloted it half the disk capacity (1.5Gb).  I then
rebooted and booted up RiscBSD from CDROM. I started the install process
as stated in my last email and lo-and-behold, when I told RiscBSD to
install onto partition 0 (QUANTU0) it all went perfectly well! After
installation I rebooted back into Risc OS and I created another partition
called QUANTUM1 which I formatted to ATAFS.  This all went fine and now
I have my Risc OS partiton back at the secondary logical partition on
this IDE disk.  I copied my files back from backup and everything is
cool.  BUT and here it comes, you all knew it was lurking around the
corner *grin*  Risc BSD does not recognise my CDROM drive!  I have
fullowed the installation instructions to the T and I told the 'inst'
program to mount my CD ROM drive.  I chose drive 0 and drive 1 but none
worked reporting the following errors:

[0]
cd0(wdc2:0): illegal request
mount_cd9660: : invalid argument
mount failed

for [1] I get
mount_cd9660: : device not configured
mount failed

So I tried doing it manually from the CLI and so I did this :

mkdir /mnt/cdrom
cd mnt/cdrom
mount -rt cd9660 /dev/cd0a .

I also tried the above without "cd mnt/cdrom" and instead did:
mount -rt cd9660 /dev/cd0a /mnt/cdrom

I got the same second error from above.

> I found that when I rebooted and went back into the RISC OS Desktop the ATAFS
> disc icon corresponding to the RiscBSD partition was greyed out, I assume

I didn't find this to happen. I currently have a yellowy coloured
ATAFS_0 icon on my icon bar even after using
CD::RISCBSD.$.RISCOS.MISC.BB_RISCBSD to reconfigure my boot block.

my PART_INFO program reports:

RISCiX (PowerTec) partition table found at cylinder 3128
Disc drive not known

is this normal?  I do have a Alsystems SCSI2 Card in my machine but I'm
installing the partition on a Yellowstone ATAFS IDE drive/card combo.
Weird... anyway................

> because it couldn't recognise what type of partition it was.  The I just went
> back into Rapier and removed the partition and all seems fine (maybe you
> could do this after step 3. above - I might try this later while all my
> data is still backed-up :-).

I tried to remove my BSD partition from the partition list in !Rapier
but my version of !Rapier will only allow me to remove partitions in
sequence, not in random order, therefore if I try to remove the BSD
partition which was first one, it won't allow me, as the RiscOS
partition is after it.  It will only erase the Risc OS partition first,
then the RiscBSD one, so I still have an annoying icon on my icon bar
which says :

Error when reading ATAFS::0.$ 0 Disc not understood - has it been
formatted?

whenever I click on it.  Otherwise it doesn't effect my system (i.e it
doesn't crash in anyway, I just get that error and click ok and things
carry on as normal).

Maybe I'm doing somethig wrong.  How did you ask !Rapier to remove your
RiscBSD partition (and therefore remove the drive icon)?

Kozzey

-- 
Kaustav Bhattacharya [ aka Kozzey ]
[ http://redhotcountry.co.uk ] - Keep an eye on Country music
[ http://www.users.dircon.co.uk ] - My personal homepage
[ +44 (0)181 930 4824 ] - Voice mail
Memeber of the Country Music Association. No. 106306




 
    
                

                     ... Is this yours? Your dog left it on my lawn ...