10 January 2017, 17:02 | #1 |
Registered User
Join Date: Dec 2012
Location: Atlanta, USA
Posts: 154
|
Guide for installing 4.1FE update 1 and altering config after?
Is there a guide for those with a working OS4.1FE (non-update1) to install the update from within a current setup, then after reboot, making the alterations needed to take advantage of the new features?
I was able to get the update1 file from amiupdate (halting extraction/auto-install and copying the lha archive), but when I run it after extracting to the harddrive, all goes well, but after reboot, it is stuck on pink screen. Will try to gather a log shortly. Just curious if this means something obvious. Thanks! |
10 January 2017, 19:23 | #2 |
Amithlon Fanatic
Join Date: Aug 2015
Location: Lexington, SC / US
Posts: 782
|
I'm don't know why a few are having issues (locked on pink screen at boot) but I'd seriously just try a new config and new install of 4.1. It doesn't take that long to setup and see if there was something in your OS 4.1 changes that was causing the issue or not.
Start a basic config, just enough to get the system up and running. You can always "add" more hardware to the config just like doing so to a real Amiga |
10 January 2017, 19:52 | #3 |
Posts: n/a
|
+1 to SnkBitten's comment above. I suspect a lot of this has to do with some sort of custom configuraiton - bus boards, maybe GREX, who knows. I was able to make this work consistently with a relatively "basic" initial OS4.1FE Classic installation using PIV and A2065 as my only real add-ons.
That said, don't add the extra Z3 memory until you're able to update the S:Startup-Sequence line. |
12 January 2017, 08:46 | #4 |
Registered User
Join Date: Nov 2014
Location: FT Lewis, WA
Posts: 374
|
I've had issues with pink screen and rebooting over and over with OS4.1FE ... It always came back to a RAM issue. Move RAM to the minimum amt to run the emulation and as esc states don't add the extra mem until the update is completed.
Last edited by DH; 14 November 2017 at 17:25. Reason: Deleted direct signature |
19 January 2017, 06:04 | #5 |
Registered User
Join Date: Aug 2014
Location: New Jersey / USA
Posts: 105
|
I was having the same issue (pink screen) until I configured 4 banks of Z3 of 512MB, 256MB, 128MB and 64MB. Make sure you keep chip memory at 2MB and zero out everything else except Z3 Ran. Also in the card order Put Z3 first followed by everything else.
|
21 January 2017, 19:45 | #6 |
Registered User
Join Date: Oct 2005
Location: russia/moskow
Age: 44
Posts: 181
|
Pink screen issues is mostly related to your x86 config and windows you use. For example on some old notebook , WinXP and 32bit winuae i can have only 128mb of z3 ram, anything else or more -> pink screens and co.
But, exactly the same config (i mean 1:1 exactly the same), but on windows7 and more recent x86, give me ability to use 768mb of z3 ram (more -> pink screens). So, you better have fast and last enough x86, something like 64 bit windows and 64 bit version of winuae, then you can have even more than 1gb of z3 ram without pink screens. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Guide] Installing AmigaOS 4.1 with FS-UAE | amigafreak68k | support.FS-UAE | 104 | 21 December 2022 00:04 |
[Guide] Installing AmigaOS 3.9 with FS-UAE | nexusle | support.FS-UAE | 30 | 23 November 2017 17:49 |
Installing 3.9 and 4.1FE - please help!! | SpaceFlightO | support.FS-UAE | 3 | 02 July 2016 09:51 |
Guide to installing OS3.9 in Winuae then transfering to real amiga | trydowave | support.Hardware | 2 | 26 September 2013 11:14 |
idots guide to installing workbench 3.0 | JACK98 | support.Apps | 4 | 12 January 2009 22:17 |
|
|