maximus92 Posted March 30, 2010 Report Share Posted March 30, 2010 Hey Pete, I trust you're doing well. I'm having a problem running RC4 over WideFS. I'm using a switch to run a single keyboard, mouse, and monitor between two computers. I can start up the WideClient and get a connection, then I start RC4 and it connects fine. However, when I switch to the PC running FSX, which I do by tapping the "Scroll Lock" key twice, the WideClient crashes, with the below error log. I'm guessing that the WideClient doesn't like it when you use a switch. If I stay on the Client PC it doesn't crash, only when I switch. ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 30/03/10, Time 12:55:01.720: Client name is SECONDARY-PC 453 Attempting to connect now 1078 Server = GAMING-PC 1110 Trying TCP/IP host "GAMING-PC" port 8002 ... 1110Okay, IP Address = 192.168.1.46 1110 Connection made okay! 1188 Connection closed by server! 1188 Attempting to connect now 1188 Trying to locate server: Need details from Server Broadcast 6156 Server = GAMING-PC 6156 Trying TCP/IP host "GAMING-PC" port 8002 ... 6156Okay, IP Address = 192.168.1.46 6172 Connection made okay! 37406 New Client Application: "rcv4" (Id=4684) 66860 ***ERROR C0000005 at 6FC13F1D WinMain(0x00400000, 0x00000000, 0x00000000) 66860 *** Access violation trying to read address 00000004 66860 *** EAX 00000000 EBX 00000004 ECX 0023E708 EDX 00000001 EDI 00000000 ESI 00000001 66860 *** EIP 6FC13F1D EBP 00120918 ESP 0012090C 66860 ********** Modules List *********** 66860 00400000-00ACC000 WideClient.exe 66860 6FC00000-6FC25000 DINPUT.DLL 66860 70E10000-70E16000 rasadhlp.dll 66860 70EF0000-70F02000 pnrpnsp.dll 66860 70F10000-70F20000 napinsp.dll 66860 70F20000-70F28000 winrnr.dll 66860 71890000-718C8000 fwpuclnt.dll 66860 71A20000-71A27000 WINNSI.DLL 66860 71A30000-71A4C000 IPHLPAPI.DLL 66860 73710000-73720000 NLAapi.dll 66860 73970000-739A2000 WINMM.dll 66860 73F70000-73F83000 dwmapi.dll 66860 73FD0000-73FD9000 HID.DLL 66860 742A0000-742E0000 uxtheme.dll 66860 74880000-748A1000 ntmarta.dll 66860 74940000-74945000 wshtcpip.dll 66860 74CB0000-74CF4000 DNSAPI.dll 66860 74DF0000-74E2C000 mswsock.dll 66860 75300000-7530C000 CRYPTBASE.dll 66860 75420000-7542C000 MSASN1.dll 66860 75430000-7547A000 KERNELBASE.dll 66860 75510000-7553D000 WINTRUST.dll 66860 75540000-75552000 DEVOBJ.dll 66860 75560000-7567C000 CRYPT32.dll 66860 75680000-756A7000 CFGMGR32.dll 66860 759A0000-75A3D000 USP10.dll 66860 75AA0000-75B74000 kernel32.dll 66860 75B80000-75C2C000 msvcrt.dll 66860 769B0000-76B4D000 SETUPAPI.DLL 66860 76B50000-76B85000 WS2_32.dll 66860 76D60000-76D79000 sechost.dll 66860 76D80000-76EDC000 ole32.dll 66860 76EE0000-76F25000 WLDAP32.dll 66860 76F30000-76FBF000 OLEAUT32.dll 66860 76FC0000-77089000 USER32.dll 66860 77090000-770DE000 GDI32.dll 66860 770E0000-77181000 RPCRT4.dll 66860 77190000-7725C000 MSCTF.dll 66860 77260000-7739C000 ntdll.dll 66860 773A0000-773AA000 LPK.dll 66860 773C0000-773C6000 NSI.dll 66860 773D0000-773EF000 IMM32.DLL 66860 773F0000-77490000 ADVAPI32.dll 66860 *********************************** 66860 EIP 6FC13F1D is in DINPUT.DLL, Base=6FC00000 66860 Stack EBP 00120918->6FC13FD9, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 00120928->6FC1756C, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 00120944->6FC12D50, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 00120BC4->6FC0F2A5, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 00120BDC->6FC19245, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 0012133C->6FC15B74, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 00121994->6FC15C0C, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 001219C8->6FC13AC4, which is DINPUT.DLL (Base=6FC00000) 66860 Stack EBP 001219EC->73981AD6, which is WINMM.dll (Base=73970000) 66860 Stack EBP 0012286C->739826BD, which is WINMM.dll (Base=73970000) 66860 Stack EBP 001228EC->00401167, which is WideClient.exe (Base=00400000) 66860 Stack EBP 00122954->00000000, which is (BAD) (Base=00000000) 329688 Connection closed by server! 329688 Attempting to connect now Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 30, 2010 Report Share Posted March 30, 2010 I'm guessing that the WideClient doesn't like it when you use a switch. If I stay on the Client PC it doesn't crash, only when I switch. Don't know how that could be -- it wouldn't know how to detect it. Could you try it with this version please: http://fsuipc.simflight.com/beta/WideClient6797.zip This is the one I am using and I can use the Log details to narrow it down a bit then. Unfortunately I've only tomorrow left before I take a week's holiday. I might not solve it before then. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 30, 2010 Report Share Posted March 30, 2010 One more thing, as well as trying that later version, please let me see your WideClient.INI file. One interesting thing is that the crash occurs in Windows' DirectInput module: [/code] 66860 ***ERROR C0000005 at 6FC13F1D WinMain(0x00400000, 0x00000000, 0x00000000) ... 66860 6FC00000-6FC25000 DINPUT.DLL 66860 EIP 6FC13F1D is in DINPUT.DLL, Base=6FC00000 ... 66860 Stack EBP 00120918->6FC13FD9, which is DINPUT.DLL (Base=6FC00000) ... 66860 Stack EBP 001228EC->00401167, which is WideClient.exe (Base=00400000) [/code] I suspect that address in WideClient isn't far off where it would be in the later version, as it is very near the beginning of the code module. It looks like it is in the Button scanning routine, within the call to Windows "joyGetPosEx", used to get details of button states. If this is the case it might be simply that the DirectInput routines in Windows don't take kindly to a HID (Human Interface Device -- keyboards and mice as well as joysticks fall into DirectInput's lap) disappearing whilst being looked at. Most KVM switches I know of maintain some correct signals or voltage levels or whatever it takes in order to make sure that the device doesn't look like it has actually disappeared suddenly. Does yours? Is it connecting to USB or to older type PS/2 sockets? If not the latter it might be a good idea to try connecting to the old round sockets (via adapters) if your Client PC has them. Alternatively you could turn Button Scanning off on the Client -- put "ButtonScanInterval=0" into the [Config] section of the WideClient.INI file. Regards Pete Link to comment Share on other sites More sharing options...
maximus92 Posted March 30, 2010 Author Report Share Posted March 30, 2010 Here's the WideClient.ini file as it stands now. Going to try your version of the WideClient now, will post results in a few. [Config] ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port=8002 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=255,110,601,493 Link to comment Share on other sites More sharing options...
maximus92 Posted March 31, 2010 Author Report Share Posted March 31, 2010 Well, a new problem cropped up. I tried reinstalling, restarting the computer all to no avail. I have to get ready for work tonight (work the midnight shift.) Hopefully I can sort this all out tomorrow morning before I go to bed. Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 31, 2010 Report Share Posted March 31, 2010 Well, a new problem cropped up. You've not changed FSUIPC, only WideClient? If so, it cannot make a difference on the FSX PC -- there's no contact made till it's "ready to fly". I tried reinstalling, restarting the computer all to no avail. Reinstalling what? Replacing FSUIPC4.DLL with an identical FSUIPC4.DLL won't make any difference. It looks like a clash between two modules being loaded simultaneously by SimConnect. That's the only time I've seen that. Check to see if there's any log fragment produced -- I don't think there will be. If you want to try the latest FSUIPC4 there's a 4.604 available in the Updates Announcement. Regards Pete Link to comment Share on other sites More sharing options...
maximus92 Posted March 31, 2010 Author Report Share Posted March 31, 2010 Just WideClient. Sorry, reinstalling FSUIPC. Usually a first step for me, as that's the first thing every tech asks me if I've done...I should know, I'm one of those techs, eliminate the obvious. Anyhow, not much I can do at work, so I'll post the log when I get home. Link to comment Share on other sites More sharing options...
maximus92 Posted March 31, 2010 Author Report Share Posted March 31, 2010 Alright, FSX started up normally this morning, so I suspect it had something to do with REX running on the other machine through Sim Connect. Anyhow, the WideClient version you gave me still crashed, below is the log file. Next I will attempt the setting you gave me for the ini file. ********* WideClient Log [version 6.796] Class=FS98MAIN ********* Date (dmy): 31/03/10, Time 07:53:20.018: Client name is SECONDARY-PC 438 Attempting to connect now 1016 Server = GAMING-PC 1063 Trying TCP/IP host "GAMING-PC" port 8002 ... 1063Okay, IP Address = 192.168.1.46 1188 Connection made okay! 59594 New Client Application: "rcv4" (Id=320) 86672 ***ERROR C0000005 at 6FC13F1D WinMain(0x00400000, 0x00000000, 0x00000000) 86672 *** Access violation trying to read address 00000004 86672 *** EAX 00000000 EBX 00000004 ECX 0024E6F0 EDX 00000001 EDI 00000000 ESI 00000001 86672 *** EIP 6FC13F1D EBP 0012CC04 ESP 0012CBF8 86688 ********** Modules List *********** 86688 00400000-00AD0000 WideClient.exe 86688 6FC00000-6FC25000 DINPUT.DLL 86688 70E10000-70E16000 rasadhlp.dll 86688 70EF0000-70F02000 pnrpnsp.dll 86688 70F10000-70F20000 napinsp.dll 86688 70F20000-70F28000 winrnr.dll 86688 71890000-718C8000 fwpuclnt.dll 86688 71A20000-71A27000 WINNSI.DLL 86688 71A30000-71A4C000 IPHLPAPI.DLL 86688 73710000-73720000 NLAapi.dll 86688 73970000-739A2000 WINMM.dll 86688 73F70000-73F83000 dwmapi.dll 86688 73FD0000-73FD9000 HID.DLL 86688 742A0000-742E0000 uxtheme.dll 86688 74880000-748A1000 ntmarta.dll 86688 74940000-74945000 wshtcpip.dll 86688 74CB0000-74CF4000 DNSAPI.dll 86688 74DF0000-74E2C000 mswsock.dll 86688 75300000-7530C000 CRYPTBASE.dll 86688 75420000-7542C000 MSASN1.dll 86688 75430000-7547A000 KERNELBASE.dll 86688 75510000-7553D000 WINTRUST.dll 86688 75540000-75552000 DEVOBJ.dll 86688 75560000-7567C000 CRYPT32.dll 86688 75680000-756A7000 CFGMGR32.dll 86688 759A0000-75A3D000 USP10.dll 86688 75AA0000-75B74000 kernel32.dll 86688 75B80000-75C2C000 msvcrt.dll 86688 769B0000-76B4D000 SETUPAPI.DLL 86688 76B50000-76B85000 WS2_32.dll 86688 76D60000-76D79000 sechost.dll 86688 76D80000-76EDC000 ole32.dll 86688 76EE0000-76F25000 WLDAP32.dll 86688 76F30000-76FBF000 OLEAUT32.dll 86688 76FC0000-77089000 USER32.dll 86688 77090000-770DE000 GDI32.dll 86688 770E0000-77181000 RPCRT4.dll 86688 77190000-7725C000 MSCTF.dll 86688 77260000-7739C000 ntdll.dll 86688 773A0000-773AA000 LPK.dll 86688 773C0000-773C6000 NSI.dll 86688 773D0000-773EF000 IMM32.DLL 86688 773F0000-77490000 ADVAPI32.dll 86688 *********************************** 86688 EIP 6FC13F1D is in DINPUT.DLL, Base=6FC00000 86688 Stack EBP 0012CC04->6FC13FD9, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012CC14->6FC1756C, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012CC30->6FC12D50, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012CEB0->6FC0F2A5, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012CEC8->6FC19245, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012D628->6FC15B74, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012DC80->6FC15C0C, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012DCB4->6FC13AC4, which is DINPUT.DLL (Base=6FC00000) 86688 Stack EBP 0012DCD8->73981AD6, which is WINMM.dll (Base=73970000) 86688 Stack EBP 0012EB58->739826BD, which is WINMM.dll (Base=73970000) 86688 Stack EBP 0012EBD8->00401167, which is WideClient.exe (Base=00400000) 86688 Stack EBP 0012EC40->0012EC60, which is (Base=00000000) 86688 Stack EBP 0040C3F8->000EBBE9, which is (BAD) (Base=00000000) 161484 Connection closed by server! 161484 Attempting to connect now Link to comment Share on other sites More sharing options...
maximus92 Posted March 31, 2010 Author Report Share Posted March 31, 2010 It would appear that setting the "ButtonScanInterval" to zero did the trick. Thanks for your help. If I have any more problems related to this, I'll post here. Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 31, 2010 Report Share Posted March 31, 2010 Alright, FSX started up normally this morning, so I suspect it had something to do with REX running on the other machine through Sim Connect. Anyhow, the WideClient version you gave me still crashed, below is the log file. Yes, from your last log I did expect this version to crash also. I'm afraid it isn't something I can fix -- it is definitely in DirectInput, as I said. Looks like your KVM switch doesn't treat the connections very nicely and Microsoft's code objects. All you could possibly try, apart from the work-around I gave you, is updating the DirectX on that PC. Maybe it was a bug and is fixed now. It would appear that setting the "ButtonScanInterval" to zero did the trick. Yes, thought it would. It simply stops WideClient scanning joysticks in order to send buttons to FSUIPC. That's an okay solution providing you don't want to connect anything on that PC. Regards Pete Link to comment Share on other sites More sharing options...
maximus92 Posted March 31, 2010 Author Report Share Posted March 31, 2010 All my controls are plugged into the FSX machine, and that probably won't change, so this work around suits me just fine. Enjoy your holiday. 8) Link to comment Share on other sites More sharing options...
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