eaccess violation

posted on January 11th, 2010, 11:22 pm

address of the armada2.exe is giving me an error now after i've been able to play fo mod for a few days.  I have reinstalled several times and even tried to use a cracked exe.  I do not have access to orignal disk anymore.  Any suggestions?

posted on January 11th, 2010, 11:30 pm

welcome to the forums
did you have sent a bug report? i then may be able to help you.

[Gavisk]

posted on January 11th, 2010, 11:43 pm

Last edited by Gavisk on January 12th, 2010, 2:39 am, edited 1 time in total.

yes i did and i saved the report just can't find where it saved to. And thanks for the welcome.

posted on January 12th, 2010, 1:39 am

heres the log and thanks for any help you can give me.

Attachments

exceptArmada2.txt

(18.16 KiB) Downloaded 251 times

[DOCa Cola]

posted on January 12th, 2010, 8:22 am

Last edited by DOCa Cola on January 12th, 2010, 8:45 am, edited 1 time in total.

strange, first time i see that kind of issue. i will analyze the crash and let you know what may have caused it.
btw. for some reason i have not received a bug report from you via mail.
edit2: i found an earlier report from someone who had the same crash that you were reporting. he said that the error occurred when he used a no-cd patch. are you trying to use a no-cd patch too? if so, i'd try to use another patch

posted on January 12th, 2010, 8:58 am

Hey there

now, i also have a crash, but i have to say, its the first time ever....


so here is the report and as i think, its an eaccess violation too, i dont use a no-cd patch, i use the original armada2 cd.


greetings

Attachments

exceptArmada2.txt

(18.6 KiB) Downloaded 187 times

posted on January 12th, 2010, 9:02 am

so here is the report and as i think, its an eaccess violation too, i dont use a no-cd patch, i use the original armada2 cd.

your crash is actually a different one. eaccess violation is a general term when something goes wrong. his log shows a crash during cd check...

posted on January 12th, 2010, 9:07 am

your crash is actually a different one. eaccess violation is a general term when something goes wrong. his log shows a crash during cd check...

what ever you say....
i just noticed, that something went wrong....

posted on January 12th, 2010, 9:12 am

what ever you say....
i just noticed, that something went wrong....

no problem at all. it's my job to look at the crashes anyway, not yours i am not sure about your crash yet, rüdiger, but i think thats one of those rare armada crashes that i have no clue about why they occur at all.

posted on January 12th, 2010, 9:17 am

as i said, it was the first crash ever....

so who cares (not me) 

the report is just to help....

posted on January 12th, 2010, 7:14 pm

This turned out to be a bad armada2.exe file.  Thanks Doca cola for the rapid response and the help resolving this issue.  This is a great community and a great mod.  I'm going to retire from eve so I can spend more time learning this game.

posted on January 12th, 2010, 7:28 pm

as i said, it was the first crash ever....

so who cares (not me) 

the report is just to help....

I care, because I had the same crash today and also for the first time. I just couldn't send a bug report because my game PC has no internet access and I was too lazy to transfer the report via USB-stick yet

posted on January 12th, 2010, 9:24 pm

no problem at all. it's my job to look at the crashes anyway, not yours i am not sure about your crash yet, rüdiger, but i think thats one of those rare armada crashes that i have no clue about why they occur at all.

Maybe someone rigged it...

[RedEyedRaven]

posted on January 13th, 2010, 10:05 am

Last edited by RedEyedRaven on January 15th, 2010, 12:31 pm, edited 1 time in total.

The romulans and section 31 did it. They managed to sabotage the new FO-exe 


Edit: Got an access violation again, so I've tagged on a bug report.

Attachments

exceptArmada2.txt

(16.93 KiB) Downloaded 201 times

posted on January 15th, 2010, 12:34 pm

Sorry for the double-post, but I also don't want my report to be overlooked while that topic gets forgotten