Unpacker. The installer works somewhat if started manually. It can get to the "installing components" screen if Windows version is set to Windows 95 in winecfg.
What does not
Installation fails at the installing components screen in Win95 mode, and sooner than that in WinXP mode.
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 10.04 "Lucid" amd64 (+ variants like Kubuntu)||Sep 12 2011||1.3.28||Yes||Yes||Silver||A Wine user|
|Show||Ubuntu 10.04 "Lucid" amd64 (+ variants like Kubuntu)||Nov 24 2010||1.3.6||Yes||Yes||Silver||A Wine user|
|Show||Ubuntu 10.04 "Lucid" amd64 (+ variants like Kubuntu)||Jul 09 2010||1.2-rc7||No||Not installable||Garbage||Michael Lancaster|
|Current||Ubuntu 9.10 "Karmic" amd64 (+ variants like Kubuntu)||Feb 24 2010||1.1.39||No||Not installable||Garbage||A Wine user|
|Show||sidux||Sep 25 2009||1.1.29||No||Not installable||Garbage||phobie|
This note was originally added to IE Version 5, but may be relevant to all versions.
Don't run IE on an RW mounted DOS partition !
Pretty problematic directory renaming/corruption can happen.
This seems to happen if Wine doesn't have access to certain Windows registry keys.
Renames e.g. "Program Files" to "$!$!$!$!.pfr" and does other horrible things.
BTW, it does not only happen with IE, as it seems to be a generic Windows Setup process of Explorer which is doing this, which can be launched under multiple circumstances.
To be safe, use a backup copy only, i.e. copy all relevant windows files over e.g. to an ext2 partition.