EDIT: as of 2016 Nov 06, my 'green_dome' account was re-enabled. Thank you 'Makoto'.
With that said, I think I will be using my 'version2013' account as my main account and forum presence.
My webpage for Puppy Linux is currently at http://version2013.yolasite.com/page1.
My webpage is where I try to maintain current download links to various files even if links on the forum are no longer valid.
The important content of my website is backed up at:
https://gitlab.com/version2013/puppylin ... ter/backup
in the format of "version2013_date.zip"
A link to the current location of my website is:
- at the bottom of my posts, next to "Profile" "PM"
- at https://archive.org/details/@version2013
This post contains links to the Internet Archive Wayback Machine.
On a given archived page, the top of the page is a navigation header where one can navigate to all captures/snapshots that are available for the given page.
----------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------
Home: http://www.winehq.org/
My previous Wine thread using my previous username. [>]
For previous Wine .pets and lots of information, visit technosaurus's thread. [>]
Listed in puppylinux wiki. - http://wikka.puppylinux.com/wine
My other forum thread. - http://puppylinux.info/topic/wine
I did nothing clever in compiling Wine, I just followed the instructions/examples of others. Thanks go to them for providing the information, files, and work.
This post will point to new wine versions as I compile them.
For a basic wine setup, I recommend the latest stable release.
If the windows software you are trying to use is not functioning as it should (using stable release), then I recommend the latest development release.
more details [>] [>]
I am interested to read about which puppy versions these packages succeed and fail to run in.
Please post your experiences with wine.
----------------------------------------------------------------------------------------------------------
* note - current download links are listed on my webpage, http://version2013.yolasite.com/page1.
There are invalid download links in some forum posts, made with my older username 'green_dome'. Those posts are now just useful for the configure/compile information.
stable (32-bit):
1.2 | 1.2.1 | 1.2.2 | 1.2.3
1.4 | 1.4.1
1.6 | 1.6.1 | 1.6.2
1.8 | 1.8.1 | 1.8.2 | 1.8.3 | 1.8.4 | 1.8.5
2.0 | 2.0.1 | 2.0.2 | 2.0.3 | 2.0.4
3.0 | 3.0.1 | 3.0.2 | 3.0.3 | 3.0.4
4.0 | 4.0.3
5.0 | 5.0.1
development (32-bit):
1.1.41 | 1.1.42 | 1.1.43 | 1.1.44
1.2-rc1 | 1.2-rc2 | 1.2-rc3 | 1.2-rc4 | 1.2-rc5 | 1.2-rc6 | 1.2-rc7
1.3.0 | 1.3.1 | 1.3.2 | 1.3.3 | 1.3.4 | 1.3.5 | 1.3.6 | 1.3.7 | 1.3.8 | 1.3.9
1.3.10 | 1.3.13 | 1.3.14 | 1.3.16 | 1.3.17 | 1.3.19
1.3.20 | 1.3.21 | 1.3.22 | 1.3.23 | 1.3.24 | 1.3.25 | 1.3.26 | 1.3.27 | 1.3.28 | 1.3.29
1.3.30 | 1.3.31 | 1.3.32 | 1.3.33 | 1.3.34 | 1.3.35 | 1.3.36 | 1.3.37
1.4-rc4 | 1.4-rc5
1.5.0 | 1.5.1 | 1.5.2 | 1.5.3 | 1.5.4 | 1.5.5 | 1.5.6 | 1.5.7 | 1.5.8 | 1.5.9
1.5.10 | 1.5.11 | 1.5.12 | 1.5.13 | 1.5.14 | 1.5.15 | 1.5.16 | 1.5.17 | 1.5.18 | 1.5.19
1.5.20 | 1.5.21 | 1.5.22 | 1.5.23 | 1.5.24 | 1.5.25 | 1.5.26 | 1.5.27 | 1.5.28 | 1.5.29
1.5.30 | 1.5.31
1.6-rc1 | 1.6-rc2 | 1.6-rc3 | 1.6-rc4 | 1.6-rc5
1.7.0 | 1.7.1 | 1.7.2 | 1.7.3 | 1.7.4 | 1.7.5 | 1.7.6 | 1.7.7 | 1.7.8 | 1.7.9
1.7.10 | 1.7.11 | 1.7.12 | 1.7.13 | 1.7.14 | 1.7.15 | 1.7.16 | 1.7.17 | 1.7.18 | 1.7.19
1.7.20 | 1.7.21 | 1.7.22 | 1.7.23 | 1.7.24 | 1.7.25 | 1.7.26 | 1.7.27 | 1.7.28 | 1.7.29
1.7.30 | 1.7.31 | 1.7.32 | 1.7.33 | 1.7.34 | 1.7.35 | 1.7.36 | 1.7.37 | 1.7.38 | 1.7.39
1.7.40 | 1.7.41 | 1.7.42 | 1.7.43 | 1.7.44 | 1.7.45 | 1.7.46 | 1.7.47 | 1.7.48 | 1.7.49
1.7.50 | 1.7.51 | 1.7.52 | 1.7.53 | 1.7.54 | 1.7.55
1.8-rc1 | 1.8-rc2 | 1.8-rc3 | 1.8-rc4
1.9.0 | 1.9.1 | 1.9.2 | 1.9.3 | 1.9.4 | 1.9.5 | 1.9.6 | 1.9.7 | 1.9.8 | 1.9.9
1.9.10 | 1.9.11 | 1.9.12 | 1.9.14 | 1.9.15 | 1.9.16 | 1.9.17 | 1.9.18 | 1.9.19
1.9.20 | 1.9.21 | 1.9.22 | 1.9.24
2.0-rc1 | 2.0-rc2 | 2.0-rc5 | 2.0-rc6
2.1 | 2.2 | 2.3 | 2.4 | 2.5 | 2.6 | 2.7 | 2.8 | 2.9
2.10 | 2.11 | 2.12 | 2.13 | 2.14 | 2.15 | 2.16 | 2.17 | 2.18 | 2.19
2.20 | 2.21 | 2.22
3.0-rc1 | 3.0-rc2 | 3.0-rc3 | 3.0-rc4 | 3.0-rc5 | 3.0-rc6
3.1 | 3.2 | 3.3 | 3.4 | 3.5 | 3.6 | 3.7 | 3.8 | 3.9
3.10 | 3.11 | 3.12 | 3.13 | 3.14 | 3.15 | 3.16 | 3.17 | 3.18 | 3.19
3.20 | 3.21
4.1 | 4.2 | 4.3 | 4.4 | 4.5 | 4.6 | 4.7 | 4.8 | 4.9
4.10 | 4.11 | 4.12.1 | 4.13 | 4.14 | 4.15 | 4.16 | 4.17 | 4.18
4.20 | 4.21
5.0-rc1 | 5.0-rc2 | 5.0-rc3 | 5.0-rc4 | 5.0-rc5 | 5.0-rc6
5.1 | 5.2 | 5.3 | 5.4 | 5.5 | 5.6 | 5.7 | 5.8 | 5.9
5.11 |
stable (64-bit):
2.0.3
3.0 | 3.0.1 | 3.0.2 | 3.0.3 | 3.0.4
4.0 | 4.0.3
5.0 | 5.0.1
development (64-bit):
2.14 | 2.18 | 2.19
3.1 | 3.2 | 3.3 | 3.4 | 3.5 | 3.6 | 3.7 | 3.8 | 3.9
3.10 | 3.11 | 3.12 | 3.13 | 3.14 | 3.15 | 3.16 | 3.17 | 3.18 | 3.19
3.20 | 3.21
4.1 | 4.2 | 4.3 | 4.4 | 4.5 | 4.6 | 4.7 | 4.8 | 4.9
4.10 | 4.11 | 4.12.1 | 4.13 | 4.14 | 4.15 | 4.16 | 4.17 | 4.18
4.20 | 4.21
5.0-rc1 | 5.0-rc2 | 5.0-rc3 | 5.0-rc4 | 5.0-rc5 | 5.0-rc6
5.1 | 5.2 | 5.3 | 5.4 | 5.5 | 5.6 | 5.7 | 5.8 | 5.9
----------------------------------------------------------------------------------------------------------
I usually just create .pet files.
There are a few tools that I find useful in creating sfs files.
- pets2sfs | post | download | post
- createsfs | thread | download
- PaDS 1.0.4 ---> convert and merge (P)ET (a)nd (D)EB into a single (S)FS | post
- right-click options | page | post | * has many features, one of which is converting to sfs
- dir2sfs | a script that many pupplets already have.
- PETS2SFSGUI | thread
Related scripts:
sfs2pet | webpage | thread | download
sfs2dir | webpage | download
----------------------------------------------------------------------------------------------------------
- general linux info -
command prompt
http://www.linfo.org/command_line.html
http://www.linfo.org/console.html
http://www.linfo.org/terminal_window.html
-----------------------------------------------
Note: BBCode does not like asterisks within url tags.
about Gecko
- http://wiki.winehq.org/Gecko
--- archived -> https://web.archive.org/web/*/http://wi ... .org/Gecko
- https://en.wikipedia.org/wiki/Gecko_%28software%29
about Mono
- http://wiki.winehq.org/Mono
--- archived -> https://web.archive.org/web/*/http://wi ... q.org/Mono
- https://en.wikipedia.org/wiki/Mono_%28software%29
about Prelink
--- archived -> https://web.archive.org/web/*/http://wi ... rg/Prelink
- https://en.wikipedia.org/wiki/Prelink
- https://www.winehq.org/pipermail/wine-d ... 12285.html
about patching
- http://wiki.winehq.org/Patching
--- older version archived -> https://web.archive.org/web/20160112095 ... g/Patching
about Gcc
- https://wiki.winehq.org/Gcc
--- archived -> https://web.archive.org/web/*/https://w ... hq.org/Gcc
about DInput
- https://wiki.winehq.org/DInput
--- archived -> http://web.archive.org/web/*/https://wi ... org/DInput
about XI2
- http://www.x.org/wiki/XI2 | [archived]
----------------------------------------------------------
I use a console, or terminal window, to install packages from winetricks:
# winetricks -h
winetricks references:
http://wiki.winehq.org/winetricks | http://winetricks.org/download/releases/ | http://www.winehq.org/pipermail/wine-de ... 62347.html
For a GUI with winetricks, use 'zenity'.
http://wikka.puppylinux.com/zenity
http://murga-linux.com/puppy/viewtopic. ... 170#421170
After installing 'zenity-2.20.1.pet', I used the following commands to make it work with winetricks.
# mkdir /usr/local/share/zenity/
# ln -s /usr/share/zenity/zenity.glade /usr/local/share/zenity/zenity.glade
See this post for updating winetricks.
----------------------------------------------------------
- menu entries
Starting with 1.5.18, I moved the menu entries into a separate dotpet.
Some users prefer wine with menu entries.
Some users prefer wine without menu entries.
[reference post]
[reference post]
The dotpet with menu entries - 'wine_extras-v2.1.pet'
Links to download 'wine_extras-v2.1.pet'
In reference to menu entries, many of them launch executable wrappers (I think) to sub-programs in Wine.
http://wiki.winehq.org/List_of_Commands [archived] [old wiki page archived]
For those that want menu entries, but ...'just one entry under Utility which leads to a menu of all the wine programs.' [>]
Another menu entry utility 'WineEnv' [>] [>]
menu entry utility 'WinUtil' [>] [>]
menu entry utility 'xdg-wine 1.0' [>]
----------------------------------------------------------------------------------------------------------
Wine usage tips:
- cd to the program folder, then launch program from there. As "mikeb" has mentioned, I have also found this to be accurate with several programs that would not launch previously.
How to run Windows programs from the command line
explanation: https://forum.winehq.org/viewtopic.php?t=14623
Possible related bug report
- To minimize space used in my savefile, I use separate wineprefixes for each windows application, placed outside of the savefile, somewhere under '/mnt/home/'.
If all windows applications were installed to the default wineprefix (~/.wine/), things could possibly become time consuming when a problem arises.
When one application continues to fail, or messes up the wine config files, I would need to reinstall all the windows applications that are in the default wineprefix.
Having separate wineprefixes is useful when one application continues to be problematic. I can reinstall just that application.
When troubleshooting and bug reporting, having separate wineprefixes for each application is recommended.
references:
7.1 Can I store the virtual Windows installation somewhere other than ~/.wine? [archived]
https://forum.winehq.org/viewtopic.php? ... 96#p106717
For each application, I use:
# WINEPREFIX=/path/to/wineprefix winecfg
(let wine create the last directory; in this example it would be '/wineprefix')
# WINEPREFIX=/path/to/wineprefix wine application_installer.exe
(I put the following in a script, for when I run the application)
# cd "/path/to/wineprefix/drive_c/Program Files/application/"
# WINEPREFIX=/path/to/wineprefix wine application_launcher.exe
other ways to launch wine:
# wine start /Unix "/path/to/application.exe"
# exec wine start /Unix "/path/to/application.exe"
references:
post
http://wiki.winehq.org/start
6.4. How should I start Windows programs from the command line? [archived]
- Also to minimize space used in my pupsave file, I symlink a few things.
~/.cache/wine
This is used to store wine-gecko* and wine-mono* files that wine looks for when creating wineprefixes.
~/.cache/winetricks
This is used to store the files that winetricks downloads.
I move those directories (and their contents) to somewhere in "/mnt/home/". I then create symlinks back to where they originally were.
references:
http://wikka.puppylinux.com/symlink
http://www.linfo.org/hard_link.html
----------------------------------------------------------------------------------------------------------
I have been compiling in a few puppy distros.
----------------
puppy 431
----------------
mirrors | /distro/4.3__1/puppies-431.1-main-Xserver.iso
mirrors | /distro/4.3__1/devx_430.sfs
kernel release 2.6.30.5
Code: Select all
uname --kernel-releaseCode: Select all
gcc --versionCode: Select all
ldd --versionCode: Select all
/lib/libc.so.6Code: Select all
getconf GNU_LIBC_VERSION- before 2.6.1, will possibly fail
- of 2.6.1 and above, will possibly succeed
------------
racy 5.5
------------
mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs
kernel release 3.0.66
Code: Select all
uname --kernel-releaseCode: Select all
gcc --versionCode: Select all
ldd --versionCode: Select all
/lib/libc.so.6Code: Select all
getconf GNU_LIBC_VERSION- before 2.10.1, will possibly fail
- of 2.10.1 and above, will possibly succeed
----------------------------
tahrpup 6.0.5 PAE
----------------------------
mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs
kernel release 3.14.56
Code: Select all
uname --kernel-releaseCode: Select all
gcc --versionCode: Select all
ldd --versionCode: Select all
/lib/libc.so.6Code: Select all
getconf GNU_LIBC_VERSION- before 2.19, will possibly fail
- of 2.19 and above, will possibly succeed
----------------------------
tahrpup64 6.0.5
----------------------------
kernel release 3.14.54
Code: Select all
uname --kernel-releaseCode: Select all
gcc --versionCode: Select all
ldd --versionCode: Select all
/lib/libc.so.6Code: Select all
getconf GNU_LIBC_VERSION- before 2.19, will possibly fail
- of 2.19 and above, will possibly succeed
----------------------------------------------------------------------------------------------------------
. V. 1.7.1 runs fine for me, so thanks....