[Wine] Problems installing Watchguard Firebox System software in wine (installshield)

Kevin Hanser kevin at mica.net
Tue Oct 11 13:23:16 CDT 2005

Thanx for all the good suggestions!  It turns out that the suggestion of 
updating my wine installation was the one that was needed.  I wiped out 
my .wine dir (this is the first app I've tried to install in wine), and 
emerge'd the 20050930 release.  After that, the installer ran all by 
itself w/no native dll's!  After installation I needed to grab MFC42.dll 
from my windoze box, and now the app seems to be running great! 



Holly Bostick wrote:

>Several things you could try:
>1) cd to the directory containing the installer first, then try running
>it again. InstallShield installers are particularly notorious (in my
>experience) for refusing to run from a 'long path' command rather than
>from the current directory (from which they run successfully).
>2) Assuming that your setup is correct (which may not be true, but let's
>start from the easiest steps to the hardest), the problem may be that
>the previous install attempts left 'borked' setup files that are
>continually being read. I've seen this happen a lot. To fix this:
>a) make sure all instances of Wine are stopped; in a terminal, run the
>following commands -- in fact, you should do this before performing any
>of the suggested commands:
>killall -9 wine
>killall -9 wineserver
>killall -9 wine-preloader
>b) go to /tmp/  (which is the default location where Windows will
>extract pre-installation files), and look for a folder name that doesn't
>look like it's from Linux but from Windows, and seems to be dedicatedly
>temporary (sorry that's not more precise, but obviously I can't know
>what the temporary extraction folder is going to be called, and that's
>how I find them when this happens to me), something like this:
>ls -UF /tmp
>==> Config.Msi/ (pretty obviously a Windows-created dir, but not really
>==> Ultra$ISO/ (I know this is a program installed under Wine, also not
>==> IXP000.TMP/ (this looks a lot like a Windows temporary install
>I hope you see what I mean; single files, or things with my username, or
>named as programs that I know to be Linux apps (seahorse, keyring, kde),
>can be ignored, but IXP000.TMP/ is pretty evident as a Windows-created
>directory (if only because it looks nothing like the other Linux
>directories), and looking inside it proves the point:
>ls /tmp/IXP000.TMP/
>ACCESSIB.CNT  cdccln.inf    eula.txt      mp2wrap.exe   msdxddex.inf
>oleaut32.dll  rmvv1.inf     vh263ax.inf
>ACCESSIB.HLP  CFGMGR32.DLL  fhgax.inf     mpeg4ax.inf   msdxmLC.DLL
>oleaut.inf    RUNDLL32.EXE  vidx16.dll
>ACELPDEC.AX   choose.inf    hlink.dll     mpg2splt.ax   msdxm.ocx
>ole.inf       schannel.dll  VoxMSDec.ax
>acelp.inf     control.ini   hlinkprx.dll  mpg4ds32.ax   MSMS001.vwp
>olepro32.dll  SETUPAPI.DLL  voxmsdec.inf
>actmovie.exe  ddexinst.exe  inloader.dll  mplayer2.cnt  msvcrt.dll
>qdvd.dll      setup.inf     VoxMVDec.ax
>ADVPACK.DLL   ddrawex.dll   l3codecx.ax   mplayer2.exe  msvcrt.inf
>qnspro.dll    stdole2.tlb   voxmvdec.inf
>amov4ie.inf   devenum.dll   laprxy.dll    mplayer2.hlp  MVoiced.vwp
>quartz.dll    strmdll.dll   vvAudFlt.ax
>amovfix.inf   drmclien.dll  logagent.exe  mplayer2.inf  nafiles.txt
>quartz.vxd    unam4ie.exe   vvVidFlt.ax
>amstream.dll  drmstor.dll   mciqtz32.dll  MPSUPP.HLP    NPDSPlay.dll
>quiet.inf     unregmp2.exe  W95INF16.DLL
>asfsipc.dll   dxmasf.dll    mciqtz.drv    msadds32.ax   NPDS.zip
>reboot.inf    urlmon.dll    W95INF32.DLL
>axdist.inf    dxmini.exe    mp2tiger.inf  msaudio.inf   npwmsdrm.dll
>Regsvr32.exe  vg723ax.inf   wininet.dll
>This directory was created by some Windows installer, which probably
>failed to run (because if the installer had completed, these temporary
>files should have been cleaned up/deleted). However, any re-run of the
>installer will attempt to extract these files again, possibly to the
>same directory, and apparenty does not delete/overwrite
>previously-existing files.
>I don't know squat about InstallShield or any other installer, but I can
>tell you that deleting previously extracted temporary installer files
>from a failed installer extraction often helps to rectify issues when
>you've changed your Wine configuration in order to enable the installer
>to run.
>I hope that makes sense in some way; but it may be clearer if you try it.
>c) go to step 3, and then run the installer again.
>2) upgrade Wine (current version 20050930, ~x86 in Gentoo) contains a
>number of fixes to the support for InstallShield installers; it may
>solve your issue without having to do anything else. I would suggest
>removing or renaming your ~/.wine directory before running it (the many
>changes in Wine over the past few months don't seem to play all that
>well with previous installs).
>3) If you don't want to or can't upgrade Wine at this time, perhaps the
>problem is that Wine doesn't know what DCOM you want to use (because you
>have installed DCOM98, but also copied Win2K dlls). If you are convinced
>that installing native DCOM dlls is necessary, blow away your ~/.wine
>folder (again/anyway), and run 'wine' to recreate it clean (basically
>without the self-installed native DCOM98, which a) may not be necessary,
>and b) may be a problem, since the application doesn't even work/install
>under 98 anyway, so it seems unlikely that it would be happy to find
>native 98 dlls).
>Then copy your Win2K dlls to the Wine system directory and perform one
>of the two following branches:
>I: To run just this installer using these dlls as native, use the
>WINEDLLOVERRIDE setting (the corrected command assumes that you cd-ed to
>the directory containing WFS73s.exe):
>WINEDLLOVERRIDES="ole32,oleaut32,rpcrt4=n" wine "WFS73s.exe /setup"
>II: To set a permanent DLLOVERRIDE for this *.exe (which in this case is
>'safe' to do, because the installer has a unique name, unlike
>'Setup.exe' which is what's usually found, and creating a per-app
>default for 'Setup.exe' would then apply to all installers which you
>normally might not want to do):
>- run 'winecfg'
>- in the first tab (Applications), click the 'Add Application' button
>and browse to and select WFS73s, then select it in the main window so
>that it is highlighted (and the Titlebar reads 'Wine Configuration for
>- go to the second tab (Libraries), and type 'ole32' (without '.dll') in
>the 'New override for dll: field, then click 'Add'. Repeat for oleaut32
>and rpcrt4.
>-  each of these dlls will appear in the 'Existing overrides' box as
>'(native,builtin); if you want to set them only to 'native', select each
>dll and click the 'Edit' button, where you can select something
>different (like "native (Windows)" only).
>Click the 'Apply' or "OK'  buttons to save the settings, or to save the
>settings and exit winecfg, then try your install again.
>Hope this helps,

More information about the wine-users mailing list