<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  
  
  <channel>
    <title>chrisjrob: wine</title>
    <link>https://chrisjrob.com</link>
    <atom:link href="https://chrisjrob.com/tag/wine/feed/index.xml" rel="self" type="application/rss+xml" />
    <description>GNU Linux, Perl and FLOSS</description>
    <language>en-gb</language>
    <pubDate>Fri, 13 Feb 2026 17:22:31 +0000</pubDate>
    <lastBuildDate>Fri, 13 Feb 2026 17:22:31 +0000</lastBuildDate>
    
    <item>
      <title>Wine 1.4 On Debian Wheezy</title>
      <link>https://chrisjrob.com/2012/03/08/wine-1-4-on-debian-wheezy/</link>
      <pubDate>Thu, 08 Mar 2012 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2012/03/08/wine-1-4-on-debian-wheezy</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/winehq_logo_glass.png" align="right" alt="Featured Image">
         
         <p>I was delighted to read this morning that <a href="http://www.winehq.org/news/2012030701" title="Wine 1.4 Released">Wine 1.4 stable had been released</a>, a
quick <code class="language-plaintext highlighter-rouge">dpkg -l wine</code> revealed that my Debian Wheezy install was running version 1.0.1,
several significant versions old.  There may be good stability reasons
for that decision, but I can afford to be a little more adventurous on
my desktop PC.</p>

<!--more-->

<p>So the question was how to build, well 
<a href="http://verahill.blogspot.com/2012/03/wine-14-out-now-very-brief-build.html" title="Wine 1.4 out now -- very brief build instructions">some brief and helpful instructions are already available</a>.</p>

<p>The only ways I deviated from these instructions was to use the standard
Wine option for the build:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ cd tmp/ $ ./tools/wineinstall
</code></pre></div></div>

<p>Taking the option for “no” to build without installation, and once
complete I installed with:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo checkinstall
</code></pre></div></div>

<p>Checkinstall is a wonderful program to install from source via a Deb
package, that can later be uninstalled or upgraded.</p>

<p>Many thanks to lindqvist for saving me the hassle of working out the
dependencies!</p>

<p><strong>Update <a href="http://www.winehq.org/announce/1.5.0" title="Wine 1.5 Announcement">Wine 1.5 has now been announced</a>!</strong></p>

       ]]>
      </description>
    </item>
    
    <item>
      <title>Howto | Install Wine on LTSP</title>
      <link>https://chrisjrob.com/2010/10/06/install-wine-on-ltsp/</link>
      <pubDate>Wed, 06 Oct 2010 15:29:55 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2010/10/06/install-wine-on-ltsp</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/winehq_logo_glass.png" align="right" alt="Featured Image">
         
         <p><strong>These instructions have not been tested since re-writing, in particular there will be permissions issues.</strong></p>

<h2 id="step-1-install-wine">Step 1: Install Wine</h2>

<p>Please visit for instructions on how to install Wine:</p>

<!--more-->

<ul>
  <li>http://www.winehq.org/site/download</li>
</ul>

<p>If you get a problem with applications appearing without any text, then you need to install some Windows fonts in Wine. 
One option is to simply download them from <a href="http://sourceforge.net/projects/corefonts/">http://sourceforge.net/projects/corefonts/</a>. You may also be able to install via a debian installer package:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get ttf-mscorefonts-installer
</code></pre></div></div>

<p>Install Wine packages:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install libwine libwine-print libwine-sane libwine-alsa
</code></pre></div></div>

<p>Your requirements may vary, a non-inclusive list of available libraries is:</p>

<ul>
  <li>libwine: the core wine library</li>
  <li>libwine-print: the printing library</li>
  <li>libwine-sane: the scanning library</li>
  <li>libwine-alsa: the alsa sound library</li>
  <li>libwine-oss: the oss sound library</li>
</ul>

<p>You will notice winetools mentioned on several websites, my understanding is that this is no longer supported.</p>

<h2 id="step-2-create-a-wine-directory-for-your-application">Step 2: Create a Wine directory for your application</h2>

<p>By default Windows applications are installed in <code class="language-plaintext highlighter-rouge">/home/user/.wine</code>. If you want to install your application in a different directory then you must use the WINEPREFIX variable.</p>

<p>If you want your application to be installed in <code class="language-plaintext highlighter-rouge">/usr/local/share/appname</code> you must first create the directory:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ cd /usr/local/share
$ mkdir appname
$ WINEPREFIX="/usr/local/share/appname" wineprefixcreate
</code></pre></div></div>

<p>In this directory you will now find a fake Windows drive and the Wine configuration files system.reg and user.reg.</p>

<h2 id="step-3-configure-your-wine-directory">Step 3: Configure your Wine directory</h2>

<p><strong>You can probably skip this step for typical installations.</strong></p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ WINEPREFIX="/usr/local/share/appname" winecfg
</code></pre></div></div>

<h2 id="step-4-install-your-application">Step 4: Install your application</h2>

<h4 id="installing-from-an-msi-file">Installing from an .msi file</h4>

<p>You can install .msi files with the msiexec.exe utility. This command is built into Wine, so you don’t have to install Windows Installer from Microsoft.
If the .msi file is called msifile.msi you just have to type msiexec /i msifile.msi and the application will be installed.</p>

<p><strong>Make sure you’re not using a native version of msi.dll, but the builtin one.</strong>
To run the Windows install program, please type the following:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ WINEPREFIX="/usr/local/share/appname" wine /path/to/setup.exe
</code></pre></div></div>

<p><strong>Substitute “/path/to/setup.exe” with the installation path executable for your application</strong></p>

<h2 id="step-5-test-your-application">Step 5: Test your application</h2>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ WINEPREFIX="/usr/local/share/appname" wine "drive_c/Program Files/app/appname.exe"
</code></pre></div></div>

<h2 id="step-6-configure-for-multi-user-operation">Step 6: Configure for multi-user operation</h2>

<p><strong>This section needs a re-write (or just refer to Example automation script below)</strong></p>

<p>It is possible to configure the system so that a system Wine installation (and applications) can be shared by all the users, and still let the users all have their own personalized configuration.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Creating individual user directory, e.g. /home/username/.appname
# Symlink directory structure to /usr/local/share/appname
# Remove symlink for user.reg (will be auto-created for each user on first run)

$ ln -sf /usr/local/share/appname/system.reg system.reg
</code></pre></div></div>

<p>To assist in this process, please refer to the following guide:</p>

<ul>
  <li>http://www.winehq.org/site/docs/wineusr-guide/using-regedit</li>
</ul>

<p>and perhaps even symlink these back to the administrator’s account, to make it easier to install apps system-wide later:</p>

<p>You might be tempted to do the same for user.reg as well, however that file contains user specific settings. Every user should have their own copy of that file along with the permissions to modify it.</p>

<p>You’ll want to pay attention to drive mappings. If you’re sharing the system.reg file you’ll want to make sure the registry settings are compatible with the drive mappings in ~/.wine/dosdevices of each individual user. As a general rule of thumb, the closer you keep your drive mappings to the default configuration provided by wineprefixcreate, the easier this will be to manage. You may or may not be able to share some or all of the actual “c:” drive you originally installed the application to. Some applications require the ability to write specific settings to the drive, especially those designed for Windows 95/98/ME.</p>

<h3 id="example-automation-script">Example automation script</h3>

<p>This script was probably cobbled together from the superb ies4linux installation, or possibly from Franks Corner,</p>

<div class="language-pl highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1">#!/usr/bin/perl</span>
<span class="c1"># Launch script for multiuser appname, master copy in /usr/local/share/appname.</span>

<span class="k">use</span> <span class="nv">strict</span><span class="p">;</span>

<span class="k">my</span> <span class="nv">$MASTERPREFIX</span> <span class="o">=</span> <span class="p">'</span><span class="s1">/usr/local/share/appname</span><span class="p">';</span>
<span class="k">my</span> <span class="nv">$WINEPREFIX</span>   <span class="o">=</span> <span class="nv">$ENV</span><span class="p">['</span><span class="s1">HOME</span><span class="p">'}</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/.appname</span><span class="p">';</span>

<span class="k">use</span> <span class="nv">vars</span> <span class="sx">qw($MASTERPREFIX $WINEPREFIX)</span><span class="p">;</span>

<span class="c1"># If we're not set up, create the user's magic symlink-copy of the master</span>
<span class="c1"># installation.</span>

<span class="k">unless</span> <span class="p">(</span><span class="o">-</span><span class="nv">d</span> <span class="p">"</span><span class="si">$WINEPREFIX</span><span class="p">")</span> <span class="p">{</span>
	<span class="nb">system</span><span class="p">('</span><span class="s1">mkdir</span><span class="p">',</span> <span class="p">'</span><span class="s1">-p</span><span class="p">',</span> <span class="p">"</span><span class="si">$WINEPREFIX</span><span class="p">")</span> <span class="o">==</span> <span class="mi">0</span> <span class="p">](</span><span class="o">|</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">mkdir -p </span><span class="si">$WINEPREFIX</span><span class="s2">: $?</span><span class="p">";</span>
	<span class="nb">system</span><span class="p">('</span><span class="s1">lndir</span><span class="p">',</span> <span class="p">"</span><span class="si">$MASTERPREFIX</span><span class="p">",</span> <span class="p">"</span><span class="si">$WINEPREFIX</span><span class="p">")</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">lndir failed: is xutils installed? $?</span><span class="p">";</span>

	<span class="c1"># The profile directory will be recreated automatically by wine on the</span>
	<span class="c1"># first run, so it's OK to blow away eny existing copy hanging around in</span>
	<span class="c1"># unwritable symlink form from the install, and it's OK to just create a</span>
	<span class="c1"># blank one.</span>
   
	<span class="nv">$PROFILES</span> <span class="o">=</span> <span class="nv">$WINEPREFIX</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/drive_c/windows/profiles</span><span class="p">';</span>
	<span class="nb">system</span><span class="p">('</span><span class="s1">rm</span><span class="p">',</span> <span class="p">'</span><span class="s1">-fr</span><span class="p">',</span> <span class="p">"</span><span class="si">$PROFILES</span><span class="p">")</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">rm -fr </span><span class="si">$PROFILES</span><span class="s2"> failed: $?</span><span class="p">";</span>
	<span class="nb">system</span><span class="p">('</span><span class="s1">mkdir</span><span class="p">',</span> <span class="p">'</span><span class="s1">-p</span><span class="p">',</span> <span class="p">"</span><span class="si">$PROFILES</span><span class="p">")</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">mkdir -p </span><span class="si">$PROFILES</span><span class="s2"> failed: $?</span><span class="p">";</span>

	<span class="c1"># WINE needs to be able to write to the following files, so they can't be</span>
	<span class="c1"># symlinks to root-owned ones.</span>
   
	<span class="k">foreach</span> <span class="k">my</span> <span class="nv">$file</span> <span class="p">('</span><span class="s1">.no_prelaunch_window_flag</span><span class="p">',</span> <span class="p">'</span><span class="s1">system.reg</span><span class="p">',</span> <span class="p">'</span><span class="s1">userdef.reg</span><span class="p">',</span> <span class="p">'</span><span class="s1">user.reg</span><span class="p">')</span> <span class="p">{</span>
		<span class="k">if</span> <span class="p">(</span><span class="o">-</span><span class="nv">l</span> <span class="nv">$WINEPREFIX</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/</span><span class="p">'</span> <span class="o">.</span> <span class="nv">$file</span><span class="p">)</span> <span class="p">{</span>
			<span class="nb">system</span><span class="p">('</span><span class="s1">rm</span><span class="p">',</span> <span class="p">'</span><span class="s1">-f</span><span class="p">',</span> <span class="nv">$WINEPREFIX</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/</span><span class="p">'</span> <span class="o">.</span> <span class="nv">$file</span><span class="p">)</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">rm -f </span><span class="si">$WINEPREFIX</span><span class="s2">/</span><span class="si">$file</span><span class="s2"> failed: $?</span><span class="p">";</span>
			<span class="nb">system</span><span class="p">('</span><span class="s1">cp</span><span class="p">',</span> <span class="nv">$MASTERPREFIX</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/</span><span class="p">'</span> <span class="o">.</span> <span class="nv">$file</span><span class="p">,</span> <span class="nv">$WINEPREFIX</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/</span><span class="p">'</span> <span class="o">.</span> <span class="nv">$file</span><span class="p">)</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">Cannot copy </span><span class="si">$MASTERPREFIX</span><span class="s2">/</span><span class="si">$file</span><span class="s2"> to </span><span class="si">$WINEPREFIX</span><span class="s2">/</span><span class="si">$file</span><span class="s2">: $?</span><span class="p">";</span>
		<span class="p">)</span>
	<span class="p">}</span>
	<span class="nb">system</span><span class="p">('</span><span class="s1">chmod</span><span class="p">',</span> <span class="p">'</span><span class="s1">-R</span><span class="p">',</span> <span class="p">'</span><span class="s1">og-rwx</span><span class="p">',</span> <span class="nv">$WINEPREFIX</span><span class="p">)</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">Cannot chmod -R og-rwx </span><span class="si">$WINEPREFIX</span><span class="s2">: $?</span><span class="p">";</span>

<span class="p">}</span>

<span class="nb">exec</span><span class="p">('</span><span class="s1">env</span><span class="p">',</span> <span class="p">'</span><span class="s1">WINEPREFIX=</span><span class="p">'</span> <span class="o">.</span> <span class="nv">$WINEPREFIX</span><span class="p">,</span> <span class="p">'</span><span class="s1">wine</span><span class="p">',</span> <span class="nv">$WINEPREFIX</span> <span class="o">.</span> <span class="p">'</span><span class="s1">/drive_c/Program Files/appname/appname.exe</span><span class="p">',</span> <span class="nv">@ARGV</span><span class="p">)</span> <span class="o">==</span> <span class="mi">0</span> <span class="o">||</span> <span class="nb">die</span> <span class="p">"</span><span class="s2">Failed to launch appname: $?</span><span class="se">\n</span><span class="p">";</span>

<span class="nb">exit</span><span class="p">;</span>
</code></pre></div></div>

<h2 id="references">References</h2>

<ul>
  <li><a href="http://www.winehq.org/">WineHQ</a>
    <ul>
      <li><a href="http://www.winehq.org/mailman/listinfo/wine-users">Wine Mailing List</a></li>
    </ul>
  </li>
  <li><a href="http://www.ltsp.org/">LTSP</a>
    <ul>
      <li><a href="http://marc.info/?l=ltsp-discuss&amp;r=1&amp;w=2">LTSP Mailing List</a></li>
    </ul>
  </li>
  <li><a href="http://www.tatanka.com.br/">IES4Linux</a></li>
  <li>
    <table>
      <tbody>
        <tr>
          <td>Franks Corner</td>
          <td>http://frankscorner.org/}</td>
        </tr>
      </tbody>
    </table>
  </li>
  <li>Wine printing problems:
    <ul>
      <li>http://www.la-sorciere.de/Wine-HOWTO/wineprintconfig.html</li>
      <li>http://groups.google.com/group/comp.emulators.ms-windows.wine/msg/b05da7237281dbab</li>
    </ul>
  </li>
</ul>

       ]]>
      </description>
    </item>
    
    <item>
      <title>Howto | Install SMR2000 under Wine</title>
      <link>https://chrisjrob.com/2009/11/20/install-smr2000-wine/</link>
      <pubDate>Fri, 20 Nov 2009 17:45:22 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2009/11/20/install-smr2000-wine</guid>
      <description>
       <![CDATA[
         
         <p>I managed to install the Honda menu-pricing SMR2000 program on Wine:</p>

<ul>
  <li>Installed winetricks</li>
  <li>winetricks: fakeie, vb6run, mdac25, mdac28, jet40, vcrun6, wsh56, allfonts, riched30, mdac27, native_mdac, native_oldaut32, gecko</li>
  <li>Installed Adobe Reader 8.1.2 from Intranet Downloads</li>
  <li>Accepted Adobe licence via “wine regedit”, <code class="language-plaintext highlighter-rouge">HKEY_CURRENT_USER/Software/Adobe/Acrobat Reader/8.0/AdobeViewer</code>, add a DWORD “EULA” = “1”</li>
  <li>Installed SMR2000</li>
  <li>Updated SMR2000 by running update self-extracting zip files</li>
</ul>

       ]]>
      </description>
    </item>
    
    <item>
      <title>Howto | Install Scanning in Wine</title>
      <link>https://chrisjrob.com/2009/03/21/install-scanning-in-wine/</link>
      <pubDate>Sat, 21 Mar 2009 06:16:07 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2009/03/21/install-scanning-in-wine</guid>
      <description>
       <![CDATA[
         
         <p>Ensure you install the same version as wine.  For me that meant installing as follows:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install -t 'etch-backports' libwine-sane
</code></pre></div></div>

<!--more-->

<p>This worked to a fashion for me; in that it brought up a rather poor scanner dialog, and triggered the scanner, but never completed the scan job.  That said, I was using saned on LTSP (i.e. via network) which may be a step too far for libwine-sane!</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Howto | Install Print System</title>
      <link>https://chrisjrob.com/2009/03/21/install-print-system/</link>
      <pubDate>Sat, 21 Mar 2009 06:06:29 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2009/03/21/install-print-system</guid>
      <description>
       <![CDATA[
         
         <p>This document is certainly incomplete and possible inaccurate, please proceed with caution:</p>

<h2 id="install-cups-print-system">Install Cups Print System</h2>

<p>This also installs printer libraries, printing for GIMP, additional fonts etc.</p>

<!--more-->

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install cupsys cupsys-client cupsys-bsd cupsys-driver-gimpprint cups-pdf cupsys-pt cupsys-driver-gutenprint libgutenprint2 gutenprint-doc gutenprint-locales foomatic-db-gutenprint foomatic-db-engine foomatic-db foomatic-db-hpijs foomatic-filters foomatic-filters-ppds hplip hplip-doc hp-ppd hpijs hpijs-ppds hplip-data python-qt3 python-sip4 psfontmgr ttf-kochi-mincho ttf-arphic-bkai00mp ttf-arphic-bsmi00lp ttf-arphic-gbsn00lp ttf-arphic-gkai00mp ttf-baekmuk gs-cjk-resource xpp linuxprinting.org-ppds 
</code></pre></div></div>

<h2 id="wine-printing">Wine Printing</h2>

<p>See: http://frankscorner.org</p>

<p>Another way to print in Wine, steps:</p>

<ul>
  <li>regedit</li>
  <li>in <code class="language-plaintext highlighter-rouge">HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers\~cups_printer_name~</code></li>
  <li>find the key “Port”</li>
  <li>change it’s value to <code class="language-plaintext highlighter-rouge">|kprinter</code> for KDE</li>
</ul>

<p>When the user wants to print, the standard print dialog appears.</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Howto | Install IES4Linux on LTSP</title>
      <link>https://chrisjrob.com/2009/03/21/install-ies4linux-on-ltsp/</link>
      <pubDate>Sat, 21 Mar 2009 06:02:07 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2009/03/21/install-ies4linux-on-ltsp</guid>
      <description>
       <![CDATA[
         
         <h2 id="ies4linux">IES4Linux</h2>

<p>Internet Explorer for Linux</p>

<h2 id="recent-developments">Recent developments</h2>

<h3 id="bugs">Bugs</h3>

<p>Versions of Wine greater than 0.92 seem to cause IES4Linux to consume vast amounts of CPU both for wineserver and iexplore.exe. This problem seems to occur when accessing SSL pages (possibly Active-X pages).  Bugs have been <a href="https://bugs.launchpad.net/bugs/205895">logged with Ubuntu</a> which was quite rightly <a href="http://bugs.winehq.org/show_bug.cgi?id=13687">redirected to Wine</a>, which was rejected pending a <a href="http://bugs.winehq.org/show_bug.cgi?id=13734">regression test</a>, which in turn was redirected to IES4Linux.  The issue seems to be that Wine do not support native DLLs, but these are essential in making IE work under Linux.</p>

<!--more-->

<h3 id="deb-package">Deb package</h3>

<p>There <em>may</em> be a multi-user install deb package (for Ubuntu at least):</p>

<ul>
  <li>http://ubuntuforums.org/showthread.php?t=636758</li>
</ul>

<h2 id="install-wine">Install Wine</h2>

<p>Make sure you’ve installed Wine.</p>

<h2 id="read-debian-installation">Read Debian Installation</h2>

<ul>
  <li>http://www.tatanka.com.br/ies4linux/page/Installation:Debian</li>
</ul>

<h2 id="master-installation-ies4linux">Master Installation IES4Linux</h2>

<p>First you must create a master installation of ies4linux under <code class="language-plaintext highlighter-rouge">/usr/local</code>. To create the master copy, perform a standard ies4linux install as an ordinary desktop user (i.e. unpack the tarball, run <code class="language-plaintext highlighter-rouge">./ies4linux</code>):</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ wget http://www.tatanka.com.br/ies4linux/downloads/ies4linux-latest.tar.gz
$ tar zxvf ies4linux-latest.tar.gz
$ cd ies4linux-*
$ ./ies4linux
</code></pre></div></div>

<h2 id="convert-to-multi-user-system">Convert to Multi-user System</h2>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ cd
$ rm bin/ie{5,55,6}
$ sudo mkdir -p /usr/local/share
$ sudo chmod a+rX /usr/local/share
$ sudo mv .ies4linux /usr/local/share/ies4linux
$ sudo chown -R root:root /usr/local/share/ies4linux
$ sudo chmod -R a+rX /usr/local/share/ies4linux
</code></pre></div></div>

<ul>
  <li>http://www.tatanka.com.br/ies4linux/forum/viewtopic.php?t=431</li>
</ul>

<p>Then install this script as any or all of <code class="language-plaintext highlighter-rouge">/usr/local/bin/ie{5,55,6}</code> and let your users run it:</p>

<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#!/bin/sh</span>
<span class="c"># Launch script for multiuser ies4linux, master copy in /usr/local/share.</span>
<span class="c"># Install as /usr/local/bin/ie6 (or ie55 or ie5)</span>
<span class="c">#</span>
<span class="c"># Blame Andrew Chadwick &lt;andrewc-ies4linux0606@piffle.org&gt;, not Sergio.</span>
<span class="c">#</span>
<span class="c"># Released under the GNU GPL version 2 (or later, your call).</span>
<span class="c"># See ies4linux's own LICENSE or COPYING file for more information.</span>
<span class="c">####################################################</span>

<span class="nv">IE</span><span class="o">=</span><span class="sb">`</span><span class="nb">basename</span> <span class="s2">"</span><span class="nv">$0</span><span class="s2">"</span><span class="sb">`</span>
<span class="nv">MASTERPREFIX</span><span class="o">=</span><span class="s2">"/usr/local/share/ies4linux/</span><span class="nv">$IE</span><span class="s2">"</span>
<span class="nv">WINEPREFIX</span><span class="o">=</span><span class="s2">"</span><span class="k">${</span><span class="nv">HOME</span><span class="k">}</span><span class="s2">/.ies4linux/</span><span class="nv">$IE</span><span class="s2">"</span>

<span class="c"># If we're not set up, create the user's magic symlink-copy of the master</span>
<span class="c"># installation.</span>

<span class="k">if</span> <span class="o">!</span> <span class="nb">test</span> <span class="nt">-d</span> <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">"</span><span class="p">;</span> <span class="k">then
    if</span> <span class="o">!</span> <span class="nb">mkdir</span> <span class="nt">-p</span> <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">"</span><span class="p">;</span> <span class="k">then
        </span><span class="nb">echo</span> <span class="s2">"mkdir </span><span class="nv">$WINEPREFIX</span><span class="s2"> failed"</span>
        <span class="nb">exit </span>1
    <span class="k">fi
    if</span> <span class="o">!</span> lndir <span class="s2">"</span><span class="nv">$MASTERPREFIX</span><span class="s2">"</span> <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">"</span><span class="p">;</span> <span class="k">then
        </span><span class="nb">echo</span> <span class="s2">"lndir failed: is xutils installed?"</span>
        <span class="nb">exit </span>1
    <span class="k">fi</span>

    <span class="c"># The profile directory will be recreated automatically by wine on the</span>
    <span class="c"># first run, so it's OK to blow away eny existing copy hanging around in</span>
    <span class="c"># unwritable symlink form from the install, and it's OK to just create a</span>
    <span class="c"># blank one.</span>
   
    <span class="nv">PROFILES</span><span class="o">=</span><span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">/drive_c/windows/profiles"</span>
    <span class="nb">rm</span> <span class="nt">-fr</span> <span class="s2">"</span><span class="nv">$PROFILES</span><span class="s2">"</span>
    <span class="nb">mkdir</span> <span class="nt">-p</span> <span class="s2">"</span><span class="nv">$PROFILES</span><span class="s2">"</span>

    <span class="c"># WINE needs to be able to write to the following files, so they can't be</span>
    <span class="c"># symlinks to root-owned ones.</span>
   
    <span class="k">for </span>file <span class="k">in</span> .no_prelaunch_window_flag system.reg userdef.reg user.reg<span class="p">;</span> <span class="k">do
        if </span><span class="nb">test</span> <span class="nt">-L</span> <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">/</span><span class="nv">$file</span><span class="s2">"</span><span class="p">;</span> <span class="k">then
            </span><span class="nb">rm</span> <span class="nt">-f</span> <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">/</span><span class="nv">$file</span><span class="s2">"</span>
            <span class="nb">cp</span> <span class="s2">"</span><span class="nv">$MASTERPREFIX</span><span class="s2">/</span><span class="nv">$file</span><span class="s2">"</span> <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">/</span><span class="nv">$file</span><span class="s2">"</span>
        <span class="k">fi
    done
    </span><span class="nb">chmod</span> <span class="nt">-R</span> og-rwx <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">"</span>
<span class="k">fi

</span><span class="nb">export </span>WINEPREFIX
<span class="nb">exec </span>wine <span class="s2">"</span><span class="nv">$WINEPREFIX</span><span class="s2">/drive_c/Program Files/Internet Explorer/IEXPLORE.EXE"</span>
<span class="nb">echo</span> <span class="s2">"Failed to launch WINE: see above for details"</span>
<span class="nb">exit </span>1
</code></pre></div></div>

<p>Run the script above as an ordinary desktop user. When it runs, this script tries to create a WINE prefix location under the user’s home, consisting mainly of symlinks to the master copy’s files. It then launches IE in the normal way.</p>

<p>If it screws up, delete your <code class="language-plaintext highlighter-rouge">~/.ies4linux</code> directory and try again.</p>


       ]]>
      </description>
    </item>
    
  </channel> 
</rss>
