Welcome, Guest. Please login or register.

Author Topic: A600GS Updates  (Read 252658 times)

Description:

0 Members and 3 Guests are viewing this topic.

Offline FlynnTA

  • Newbie
  • *
  • Join Date: Apr 2025
  • Posts: 7
  • Country: de
    • Show all replies
Re: A600GS Updates
« on: April 22, 2025, 12:57:52 PM »
@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
« Last Edit: April 22, 2025, 01:06:14 PM by FlynnTA »
 

Offline FlynnTA

  • Newbie
  • *
  • Join Date: Apr 2025
  • Posts: 7
  • Country: de
    • Show all replies
Re: A600GS Updates
« Reply #1 on: May 13, 2025, 04:12:45 PM »
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.
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.

Thanks for fixing the default icon.

Regarding RX: there are serveral REXX scripts for sending various information (uptime, weather, system infos) to IMP3. They are not doing anything or are crashing.

And about the RDB issue: it seems that the last update broke RDB support. I had a working 3.2.3 installation created with the previous (not current) patch. It worked fine until I edited the profile with the current firmware. I did not change anything regarding the harddrives, just selected a new ROM. And the RDB harddisk was no longer booting.
I deleted the profile and re-imported a working full RDB harddisk again. And guess what... the RDB hard disk is not booting.
And just to be clear: There is only one harddisk, the RDB one.
« Last Edit: May 13, 2025, 04:13:51 PM by FlynnTA »