Gerald Maritschnegg Posted August 11, 2005 Report Posted August 11, 2005 Dear Pete, after a new installation of my MCDU-PC (in a network of 4 PCs for my Cockpit using PM-Software) I re-installed the MCDU-Software as well as the newest WideFS (registered of course ;-). The MCDU itself - I mean stand alone without FS2004) is running well, but when I start FS2004 an error-box appears: The procedure-startpoint "GetRawInputDeviceList" in the module USER32.dll was not found. Now I am looking for days to find the problem (reinstallation of all modules), but the error-message appears still every time and after that the PC is frozen. Can you give me some hints to find a solution? Below you can see the text of the log-file. Best regards Gerald ********* WideClient Log [version 6.47] Class=FS98MAIN ********* Date (dmy): 11/08/05, Time 13:29:57.171: Client name is MCDU 328 Attempting to connect now 23265 Error on client pre-Connection Select() [Error=10060] Connection timed out 23265 Ready to try connection again 23297 Attempting to connect now 477547 New Client Application: "mcdu" (Id=572) 1296062 Connection made okay! 1332172 Timed out response: connection assumed lost!
Pete Dowson Posted August 11, 2005 Report Posted August 11, 2005 Dear Pete,after a new installation of my MCDU-PC (in a network of 4 PCs for my Cockpit using PM-Software) I re-installed the MCDU-Software as well as the newest WideFS (registered of course ;-). The MCDU itself - I mean stand alone without FS2004) is running well, but when I start FS2004 an error-box appears: The procedure-startpoint "GetRawInputDeviceList" in the module USER32.dll was not found. Now I am looking for days to find the problem (reinstallation of all modules), but the error-message appears still every time and after that the PC is frozen. Can you give me some hints to find a solution? Below you can see the text of the log-file. I don't use "GetRawInputDeviceList" -- I don't even know what it is. I don't really understand your report. "When you start FS2004 an error-box appears" -- where, on top of FS2004? Is FS2004 still running, or is it FS2004 which has crashed? If not FS2004, what program is the error box emanating from? This may be the first step -- identifying what is crashing and on which PC. I note you attached a fragment of a WideClient log file. Is that intended to be relevant? I'm finding it hard to understand what you are seeing. If it is the PM MCDU which is crashing you need to talk to PM support. BTW, I just checked, and the USER32.DLL module, at least the one from WinXP, most certainly does include a "GetRawInputDeviceList" procedure. If yours doesn't, then presumably either it is corrupted, or you are using a version of Windows which doesn't support it. Regards, Pete
Gerald Maritschnegg Posted August 11, 2005 Author Report Posted August 11, 2005 Hi Pete, thanks for your quick answer. FS2004 is running on my "Main-PC" and I have installed in my network another 3 PCs, one with "Glascockpit (PFD & ND)" for Captain, one for Glascockpit-F/O and one for the MCDU. The PM-Software is running well on the all other PCs connected by WideFS. But only on the MCDU-PC (Pentium 2400 with WIN2000) I am getting the message-box from WideFS (see attachment) when starting the FS2004 on the Main-PC. As you, I do not have any idea to understand this message. The question is, what can I do. Shall I reinstall the operating system? Best regards Gerald
Pete Dowson Posted August 12, 2005 Report Posted August 12, 2005 The PM-Software is running well on the all other PCs connected by WideFS. But only on the MCDU-PC (Pentium 2400 with WIN2000) I am getting the message-box from WideFS (see attachment) when starting the FS2004 on the Main-PC. Well, that USER32.DLL procedure isn't used by WideClient, nor is it called by anything WideClient calls (I've just used ProcExp to do a dependency check). It looks like something WideClient is running needs that procedure. Can you show me the WideClient.INI file from that PC please? What operating system are you running on the other PCs? I've checked the USER32.DLL in Win2000, and indeed it doesn't have a "GetRawInputDeviceList" procedure -- it looks like that is specific to WinXP (maybe also Win98/Me). Something is not compatible with Win2000 by the look of it. Let me see the WideClient.INI file first, please. Regards, Pete
Gerald Maritschnegg Posted August 12, 2005 Author Report Posted August 12, 2005 Dear Pete, attached you will find the requested WideClient.ini and the log-file of the MCDU-PC. On that PC I am working with WIN2000, on the Main-PC (FS2004 running) is installed WIN XP Home. Thanks again for your help. Best regards Gerald WideClient.exe: ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=32000,32000,112,27 UseTCPIP=Yes ServerIPAddr=192.168.2.2 Visible=min ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No UseTCPIP=Yes WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== ********* WideClient Log [version 6.47] Class=FS98MAIN ********* Date (dmy): 12/08/05, Time 03:48:37.078: Client name is MCDU 390 Attempting to connect now 23343 Error on client pre-Connection Select() [Error=10060] Connection timed out 23343 Ready to try connection again 23359 Attempting to connect now 152953 Connection made okay! 189109 Timed out response: connection assumed lost!
Pete Dowson Posted August 12, 2005 Report Posted August 12, 2005 Dear Pete, attached you will find the requested WideClient.ini Okay. You are not getting WideClient to run anything else, so that's not the problem. The only thing extra which WideClient will be doing when it connects to FS is to start scanning Buttons, in case you want to send button presses to FSUIPC for programming. It does this two ways. For normal Windows-connected joysticks it simply calls the standard Windows API "joyGetPosEx". That is supported in all versions of Windows and most certainly Win2000 as well. The only possible thing I can think of which might go wrong is if there's a joystick installed with a driver which is not Win2000 compatible -- though how you'd get it installed would be somewhat of a mystery. You could try checking for joysticks using the Control Panel "Game Controllers" facility (or whatever it is called on Win2000). The other thing it runs, if it can find it, is a module called "GFdev.DLL", which is the GoFlight device access library. Now I've checked that here and it, too, most definitely does not use "GetRawDeviceList" -- and in fact it works fine on Win2000 as well as WinXP. However, maybe another module by the same name is being picked up. Is this possible? Can you search your Windows folder for a GFDev.DLL (you will have to change folder options to unhide system files and show full names). I really cannot think of anything else that could be happening. If neither of the above yields any results for you I can try supplying a modified version of WideClient with a new parameter to set to make it bypass all the button-checking options. But could you also edit the WideClient.INI file and set "Log=DebugAll" in the [user] section, and let me see the log. (If it is too big, Zip it and send it to petedowson@btconnect.com). Regards, Pete
Gerald Maritschnegg Posted August 12, 2005 Author Report Posted August 12, 2005 Dear Pete, thanks again for your support. I will use all your mentioned recommendations and send the rewuisted Log-file. But me be tomorrow, because now I have to do different tasks. Thanks and best regards Gerald
Gerald Maritschnegg Posted August 14, 2005 Author Report Posted August 14, 2005 Dear Pete, the last recommendation to check the joystick-configuration was a good one (even I didn't connect any joystick to this PC), because in contrast with the other PCs I realized, that no "Game Controller"-folder is available on my system. This could be the reason for the error-message, am I right? Please don't ask me why this folder is missing !?! I am not an operation system expert, so I have to discuss this item with my PC-dealer, but he is on holidays the next weeks. Best regards Gerald
Pete Dowson Posted August 14, 2005 Report Posted August 14, 2005 Dear Pete, the last recommendation to check the joystick-configuration was a good one (even I didn't connect any joystick to this PC), because in contrast with the other PCs I realized, that no "Game Controller"-folder is available on my system. This could be the reason for the error-message, am I right? Please don't ask me why this folder is missing I'll look on my Win2000 installation. It may not be called that anyway -- it wasn't called that in earlier versions of Windows in any case. [LATER] In my Win2000 Pro installation the joystick settings are in Settings-Control Panel-Gaming Options. Please try changing the ButtonScanInterval=20 parameter to ButtonScanInterval=0 in the [Config] section of the WideClient.ini file. That will stop Wideclient looking at any buttons, whether Windows or GoFlight. Regards, Pete
Gerald Maritschnegg Posted August 15, 2005 Author Report Posted August 15, 2005 Dear Pete, I thank you very much for this configuration-hint. Now the error-message does not appaer any more :-)). Best regards Gerald
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now