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

With Amiga Browsers it doesn't work, on AROS you have to wait before using it, because it requires upgrade to Premium for a fee, if you don't do it the waiting time gets longer, I would say to discard, much better "AmiFox" which is native AROS and works very well and you can access any site !

a service for obsolete browsers for those who use the internet intensively and do not just surf amiga sites https://www.browserling.com

Alfred Faust is also working for us is bringing BarsPipes to Aros thanks to everyone who has contributed to this

Guteprint is the next target I thank Alexander for his availability I personally will continue to donate for the work he is doing for the aros community

i asked Alexander the author of the wcs porting if he could work on guteprint and give us a printing system on aros he replied that he is still working on wcs again to improve it, maybe in the future we can hope for more portings, he is very kind and skilled in programming

Hello, If you are a developer who wants to port or develop software for AROS ABIv0 (32-bit x86), this post will provide resources to help you with your work. [b]Compiler and SDK[/b] Currently AROS ABIv0 provides GCC 6.5.0. If you plan developing [b]natively (directly on AROS)[/b], the compiler and SDK are already pre-built and available on installation disk. When installing through InstallAROS, select "Install Debugging tools and Developer software" option. After installation, GCC will be available from AROShell and Unix Shell (sh). If you plan developing through cross-compilation, you will need to build cross-compiler and SDK on an instance of Linux. This can be done directly on Linux or indirectly on Windows. If you plan developing[b] through cross-compilation[/b] and you are [b]a Windows user[/b], the recommended method is to build AROS under Linux through WSL. The tutorial on how to do this is available here:[url]https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/[/url]. Please note that tutorial described setting up environment for 64-bit AROS. In order to build ABIv0 32-bit x86 AROS, you need to make some slight adjustments so that process matches following tutorial: [url]https://github.com/deadwood2/AROS/blob/alt-abiv0/INSTALL.md[/url]. Remember to checkout branch alt-abiv0 in both AROS and contrib git clones in this case. Alternatively, you can set up a virtual machine with Linux installed and simply follow the section below. If you plan developing [b]through cross-compilation[/b] and you are [b]a Linux user[/b], you will need to build cross-compiler and AROS directly on your machine. The tutorial for doing this is available here, [url]https://github.com/deadwood2/AROS/blob/alt-abiv0/INSTALL.md[/url]. Be sure to follow section on "Linux-i386". Once you complete these steps, additional steps (building contrib and making cross-compiler scripts) can be followed in "WSL" tutorial: [url]https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/[/url]. Remember to checkout branch alt-abiv0 in the contrib git clone. At this point, whether you are a Windows or a Linux user, you have a cross-compiler available with full SDK as well as local compilation of AROS hosted which will allow you to quickly test your software. [b]Documentation[/b] Your main point of reference should be Autodocs. These are compiled from source code and thus are always up to date. You can find them here: [url]http://www.aros.org/documentation/developers/autodocs/index.php[/url] Next, there are two repositories of documentation on different topics related to AROS. They have different levels of freshness and up-to-dateness, but are good to show general direction. First is developers documentation on www,aros.org, and specifically: [ulist=circle][url]http://www.aros.org/documentation/developers/app-dev/index.php[/url] [url]http://www.aros.org/documentation/developers/zune-dev/zune-application-development.php[/url] [url]http://www.aros.org/documentation/developers/debugging.php[/url] [url]http://www.aros.org/documentation/developers/porting.php[/url][/ulist] Second is developers documentation on AROS Wikibooks, and specifically: [ulist=circle][url]https://en.wikibooks.org/wiki/Aros/Developer/Docs[/url] [url]https://en.wikibooks.org/wiki/Aros/Developer/Porting_software[/url] [url]https://en.wikibooks.org/wiki/Aros/Developer/Zune[/url] [url]https://en.wikibooks.org/wiki/Aros/Developer/Zune/Classes[/url][/ulist] Last group of reference comes from documentation of projects that AROS integrates or re-implements: [ulist=circle][url]https://github.com/amiga-mui/muidev/wiki[/url] [url]https://amigadev.elowar.com/[/url] [/ulist] [b]Contact/Questions[/b] There are multiple ways you can get in touch with other developers to get help and have your questions answered: [ulist=disc]Create a thread in this forum Join #aros channel on AmigaDev discord ([url]https://discord.gg/nU3tH86acb[/url]) PM user deadwood on this forum[/ulist] Also if you don't have any questions, but would just like to share with AROS community what you are working on, this forum is the place to post. Looking forward to hearing from you!

do not have sonos speaker sorry:(

[quote name=AMIGASYSTEM post=4148]@AMIGASYSTEM - Today I tried installing AROS One 2.4 from Pendrive by adding the "S" flag to a text file (script), fiinished the installation I noticed that on the Hardisk the "S" flag had disappeared. It seems that InstallAROS deletes the Flags during the copy phase, this should not happen because if there are scripts with the "S" flag in the system, these files once installedat would no longer work. [/quote] I created a new bug report: [url]https://github.com/deadwood2/AROS/issues/136[/url] [quote name=AMIGASYSTEM post=4148] I don't remember reporting the ghost "icons" problem on Wanderer, that if you try to delete them, instead of being deleted they multiply, it is solved only if you delete the .backdrop file Ghost icons appear for example when the .backdrop file is linked to a file that is no longer on the system. [/quote] I added this to existing bug report: [url]https://github.com/deadwood2/AROS/issues/25[/url]

Today I tried installing AROS One 2.4 from Pendrive by adding the "S" flag to a text file (script), fiinished the installation I noticed that on the Hardisk the "S" flag had disappeared. It seems that InstallAROS deletes the Flags during the copy phase, this should not happen because if there are scripts with the "S" flag in the system, these files once installedat would no longer work. I don't remember reporting the ghost "icons" problem on Wanderer, that if you try to delete them, instead of being deleted they multiply, it is solved only if you delete the .backdrop file Ghost icons appear for example when the .backdrop file is linked to a file that is no longer on the system.

The OS3, OS4 and MOS versions posted on Aminet include a Guide file. http://aminet.net/search?query=SonosController

Hi, I do not have any Sonos stuff , just wondered if the guide gave an idea what was supported as there are a few models over the years? https://en.wikibooks.org/wiki/Aros/User/Applications#Audio

Michael Rupp developer of "SonosController" kindly asks if any AROS users owning "SonosController" could test the operation. Michael Rupp provides his Email for any comments on the operation of "SonosController" The "SonosController" Software for AROS x86 is not yet officially distributed , I have a betatester copy which I could attach here, or wait for AROS One v2.4 where it will be installed. Soon you will also find it on Archive AROS. [img]https://www.arosworld.org/infusions/forum/attachments/sonoscontroller.jpg[/img]

Yes I always use execute "Script," but if you add the "S" flag, you don't need to use the Execute command, because it will still be used in a hidden manienra. I am not referring to ordinary scripts like the startup sequence, but you have text files with the Flag "S", they basically work like .Bat files on Windows. Any amigados script can be run if you add the "S" flag. I made a small video showing what I mean, I used a Shell but you can run the script as an executable even from Wanderer ! And unfortunately on FAT32 and CDFilesystem the "S" flag is not supported ! That's why I was asking if you could compile the scripts, on OS3, OS4 and MOS there should be, I also remember that there is an amiga program "Picture To EXE", which converts a picture to an executable

I'm not aware of any way of doing this. However running scripts work, at least on ISOs. Startup-Sequnce is a script as well as User-Startup. Have you tried "Execute <script>" command?

deadwood can you compile a script so that it transfers to an executable ? I ask this because scripts with "S" flag will not work on FAT32 and DVD !

thanks also to Kalamatee, Neil cafferkey and Alfred Faust for their commitment to driver development:)

hitchhikr it is difficult to implement midi on Protrekkr!