[quote name=Amiwell79 post=4086]@Amiwell79 - with this library only icon editor did not work for me mcc_thebar-26.15fix1.i386-aros[/quote] Are you saying you found program that does not work with 26.22?

[quote name=mattson62 post=4090]@mattson62 - Wow,Everything sounds very exciting![/quote] As it should be ;)

Today I checked WCS on real hardware and it runs. So the only problem is that it doesn't run under a virtual machine (VirtualBox 7.0.4).

Wow,Everything sounds very exciting!

I don't know what the problem might be then, I am using the latest mui texteditor class taken from aminet

I tried on: ABIv0 20220318-1 Aros One 2.3 In both cases nothing happens when I click on the program icon.

thank you hitchhikr to whom I asked about the porting and he replied in the affirmative hopefully everything will go well

with this library only icon editor did not work for me mcc_thebar-26.15fix1.i386-aros

then I am not aware of how Alexander compiled the software and on which build he tested everything I think the reference is one of the latest with changes to the c library

there are no special requirements apart from fixes to the muimaster.library which I remember caused problems for the correct functioning of the software, what distribution are you using I tiny Aros 3.1b

[quote name=Amiwell79 post=3977]@Amiwell79 - This is the v2.031 release of WCS Alexander has other ideas to make the software even more performant will work on it further https://www.adrive.com/public/MbuT6k/wcs-multi-aros.zip[/quote] Any special requirements to run this program? Nothing happens when I try to run WCS_i386-aros (the latest AROS build on VirtualBox).

deadwood seems to be doing very well, I tried about ten Hollywood Applications, among them the two most sensitive ones like RNOTune and IconEditor.

Please check this build: [b][url]https://axrt.org/development/TheBar_26.22-1.i386-aros.zip[/url][/b] I haven't tested it much - only with RNOTunes, so please do the testing with other applications.

[quote name=deadwood post=4074]@deadwood - I will try to port TheBar 26.22 and apply the fix from the 26.15fix1 so that we have a single version working with all applications.[/quote] Thank you Deadwood

many thanks Deadwood

Ok thanks, I will wait for this important library before I start packaging AROS One 2.4 Regarding the Hollywood Software, after a report I made to a developer, I discovered that starting with Hollywood 9 the Hollywood Applications look for the necessary Libraries/Codecs in the folder where the binary resides, ignoring the Libs/Hollywood path. The Loview developer got around this problem so that libraries located in SYS:Libs are also used by Loview ! The dual path is necessary for those obsolete software that uses an old Library, in which case you can copy the old library into its path, and all other more up-to-date software uses those in SYS:Libs. All this makes it possible not to have so many Hollywood libraries scattered throughout the system.

I will try to port TheBar 26.22 and apply the fix from the 26.15fix1 so that we have a single version working with all applications.

Hello, Another update from me on the plan: 1) Release new version of ABIv0 refreshed to 20211214 containing switch to new C library [b][DONE][/b] 2) Rebuild Odyssey Web Browser using GCC 6.5.0 and new C library [b][DONE][/b] These have been intensive two months, but we are finally pass that milestone! Next actions to undertake are: 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 3) Release new version of ABIv0 refreshed to 20221221 codebase With first item, I want to bring Odyssey to the level of stability that allows me to use it for everyday surfing of Amiga-related sites while continue using my main Linux Mint system for everything else. Any improvements that I will introduce will also be available to 32-bit version of Odyssey, so you may expect a small update there as well. With the second item, the emulator prototype, it's really the first steps to see what is needed and how to design the solution so that it takes least amount of work while supporting ~80% of existing third party 32-bit software. 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 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."

I talked to Alfred Faust all right he sent me what I needed:)

I think so but I'm not sure I have to ask