Ok.

I have a A4000D (KS3.1,OS3.9) with a CSPPC and a Cybervision 64 + AdrianeII network card.

I have 4 partitions on my IDE harddrive. (IDH0,1,2,3). I have copied the content of the latest version over to IDH3). And placed a kick.rom file (made a copy of my kickstart through Amiga Explorer) in IDH3:DEVS/Kick.rom.

MorphOS wont boot. It boots a little, and then i get a AmigaDOS screen saying "startup failed returncode 10"

My startup-sequence is:

;
; This is the MorphOS loader startup-sequence. If you set the MorphOS partition as bootable,
; this file would cause MorphOS to get loaded on boot automaticly.
;
; By default MorphOS boots without using the ROM contents of your Amiga. If you wish to
; make it use the kickstart contents (to be able to use trackdisk.device for example)
; please follow those steps:
;
; 1) Check if you have a correct kickstart file:
; The Kickstart version required are:
; Amiga4000/4000T/3000 - 40.68 or 40.70
; Amiga1200 - 40.68
; Is is advised that you use the unpatched ROM files
;
; 2) Move or delete fakerom.elf from boot/extmoudles
;
; 3) Change the kickstart variable, remember to tune the file path

set kickstart "kickstart=IDH3:Devs:Kick.rom"
;set kickstart "nokickstart"

; Bootdevice can be used to specify the MorphOS partition if you have more than one
; bootable partition and the MorphOS one doesn't have the highest boot priority. Remember
; to use partition names, not volume names! This option requires the 'bootdevice' keyword
; like in the example below:
; set bootdevice "bootdevice=DH1"
; Leave the var blank if you want to boot from the default boot partition!

set bootdevice "IDH3"

; The resetlevel and delay variables are there for you to tweak if MorphOS startup doesn't
; reboot the machine properly after loading MorphOS files.
;
; The possible resetlevel values are:
; 0 exec/coldreboot (System Reboot)
; 1 MMU switch off + normal reset in chipram (default)
; 2 MMU switch off + double reset in chipram
; 3 MMU switch off + Cyberstorm HW Reset in chipram
; 4 for (;;);..waiting for manual reset by your hands:-)
; 5 MMU switch off + normal reset in fastram
; 6 MMU switch off + double reset in fastram
; 7 MMU switch off + Cyberstorm HW Reset in fastram
;
; NOTE: most common setting for BlizzardPPC is resetlevel 1 and 5 for CyberStormPPC!

set resetlevel 5
set delay 1

; Load the MorphOS loader!

cd sys:boot
startup hal=roms/hal.com1 kernel=roms/kernel.com1 abox=roms/abox2.com1 module=roms/module.com1 resetlevel=$resetlevel ramdebug verbose debug EDebugFlags="NoLogServer NoLogWindow" sumkick disableled delay=$delay extmodules=extmodules/#? $bootdevice $kickstart >NIL:

Thanks in advance!

[ Edited by JohnFante on 2006/9/17 12:40 ]

I saw 2 errors in your startup-sequence:

Quote:

set kickstart "kickstart=Devs:Kick.rom"

Quote:

set bootdevice "bootdevice=IDH3"




[ Edited by DJBase on 2006/9/16 16:34 ]

Thanks!

That helped a bit. Now it boots for a short while, the screen blinks (I have a monitor that can show both AGA and Hi-res screenmodes), the HD light is turned on for a couple of seconds and then it halts.

I have nothing enabled in my CSPPC.

I use normal FFS (default).

If you remove the >NIL: maybe it will give an output.

Now it shows a Dos screen saying MorphOS is starting up.

After a couple of seconds it is back to the black screen from before.

At least something is happening.

But you are aware that after MorphOS reboots the screen will stay black until the bootlogo will be shown? This may can take a while.

How much is a while. Are we talking minutes? I have waited 5 minutes now, and that must be to long.

I think there is another issue.

Thanks in advance.

Try using the idehack module instead, this worked for me

Thanks that worked!

Cool! MorphOS kicks ass.

I'm in the process of building a new A4000 tower with my CSPPC/CVISIONPPC and want to try MOS on it but what is this idehack module mentioned here?
I guess I will need it too

Hi
I`ve got similar problem with my A4000T CSPPC+CVPPC (blank screen after reboot) so would like to know what is this idehack module?

Quote:

Had the same problem

Please read THIS