Several serious errors with dotnet40, msxml3, dotnet11

[GoogleCodeExporter]

Several serious errors with winetricks 20140726 on FreeBSD_11-curent.
shell is csh, WINEARCH=win32, wine-ver 1.7.22

What I have installed under wine thus far:
corefonts dotnet40 cabinet comctl32 secur32 crypt32 msasn1 msls31 d3dx9_36 ie6 
pngfilt.  FONTS: liberation opensymbol unifont droid corefonts consolas tahoma 
lucida uff

1. This error still continues:
$ {bash} winetricks list-installed  => sort: -k -k3.1: Invalid argument

2. winetricks corefonts dotnet40 => installs dotnet40 but no previous dotnet 
(11 - 35sp1)
I run "wine "c:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\ngen.exe" 
update" and dotnetverifier confirms 40-client as installed. But running a 
dotnet-dependent app shows mscoree, parsing and many more errors: 
dotnet40-err.txt

3. Tring to fix #2, "winetricks msxml3" results in error: msxml3-err.txt

4. Again, tring to fix mscoreee from #2, "winetricks dotnet11" results in 
error: dotnet11-err.txt

5. I lost track of what I was trying to install, but it failed with this old 
error:
"fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the 
registry for bias 180, std (d/m/y): aa/bb/2014, dlt (d/m/y): cc/dd/2014"

Original issue reported on code.google.com by r...@berentweb.com on 31 Jul 2014 at 3:45

Attachments:

• dotnet40-err.txt
• msxml3-err.txt
• dotnet11-err.txt

[GoogleCodeExporter]

I was able to solve most of this problem by running on completely clean wine 
prefix:
winecfg && winetricks win7
winetricks dotnet35 dotnet40 corefonts
wine "c:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\ngen.exe" update
wine ./netfx_setupverifier.exe
winetricks cabinet secur32 crypt32

I left the windows version at win7 (did not switch back to XP) and things seem 
to be working. You can ignore issues numbered 2, 3, & 4.

Original comment by r...@berentweb.com on 2 Aug 2014 at 1:21

[GoogleCodeExporter]

Why are you setting windows version to 7? That can break a lot of applications 
and should not be done without a good reason.

Original comment by austinenglish@gmail.com on 3 Aug 2014 at 3:39

[GoogleCodeExporter]

> Why are you setting windows version to 7? That can break a lot of  
> applications and should not be done without a good reason.  
OK, I did a clean re-install on default (XP), it completed without problems.

winetricks msxml6 OR winetricks vb6run (and several other installs) fail with 
this message:
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the 
registry for bias -120, std (d/m/y): 26/10/2014, dlt (d/m/y): 31/03/2014
wine: Unhandled page fault on read access to 0x00000000 at address 0x1331a82 
(thread 002e), starting debugger...

Any way to correct this other than manually editing the registry?

Original comment by r...@berentweb.com on 4 Aug 2014 at 10:16

[GoogleCodeExporter]

You could change TZ in your environment before running wine{,tricks}

Original comment by austinenglish@gmail.com on 4 Aug 2014 at 5:47

[GoogleCodeExporter]

Not viable, it seems it's a wine bug. I have updated a wine PR accordingly:
http://bugs.winehq.org/show_bug.cgi?id=36966

Original comment by r...@berentweb.com on 4 Aug 2014 at 6:17

[GoogleCodeExporter]

$ setenv TZ 'Europe/London'
$ winetricks vb6run => installs without problem

$ winetricks msxml6 => still results in error, logs attached.

Original comment by r...@berentweb.com on 8 Aug 2014 at 5:47

Attachments:

• backtrace-msxml6.txt
• msxml6-install.log

[GoogleCodeExporter]

Is that with a clean wineprefix? Or are you setting windows version to 7/other 
tweaks?

What compiler was used to compile wine?

Original comment by austinenglish@gmail.com on 8 Aug 2014 at 5:58

[GoogleCodeExporter]

No, wine prefix is not clean, it has a bunch of stuff installed. I tried a 
clean / zero wine folder and msxml6 did install. I suppose I now have to 
re-start from scratch?

I would assume the compiler is clang, but the wine port on FreeBSD installs 
from a combination of pre-compiled binaries + source. I emailed the port 
maintainer re this question.

Original comment by r...@berentweb.com on 8 Aug 2014 at 6:31

[GoogleCodeExporter]

If it works in a clean WINEPREFIX, it's not a valid bug.

Original comment by austinenglish@gmail.com on 8 Aug 2014 at 6:35

• Changed state: Invalid