You're trying to run an emulator (WinUAE) in an emulator (Wine/PlayOnLinux) and trying to get it all going in an environment that is unsuitable for building/debugging. The solution is right there - set up AmiKit XE in a different environment then move it over and run it under FS-UAE, where you won't have to struggle with getting Wine running in a hostile environment.

I eventually found my way to the Wine Configuration inside PlayonLinux, I presume I'm actually changing the settings for the separate wine install for WinUAE/AmiKit. The «Test Sound» button produces a sound. So it's looking like this is a WinUAE or AmiKit problem, not a Wine or Ubuntu problem.

I do not know how custom AmiKit's version of WinUAE is, nor do I have any clue of the differences (if any) between WinUAE and FS-UAE. I foresee many hours if not weeks of trouble with that potential solution. Additionally, I have no idea if any forums or authors exist where I could ask any questions I might have. This may be a hostile environment, but AT LEAST IT IS AN ENVIRONMENT.

Now that I have some clue where to begin, I'm finding solutions to do with using alsa instead of pulseaudio, but also other things to do with SDL. Does anyone here know if AmiKit/WinUAE uses SDL?

I've done some googling and tried some things, but no one seems to have this particular problem. There's plenty of people having issues with bad audio on WinUAE/Wine, but no one having trouble with no audio, with settings that do not let you Enable audio. In case Playonlinux was setting SDL_AUDIODRIVER incorrectly, I overrode that in the registry. I tried installing alsa, but Wine doesn't recognize it. My only choice seems to be pulseaudio. I've tried re-installing AmiKit. Perhaps I should try re-installing wine as well?

Why would anyone purchase anything that took him weeks (!) to get it to work is beyond my understanding. If I were you...

Anyaway, if the X version worked for you in the end, you can try to copy the AmiKit.hdf file from the XE package to your working X environment. If it still doesn't work for you, I will refund you.

I found someone who tells me they have WinUAE 4.9.1 fully working on Linux Lint, but under Wine 4.0. The Amikit .msi installs wine 6.10. Before I figured out that I needed a more recent version of PlayOnLinux, I briefly tried running AmiKit under Wine 3.20 (the most recent version that old version of PlayonLinux knew about). It did not work well. I'm tempted to try AmiKit under Wine 4.0 now, but perhaps someone here can tell me why that's a really bad idea. Vanilla WinUAE runs fine on wine 4.0 apparently. But will AmiKit? Can anyone tell me if there is a particular reason AmiKit installs Wine 6.10? Is there specific functionality is uses that is not supported by older versions of Wine? Or is it simply the most recent stable version or something?

The weeks I spent trying to get it to work were not spent with AmiKit. They were spent trying to install Windows. Once I had Windows installed, AmiKit installed quickly and worked fine. But Windows did not. It took a very long time to boot, wanted to send all kinds of information about me to Microsoft, kept showing me ads, locked up for minutes at a time. It was a horrible experience. But none of that was AmiKit's fault. Once I had AmiKit working on Windows, I figured I would try the same process on Linux, which doesn't do any of those things. However, my linux install was on a jump drive that did not have enough free space to install playonlinux and wine. I then spent another week cloning my linux install, removing stuff from it so I thought I'd have room, not actually having enough room, ending up with a borked install and having to start over with a new clone install. Finally I gave up on that and bought a larger drive and installed linux from scratch. Having done that, it took about 6 hours to install playonlinux, Wine, and Amikit combined. And it worked. Having put that much time into getting something to work, why wouldn't I want the latest, best version of that thing?

I have long ago removed the old version of AmiKit. I wanted to be sure I would have enough room for the new one. it would take me another 6 hours to re-install it at this point, so I think I will keep trying to get the new version working for the moment, as that is what I have quick and easy access to.

You may assume that AmiKit could not run well if it takes that long to install, but aside from the sound issue it runs fine. Installation is slow because the drive I am using is slow. Because AmiKit works with files from the Amiga era, and Amiga era programs, the amount of disk access it does is miniscule in comparison with installing large packages on a modern operating system like Wine on Ubuntu. It runs substantially better than the operating system it is running under. I'd much rather use it than Ubuntu OR Windows any day. That's why I like it and want to get it working. But because the machine I have to run it on is an x64, I have to run horrible slow lazy unoptimized operating systems that only run well on SSDs in-between. Apparently.

The guy using wine 4.0 advised me to uninstall everything and start over without PlayOnLinux. He gave me a command line to install WinUAE under wine:
wine msiexec.exe /I InstallWinUAE4910.msi

Before taking on such a task that would likely involve many hours of waiting, I decided to instead use msiexec.exe to try to install the AmiKit .msi instead. I now have working sound. I had mistakenly thought in the past that I needed to upgrade Wine, rather than PlayOnLinux, so this is currently running on Wine 7.0.

I do not know what (if any) other features will not work using this installation. But at least I have sound.

--Gabe

I have figured out the ROM error messages when starting apps/games. It appears they use something called WHDLoad to run using different Amiga ROMs which they are expecting to find in
devs:kickstarts/
So far I've had to copy them in one by one by hand, and the names of the ROM files I have are not the names they are expecting so I have to guess which one they are looking for. I tried ROMFIND.EXE but it seems to only look for one main file to install as kick.rom. Is there any way to have AmiKit look through my Amiga ROM files, recognize them and install them with the proper name in the proper directory?

I was able to do a stream last night where I played some Amiga games on AmiKit. here's the video:
https://www.youtube.com/watch?v=6RirvjXUMzI