@khayoz

Hello,

Thank you so much for your support, it's very kind of you.

For F12, it's much simpler to have it at the very end of the keyboard (PC type).

However, if you're referring to fullscreen for Virtual Jaguar, you can enable it in the config file.

I imagine there aren't many of you on AmigaNG who have an Amiga-style keyboard.

Thanks again and have a great day!

HunoPPC

@Tuvok

If you define new menu entries for Workbench using ARexx, you can specify the shortcuts and they will appear next to the item name.
I'm not sure if all combos can be displayed as I only use Amiga+letter shortcuts.

A long time ago I released AddMenu: http://aminet.net/package/util/wb/AddMenu which shows how to add custom menus with ARexx, maybe it's helpful.

@redfox

That's nothing new with update 3; I've had the same thing happen with MakeCD and older versions of OS4. I think the problem is that MakeCD doesn't understand file links, and so crashes when it encounters one. The Sys:SObjs directory, at least, contains file links, so trying to make images of Sys: fails.

@NinjaCyborg

Have a look at these:

http://aminet.net/package/util/mouse/AnimaPoint
http://aminet.net/package/game/gag/PingBoing

@LyleHaze

Hi Lyle,

> Unfortunately I loaned out the Xorro board and it was never returned, so you'll have to take my word for it.

I did buy two when they came out, and haven't used them yet. If you want I can send you one as I really only need one, if I ever get around to using it.

@ldg72

It's quite impressive that AI was able to help, considering that it's very biased when it comes to code, assuming most of the data used by the LLMs comes from linux, some from windows, and presumably not a lot of source code comes from OS4 projects.
I took a quick look at the client source code and there's a lot of platform-dependent code in there. I'd replace the calls to malloc() with calls to AllocVecTags() but I don't know if that's necessary or more of a principle when porting code.

It begs the question whether AI would be helpful with porting FireFox, as the main obstacle is the broad array of libraries that need to be ported and endian conversions needed all over the place.

I think I found another casualty,

Today I was trying to use MakeCD to create a backup of my system partition, but MakeCD crashed while making an image file. I think it was scanning my system partition at the time.

The last time I used MakeCD was in 2015.

I wish I could use AmiDVD but it does not work with Update 3.

---
redfox

I don't know enough about these things and... I hate ‘AI’.
If the code was based on ‘AI’, as far as I'm concerned, it ‘doesn't exist’ – it's sludge.

I'm just expressing my opinion and I hope you won't be offended
I'm sure you put a lot of work into it and it works great.

@Capehill
Thank you for the update.

Few people know that the data in gamecontrollerdb.txt has changed with newer versions of SDL, even the new SDL2.
If you have ever generated data for your gamepad/joypad under AOS4 and it is not included here:
https://github.com/AmigaPorts/SDL/blob ... ick/SDL_gamepad_db.h#L870

They will need to do it again. It is a bit complicated due to the SDL2/GL4ES and EGL versions, where older versions of SDL2 are used.

There used to be a thread on this topic here -> https://www.amigans.net/modules/newbb/viewtopic.php?post_id=140094
The data is old and incorrect for the latest versions of SDL.
Currently, it is best to generate a new gamecontrollerdb.txt if someone's gamepad/joypad does not work using the testcontroller included in the SDK package and add the above-mentioned data.

Regarding the latest version of SDL3 - I will check it on some port and let you know if it works.

Thank you again.

*) If a game uses the old SDL API for joy/pad and the controller works, it does not mean that the data is correct.
The game must be based on a relatively newer SDL port and use the new API for pad/joy.
It's a bit complicated.
It can be explained as follows. Once configured, the pad should work correctly in every game. You do not need to configure the settings in the programme/game each time to ensure that each button is set correctly. Modern systems and ports use this. The old SDL (1) API is no longer used in the latest SDL programmes on the newest systems.

@NovaCoder

Great news

I'm trying to do that over 12 months to recover that account...

I have tried to reach out to A-EON for this and other issues several times over the last few years. I didn't receive any replies either.

@khayoz
Quote:Only with software not supporting all Amiga input methods.

Quote:Amiga keyboards support 20 F-keys, F1 (CSI 0) - F20 (CSI 19), not only 10!
From the Amiga ROM Kernal Reference Manual: Libraries:Old ports of unix console software, like the Lynx and w3m web browsers, the mutt E-Mail client or the slrn newsreader (and any other software using the S-Lang library as well) supported all of them.
But with current software, no matter if AmigaOS native or ports from other systems, I wouldn't be surprised if only F1-F10 work

Hello,

anybody had issues with recovering AmiSphere user account?

I wan to register ES2.2 license, however not able to recover my password. I tried to use http://www.a-eon.com page to contact them multiple times - no reply for months.

Do you have any recommendations?

Thank you

@NinjaCyborg

There is also vlink (VBCC linker) which is also written by Frank Wille:

http://sun.hasenbraten.de/vlink/

It is portable and supports a wide variety of object/executable formats.

Awesome stuff. Thanks Capehill

That is very cool!

Hi everyone,

I wanted to share some exciting news regarding a project I’ve been working on. I have successfully ported the Paho MQTT C library to AmigaOS4.

To be honest, I don’t consider myself a professional developer—I am still a beginner in many ways. However, I wanted to experiment with AI-assisted development to see if it could help bridge the gap for porting libraries to our platform. To my surprise, I managed to complete the Paho MQTT port in just 4.5 hours.

Progress & Testing
Environment: The entire development and compilation were done using QEMU/Pegasos2 emulation on a MacBook Air M4.

Results: I successfully compiled the included examples and connected to my local MQTT server running on a Raspberry Pi. I was able to publish topics without issues.

CuraEngine: Additionally, I spent about 1.5 hours porting CuraEngine 15.4.6. The command-line tool works correctly on my emulated AmigaOS4; I tested slicing both binary and ASCII STL files with success.

Call for Feedback
I am releasing the source code on GitHub. Since this was a fast-paced experiment heavily aided by AI, I would love for more experienced Amiga developers to take a look at the code. I am curious to hear your thoughts on the quality of the implementation and how the AI handled the Amiga-specific requirements.

GitHub Repository: https://github.com/ldg72/paho.mqtt.c-amigaos4

I hope this can be useful to the community and perhaps spark a discussion on how AI can help us bring more modern software to AmigaOS4.

Best regards, Luca De Giovanni

the original blink linker by Software Distillery, was it ever open sourced? Seems odd that it wasn't.

The only open source linkers for Amiga I am aware of now are DICE dlink and Frank Wille's PhxLnk

How do you hook it up to your X5000?