URL_ParseUrl FIXME messages on console when running/installing .NET apps are harmless and can be safely ignored. Example console output:

­­fixme:shell:URL_ParseUrl failed to parse L"mscorlib"

­Where "component" is one of ­the following:

• "IE5.01 or higher version is required"
• "Microsoft Windows Installer 3.0" is the requirement

Possible causes:

• inconsistent or broken WINEPREFIX (native overrides, services/device drivers). See Bug 16445 for such case.­
  
• wineboot problem (failed update of WINEPREFIX/timeout/permissions)
  

Solution:

First try to remove your old WINEPREFIX (rm -rf ~/.wine) and create a new o­ne by rerunning Winetricks .

If the problem persists, run wineboot manually:­

$ wineboot --update

­If you get a crash/backtrace like the following in console:

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipCreateFontFromLogfontW(HandleRef hdc, Object lf, IntPtr& font)
at System.Drawing.Font.FromLogFont(Object lf, IntPtr hdc)
at System.Drawing.Font.FromHfont(IntPtr hfont)
at System.Drawing.SystemFonts.get_DefaultFont()
at System.Windows.Forms.Control.get_Font()
....

You most likely have a corrupted or non-conformant truetype font in your system. These are the most notorious ones:

­­/usr/share/fonts/truetype/arphic/ukai.ttf
/usr/share/fonts/truetype/ttf-oriya-fonts/Samyak-Oriya.ttf­

Method 1: Removal of fonts

Either remove that font files manually (not just renaming) or use your Linux package manager. On Ubuntu something like:

$ sudo apt-get remove ttf-oriya-fonts­

Make sure you use a recent version of winetricks script to make sure you get all font fixes required for .NET.

After winetricks script update, execute the following command in console (if you don't want to reinstall everything in new WINEPREFIX):

­$ sh winetricks fontfix

'winetricks fontfix' will install working versions of truetype fonts known as broken (like the notorious "ukai"). Don't worry, your original (broken) ones from your Linux distribution will be left unchanged. The "good" fonts get installed into Wine/Windows font directory which has higher font search path precedence - so the good ones will be pulled in when found before defaulting to Linux distribution ones.

If the application still crashes with the workarounds applied showing the above backtrace file a bug with bugzilla.

Reason #1

You used an old Wine version (< 1.1.7). Upgrade to Wine >= 1.1.7 which fixed this specific problem.

For Wine version < 1.1.7 use winetricks step:

$ wget http://kegel.com/wine/winetricks && sh winetricks volnum

Reason #2

This message can also result from installing into a broken WINEPREFIX. The following console message is an indication of a WINEPREFIX problem:

­err:process:__wine_kernel_init boot event wait timed out

Remove your WINEPREFIX and create a new one.

Some winetricks scripts install a newer version of "Samyak Oriya" meant as Linux system override for broken font version ('fontfix' step).

Because this updated font gets installed into "c:\\windows\\fonts" it will always be selected first when a requested font or substitute is not found (font path precedence enforces order in list).

This might cause garbage symbol display. To work around this, please remove the font "c:\\windows\\fonts\\Samyak-Oriya.ttf" if it exists.

Additionally make sure you update or remove the Samyak-Oriya font installed in your Linux Distribution. It often causes more harm than good when using native gdiplus (especially for .NET apps).

On Ubuntu something like:

$ sudo apt-get remove ttf-oriya-fonts­

Never run wine as root (su, sudo)! Wine doesn't require to be run as root!

You will screw your WINEPREFIX and possibly other things up. If you have run Wine as root you need to:

$ sudo rm -rf ~/.wine­

and then run winecfg to set Wine folder structure back up. If you used winetricks script as root you might also need to:

$ sudo rm -rf ~/winetrickscache

Again: Just run wine as regular user and all should be fine.

­­Make sure you operate on a clean WINEPREFIX (~/.wine)!

Method 1: Installation by using 'winetricks' script

Use this option for easy installation of .NET 1.1 Framework. Winetricks will take care of all needed installation prerequisites and work around some problems.

$ wget http://kegel.com/wine/winetricks

$ sh winetricks corefonts dotnet11

You need cabextract utility for winetricks corefonts step. Make sure it's installed locally.

Ubuntu:

$ sudo apt-get install cabextract

Fedora:

­$ sudo yum install cabextract

Method 2: Manual installation

1.) Run the installer of .NET Framework 1.1

2.) optionally install corefonts (using winetricks)

Wine's msi component doesn't publish/install some assemblies into system GAC, see Bug 7098.

One example is Microsoft.VisualBasic.dll assembly. For instance VB.NET based apps won't run because they depend on these assemblies.

If you see an error message at the end of the installer in console like this:

­­err:msi:HANDLE_CustomType34 Unable to ­execute command L"\"C:\\windows\\Microsoft.NET\\Framework\\netfxsbs11.exe\" /install"

This message is harmless and expected (see my comment here).

Unattended Installation

Example command lines you can use to perform unattended installations for the .NET Framework 1.1 installation­:
­

Silent installation

These command lines will run the .NET Framework 1.1 setup in fully silent mode. The setup package will extract to a temporary location and installation will begin with no user interaction and no visible UI. The user will see no visible indication that setup is running.

$ ­wine setup.exe /q:a /c:"install.exe /q"­

­

Standard unattended installation

These command lines will run the .NET Framework 1.1 setup in standard unattended mode. The setup package will extract to a temporary location and installation will begin with no user interaction. A progress dialog will appear on the screen during installation, and it will disappear when setup is complete. Errors encountered during installation might pop up message boxes during installation if they occur.

­$ wine setup.exe /q:a /c:"install.exe /qb"

Unattended installation with no cancel button available in the UI

These command lines will run the .NET Framework 1.1 setup in unattended mode with no cancel button. The behavior of setup is the same as with the command lines above except the cancel button will be hidden on the progress page during installation. This allows the user to know that a setup is in progress but prevent them from cancelling it (unless they kill the process).

­$ wine setup.exe /q:a /c:"install.exe /q­b!"

­

This message most likely results from installing software into a broken WINEPREFIX. Remove your WINEPREFIX and create a new one.­

This is­ ­­­­bug 16956 (applying transforms to Media table with same disk id).

You can try to fake the service pack install by using following registry keys (assuming you already have the appropriate .NET Framework version installed). This is not a solution if your application depends on some service pack specific feature!

.NET Framework version 1.1 SP1

[HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v1.1.4322]
"SP"=dword:00000001

.NET Framework version 2.0 SP1

[HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727]
"SP"=dword:00000001