I'm a longtime Amiga user who is building a Pegasos/MorphOS setup. It is a Pegasos I (Rev. 1A) with a G3/600, 128MB registered memory, Toshiba DVD-ROM, a Radeon 9000, and a Quantum Fireball SE 4GB hard disk. My problem is that Smartfirmware won't recognize the hard disk after I partition it, though I can repartition and format it all I want within MorphOS. I'm using lowprofile ATA100/133 cables with both the hard disk and DVD-ROM on their own cable/channel as Master. Does anyone have any suggestions as to what to try? Thanks.

Quote:

Have you looked at the trouble shooting section of the install guide (Click Here!)? Specifically the answeres to the "SmartFirmware can't find any of the two partitions" and "When I boot from the hard-drive I get the error message: 'The Filesystem is not supported'" questions?

Yes, I followed the steps in the install guide exactly. It complains that it can't find the device though I'm using the say device number as was used during partitioning. I've swapped cables, channels and everything else I can think of but the DVD-ROM is always recognized while the hard disk is not.

Use HDWrite or HDMBRClear to delete the MBR on the HD (if you used it on a Windoze machine).Let us know if you solve (probable..).
Bye.

I initially had a simular issue, I could boot the CD partition to me hearts content but couldn't boot the HD, trying what was said in the manual. Then I decided to uses the intructions (readme) file on the morphos cd and that corrected my issue with booting. They do differ from the instruction manual. I'll try to remeber to post it here later when I return home.

After a bit of experimentation, it looks like the hard disk is only recognized after a warm reboot, not after an initial cold boot. I used to have a similar problem on my A3000 because the SCSI disk wasn't spinning up fast enough...is it a similar issue here? I've now gotten MorphOS installed and booting off of the hard disk.

@cchaven

The issue with warm and cold boots is known. I didn't think it
invloved scsi drives though. There was a rumor that a new Open
Firmware was going to be released this week which should correct the
issue. We'll have to wait and see if it becomes a reality. :)