well im just not having fun. I get morphos installed the way I want it and the hardrive i had it on has mechanical failure. Ok np I get a new hardrive and view the fact that I can get installed much faster this time.

I type "boot cd"
It starts up shows the sustyem id of cd etc corrext goes to
Quark/openfirmware

and tis stuck there will not move on to boot =(....

Any ideas of whats wrong please help!!!> I thought might be the cd but i burned another one and have same problem.

like to add whats real wierd is I can boot upthe debian install cd go figure

[ Edited by zephar123 on 2005/10/2 4:58 ]

[ Edited by zephar123 on 2005/10/2 4:59 ]

Try boot /pci/cdrom boot.img

Quote:
ive troied that ive also tried even writing it out with the cdrom@0,0
Ive also tried moving the hardrives cdroms and that and then doing it at cdrom@0,1. im goign bonkers here.

I can boot any other cd but the morphos one.
ok foudn one more bug what ever the issue is apparently has to do with mounting the cd rom drive go figure. As i foudn out if I load the install cds for sarge linux I get the error / CD_rom couldn't be mounted

[ Edited by zephar123 on 2005/10/2 17:13 ]

stevo solved the problem for em its the cdrom drive. FOr some reason its reading cds, but will not mount detect right. So go figure rofl

Probably there's some crap on your HD which is recognized by MorphOS as (semi)valid RDB with some partition as bootable.
Try booting from Linux CD then execute the following:
cp /dev/zero /dev/hda
This will completely clear your drive. You can not wait for this operation to finish completely ;), just wait for 20-30 sec and abort it. You just need to erase beginning of the drive.

Since you are speaking of RDB crap, let me mention an accident that made unusable my main hard disk some weeks ago. After a system crash the Pegasos became unable to boot. The boot phase from ANY device (MorphOS CDROM included) always stopped as soon as the "Quark/OpenFirmware" sentence appeared in the OpenFirmware screen. After some investigations I verified that this was caused simply by the presence of the affected hard disk. Yet, in the OpenFirmware environment I was able to see all its partitions and their contents with the ls command (BootImage partition formatted with FFS, all the others with PFS3).

I solved the problem putting the hard disk in my Amiga 4000, whose boot was not affected by its presence. Then I simply read and rewrote the RDB with OS3.9 HDToolBox, without changing anything. This was sufficient to restore the RDB into a suitable state. There were no problems at all when I reinserted the cured hard disk into my Pegasos. In such a way I recovered 120 Gb of precious data!

The MorphOS Team should take into account either the insertion of a BootMenu soon after the boot.img loading, or the insertion of a RDB curing utility in the OpenFirmware. In my humble opinion it is absolutely necessary that any user might cure such problems without making recourse to Linux or an old Amiga.

[ Edited by DoctorMorbius_FP on 2005/10/3 15:44 ]

Quote:

Hm, i remembered about Amiga early startup control menu... But, there is some analogue - boot options. Just thought that you could try "BootDevice" (or something like that - don't remember exactly) parameter for the kernel, it allows you to specify system root device manually. Probably this could help too.
OpenFirmware is somehow open, so not only MorphOS team but anyone is able to write RDB (or whatever else) emergency tool which runs directly under OpenFirmware. So - suggest a bounty?