I've tried following the other suggestions in the thread with no luck.
I'm on Windows 7 64bit.
So far no nothing I've done has resulted in successfully loading the game. I've turned .Net 3.5.1 off and on, uninstalled the game, reinstalled.
The error thrown is:
quote:
Unhandled Exception
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.---> System.Runtime.InteropServices.COMException (0x80040154): Class not registered (Exception from HRESULT: 080040154
and so on.
The error seems to indicate an issue with .Net, but the netfx_setupverifier assures me everything verifies successfully.
The error happens regardless of the compatibility settings.
After installing ROTS the following error is thrown when attempting to launch the game:
Description: Stopped working
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: distantworlds.exe Problem Signature 02: 1.5.0.0 Problem Signature 03: 4d07cec1 Problem Signature 04: System Problem Signature 05: 2.0.0.0 Problem Signature 06: 4a275e12 Problem Signature 07: 3a97 Problem Signature 08: 394 Problem Signature 09: System.ComponentModel.Win32 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033
When using compatibility mode for XP SP2 the following error is thrown: Description: Stopped working
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: distantworlds.exe Problem Signature 02: 1.5.0.0 Problem Signature 03: 4d07cec1 Problem Signature 04: System.Windows.Forms Problem Signature 05: 2.0.0.0 Problem Signature 06: 4a275ebd Problem Signature 07: 199c Problem Signature 08: 2 Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033
Don't know why but that com exception with the class not registered makes me think of a game install problem, not a .NET problem; that's why I wanted to confirm if it ever worked before moving to ROTS.
Thank you, a pleasure to be here . So far the game hasn't worked at all. A fresh install, without patching, results in the first error. Patching or installing the expansion results in the second.
cookie monster:
I've tried various ways of fixing .Net. Windows 7 uses .Net 2 as a critical system, and .Net 3 can only be activated/deactivated through the "Turn Windows features on or off" in the control panel. I've also tried using sfc /scannow - still no luck.
There is an interesting error in the event viewer: Error 1111 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_64) - Service reached limit of transient errors. Will shut down. Last error returned from Service Manager: 0x80029c4a.
I suspect this may be the root cause, can you confirm?
This is a new one but looks particular enough, I'll google for it and let you know if I find something relevant; do you have another Windows where you can setup the game? at least to confirm that the Windows installation is not the actual problem.
Hi guys, I'm having the same problem. The game will not launch , but it ran fine on my older windows 7. The only difference is that this one is a little newer and its an hp with an AMD processor(instead of an intell). Now I've tried all the various versions on this pc and none of them work on it. So I'm guessing it might be the brand perhaps ?? here are the various errors (for each version) Description: Stopped working
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: distantworlds.exe Problem Signature 02: 1.5.0.0 Problem Signature 03: 4d07cec1 (release version 1.5) 4d134ca3 (first update) Problem Signature 04: System.Drawing Problem Signature 05: 2.0.0.0 Problem Signature 06: 4a275e83 Problem Signature 07: 7af Problem Signature 08: 6c Problem Signature 09: System.ArgumentException OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Problem Event Name: CLR20r3 Problem Signature 01: distantworlds.exe Problem Signature 02: 1.5.0.8 Problem Signature 03: 4d8d101c (this is with the "latest update") Problem Signature 04: System.Drawing Problem Signature 05: 2.0.0.0 Problem Signature 06: 4a275e83 Problem Signature 07: 7af Problem Signature 08: 6c Problem Signature 09: System.ArgumentException OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033
< Message edited by princej -- 5/24/2011 5:32:25 PM >
All my other games/softare work fine so it would appear that its related to the .net 2.0 It is also possible that one of the optional windows updates contain a fix for this.
princej, can you run services.msc and see if Microsoft .NET Framework NGEN v2.0.50727_X64 or Microsoft .NET Framework NGEN v2.0.50727_X86 is running? I'm beginning to suspect that might be the issue - at least for me.
Data: Unfortunately the only other non-work machine is my wife's laptop. I dare not risk her wrath, so I'm not even going to bother trying to install it on there.
I understood your link - trying various things. Will report back later.
Alright , I'll do that and get back with you on it. but I can definately tell you its not a problem with the update as it runs perfectly on my xp with the latest update (it just will not run on my new win7)
< Message edited by princej -- 5/26/2011 10:09:38 AM >
-----problem located ---------------- I have located the problem and fix for our systems. Once I enabled the services, I got the error listed on the left side of the attatched image. Now pay close attention to the right side of the image. Did you notice that something was missing ? To make this short, the font whitch is called in the code on the left is simply not present on our speciffic systems. You can verify on your system this by opening up notepad and attempting to change your font to "verdana" regular.
The Fix
1)You can do like me and grab the font from an older system that you own or get the font from a freinds pc by going to c:\windows\fonts Once you find the font hold down ctl press "C" . You can now paste the file to an external drive and install it to your system by right clicking on the file and clicking install. 2)An alternate more exspensive method is to purchase it : here
I am very happy to report that I am now able to run DWRS with the latest patch but in the process of searching for the answer ran accross some very interesting articles here
Hi Crane and welcome to the forum, the fact that if work fine with 1.0.6 but not with 1.0.7 kinda confirms your setup is ok. I was thinking the .NET is newer than the one recomended for the game but it works with 1.0.6, maybe 1.0.7 hits an incompatibility. How exactly did you apply 1.0.7? you used the game updater or downloaded it and installed it manually?
Just tried something found by google command prompt: "Regsvr32 C:\Windows\System32\Kernelbase.dll"
It said: "The module 'C:\Windows\System32\Kernelbase.dll' was loaded but the entry-point DllRegisterServer was not found. Make sure that "c:\windows\System32\Kernelbase.dll" is a valid DLL or OCX file and then try again.
Yap, registering dll's manually helps sometimes but I've never heard of this helping with any DW issue so far. Still, it's the only lead we've got so far; if it is this, than trying the 1.0.7 on another windows where you don't get this message might be a good test, see if it behaves the same way there also. At the very least it will eliminate this dll as a possible root cause.
Posts: 224
Joined: 9/23/2002 From: Terrapin Station Status: offline
Wow.
If you're the sort to read a tech support forum before you buy a game, this should send you running for the hills. These guys apparently don't have a clue as to what they are doing. No way on earth should a piece of software have these sorts of problems.
The problems obviously began with ROTS and the equivalent 1.07 update to DW. They broke something when they did this. But, instead of trying to figure it out, they have their customers running around jumping through hoops to reconfigure their computers.
I worked for years with a programming group that worked in C# and .net. We never had problems like this. Heck, this sounds like it never would have passed our beta testing. Serious install problems requiring a customer to reconfigure Windows and uninstall and reinstall .net .... that would definitely be a 'bug' that would flunk a beta test.
I can't believe a company is asking customers to do this sort of stuff. This is insane.
Me, I do some programming myself in .net. So, no way is it even thinkable that I'm going to even think about messing with my computer, which in every other way related to .net is working fine, in order to wage what sounds like an hours-long fight to install some silly game. Not a chance. I can write my own .net programs, install them and run them with no problems ... and there's no way I'm even going to think about messing with that to solve some problem that some wacky game programmers can't solve in their own code.
There are lots of .net programs and programmers out there. Lots of people write .net programs that don't have these sorts of problems. They broke something or did something they shouldn't have done when they did the expansion. Now they've got their customers jumping through hoops because they can't or won't fix it.
Sure glad I read this before I plunked down any money. Wow. There are some seriously incompetent people around here, ranging from the programmers who wrote this to the support people telling customers to seriously reconfigure windows to run a game, and I hope I remember never to do business with them in the future.
I hope people know what they are doing when they start running some of these serious re-configurations of windows. If you don't think of yourself as a 'geek', in the long run you might be a whole lot happier if you just returned this game and its buggy install and got your money back before you mess up your computer doing this sort of stuff. Please be careful.
oUCH , in my case ,it was not the game or the programmers , but the way that the OS was configured on my new" computer. Of all the pc's I installed it on DW worked perfectly and I had no problems running the game or its exspansions until I got an HP. Infact, I honestly cant recomend that anyone buys an HP anymore because windows 7 may be a great OS on the right brand but an HP appears to me to be a different monster as its hard to get anything to run on this thing without modifications. (just a thought that it might not be the programmers , but the brand or speciffic model of pc that some may be using)
Until the actual root cause is found we're just speculating, that's why is safer to hold off on casting blames...or inflate the issue to the point of blaming the entire game or developers and such.
Having worked in a dev environment, you should know that there are many possible causes for software crashes. Consider the number of variables the application needs to account for, processor, OS, DirectX, external libraries (just to name a small few). If any one of those variables is corrupted, then it's entirely possible for the application to crash or even fail to load. Even poorly written third party applications may crash your application, and there's not a thing you can do about that.
In my case the blame lies firmly on Microsoft's shoulder. My .Net framework was corrupted, and as it's now a core component of Windows 7, I couldn't simply re-install it. My options were to either do a lot of digging in the registry or to do a completely fresh install of W7.
Either way, I'm having a lot of fun with the game and I strongly recommend it.
Printable Version
All Forums >> [New Releases from Matrix Games] >> Distant Worlds 1 Series >> Tech Support >> Game crashes before loading 
Game crashes before loading - 
. So far the game hasn't worked at all. A fresh install, without patching, results in the first error. Patching or installing the expansion results in the second. 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread