Windows 8 - Joystick Megathread problem.

[DerStig 4]

I think we have all established that this is due to a windows UPDATE not just windows 8. A lot of windows 7 (with up to date patches) users are also reporting the problem. I don't think this has anything to do with hardware or drivers, its entirely operating system API that is causing it and to be honest with everyone our best bet might be trying to find someone inside Microsoft who will relay the message to the right team to fix the actual problem. Posting to the microsoft connect forums will not get you anywhere other than their offshore team in india whereas our point needs to make it to their Seattle, WA offices:) Otherwise, I don't know what to tell you, but our only bet might be going back to Windows 7 pre December patches (not sure how that's even doable) and disable auto updates.

[Jude Bradley 659]

I tried the dll, it didnt do anything.

 

Did you register the file with regsvr32 command?

http://support.microsoft.com/kb/249873

[DerStig 4]

Tried that now as well, no difference. I could see the right dll being loaded by the process when I run dlllist so I know it loaded fine.

 

But then again, the problem is, this dll was from my windows 7 machine which has also been updated and most likely has the problem. I need a direct input binary from an older windows 7 build.

 

EDIT : Nevermind, the file is from 2009, i dont think it makes a difference.

[Zangoose 1,631]

So Windows 7 also has this problem when it's updated with the latest updates? How many users on Win 7 have noticed this issue then..

[Seelandpirat 0]

So far I've no problems (fingers crossed) with Windows 7 Ultimate 64 Bit, newest updates - hope it will stay like this - I have just "downgraded" from Windows 8 a few days ago...

[DerStig 4]

So far I've no problems (fingers crossed) with Windows 7 Ultimate 64 Bit, newest updates - hope it will stay like this - I have just "downgraded" from Windows 8 a few days ago...

 

If you have downgraded just a few days ago, you dont have the latest updates. The way windows updates work is quite complicated. But in a gist, if I were to install Windows 7 right now, the first build from 2 years ago, go to windows update and update my PC, if it installs 2 updates and then says your PC is up to date, that does not mean all updates are installed. It will take you several days/at least couple of weeks to get all the updates. When windows considers an update installed, it works with update "cycles". So you might be up to date in cycle 25 whereas the latest cycle in the world is 245. Does that make sense? So if there is an issue, you will most likely see it sometime this month.

[Jude Bradley 659]

I don't have the issue with Windows 7 (yet).

[Bob Scott 7,716]

I don't have the issue with Windows 7 (yet).

 

Nor do I. I have seen a very few people describe this, but not enough to conclude that this is now a widespread Win7 problem as well.

[Seelandpirat 0]

Then it might be a good idea to stop updating now?

[DerStig 4]

Then it might be a good idea to stop updating now?

 

Sure but thats risky too against hackers and viruses. Some of these updates are security updates.

[Seelandpirat 0]

Hm - ok - if i get this issue in windows 7 too, i'll quit flying and will start controlling....

[jjjallen 37]

Did some testing today and now I'm 99% sure that the loss of my stick is due to EZCA. Right before I lost my stick throttle I got this error in the application logs - Faulting application name: EZCA.exe, version: 1.1.7.0, time stamp: 0x2a425e19. I get this error multiple times during a flight but the last one seemed to kill the stick. I logged this on the EZCA SimForums site multiple times. I think that it has something to do with EZCA using DMA that Windows doesn't like. Cheers jja

[Seelandpirat 0]

I never had this EZDA-thing installed and had the problem too...

[jjjallen 37]

OK well that is interesting but I still believe that there is some kind of low-level interaction at the driver level that is causing the issue. With every Windows release there seems to be driver issues that take some time to iron out. Cheers jja

[Zangoose 1,631]

Did some testing today and now I'm 99% sure that the loss of my stick is due to EZCA. Right before I lost my stick throttle I got this error in the application logs - Faulting application name: EZCA.exe, version: 1.1.7.0, time stamp: 0x2a425e19. I get this error multiple times during a flight but the last one seemed to kill the stick. I logged this on the EZCA SimForums site multiple times. I think that it has something to do with EZCA using DMA that Windows doesn't like. Cheers jja

 

I don't have EZCA on this computer either so that can't be the problem.