@smarkusg

wow

@redfox
Quote:There are several versions of AmiDVD working with Update 3 since about 3 years already.
I don't know why they still aren't available through Updater

@AlexC
Quote:The main problem porting modern browsers like FireFox or Chromium to AmigaOS is no longer the libraries, but even much lower level parts like support for the programming languages used, for example Rust in case of FireFox.
And of course still assembler for the JavaScript JIT (no PowerPC support any more, even if it was unfinished and unusable, a PPC port was at least started for JavaScriptCore, usually not even any big endian support any more in any parts) and WebAssembly.
Additionally required, compared to about 15-20 years ago with OWB:
A 3D gfx library like Skia for Chromium, instead of the 2D Cairo gfx library (+ some small AmigaOS 4.x parts) used in OWB, support for colour outline fonts (not only for emoji, at least FireFox uses them for GUI parts as well, and colour outline fonts aren't supported by AmigaOS at all yet, i.e. you'd need to use something like the much slower libfreetype instead of native AmigaOS text rendering OWB used).

@AlexC

Uh why... neither of those are what I was asking about

@xenic

Do you have any crash logs for TurboText?

So wanting to see more of what's in that memory space I've added more reads.
But I'm soon out of ideas of why this isn't working in AmigaOS, but seems to be working in uboot land.

https://jaokim.github.io/files/XTools-1.7g.lha

@msteed

Thank you.

@AlexC

" If you want I can send you one as I really only need one, if I ever get around to using it."

Thank You. At this time I am just too busy with "real life".
I'll spare you the list, but it looks to be getting worse instead of better.

I DO finally have an X5000, and I also replaced my dead A1222. So I'm setting myself with four working NG Amigas now. (possibly preparing for retirement??)

But I have more projects than I can handle, and not nearly enough time to make it happen.

Thank you though kindly for the offer.

" if I understand correctly, the xena resource doesn't really do much setup, but rather acts a semaphore. "

Exactly correct. It might also check machine type, and you can see how well THAT idea worked out. ;)

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