Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
52 user(s) are online (35 user(s) are browsing Forums)

Members: 0
Guests: 52

more...

Support us!

Headlines

Forum Index


Board index » All Posts




Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
Just popping in
Just popping in


@joerg
Quote:
An update of AmiDVD is available through Updater now.


Superb, thank you!

Go to top


Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
Just can't stay away
Just can't stay away


@NinjaCyborg

Sorry about the delay. It's a system freeze so I have no crash log. The only way to get past the freeze is to hit the reset button on my X1000. Since TurboText is a 68k program written with Modula2 and no source available, I doubt if there is any way to fix TurboText.

Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450

Go to top


Re: Life of Tech
Just popping in
Just popping in



Go to top


Re: HunoPPC
Quite a regular
Quite a regular


@xe1huku

I use an A1200 keyoard(in a CDTV keybord case) -> Keyrah -> X5000 USB.

@joerg

Ahh ok, didn't know that!

@HunoPPC

Will try that.

1989-> A500, A600, A3000, A4000, A1200, CD32, µA1, PegII, A1XE, CDTV, Amy/416D79, A1X5000, Vampire 500 V2+, Vampire 600 V2, Amy-ITX, Denise ITX <-2024
Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Home away from home
Home away from home


@ldg72

Congrats on getting it working.

@AlexC

Quote:
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.

Interesting question. My first thought would be that LLMs probably wouldn't be effective with such a huge code-base. Second thought, maybe someone should try it.

I've been testing out using AI coding assistants. There are times when they're surprisingly good. For example, the auto suggestions for DebugPrintF() calls are pretty good at guessing what debug output I want to print, and writing out the code correctly. Being able to write that code with a single TAB certainly saves time.

Other times, the code suggestions are dead wrong, and I write out the code manually.

Code generated via chatting with the LLM is also sometimes impressive, and sometimes utter garbage. I review any code generated line by line, because it gets a lot of stuff wrong, puts magic numbers all over the place, and likes to over-use comments. I do have to do a fair bit of cleanup to make the code higher quality. This does make me wonder about the quality of the code that it was trained on...

I find it very useful to learn how to use 3rd party libraries that I'm unfamiliar with (even large ones). This is especially true, with poorly documented libraries. That might be one of the biggest time savings.

AI code assistants do allow me to write code faster, but I think that being an experienced programmer is essential to keeping the code quality high, and structuring the code well.

@smarkusg

Copyright infringement is indeed a concern with AI. I'm sure that they've slurped up the public parts of my website in their entirety, without my permission. Not much that I can do about it.

If you're using an AI code assistant to work on proprietary code, then you do need to use the settings to exclude GPL licensed ccode (or similar).

I'd love to build my own private LLM code assistant. Alas, I don't have the money to buy hardware sufficiently powerful to run a sufficiently large LLM.**

Hans


** From what I've seen, small LLM models can't even code a working to-do list program.

Join Kea Campus' Amiga Corner and support Amiga content creation
https://keasigmadelta.com/ - see more of my work
Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Not too shy to talk
Not too shy to talk


@smarkusg

no one cares

Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Quite a regular
Quite a regular


@LiveForIt @ldg72
I will elaborate on what I wrote about my point of view on AI.
Perhaps what I wrote was too simplistic and did not cover my point of view.

I tried to use generic artificial intelligence tools. They were either inaccurate or verifying what they proposed took longer than if I had found the solution in the traditional way. It wasn't even about programming, but about solutions with hardware and the Linux system. I tried it a few times and always noticed that what it suggested was in the top 10 hits from various browsers. Even some topics were suggested correctly, but it never suggested them unless it was specifically asked about them.

Now, the topic of AI itself, as I see it. The topic of current trends in AI applications and legal issues.
I think many of us remember the late 1990s when the internet appeared. Everyone was excited about the ‘freedom’ it offered.
Of course, access to information was the main thing. There was also a dark side (from today's perspective) - where no one cared about posting files of various kinds (music, photos, codes). The very freedom of access to all this data prevailed over everything else.
This can be compared to what we have with AI – a period where everyone uses various data without caring who created it and how it was transferred to us.
This is changing very slowly. It is most noticeable in the computer games and music industries.


In the computer games industry, users themselves are forcing companies to ensure that games do not contain AI-related code.
There has recently been a huge wave of criticism surrounding the game ‘ARC Raiders’, where sound was generated by AI in certain applications.
Even some companies themselves have stated that they do not want this.
Example -> https://www.gamedeveloper.com/business ... oid-genai-like-the-plague

The music industry is also currently very negative towards AI.
This is not about corporations, but about independent creators.
A simple example. Creators place their music files on various streaming platforms. The payment for opening a song for the creator is a bit complicated. It can be simplified in a 1:1 example (this is not how it works in reality)
The flood of AI-generated music, where the author's role is reduced to simply entering commands into the AI generator, means that real artists who spend a lot of time creating music get almost nothing. Platforms are obviously fighting this, but with little success.

There is a legal issue here. You can easily listen to Metallica in country style, where the authors have nothing to do with it. Some creators try to fight this by deliberately damaging fragments of music in files.
Legal issues also apply to the data that AI spits out, including what you are asking about.

If you train your own AI model on your own data, this topic does not concern you.
The data on which AI is ‘trained’ in publicly available generators is controversial and unregulated.
Few people pay attention to this. Some of the data used by public AI tools (which may apply to programming code) has been downloaded
from sources that are not necessarily legal.


I hope that I have now presented my point of view on AI more comprehensively.
This is just my point of view. I translated it from Polish and I hope that everything has been translated correctly.
If the forum moderator thinks that my comment on AI is irrelevant, feel free to delete it.

Go to top


Re: Introducing Gabrielle - Xena's companion
Just can't stay away
Just can't stay away


@jaokim

I don't expect miracles from Xena, but if it can be useful for debugging in the future without extra hardware serial output and recording, that's really interesting.

Thank you for addressing this issue.

Retested with XTools1.7h

Issue:

4.RAM Disk:XToolsXenaStatus 
Warning
This set of XTools currently only tested on X1000
Setting up x5000
The support 
for X5000 is UNTESTED!
----------------------------------
If 
you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.

The only reason you would want to run these tests is to
inform the developer on your progress.

You can abort this process by entering '
q' at any testpoint.

You will be asked to enter something to continue before each test.

 YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!

Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter '
q' to quit, anything else to continue... 

-----------------------------------------------------
Performing test with ITimer->MicroDelay 0, with read/write 0x8000
with read/write 0x8000. Res in SIG1 is:   0xdead. Should be 0xdead
with read/write 0x8000. Res in SIG2 is:   0xdead. Should be 0xbeef.
with read/write 0x8000. Res in REG_HWREV: 0xdead.
with read/write 0x8000. Read scratch1:    0xdead (don'
t know what it should be)
with read/write 0x8000Read scratch2:    0xdead (don't know what it should be)
with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0001 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0002 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0003 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0004 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x000c is 0xdead 1101111010101101
with read/write 0x8000. REG:0x000d is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0010 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0020 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0021 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0022 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0023 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0024 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x002f is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0030 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0031 is 0xdead 1101111010101101
-----------------------------------------------------
Performing test with ITimer->MicroDelay 5, with read/write 0x8000
with read/write 0x8000. Res in SIG1 is:   0xdead. Should be 0xdead
with read/write 0x8000. Res in SIG2 is:   0xdead. Should be 0xbeef.
with read/write 0x8000. Res in REG_HWREV: 0xdead.
with read/write 0x8000. Read scratch1:    0xdead (don'
t know what it should be)
with read/write 0x8000Read scratch2:    0xdead (don't know what it should be)
with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0001 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0002 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0003 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0004 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x000c is 0xdead 1101111010101101
with read/write 0x8000. REG:0x000d is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0010 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0020 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0021 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0022 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0023 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0024 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x002f is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0030 is 0xdead 1101111010101101
with read/write 0x8000. REG:0x0031 is 0xdead 1101111010101101
-----------------------------------------------------
Performing test with ITimer->MicroDelay 10, with read/write to 0x8000
with read/write to 0x8000. Res in SIG1 is:   0xdead. Should be 0xdead
with read/write to 0x8000. Res in SIG2 is:   0xdead. Should be 0xbeef.
with read/write to 0x8000. Res in REG_HWREV: 0xdead.
with read/write to 0x8000. Read scratch1:    0xdead (don'
t know what it should be)
with read/write to 0x8000Read scratch2:    0xdead (don't know what it should be)
with read/write to 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0001 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0002 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0003 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0004 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x000c is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x000d is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0010 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0020 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0021 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0022 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0023 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0024 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x002f is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0030 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0031 is 0xdead 1101111010101101
Tests done.
Exiting since its all very unclear.
If you got good values back from test, things seem to work.
If there were good results for the delay 10 test, then you could continue to run
and stuff might work. If no good results were seen then you might as well abort now.
fatal: chain too long returned 128
Enter '
q' to quit, anything else to continue... 4.RAM Disk:XTools>

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Go to top


Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
Quite a regular
Quite a regular


@joerg

Quote:
An update of AmiDVD is available through Updater now.

Thank you so much Joerg. I downloaded AmiDVD 1.54 via Updater.

It works beautifully. I made a bootable backup of my system partition.

Thanks,
redfox


Edited by redfox on 2026/1/25 4:35:33
Go to top


Re: Introducing Gabrielle - Xena's companion
Just popping in
Just popping in


@Maijestro
@FlynnTheAvatar

Thanks for testing!
I've got yet another on to try out:
https://jaokim.github.io/files/XTools-1.7h.lha

This now does it according to TRM, but also adds some PPCs eieio, and sync. Lets see what it'll show us.

Maintainer and developer for Jamiga2 - Java for Amiga
Go to top


Re: Introducing Gabrielle - Xena's companion
Just can't stay away
Just can't stay away


@jaokim

Tested with XTools 1.7g on my X5000/40

I get exactly the same output as @FlynnTheAvatar.

4.RAM Disk:XToolsXenaStatus
Warning
This set of XTools currently only tested on X1000
Setting up x5000
The support 
for X5000 is UNTESTED!
----------------------------------
If 
you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.

The only reason you would want to run these tests is to
inform the developer on your progress.

You can abort this process by entering '
q' at any testpoint.

You will be asked to enter something to continue before each test.

 YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!

Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter '
q' to quit, anything else to continue... 

--- 8 memtest: reg: 0001, SIG2 should be 0xbeef
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0000, SIG1 should be 0xdead
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0002, HWREV should be 2210 perhaps?
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 000c, XDBG bit 7=1 if xorro, bit 8=1 if xtag detected 
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0004, LBALIVE should be 0001
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0021, DATELB should be low bits of some date
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0031, SCRATCH2
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

Tests done.
Exiting since its all very unclear.
Xena setup failed
4.RAM Disk:XTools>

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Amigans Defender
Amigans Defender


@joergQuote:
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).


I think there's no reason why colour outline fonts can't be supported by BulletAPI. Might need some extensions (not much different to the alpha channel glyphs that were added to OS4). I looked into it a long time ago and then didn't do anything with it. In theory you could convert colour outline fonts into bitmap ColourFonts too.

I might put this back onto my list as it's something I'd like to see but I'd forgotten about.

Go to top


Re: Introducing Gabrielle - Xena's companion
Just popping in
Just popping in


@jaokim

Thank you for your continued effort to make Xena work.

This is the output of XTools 1.7g:

XenaStatus 
Warning
This set of XTools currently only tested on X1000
Setting up x5000
The support 
for X5000 is UNTESTED!
----------------------------------
If 
you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.

The only reason you would want to run these tests is to
inform the developer on your progress.

You can abort this process by entering '
q' at any testpoint.

You will be asked to enter something to continue before each test.

 YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!

Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter '
q' to quit, anything else to continue... a
--- 8 memtest: reg: 0001, SIG2 should be 0xbeef
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0000, SIG1 should be 0xdead
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0002, HWREV should be 2210 perhaps?
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 000c, XDBG bit 7=1 if xorro, bit 8=1 if xtag detected 
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0004, LBALIVE should be 0001
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0021, DATELB should be low bits of some date
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

--- 8 memtest: reg: 0031, SCRATCH2
0xe0008000: dead dead dead dead dead dead dead dead 
0xe0008010: beef beef beef beef beef beef beef beef 
0xe0008020: dead dead dead dead dead dead dead dead 
0xe0008030: beef beef beef beef beef beef beef beef 
memtest done ---

Tests done.
Exiting since its all very unclear.
Xena setup failed

Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Just popping in
Just popping in


@LiveForIt

Hi! Thank you for your feedback, I totally agree with you. I've experienced first-hand that AI is not a magic wand. Many times it suggested code that looked okay but didn't work at all because it ignored how Amiga actually works.

I clearly noticed that as the project grew, the AI tended to get confused and make more mistakes. For me, it was useful as a 'talking book' to get started, but I realized early on that I couldn't trust it blindly. If I hadn't checked the code myself, line by line, trying to understand what was going on, the program would never have worked.

However, I believe AI is a huge help in two ways: for beginners, it’s essential to take those first steps and finally produce something functional, while for expert developers, it’s a fantastic tool to speed up the daily workflow. In both cases, you still need a human being putting in the time and patience to guide it, or you just get stuck. Thanks again for your insights!

AmigaOS4.1FE & AmigaOS3.2 on MacMini M1 - MacBook Air M4 - Raspberry Pi500+
Go to top


Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
Quite a regular
Quite a regular


@MazinKaesarQuote:
MazinKaesar wrote:@MazinKaesar

I solved my network issue with help from guys from Hyperion forums.

I run the command c:CheckRoadshowConfig VERBOSE and this was the output:

New Shell process 7
7.OS41
:> C:CheckRoadshowConfig VERBOSE
C
:CheckRoadshowConfigDuplicate service name "kshell/544/tcp"see line 217 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "ekshell/545/tcp"see line 218 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kerberos-adm/749/tcp"see line 220 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kerberos-iv/750/udp"see line 221 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kerberos-iv/750/tcp"see line 222 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kerberos_master/751/udp"see line 223 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kerberos_master/751/tcp"see line 224 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "krb_prop/754/tcp"see line 225 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kpop/1109/tcp"see line 227 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "eklogin/2105/tcp"see line 228 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "rkinit/2108/tcp"see line 229 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kx/2111/tcp"see line 230 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kip/2112/tcp"see line 231 of file "DEVS:Internet/services".
C:CheckRoadshowConfigDuplicate service name "kauth/2120/tcp"see line 232 of file "DEVS:Internet/services".
You may have to update or repair your Roadshow configuration files.


I removed all the duplicate entris in DEVS:Internet/service file and after a restart all seems working fine.


Thank you, exactly same issue on my Pegasos 2.

AmigaOS3: Amiga 1200
AmigaOS4: Micro A1-C, AmigaOne XE, Pegasos II, Sam440ep, Sam440ep-flex, AmigaOne X1000
MorphOS: Efika 5200b, Pegasos I, Pegasos II, Powerbook, Mac Mini, iMac, Powermac Quad
Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Home away from home
Home away from home


@smarkusg

It be stupid to not use tool that can help speed up development, we lack developers, we lack funding, and we lack the time. Anything can speed up development, or help if used correct should be used.

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Home away from home
Home away from home


@ldg72

the main issue with AI, is that when code base gets too big, the AI can’t keep track, and if you don’t understand the code, your stuck. As for sloppy code, AI often produce example quality code, and always need to read the code, before using it.

Often mistakes are unnoticed, memory is not cleaned up correct, things are not checked correctly. LLM produce code from what has learned from human mistakes. its not a inventor, but can stick different things to a degree to a degree.

The more you ask it to fix something, the more confused it gets, and suddenly see it undoing stuff.

AI is good learning tool, it help you get started, and it come up suggestions, it can prof read code, if you ask it, and it can be a aid, but it lacks creativity, focus and does not actually understand the impotence of the work its doing. the AI tool need guidance.

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top


Re: Has anyone ever made a Boing ball mouse pointer?
Just popping in
Just popping in


@NinjaCyborg

Not directly, but it shows that it's feasible.
Just get a nice sequence of boing balls to have the full rotation and apply the animation technique shown with the checkered arrow on the busy pointer instead, if you only want the busy pointer to show a rotating boing ball.

Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Home away from home
Home away from home


@joerg

I don’t think it makes sense to work on more up to date browser, before we have 64bit version of AmigaOS4, if keep running out memory, its no point having latest version, its nice to see progress on SMP.. but we have a long way to go..

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top


Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
Just popping in
Just popping in


@AlexC

Thanks a lot for your technical observations which I find truly interesting and valuable for improving the project. To be honest with you and the entire community I do not consider myself a C expert at all as my programming knowledge is actually quite basic. This is why I find it surprising that I was able to complete such a port because without the help of AI I would never have made it. For me AI has been a tireless tutor that allowed me to learn coding concepts while producing something useful and I believe this is a fundamental point for the future of AmigaOS. A clear example happened during the CuraEngine port where the AI initially pointed out the PowerPC big-endian issue but then during the conversion it actually forgot to handle the little-endian to big-endian transition. While testing the program I noticed it wouldn't read binary STL files even though ASCII STLs worked perfectly so I remembered the issue and explicitly asked the AI if we had done the conversion. Only after this correction of mine and a new compilation did CuraEngine start reading binary STL files correctly. I am currently also developing my own project from scratch which is a video processing program that uses ffmpeg and a MUI graphical interface. This is primarily an educational project for me and AI is helping me immensely to understand the complex logic behind MUI development. I must say that sometimes the AI makes mistakes and in those cases it is actually me who by studying the code and the SDK manages to correct it. It is a very active way of learning and today I wouldn't find any human tutor able to teach me how to program on Amiga so this has become a significant educational training ground for me. If someone with little experience can achieve these results just imagine what a veteran and trained developer like you could do by giving precise directions to the AI to accelerate the work and saving hours of tedious tasks. My work is not perfect yet but I hope it serves as proof that with AI and the right determination even those starting from zero can actively contribute to growing our software library.

AmigaOS4.1FE & AmigaOS3.2 on MacMini M1 - MacBook Air M4 - Raspberry Pi500+
Go to top



TopTop
(1) 2 3 4 ... 7610 »



Polls
Running AmigaOS 4 on?
AmigaOne SE/XE or microA1 12% (26)
Pegasos2 3% (8)
X5000 22% (48)
X1000 14% (30)
A1222 8% (19)
Sam 440/460 18% (40)
Classic PowerPC Amiga 2% (6)
WinUAE emulation 7% (16)
Qemu emulation 9% (21)
Total Votes: 214
The poll closed at 2025/12/1 12:00
6 Comments


Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project