Hi Swisso,

UBoot does not recognize the sii3114 card at all. This means that you cannot boot from any device connected to your sii3114. But once you booted into Amiga OS 4.1, its drivers take over and you should have access to all devices connected to the card.

Could you please check if you have the following line (not comment out) in your Sys:Kickstart/kicklayout file?

MODULE Kickstart/sii3114ide.device.kmod

Amiga OS 4.1 needs that to access the card and the devices connected to it.

If you have the driver activated, maybe you need to configure the HDs in Media Toolbox first before they show up in your system. Are the HDs empty, or did you already initialize them on a different Amiga system?

And I also have a sii3114, but I have only a DVD drive connected to it. On my card, the connectors are not covered in hotglue. But I think somebody did this to secure their cables.

@Rigo

Thank you very much for the new version. AmiUpdate 2.51 did not show the 2.52 update, so I downloaded the full 2.52 archive and installed that.

As others already said, 2.52 now works flawlessly. No more error messages, and it also showed two additional updates that I never saw with 2.49, 2.50 or 2.51.

Thanks again for your great work!

@Rigo:

The pop-up window with the error message only appears if you activated "Start iconified (recommended)" and start AmiUpdate a second time (either by clicking on the Icon in the sys:System/AmiUpdate directory, Icon on AmiDock - not the docky, or using the Windows->Update Software menu).

Clicking on the AmiDock Docky does nothing but changing the icon to an arrow pointing down. Therefore clicking on the docky will not trigger the issue.

When I deactivate the option, the error window will not show and AmiUpdate starts fine.

@Rigo

Several people reported the same issue in this thread (sailor,
Maijestro, AlfredOne).

So, it is not just me...

@Rigo:

Just updated to 2.51 from 2.50. Self-update worked without any issues.

But I still get the same pop-up as on 2.50:

The application "AmiUpdate" has opened version 2 of the interface "application", but tried to pass version 1 tag definitions to application.lib!

Please inform the author about this problem.

Note: The called function (and hence probably the application itself) will fail now.

As with 2.50, clicking on the icon on AmiDock after starting does not open the application window.

Thank you for the suggestions, but they do not work. Using "DELETE #?" or "rm *" always opened the window with "Please insert volume ...".

Also, renaming had the same issue.

@joerg: The filesystem is NGF\00. And yes, it is ancient, there is a new version, but the general public has no access to it. <rant>As for most other improved components of OS 4.1</rant>.

EDIT:
If you want to reproduce the issue, create a file, and rename it to <File>: in Directory Opus 4. And see if you can get rid of it without using DOpus again.

To answer my question: strangely enough, Directory Opus 4 was able to handle this issue and delete the file.

Not sure what Directory Opus does different than WB or DOS...

Hi,

I have an issue that Wookiechat created a log file ending in ':'. Do not ask me how it managed to do it.



But how do I get rid of it? Deleting with shell, Filer or WB does not work. Everytime I try, I get a window saying:
"Please insert volume AmigaWorld.net_#amigadev: in any drive"

Any idea?

Thank you,
Flynn

Great work!

I tried the new binutils + gcc-11.3.0 + clib4 with a number of small standard C programs without any issues. I did not check if the file sizes, though.

@joerg

Hi,
I have the same issue with my DVD drive/burner.

Media Toolbox says:
HL-DT-ST DVDRAM GH23NSD5, Version LV00

AmiDVD shows:
Device sii3114ide.device (yes, I connected my DVD to a SII3114)
Firmware date: 2019-06-12 14:59:
Serial number: KLJLBOG3400
MMC-5

In read/write everything is checked but for
rows RWDL and MRW.

Hi AmigaSociety,

Not sure if you already did it, or have the equipment to do so, but I would try to capture the serial output of the X5000 on a second computer. You would need a null model cable and maybe a USB to RS232 converter.

I permanently hooked up my X5000 to another PC to get the stack traces if my X5000 crashes. That is really helpful if the X5000 freezes, as most of the time one program crashed and took the entire OS with it.

This might help you with setting it up:
https://wiki.amigaos.net/wiki/Advanced_Serial_Debugging_Guide

Regarding the missing include from the SDK, this can happen if you have a broken lha installed in Ubuntu. All versions that come with Ubuntu do not work correctly.

This should be a working version, but you need to install it manually (download, ./configure, make install, ...): https://github.com/jca02266/lha

If you try to debug programs on a X5000 you are out of luck anyway. The stock kernel on a X5000 is broken and prevents any debugger (gdb, DB101 or Spotless) to work.

As kas1e says, printf/kprintf/IExec->DebugPrintF are your friends.

And maybe that helps you finding the problematic line of code after a crash: https://wiki.amigaos.net/wiki/Using_Crash-Logs_for_Debugging

@cnicol

Thank you very much for fixing the bug and the explanation. Yes, I can imagine that this causes serious issues if you need the column length for formatting the output, but you do not get it because of the backticks.

I hope the fixed command is available soon.

@rjd324

This is a bug in DIR 54.5.

I switched to the DIR coming with the installation CD (Version 53.3), and it works without any issue.

Hi,

I was trying to run the tests from the adtools_testing repo on my X5020. But the Enhancer DIR command (Version 54.5) constantly crashed with an DSI.

Crash log:


The crashing command is


Running the command without the backticks work. With backticks it crashes.

Update:
Minimal test case:

@rjd324

Thank you, with your latest change I could generate a cross-compiler.

Some of the tests fail to build, though. I am looking into it.

@rjd324

Thank you for providing such an easy solution for compiling gcc. I managed to compile a cross-compiler using the normal adtools repository, but the script makes everything much easier.

Sadly, it does not seem to work on aarch64 (Raspberry Pi). It would be great if you could make it work on this platform, too.

@white

Yes, this is correct. In the latest official release (0.8.29), only the SDL version supported UAEGFX.

LiveForIt did a lot of changes to make UAEGFX work with AmiGFX/NON-SDL graphics driver. But he prioritized making it work on the 8bit and 32/24bit modes.

@white

Yes, you are correct. 16bit color depth is only working on SDL or the original E-UAE 0.8.29 AmiGFX version.

And sorry, I just compiled the changes by @LiveForIt. He would be the better person to ask. Sadly, he stopped working on the AmiGFX improvements.