Main Forum > General Computer Support
Homegroup and Windows FW problems solved but now I can't play L4D2
LolosArt:
Ok, I'm not really sure what registering a file means.. But how would you know if swapping the order of the folders work?
Would you need me to try and recreate that whole mess again to test it? I really wouldn't want to mess with all the fixes, but let me know if I can help in any way.
Lolo
Shane:
When you register a dll or ocx file with the regsvr32.exe it writes the file information to the registry. This is how Windows knows where the file is and other information.
I checked and my repair does the syswow64 folder first then the system32 folder. I had it backwards from what i told you before.
Normally this isnt ever a problem as the 64bit and 32bit version get written, normally, to different areas in the registry.
Never seen a problem with any other program, and looks like it is only the steam dll that flips out. I have a feeling it was loading up the wrong version. But without more testing I wont know.
I dont want you to have to go through it again. I have L4D2, I just have to download it again. I can test on my system, and I can trace which file it is trying to hit and hopefully find what is going on :-D
Shane
Shane:
Ok so I got the game, I am on Windows 8.1 and ran my repair wmi, rebooted and the game loads to the main menu just fine.
I am using a ATI 7970 HD card with their latest drivers. Not sure if that would have any effect on it.
What video card and drivers do you have? And did the game at least make it to the main menu for you?
Shane
LolosArt:
Hey Shane,
I have gtx 680 with latest drivers and no, it never would get as far as actually launching. The small steam window that indicates that the game is launching would disappear quickly. On the friend's list my screen name would turn green and say I was in game for like 7 seconds before it went back to turning white and saying I'm online.
Maybe the game not launching problem may have been somehow connected to my initial problem of losing access to network sharing capabilities and windows firewall being unresponsive.
Shane:
Hard to tell. If I could replicate the problem i could trace it down. But I cant.
When the game loaded I went back to the desktop and opened up processexplorer and looked at the dlls loaded by the game and shaderapidx9.dll was in there.
I ran the same repairs as well. Only difference is I have ATI drivers while you have nividia. Maybe that has something to do with it.
But for now you are working and that is what counts :-)
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version