A600GS Updates

[broadblues]

Jumped into an old part of the thread, duh!

[broadblues]

Should this work with a Greaseweazle v4.1 ? Cause it doesn't with mine

Initially only drawbridge support was added as it simplifies setup ( a number of options need to be tweaked in  parallel internally) and I wanted to get the options out for "testing" in the wild. If there is demand for greaseweazle I can add it.

The standalone config it not fixed to A500 you can choose which model you want from the edit panel.

Initial support is disabled in AmiBench as there were issues there when testing in the team, but these may now be resolved, so hopefully it can be enabled soon.

Oh, and the A1200 Config seems to be broken now, every Game and/or HDF I try to start is using Kick 1.3 instead of Kick 3.1 now  :'(

That's odd as AmiBerry wasn't udated fpr a few updates and this is controlled internally by AmiBerry.

[broadblues]

hello , how do I get old updates on my a600gs?

What do you mean by old updates? Updates are incremental, so all previous updates are effectively included when you update.

If mean that you want to downgrade to an earlier version, then that's not possible, but what issue would you be trying to solve by doing that?

[broadblues]

It would be great if you could show what has already been downloaded in the download section. At the moment I see the games and the option to install but can’t see any indication of the ones already downloaded.

That's on my todo list to have available version and locally downloaded version, and then offer update and redownload options.

[broadblues]

Thanks for this most wanted update.
I can now map the USB drive and Global disks, and even there are no custom memory settings I got 2 MB chip/1GB Fastram.

But how is the RTG supposed to work, what RTG card is activated by Amiberry?
uaegfx does not seem to work here.

As mentioned in another post, the A600GS version of the Amiberry executable did not work with uaegfx under Orange Pi Debian Bookworm either, while building Amiberry-Lite from source did made an executable that had uaegfx working.

AmiBench picks up the RTG automatically but more standard picasso installs  will need the monitor driver in DEVS:Monitors editing.

What I did for my AmigaOS3.5 installation was:

copy the original uaegfx to storage
rename the copy in DEVS:Monitors to 'a600gs'
open icon information for the DEVS:Monitors/a600gs filr and chnage the BOARDTYPE tooltype to
BOARDTYPE=a600gs

[broadblues]

Nice. Got RTG working by the simple instructuctions.

Good to hear.

EDIT: Just after posting I made another custom setup with my Workbench 3.9 setup, and this setup does not suffer from the same delay as the WB31.

Second Edit: I found the problem with WB31 is the setpatch (v.40.16) command in startup-sequence that takes very long time to finish. As mentioned above, the same setup (same hdf file) in a non-custom setup dows not have this slowdown.
OS3.2 also suffers from a setpatch delay with custom setup, but not as long as 3.1.

I have to admit I  don't know what going on here. I'm not sure if I'm experiencing this with my 3.5 install, it's a straight copy of my old a1200 and an utter mess, so I've dismissed any delays as down to that,

What options (if any) is setpatch being called with?

[broadblues]

I have to admit I  don't know what going on here. I'm not sure if I'm experiencing this with my 3.5 install, it's a straight copy of my old a1200 and an utter mess, so I've dismissed any delays as down to that,

I just disabled SetPatch in my 3.5 startup sequence boot and yes it boots very fast without it.  But, of course, it doesn't update the ROM in memory so it not really running 3.5.

Its a long time since I booted this on real hardware so not sure what the time to boot should be in a "real hardware" case.

[edit]
Restoring set patch but removing the quiet option I see that the bulk of the delay occurs after the reboot. Not sure what it is doing at this point.
[/edit]

[broadblues]

I haven't tested with 3.2 but I do have RTG working as described with my preexisting AmigaOS 35 setup.

I did a test just now, and it didn't boot, into RTG but then I removed the fast RAM so there was only Chip and Z3 and it booted again, so you could try that. (next test it booted with fast ram as well so might have been a spurious one off glitch)

[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.

[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

[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 .....

[broadblues]

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

[broadblues]

@amigakit

Thank you for the update.

Playing around with the new update, I found the following issues. Maybe they are also in the older firmware updates:

• The default tool icon (sys:prefs/env-archive/sys/def_tool.info) is set to Project, not Tool
• The RX command does not seem to work. At least rx "say 'hello'" does not do anything.
• Closing EaglePlayer crashes the system / shows a "Memory freed twice" window.
• After updating a profile with a full RDB hard disk, the system no longer boots from the hard disk.

Thanks,
Flynn

Just fixed the the type of the def_tool icon, I had previous fixed up all (most of) the default disk types but missed that one.

RX does work, but SAY doesn't ...

try starting YAM and then doing

RX "ADDRESS YAM QUIT"

to verify.

• After updating a profile with a full RDB hard disk, the system no longer boots from the hard disk.

Need a little more explanation here. What exactly did you do?

If you had a system booting from a non RDB harddisk file and you set it to RDB, it will no longer be seen as a valid diskfile and so not boot.

If you added a RDB harddiskfile it *should* be auto detected but could be edge cases I've missed. 

If you added a RDB disk to a system already booting from another partition / harddisk file, then you may need to check no partitions on the RDB have a greater or equal bootpri to the disk you were booting from.

[broadblues]

Hi guys,
After the latest update, my USB key no longer appears in the volumes list when trying to upload ADF files.
Has anyone else experienced this issue?

Are you still having this issue? No changes to the mechanism that drives this have been made, so I'm not sure what might be wrong.