http://bugs.winehq.org/show_bug.cgi?id=14556
--- Comment #5 from Anastasius Focht focht@gmx.net 2008-07-19 05:51:46 --- Hello,
--- quote --- But I wonder why it's broken now and it was ok on 1.0.
..
I still don't understand WHY it works on 1.0 and not on 1.1.1 .
And, I'm still not sure that's just that one the problem. Bug 14040 was there in 1.0 and on 1.1.1 too, dotnet20 did work on 1.0 and doesn't now. --- quote ---
Because .NET lies on top of win32 API, covering a large part of it. Every time new APIs get added in wine (partly or completely implemented) it might affect parts of .NET. Same applies to changing behaviour of existing API or just plain regressions.
Due to this large coverage, practically every area in wine can cause failures or new behaviour for .NET apps.
For your reference: The ngen registry bug was also present in wine 1.0
--- snip --- $ which wineserver ~/wine-install/wine-1.0/bin/wineserver
$ wine --version wine-1.0
$ pwd /home/focht/.wine/drive_c/windows/Microsoft.NET/Framework/v2.0.50727
$ wine ./ngen.exe executeQueuedItems
fixme:powrprof:DllMain (0x60a70000, 1, (nil)) not fully implemented fixme:ntdll:NtPowerInformation Unimplemented NtPowerInformation action: 16 Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42 Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Exception from HRESULT: 0x80070005 (E_ACCESSDENIED) You must have administrative credentials to perform this task. Contact your system administrator for assistance. --- snip ---
Again: This bug is *not* the cause of your problem.
You did not state what your *actual* problem is.
"It crashes some time later due to unimplemented gdi call."
So what? What should one do? Guess the call?
Whenever I see rather unspecific "Doesn't work" I don't feel inclined to help. Though an exception might be if the area covers some of my interests.
Same applies to forums .. there is guesswork, FUD spread there - even from regulars - that makes me cringe every time and I quickly flip to next page. If you have a problem that looks like a bug/regression, report it on bugzilla and provide *all* the necessary information (clean WINEPREFIX, all install steps, tracelogs/backtraces ...).
Regards