OS 4.1 FE Update 1: Expand RAM On WinUAE?

[kamelito]

It is just a WinUAE configuration problem IMO, I also got this pink screen, but after checking another person config I managed to make mine working, but it took time and it was very frustrating.

I had a fresh install of AmigaOS 4.1 FE, then I manually downloaded the update and installed it. I was at that time using Picasso IV. I changed this to uaegfx. It seems that my problem was related to the ROM selection, don't have it in front of me be I used something like indirect uae rom.

Kamelito

Kamel

[AMIGASYSTEM]

Kamelito, depends on how updated your OS4.1, configuration WinUAE it has no interference or fault

[Toni Wilen]

Lots of talk, no useful information whatsoever..

And stop suggesting that stupid library replacement hack. It is not a fix!

[AMIGASYSTEM]

Ciao Toni, excuse me if i insist (I'm not talking about stupid library), no chatter, but the result of a number of practical tests with "OS41FE" It is the problem screen PINK It was always caused by "KickLayout-A4000 53.2 (10.9.2011)", replaced with KickLayout-A4000 53.2 (03.11.2014) OS4.1 It has always started without problems.

[Toni Wilen]

Obviously it isn't the reason because there are lots of people that run it fine, without ugly hacks.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Obviously it isn't the reason because there are lots of people that run it fine, without ugly hacks.

Toni I have not had any problem because I had OS4.1 updated, those who have a version of OS4.1 outdated it has this problem, my tests were done on PC Friends who had these versions of OS4.1.
What I do not understand is why KickLayout v.53.2 they have different creation date

[elowan]

Originally Posted by AMIGASYSTEM

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

I tried SYS:C/BootLoader COMMANDLINE = "NoRamPager" and still no RAM...
Deleting the "C:" and just keeping BootLoader COMMANDLINE = "NoRamPager" results in a not booting system for me...

[AMIGASYSTEM]

If the RAM does not appear it means that the upgrade has not been successful, repeat update with these steps:

- OS41FE.HDF Set as -> Accelerator (Cyberstorm PPC)
- Unzip "AmigaOS4.1FinalEditionUpdate.LHA"
- Copy Dir FinalEditionUpdate to HardFile OS4.1(if you have problems using OS3)
- Start Update by HardFile OS4.1
- Add Startup-sequence (BootLoader COMMANDLINE = "NoRamPager")

If you Pink screen follow as mentioned above

[elowan]

hmmm, I think I did everything, like youii said.

but after I set "BootLoader COMMANDLINE = "NoRamPager" withe trhe "C:" , system does not boot anymore -> amigha dos shell, somethign like CD not found 20 error...

I give this shit up, man!

[AMIGASYSTEM]

Perhaps you made a mistake in writing the command!
Add Hardfile OS4.1 on other OS Amiga and edit Startup-sequence

[DarrenHD]

Originally Posted by elowan

hmmm, I think I did everything, like youii said.

but after I set "BootLoader COMMANDLINE = "NoRamPager" withe trhe "C:" , system does not boot anymore -> amigha dos shell, somethign like CD not found 20 error...

I give this shit up, man!

C:Bootloader COMMANDLINE="NORAMPAGER"

...exactly typed like that....should work.

[AMIGASYSTEM]

Yes DarrenHD, important there is not the space

[Snake79]

Yeah. Here's proof example.

[AMIGASYSTEM]

Equals nothing change even without c:

[UncleSpam]

It works this way as well:

C:BootLoader COMMANDLINE NORAMPAGER

[AMIGASYSTEM]

Same as above

[elowan]

hmmm, I did another install and upodate, but still no RAM

check out S-S entry and then, in WB-topbar there is no "...Update 1" showing, just "OS 4.1 FE"

so I assume, the update itself did not even install???

I let it install to "SYS:" (I made no changes to the path in installer)

[AMIGASYSTEM]

Originally Posted by elowan

so I assume, the update itself did not even install???

I let it install to "SYS:" (I made no changes to the path in installer)

You have performed step by step my suggestion?

- OS41FE.HDF Set as -> Accelerator (Cyberstorm PPC)
- Unzip "AmigaOS4.1FinalEditionUpdate.LHA" 
- Copy Dir FinalEditionUpdate to HardFile OS4.1(if you have problems using OS3)
- Start Update by HardFile OS4.1

You can check version Kickstart and Workbench (see screenshot)

[elowan]

Originally Posted by AMIGASYSTEM

You have performed step by step my suggestion?

- OS41FE.HDF Set as -> Accelerator (Cyberstorm PPC)
- Unzip "AmigaOS4.1FinalEditionUpdate.LHA" 
- Copy Dir FinalEditionUpdate to HardFile OS4.1(if you have problems using OS3)
- Start Update by HardFile OS4.1

Yes, I have - exept for this: Copy Dir FinalEditionUpdate to HardFile OS4.1
I have the unzipped installer on my "Windows-swap folder", that is connected to OS4.1 (I setup a Harddrive-folder in WinUAE for transfering files)
and I started installer from there. But I think, this does not matter, cause installer got "SYS:" path for install the update...

I will check the kickstart version...

[AMIGASYSTEM]

Originally Posted by elowan

I have the unzipped installer on my "Windows-swap folder", that is connected to OS4.1
I will check the kickstart version...

No this is not good, so the process is very slow and can cause errors even you can get on the filesystem corruption on OS4.1 if you use HD controller UAE (there is a way to avoid, but never mind)

To be sure of setup, you must first copy the Update folder on HD OS4.1 and only then do the setup.