Lumarra -> RE: NEVERENDING Crash at startup (8/3/2012 9:51:09 AM)
|
First, my apologies for jumping in here, causing somewhat of a ruckus and then up and disappearing, I was extremely busy the last few weeks and not able to work on getting 'Legends' running. It was always on my mind though, thinking of alternative ways to fix the error but I couldn't dedicate the time to it lately. However, today was the first day I was able to actually have some time to spend on it. As I had stated in my OP, I had tried nearly everything to get Legends working under Win7/x64 with absolutely no luck whatsoever and it had become just a disgusting frustration. I even grabbed some relatives and friends who weren't even gamers or all that familiar with how games work under Windows (except for Solitaire and Angry Birds...lol) but I figured it might help to have a different perspective on it. Still, nothing worked. I came about >this< close to installing WinXP on a separate partition and dual-booting JUST to be able to play Legends (and some other apps that have failed to load under x64). Today I didn't even know where I should start, so rather casually, I read the thread again and ran RegEdit and erased any and all references to DW or Legends in the registry. That done, I then remembered I had pulled Windows Media Player, Media Center and IE9 out before stepping away from it the last time I was here a few weeks ago. I use Firefox and GOM player anyway, so having those removed didn't make much difference. I didn't even realize they were gone at first until I saw my IE9 desktop shortcut was showing a 'broken' icon. I went into 'Windows Features On/Off' in the Control Panel and rechecked Media Center, Media Player and IE9 and reboot... Upon getting to my desktop again, my IE9 icon was back to normal and functional. WMP 12 was in and running fine, as was Media Center. I crossed my fingers and began reinstalling DW, letting it install dotNet 3.5 on it's own even though I have 4.0 installed already. I figured it wouldn't hurt. I knew DX9 was up-to-date, so I left that one alone. My vid drivers were brand new, Catalyst 12.7 betas. I installed RotS next and without updating it, went right into Legends after. Once Legends was in, I patched it to 1.7.0.6 (since that was the latest publicly released patch). After everything was done, I sat there and took a deep breath. The voice in the back of my head was say it wasn't going to work and I was just asking for a slap in the face, but I ran it anyway, and this is what I got... [image]https://lh3.googleusercontent.com/--NAcKxxNYes/UBtaBY7-wNI/AAAAAAAAACQ/IpTZukhcD1s/s800/DistantWorlds-TogetherAgainAtLast-080312-1234am.jpg[/image] It didn't appear right away and I was getting ready for that error to pop up and start screaming bloody murder, but the splash screen popped up instead and I truly had my stomach in my throat for a second, I just couldn't believe what I was seeing! I mean, could it be?! That's ALL it took to get running again?! After everything I had tried and failed and it was just like that?! I was considering screaming bloody murder anyway after realizing all of this but then I was just overjoyed to finally be able to play my beloved game once again! So, to conclude my story (and hopefully the whole ordeal), the thing that I believe fixed the dreaded 'CLR20r3' error was to completely wipe the registry of all traces of DW and Legends, if they were there, and then pull out WMP12, WMC, and IE9 via 'Programs and Features' in the Control Panel, under Windows Features On/Off on the left panel. Uncheck them, reboot after it's finished, recheck them all and reboot again, thus re-installing the originals. Make sure your dotNET is updated (also have DW install dotNET3.5 at the end of it's setup even if you have 4.0 already. It doesn't seem to interfere at all, much like the vcredistx86/x64 C runtime's don't conflict with each other (indeed, I must have at least 6 in my system, all different versions - 2005, 2008, and 2010) and DirectX9. Don't forget your video card drivers either! Thank you, to everyone that pitched in and tried to help. Hopefully anyone else coming in with the same problem will see this post, along with the others and work out a way to fix their particular error without losing their minds in the process! Now, if you'll excuse me, I have a few months worth of turns to catch up on... [;)] -Lumarra
|
|
|
|