Wine 1.1.30 + winetricks +color setter +goodies ...pet & sfs

[Patriot]

Hmmm .....

........
Anyway I'm supposed to be working

Well, we should let the chi flows ..... and let the yin and yang fills this thread with harmony once again ..... Come on, I'll buy you a cuppa coffee (since you're supposed to be working ...)

Leave wine for later ....


Rgds

[Keanen]

Will someone please just tell me what the extension for a binary executable is in Linux? In Windows it's exe. Is there a Linux exe? I'm not talking about Wine. What is the extension?

[Patriot]

Hmmm .....

Will someone please just tell me what the extension for a binary executable is in Linux? In Windows it's exe. Is there a Linux exe? I'm not talking about Wine. What is the extension?

FYI, there is no such thing as a linux .exe extension ... (exe = executables) ... on linux, executables are indicated by the file execute permission.

I suggest that you kindly post your future queries in a new specific thread and help keep this thread clean for wine ...


Rgds

[Keanen]

No! All files should have file execute permissions! How do I configure Puppy Linux to execute everything unless otherwise specified?

[jason.b.c]

hey everyone, let's just not answer him anymore...


Maybe he'll get the hint..

[Keanen]

Hey Jason, guess what? It's the same question I've been asking since I started asking questions here, so why doesn't somebody answer it? I call conspiracy!

[jason.b.c]

<ignoring now>

[abushcrafter]

Sorry Keanen but you need to read a linux manual or two. That will help a lot for you and me (I have a LOT to read still )

[abushcrafter]

Can any one face compiling (if there not already) the latest stable version of wine Please. :beg:

[green_dome]

My novice attempt at compiling wine:

wine-1.1.34-i486.pet (release 1)
wine_DEV-1.1.34-i486.pet - development package (release 1)
wine_DOC-1.1.34-i486.pet - documentation package (release 1)

I installed these packages before compiling:

jack-audio-connection-kit-0.116.1-i486.pet (source)
jack-audio-connection-kit_DEV-0.116.1-i486.pet (source)
xorg_xorg_full_dri-7.3.pet (source)
xorg_xorg_full_dri_DEV-7.3.pet (source)

During the wineprefix creation it will attempt to download Gecko. Either let it download automatically, or do it manually (source):

Code: Select all

wget http://downloads.sourceforge.net/wine/wine_gecko-1.0.0-x86.cab

Code: Select all

mkdir -p /usr/share/wine/gecko

Code: Select all

mv wine_gecko-1.0.0-x86.cab /usr/share/wine/gecko/

my graphics card is a Nvidia GeForce 8400GS, so I install the 'NVIDIA-190.42-k2.6.30.5-1.pet' from this post.

[T_B]

Hi green_dome,
Thanks for compiling 1.34. Works fine.

Are the audo + xorg packages mandatory for installation? (I installed them to avoid dependency issues)

[mikeb]

Are the audo + xorg packages mandatory for installation? (I installed them to avoid dependency issues)

Only if your program wants to use...opengl and directx 3d games for example.....and jack is selected in the winecfg menu if desired. If you want to save space the xorg dri package can be trimmed down to only the drivers needed for your card.

They are 'soft' dependancies so wine will run without.

mike

[gulk]

Talking about space, once you get things installed in wine, the .wine and .winetrickscache can become quite huge.
Since I have a frugal install my .2fs is limited in size and I would like to have the wine package installed outside my pupsave. I tried linking those folders from another partition but I lost the c_drive in the process (basically broke my wine install).

Any idea on how to symlink the wine folders to other partitions?

[mikeb]

Any idea on how to symlink the wine fol ... artitions?

It didn't work because you symlinked to a FAT or ntfs partition. There's only a couple of links but they are needed.

So either you need some space on an ext2/3 partition or you can make an image file and use that. It also solves the problem of wine gecko not working.

By the way you cannot make a link to an empty folder then let wine fill it up...it thinks its broken that way. let wine make the .wine folder then move it entirely as you have done. Its also handy as everything is there after a remaster or for any other puppy running the same wine version.(note the link to empty folder may catch you out if you do hence the warning)

What goes in .winetrickscache by the way..I don't have that?

mike

[gulk]

It didn't work because you symlinked to a FAT or ntfs partition.

You're perfectly correct; I was definitely trying to link to a fat partition.
I'll create an ext3 one and keep you posted.

As far as the .winetrickscache is concerned, it seems it holds the temporary data downloaded when I use the Wine Tricks app I found in the Utility menu.


<EDIT>
MikeB, I managed to do exactly what you suggested: create an ext3 partition and symlink from it.
This will let me keep my pupsave files leaner in the future!!! Thanks a lot for your help and Best Wishes for 2010!

[mikeb]

Thanks a lot for your help and Best Wishes for 2010!
No problem and the same to you .

So if you do happen to remaster make sure the symlink /root/.wine is removed first to avoid hair pulling later...just pop it in after the first boot.

mike

ps just a though...If you happen to have dedicated a whole partition to this your link could go to /mnt/sd(x)...just a thought.

pps..there are ext2/3 drivers for windows...might come in handy

[technosaurus]

I just compiled wine 1.1.35, but I did not yet add support for some of the features not included in Puppy (gsm, openal, mpg123, gnutls, capi)

http://puppy-development.googlecode.com ... 5-i486.pxt

I may add mpg123 later, but I want to try and patch the build system to use shared instead of static libwpp and libwine_port because it could significantly reduce the size (400 files in /usr/lib/wine statically linking 100+kb is a bit significant and make the smallest files over 70kb)... the Git developers do the same thing. This is also probably a contributing factor to why xz gets such better compression.

[green_dome]

I installed wine-1.1.35-i486.pxt. When attempting to run the game, FlatOut, it gives me the error message about a debugger detected. Since FlatOut refuses to run, I will share my novice attempt at compiling wine 1.1.35.

wine-1.1.35-i486.pet (release 1)
wine_DEV-1.1.35-i486.pet (release1) (development package)
wine_DOC-1.1.35-i486.pet (release 1) (documentation package)

I installed these packages before compiling:
jack-audio-connection-kit-0.116.1-i486.pet
jack-audio-connection-kit_DEV-0.116.1-i486.pet
xorg_xorg_full_dri-7.3.pet
xorg_xorg_full_dri_DEV-7.3.pet

For help with Gecko, look here

When trying to use winetricks, the GUI appears to be a long horizontal menu that goes off the screen to the right. Since I have difficulty accessing the rest of the menu, I use the console to install packages from winetricks. For help with this I use the code:

Code: Select all

winetricks -h

[source]

my graphics card is a Nvidia GeForce 8400GS, so I install the 'NVIDIA-190.42-k2.6.30.5-1.pet' from this post

[abushcrafter]

Code: Select all

winetricks -h

thanks for that. btw you can use the alt key pressed and click and drag it to get the rest of it

[Frank Cox]

This is probably a dumb question but will wine work on a ntfs partition?
I am running Puppy 4.31 on a ntfs frugal setup and wine installed and it let me install a program but when I try to open it nothing happens.
When I try again it says it is already running and would I like to open another ?
That does nothing either.

Would someone please answer my question? I posted it more than a week ago,thanks!