PuppyLinux : Wine

• Categories
• PageIndex
• RecentChanges
• RecentlyCommented
• Login/Register
• Search:

WINE runs win16/32 software on Linux

Wine Software package(s)

Absolutely no warranty given or implied; use entirely at your own risk

Download a .pet software package then single-left-mouse-click on it for automatic installation:
http://www.murga-linux.com/puppy/viewtopic.php?t=53675

How to activate/use WINE so as to start/run programs

Locate the .exe file of the program you wish to run/start, by using the window manager

1. Navigate to: /root
2. View hidden files in that directory by clicking once on the eye icon located in the toolbar of ROX-Filer.
3. Navigate to: /root/.wine/drive_c/Program Files/
4. Find the .exe file in the relevant subdirectory

Start the program by clicking on its .exe file
WINE will then run the program. If it does not then you must associate .exe files with WINE by doing the following:

1. Right click on the .exe file
2. Then select: Set Run Action
3. Confirm that the radio button for: Only for the type 'application/x-ms-dos-executiable' is selected
4. Or type: wine "$@" in the field for Enter a shell command
5. Now click Use Command button

An alternative method (Method B)is explained in the Appendix.

Installing Windows software

Use the file manager to navigate to the directory that contains the program's set-up file setup.exe and click on it. This will only work if WINE has been activated first (see above).

When installing commences accept the defaults for where to install. Most installers will default to C:\Program Files.

Ensure that the size of the pup_save file is large enough to accommodate the Windows programs that you wish to install. If necessary increase the size of the personal storage file by going to: Menu > Utility > Resize

Note: Using WINE does not mean you will have success with any software designed to run under Microsoft Windows (Win16/32 software). Some installed programs may not run, or if they do, may subsequently crash. One does not know if a particular software program designed for Windows will run under Linux+WINE until it is actually attempted. WINE is continually being developed and improved resulting in frequent new releases.

Free technical support is available at the Puppy Linux Discussion Forum

Appendix

[full article for advanced users]

Making WINE available to Puppy Linux

Choose one of the following four methods:
(.sfs files are intended for frugal installations only; .pet files are intended for either full or frugal installations)

1. Automatic installation using a .pet software package
The provision of .pet software packages of WINE which someone else has already kindly created means that this is the method recommended for beginners.
http://www.murga-linux.com/puppy/viewtopic.php?t=53675
http://www.murga-linux.com/puppy/viewtopic.php?p=266552#266552

2. Manual installation using the Slackware binary package for WINE (no compiling necessary)
Create a .pet in 5 easy steps:

• Download latest available WINE binary package for Slackware to directory ~/my-documents, or to any other directory of your choice.
• Navigate to this directory, using the file manager
• With this directory window open and active, press ` key to open a console (terminal) window, or, alternatively, right-click and select Window/Terminal Here
• Type or copy e.g. tgz2pet wine-1.1.29-i486-1kjz.tgz into a terminal window; this command converts the .tgz binary package file into a .pet binary package file; to avoid typing the whole file name, type just the first few letters then the rest can be automatically completed by pressing the tab key, or, copy and then paste with middle-button mouse click
• Click on the created .pet file, and WINE will be installed automatically

3. No installation by using a single .sfs file (for frugal Puppy installations only)
Either create your own or use what someone else has kindly created; place the SFS file in directory /mnt/home; modify the filename suffix so that it corresponds with the version of Puppy Linux in use, e.g. wine-1.1.20_421.sfs, wine-1.1.20_423.sfs, etc.; go to Menu > System > BootManager; click Choose which extra SFS files to load at boot-up; configure accordingly and un-tick the box).

4. Manual installation by compiling the WINE source code (and then optionally creating a .pet software package)
If more control is required over the installation process then consult the next section where the alternative process of using the WINE source code (instead of binary packages) is outlined.

How to activate/use WINE

WINE makes it possible to run computer software, that was specifically written for the Microsoft Windows operating system, with any Unix-like operating system, particularly Linux. Running these Windows-dedicated software can be initiated via two methods.

Method A of running Windows software

Start the application by clicking on the program's .exe file, and WINE will run the program. If this does not happen, you can make it happen by associating .exe files with WINE. Do this by right-clicking on the .exe file; then select Set Run Action...; confirm that only for the type 'application... is selected; for Enter a shell command: type wine "$@"; click Use Command.

To locate your program's .exe file: navigate to /root; show hidden files in that directory by left-clicking once on the eye icon in the toolbar; navigate to /root/.wine/drive_c/Program Files and expect to find the .exe file in the relevant subdirectory.

Method B of running Windows software

Once installed, the program can be run from the command line. When invoking WINE, you may specify the entire path to the executable or a filename only. One of these commands should work [virtually all software written for the Microsoft Windows operating system will by default install to C:\Program Files, which in Linux equates to /root/.wine/drive_c/Program Files; if this was altered then amend the command accordingly):

or

or, using DOS filename syntax

Start the application by clicking on the program's Menu (or desktop) icon (if it exists), and WINE will run the program.

Because one may have forgotten, or because some programs do not always use obvious naming for their directories or their .EXE file, it might be necessary to examine the /root/.wine/drive_c directory to obtain that information.

• Use the file manager to navigate to the directory containing the Windows program you want to run
• Open a console window by pressing the ` key, or, right-click and select Window/Terminal Here]
• Type wine followed by the program's executable file, i.e. wine fantasticprogram.exe or wine fantasticprogram

The command to run your program can be made into a script, semi-automating this process. Open a file manager window and navigate to /root/my-applications/bin. Then right-click and select menu/new/script. Give a name for your script. Open the script and add the appropriate lines:

Since /root/my-applications/bin is in the path, one can now run fantasticprogram from the command line:

This script file can be dragged to the desktop where one can now simply click it to run the script.

Installing Windows Software under Linux

Install software designed for Windows in the same way one would under Microsoft Windows: by running the application's installer. Either use the file manager to navigate to the directory that contains the program's set-up file setup.exe and click on it, or, use the command line to run the set-up file.

For example, supposing that there is a Photoshop CD in the optical drive which is mounted at /mnt/sr0, then the command to install is:

When installing commences accept the defaults for where to install. Most installers will default to C:\Program Files. The application installer may ask permission to create icons on the desktop and in the applications menu. Those icons may not appear, but you can create them later.

Ensure that the size of the pup_save.2fs file is large enough to accommodate the Windows programs that may be installed.

Configuring WINE

After its installation, WINE can be configured. Most of the common configuration changes can be done by issuing the winecfg command. The first time it runs it will create a directory .wine in /root. It will also set up a fake Windows drive inside .wine. A window opens where one can configure lots of options. Initially, do not configure anything. But if a particular Windows program does not run configure WINE to use a different version of Windows. Some programs will not even install unless WINE reports itself as Windows XP, while others will run better as Windows 98. To configure WINE enter into a terminal window:

Using WINE Summary

Run the specified program:

Display help information and exit:

Output version information and exit:

Wine features
Wine User Guide

Compiling the WINE source code

Ensure that the devx_XXX.sfs file is in the same directory as the pup_save.2fs file. Otherwise it is not possible to compile anything. If that file is not present then it will be necessary to acquire it.

Download the latest source file of WINE in compressed tar.bz2 format (known as a tarball).

Navigate to the directory that contains the source tarball. Open a terminal window and extract the WINE source tarball with the command:

{x main operation mode = extract files from an archive; f device selection = use archive file; j compression option = filter the archive through bzip2; v informative output = verbosely list files processed}

This creates a new directory with the extracted and expanded source code files. This directory will only be created if there is at least 350MB of space available. Now change to this directory that contains the extracted files, so, if the source file wine-1.1.44.tar.bz2 was downloaded to /mnt/home, give the command:

WINE contains a script that will automatically build and install WINE. Do not use it as it will not install everything to where Puppy Linux would like it to. Instead, one should build (compile) and install manually. Before compiling one has to set up the configuration:

then to build (compile):

and then to install:

Now wait whilst it processes. Depending on the capability of the C.P.U. it could take more than an hour. If there are no errors reported then WINE has compiled and installed successfully.

Do not delete the directory within which WINE was compiled (the source directory). Because when a new version of WINE is released the old one can be removed with ease: with that directory open and active open a terminal window and give the command:

The new version can then be compiled and installed. Installed version information can be obtained via:

Compile and Install Summary

For WINE source file under Puppy Linux:

References

http://www.t2-project.org/packages/wine.html
http://www.murga-linux.com/puppy/viewtopic.php?t=37783
http://www.murga-linux.com/puppy/viewtopic.php?t=20548
http://www.murga-linux.com/puppy/viewtopic.php?p=266552#266552

Appendix

Dependencies: +alsalib,+audiofile,+bash,+binutils,+bison,+bzip2,+cf,+compositeproto,+coreutils,+cups,+dbus,+diffutils,+e2fsprogs,+esound,+expat,+findutils,+fixesproto,+flex,+fontconfig,+freetype,+gawk,+gcc,+glibc,+grep,+imake,+inputproto,+jack,+kbproto,+lcms,+libdrm,+libexif,+libgcrypt,+libgpg-error,+libgphoto2,+libice,+libjpeg,+libpng,+libpthread-stubs,+libsm,+libtasn1,+libtiff,+libtool,+libusb,+libx11,+libxau,+libxcb,+libxcomposite,+libxcursor,+libxdamage,+libxdmcp,+libxext,+libxfixes,+libxi,+libxinerama,+libxml2,+libxrandr,+libxrender,+libxslt,+libxt,+libxxf86vm,+linux-header,+m4,+make,+mesa,+mktemp,+mpg123,+nas,+ncurses,+net-tools,+openldap,+openssl,+pkgconfig,+prelink,+randrproto,+renderproto,+sane-backends,+sed,+sysfiles,+tar,+valgrind,+xextproto,+xf86vidmodeproto,+xineramaproto,+xproto,+zlib

---

Categories

CategorySoftware

• [Source]
• [History]
• 2010-06-09 00:58:26
• Owner: coolpup

Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by WikkaWiki , online since July 19, 2009.