Who's Online |
52 user(s) are online ( 29 user(s) are browsing Forums)
Members: 1
Guests: 51
flash,
more...
|
|
|
|
|
Re: The Settlers II Gold Edition Comes to Amiga – October 18, 2025
|
Posted on: Today 18:06
#1
|
Not too shy to talk 
|
@thread
Did anyone in the US ever get their physical copies? I received an email from Simon back in October asking if I wanted the English or German version, but nothing since. I sent an email a couple of weeks ago asking if it ever shipped, and no response yet.
Wondering if I'm alone or maybe they halted shipments to the US because of tariff uncertainty?
-- eliyahu
|
|
"Physical reality is consistent with universal laws. When the laws do not operate, there is no reality. All of this is unreal."
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
Posted on: Today 10:27
#2
|
Just popping in 
|
@LyleHaze
You're welcome! I know the feeling, too many projects, too little time, and real life/work on top of it all :-/
I was also very eager to play with Xena but work got in the way and other projects too. Now I just realized that it's been 14 years already since I got my X1000?! That's scary, and I still haven't done anything useful with Xena.
|
|
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
Posted on: Today 10:14
#3
|
Just popping in 
|
@Hans
My hands-on experience with modern AI is limited to objects recognition, running DeepSeek locally on RPi5, and it works quite well in that narrow predictable context, so it may also be possible to generate an LLM from your own code archive on some powerful-enough local machine, or short-live online compute instance and then use that LLM on a less powerful machine. Still, I wouldn't trust AI when it comes to decision-making. It may be helpful to suggest the seemingly most appropriate options, but lacks any actual understanding of anything. With code though, since it is something so mechanical with rigid rules, it seems like it can be a useful tool once it knows all the rules.
|
|
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
|
Just popping in 
|
@joerg
Thanks Joerg for your insights!
Even though I wish it was otherwise, I do believe that the web browser has become the most important program any OS must have, at least to fully benefit from the mainstream web, but catching up with current web technologies is such a massive undertaking that for one or a few coders it's not possible to update what we have fast enough, let alone writing a new browser from scratch.
For that reason I think it makes sense to use what has already been written and keeps getting updated, by porting it, be it Chromium or FF, but even that is a daunting task, unless at least a hundred of us join forces (and we do have more than a hundred coders).
With or without AI, I think it's the most worthwhile undertaking to keep the platform relevant as a daily driver, and if we want at least a remote chance of getting new users (as long as the browser works most people don't care what's under the hood) and one huge benefit of being on an exotic platform is that none of the exploits and zero day attacks work on our architecture/OS making it quite safe to open any attachment without worries.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: Yesterday 20:39
#5
|
Just can't stay away 
|
@joerg Quote: joerg wrote:@redfox Quote:I wish I could use AmiDVD but it does not work with Update 3. An update of AmiDVD is available through Updater now. Thank you for your efforts. It's great to be able to make backups again with AmiDVD.
|
|
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
Posted on: Yesterday 11:00
#6
|
Just popping in 
|
@jaokim:
Sadly, I have the same output as Maijestro on my X5000/20.
Something is still very strange. Like as some compoment of AmigaOS 4.1 is blocking the reads to the registers.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: Yesterday 7:58
#7
|
Just popping in 
|
@joerg Quote: An update of AmiDVD is available through Updater now. Superb, thank you!
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
|
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
|
|
|
|
Re: Life of Tech
|
|
Just popping in 
|
|
|
|
|
|
|
Re: HunoPPC
|
|
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
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
|
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.
|
|
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
Posted on: 1/24 23:51
#12
|
Not too shy to talk 
|
@smarkusg
no one cares
|
|
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
Posted on: 1/24 22:41
#13
|
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-plagueThe 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.
|
|
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
Posted on: 1/24 21:55
#14
|
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:XTools> 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...
-----------------------------------------------------
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 0x8000. Read 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 0x8000. Read 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 0x8000. Read 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
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: 1/24 21:21
#15
|
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
|
|
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
Posted on: 1/24 20:48
#16
|
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.lhaThis now does it according to TRM, but also adds some PPCs eieio, and sync. Lets see what it'll show us.
|
|
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
Posted on: 1/24 20:13
#17
|
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:XTools> 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...
--- 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
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
Posted on: 1/24 17:41
#18
|
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.
|
|
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
Posted on: 1/24 16:04
#19
|
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
|
|
|
|
|
|
Re: New Port: Paho MQTT C and CuraEngine for AmigaOS4
|
Posted on: 1/24 12:53
#20
|
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+
|
|
|
|