@geennaam
Quote:

I am on the Enhancer beta list and as much as I know, the HDAudio driver is not included in the latest beta package, nor it was mentioned that it will be included in any email. So I didn't know that this would come or not with Enhancer, as Matthew never shared that information in the mailing list.

But even if I knew that, I couldn't share it publicly, since I, in contrast with you, I honour my NDAs.

Quote:

Well, to be honest with you, I do not know what is this exceptional thing you are working on and if it will see the light of the day for the OS4 community to use. I am sure it would be useful.

I am sorry that for one more time you develop so much drama out of nowhere. I do not know why you do it, and this is not my concern, but this is the third or fourth time you do the same thing here in this forum and in the Discord channel.

So instead of attacking people personally, and the community in general, please consider deciding:
- if you want to leave, please do so
- if you want to stay, we would be more than happy to have you with us
- if you would like to develop and release software/hardware for the OS4 community, please do so
- if you want to cease all of your projects and leave, farewell and good luck

But please stop bringing drama where there is none. Respect us, respect the community, respect the companies so that you can get back all of our respect and appreciation.

And finally... HAVE FUN.
If you don't, there is no reason to be here.

In my situation, I only use old SounBlaster cards, for which drivers are coming with the OS. I would suggest everyone to use these cards and get rid of this drama, having a usable system.

Quote:

This is reality. You have to get down to the earth. If anyone wants to use their hardware, they will try to find a way to do it. Since you decided to "panish" the community months ago just by removing the driver from OS4Depot, do not expect that the users will not try to find it any way they can.

If people share the driver "illegally" as you say, then you should help them do it legally, which you didn't. Instead of being thankful for people finding your work useful, you end up accusing us (and me personally) for being immoral. That is your opinion, but do not expect us to agree with that.

Yes, people should respect the licence file you included in your archive, but you also need to land to reality and start doing something useful.

I do not know if I am immoral because I proposed you solutions. If that's the case, so be it. But please think before you talk.

Quote:

I am looking forward to hearing ACube's side of the story since geennaam is so offended by their actions and decided to bring this matter public, instead of solving it with them.

@geennaam
It is interesting that instead of trying to solve any issue, you just try to victimise yourself and blame the community ones again, calling us immoral. I once again offer my help to have your drivers hosted and sold by you, if that's what you need to do.

Quote:

Yeah, CubicIDE has an old version. I do not let the plugin do the SDK installation.
SDK has multiple different versions which you can select with its installer. There is GCC 8, 10, 11 and 6 for SPE compatibility (A1222).

Quote:

GCC 4.x is not part of the SDK 54.16? How did you install it and why you prefer to use that old version? Is there some kind of a benefit using it?

If we would like this community to remain alive and vibrant, the users should be helped to have fun with their computers as much as possible, with less problems.

@geennaam
The reason people are trying to find the driver here and there, as others mentioned previously, it is because they want their hardware to be usable. In my opinion, it is your fault you didn't establish yet, after so much time, a way for everyone to get the driver from any other "legal" source. It is effortless nowadays to set up a simple page to sell your drivers. This way, anyone would link to your website and the only source will be yours.

I would suggest you set up a ko-fi page (ko-fi.com) which provides that feature, having products and people buy them, and it is easy to configure. I would be more than happy to help you with that if you need help.

Have also in mind that this is not going to protect you from "piracy". I have seen people doing that with software even nowadays. OS4 and OS3 are shared openly. Archive.org has them as well. And that has been happening for decades, and I do not expect it to change.

Threatening and blaming the community (again) doesn't help nor you nor anyone. So, please, do the best you can and want to do, and spare the drama. If ACube made a mistake, speak with them and solve it. I do not believe they had any bad intentions, nor they got rich by selling Audigy FX cards.

What it needs is a willingness to solve issues and not create more.

You are welcome, mate.

I found it in my files. Sent you a message on discord to download it.

@root
Thank you for your kind words.
That is part of the treeview module, that why it requires it to be active. If I wanted to do something like that I would create my own plugin and create there a new menu item, that would do exactly that and have the same functionality. That means that you might need to copy code from the treeview module.

The reason I am saying that I would make this implementation in a new plugin is that this way every new Lite XL release will not replace those changes, and they will keep working as long as this plugin is installed. Writing a plugin is not that difficult because it uses Lua and there is no need to compile the editor. You can get examples from the rest of the plugins.

Try whatever customisation you want to do, to make them in a way that it doesn't change the release code. This way you will not need to make those changes after every release, and they could be shareable with others.

If you need more info on that, I would be more than glad to help as much as I can.

Quote:

Not at all. It is a pity you sold your Amigas back then. But it doesn't matter any more. Now you are here, and I wish to have a lot of fun with your new system.

I am starting this thread because I saw some messages about the SPE support in the last released SDK. Because I care to make it even better in the next releases, I would like you to add here the problems you have, examples or ideas.

Let's have a discussion on how to improve the SDK support to the SPE based systems.

@kishigo
Welcome to amigans forum. We are glad to have you here.

Did/do you have Classic Amigas?

What drove you to AmigaOS 4? Were you exposed to it at some point somewhere, and then you decided to buy the hardware for it?

In case you have questions, we will be more than happy to help you in here. Please do not hesitate to ask questions.

Three weeks passed since I did a new release for the Lite XL editor, and now I managed to find some time to write about it. Please have a look at https://ko-fi.com/post/Lite-XL-v2-1-3r ... d-some-time-ago-W7W0W6E3M and find out all the new features and bug fixes that are included.

Tomorrow, at 19:00 UTC I will do a live stream on Twitch (https://twitch.tv/walkerogr) where I will start with the presentation of the new release and playing the game on my X5000.

This will be the start of a new series of streams, which will be about gaming on AmigaOS 4. Join me if you want to see how Heretic 2 plays.

@Maijestro
I agree with you that a Virtio-net driver would be the best solution. As I explained in my post, this is what I did and seems to work on my system. This might not work for everyone because it seems to be influenced by many things, and a lot of software is involved.

It might even stop working for me in the following days, but yesterday I tried playing streaming radio in AmigaAmp from a very specific station, while I was using Odyssey, and that worked fine. Before those changes, even only streaming the radio was breaking the network in less than a minute.

I wanted to share it, in case this is helpful for someone.

For a long time I had issues with network and audio on my emulated Pegasos 2 setup. As I have noticed that this is still mentioned at http://zero.eik.bme.hu/~balaton/qemu/amiga/aos_pegasos2.html as a known problem, I would like to share how I resolved it today.

Please excuse me if someone already mentioned that solution and I missed it. I also read the whole thread at the AmigaOneXE emulation and some stuff are mentioned there as well.

So, what I did:

First of all at qemu command I use the following for the networks and audio devices.


Have in mind that Pegasos has by default an AC97 audio card, which I am not sure if it can be removed. By using the es1370 like above, the emulated AmigaOS 4 recognises 2 audio cards. This one is a SB128. Having both of the cards, I had to go to Devs:AudioModes and remove everything except FILESAVE and SB128 files. After a reboot, I set in the AHI prefs the SB128 mode and then the sound was working fine.

Also, for the network I use the rtl8139 v53.4 which is mentioned many times by many people here that is the best working driver for Pegasos 2.

My qemu installation is v8.2.2 under Linux, as it is available on Manjaro repositories. What I mean by that is that I haven't done any specific compilation of it.

So, on my system, and based on my experience, the AC97 audio device brings conflicts with the network card on my system.

I wanted to share with you a resume of my experience in case it helps anyone in here. Again, I am sorry if someone mentioned all these, and I missed it somehow.

Thanks Niels. Yeah, I have unfortunately miswritten the URL. Thank you so much for providing the right one.

@Maijestro
Quote:

Yesterday I took some time to implement it and it is working quite well. It is possible to drag 'n drop a file or a folder on the LiteXL icon on AmiDock and have that open in a new window. I have that working on AmigaOS 4 and I need to first make it available for MorphOS as well before a new release happens.

I plan to give a beta version to my monthly supporters on https://ko-fi/walkero in the following days, since such things are included in the perks they get from me.

Thank you root for helping here.
I would like to propose a different approach though

1. To change the path or folder you can use CTRL+SHIFT+C, or select from the menu that opens with CTRL+SHIFT+P the "Change Project Folder" and then type the path you want to open. Another way is to drag a drop a folder inside the LiteXL window.

2. I hoped that you Eliyahu would read the manuals. :(

Quote:

I wouldn't do that, because on every update you will need to redo those changes as these files are overwritten. From the documentation:

Quote: