A600GS Updates

[amigakit]

The following software updates for the A600GS have been uploaded today through the in-built live update system.  They are available to download for all registered AmiSphere users:


46.1.1015  (28/02/2025):

A600GS:

* Add Italian language translation thanks to Samir Hawamdeh

* Add test for RDB based HDFs, when RDB found omit altered options to allow correct handling by AmiBerry

* Suppress editing of DEVICE VOLUME and BOOTPRI for RDB based HDFs as these are all in the control of the RDB

* Add option to limit Z3 memory space used to 1Gb, this should allow RTG and Z3 memory to be used on OS variants that inadvertently impose this limit.

YAM:

YAM v2.10 has been rebuilt with important bug fixes implemented.  A new YAM support page has been added to the Wiki for A600GS / A1200NG users: https://wiki.amiga.org/yam

* Regenerate the flex generated C files from HTML2Mail.l and ParseMail.l with flex version 4.6 (run on the A600gs itself 🙂 ) as the OS4 version used for cross compiling was just slightly too old and caused occasional crashes.

* Fix bug in RecipientString GoActive method, custom MUI class that could set the same input handler on the window more than once and cause lock-ups due to queueing a node twice.

* Fix equivalent issue in GoInactive method

The last two fix an issue with the Forward window locking up and also the Edit draft window in some circumstances

AmiBerry:

Minor refactor of Z3mem options parsing to allow setting up of multiple Z3 memory "cards" , the previous parser would overwrite the same memory bank with the subsequant options causing some quirky side effects!  The end result of this is to allow combinations of memory like 512 + 256 (for 768 total)

[nbache]

YAM v2.10 has been rebuilt with important bug fixes implemented.

Was an OS4 build also made with these fixes? Or will it be?

Best regards,

Niels

[amigakit]

@nbache

As official YAM Development stopped a few years ago , we are willing to progress the project so it does not die off.  It is important to keep the applications on the A600GS and A1200NG up to date.  We have already added up to date AmiSSL 5 support and fixed some important issues.   An OS4 port would be perfectly feasible too.

[broadblues]

I haven't as yet.
Just tried for a quick test whilst building something else on the other machine, and  it needs a bit of attention to  build with the recent OS4 SDK when I have more time I might take bit more in depth look. Might be just used the wrong makefile options as it generated alot more warnings than I would expect.

[ernsteiswuerfel]

* Add option to limit Z3 memory space used to 1Gb, this should allow RTG and Z3 memory to be used on OS variants that inadvertently impose this limit.

Many thanks! I can now use the A600GS 'uagefx' graphics card on a bog standard OS3.2.2.1 install with Picasso 3.5.0 and 800 MB RAM.

However now when selecting 'Use Z3 RAM' option I get 800 MB Fast as default. What does the 'Limit Z3 to 1 GB' option do then?

Not that I am complaining as the now seemingly default 800 MB are more then enough for me and everything is working fine. Simply curious about what the new option might be good for when the former default 1 GB Fast got reduced to 800 MB Fast as default anyhow?

[broadblues]

It limits the *total* Z3 ram, including that used by the Z3 graphics card to less than 1GiB (exceeding the 1GiB "barrier" being the reason for the issue)

In the is iteration it means you get a bank of 512MiB and 1 of 256MiB giving  756GiB of Z3 ram plus the 128MiB Z3 P96 card. (which leaves 128MiB spare )

Workebench will e reporting GB rather than GiB hence the 800+ instead of 756

[ernsteiswuerfel]

It limits the *total* Z3 ram, including that used by the Z3 graphics card to less than 1GiB (exceeding the 1GiB "barrier" being the reason for the issue)

Thanks for explaining!

But the point why I was asking is that the P96 issue on my OS 3.2.2.1 install disappeared _without_ selecting the '1 GB Z3 RAM limit' option. Default Z3 setting, now supplying 768 MiB RAM seems enough.

In the is iteration it means you get a bank of 512MiB and 1 of 256MiB giving  756GiB of Z3 ram plus the 128MiB Z3 P96 card. (which leaves 128MiB spare )

Workebench will e reporting GB rather than GiB hence the 800+ instead of 756

Ah I see - thanks for the details!

[broadblues]

Default Z3 setting, now supplying 768 MiB

Are you saying that with limt Z3 to 1Gb unticked you only get 768 GiB ? That's not right. I will double check things my end.  Usual cause for weirdness like that is not setting the bool to false in constructor, usual catch those before release but .....

[ernsteiswuerfel]

Are you saying that with limt Z3 to 1Gb unticked you only get 768 GiB ?

Exactly.

[broadblues]

The option is set but not the widget, fixed in next update.

[Jeff]

Do I use my existing AmiShere account for updates, or do I create a new account bespoke the A600GS? I bought my A600GS right from AmigaKit and it hasn't had it's first update yet.
I appreciate ALL of the updates - it's becoming a nice small system.

[AmigaOldskooler]

@Jeff

You can use your existing AmiSphere account. Then you will get a list of your previous purchases from AmiStore as well (if you've bought something in the past on AmigaOS 4 for example).

[Jeff]

Thank You! I think I own everything they sell on there with credit leftover so... I am still waiting for some awesome looking packages to be released 

[Stilvoid]

Just got round to digging out my Greaseweazle to try on the A600GS. I have a PC floppy drive but only flat cables (no twist) from the Amiga but it works fine from my PC if I tell the software to use drive 1. Is there a way to specify this for the A600GS? I just tried, hoping it would detect or try different drive numbers but nothing happens

[SkulleateR]

Just got round to digging out my Greaseweazle to try on the A600GS. I have a PC floppy drive but only flat cables (no twist) from the Amiga but it works fine from my PC if I tell the software to use drive 1. Is there a way to specify this for the A600GS? I just tried, hoping it would detect or try different drive numbers but nothing happens

Had the same problem and just bought a twisted cable for 2€ of EBay

You can also use an older Greaseweazle F1, that use a flat cable ...

[F0LLETT]

Just got round to digging out my Greaseweazle to try on the A600GS. I have a PC floppy drive but only flat cables (no twist) from the Amiga but it works fine from my PC if I tell the software to use drive 1. Is there a way to specify this for the A600GS? I just tried, hoping it would detect or try different drive numbers but nothing happens

Just selecting DF1 in menu, will not work. You need to set it on GW level. Its currently being worked on / added.