OS 4.1 FE Update 1: Expand RAM On WinUAE?

[Seiya]

Working!!
i have copied manually every files except the "kickstart" drawer.


Now i have Amiga OS 4.1 update 1, but, with only 768 MB+64 MB MotherBoard RAM.
if i set 512MB or 1 GB on single Z3 slot (or use 256 MB in 4 slot to have 1 GB) i have this screen:




However now it works..
However i like to install update 1 from installer..

[Toni Wilen]

Usual suggestion is to remove all expansions that are not needed for booting (Z3, PIV, A2065, 64M MB RAM). Also switch off JIT, it is useless in OS4 emulation. Finally use non-modified CSPPC ROM file. Does it still hang identically? What if you disable UAE boot ROM completely?

[Toni Wilen]

Originally Posted by Seiya

Working!!
i have copied manually every files except the "kickstart" drawer.

I don't count this as "working"..

Now i have Amiga OS 4.1 update 1, but, with only 768 MB+64 MB MotherBoard RAM.
if i set 512MB or 1 GB on single Z3 slot (or use 256 MB in 4 slot to have 1 GB) i have this screen:

Check Hardware Info GUI panel. You probably run out of Z3 space.

[Seiya]

i found the 2 file that block OS4 loading on pink screen.
"graphics.library.kmod" and "intuition.library.kmod"

what you mean complete disable uae boot rom?

however i have complete remove Z3 memory, motherboard RAM, A2065 (i have copied all files of update 1) and i have pink screem.
i have replaced cyberstorm ppc default rom with cyberstormppc_44.71.rom, but the same result

copying all files of update 1 except "intuition and graphics" it works

[Toni Wilen]

Originally Posted by Seiya

what you mean complete disable uae boot rom?

ROM -> Board type = ROM disabled. (at the bottom of panel). This of course breaks all UAE expansions.

[Seiya]

with rom disabled i have the same pink screen..

however, even if it's not a valid solution, i have find a way to have a working update 1 even if it's absurd that an installation make so big problems when the original OS 4.1 FE working very well.

maybe one day i can to retry again.
for now i have other amiga project to finish

[elowan]

Originally Posted by DarrenHD

You can also try not using/configuring a PCI busboard (Mediator/GREX). Those use up Zorro III address space.

Try with Picasso IV and C= 2065 emulated with ethernet.device, it will use less address space and then try to add 256MB Zorro III memory.

CS PPC Boot menu is accessed by holding down the ESC key immdiately after starting WinUAE. In the "System" option there is an option to MapROM. Make sure it is OFF.

Thank you DarrenHD - I took a look at the system settings - MapROM was turned off

Is there known fix for powerpc side not starting when you have Amigaos4.1 Final edition installed?
Emulator starts, but then it throws 8000 0008 Guru Mediation. I can only start system when i remove my hardfile and use installation CD to start ppc emulation. Then i can add hardfile back and start Amigaos 4.1 form hardfile.

WinUAE version 3.4.0 (2016.12.21) in use.

[Toni Wilen]

Originally Posted by rateoni

Is there known fix for powerpc side not starting when you have Amigaos4.1 Final edition installed?
Emulator starts, but then it throws 8000 0008 Guru Mediation. I can only start system when i remove my hardfile and use installation CD to start ppc emulation. Then i can add hardfile back and start Amigaos 4.1 form hardfile.

WinUAE version 3.4.0 (2016.12.21) in use.

Standard answer: not enough information. Required info is config and logs (see older posts for more information).

[elowan]

I just installed update 1 over the already updated system - but it still does not recocnise the Z3 extra RAM. but at least, it boots.

If I install Update 1 on the not updated 4.1 system, it does not boot anymore (pink screen, like I wrote a few pages ago...)

After trying all hints and suggestions, there is only a complete new-install left, which is very sad...

Seems like Update 1 and extra RAM does not work for every 4.1FE install around, as there were some people, that get pink screens and whatnot.

Maybe there will be some fix to the update 1 or update 1.1 around the corner? I do not think, it´s WinUAE´s "fault"


cheers

[Seiya]

intuition.library.kmod and graphics.library.kmod cause the pink screen.
if you delete it after install update 1 or you make a manual installation and avoid to copy on the system, your update 1 will works

[Toni Wilen]

Originally Posted by Seiya

intuition.library.kmod and graphics.library.kmod cause the pink screen.
if you delete it after install update 1 or you make a manual installation and avoid to copy on the system, your update 1 will works

But remember that: You are not allowed to report any UAE related problems as long as any unsupported hack(s) are in use. Trying to do that without also including that you are using unsupported OS setup: I'll get very annoyed.

Hi,
I'm a new member but a long time amiga user. In order to use the Fe update 1 I had to change my HD controller to IDE(auto) and it booted right up. With HD controller set to cyberstorm ppc the system would hang at the pink screen every time.

I hope this helps. Good luck.

[elowan]

Originally Posted by Doyle01

Hi,
I'm a new member but a long time amiga user. In order to use the Fe update 1 I had to change my HD controller to IDE(auto) and it booted right up. With HD controller set to cyberstorm ppc the system would hang at the pink screen every time.

I hope this helps. Good luck.

sounds interesting, I will see, if this work for me, too !

Thanks for this information!

[Toni Wilen]

Some clues finally..

Include logs from "original" version and update #1 with -scsiemulog command line parameter. It should show some differences if it really is SCSI related.

[elowan]

Ok - I installed Upd. 1 once again - this time, I did not let the installer/system do the restart. I let WinUAE restart and now no pink-scree-issue anymore - BUT no RAM, also

I edited startup-sequence, set "IDE" instead of "cyberstrom accelerator", as suggested and added a medium amout of Z3 ram, of course!

[SnkBitten]

Originally Posted by elowan

Ok - I installed Upd. 1 once again - this time, I did not let the installer/system do the restart. I let WinUAE restart and now no pink-scree-issue anymore - BUT no RAM, also

I edited startup-sequence, set "IDE" instead of "cyberstrom accelerator", as suggested and added a medium amout of Z3 ram, of course!

and you remembered to edit your s:startup-sequence to add the commandline option to the bootloader?

C: BootLoader COMMANDLINE = "NoRamPager"

[elowan]

yes of course - you can see it in the image, btw

[AMIGASYSTEM]

Originally Posted by elowan

I let WinUAE restart and now no pink-scree-issue anymore - BUT no RAM, also

Delete C: (or Add SYS:C/), leave the command without the path, in this way you will see the added RAM

BootLoader COMMANDLINE = "NoRamPager"

If its interesting to someone found the cause of PINK screen lock after update 1

[Seiya]

i have pink screen without bootloader setting :P

maybe now we have (me and AmigaSystem) found the problem of pink screen.

in update 1 there is a kicklayout v53.2 2011 that is incompatibile with

intuition.library.kmod and graphics.library.kmod

new v53.2 2014 is compatible.