This is my first post here. I'd like to ask you a few things about the MorphOS PUP version.
I have an A1200 with 603/175-040/25 192MB RAM, Bvision, Fast ATA MK-II, 3.1 ROM installed and a hard disk with two bootable partion. The first partition has FFS 45.14 and OS3.9 BB2 installed, and the second SFS 2.2 68K and the latest MorphOS PUP version installed.

When I boot from the MorphOS it gives me nothing. Make the first reboot, and after that a black screen comes up, and no signal to the monitor.

I tried all the reset levels, I removed the fakerom from the boot/roms folder. I even tried with a 3.1 ROM kickstart file. No change. I tried to remove the Ram sims one at a time, still the same results. I also tried the idehack module with the same results. No MorphOS Logo at the boot.

Is there anything else I could try? Do you know what should I do?

Thanks for your time...

Quote:
My first bet are the filesystems. FFS v45 is known to cause problems under MorphOS. Also, SFS 2 was never tested under MorphOS, and who knows what it could cause. I now dropped it on my "to test" list.

Quote:
Hook up your Amiga via a serial port to another computer, turn off ramdebug in your startup command (remove the ramdebug argument), and send the serial log to me. That could result a more exact report where the boot procedure stops.

Thanks for your faaaast reply!
I also tried with SFS v.1.252, but I had the same results. Black screen.

Do you know if the FastATA MKII works with MorphOS. I mean if there is someone who succesfully uses it?

I never before used the serial port the you mention. So, all I have to do is to make the changes you mention in the startup sequence,plug the serial cable to my amiga and a PC, probably. Should I start any program at the PC? Maybe a telnet? And what should I do next?

Sorry for disturbing you, and thanks for your help

just to let you know both PFS3 and the latest version of SFS on the boot patition work fine on my 1200PPC no FastATA tho

what boot priorty do you have for Morphos if it isnt higher than workbench you will have to change the startup or just raise the boot priorty of the MorphOS partition just to see if you get a sucessfull boot

Quote:
Well, there's no direct FastATA support in MorphOS, but i know users who use their FastATA with MorphOS (in slow mode, since there's no driver). So in general, it shouldn't cause a problem. For safety, try to use only first channel of the FastATA controller with MorphOS, when solving boot problems.

Quote:
MorphOS dumps debug output to serial port, when booting and if this feature is not disabled in the startup command, as it is by default. You need to connect your computers together with a serial link cable (a.k.a. serial file transfer cable). Normal modem cables won't do, but most good PC shops should have the proper cables for this job. Then you need to start a terminal software on your "remote" computer. I usually debug MOSPUP using my Amiga 2000/060, so i use DreamTerm for this. On Windows you can use HyperTerminal. That's included with some versions of Windows at least, if i remember correctly. Maybe someone else can recommend a better terminal app, as i don't use Windows, so i don't know many apps for it. On Linux, you can use Minicom for example. You need to setup that software of course properly to receive data on the serial port, with speed 115200, settings 8N1. (This cryptic code will be obvious if you look at the setup of your terminal software, i hope... ).

Then, you need to start MorphOS on your Amiga, and then look for the output you receive in the terminal app. I hope this short description makes things a few more clear. You can also search the internet for more references about various serial cables, to see the whole spot, and get the proper one.

I have FastATA MK-III in my setUo and MOS booting without any problem..and have two HDD and CDRW connected to FastATA!

thank you all for your replies

@Chain-Q
I'll try today to gather those info you want from the serial. I'll post them here as soon as possible

> FFS v45 is known to cause problems under MorphOS.

But its never used by MorphOS because the native FFS has a higher version. FWIW, I have partitions using muFS and that FS is based on FFS v45. Everything works well.
And the version number is the key for SFS as well: the MorphOS SFS version is 1.210 thus you need a lower version in the RDB (maybe its enough to pretend its an older version). With 1.84 in the RDB MorphOS boots, with 1.254 in the RDB the system doesn't boot.

mhhhh! i doubt it (no offence)

Installed times ago (for testing pourpose) SFS 1.236 as boot partition and worked perfectly (otherwise 1.252 gives me some minor problems- no "disk.info" icons displayed).

Hence, its always the version in RDB that have the higher priority.

To see working a SFS 1.210(native) partition (not as boot), i have used a spare IDE disk with NO SFS in RDB.

Your theory, is valid if 2 different SFS versions are in RDB. The system will use the newer one.

EDIT- IMHO "probably" is the latest SFS 1.252 that gives problems on MOS ...don't ask "me" why


[ Edited by Framiga on 2006/3/28 12:27 ]

Quote:
What did c:version full <partitionname> output when run from MorphOS? If 1.236 was in the RDB, then it should be used for SFS partitions. And you need a SFS in the RDB or you can't boot the partition ;-)

Quote:
Nope. The highest version wins regardless where it comes from. You can safely put the latest and greatest SFS version for OS3 into the RDB just pretend its 1.209. That works for me.

Quote:
You can only have one(!) FS per DosType in the RDB.

Quote:
There is 1.254. See above how to install it into the RDB.

interesting! i'll try Thanks

EDIT- spoofing the SFS version as 1.209 in HDToolbox did the trick. Thanks again

I'm trying to understand if theres differences in performances compared to PFS3 but they "seems" about the same.

[ Edited by Framiga on 2006/3/28 16:44 ]