How to run Wine in Puppy?

[Tarq]

I want to download Wine

[mikewalsh]

@Tarq :-

O-kay. I assume you want to run some Windows program in Puppy, yes?

This can be a bit of a minefield, but, you're in luck. Many of us here have plenty of experience in running WINE.

Can you let us have three things, please?

• Details of your machine's specifications - CPU, amount of RAM, storage amount (HDD or SSD), graphics.....that kind of thing.

• Exact details of which Puppy you are running?

• Which Windows program(s) you are wanting to run?

This will help us to figure out the best way for you to implement this. Okay? There's several different ways to do this; you can use a WINE .pet, you can use a WINE SFS package. There's portable-WINE, and if running 64-bit the simplest way to implement it is with a WINE AppImage. Let us have some specs, please, and we'll see what's what.....

Over to you.

Mike.

[Tarq]

@Tarq :-

O-kay. I assume you want to run some Windows program in Puppy, yes?

This can be a bit of a minefield, but, you're in luck. Many of us here have plenty of experience in running WINE.

Can you let us have three things, please?

• Details of your machine's specifications - CPU, amount of RAM, storage amount (HDD or SSD), graphics.....that kind of thing.

• Exact details of which Puppy you are running?

• Which Windows program(s) you are wanting to run?

This will help us to figure out the best way for you to implement this. Okay? There's several different ways to do this; you can use a WINE .pet, you can use a WINE SFS package. There's portable-WINE, and if running 64-bit the simplest way to implement it is with a WINE AppImage. Let us have some specs, please, and we'll see what's what.....

Over to you.

Mike.

Code: Select all

root# lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   36 bits physical, 48 bits virtual
CPU(s):                          8
On-line CPU(s) list:             0-7
Thread(s) per core:              2
Core(s) per socket:              4
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           42
Model name:                      Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
Stepping:                        7
CPU MHz:                         798.243
CPU max MHz:                     3100.0000
CPU min MHz:                     800.0000
BogoMIPS:                        4390.42
Virtualization:                  VT-x
L1d cache:                       128 KiB
L1i cache:                       128 KiB
L2 cache:                        1 MiB
L3 cache:                        6 MiB
NUMA node0 CPU(s):               0-7
Vulnerability Itlb multihit:     KVM: Vulnerable
Vulnerability L1tf:              Mitigation; PTE Inversion
Vulnerability Mds:               Vulnerable: Clear CPU buffers attempted, no mic
                                 rocode; SMT vulnerable
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user
                                  pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, STIBP disab
led, RSB fil

I do not know the command line to know the system version

[fernan]

The easiest way I've found to run Wine , that works, is to download wine-portable-3.3_v2.1.tar.gz from the internet (I don't have the right link to post it here, but searching for the file name you'll find it). Extract and copy the folder to /initrd/mnt/dev_save/ and use it (32 bit though)

viewtopic.php?t=103

[mikeslr]

Wine-portable can be downloaded via a link from here, viewtopic.php?p=279#p279. Be sure to read that post and the following one, especially if you are running a 64-bit Puppy.

Despite there being newer versions of Wine, I still run this one even under Fossapup64. It just works. Most of the Windows programs I use are portables that have been around a long time, even if the versions I run are recent updates.

[Geek3579]

I agree with mike.

I use the 3.3 version and it just works. And I like the menu items too!

• Just extract the WINE files outside the save folder
  load the 32 compatability sfs for the particular puppy ( if its 64 bit)
  run ldconfig in the terminal
  run the register script to start wine
  run wine.sh winecfg in the terminal to load Gecko and Mono .... and away we go!

[jakobus]

Can someone instruct me exactly how to get Wine-portable installed and running,
etc. I haven't done this kind of thing for a coon's age. (Weak on the console, ha ha).
I have a wine-portable-3.3_v2.1.tar.gaz in my download folder. What's next?

Jakobus,
Jakob Cornelis
xenial 75,
Box: HP Compaq
Model: DC 7100 SFF
CPU: P4 3.0GHz
HDD: 89 GB - SATA
RAM: 1024MB
OS: xenial 75
Optical: DVD-Rom

[mikewalsh]

@jakobus :-

I would answer this, but TBH, @mikeslr has far more experience with portable-WINE (Shinobar's original set-up); me, I prefer version2013's builds, though I run them from an external partition, fully sym-linked into Puppy where it looks to find all the components.

There IS method in the madness, trust me. Amongst other things I run TextAloud! - a text-to-speech app - and many of the AT&T 'Natural Voices' I use run out at around 6-800 MB each. It doesn't take long for a few of those to start occupying several GB......and that's just background components that HAVE to be installed for the 'front-end' app itself to function!

I have constructed a couple of WINE-portable builds making use of WINE AppImages, though these don't have the method Shinobar developed for calling the installed apps directly from their .exes. You have to create your own Menu entries, though this is not hard to do.

Mike should be around later on, so if he spots this hopefully he'll chime-in & explain the 'nitty-gritty' of using Shinobar's portable-WINE.....

Mike.

[mikeslr]

And even though I built it and still have wine-portable-3.3_v2.1.tar.gz running under a couple of Puppys I set up a while back, I use MikeWalsh's Wine-portables --from the link at the top of this post, https://www.forum.puppylinux.com/viewto ... 191#p68191-- with new Puppys.

You didn't tell us whether the Xenialpup you are using is 64-or-32bit. If a 64-bit operating system I strongly recommend using MikeWalsh's WINE 5.11. It's just easier to setup. You won't need to SFS-load a 32-bit compatibility SFS, and configure the 32-bit system before making use of the Wine implementation. Even if you running a 32-bit Puppy, MikeWalsh's Wine 4.0.4 will just be easier to setup.

The first steps with any of the above implementations is to download the tar.gz or tar.xz, Right-Click it and select either UExtract or pExtract or some other extraction application from the pop-up menu. Extraction will create a folder you can move anywhere and should move to its 'final' destination. It should NOT be within Puppy's SaveFile/Folder. Best placed on the partition/drive your Puppy boots from. You can Right-Click the folder and rename it. I usually name it just 'wine-portable': less likely to generate scribner's errors if I have to write or edit something referring to it.

I'm assuming your xenialpup is 32. Please correct if that's not the case.

If it is xenialpup32, after relocating the wine-portable folder you're almost finished. Make sure you have an internet connection established.

With wine-portable-3.3 Right-Click the folder. Under some Puppys you'll see an option to Register wine portable. If not, select the option to 'Look Inside'. Inside you'll see the Register script. Right-Click it. Wine-portable will be registered and applications will appear on your Start Menu. In the Utilities Section Click Wine Config.
Keep in mind that if you have to start a program using a command it will be wine.sh.

In the folder for Wine-portable-4.0.4 Right-Click the script named WINE-Link. When it's finished setting up, Right-Click the script named menuadd. Again I think you'll find the Wine Config application in the Utilities Section of the Start Menu. Keep in mind that if you have to start a 32-bit program using a command I think it will be wine32. @ MikeWalsh, is that right?

[jakobus]

Hello, hello: I now got a thing on my desktop that looks suspiciously as a functioning Wine. How exactly it got there I could not testify to; it probably is a mixture of sniffing out what one would think of as something that might work, either confirmed or denied by notices appearing along the way on the screen, and voila I now can see a few things that ring a wine bell, such as ":c" and "Program Files". What impresses me is that on this path one is not ending up feeling abandoned, as is so often the case with half-wits like me; no, one is told, don't do that, do this. This is really clever,....what...code? However, I'm not there yet. I am still trying to sort out how to use this set-up, which looks slightly different from what I am used to from, well, OK, the old days. So if youse guys have something better to do than messing with a ..... well, I got something right, didn't I? I'll move on to figuring out how exactly to work this thing, and prove it by installing my favourite word processor, atlantis, which to my knowledge is still only available in Windose. And, by the way, sorry for omitting that I run a 32-bit box. Thanks for your inspiration,

jakobus

[jakobus]

Hello: I have given up on this project for the time being. I found a way of running the applications I need directly, on an old mac. For now it meets my current requirements. Thank you respondents for your help.

Greetings, Jakobus.

[Klaus1]

Hi everybody,
thanks all for the WINE-explanations. I finally was able to install WINE32 (wine-portable-3.3_v2.1) and also the first programs. I have only one problem in the moment: in the "Wine Console" is my german keyboard layout active. It works fine.
Only the character V on the keyboard appears in the Wine Console as Ö. To be able to write V, I have to change the keayboard layout in Puppy (FOSSAPup64-9.5) from German to English.
It seems to me to be a problem with the character set in Wine.

Any Idea?
Regards,
Klaus

PS: once more. How does the command line in the terminal look like to start a windows program (which is on C:\) via WIN32 START? I have seen the command in a post, unfortunately not saved.
PS 07.12.2023 / 10:04 : not needed anymore, I wrote a BASh-file to start it. It is running well.