And we have a tie this month! To resolve that I did a flip of the coin the and winner is #125 - so this bug will be fixed in May. As for #140 it will then automatically be selected as June's bug.

Thanks Deadwood. I though it might be something like that :) I will try now.

many thanks deadwoodfor fix release

For D520 you need to add 'noacpi' to grub command line in order to boot.

I tried this build and AROS ABIv0 20211128-1. None of them work. Boots from CD then stops with some APIC failture. This is with DELL D520 laptop. The latest build from Deadwood that work fine is AROS ABIv0 20201110-2

Ok Thanks deadwood, I will test and report any problems, as soon as you release the stable version I will build the new AROS One 2.5 !

Hi All, I prepared an update package for the 20220318-1 release. It contains all the changes since the release was made. Please test it and if all works ok, it will be officially released in a couple of days: [b][url]https://axrt.org/development/AROS-20220318-1-U1-any-i386.zip[/url][/b] [code] AROS ABIv0 20220318-1-U1 changes: Functionalities: Simplify adding tethering in Prefs/Network (#115) (deadwood) Speed up boot using ahci.device (deadwood) Delete files with DEL key in Wanderer (#116) (deadwood) Updates: Use standard C library function names in SDK (deadwood) Functional fixes: camd.library, camdusbmidi.class (hitchhikr) ram-handler (bugs: #134) (deadwood) ahci.device (bugs: #135, unnecessary 60MB memory allocation) (deadwood) Wanderer (bugs: 105, offline volumes showing with "ghost" icons) (Kalamatee) rtl8139.device (bugs: no support for wrapped buffer) (stegerg) Stability fixes: crt.library (bugs: calling atexit in CTOR set crashes program) (deadwood) 64-bit/68k/ARM support: [/code]

Thanks to all who voted already and a reminder that today is a the last day to vote.

Done some tests confirming what said to jPV, the problem "output.txt" empty, as I had suspected is the fault of LHA native AROS version. I tried running the command c:lha *>ram:output.txt on "AROS 68k" with two LHA versions, one Native and one AmigaOS LHA (Native AROS) -> Generate output.txt "Empty" LHA (Native Amiga v22) -> Generates output.txt "output Corrected " Done other test on AROS x86 with [url=http://archives.aros-exec.org/?function=showfile&file=utility/archive/lha_4u4a-i386-aros.lha][b]This[/b][/url] version of LHA, output.txt is saved correctly !

Yes the problem of the "output.txt" file generated "Empty" exists on AROS x86/68k, but I think that of hangs from LHA which does not work well on AROS, in fact on AROS One I don't use LHA anymore, instead I use "XadUnfile" which works better and supports miolti other formats. Redirection with other Commands works fine and the file "output.txt" is generated correctly On AROS as reported [url=http://www.aros.org/documentation/users/shell/introduction.php][b]HERE[/b][/url] the Redirection should work fine: Example: dir >ram:a -> correctly generates the output file ! Also the command c:lha >ram:output.txt *>>ram:output.txt, works fine on AROS, but it generates an empty file !

Hello, I had discussions on amigaworld where jpV told me that he had problems with amigscripts (DOS) on AROS. I was surprised and asked him for examples. He referred to two problems he found. https://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=45085&forum=33&start=1160&viewmode=flat&order=0 One seemed to happen with lha and stderr output in a file:. He already reported it: https://ae.arosworld.org/index.php?topic=695.msg6759#msg6759 Another one which command who not found files, f.e. in C I tested both in my distribution and had no problems but I heavily mix aros and amiga components. Could someone test on X86 and report if the problems are still valid?

Number #140 seems to be popular as well.

Voted.

Thanks voted for #125

[quote name=AMIGASYSTEM post=5059]@AMIGASYSTEM - Regarding Bug #136, I noticed that the "S" flag is set on some files by the Startup-sequence after the first reboot, so done fixing then you can delete these strings![/quote] I don't think this will be possible. These files on ISO image won't have the S flag, so if the commands are removed from Startup-Sequence, then they will never get these flags on HDD.

voted many thanks Deadwood

Regarding Bug #136, I noticed that the "S" flag is set on some files by the Startup-sequence after the first reboot, so done fixing then you can delete these strings!

TLDR: >>>> [url][b]https://github.com/deadwood2/AROS/labels/IBOTM[/b][/url] <<<< Here were are with another IBOTM! We continue with bug-fixing fun! PS. If there are additional bugs that irritate you, but they are not yet > the bug tracker, please report them in the release support thread. They might make it to the voting in following months! General rules are simple: 1) Bugs are selected from bugs reported > bug tracker 2) There is a poll made and community selects one bug from suggested bugs 3) I fix the bug. 4) Wait until next month; Go To 1; The initial list of bugs will be related to ABIv0 i386 or ABIv11 x86_64. In effect bugs specific to m68k AROS or any other AROS flavor won't be added to poll options. Bugs can be in either AROS core system or in Contrib package. Bugs need to be reproducible on clean system releases, so bugs visible only on distributions won't be included.

Ok, with that I'm closing April's IBOTM. Tomorrow we will open voting for May's bug!

@AmigaMia Right, on some keyboards you also find also Del O Canc @deadwood Ok, mine was just a report, we will wait for the new feature in the next builds !