AmigaOS 3.2 released!

[Daedalus]

Ooooooooh I like it!

[Akiko]

I hope someone will offer a ROM compilation and burning service for the experimental CD32 Kickstart, otherwise it's beyond my expertise.

[gulliver]

File Name: AmigaOS3.2CD.iso
Size: 77899776 bytes (74 MB)
MD5: 202189a8caa7a25f5700c0b9010aa30a
CRC32: D46440F8
CRC64: F02F5B115AA2DCEF
SHA256: EDEB49AC327F1957BBC1B32C241E80D456F7C46499BD2A55C3F6538E50370A5C
SHA1: 386D1738B36C8127671205779B8BDB0A3D3C788D
BLAKE2sp: 38EC35C8520EAF5CC706787EF895329FAE44762BB510FC911AD03CF848462F23


The CD-ROM already contains a file with the hash numbers of all its files
(except that file itself):

AmigaOS3.2:S/AmigaOS3.2CD.MD5.hashes

From AmigaOS if you booted from the CD or AmigaOS 3.2 you can verify its
integrity by entering from a CLI/Shell:

execute amigaOS3.2cd:s/cdintegrity

[btp]

Awesome to see a new version of the AmigaOS on sale!
Well deserved praise and congratulations to all the great people involved!

Also the CD containing all disk images and ROM modules for all systems (along with some extras) sounds like a good deal!

[alexh]

Originally Posted by gulliver

Please read section 14 of the FAQ (CDTV & CD32) and let me know if you have doubts.

There's one line which looks dubious.

14.8 * Can I use accelerators and fast RAM on my CDTV

You can use accelerators on the CDTV but you must be aware of the memory expansions they use.

There is a bug in the DMA controller (DMAC custom chip) inside the CDTV that causes an issue regarding RAM support.

This prevents you from using AutoConfig based FastMem in the 32-bit (Zorro III) address range in a compatible way.

This is the first I've heard of this. Is there any evidence of this? An in depth technical description? I'd be amazed if this was true. Everyone and I am including some very smart and experienced AmigaOS people were certain this was a "feature" of the way the extended ROM was written.

I'm ready to believe but this answer reads like "I don't understand why this code doesn't work, must be a hardware bug, nothing we can do".

Typical answer I get from softies all the time at my work :-)

UPDATE
This statement in the AmigaOS 3.2 FAQ isn't true. The bug in the DMAC (which is worked around in SW) is irrelevant. The extended ROM v2.30 was written assuming there would be no 32-bit FAST RAM in the system. It fails to work if there is. It uses AllocMem to allocate DMA buffers but calls it with attributes that mean the buffers can be anywhere. However DMA buffers must be within the 24-bit address range of the DMAC. These AllocMem calls can be patched and CDTV works as normal.

[gulliver]

Originally Posted by alexh

There's one line which looks dubious.


This is the first I've heard of this. Is there any evidence of this? An in depth technical description? I'd be amazed if this was true. Everyone and I am including some very smart and experienced AmigaOS people were certain this was a "feature" of the way the extended ROM was written.

It was written by the CDTV creators somewhere in the source code.

I have no reason to believe it is wrong. But as everything in life, there could be a possibility they made a mistake. After all, they were humans AFAIK.

Originally Posted by alexh

Typical answer I get from softies all the time at my work :-)

That is another matter altogether. That could be just lazyness.

[NinjaCyborg]

Originally Posted by Olaf Barthel

We're mostly following what star we can harness right now AmigaOS 3.2 is not (yet) the kind of long term development project which ended up reworking several complete parts of the operating system with each release. As you may recall, 3.1.4 and then 3.1.4.1 reworked the fundamentals, the operating system mostly, with the application software and shell commands receiving their due, but they were not the prime focus. Restarting development work on the 3.1 operating system was.

Here's hoping we'll be able to get more of the reworking done (if they let us) in the future, reworking and building up what so far hasn't been taken care of yet.



AmigaOS 4 is technologically still years ahead of what AmigaOS 3.2 can deliver given the time and work went spent on it. It's not a superset. It's more like AmigaOS 4 and AmigaOS 3.2 are two sets with a large intersection. Right now, we're trying to address the challenges our own peculiar project: it's a legacy operating system with a big "L" and dependencies which go back some 36+ years. AmigaOS 4 had its own challenges of this kind, but it also had to find solutions for challenges unique to its architecture. It can be liberating to be able to break new ground and let the legacy be legacy

I understand! Don't worry, I think it's awesome, don't misunderstand what I say as anything negative at all! Thank you so much.

[trixster]

It looks like 3.2 is broadly compatible with 3.9. With the advice given in the faq in mind, can 3.2 generally be installed over the top of 3.9 without too many issues?

Can the new 3.2 rom modules be placed into a Deneb’s flashrom similar to the way 3.9 rom modules can?

[malko]

The timing is really bad to put it on sale (Friday evening - just on week-end's door ) but ...
THANK YOU to all involved and that made by their work this GREAT news to happen !

[gulliver]

Originally Posted by trixster

It looks like 3.2 is broadly compatible with 3.9. With the advice given in the faq in mind, can 3.2 generally be installed over the top of 3.9 without too many issues?

Can the new 3.2 rom modules be placed into a Deneb’s flashrom similar to the way 3.9 rom modules can?

I don't have a Deneb.
Lucky you! I would have loved to have one.

And to be honest, I haven't touched 3.9 for several years (probably since 2018).

We have a developer with a Deneb. I will try to ask him. We compiled AmigaOS 3.2 on his A4000 which had a Deneb. Not sure how/if he added the 3.2 ROMs to it.

[klx300r]

Awesome news to start off the weekend !!! Thanks to everyone involved

[Firestone]

Congratulations to the team and everyone involved!
I will buy it for sure, as I did with 3.5, 3.9 and 3.1.4.....
Thanks again for your hard work

[alexh]

Originally Posted by gulliver

It was written by the CDTV creators somewhere in the source code.

The source code for the CDTV extended ROM? The last I heard it was lost. It's certainly never "surfaced" before. I'd really like to see the exact text they used and in reference to what function.

Originally Posted by gulliver

I have no reason to believe it is wrong. But as everything in life, there could be a possibility they made a mistake

Maybe. The disassembly of the v2.30 extended ROM clearly shows software that would be incompatible with a system with 32-bit FastRAM. Memory allocation functions being called with the wrong memory attributes so they don't restrict buffers to within the 24-bit address space the CDTV's DMAC can use. Everyone who has seen the diassembled code has said clearly the author's must never have expected to have 32-bit FASTRAM and why would they?

I'd be happy to share detailed information. Toni Wilen introduced in WinUAE 4.5.0 beta 7 the option emulate the issue so it's now possibly to test software fixes more easily.

[walkero]

Congrats to the whole team that developed the new AmigaOS 3.2 and to Hyperion who released it. Hope my local Amiga shop gets the physical version soon. I'd love to have it in my hands.

[golem]

This looks really good. I will buy a copy for sure.

[blasterreal]

SDK ? or NDK?

[Firestone]

I have to say I'm amazed when reading through the over 4000 lines long FAQ-file...
How on earth have you come across all these different scenarios? All these combinations of hardware, workarounds and bugfixes.....Impressive!

[aeberbach]

I _just_ got my TF536 working in my A600. My Hyperion 3.1.4 ROM does not boot (2.05 ROM is OK).

Any way I could test a ROM? I’d just want to see an “insert workbench” before buying this release. I expect it would be useful information for a few others.

[Ledfoot]

Wonder if there are any issues with using the Buddha IDE interface on an A2000 with this? CDRom support through it?

[gulliver]

Let me clarify some things about the CDTV and CD32:

These are experimental CDTV & CD32 builds, as the feature list mentions. And clearly labeled as "at your own risk" with no further support provided, as mentioned in the FAQ.

They have been supplied under such conditions because it was requested by users of this very same forum. Otherwise, it would have meant leaving those machines marginalized, as usual, since decades.

3.2 works on these machines if you are sufficiently skilled, and willing to accept compromises (as mentioned in the FAQ).

The CDTV Extended ROM included is not based on the 2.30 one. And as mentioned in the FAQ the code has not been reviewed. Only tweaked.

And that said, this involved quite a lot of work to make it happen. It took a lot of effort to make both machines run after decades on a newer OS. For example, it implied a particular tester to burn ROMs several times a week and conduct several specific boring tests during months, and report on them. Carl should deserve a medal. But others also thankfully helped too.

Will this code be reviewed in the future? I don't know.
Why? It will depend on time and interest of both developers and testers.

The good thing is that now you can get a newer AmigaOS working on a CDTV, which is something that did not occur since the 90's. And that was the goal.

The same more or less happened with the CD32.