wow runtime error, new with patch 3.3

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
denali
Level 2
Level 2
Posts: 21
Joined: Fri Jul 04, 2008 1:43 pm

Post by denali »

I tried the above captioned fixes; no joy.

What I noticed is this. I normally start the game with this command line:

Code: Select all

WINEDEBUG="fixme-all" wine "/home/denali/.wine/drive_c/Program Files/World of Warcraft/WoW.exe" -opengl
This causes the error. However, when I start with this command line:

Code: Select all

wine .wine/drive_c/Program\ Files/World\ of\ Warcraft/Wow.exe
I don't get the error. Any ideas?
elliez
Newbie
Newbie
Posts: 1
Joined: Tue Dec 08, 2009 11:40 pm

Post by elliez »

@shadyman thank you very much for these detailed directions! finally got it working!
timpa
Level 1
Level 1
Posts: 6
Joined: Sat Sep 26, 2009 4:24 am

Post by timpa »

PiperMatt wrote:This has apparently worked for some folks:

Code: Select all

wget http://www.kegel.com/wine/winetricks
sh winetricks vcrun2005sp1 vcrun2005
Worked for me, thanks!
Richie086
Newbie
Newbie
Posts: 3
Joined: Tue Dec 08, 2009 5:55 pm

Post by Richie086 »

BTW i got everything working by removing all x86_64 wine rpms (just leave the i386 or i586 rpms), and then installing the C++ executable

So if you are running x86_64, try that as a fix
contrebasse
Newbie
Newbie
Posts: 2
Joined: Wed Dec 09, 2009 8:12 am

Post by contrebasse »

winetricks didn't work for me, but when I try to install vcredist_x86.exe manually I get the error "Command line option syntax error. Type command /? for Help."
I used :

Code: Select all

export WINEPREFIX=/mnt/win/Linux/WoW/wine-wow
wine vcredist_x86.exe
Any ideas ?
contrebasse
Newbie
Newbie
Posts: 2
Joined: Wed Dec 09, 2009 8:12 am

Post by contrebasse »

I found out : vcredist_x86.exe had to be in my home folder...

But I still get the error R6034 !
I get a wow error when removing the @ in my e-mail address, ("can not connect" or "can not validate wow version") that's strange...
timpa
Level 1
Level 1
Posts: 6
Joined: Sat Sep 26, 2009 4:24 am

Post by timpa »

Did use

Code: Select all

wget http://www.kegel.com/wine/winetricks
sh winetricks vcrun2005sp1 vcrun2005
to get it working. Logged out and left the computer for a few hours.

When I try loading the game (after chosing character) I get:
"The program WoW.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."

Any ideas?
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Post by Fallhallen »

For those who have successfully fixed this issue, What type of install are you guys using? Did you install WoW in Wine? Or are you pointing to a WoW installation on a Windoze drive?

I am using Slackware 13 and wine-1.1.23

I have a duel-boot on this machine, running Windoze 7 on a separate HD. I run WoW in linux by simply pointing to the WoW executable in my Windoze drive. I have never had a problem before this update. I have tried using Winetricks to install the aforementioned upgrades, that did not work. I also tried downloading the source and running that install as mentioned. This also did not work. I am wondering if it is not working because I do not have a native Wine install of WoW? I could not get WoW to install in Wine using the DVD's or the Downloader. Is there an easy workaround to get things back up and running again? Having to reboot multiple times a day is a pain.

Thanks
MacNean Tyrrell

wow runtime error, new with patch 3.3

Post by MacNean Tyrrell »

I run Ubuntu 9.10 64bit, dedicated, no windows partition.
Wine 1.1.33 32bit with quasi Hardware mouse in openGL patch, built in pulse
audio patch also. I have tried 2 different wine prefixes, one with
./winetricks vcrun2005 and one with the downlaoded file from MS. Both work
fine for me.

Check the folder permissions, the launcher lately in linux has changged the
folder permissions (something for windoze 7) that wasn't allowing WoW.exe to
be run by the user. Just had to change the folder permissions back.

On Wed, Dec 9, 2009 at 10:51 PM, Fallhallen <[email protected]>wrote:
For those who have successfully fixed this issue, What type of install are
you guys using? Did you install WoW in Wine? Or are you pointing to a WoW
installation on a Windoze drive?

I am using Slackware 13 and wine-1.1.23

I have a duel-boot on this machine, running Windoze 7 on a separate HD. I
run WoW in linux by simply pointing to the WoW executable in my Windoze
drive. I have never had a problem before this update. I have tried using
Winetricks to install the aforementioned upgrades, that did not work. I
also tried downloading the source and running that install as mentioned.
This also did not work. I am wondering if it is not working because I do
not have a native Wine install of WoW? I could not get WoW to install in
Wine using the DVD's or the Downloader. Is there an easy workaround to get
things back up and running again? Having to reboot multiple times a day is
a pain.

Thanks





--
Sincerely,

MacNean C. Tyrrell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Post by Fallhallen »

All my folder permissions on that drive are RW for users and root. And I run WoW in user mode, not root. I have tried running it in both, but I still get the same issues in Root. Is that what you meant by folder permissions? RW access?
MacNean Tyrrell

wow runtime error, new with patch 3.3

Post by MacNean Tyrrell »

Yea, what is the exact error/problem?


On Wed, Dec 9, 2009 at 11:11 PM, Fallhallen <[email protected]>wrote:
All my folder permissions on that drive are RW for users and root. And I
run WoW in user mode, not root. I have tried running it in both, but I
still get the same issues in Root. Is that what you meant by folder
permissions? RW access?





--
Sincerely,

MacNean C. Tyrrell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Post by Fallhallen »

Same error everyone else is getting:

microsoft visual C++ runtime library
Runtime error!
Program z:/mnt/Windoze/Users/Games/world of warcraft/wow.exe

R6034
An Application has made an attempt to load the C runtime library incorrectly.
Please contact the applications support team for more information.

The error appears after you enter your username and password and click the login button.
docfruitbat

wow runtime error, new with patch 3.3

Post by docfruitbat »

On Wed, 09 Dec 2009, "Fallhallen" wrote:
For those who have successfully fixed this issue, What type of install
are you guys using? Did you install WoW in Wine? Or are you pointing to
a WoW installation on a Windoze drive?

I am using Slackware 13 and wine-1.1.23
A fellow slacker!! :-)
As a data-point, I'm running Slackware 11 and wine-1.1.34 (self built).
I have a duel-boot on this machine, running Windoze 7 on a separate HD.
I run WoW in linux by simply pointing to the WoW executable in my Windoze
drive. I have never had a problem before this update. I have tried using
Winetricks to install the aforementioned upgrades, that did not work. I
also tried downloading the source and running that install as mentioned.
This also did not work. I am wondering if it is not working because I do
not have a native Wine install of WoW? I could not get WoW to install in
Wine using the DVD's or the Downloader. Is there an easy workaround to
get things back up and running again? Having to reboot multiple times a
day is a pain.
I actually took a different approach. I removed the following files from
my WorldofWarcraft directory:

Microsoft.VC80.CRT.manifest
msvcr80.dll

It seems these were either incorrectly installed by the patch. Further
more, it only placed this one file from the full MSVC Runtime instead the
rest of the files which are usually distributed with it. It appears the
manifest doesn't match the file (which is why you get the bizarre error
message about the runtime being the incorrect version).

So, I removed both of them and WoW loaded just fine for me. Go figure.
YMMV.
Thanks
--
Peter A. Castro <[email protected]> or <[email protected]>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Post by Fallhallen »

hrm.... I had hopes, but that had no effect for me. Same error. Are you running Wine in XP mode? Is there anything I need to change in Winecfg? I have mine set for XP mode.
docfruitbat

wow runtime error, new with patch 3.3

Post by docfruitbat »

On Thu, 10 Dec 2009, "Fallhallen" wrote:
hrm.... I had hopes, but that had no effect for me. Same error. Are you
running Wine in XP mode? Is there anything I need to change in Winecfg? I
have mine set for XP mode.
I'm running in XP mode, but it doesn't seem to matter (I've tried Win
2000 mode and WoW doesn't seem to care). I didn't change anything in
winecfg either.

Are you getting the R6034 Runtime error? If so, have you applied the
vcrun2005sp1 or vcrun2005 via winetricks?

The runtime appears to be under C:/windows/winsxs. In the /manifest dir
under winsxs there should be a correct manifest for
Microsoft.VC80.CRT.xxxxx.
eg:
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700

Check that that matchs the actual directory of the same name under
winsxs. Then check that your system.reg has the same references to that
same version (there were 8 references of them in mine).

I recall the error said what the versions it expected and found. Check
that you have that version in the manifest directory. In my example, it
wanted "4053" but the installed version was actually "762". The
erroneous 4053 was coming from that Microsoft.VC80.CRT.manifest in my
WoW directory. Once I removed that, it looked for the manifest in the
correct (ie: registered) place.

I don't know weither WoW really needs this apparent update (4053) or not.
All I know is that my game play doesn't seem to encounter any problems
(yet).

One additional thing to note. I had trouble applying vcrun2005sp1 via
winetricks myself. It starts to apply it and then appears to error out
(though I'm not really sure Im reading the output correctly), so I don't
really know if I even have vc2005sp1 installed correctly (still have to
verify the version numbers somehow).

Again, YMMV.

Good luck!

--
Peter A. Castro <[email protected]> or <[email protected]>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Re: wow runtime error, new with patch 3.3

Post by Fallhallen »

I'm not really understanding you...
docfruitbat wrote: Are you getting the R6034 Runtime error? If so, have you applied the
vcrun2005sp1 or vcrun2005 via winetricks?
Yes, I am getting the R6034 Runtime error. Yes I applied both patches via winetricks (I also tried the manual patch as mentioned earlier)
docfruitbat wrote: The runtime appears to be under C:/windows/winsxs. In the /manifest dir
under winsxs there should be a correct manifest for
Microsoft.VC80.CRT.xxxxx.
eg:
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700
I have a C:\windows\winsxs\manifests directory, which holds over 10,000 files. There are 6 different x86_Microsoft.VC80.CRT files. Most of them are version 762.
docfruitbat wrote: Check that that matchs the actual directory of the same name under
winsxs. Then check that your system.reg has the same references to that
same version (there were 8 references of them in mine).
There are no sub-directories in C:\windows\winsxs\manifests so I cannot match the file with a directory. Also, I do not know where system.reg is located. I did a search, found nothing.

Here is what my WINE is telling me:

fallhallen@SlackHem:~$ wine /mnt/Windoze/Users/Public/Games/World\ of\ Warcraft/WoW.exe
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:iphlpapi:GetAdaptersAddresses no support for IPv6 addresses
fixme:iphlpapi:GetAdaptersAddresses no support for IPv6 addresses
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:service:EnumServicesStatusW 0x1246c0 type=30 state=3 (nil) 0 0x87e7c8 0x87e7d4 0x87e7d0
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x20000001,(nil),0x0001,0x00000000,0x87e5d8,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x20000001,(nil),0x0001,0x00000000,0x1244f0,(nil)): stub
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
fixme:mixer:ALSA_MixerInit No master control found on MPU-401 UART, disabling mixer
fixme:advapi:SetSecurityInfo stub
archive Data\enGB\patch-enGB.MPQ opened
archive Data\patch.MPQ opened
archive Data\enGB\patch-enGB-2.MPQ opened
archive Data\patch-2.MPQ opened
archive Data\expansion.MPQ opened
archive Data\common.MPQ opened
archive Data\common-2.MPQ opened
archive Data\enGB\locale-enGB.MPQ opened
archive Data\enGB\speech-enGB.MPQ opened
archive Data\enGB\expansion-locale-enGB.MPQ opened
archive Data\enGB\expansion-speech-enGB.MPQ opened
fixme:win:EnumDisplayDevicesW ((null),0,0x39ed9c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39ebd4,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39f2cc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39f3e0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39f578,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39f574,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39f5e0,0x00000000), stub!
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface
fixme:win:EnumDisplayDevicesW ((null),0,0x39eff8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39f130,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39dedc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39df04,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x39ded0,0x00000000), stub!
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 5000
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 5000
fixme:reg:GetNativeSystemInfo (0x37404484) using GetSystemInfo()
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface
fallhallen@SlackHem:~$ fixme:service:EnumServicesStatusW 0x1246c0 type=30 state=3 (nil) 0 0x87e7b0 0x87e7bc 0x87e7b8

If I am reading this correct, it is looking for a Microsoft.VC80.CRT" (8.0.50727.762) version file. From the aforementioned directory, those numbers match up. So what exactly am I suppose to do? I prefer to have very specific idiot proof answers, because I am not fluent in everything, so please do not assume I know how to do anything.

Thanks for the help
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Post by Fallhallen »

***FIXED***

***FIXED***

Here is what I did:

Step one, DO NOT DELETE ANYTHING!!!'

Step two: Navigate to your World of Warcraft Directory (this will be different depending on your version of Windoze) Mine was found in:

C:\Users\Public\Games\World of Warcraft

Step Three: Edit the Microsoft.VC80.CRT.manifest file

Step Four: Find the line that looks like this:

<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.4053" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

Replace the version number to 8.0.50727.762 (it should look like this)

<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

Step Five: Save the file (it is a good idea to first make a backup file before overwriting)

All done. Your WoW should work perfectly. (You may also need to apply the aforementioned updates). But this worked for me.
faeyin
Newbie
Newbie
Posts: 1
Joined: Thu Dec 10, 2009 11:06 pm

Post by faeyin »

I hope you submit this fix in a nice public place Fall :) it worked for me and it's by far the easiest fix I've seen in all the places I've looked.

Thanks very much!

Fallhallen wrote:***FIXED***

***FIXED***

Here is what I did:

Step one, DO NOT DELETE ANYTHING!!!'

Step two: Navigate to your World of Warcraft Directory (this will be different depending on your version of Windoze) Mine was found in:

C:\Users\Public\Games\World of Warcraft

Step Three: Edit the Microsoft.VC80.CRT.manifest file

Step Four: Find the line that looks like this:

<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.4053" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

Replace the version number to 8.0.50727.762 (it should look like this)

<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

Step Five: Save the file (it is a good idea to first make a backup file before overwriting)

All done. Your WoW should work perfectly. (You may also need to apply the aforementioned updates). But this worked for me.
thethinker
Level 1
Level 1
Posts: 9
Joined: Fri Dec 11, 2009 1:27 am

Still not working...

Post by thethinker »

Hey guys,
I found all your fixes, dilligently used winetricks and the microsoft site, and changed the version in the .CRT file, but no dice. I'm getting the exactly same error message about C++ runtime when I (try to) log in. Wine errors are:

Code: Select all

fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
But I noticed that there is some apparent installation problem when I do any of the following three commands:
sh winetricks vcrun2005
sh winetricks vcrun2005sp1
wine vcredist_x86.exe

I get things like the following:

Code: Select all

fixme:advapi:LookupAccountNameW (null) L"USERNAME" (nil) 0x33f590 (nil) 0x33f594 0x33f588 - stub
fixme:advapi:LookupAccountNameW (null) L"USERNAME" 0x152820 0x33f590 0x153020 0x33f594 0x33f588 - stub
fixme:msi:ACTION_HandleStandardAction unhandled standard action L"SetODBCFolders"
fixme:msi:msi_unimplemented_action_stub RemoveExistingProducts -> 1 ignored L"Upgrade" table values
fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 10 ignored L"MsiAssembly" table values
fixme:msi:install_assembly Manifest unhandled
fixme:msi:install_assembly Win32 assemblies not handled
In the above I've replaced my username with USERNAME. So perhaps VC is not installing correctly, in any way at all? Any idea on how to fix this?
JaySulli
Newbie
Newbie
Posts: 2
Joined: Fri Dec 11, 2009 4:24 pm

Visual C++ load error when logging into WOW

Post by JaySulli »

vib3 wrote:Third confirmation here. Logged into WoW without a problem after installing the distributable from the MS website. Wine-Doors install DID NOT work for me. Thanks guys. :)
Exactly the same with me here, too. Thanks, guys. I'd been tearing my hair out over this silly error for the past two days!
:evil:
There was a short message when I tried to log in about my account not being validateable anymore, but I quit and restarted and it was fine after that. :wink:
JaySulli
Newbie
Newbie
Posts: 2
Joined: Fri Dec 11, 2009 4:24 pm

Post subject: Quirks downloading WoW patches

Post by JaySulli »

Btw: does anyone else have recent patch downloads (the last two as well as this one) keep changing the file mode on their drive_c/Program Files/World of Warcraft directory, locking them out? I have to keep chmod-ing mine back. Not really a problem because this fixes it, but a bit irritating.
Jim Hall

wow runtime error, new with patch 3.3

Post by Jim Hall »

On Fri, Dec 11, 2009 at 3:53 PM, JaySulli <[email protected]> wrote:
Btw: does anyone else have recent patch downloads (the last two as well as
this one) keep changing the file mode on their drive_c/Program Files/World
of Warcraft directory, locking them out? I have to keep chmod-ing mine back.
Not really a problem because this fixes it, but a bit irritating.


That's about all you can do. Blizzard thinks it's a great idea for Windoze
so we suffer for it

Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>
billdozor
Newbie
Newbie
Posts: 4
Joined: Fri Dec 11, 2009 8:52 pm

Post by billdozor »

I am running Ubuntu 9.10 64 bit
kernel 2.6.31-16
wine 1.0.1
and the following fix WORKED. Thank you!
Fallhallen wrote:***FIXED***

***FIXED***

Here is what I did:

Step one, DO NOT DELETE ANYTHING!!!'

Step two: Navigate to your World of Warcraft Directory (this will be different depending on your version of Windoze) Mine was found in:

C:\Users\Public\Games\World of Warcraft

Step Three: Edit the Microsoft.VC80.CRT.manifest file

Step Four: Find the line that looks like this:

<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.4053" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

Replace the version number to 8.0.50727.762 (it should look like this)

<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

Step Five: Save the file (it is a good idea to first make a backup file before overwriting)

All done. Your WoW should work perfectly. (You may also need to apply the aforementioned updates). But this worked for me.
Fallhallen
Level 1
Level 1
Posts: 8
Joined: Wed Dec 09, 2009 10:44 pm

Re: Still not working...

Post by Fallhallen »

thethinker wrote:Hey guys,
I found all your fixes, dilligently used winetricks and the microsoft site, and changed the version in the .CRT file, but no dice. I'm getting the exactly same error message about C++ runtime when I (try to) log in. Wine errors are:

Code: Select all

fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
But I noticed that there is some apparent installation problem when I do any of the following three commands:
sh winetricks vcrun2005
sh winetricks vcrun2005sp1
wine vcredist_x86.exe

I get things like the following:

Code: Select all

fixme:advapi:LookupAccountNameW (null) L"USERNAME" (nil) 0x33f590 (nil) 0x33f594 0x33f588 - stub
fixme:advapi:LookupAccountNameW (null) L"USERNAME" 0x152820 0x33f590 0x153020 0x33f594 0x33f588 - stub
fixme:msi:ACTION_HandleStandardAction unhandled standard action L"SetODBCFolders"
fixme:msi:msi_unimplemented_action_stub RemoveExistingProducts -> 1 ignored L"Upgrade" table values
fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 10 ignored L"MsiAssembly" table values
fixme:msi:install_assembly Manifest unhandled
fixme:msi:install_assembly Win32 assemblies not handled
In the above I've replaced my username with USERNAME. So perhaps VC is not installing correctly, in any way at all? Any idea on how to fix this?
Which version of Wine are you running?
tparker
Level 5
Level 5
Posts: 354
Joined: Tue Feb 24, 2009 3:06 pm

wow runtime error, new with patch 3.3

Post by tparker »

On Friday 11 December 2009 4:53:28 pm JaySulli wrote:
Btw: does anyone else have recent patch downloads (the last two as
well as
this one) keep changing the file mode on their drive_c/Program
Files/World
of Warcraft directory, locking them out? I have to keep chmod-ing mine
back. Not really a problem because this fixes it, but a bit irritating.
Yup, that has been happening for a while. You can also change them back
through the graphical interface. If you have to do a re-install of the game
before this changes I would recommend leaving the window with the wow
folder open in the background so you can easily change permissions -
after every single little patch! lol.
Locked