[quote name=Amiwell79 post=8154]@Amiwell79 - Many ThanksB)[/quote] I checked the source. Changes to Poseidon USB class and camd.library are already integrated into AROS. The only thing was to compile usbmidi file. Please find it attached. Note: it's a straight recompilation - I have no way to testing if it will work.

The archive does not contain source for the library only sources for the player - that is why you are getting error "cannot find -lraudio' Also, please don't do any actions is RAM:Clipboards. This is a system directory used for copy-paste and working with files there might confuse system. If you want to use RAM, use RAM:T which is a temporary directory in RAM.

I tried compiling "raudio" see attached aros archive link, with AROS One 32Bit the compilation was successful, and the obtained raudio binary works fine. On AROS One 64Bit (both Vmware Windows, and Linux Hosted) I have errors with both GCC 6.5.0 and GCC 10.5.0, although the errors are different, see the 2 screenshots https://archives.arosworld.org/?function=showfile&file=development/library/raudio.i386-aros.zip

[quote name=AMIGASYSTEM post=8170]@AMIGASYSTEM I also noticed that there is still a "duplicate" Catalogs, there are "catalan" and "catalonian", Catalonia is an "Autonomous Community of Spain". [/quote] I'll fix that when synchronizing translations after the release. catalonian will be removed.

[quote name=AMIGASYSTEM post=8170]@AMIGASYSTEM - deadwood a question ! I noticed that the files of the Contrib have different sizes, for example the Libs folder, I assume it's the difference in the compilation, should I overwrite those of the Build ? [/quote] They are built from exactly same sources, but for sake a clarity, please always use file that came on the ISO instead the one from Contrib.

Catalan is a language of Spain (not Spanish, another Latín Dialect), Catalonianian and similar are the same... Where can I try any Linux Hosted for ArosX86? Is there any link to just Download and make a try?

deadwood a question ! I noticed that the files of the Contrib have different sizes, for example the Libs folder, I assume it's the difference in the compilation, should I overwrite those of the Build ? I also noticed that there is still a "duplicate" Catalogs, there are "catalan" and "catalonian", Catalonia is an "Autonomous Community of Spain". In the Demo folder of the Buid, folder MCC_NList, the demo "NList-Demo" crashes WMware and Guru on AROS Hosted

Beautiful news about odyssey without setting aside the rest of the plan

Hi, i am not sure if this fits in this topic, but if the objective is to run aros under emu68, maybe a better start would be to modularise the graphics support of the 68k port. as from this link [url]https://github.com/aros-development-team/AROS/blob/master/boot/modular_kickstart.txt[/url] These modules are not allowed to have machine-specific code because it violates portability convention. As of 12.09.2011, m68k-amiga (chipset-specific code in graphics.library) and PowerPC-native (display driver setup kludge in dos.library boot code) ports do not conform to this rule. Kind regards,

With recent release of 32-bit and 64-bit versions of AROS, I think it's high time to give update on developments ahead! Just as a reminder, this was the current short term plan: 1) Upgrade ABIv0 fully to 20241102 codebase [b][DONE][/b] 2) Synchronize ABIv0 and ABIv11 codebases to minimize differences [b][DONE][/b] 3) Provide synchronized releases of ABIv11 and ABIv0 [b][DONE][/b] Delivering on point 3) closed the first major milestone of long term plan. ABIv0 has now reached feature parity with 64-bit version. Now the focus shifts to second major milestone - the migration to 64-bit this year. So how will rest of the year look like? First of all I don't expect any major 32-bit or 64-bit release for remainder of the year. There will be lots of developments happening, but they all should be delivered in form of update packages. This means we will be incrementally adding features on top of stable bases and provide stability for users. I expect three development streams to be running in parallel: 1) Odyssey - the aim here is to get the browser updated to the level where modern online services can be used in stable and fast manner. This will allow substituting missing software for their online replacements during the migrations process. 2) Software - either via re-compilation or via emulator, missing functionalities will be added. The goal is not to have all the software from 32-bit working, but to have a least one software working good in each functionality category 3) Hardware - 64-bit system as it stands right now does not yet support parts of hardware that 32-bit system supports (for example NVidia cards). The aim here is to restore that support and hopefully add newer, easily available second hand hardware to our hardware base. The overall goal I see for this year is to arrive at situation where 64-bit version has better usability than 32-bit version today - but I can't do this alone! Please continue porting software to 64-bit - it's been great so far seeing several community members stepping up and working on ports. Thank you! If you are on the other hand interested in driver and kernel development - just let me know - and I'll get you up to speed! The long term horizon is now updated: "With ABIv0 reaching feature parity, work on a longer horizon will focus on 64-bit version of AROS and on AxRuntime. ABIv11 64-bit native will be fixed to provide the same level of hardware compatibility on recommended hardware as current ABIv0 32-bit. Furthermore, on software side, functionalities will be enabled by either re-compiling application or using 32-bit emulator where such process is not possible. On AxRuntime side, the goal will be to develop a working window manager (IntuitionWM) and Linux-native desktop, most likely in form of Scalos. All this work will enable creation and maintenance of two development lines: For people preferring native AROS we will have ability to use subset of the existing 32-bit software base on 64-bit AROS and a native 64-bit system working on recommended hardware, which then is an enabler for creation of 64-bit distributions that exceed current 32-bit distributions in user experience. For people interested in AxRuntime route we will have a Linux-native desktop and ability to run subset of AROS ABIv0 programs (32-bit) as well as 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."

Hi All, We are almost there with the release! Here are RC (release candidate) versions: [url]https://axrt.org/development/tmp/AROS-20250418-RC1-any-x86_64-contrib.tar.bz2[/url] [url]https://axrt.org/development/tmp/AROS-20250418-RC1-linux-x86_64-system.tar.bz2[/url] [url]https://axrt.org/development/tmp/AROS-20250418-RC1-pc-x86_64-boot-iso.zip[/url] Changes compared to 64D14: - Prefs/Boot - L/ram-handler - Devs/Drivers/vmwaresvga.hidd - C/Partition For contrib, fixes are in: - Libs/SDL.library If no major issues are found, these builds will become the final release builds next week. Full changelog: [code] AROS ABIv11 20250418-1 changes: Functionalities: AROS is now built with GCC 10.5.0 (Johan G) Network, audio and video drivers for VirtualBox, VMware and QEMU are improved and stabilized (deadwood) 64-bit native kernel received multiple fixes and is now stable (deadwood) Warm reboot is now more stable on several configurations (deadwood) Added several wide-char functions to C library (Deremon) Boot menu is simplified to provide best user experience by default (deadwood) Updates: AROS build system (deadwood, Johan G) InstallAROS v1.31 (deadwood) Documentation (deadwood) Kernel (deadwood) ahci.device v1.0 (deadwood) e1000.device v1.0 (deadwood) vmwaresvga.hidd v45.7 (deadwood) Prefs/Apperance v1.5 (deadwood) 64-bit support: pcnet32.device, e1000.device (fixed to work on 64-bit) (deadwood) HDAudio.audio, sb128.audio (fixed to work on 64-bit) (deadwood) AVX registers are now preserved when doing task switch (deadwood) z1.library (generate SSE4.1 code only when CPU support the instructions) (deadwood) System/FTManager (fixed to work on 64-bit) (deadwood) Functional fixes: dos.library (deadwood) InstallAROS (bugs: problems with UI elements after re-work) (deadwood) vmwaresvga.hidd (improved to work no both VMware and VirtualBox) (deadwood) Editor (bugs: #180) (DreamOS82) sfs-handler (bugs: offline volumes don't process ACTION_REMOVE_NOTIFY, missing ACTION_DIE) (deadwood) Wanderer (bugs: wrong matching of existing icons to volumes) (deadwood) crt.library (bugs: #123) (deadwood) diskimage.device (deadwood) Prefs/Boot (bugs: wrong parsing of some options) (retrofaza) C:Partition (bugs: creating AROS partitions when there are other partitions fails) (deadwood) Stability fixes: asl.library (bugs: crash with file requester) (deadwood) processor.resource (bugs: crash on QEMU) (deadwood) i8042.hidd (bugs: crash at system reset) (deadwood) crt.library (bugs: crash in vfork()) (deadwood) ram-handler (bugs: crash when using ExNext and file deleted) (deadwood) 68k support: amigavideo.hidd (faster LUT rendering, fix OCS and AGA cursor) (Johan G) graphics.library (improved detection and initialization of AGA) (Johan G) keyboard.device (bugs: #176) (Broadblues) ARM support: [/code]

Many ThanksB)

Let me see - if this is a quick and easy compile I can try doing it.

The file unfortunately is on archives inside the usbmidi package in theory should be included in the builds

Both 32-bit and 64-bit build have a file "debugdriver" in Devs:Midi so I'm not sure what driver you are refering to. If there is a file on 32-bit ISO that is not present on 64-bit please point me to the exact file.

[quote name=deadwood post=8147]@deadwood - I'm not sure what you mean. camusbmidi.class in part of ISO (SYS:Classes/USB)[/quote] Driver is missing in devs/midi

Glad to hear that (y)

Deadwood, I have good news my 2 Laptops ACER ASpire 5920 and AROS 64Bit both boot AROS 64Bit via the "noacpi" option in the Grub. Native card on the 2 Laptops not supported (also on AROS 32Bit) ACER Aspire 5920, no Audio (also on AROS 32Bit) Samsung R730, Touchpad does not work, USB Mouse works fine

I'm not sure what you mean. camusbmidi.class in part of ISO (SYS:Classes/USB)

deadwood since it is part of the system usbmidi it is possible to compile it:(