Amiga OS 3.2 released

[kolla]

OS3.9's unarchiver doesn't work with new Reaction. It gives guru when target is choosed.

Shocking. What guru? 8000 0003 again?
Have you tried upping the stack?

[QuikSanz]

Maybe someone can make a new Reaction front end for XAD11.

[Matt_H]

Try the TC020 version of icon.library found on aminet. This also makes any png icons you might have visible again.

It’s a fresh install on a stock (emulated) 4000 with plain, 4-color icons. The only explanations for the gadget corruption are a 3.2 system bug or an FS-UAE emulation bug.

[x303]

Try the TC020 version of icon.library found on aminet. This also makes any png icons you might have visible again.

It’s a fresh install on a stock (emulated) 4000 with plain, 4-color icons. The only explanations for the gadget corruption are a 3.2 system bug or an FS-UAE emulation bug.

Could be, but over here opening pointer prefs gives a corrupt display on uaertg 1920*1080*32. Replacing the stock icon.library with the one from aminet solves this problem.

[TribbleSmasher]

The NDK got updated again today.

Native Developer Kit for AmigaOS 3.2 (NDK 3.2 Release 3) available for immediate download
Brussels, July 30, 2021

Hyperion Entertainment is proud to announce another update for the Native Developer Kit for AmigaOS 3.2.

This NDK update contains further reviewed contents to ensure developers using several different compilers will be able to harness all the new features AmigaOS 3.2 brings.

This release also paves the way for a continued flow of updates to the Native Developer Kit for AmigaOS 3.2 which will also be accessible in other venues to pursue greater adoption and wider availability.

Hyperion is committed to AmigaOS development support, so stay tuned for further NDK updates!

AmigaOS NDK 3.2 R3 is available for free from our download area for any interested party.

We thank all of you who have rushed Amiga dealers worldwide to get their hands on a copy of AmigaOS 3.2.
If you want to support our efforts further, please head over to our AmigaOS merchandise store.

https://www.hyperion-entertainment.com/index.php/downloads?view=files&parent=40

[TribbleSmasher]

Now that i am testing the new OS myself, at a first glance i find it very weird that the previous 3.1.4.1 installation doesn't even fully boot with just the new ROM installed. It even complains for not finding iconlib and workbenchlib.
And, it keeps asking for the workbenchlib like a hundred times, i wonder how that was implemented...user clicks Cancel just ask again and again, right?
How can one put logic into this?
If there is no (good)workbenchlib, system's keep booting into a limbo state (empty screen) and a user banging his head onto the desk (remember: we hit CANCEL multiple times as we are SURE there is such a lib on the harddrive)...
The OS could instead nest the calls for the lib and break the booting at the best possible time and leave the user with a CONsole and an error message and a possibility to recover from this? Like, the OS3.2 ROM doesn't like the 3.1.4 ROM or the 3.1.4.1 workbenchlib and would offer a hint (a few bytes of text)?

i never experienced this behaviour before, you could always boot with just the new ROM installed.

More complains:
The installation with CDROM(image) is not as smooth as possible:
-boot from Install32 disk
- Click ActivateCDRom
it should open the CD after mounting it. In my case i get an error because it is already mounted! How is this an error?
Then, from the CD, which i opened by myself, i have to open the install drawer, to find toomany icons.
I click 'Starthere', but nothing happens, instead it tells me to dblclick the install disk (again!)... so i did. guess what happens? Nothing. The installation from CD did not start, i am looking at the same screen but now the CD is mounted.
Not smooth, not at all.
I'd like to see  two more icons in the root of the CD: 'Install to HD' and 'Install new system', maybe even integrated into a simple chooser app.

Once the CD is mounted (and we have some RAM of course) there is no excuse for not having a bigger installer, another RequestChoice, launch RexxMast or whatever.

Why isn't the Locale&Input selector the first thing i see? A pretty one, of course, not the Prefs editor as it is now. Just glue those gadgets (that your already have in source!) )together in one LangSel tool and you are done, how hard can it be?

Locale prefs is not set to the country i chose the language for, instead it is U.S. and it doesn't point me to change it. Prefered language is not set, time zone neither. nothing is localised, i choosed two languages to install and none is prefered.
If i chose more than the internal language (eng u.s.) shouldn't there be an muex choice for my prefered language/country in the next installer page?
The RAM icon is 'wrong', ugly.
'Auto-arrange icons' from the tools menu also snapshots the positions without asking me?? Maybe i want to judge the result before keeping it?
There is still an Expansion drawer, what is this for?

No help support for several tools. You hit HELP key and nothing happens.
If you hit HELP and the app uses its own screen, the help guide is not popping to the front, it stays in the back, e.g. Workbench screen.
No version/build information in GUI tools/utilities even if they already have a menu built in. Could be in the window title tho, i mean cmon.
Workbenchs stack size is still 4kB?
Workbench prefs: 'hidden devices' do not indicate if there is actually a disk in the drives.
Icontrol prefs does funny things when you open up its async windows and clicking checkboxes and then just click Use in the farthest window...
DefaultIcons prefs is ... special.

There was no "Welcome" or "ThankYou" demo after a fresh install from CD. So much wasted space.. :

[chris]

Why isn't the Locale&Input selector the first thing i see? A pretty one, of course, not the Prefs editor as it is now. Just glue those gadgets (that your already have in source!) )together in one LangSel tool and you are done, how hard can it be?

Locale prefs is not set to the country i chose the language for, instead it is U.S. and it doesn't point me to change it. Prefered language is not set, time zone neither. nothing is localised, i choosed two languages to install and none is prefered.
If i chose more than the internal language (eng u.s.) shouldn't there be an muex choice for my prefered language/country in the next installer page?

Yes; this got me.  I assumed that because I'd selected the British English install that my language would be set to British English.  In fact, I'd forgotten that this was even something that needed to be set.

In Locale Prefs there are no preferred languages, and HELP doesn't work because it is looking at the preferred languages list, which is empty (so default English), yet there are no English language help files installed, because I installed British English (I'd normally put both in the preferred languages as usually things don't come with a specific British English catalog).  It should set the preferred language to the one used for the install.  If the user wants to change it later, that's up to them, but the install should be set to the language the user installed.

There is still an Expansion drawer, what is this for?

The same thing it has always been for?

Workbenchs stack size is still 4kB?

Can be changed in WB prefs.

[Minuous]

@TribbleSmasher:

Language and country are two separate things and always have been.

[TribbleSmasher]

There is still an Expansion drawer, what is this for?

The same thing it has always been for?

There are still expansions initialising their drivers this way and OS3.2 is still supporting this and those expansions still work??
Really?
The only thing i've ever had in there was 'BuddhaSpeed', which is obsolete for, like, 10 years?

Workbenchs stack size is still 4kB?

Can be changed in WB prefs.

Yeah, but as 3.2 requires more resources anyway, why not set this to e.g. 16kB default?

[kolla]

Things have progressed since 1985 - GUIs are supposed to be self-explaining, albeit this presents an ongoing and sometimes impossible challenge, given the technical restrictions. Radio buttons are a well established paradigm for mutual-exclusive choices in AmigaOS since 1990, so it makes sense to extend it to menus as well.

Not really, we had cycle gadgets and cycle-to-menu - those have been using checkmarks. What do they use now?

Alas...


Oh great - so checkmarks as ...heh... "radiobuttons" are removed in menus, but kept in cycle-to-menu, with flying colours, litereally, da effin lolz... consistency!

Are "hidden" volumes (wb prefs) possible to open via the "open volume" in Workbench menu? I haven't seen an answer to that.

Still not answered as far as I can see.

I don't have 3.2, I comment from what I see people fumble around with on youtube videos.

Like the above screenshot, thanks ....uhm... Bill!

[hypnoia]

Hey all, here's a question I haven't seen come up:  is AmigaOS 4.1 FE for classics compatible with the 3.2 Kickstart ROMs?  And by 'compatible' I just mean 'will not break if I install them.'

[Minuous]

>Oh great - so checkmarks as ...heh... "radiobuttons" are removed in menus, but kept in cycle-to-menu, with flying colours, litereally, da effin lolz... consistency!

This has now been changed; chooser.gadget will be consistent with the rest of the OS.

>Are "hidden" volumes (wb prefs) possible to open via the "open volume" in Workbench menu?

No.

>is AmigaOS 4.1 FE for classics compatible with the 3.2 Kickstart ROMs?  And by 'compatible' I just mean 'will not break if I install them.'

Using an A4000 3.2 ROM instead of an A4000 3.1 ROM works fine for booting OS4.1FEu2 in WinUAE.

[kolla]

>Oh great - so checkmarks as ...heh... "radiobuttons" are removed in menus, but kept in cycle-to-menu, with flying colours, litereally, da effin lolz... consistency!

This has now been changed; chooser.gadget will be consistent with the rest of the OS.

Really, haha, that’s funny - how about removing all “theming” and render Sys:Prefs/ReAction pointless while you’re at it, so all ReAction classes render to something consistent with the OS… rest of the OS.. hehe, I’m sure it would also shrink the code and remove bloat as well.

>Are "hidden" volumes (wb prefs) possible to open via the "open volume" in Workbench menu?
No.

Right, though so. That’s one aspect of “hide volume” in Workbench prefs that I really don’t like, it goes too far. Typically it is used to remove clutter from the root desktop, but it also makes it impossible to open a Workbench window of the volume or any of its sub-drawers at all.

One more - in 3.2, do any of “Update all”, “Redraw all” or “Reset WB” move left out icons and volume icons back to their stored positions? I *really* think “Update all” should clean up the root window too, and not just volume and drawer windows.

[hypnoia]

Hey all, here's a question I haven't seen come up:  is AmigaOS 4.1 FE for classics compatible with the 3.2 Kickstart ROMs?  And by 'compatible' I just mean 'will not break if I install them.'

After installing the 3.2 ROMs in my A3000, I have to say that the answer to this appears to be "no, 4.1 FE Classic will not boot with these ROMs".

At least, that's all the evidence I have at this point.  I'll have to get the 40.68's back in there until we have more testimonials.

Disregard.  You would think, after 31 years, that I'd have learned to be careful with the old girl when putting her back together again.

Code: [Select]

5.Tiamat_SSD:> showconfig
PROCESSOR: 604e
EMULATED: CPU 68020/68881fpu
CUSTOM CHIPS: ECS NTSC Agnus (id=$0030), ECS Denise (id=$00FC)
VERSION: Kickstart version 54.30, Exec version 54.30, Disk version 53.18
LEGACY RAM: Node type $A, Attributes $703 (CHIP), at $3000-$1FFFFF (~2.0 meg)
ZORRO BOARDS:
 Board (Elbox Computer):   Prod=2206/161($89E/$A1)
     (@$40000000, size 256meg, subsize same)
 Board (Elbox Computer):   Prod=2206/33($89E/$21)
     (@$50000000, size 16meg, subsize same)
 Board (Individual Computers):   Prod=4626/100($1212/$64)
     (@$54000000, size 64meg, subsize 64K)
 RAM (E3B, Michael Boehmer):   Prod=3643/32($E3B/$20)
     (@$60000000, size 256meg, subsize autosized Mem)
PCI BOARDS:
Bus Device Funct. Manuf. Product Status
0x00 0x02 0x00 0x1002 0x5964 working
0x00 0x02 0x01 0x1002 0x5D44 working


[Steady]

Right, though so. That’s one aspect of “hide volume” in Workbench prefs that I really don’t like, it goes too far. Typically it is used to remove clutter from the root desktop, but it also makes it impossible to open a Workbench window of the volume or any of its sub-drawers at all.

I disagree. It is not just about tidying up the Workbench screen, but also removing Volumes/Devices from being selected where it makes no sense to do so. To just remove it from the Workbench and not the menu would be incomplete.

And before you say it, yes, it should still be available from the CLI because that is a Workbench option, not system-wide.

[Minuous]

Workbench will not open a hidden window; this includes eg. requests from ARexx scripts to do so.