OS4.1 FE classic installation gives me black screen!

[jonssonj]

Hello!

I'm trying to do a install of my newly bought OS4.1 Classic in WinUAE beta 7. I have created the Bootfloppy from the CD and booting up with floppy and then the CD.

After a while I'm greeted with a picture "Amiga 4.1 ... " and then the processor switch over to the PPC one and I'm greeted with another picture of "Amiga 4.1 ...". This picture is visible, maybe 10 seconds, and then I get a black screen.

WinUAE Says that the PPC is running, 68K stop and FPS is jumping between 59 and 61, but nothing else happens. It does not read from the CD, and it does not read from the floppy.

I have attached config and log. I would be very grateful if I could get a hint of what I'm doing wrong.

BR
Jörgen Jönsson


winuae_debug.zip

OS4.1 Classics.uae

[Toni Wilen]

Remove A4091. (I don't know if it is supposed to do that)

[jonssonj]

Ok I did that and then the installation worked. Thanks Toni!

BR
Jörgen

[Toni Wilen]

I debugged this a bit more (with older 4.1 version).

It seems some A4091 driver runs (m68k emulated A4091 ROM code?) at that point which tries to reset the chip and it was not handled correctly.

After fixing it, driver does more chip init and then finally points NCR chip SCRIPTS DMA pointer to non-existing RAM (0x3fxxxxxx region, perhaps this is PPC CPU MMU remapped logical address, not physical which hardware needs) and starts SCRIPTS DMA which of course won't work very well.

Probably OS4.x "feature".

[Khylrion]

I have the same problem, but removing A4091 did not solve it for me.
Have tried a myriad of different options now and that's why I am turning to the experts now :-).

If you prefer, I can of course make my own thread.

thanks in advance Toni and team!

[FOL]

Originally Posted by Khylrion

I have the same problem, but removing A4091 did not solve it for me.
Have tried a myriad of different options now and that's why I am turning to the experts now :-).

If you prefer, I can of course make my own thread.

thanks in advance Toni and team!

You have a different issue. As his was getting stuck after starting to boot OS4.1. Yours is getting stuck as soon as its loaded the OS4.1 ROM Modules and Kernel.

Silly question, as I get stuck on pink screen sometimes. Have you done a soft reset?
This tends to solve the issue for me.

[Toni Wilen]

Yes, it is different. UAE Boot ROM is enabled. You have some UAE expansion enabled. All of them MUST be disabled. (hardfile, directory harddrive, uaeserial, bsdsocket, uaenet etc..)

[Khylrion]

Originally Posted by FOL

You have a different issue. As his was getting stuck after starting to boot OS4.1. Yours is getting stuck as soon as its loaded the OS4.1 ROM Modules and Kernel.

Silly question, as I get stuck on pink screen sometimes. Have you done a soft reset?
This tends to solve the issue for me.

apologise, had so many tabs open I did end up posting in the wrong one :/

I have done many hard and soft resets from within winUAE. Or are you referring to a different method?

Originally Posted by Toni Wilen

Yes, it is different. UAE Boot ROM is enabled. You have some UAE expansion enabled. All of them MUST be disabled. (hardfile, directory harddrive, uaeserial, bsdsocket, uaenet etc..)

Thanks as well for the quick feedback!

I am not sure how to proceed with disabling all the expansions, as all the guides do mention the use of a hardfile for instance.

does that mean I can't use the PIV graphic card either? I don't understand why all this seems to work for everyone else, but just a few of us are stuck in this pink bootscreen.

Will try disabling all expansions and try it like that.

[Toni Wilen]

You can't use "UAE" controller hardfiles. All hardware emulated devices are fine. (mainboard IDE, CSPPC SCSI and so on)

[Khylrion]

interesting fact, even though I have disabled all expansions (no RTG card, no UAESCSI.device) after I start the machine, the expansion UAESCSI.device is checked after all.

will see if switching to IDE without any expansions brings anything.

even when I disable the internal SCSI Hardware in the Adv. Chipset, even when I put configure all my harddrives as IDE, ... the expansion still starts the uaescsi.device when I start the machine (and it is disabled in my config).

for some odd reason I do have to select a SCSI ROM file (in ROM settings) and I have now tried with the A2091 with the ROM Disabled.

Not sure what more I can try here :/

[Toni Wilen]

No config file but my crystal ball says you have some harddrives panel option enabled, like CDFS automount.

[Khylrion]

Originally Posted by Toni Wilen

No config file but my crystal ball says you have some harddrives panel option enabled, like CDFS automount.

that is the only option I have enabled indeed :-).

without it he can't find from CDROM to boot AOS4.1 FE.

[Toni Wilen]

You are doing it wrong. I am 100% sure no guide asked you to enable it or use it.

Add CD as IDE1 or CSPPC SCSI CD unit. Then add the CD (image or CD drive letter) using CD drive/image select box in CD&HardDrives panel.

[Khylrion]

Originally Posted by Toni Wilen

You are doing it wrong. I am 100% sure no guide asked you to enable it or use it.

Add CD as IDE1 or CSPPC SCSI CD unit. Then add the CD (image or CD drive letter) using CD drive/image select box in CD&HardDrives panel.

that is exactly what I did and the only way I was able to boot was to automount it.

Tried all versions of SCSI, IDE as well.

So you are saying that this automount is the rootcause for hanging at the pink screen?

what could a reason be that the CD does not boot from either image or physical disk (and only works with automount?)

[Toni Wilen]

Pink screen = any UAE device enabled, any non-proper hardware configuration. Don't do it.

No "normal" Amiga boots CDs. (Only exceptions are CD32/CDTV). CSPPC can also also boot CDs if configured to do so. (Instructions in some other thread, nothing to do with emulation)

Or use boot disk.

[Khylrion]

Originally Posted by Toni Wilen

Pink screen = any UAE device enabled, any non-proper hardware configuration. Don't do it.

No "normal" Amiga boots CDs. (Only exceptions are CD32/CDTV). CSPPC can also also boot CDs if configured to do so. (Instructions in some other thread, nothing to do with emulation)

Or use boot disk.

ah sorry should have highlighted that I am using the bootfloppy.adf from the OS4.1 FE cd.

let me rephrase my question: what could the reason be that the bootfloppy can't start the OS4.1 FE CD (when automount is not enabled) using winUAE?

[Toni Wilen]

This is so called crystall ball answer because I still can't find your config file: you use IDE but you have CD connected to IDE splitter (IDE unit 2 or 3) which is not available until installation has been completed.

Use CSPPC SCSI. Much faster. Not limited to two units.

[Khylrion]

Originally Posted by Toni Wilen

This is so called crystall ball answer because I still can't find your config file: you use IDE but you have CD connected to IDE splitter (IDE unit 2 or 3) which is not available until installation has been completed.

Use CSPPC SCSI. Much faster. Not limited to two units.

First of all thank you for your quick feedback!

Second of all, thanks for the amazing piece of software, allowing me to relive the computer that kickstarted my interest in computers :-)
You sir, are pretty awesome!

thanks to your guidance I have now managed to go beyond the pink screen but it appears to be hanging on a black screen now.
Will check the logs for more details and then add my config as well.

[Khylrion]

attached my fresh logs and the last working config where I don't have the pink.

Any assistance is more than appreciated!

[Toni Wilen]

Config immediately shows the problem.

You don't emulate proper A4000. Tick compatible Settings in Adv. Chipset and change Chipset extra to A4000 in Chipset panel.

OS4 tries to detect A4000 IDE drives but because there is no IDE hardware emulation, it gets stuck..

Also for some reason Picasso IV is not autoconfigured by OS4, disable Z3 RAM first, if it appears now, add smaller Z3 RAM.

HD config looks fine now.