Windows 7 help please

[Raz_Specter]

Hi Guys,

 

I am currently running BS on Windows 7. Problem is that 80% of the time when i launch the game the main screen comes up as normal then i choose what i want to do, i.e. mission or campaign then when the game tries to launch in to the mission a windows error box comes up

 

"The application was unable to start correctly (0x0000142)"

 

I have searched everywhere to find what is causing this but to no avail.

 

Anyone else having this error or can suggest a way forward?

 

Thanks Mithandra

[pbsmgm]

Hi Guys,

 

I am currently running BS on Windows 7. Problem is that 80% of the time when i launch the game the main screen comes up as normal then i choose what i want to do, i.e. mission or campaign then when the game tries to launch in to the mission a windows error box comes up

 

"The application was unable to start correctly (0x0000142)"

 

I have searched everywhere to find what is causing this but to no avail.

 

Anyone else having this error or can suggest a way forward?

 

Thanks Mithandra

 

My recommendation, don't rely so much on beta OS's. Put Vista 64 on your machine and at least wait for Win 7 RC1 before generating error tickets..:cry:

[EtherealN]

That's a bit harsh.

 

People using the W7 betas are a fantastic way to make sure that BS is tested on that OS when it gets released, decreasing the risk of incompatibilities when W7 goes commercial. (Cross-reference the many issues that was going on around the Vista release.)

[joey45]

^^ as soon as i can afford vista 64.

[pbsmgm]

That's a bit harsh.

 

People using the W7 betas are a fantastic way to make sure that BS is tested on that OS when it gets released, decreasing the risk of incompatibilities when W7 goes commercial. (Cross-reference the many issues that was going on around the Vista release.)

 

How is that harsh? Where in the world did I say stop using Win7? Where in the world did I say that we don't want people tesing BS on Win7? I said don't RELY so much on beta OS's. My point is, if one is not OS savvy enough to figure out the problem and post solutions, then they are at their own risk. Granted, I do agree that at least notifying everyone of this error is probably better than not. ok, so maybe I jumped the gun a little...but a bit harsh? Do you live in the real world? But I mean this in an all good and productive nature.

Edited April 23, 2009 by pbsmgm

[joey45]

there is a problems and bugs part of the forum you know. and there are some topics related to Win7 beta.

 

a simple search found this - http://forums.eagle.ru/search.php?searchid=1376670

[pbsmgm]

there is a problems and bugs part of the forum you know. and there are some topics related to Win7 beta.

 

 

EXCELLENT point joey45....:thumbup:

[joey45]

:smartass:

[EtherealN]

Yes, it is harsh because you gave mithandra a put-down for the fact that they asked a question about a problem that arose in a beta system. You basically told them to install Vista64 and STFU.

 

If you had at least said "well, maybe this should be in the Problems & Bugs section to be easier for people to find", then there would have been a constructive point.

 

As it stands all you did was to slap mithandra for asking for help deciphering an error report. That is harsh and the antithesis of being constructive. If everyone responded to people having W7-related issues like you just did, we'd get pretty much zero testing done on W7 and the testing that were to happen would be by people who are "OS savvy enough" to figure out solutions - and who knows if they cba to post the solutions? How many of the posts in the Problems section are of the style "hey, I ran into this problem and this is how I fixed it"? How many are of the style "Hey I have this problem" and someone else goes "Hm, that's interesting" and then figure it out?

 

There exists a few threads of the first style. 98% of problems and their solutions are proliferated precisely because people raise attention to issues they haven't been able to solve themselves.

 

Getting an attitude on them is just shooting yourself in the foot. If you didn't have anything constructive to say, say nothing.

 

And that's all I'm going to say on that subject, since we'll be derailing this thread otherwise.

[pbsmgm]

Yes, it is harsh because you gave mithandra a put-down for the fact that they asked a question about a problem that arose in a beta system. You basically told them to install Vista64 and STFU.

 

If you had at least said "well, maybe this should be in the Problems & Bugs section to be easier for people to find", then there would have been a constructive point.

 

As it stands all you did was to slap mithandra for asking for help deciphering an error report. That is harsh and the antithesis of being constructive. If everyone responded to people having W7-related issues like you just did, we'd get pretty much zero testing done on W7 and the testing that were to happen would be by people who are "OS savvy enough" to figure out solutions - and who knows if they cba to post the solutions? How many of the posts in the Problems section are of the style "hey, I ran into this problem and this is how I fixed it"? How many are of the style "Hey I have this problem" and someone else goes "Hm, that's interesting" and then figure it out?

 

There exists a few threads of the first style. 98% of problems and their solutions are proliferated precisely because people raise attention to issues they haven't been able to solve themselves.

 

Getting an attitude on them is just shooting yourself in the foot. If you didn't have anything constructive to say, say nothing.

 

And that's all I'm going to say on that subject, since we'll be derailing this thread otherwise.

 

ok, now it's gone from me making a whimsical solution to me having an attitude problem. :pilotfly: That's Incredible...you took my intitial comment to this level. In fact, my initial comment is constructive. Are you the tsar of the forum parsing emotional elements or something? Maybe it's your unbelievable interpretations that drive people away from the forum. Is that constructive?

Edited April 23, 2009 by pbsmgm

[192nd_Erdem]

I use Win7 beta too, and sometimes I have the exact problem. A search in ED forums revealed that there's a slight incompatibility with Win 7(as said by an ED dev). BTW there are some users experiencing the problem in Vista too, so it's not a Win7 isolated problem.

 

Sometimes a restart solves the problem for me, sometimes opening-closing the game does the trick too. Sometimes everything works just fine.

 

BUT the ultimate solution is to use DCSMax, and launch the mission from there. You won't get any errors. Bad thing is you can't play campaigns this way, but campaigns are not Vista compatible and you'll keep getting errors anyway.

[Devas]

Hi pbsmgm!!! if you have an ATI, as I do, try disabling the Catalyst AI and test again, I have solved that way :book:

 

See you!!:thumbup:

[slug88]

I use Win7 beta too, and sometimes I have the exact problem. A search in ED forums revealed that there's a slight incompatibility with Win 7(as said by an ED dev). BTW there are some users experiencing the problem in Vista too, so it's not a Win7 isolated problem.

 

Sometimes a restart solves the problem for me, sometimes opening-closing the game does the trick too. Sometimes everything works just fine.

 

BUT the ultimate solution is to use DCSMax, and launch the mission from there. You won't get any errors. Bad thing is you can't play campaigns this way, but campaigns are not Vista compatible and you'll keep getting errors anyway.

 

Err, the campaigns are perfectly compatible with both Vista and W7. The "incompatible" disclaimer that they wrote was intended more as a (imho very poorly worded) warning that memory issues may arise on lower end machines. However, with the affinity tools, performance under Vista and W7 is actually superior to XP. I believe it was even stated that they will change the wording of the disclaimer with the patch.

 

Anyway, I do see this error about 50% of the time I try to launch a mission in W7. Usually, if I try a second or third time, it will load just fine. Considering that it adds about 30 seconds to the load time of each mission, I don't find it to be too big a deal. I'm going through the GOW campaign now and I've learned to live with the error.

[Slick Twitchy]

It is weird, I used to get same or similar bug, but after a reinstall of nvida drivers and messing with ntune (to cool the CPU) the bug seems to have disappeared. It would crash occasionally, and I could usually just restart.

[Madmatt_BFC]

I too have encountered this problem pretty frequently under Windows 7.

 

For me, I have found two reliable ways to get around this problem.

 

The first option, if you want to only play a stand-alone mission and don't need to read the briefing, is to use the excellent DCS Max program and automatically load up into the mission.

 

If I need to read a briefing, or need to play a campaign mission, I have found that if I first load up the Multiplayer module, then exit from multiplayer (I don't need to join or host anything, just load it and then exit) and THEN load the normal single player module, that I don't get the error when loading a new mission.

 

Not sure why that second option works, but it does for me, every time.

 

Madmatt

[slug88]

I too have encountered this problem pretty frequently under Windows 7.

 

For me, I have found two reliable ways to get around this problem.

 

The first option, if you want to only play a stand-alone mission and don't need to read the briefing, is to use the excellent DCS Max program and automatically load up into the mission.

 

If I need to read a briefing, or need to play a campaign mission, I have found that if I first load up the Multiplayer module, then exit from multiplayer (I don't need to join or host anything, just load it and then exit) and THEN load the normal single player module, that I don't get the error when loading a new mission.

 

Not sure why that second option works, but it does for me, every time.

 

Madmatt

 

Sorry for the offtopic, but I just wanted to express how awesome it is to see a post from a developer of my favorite game on the forum for my other favorite game :D.

[Raz_Specter]

Thanks for the info guys, I will look into it a little further and perform some tests.

 

with regards to someone saying a low end system this is my setup

 

Striker Extreme M/B

4Gig of ram

intel 9850 Quad Core CPU

2 x 8800 GTX 768MB NVidia Cards (running in SLI only when i dont want the ABRIS and SCHAVAL on the second display)

 

I dont believe this is a low end system to be honest :)

 

With regards the the first reply. I am quite a compitent user of windows although I normally use Unix / Linux / Solaris. Without people testing games and stuff on new operating systems how can the developers cater for the release of a new op without more time spent on internal testing. The more people that can help out and possibly find errors so that they can try and fix them the better IMHO.

 

Anyways thanks again for the replies :)

 

Thanks Mithandra

[Madmatt_BFC]

Looks like I was mistaken slightly in my post above. I just had the problem again with the single player mode giving me that 000142 launch error again. This time, in order to get it to work, I did have to actually load a mission in Multiplayer mode first and then exit.

 

I had thought that simply bringing up the MP UI would be enough, but apparently not.

 

Oh well, at least I was able to get in to continue with my campaign.

 

Oh, and thanks for the nice words slug88. Anyone that knows me, knows that I love good games no matter who makes them and have long tried to promote computer gaming and the smaller development houses whenever I can.

 

Madmatt

[Topo]

Sorry for the offtopic, but I just wanted to express how awesome it is to see a post from a developer of my favorite game on the forum for my other favorite game :D.

 

Agree, Hi Madmatt!

[Lav69]

^^ as soon as i can afford vista 64.

 

You do know you can get the OEM version relatively cheap.

 

http://www.newegg.com/Product/Product.aspx?Item=N82E16832116488