Puppy Linux Discussion Forum

sketchman · Joined: 01 Jun 2006 Posts: 219 Location: West Virginia, USA

Has anybody gotten the newer versions of wine to work in Puppy 2.17.1? I know 3.01 will run the Slackware .tgz's fine with tgz2pet, but I'm just plain not interested in moving to 3.01 yet.

When it first was released, I redid my entire system with it, and some weird thing, I don't even remember what now, killed it and I lost everything.

Since then, I learned to keep a test partition.

Is there a way to do it, or should I just wait for the 3.xx series to get more stable? If it can be done, I'll do it and release it for everyone, if I can.

Ian · Posted: Thu 20 Dec 2007, 05:00 Post subject:

Could you please provide some more infomation about what you did when you tried Wine. I know tjhat you said,

"When it first was released, I redid my entire system with it, and some weird thing, I don't even remember what now, killed it and I lost everything. "

but could you clarify this a bit.

Such as "I redid my entire system with it" ? and when you say it " killed it and I lost everything. " I am not sure what you mean.

What method did you use to install Wine in Puppy.

sketchman · Joined: 01 Jun 2006 Posts: 219 Location: West Virginia, USA

I tried the slackware .tgz's from WineHQ.org. I have gotten the latest version, .9.51, working fine in 3.01, using "tgz2pet". That is, download the .9.51 .tgz, then "type tgz2pet (filename)", then click the newly created .pet.

It wasn't wine that killed my 3.01 pup. It was something else. I mean "killed" as in, it wouldn't boot at all.

So I went back to 2.17.1, and tried the same method of installing wine. But, wine wouldn't start. So, now I'm using the latest pup available through PSI. .9.28, I think.

Ian · Posted: Thu 20 Dec 2007, 19:03 Post subject:

Have you been able to work out why Puppy didn't boot, if you are booting from grub check the menu.lst file in /boot/grub and see if it is corrupt.

sketchman · Joined: 01 Jun 2006 Posts: 219 Location: West Virginia, USA

Yes, it will boot, now, because I reinstalled 2.17.1. I have a spare partition, to use for testing the newest Puppy. Then, when 3.xx is stable to my preference I'll switch to it.

Right, now, though, I'm sticking with 2.17.1. So, even if it means compiling wine, I'd like to get the latest version of it working in 2.17.1.

2byte · Joined: 09 Oct 2006 Posts: 356

I have a 15MB wine-0.9.51.sfs that I use in 2.17.1.

You're welcome to it if someone could provide a host for it.

sketchman · Joined: 01 Jun 2006 Posts: 219 Location: West Virginia, USA

I have an HDD install, so I don't think I can use an .sfs, but could you tell me what you did to get it to work? Did you have to compile?

2byte · Joined: 09 Oct 2006 Posts: 356

These are the steps I followed, except I made a sfs instead of copying everything to disk. No compiling was done.

First it requires glibc-2.4.pet. It's been awhile but I think I got it from here
http://www.murga-linux.com/puppy/viewtopic.php?t=17359

It would be a good idea if you backed up your existing partition until you are satisfied that glibc-2.4 didn't break anything you need. You cannot uninstall it without trashing your puppy install. I have installed it in 2.14 and 2.17.1 on 4 machines using pup_save, frugal, and full HD installs without any trouble but some people say it breaks some programs they use.

Download the file for Slackware packages ( wine-0.9.51-i486-1kjz.tgz )
http://sourceforge.net/project/showfiles.php?group_id=6241

Extract it in a working directory. You'll get two directories, install and usr.
I deleted the install directory.
Expand usr and delete the include directory, unless you want all of those C header files in there.

Then copy all of the files, and any sub directories that don't already exist, from your working directory usr on down into their matching directories under /. Make sure you don't overwrite any directories.
Someone can jump in here with the proper cp command to do this easily, I don't know what it is.

When everything is copied run this script, created from the slackware doinst.sh that was in the install directory.

sketchman · Joined: 01 Jun 2006 Posts: 219 Location: West Virginia, USA

Thanks, I'll try that.

sketchman · Joined: 01 Jun 2006 Posts: 219 Location: West Virginia, USA

That works. Thank you.

I remember installing that glibc package a while ago, and it did do something nasty to my puppy. I think it killed it. But, it seems OK now. Don't know what I did different.

Thanks again.

paulski · Posted: Sat 05 Jan 2008, 08:16 Post subject: I got wine 0.9.49 to go in 2.16

I got wine 0.9.49 to go in 2.16 and I did NOT need glibc2.4 rather 2.3.6
It should work okay in 2.17 as far as I can tell

Wine0.9.49 in Puppy 2.16
Here's what I did

1. Install the glibc 2.3.6 (you don't need 2.4 other threads report it stuffs up 2 series puppys badly)
downloaded glibc-solibs-2.3.6-i486-6.tgz
from Slackware (www.slacky.eu)
Opened terminal in the folder where I saved it and then
tgz2pet glibc-solibs-2.3.6-i486-6.tgz
Which made a nice .pet that I installed

2. Install wine
Downloaded wine-0.9.49-i486-1kjz.tgz from a link from another thread, or equally okay from slackware
convert to pet using
tgz2pet wine-0.9.49-i486-1kjz.tgz
Then install the pet (click on it)
then with terminal
winecfg
Builds the /root/.wine folder and you are in action!