Puppy Linux Discussion Forum

note;
Also see this post by the developer of Wine-GUI (melroy89)
viewtopic.php?p=120945#p120945
It provides link to deb package of the very latest version.

melroy89 wrote:

Instead of downloading from the links above, I advice you to download the latest deb from: https://gitlab.melroy.org/melroy/winegui/-/releases

I also have a mirror hosted on GitHub btw: https://github.com/winegui/WineGUI

ps. WineGUI is currently using the default wine that is available on your system.

Installing Wine-gui

WineGUI-v2.1.0.deb
https://mega.nz/file/P5llhZwK#XExjFRkGI ... OXu1UsAAbQ

WineGUI-v2.2.0.deb
https://mega.nz/file/vlsTzQoa#LsWVy9nKq ... lFy4jyXTYE

WineGUI-v2.1.0.pet
https://mega.nz/file/P11TXLJS#ReJpyz3IE ... ugmDEkw6k0

Features:

• Graphical user-interface on top of Wine
• Creating a new machine using an easy step-by-step wizard
• Application list per machine (with search feature and refresh button)
• Editing and removing Windows machines in a breeze
• Configure window installing additional software with just a single click (like installing DirectX)

Sofiya wrote: Mon Dec 11, 2023 12:42 am

Installing Wine-gui

WineGUI-v2.1.0.deb
https://mega.nz/file/P5llhZwK#XExjFRkGI ... OXu1UsAAbQ

WineGUI-v2.1.0.pet
https://mega.nz/file/P11TXLJS#ReJpyz3IE ... ugmDEkw6k0

Features:

• Graphical user-interface on top of Wine
• Creating a new machine using an easy step-by-step wizard
• Application list per machine (with search feature and refresh button)
• Editing and removing Windows machines in a breeze
• Configure window installing additional software with just a single click (like installing DirectX)

Thanks for this! I have a lot to learn about wine.

I've tried using wine to access windows driven devices, like audio devices with internal memory. I'm able to install the drivers, wine says they are installed correctly, but I'm never able to actually see and save to the device, even though the utility software installs and runs successfully. This is using @mikewalsh's portable wine 5.1x I believe.

At any rate a better interface will be helpful.

Hi,

Thanks for mentioning WineGUI. I'm the developer of WineGUI.

Instead of downloading from the links above, I advice you to download the latest deb from: https://gitlab.melroy.org/melroy/winegui/-/releases

I also have a mirror hosted on GitHub btw: https://github.com/winegui/WineGUI

ps. WineGUI is currently using the default wine that is available on your system.

Regards,
Melroy van den Berg

@melroy89 to the Kennels!!

Just starting to get into using Wine-GUI regularly and it's full of potential. Runs well in Puppy Linux Bookwormpup64 and about to see if I can get it to run as well on KLV-Airedale and KLV-Spectr (Void Linux based)

Running on a KLV-Airedale-sr13 in a QEMU virtual machine

Running on EasyOS.

Installed Wine with OctoXBPS but the important wine-32bit package is not present. To fix this a repo URL has to be added to the XBPS configuration, so for Wine to work well in KLV-Airedale I added the Void Linux multilib repo to the system using xbps-install to install wine 32 bit support.

xbps-install -S void-repo-multilib && xbps-install -S wine-32bit

Once wine-32bit was installed Wine-GUI found the wine binaries and configured the default settings itself.

Great to hear all this! I will soon roll-out the latest WineGUI version (v2.5.0). TODAY. EDIT: Done. Which should also give the user a better error message, eg. when wine32 isn't installed yet. But the user might try to create a 32-bit bottle.

Under Ubuntu this will looks like this:

@melroy89 :-

Nice concept. Slightly irrelevant for me, since as the major proponent of 'portable' packaging for Puppy these last few years - many of which are AppImage-based (even WINE!) - I have a different way of doing stuff. I have multiple self-contained builds of WINE - 5 at the moment - each making use of a WINE AppImage in its own directory along with its own prefix......and these self-contained builds run from outside the OS completely. You could even run them from a flash drive, or an external HDD or SSD.

All the user does is to run a script from the directory, which links the relevant executables, etc, into the system (so that WINE thinks it's fully-installed). Another unlinks the portable-WINE when the user is finished with it.

Credit for the AppImages must go to various individuals who've hosted their efforts at Github, and made them publicly available.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For myself, I've also built a 'multi-switcher' GUI.....which allows me to quickly swap around between different builds of WINE, depending on what I want to do with it. I admit, I haven't yet figured out a way of presenting launchers for all installed apps; since I tend to use much the same apps all the time, I have a directory full of individual Menu entries, packaged as .pets.....which I simply install/un-install as & when required.

It's nothing special, TBH; just simple file-system trickery/manipulation. It's simply another method for managing/running/using WINE, in such a way as to make it all as easy as possible.

Works nicely, though.

Keep up the good work, my friend! Anything that makes WINE simpler for Joe Average to use has to be a good thing...

Mike.

mikewalsh wrote: Sat Jun 22, 2024 8:26 pm

@melroy89 :-
the major proponent of 'portable' packaging for Puppy these last few years - many of which are AppImage-based (even WINE!) -

I actually also want to build a AppImage from my C++ project. I'm using CMake (together with CPack for Deb, RPM, ..), if somebody knows how to create a proper AppImage please let me know!

@melroy89 :-

See if this helps (though there's a LOT of stuff to work your way through!):-

https://docs.appimage.org/index.html

We have our own simplified scripts for building AppImages (@fredx181 discovered some time ago that AppImages are just 'read-only' squash file system packages).....a concept with which Puppy users are intimately familiar (we've been using them for years). But I wouldn't like to say if Puppy-created AppImages would work on any other distros....

Mike.