With this bug fix, an old bug has returned on Wanderer, it is not possible to move 'overwrite' a file.

TLDR: >>>> [b][url]https://github.com/deadwood2/AROS/labels/IBOTM [/url][/b]<<<< 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.

Given the requests, I will see if I can create a download package with instructions!

Ok, thanks for tests. I'll wait for a day or two for any other tests and then close the bug report.

[quote name=deadwood post=5671]@deadwood - Hi All, Here are fixed for bug #140: [url]https://axrt.org/development/Wanderer.20240621.i386-aros.zip[/url] I tested them with renaming RAM Disk, but hopefully they also work with renaming disk drivers. Let me know.[/quote] Perfect deadwood, I successfully renamed both AROS and FAT32 formatted volumes.

Thank you Deadwood, as soon as I get home I'll do all the necessary tests, now I'm going to the sea, it's 40 degrees in my region!

Thank you Deadwood:)

Hi All, Here are fixed for bug #140: [url]https://axrt.org/development/Wanderer.20240621.i386-aros.zip[/url] I tested them with renaming RAM Disk, but hopefully they also work with renaming disk drivers. Let me know.

Any chance you can share the program? I use QEMU a lot and this would be a fantastic tool to get away from all my .bat files.

Hi G-linx, There were only minor changes in final prototype version so you can consider version from #62 as up to date.

Awesome Deadwood! :) ..Is the final prototype download link the same as in post #62?

thank you deadwood:)

and amiga desktop as linux desktop is important. My personal favorites are scalos and magellan

Great work as always!

No never distributed, although very simple and functional, it is not professional software, I only sent it privately to those who requested it.

Hello, An update on the plan: 1) Release 64-bit version of Odyssey Web Browser for AROS, Linux and Windows 2) Implement first prototype of 32-bit-under-64-bit emulator for AROS [b][DONE][/b] 3) Release new version of ABIv0 refreshed to 20221221 codebase Work on the prototype has been completed. You can read more in this post: https://arosworld.org/infusions/forum/viewthread.php?thread_id=1218&rowstart=60&pid=5506#post_5506 I will now take a short break and then will start working on topic of 64-bit OWB . The long term horizon stays unchanged: "On a longer horizon, there will be a lot of work related to ABIv0 and AxRuntime. I want to update ABIv0 to be based on latest ABIv11 source code. This will be an enabler to: 1) develop an emulator that will allow running AROS 32-bit programs under 64-bit AROS. 2) develop a version of AxRuntime that is capable of running ABIv0 32-bit programs on top of Linux and Windows Furthermore, ABIv11 64-bit native will be fixed to provide the same level of hardware compatibility on recommended hardware as current ABIv0 32-bit. On AxRuntime side, the goal will be to develop a working window manager (IntuitionWM) and Linux-native desktop, most likely in form of Scalos. Once all these things are in place, there will be two development lines available: For people preferring native AROS we will have ability to use majority the existing 32-bit software base on 64-bit AROS and native 64-bit system working on recommended hardware, which then is an enabler for creation of 64-bit distributions that match current 32-bit distributions in user experience. For people interested in AxRuntime route we will have a Linux-native desktop and ability to run majority of AROS ABIv0 programs (32-bit), AROS ABIv11 programs (64-bit) and AxRuntime-recompiled programs (64-bit). This way existing distributions could be re-created using Linux as a base without loosing existing functionality for users."

And here comes the final update: 1) Test a recent program written in C using new C library (Calculator) [b][DONE][/b] 2) Test an old, 3rd party program written in C using old C library (ZuneARC) [b][DONE][/b] 3) Test program written in Hollywood (HFinder) [b][DONE][/b] 4) Test program written in Pascal (MCAmiga) [b][DONE][/b] 5) Test emulator under native AROS x86_64 and confirm it can work with native kernel [b][DONE][/b] 6) Test emulator under AxRuntime and confirm ABIv0 programs can be run directly on Linux/Windows [b][DONE][/b] As you can see on the screen shot, ABIv0 program is running on the emulator which is running on AxRuntime making the ABIv0 program run directly on Linux (and using WSL also on Windows). To summarize the prototype: I believe it will be feasible to develop the emulator with limited cost, although higher than I initially expected. The emulation interface is quite narrow (exec, dos, graphics, cybergraphics, intuition) while re-using other 32-bit libraries, which is a good thing from point of view of how much it will cost to develop the emulator. Eventually I believe the decision whether to port & re-compile the application to 64-bit or to upgrade the emulator to support it will have to be made case-by-case looking simply at what is less costly (=time consuming). The role of the emulator is to form a temporary bridge to allow the migration. With time emulator should be used less and less with more and more applications being native 64-bit.

Did you made it available somewhere?

Due to some requests from users I have changed the look of my GUI, now the "Buttons have shortened terms and in English. I developed the GUI a few years ago for my own needs so that I could have all the OSs I normally use for testing at the click of a button. Initially there was no AROS then I wanted to include it because some users use QEmu to virtualise AROS x86. [img]https://www.arosworld.org/infusions/forum/attachments/qemu-gui.jpg[/img]

Yes, you are right, I was referring to the selection, I misspoke, I was referring to the fact that for detail you can use light backgrounds to display characters well, whereas for icons it is the opposite, i.e. better with dark backgrounds, for changing the colour of the text it would be useful to use a Font Prefs like the one in OS 3.1/3.9, see screenshot