However still crashing in both method now (starting from WB menu or just double click from the AmiUpdate icon) :-/
Apparently I wasn't clear enough. The fix in workbench.library had nothing to do with any problems introduced by the just released AmiUpdate 2.25.
Until AmiUpdate gets a fix just do a rollback to whatever version you were using before. I rolled my AmiUpdate install back to 2.24 using the rollback feature and it's working fine again.
However still crashing in both method now (starting from WB menu or just double click from the AmiUpdate icon) :-/
Starting it from the Workbench menu last night, it ran for me, and (ultimately) worked OK. But it said it had to update Amiupdate first, for which I had to go through and make 12-15 assigns from requester windows for a bunch of utility and prefs items. Once those were all made, it put the actual updates (Workbench library, Sketchblock, and pci card) in the proper drawer according to my prefs, and unpacked them, ready for installing.
Paul
Builder of Frankenthousand The monster A1000 The Young Frankenthousand A1-XE G4 X5000
However still crashing in both method now (starting from WB menu or just double click from the AmiUpdate icon) :-/
Apparently I wasn't clear enough. The fix in workbench.library had nothing to do with any problems introduced by the just released AmiUpdate 2.25.
Until AmiUpdate gets a fix just do a rollback to whatever version you were using before. I rolled my AmiUpdate install back to 2.24 using the rollback feature and it's working fine again.
Ouch, sorry. I completely misunderstood
I thought "wow, that was a pretty fast fix"...yet they had nothing really to do with each other.
Sorry again, rolled back and awaiting the fix
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
Apparently I wasn't clear enough. The fix in workbench.library had nothing to do with any problems introduced by the just released AmiUpdate 2.25.
Until AmiUpdate gets a fix just do a rollback to whatever version you were using before. I rolled my AmiUpdate install back to 2.24 using the rollback feature and it's working fine again.
You got it right. Fix one bug and another one pops up to replace it. I'd like to thank the convoluted workbench.library code for making this as difficult as it could be... argh
On the plus side, the rollback feature worked great for the AmiUpdate client. I think that is the first time I ever used it.
I think the best thing is that we can really see how much is being done behind the scenes. Before we'd go for months with no changes and it could sometimes feel like there wasn't much happening.