Why there are Wanderer in aros Ambient in morphos Amibench Etc Why not 1 desktop environment?

Deadwood was clear there will be 64-bit aros running under a linux kernel and applications will be native as they are now, plus for those who want to can run linux software and the desktop enviroment will be scalos

Many Thanks I uploaded the package to archives(y)

Hi and welcome matteo [quote name=matteo post=4211]@matteo - Hi, i'm an enthusiast of amiga and i follow community of aros. [/quote] The question that follows seem to indicate that you have not been following AROS community for a long time. No problem, i'll try to explain :) [quote] I'm interested in future, is possibile change aros kernel with a linux kernel? [/quote] Sure, no problem. You can fork the AROS project and go ahead :) This topic has been discussed several times during decades of development and AROS itself will not change its kernel to Linux because... then it will just be another Linux derivative. It will destroy the legacy as we all known to like. If you have been following AROS then you clearly have missed [url=https://axrt.org/]axrt[/url]. It is a project that attempts to accommodate some of AROS' shortcomings (though initially the axrt project has another goal). Besides that there is some other (side) project by deadwood in the making that might be of interest to you and that is an Intuition windows manager for Linux. [quote] Other interesting things MUI + Reaction = ArosUI[/quote] Reaction as in classact GUI successor ? Because if that is what you are suggesting then you do not seem to have the knowledge that these are both different technologies that can't really be compared or integrated together. It is either one or the other, and for sure you can run/install both but it would be comparable to using GTK and QT widgets on a Linux distro. The latter is actually such a difference that it could probably be considered using two different desktop environments at the same time. That is probably reason why you got the thumbs down.

Just run Ubuntu with an Amiga UI Theme

Maybe mui+reaction = arosUI haikufs -> arosFS fundraising with an organization to pay developer

The result of using a linux-kernal would be some kind of that, what you can see on Haiku as "fork" of BeeOS. By using it, it felt like a linux when using it - not as a BeeOS. The Btrfs-filesystem is very efficient, but have fragmenting-problem when using it. A new development of an new, AROS-/Amiga-orientated filesystem would be more useful then a btrfs or ext4-filesystem. Also, there is some kind of AROS with Linux-Kernal (AEros), which you can use on ARES-Computers. I had never the chance to use it, but it looks like a linux and not really like an Amiga. I do not want to tell that linux is a bad idea to use, but I'm very unsure if that would let Amiga still be Amiga or if it becomes an "linux-fork".

Hi, i'm an enthusiast of amiga and i follow community of aros. I'm interested in future, is possibile change aros kernel with a linux kernel? maybe: founding with a organization managed by deadwood aros 2.0: linux kernel with Btrfs filesystem aros 3.0: with new design. I like https://twitter.com/haroleethan/status/1693664013383762322 Other interesting things MUI + Reaction = ArosUI

Thank you, updated AROS One !

V2.6.5 released: https://hitchhikr.net/ptk_v2.6.5_aros.zip Source code: https://github.com/hitchhikr/protrekkr f.

thank you I will inform alfred in fact has problems it seems to me:)

deadwood you could update the "ZIP" command included in the contrib, basically the ZIP command only compresses files and does not compress folders !

I found out that there are two bugs in camdusbmidi.class.c which prevent from sending several midi messages in the function nParseMidiOut() : [code] switch(cmd>>4) { case 0x8: case 0x9: case 0xa: case 0xb: case 0xe: if(len < 3) { len = 0; break; } len -= 3; *out++ = cmd|chan; <<<< should be: *out++ = (cmd >>4)|chan; *out++ = cmd; ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask; *out++ = buf[ca->ca_TXReadPos]; ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask; *out++ = buf[ca->ca_TXReadPos]; ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask; goodpkt++; break; case 0xc: case 0xd: if(len < 2) { len = 0; break; } len -= 2; *out++ = cmd|chan; <<<< should be: *out++ = (cmd >>4)|chan; *out++ = cmd; ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask; *out++ = buf[ca->ca_TXReadPos]; ca->ca_TXReadPos = (ca->ca_TXReadPos+1) & mask; *out++ = 0; goodpkt++; break; [/code] A fixed version is now included within the archive: https://hitchhikr.net/mididriver.zip So to install the whole stuff: - Copy "mididriver" into devs:midi (and remove any file that may be there before). - Replace "camdusbmidi.class" from SYS:Classes/USB with the one included in the archive. - Reboot. f.

we await news from Alfred

no problem i can't test the driver properly i don't have the equipment nor the software i'll pass the file to Alfred hopefully it will work thanks for the help;)

Hi, My bad, I didn't check the out going data code assuming it would work but of course it didn't and made AROS to crash. I upload another version which doesn't crash ( https://hitchhikr.net/mididriver.zip ), i also added MidiThru (which forwards messages from a port to another) and MidiSendC (which sends a middle C to a given port) shell commands. The MidiWatch tool logs the out going port properly so the data is sent but i'm not sure that it reaches the Midi device itself. Sorry for the inconvenience, f.

Alfred writes: What I've done: 1. Connect USB-MIDI-Interface: Edirol UM-1 - success (is bound via camdusbmid.class to Poseidon-USB-stack, poseidon.library, showen in Trident Prefs for Poseidon) 2. Start BarsnPipes - success 3. Set MIDI-connection: connect to cluster "mididriver.out.0" - success (this is done via camd.library) 4. Send a simple NoteOn-event BarsnPipes->mididriver.out.0->camdusbmidi.class->UM-1 - failed (this results in a total crash) there is something wrong with the driver unfortunately:|

about bars&pipes: What I've done: 1. Connect USB-MIDI-Interface: Edirol UM-1 - success (is bound via camdusbmid.class to Poseidon-USB-stack, poseidon.library, showen in Trident Prefs for Poseidon) 2. Start BarsnPipes - success 3. Set MIDI-connection: connect to cluster "mididriver.out.0" - success (this is done via camd.library) 4. Send a simple NoteOn-event BarsnPipes->mididriver.out.0->camdusbmidi.class->UM-1 - failed (this results in a total crash) there is something wrong with the driver unfortunately:(

someone may be interested

yes I forgot to write that you have to subscribe