Amiga.org
Operating System Specific Discussions => Amiga OS => Topic started by: AndyFC on April 02, 2025, 06:55:18 PM
-
Someone just shared this link on a Facebook group.
From: https://www.hyperion-entertainment.com/index.php/news
Hyperion Entertainment CVBA is proud to provide the third free update for AmigaOS 3.2.
This update includes two years’ worth of fixes and enhancements to OS 3.2.2 since the previous update.
Some of the highlights in Update 3:
ReAction classes have received numerous updates.
TextEditor now allows users to define a custom menu with macros.
12 KB of chip RAM is no longer reserved.
A new Kickstart 3.2.3 ROM.
At least 50 other fixes, including updates to DiskDoctor and HDToolbox.
-
Here are the ReleaseNotes as an AmigaGuide.
I just wrote a little more but, FFS the forum does not allow LHA attachments so my words got lost.
-
Wonderful! Isn't it when you are an an 100% Amiga user and forums bitchin about amiga file types..
X5000 over here PPC Inside / Intel Outside still! ;)
-
Great news! Thanks to all devs involved ;D
-
Intel Outside still! ;)
Never got this quote, so AMD inside, :).
Just waiting on Capitoleline to support 3.2.3 rom, so I can update my rom.
-
Awesome news! Time to update my Amiga toys...
Cheers!
D.
-
Update to AmigaOS 3.2.3 completed.
Thanks to all involved.
Cheers,
redfox
P.S. I run AmigaOS 3.2 under emulation on my OS4 system using E-UAE.
-
Just waiting on Capitoleline to support 3.2.3 rom, so I can update my rom.
Now updated...
http://capitoline.twocatsblack.com/index.php/download/ (http://capitoline.twocatsblack.com/index.php/download/)
-
Now updated...
http://capitoline.twocatsblack.com/index.php/download/ (http://capitoline.twocatsblack.com/index.php/download/)
Legend, Up and running, just backing up DH0:, :).
-
You may want to keep the old ram-handler, 'cause the new ones has weird quirks, especially if you have a habit of relabelling RAM:.
-
Can you put the extracted modules in the flash memory of a Deneb? I extracted the individual modules and loaded them to the Deneb using Luciferin, but I get a 'yellow' screen on boot. I can softkick the 47.115 ROM using Blizkick and all ok. The Deneb flash workled fine with the 47.111 modules, but its giving me 'yellow' screen on boot with 47.115
Weed
-
You may want to keep the old ram-handler, 'cause the new ones has weird quirks, especially if you have a habit of relabelling RAM:.
Who would relabel ram? Never ever thought of doing that on in 40 years.
Can you put the extracted modules in the flash memory of a Deneb? I extracted the individual modules and loaded them to the Deneb using Luciferin, but I get a 'yellow' screen on boot. I can softkick the 47.115 ROM using Blizkick and all ok. The Deneb flash workled fine with the 47.111 modules, but its giving me 'yellow' screen on boot with 47.115
Weed
It doesnt seem to extract the Exec correctly. Trying to remember what I did. As I had issues.
You tried the modules from the floppy image, they should be the same.
EDIT:- I remember now. I told it to create new rom, then added the Exec from 323 rom. Then I right clicked that and told it to extract to file. It extracted correctly and fixed my Green screen issue.
-
Who would relabel ram? Never ever thought of doing that on in 40 years.
I do.
Sometimes i call it "RamDisk" without space and sometimes e.g. "Rambo".
-
I do.
Sometimes i call it "RamDisk" without space and sometimes e.g. "Rambo".
But why?
-
One obvious reason is to get around "naive" software which doesn't work correctly with paths containing spaces.
I am a beta tester (of OS4), so I take the opposite stand - I often specifically test things against the RAM Disk to make sure I catch anything of that kind :-).
Best regards,
Niels
-
One obvious reason is to get around "naive" software which doesn't work correctly with paths containing spaces.
I am a beta tester (of OS4), so I take the opposite stand - I often specifically test things against the RAM Disk to make sure I catch anything of that kind :-).
Best regards,
Niels
Surely logic would dictate you use RAM: instead of RAM DISK:, to avoid such issues. Save messing messing around and nothing has to be done.
-
Surely logic would dictate you use RAM: instead of RAM DISK:, to avoid such issues. Save messing messing around and nothing has to be done.
Precisely my thought. Ram: has always worked as well so I don't see any problem here.
-
I have seen stuff insisting on using the volume name instead of the device name, so that even if you had specified RAM:, it would translate it to "RAM Disk:".
Best regards,
Niels
-
I have seen stuff insisting on using the volume name instead of the device name, so that even if you had specified RAM:, it would translate it to "RAM Disk:".
Best regards,
Niels
They should be shot. Thats like people using hard coded paths to say drive name:location of program. Instead of using sys:location of program.
That way, regardless of drive name, everything works.
-
They should be shot. Thats like people using hard coded paths to say drive name:location of program. Instead of using sys:location of program.
That way, regardless of drive name, everything works.
All preferences programs do expand any path to the real name, even Assigns. And yes, i hate it.
-
All preferences programs do expand any path to the real name, even Assigns. And yes, i hate it.
The reason, IIRC, is twofold.
1. If you Lock a path and then query that Lock for the path, the OS will give you the full path containing the volume name (I have a feeling some changes were made wrt this in OS4, but assigns will still be expanded)
2. You can't guarantee that the volume inserted in a device will stay the same, so using the volume name allows the OS to request the correct disk. (less of an issue these days, but historically essential)
-
All preferences programs do expand any path to the real name, even Assigns. And yes, i hate it.
I believe we did get rid of all those situations in prefs programs in OS4; the last one was WBPattern, and I think that's already 5-10 years ago.
I'd suggest reporting them as bugs also in 3.x.
Best regards,
Niels
-
I'd suggest reporting them as bugs also in 3.x.
Assuming files are on DF0: instead of Update3.2.3: is probably going to come with a lot of issues.
-
But when i want to use a generic installation and my wallpapers are on WBGFX: (SYS:Prefs/Backdrops/) Assign, i don't want a fuckup just because the boot partition is not called Workbench or System or MacintoshHD....
-
Assuming files are on DF0: instead of Update3.2.3: is probably going to come with a lot of issues.
Yeah, but I'm talking about the situation where you have saved a preference as default, e.g. (for WBPattern) with a reference to a backdrop located in SYS:Prefs/Presets/<something>/..., then you don't want "SYS:" to be converted and saved as e.g. "Workbench:" in that path, because if you copy your prefs to another boot partition, you'd have to go through them all and correct them to whatever you called that partition.
That's what we got fixed in OS4.
Best regards,
Niels
-
Anyone got a list of the full changeset / improvements / etc - i cant find them anywhere , and if the register article is anything to go by PiStorm32 would be officially supported.....
-
Anyone got a list of the full changeset / improvements / etc - i cant find them anywhere , and if the register article is anything to go by PiStorm32 would be officially supported.....
Works fine on PS32. Updated and all is working great.
-
Anyone got a list of the full changeset / improvements / etc - i cant find them anywhere , .....
the changelogs for each component are located in the ReleaseNotes folder.
I have compiled a one-file-amigaguide and attached it here
https://forum.amiga.org/index.php?topic=77131.msg862940#msg862940
be aware that all the logs have the newest changes at the end, so you'd need to scroll down each time to see if there are indeed fixes et.
-
Thanks Follett. I rebuilt the ROM and used exec from the modules.adf - works fine now.
Weed.
-
Great news that it works, but it seems like websites claiming it has specific updates for PiStorm are talking out of their proverbial . That would be big news - but its a lie as there is no mention of it in that release notes file.
-
Still waiting for an answer on this . From where im sitting the various mainstream media outlets are saying that this update has support for PiStorm. Yet there is no mention of it in the release notes. This is a big deal so why is there nothing mentioned? Why did they do this instead of supporting the different SBC in the forthcoming A1200 board ?
All this is very very messy.
-
Still waiting for an answer on this . From where im sitting the various mainstream media outlets are saying that this update has support for PiStorm. Yet there is no mention of it in the release notes. This is a big deal so why is there nothing mentioned? Why did they do this instead of supporting the different SBC in the forthcoming A1200 board ?
All this is very very messy.
Whats there to support? Pistorm works like any accelerator.
SBC? forthcoming A1200 board?
-
Who would relabel ram? Never ever thought of doing that on in 40 years.
If your entire setup was in Welsh, would you still leave an anglosaxon “RAM Disk” on the desktop?
If you read the license, you will see that it’s a requirement that you set locales according to the location of the system, and so I set mine to Norwegian, but since we have two official variants of Norwegian, but only one being supported in the OS (and thus also breaking some regulations), I had to make my own locales despite the necessary files to do so not being available. Also I had to grab some code from the leaked OS sources to fix .country and .language files. Anyhow, "RAM Disk" is not good Norwegian, as we (like all Germanic languages except one) compound words consistently without spaces, and with hyphens following acronyms, so it would have to be "RAM-disk". But I prefer "Minne", as in "Memory", it isn’t a "disk" by any means, just a file system in memory.
-
If your entire setup was in Welsh, would you still leave an anglosaxon “RAM Disk” on the desktop?
If you read the license, you will see that it’s a requirement that you set locales according to the location of the system, and so I set mine to Norwegian, but since we have two official variants of Norwegian, but only one being supported in the OS (and thus also breaking some regulations), I had to make my own locales despite the necessary files to do so not being available. Also I had to grab some code from the leaked OS sources to fix .country and .language files. Anyhow, "RAM Disk" is not good Norwegian, as we (like all Germanic languages except one) compound words consistently without spaces, and with hyphens following acronyms, so it would have to be "RAM-disk". But I prefer "Minne", as in "Memory", it isn’t a "disk" by any means, just a file system in memory.
ftp:// BAZINGA!!
-
If your entire setup was in Welsh, would you still leave an anglosaxon “RAM Disk” on the desktop?
If you read the license, you will see that it’s a requirement that you set locales according to the location of the system, and so I set mine to Norwegian, but since we have two official variants of Norwegian, but only one being supported in the OS (and thus also breaking some regulations), I had to make my own locales despite the necessary files to do so not being available. Also I had to grab some code from the leaked OS sources to fix .country and .language files. Anyhow, "RAM Disk" is not good Norwegian, as we (like all Germanic languages except one) compound words consistently without spaces, and with hyphens following acronyms, so it would have to be "RAM-disk". But I prefer "Minne", as in "Memory", it isn’t a "disk" by any means, just a file system in memory.
Welsh, why would I have my entire setup in Welsh. How do you know I'm Welsh, ;).
To be honest I could not care what RAM is labelled. I have always used RAM: and never thought twice about it.
I must be the luckiest person on the planet. Never ran into that problem ever.
-
Ye, lucky you. The “just use RAM:” is a bogus argument, both because a lot of software expand to volume name (rightfully so, normally you wish to adress the filesystem, and not the device the filesystem is atteched to, which might change over time), and because of the way the bug manifests itself - enter “ram:” in path gadget (dopus 4.12 on 68000) and it expands to just “:”, which isn’t ram: but rather root of whatever context dopus started from.
(Of course you’re Welsh, so quick to be on the defense regarding ram…)
-
Ye, lucky you. The “just use RAM:” is a bogus argument, both because a lot of software expand to volume name (rightfully so, normally you wish to adress the filesystem, and not the device the filesystem is atteched to, which might change over time), and because of the way the bug manifests itself - enter “ram:” in path gadget (dopus 4.12 on 68000) and it expands to just “:”, which isn’t ram: but rather root of whatever context dopus started from.
(Of course you’re Welsh, so quick to be on the defense regarding ram…)
Shelly strikes Again! 🙄
-
Ye, lucky you. The “just use RAM:” is a bogus argument, both because a lot of software expand to volume name (rightfully so, normally you wish to adress the filesystem, and not the device the filesystem is atteched to, which might change over time), and because of the way the bug manifests itself - enter “ram:” in path gadget (dopus 4.12 on 68000) and it expands to just “:”, which isn’t ram: but rather root of whatever context dopus started from.
(Of course you’re Welsh, so quick to be on the defense regarding ram…)
Defend? not sure I follow. Just stating facts from my point of view.
So its a locale thing? when using different languages, issue appears?
Shelly strikes Again! 🙄
Oh come on, your going abit to far now. Just trying to understand an issue I have never come across in the whole time I have used an Amiga since 1988.
-
Whats there to support? Pistorm works like any accelerator. - No actually it does not - are you being facetious?
SBC? - Im surprised you dont know what SBC stands for .
Forthcoming A1200 board? - Yes you are defenitely being facetious.
Now if anyone would care to answer my question as to why the media are stating that 3.2.3 has specific
support for PiStorm I would like to know about it. If Hyperion are stating they are supporting this board
it would be a big deal - it would be a confirmed new target platform and architecture and could pave the way
for the future. If you dont understand what "support" means in the context of target platform then dont even try to answer.
I think its a lie that nobody wants to admit, since nobody yet has been able to give me a concrete answer.
-
Whats there to support? Pistorm works like any accelerator. - No actually it does not - are you being facetious?
SBC? - Im surprised you dont know what SBC stands for .
Forthcoming A1200 board? - Yes you are defenitely being facetious.
Now if anyone would care to answer my question as to why the media are stating that 3.2.3 has specific
support for PiStorm I would like to know about it. If Hyperion are stating they are supporting this board
it would be a big deal - it would be a confirmed new target platform and architecture and could pave the way
for the future. If you dont understand what "support" means in the context of target platform then dont even try to answer.
I think its a lie that nobody wants to admit, since nobody yet has been able to give me a concrete answer.
Not being facetious at all. Your coming across as agressive, have you asked on the Hyperion forums?
Yes, pistorm in its normal state, is exactly like any other 040 accelerator (thats how I ship them, 040 with extra ram). The other harware passthrough stuff, is just an extra bonus. Are you refering to supporting those extra features out of the box? or maybe an arm version of OS 3.2.3 (which is never going to happen).
Never heard the term SBC before, hence I asked. No need to be rude.
Again, which A1200 board you refering to. You haven't exactly stated much of anything, just vague comments.
I have not heard or read anything about specific support for pistorm. So you should be asking on their forums.
The only mention of ehancements for pistorm anywhere is here;
https://www.theregister.com/2025/04/10/amigaos_3_2_3/
Also this;
High-Color and High-Resolution:
AmigaOS 3.2.3 is designed to take full advantage of the PiStorm's ability to provide RTG graphics and support high-resolution modes through HDMI.
680x0 Processor Systems:
The update is designed to work with classic Amigas running 680x0 processors, including those equipped with PiStorm accelerator boards.
Which is odd, how would they know, if Hyperion never even mention it.
There is a release notes for every single component. You could look in there.
-
Oh come on, your going abit to far now. Just trying to understand an issue I have never come across in the whole time I have used an Amiga since 1988.
That wasn’t aimed at you Chris but our resident bored Sheldon Lee Cooper who loves to put out facts. 😉
-
That wasn’t aimed at you Chris but our resident bored Sheldon Lee Cooper who loves to put out facts. 😉
I know, and my reply was in defence of Kolla. Come on, chill as it appears your trolling now, :(.
-
Now if anyone would care to answer my question as to why the media are stating that 3.2.3 has specific
support for PiStorm I would like to know about it. If Hyperion are stating they are supporting this board
it would be a big deal -
As Chris said, the PiStorm is great because it spoofs as an 040 accelerator! But isn't all this OS3.2.3 stuff irrelevant anyway as aren't we supposed to be boycotting Hyperion products until they remove the legal roadblocks to THEA1200? Come on mate, we wouldn't want to give the A1200NG an unfair head start now would we? ;)
-
As Chris said, the PiStorm is great because it spoofs as an 040 accelerator! But isn't all this OS3.2.3 stuff irrelevant anyway as aren't we supposed to be boycotting Hyperion products until they remove the legal roadblocks to THEA1200? Come on mate, we wouldn't want to give the A1200NG an unfair head start now would we? ;)
Sigh, please not another THEA1200 hijack. Why troll here and drag this off topic?
Go post on Hyperions forums.
-
Still waiting for an answer on this . From where im sitting the various mainstream media outlets are saying that this update has support for PiStorm. Yet there is no mention of it in the release notes. This is a big deal so why is there nothing mentioned?
I read The Register article and my view is that it's just not clearly written. The line "The update targets Amigas with 680x0 processors, including systems enhanced with PiStorm accelerator boards." means it targets classic systems, not PPC-based ones. If calling out PiStorm I don't know why it doesn't also refer to Vampire cards. 🤔
This isn't the same thing as saying there are PiStorm-specific enhancements in the OS.
Original article I read is here, assuming it's the same one: https://www.theregister.com/2025/04/10/amigaos_3_2_3/
-
Sigh, please not another THEA1200 hijack. Why troll here and drag this off topic?
Go post on Hyperions forums.
It just looked like you were taking flack Chris so just trying to get us back onto friendly banter rather than whatever that was about the PiStorm requiring additional support beyond Emu68! My bad! ;) Keep frosty!
-
From where im sitting the various mainstream media outlets are saying that this update has support for PiStorm.
I've been monitoring the BBC, The Guardian and The Times (and the FT) and none of them have mentioned Update 3.2.3 at all, let alone the PiStorm?
-
Yeah, well if you bump your licence fee payment and then write to the Director General a nice letter about how balanced and unbiased their news output is then they will then send you a telegram with an in-depth review of OS3.2.3 with a cost breakdown of how the spoils of the project have been spent and which lawyers got their bonuses! You have to be in the know!
-
Defend? not sure I follow.
Ok, it was a joke, playing with a certain stereotype of Welsh men.
So its a locale thing? when using different languages, issue appears?
It is not a locale problem per se, no. Once you have everything localised, "RAM Disk" sticks out like a sore thumb.
Regardless, your focus is misplaced. Relabelling RAM: has not been a problem before, but with 3.2.3 it is. This has been acknowledged and is addressed for next update, so...
-
Ok, it was a joke, playing with a certain stereotype of Welsh men.
Ah, no problems. Now if you mentioned my sheep, then we would have problems, ;).
This has been acknowledged and is addressed for next update, so...
Fair enough.