rik, psishead and others, this problem persists and is the toughest bug I've ever encountered.

I appologize for picking up this thread again some 7 months later. I still have not solved my getrawinputdeviceinflow error message described above. Here is the current status of the unsolved problem:

Both the game (Realflight Simulator) and Dxdiag.exe produce the same error message when run. "The device entry point getrawinputdeviceinflow could not be located in the dynamic library user32.dll." I would like to first eliminate this error message when running dxdiag.exe (and then see in the game will run ok). I believe that if dxdiag would do a complete run with no error messages, the game will run fine. The game developers said they did not believe the problem was with the game.

When I examine the input tab, after running dixdiag.exe, there are two listed problems from dxdiag.exe. I then save the detailed text. A registry key is described as missing. And dxdiag.exe says that no input devices were found, eventhough the game controller box is plugged into a USB port, and a light on the controller box is flashing, suggesting it is ready.

Here are the things I've tried so far to fix the bug:

1) I tried once again replacing d3d8thk.dll with a techzone downloaded version called d3d8thk.w2k, and renaming it. That did not work.

2) Tried re-installing Direct-X 9.0c. No luck, error message the same.

3) Downloaded the Direct X update posted above by phishead, and installed it, no luck.

4) Checked the event viewer, and nothing is listed when dxdiag.exe displays the error message.

5) Have not re-installed the last service pack for Win2k pro, because System Summary shows that I have Service Pack 4 build 2195 already installed, and a scannow was run to be sure all dlls are OK as described above. Did try to do this, but got a message saying that the service pack was already installed, and the MS version would not re-install. However, this is still an option, but am a bit reluctant to do it because all security patches will have to be reinstalled, perhaps a hundred. If you can think of any less invasive fixes to try before this service pack re-install, would prefer to do them first.

6) One thing I can think of, is to manually insert the registry key that is described as missing. Would like to have your input on how to do this before I try it; I have edited registry entries before, but never have inserted a complete key. Here is the key that dxdiag says is missing:

'HKCR\CLSID\{25E609E4-B259-11CF-BFC7-4445535400000}InProcServer32'

7) If you have another other ideas to try, will work with you. Was busy when we last worked together on this, but now have the time to keep going.

Thanks for your patience and support.

Peter
Nederland, Colorado