Now when I finally can run MOS on my A4000/604/233 I cant figure out how to extract lha files from linux!! Someone?
How about a lzh packet iso download?

Did it with AROS linux-hosted!!!
Now the problem is that I dont have a PAL screen connection!! ARGH!!!
Ill see if I can find it tomorrow. Cause there is no way to install MOS without PAL/NTSC mode is there?

Ok! I installed a second HD to A4k, made a bootable ffs partition, copied the files from the CD over and changed the startup sequense, removed the AmigaOS HD leaving the MOS one the only one left, and started the computer.
But it loads until the morphOS logo shows up, and then it just stops leaving no display on my SVGA at all.
Any ideas?
PPC604e/233/68k40/25/cvision64/about 50mb ram(I dont know exactly since I have not used the device for years)

Now when booting with amigaOS HD plugged in as master and MOS slave the drive is not mounted but shows up correctly in HDtoolbox.
Hmmm.
Can it be something wrong with the drive perhaps?

Quote:
What version of FFS did you use for that? V45 FFS (ie. the one in 3.5/3.9) is not recommended and can cause problems.

Quote:
Well, if you see the boot logo, you're already progressing because the video drivers got loaded, which are on the disk, so it's a sign that MorphOS PPC kernel practically started, just processing the startup-sequence got stuck for some reasons.

Quote:
Hmm, strange, so the bootlogo disappears, and you get no Ambient screen? Shouldn't happen, but everything is possible. :)

Anyway, in case of any problems, you could get a serial cable, hook up on the serial port of your Amiga, and see where it goes mad in a terminal on a remote computer. (Remove ramdebug argument from boot command. 115200 8N1 are serial settings by default.)

Another alternative to try booting from the CD-ROM itself. If that works, there's some trouble with the HDD setup. Remove (comment out) bootdevice argument, and there you go.

Quote:
Most "old" Amiga don't support that !

I suggest you to look at my old messages about MOS PUP and its solutions

50 Mb is a bit short and strange ram configuration :
2 mb AGA + 32 Mb FAST on CPPC + 16 Mb on the mobo ?
You should remove your ram on the mobo and put it on the CPPC.

Have you "ticked" your MOS partition as "Bootable" ? do you have the real Kick 3.1 ?
etc ...

I cant boot from cdrom because I dont have a PAL setup to see the bootoptions
I dont know exactly what simms is installed. but workbench shows about 48mb fast available. Ill check later. Does MOS use the fastram on the mobo?
Rom 3.1
No bootdevice argument ("") But it starts booting apparantly.
The drive is bootable priority 0, and MOS partition is the only bootable one.
However, I have had problems with the drive. I tried to install ubuntu on it but it failed. But it didnt complain when I had it formated.
Thanks for the response.
I hope I become a MOSer this evening.

@Dolen
Remove the fastram installed in your mother board. With older MOS versions it prevented the A4000 from booting, maybe it's fixed now that more than 128MB are allowed.

48MB is not much but I guess it should be enough to boot.

Put the kickstart in the MOS drive and put the path in the settings. Remove the fake klickstart.

@Chain-Q:
It may be a good idea to include another skin (and mui settings) because the default one includes lots of gradients and textures everywhere and people complains about it being slow.

Tried without fast on mobo, acts the same.
Now Ill try with nofake kick
Now its down to 32mb fast total.

[ Edited by dolen on 2006/2/25 16:53 ]

How do I copy the rom3.1 to the HD?

@Crumb
Quote:
I like the idea. Bug JoBBo about this... He creates the face of MorphOS nowadays.

Quote:
There are various utilities for this. For example in the BlizKick archive. Aminet.

@Dolen

just noticed this

"PPC604e/233/68k40/25/cvision64"

do you have a CV64 or a CV643D?

If its a 3D model, you have to rename the CVision3D.Z3 in "SYS:Morphos/Devs/" to "CVision3D" or anyway, delete all the others.

A 15 Khz monitor/tv tied to the Amiga Video port, could help to see what happen.

PS- ah . . reinstall the 16 MB on the mobo. Theres no problem at all, to leave it in place. (since the first version)

[ Edited by Framiga on 2006/2/26 15:15 ]

@Framiga

The 16MB on the motherboard prevented the A4000 I tried from booting, maybe because the csppc was already populated with 128MB.

Deleted all but cvision64 (I dont have the 3d) and it acts the same. The computer just stops loading and gives no signal to the screen directly after it shows the bootscreen. The graphix seems to work since it shows the logo at bootup. Its just the ambient which doesnt show up.
Is there any funktion key or somethin I could try to see if it reacts even though the ambient is not viewable?

@Crumb

128+16MB here + 8MB 16bit on TBCPlus thats obviously are not seen by MOS.

So please avoid statements that adds only confusion to the users.

@dolen

the only suggestion, still to connect a 15 Khz monitor to the Amiga RGB port.

When i've added my CV64 to the MOS system (via CGXrc6) the system booted on a sort of "emergency state"(?) in PAL mode (i "think" promoted by the other GFX card -CVPPC) due the lack of a couple enviroment CV64 related (don't remember now)

Honestly, its hard to help in this very "weird" enviroment, seen the poor/not existing support by the authors. (like we were well aware since the beginning)

Your problem "seems" a little different by the one reported by other users, seen that you can see the boot logo, hence MOS kernel its already up/running.

@framiga

fine for you, but the GREX4000D+CSPPC of a friend didn't work if the motherboard had ram. I'm not claiming anything without having actually tried it.

I want to see if the system reacts, is there a keycombination that makes the HD do something, or maybe I could just insert a floppie and see. Does MOS read floppies automaticly?

but... don't you have at least AmigaOS3.x working?

3.1 runs fine

[ Edited by dolen on 2006/2/26 20:56 ]

Quote:
Actually, this is not 100% correct. Chain-Q has replied a couple of times to this thread, too (and to others), and he is the mantainer of the PuP version.
Although I understand hooking up via serial a PC and send him the debug log like he suggested isn't exactly the easiest thing to do, it would help quite a lot!

Kind regards,
Andrea

Quote:
Yes, that would help the most. Without that, it's quite hard to figure out, where exactly the startup stops on MorphOS 1.4.x. Doing that a lot's more clever thing than applying all kinds of black magic to figure out the problem. Anyway, i never tested MOSPUP with less than 64MB memory. So i don't exactly know, where it could stop with less memory, or if it will work at all. Maybe i'll do a test with 32MB sometime soon...

Quote:
It only supports floppy disk operation in Kickstart mode. With nokickstart, it won't support floppy drives.