AmigaOS 3.2.1 Update released

[sq7bti]

Originally Posted by daxb

re-edit [..] S-S after OS 3.2.1 update

spot on, thanks for prompt response.

[sq7bti]

double-post

[DisasterIncarna]

registered my key as others said using the CD, i also had zero/O issue and eventually worked, gave up even trying to contact/use hyperions forum, registered 3x and its been stuck in limbo as needing them to ok it, which they never do, and you cant contact them to mention that, email was a no-go and ofc you cant use the forum, so their forum is as good as worthless and i just gave up.

[Predseda]

Note this confusing mistake in the Hyperion website:

While no new ROM images are provided, we do not suggest that you go buy new ROMs.

but in readme inside the package it is correct:

While new ROM images are provided we do not suggest that you go buy
new physical ROMs.

[Aegis]

Weirdly, on my MiSTer, the AmigaOS 'about' box reports KS 47.57 (using the 3.2.1 ROM) - the exact same rom image and .hdf in WinUAE reports KS 47.102

[paul1981]

Originally Posted by coldacid

Hey, Windows Phone was a great platform. (I'll agree with you on the WinRT crap though.)

I loved my Windows Phone. I could do everything much faster and with less presses than my Android. I could organise everything exactly to my liking too, unlike my Android. Don't ask me about iPhone though because I haven't a clue how to use one of those things (I tried and didn't like). The best doesn't always win!

[malko]

Originally Posted by paul1981

[...] The best doesn't always win!

The Amiga knows something about it...
But it is still here

[klx300r]

awesome to see another update for my favourite OS

[Solskogen]

Originally Posted by Aegis

Weirdly, on my MiSTer, the AmigaOS 'about' box reports KS 47.57 (using the 3.2.1 ROM) - the exact same rom image and .hdf in WinUAE reports KS 47.102

You're probably not using the correct roms. 3.2.1 roms on my MiSTer gets recognized as 47.102 (workbench 47.3)

[Aegis]

Originally Posted by Solskogen

You're probably not using the correct roms. 3.2.1 roms on my MiSTer gets recognized as 47.102 (workbench 47.3)

As I mentioned, it's the exact same ROM I'm using in WinUAE (which shows it correctly as 47.102)

Edit: Ok, get this - I have three configs on my MiSTer: OS3.9 (45.57), 3.2.1 (47.102) and KS 1.3 - by default I boot OS3.9 - if I load up the other config (3.2.1) I end up with KS 47.57 (!) - it looks like the MiSTer isn't fully flushing something when switching configs. To get 3.2.1 to correctly show 47.102 I have to first load KS 1.3 then switch to the 3.2.1 config

Note that this even shows up on the 'insert disk' screen - crazy.

[cugar124]

Hi guys since the update my system is stopping at load module can anyone help please?

Sent from my Pixel 4a (5G) using Tapatalk

[Storm]

I have a similar thing happen on my A2000 with a GVP 030 card, LoadModule failed return code 10. It works fine on my A600, A1200 and A4000 though.

[bni]

For me the LoadModule also fails if I have my PCMCIA network card inserted on boot up. Without it it works. I will probably get new ROMS instead at some point.

Is LoadModule doing a soft reboot like MapROM does? I know MapROM has failed similar for me in the past

[DanyPPC]

LoadModule make a soft reboot, yes.

[bubbob42]

Make sure you have:

- any hardware controlled MapROM turned off (like MapRom-jumper on Phase5 cards)
- Add option NOMEMFKICK to loadmodule-line in startup if you're using a Blizzard card

And run the LoadModule-line included in startup by hand from shell, so the program can tell you why it actually fails.

If you need help, please provide more details about your hardware.

[torturedutopian]

Hi ! Would be cool if you filed a bug report here :
https://github.com/MiSTer-devel/Mini..._MiSTer/issues

Cheers & Happy New Year everyone !

Originally Posted by Aegis

As I mentioned, it's the exact same ROM I'm using in WinUAE (which shows it correctly as 47.102)

Edit: Ok, get this - I have three configs on my MiSTer: OS3.9 (45.57), 3.2.1 (47.102) and KS 1.3 - by default I boot OS3.9 - if I load up the other config (3.2.1) I end up with KS 47.57 (!) - it looks like the MiSTer isn't fully flushing something when switching configs. To get 3.2.1 to correctly show 47.102 I have to first load KS 1.3 then switch to the 3.2.1 config

Note that this even shows up on the 'insert disk' screen - crazy.

[torturedutopian]

Oh, you've done it already, ahah !!

[Solskogen]

It seems like the 3.2.1 roms (47.102) doesn't like 1GB of memory.
With 1GB of emulated z3 memory, RTG/P96 doesn't work with 3.2.1 kickstart. It works with 3.2 roms.

[PeterK]

I don't have a 3.2.1 Rom here for tests, but in WinUAE RAM Advanced memory settings try the Z3 mapping mode "UAE" instead of "Automatic" or "Real". Then look into "Hardware Info" and ensure that everything, inclusive RTG board, is mapped to addresses below 0x80000000, or you may get in trouble, because some programs (like my IconLib too) will reject anything above 2 GB (negative numbers) as insane for a traditional Amiga, most likely it's a wrong address. And what do you need 1 GB of memory for? I'm always happy with 128 MB here.

[Solskogen]

With the new showconfig, how can I pipe the output to a file like on 3.2?