Ah, I see, that makes more sense... Thanks for clarifying!

Well, I still have my CDTV in storage. That might help in a pinch, but the general problem is currently lack of knowledge/understanding and manpower.

Knowing how to cater for the CDTV or the CD32 is an expert domain. The work being done on AmigaOS 3.2 is more of a task for generalists.

Thanks, and btw I'm a dudette if you want to use such a term

A ROM is planned but you will be able to use the 3.1.4 ROM by using LoadModule to update it.

You and Thor are experts in my book, that’s for sure :)
I’m sure Toni Wilen would help, he’s an expert on many things amiga related, plus he has a cdtv he hacked to bits, and has done quite some research on the cdtv roms already.

Nothing really, just with all the attention it is getting with accelerators etc it would be a nice to have, but not essential.

Ok, so, thanks for your hard work and dedication, dudette... :)

Stephen Leary and Toni Wilen made a possible to build CDTV.device, wich is main reason, why A500 accelerators doesn't work with CDTV.

https://github.com/terriblefire/cdtv.device

It would be nice to deliver an updated version of Toolmaker and any other tools to help developing Amiga software more rapidly also add memory protection that’s Brice Nesbitt spoke about in his video. Fix all remaining bugs found in CBM database. Deliver an updated SDK and RKMs.

Will their be any space in ROM to fit in some sort of diagnostic tool(s) ala DiagROM, so that we don't have to go swopping ROMS in and out when trying to diagnose issues with our machines?

If not (and I suspect their wont be enough space) its not a deal breaker in any shape or form (just a really nice to have).

Thank you to the team for their hard work on updating the OS for classic users :-)

Stay safe & healthy everyone.

It would be excellent to have things like AHI, P96 and a TCP stack (roadshow?) built in, but I realise that's unlikely seeing as these are 3rd party products. Could the demo versions be included as optional features though, then those of us with the keys can just drop them in and be done

Please no. Only fully functional parts of the OS should be included, ones that are developed as a part of the OS development tree. Anything that lives its own development life outside of the OS should continue to live outside.

@kamelito:

Yes, there will be a 3.2 NDK.

firstly great work guys keeping the OS updated.

my only issue would be the version name.


I know AmigaOS is a bit of mess as I gather OS 3.5 / 3.9 source code was never shared and it contained a number of third party add-ons that not owned by Haage & Partner or Amiga inc.


AmigaOS 3.1.4 is more advance than AmigaOS 3.9 correct?


I would called it AmigaOS 3.10 or now AmigaOS 3.11


as it does confuse me a least.

In some ways yes, in some ways no.

OS3.2 will be more advanced than OS3.9 in almost all areas.

3.10 is equal to 3.1 which is an already-used release number.

Please yes. An "extras" disk wouldn't hurt you; I doubt anyone will be pointing a gun at you forcing you to install it.

Well done to you all for getting 3.1.4 out there. I have it on my 1200. So it has been a while since I have used my Amiga day to day, so I am quite rusty with its workings. How hard would it be to get the raspberry pi seen from the OS directly? I am thinking from an accelerator, RTG & memory point of view. Is that even a thing that could be done?

AHI would already nee one extra disk. Roadshow 3 disks and P96 1 disk? I think such stuff is better for a distribution package like BestWB for example.

Now that's a fair point

To further E-Penguins point, would the team consider distributing the release on CD-Rom as well as a floppy version at all? This way it would be possible to include demo versions of the software E-Penguin mentioned on the CD Distribution (plus anything else the team consider as a nice add-on for people who have more powerful systems e.g BestWB etc?) as you would have plenty of space.