Runtime Error

[expatpom]

Had the not so unusual CTD with the ODE error today , then after restarting the PC and trying to get back into WWIIOL had this error after signing in and clicking campaign.

Runtime Error

R6030

-CRT not initialized.

This is a new one on me , wont let me get in at all.

[expatpom]

Anyone?

[expatpom]

Ok..

This is getting a tad annoying now , this has been up here for almost 24 hours and not one answer from support.

I STILL cannot get into the game , I have checked the logfiles and the error that Bloo described is not occurring.

[petie]

have you tried uninstalling and reinstalling?

[expatpom]

Yes,

And still the same issue.

Also tried to access 'offline' and the same error appears.

Edited May 24, 2011 by expatpom

[petie]

may want to try downloading c++ redistributable from microsoft

[expatpom]

Tried that as well.

No luck on that one

Thanks for your suggestions though Pete, appreciate it, would be nice to see someone from CRS posting on here.

Edited May 24, 2011 by expatpom

[expatpom]

All I hear is crickets.....

Surely someone from support can post on here no ?

So far...CRS support is......well....

Nowhere.............................................................................

Edited May 25, 2011 by expatpom

[AHWULF]

This error has something to do with the application not starting up correctly. Since it obviously worked for you at one point and you reinstalled and it still fails, I would suspect something in the environment is interfering with the client initialization. Bad drivers, registry errors, the usual Windows virus stuff, OS update that didn't quite succeed are all possible.

The CRT is the basis for all applications on Windows applications (common runtime) and is run by Windows before the application code actually starts. So it is either something environmental or a bad copy of the application itself (corrupted). I would guess the environment. It's not a programming kind of bug since this failure happens before the client code is even touched. dll's are usually involved in an application startup and can affect the CRT if they are broken or hacked by something.

Change anything (or had it done to you such as Windows update) before the game stopped working?

[expatpom]

Hi Mate,

And thanks for your response.

In the last few days I have been doing some digging around and it seems the issue is down to an upgrade by Norton 360 from release 4.0 to 5.0

Managed to track this down by going through each and everything on the PC individually which as you can imagine has been a right pain in the posterior.

Finally uninstalling Norton is the answer.

I wonder if you are able to replicate the issue there as well as I am thinking that this may well not be an isolated incident as the upgrades come into play at the time Norton further subscription is required (when it installs the update).

I had no issues with the previous release but it seems Norton in their infinite wisdom have sodded up this one (5.0)

And of course seeing as Norton progs have this inbuilt tamper proof code in-bedded there is no way I can dig around the registry and change anything.

Let me know if you can replicate the issue.

Now to join the legions of patient folks on Norton support....

[GOPHUR]

Glad you found it Exta. I really can;t replicate that as we don't have Norton and really don't have the support staff to QA oyther people's bugs. There was one other mention of this error on our bug reports but only 1.

For future reference (and your sanity) this is a testing and bug reporting forum. When we're not in beta it doesn't get much attention though I do ultimately read everything written here.

To get support you need to visit the community support forum or drop a support ticket on us. Well to get timely support anyway. I'll get to you eventually here...