Jump to content
The simFlight Network Forums

CDreier

Members
  • Posts

    25
  • Joined

  • Last visited

  • Days Won

    1

CDreier last won the day on March 20 2015

CDreier had the most liked content!

About CDreier

  • Birthday July 1

Profile Information

  • Gender
    Male
  • Location
    Southeast USA

CDreier's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. I'm doing an entirely new FSX install on a newly built computer. I'll be using the registered version of FSUIPC for FSX. In order to run Squawkbox on a second, networked, computer, do I run it through WideFS as I did with FS9? Thanks.
  2. I'm sorry, I thought the version was in the topic's title. It is 3.999z2 for FS9. Again, it has installed correctly after I approved the exception. I just wanted to give you a heads up so that, hopefully, someone else will see your reply in case they also have this happen. I can send you the av log if you need it for some reason. Thanks.
  3. Pete, My NAV fully blocked the installation though I'm not surprised. I added this version to my "exceptions" even though it showed a very high alert. Just to be sure, are we okay here? And will there be a further version that won't produce the alarm (I don't like having exceptions lurking about. :???: ) ? Thanks.
  4. Pete, Thanks for the quick reply. I updated to 3.999z and, strangely enough, the flashing "Differential Brakes" disappeared and everything is working fine. I'm somewhat baffled because I see no command for Differential Braking anywhere. Oh well???? Thanks again sir.
  5. FSUIPC registered version 3.999, CH Flight Sim Yoke, FS9. I'm attempting to assign the brake command (key press .) to my yoke button #1. My config is: Control sent when button pressed is "Brakes", Parameter 0, Control Repeat. But what I am seeing is the message "Differential Brakes" then some flashing before Brakes appears on the lower left of the screen. The function isn't smooth. I read in another topic that I may want to set Control sent when button released to also show "Brakes" but that doesn't seem to eliminate the flashing Differential Brakes and the application isn't smooth. Thoughts? And... thanks.........
  6. Pete, yet another problem. FSUIPC 3.93 is on the server with FS9. The laptop has WideClient, is connecting and running Squawkbox4. Everything is great - I can change frequencies, squawk code, etc in FS9 and have it appear in Squawkbox - but I can't get the button on my CH Yoke (button "0") programmed to work with SB4. I want to press the button to transmit in Squawkbox. I've read the manual as it relates to 'Integration With Other Products, page 1, and it appears that the button is set up properly following the illustration to set PTT Transmit On and OFF - but obviously it isn't correct. Nothing is happening with that button. Help please. Here's a log: ********* FSUIPC, Version 3.93 by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "F:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.DLL" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Chuck Dreier" User Addr="chucknsc@mindspring.com" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=40003605[40003605] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 422 System time = 25/11/2009 15:08:50 422 \\CORSAIR\Flight Simulator 9\ 422 System time = 25/11/2009 15:08:50, FS2004 time = 12:00:00 (00:00Z) 890 \\CORSAIR\Users\Chuck\Documents\Flight Simulator Files\Default.flt 905 AIRCRAFT\c172\Cessna172SP.air 905 Aircraft="Cessna Skyhawk 172SP" 67128 \\CORSAIR\Users\Chuck\Documents\Flight Simulator Files\Atlanta Default.flt 67346 Clear All Weather requested: external weather discarded 68282 Advanced Weather Interface Enabled 73149 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4 73149 .. Key not programmed -- passed on to FS 73227 KEYUP: VK=18, Waiting=0 76940 *** Entered Buttons option page *** 80341 FirstButtonChange res=00000000 (0.0, 0) 89264 *** Exiting Buttons option page *** 89264 WeatherOptions set, now 40003605 (timer=0) 109997 Button changed: bRef=0, Joy=0, Btn=0, Pressed 109997 [buttons] 1=P0,0,C1001,0 109997 FSUIPC Control Action: Ctrl=1001, Param=0 110465 Button changed: bRef=0, Joy=0, Btn=0, Released 110465 [buttons] 3=U0,0,C1002,0 110465 FSUIPC Control Action: Ctrl=1002, Param=0 110964 Button changed: bRef=0, Joy=0, Btn=0, Pressed 110964 [buttons] 1=P0,0,C1001,0 110964 FSUIPC Control Action: Ctrl=1001, Param=0 111245 Button changed: bRef=0, Joy=0, Btn=0, Released 111245 [buttons] 3=U0,0,C1002,0 111245 FSUIPC Control Action: Ctrl=1002, Param=0 111401 Button changed: bRef=0, Joy=0, Btn=0, Pressed 111401 [buttons] 1=P0,0,C1001,0 111401 FSUIPC Control Action: Ctrl=1001, Param=0 111526 Button changed: bRef=0, Joy=0, Btn=0, Released 111526 [buttons] 3=U0,0,C1002,0 111526 FSUIPC Control Action: Ctrl=1002, Param=0 111572 Button changed: bRef=0, Joy=0, Btn=0, Pressed 111572 [buttons] 1=P0,0,C1001,0 111572 FSUIPC Control Action: Ctrl=1001, Param=0 111697 Button changed: bRef=0, Joy=0, Btn=0, Released 111697 [buttons] 3=U0,0,C1002,0 111697 FSUIPC Control Action: Ctrl=1002, Param=0 111806 Button changed: bRef=0, Joy=0, Btn=0, Pressed 111806 [buttons] 1=P0,0,C1001,0 111806 FSUIPC Control Action: Ctrl=1001, Param=0 111947 Button changed: bRef=0, Joy=0, Btn=0, Released 111947 [buttons] 3=U0,0,C1002,0 111947 FSUIPC Control Action: Ctrl=1002, Param=0 112415 Button changed: bRef=0, Joy=0, Btn=0, Pressed 112415 [buttons] 1=P0,0,C1001,0 112415 FSUIPC Control Action: Ctrl=1001, Param=0 112555 Button changed: bRef=0, Joy=0, Btn=0, Released 112555 [buttons] 3=U0,0,C1002,0 112555 FSUIPC Control Action: Ctrl=1002, Param=0 112618 Button changed: bRef=0, Joy=0, Btn=0, Pressed 112618 [buttons] 1=P0,0,C1001,0 112618 FSUIPC Control Action: Ctrl=1001, Param=0 112727 Button changed: bRef=0, Joy=0, Btn=0, Released 112727 [buttons] 3=U0,0,C1002,0 112727 FSUIPC Control Action: Ctrl=1002, Param=0 112774 Button changed: bRef=0, Joy=0, Btn=0, Pressed 112774 [buttons] 1=P0,0,C1001,0 112774 FSUIPC Control Action: Ctrl=1001, Param=0 112867 Button changed: bRef=0, Joy=0, Btn=0, Released 112867 [buttons] 3=U0,0,C1002,0 112867 FSUIPC Control Action: Ctrl=1002, Param=0 112914 Button changed: bRef=0, Joy=0, Btn=0, Pressed 112914 [buttons] 1=P0,0,C1001,0 112914 FSUIPC Control Action: Ctrl=1001, Param=0 113054 Button changed: bRef=0, Joy=0, Btn=0, Released 113054 [buttons] 3=U0,0,C1002,0 113054 FSUIPC Control Action: Ctrl=1002, Param=0 113335 Button changed: bRef=0, Joy=0, Btn=0, Pressed 113335 [buttons] 1=P0,0,C1001,0 113335 FSUIPC Control Action: Ctrl=1001, Param=0 113476 Button changed: bRef=0, Joy=0, Btn=0, Released 113476 [buttons] 3=U0,0,C1002,0 113476 FSUIPC Control Action: Ctrl=1002, Param=0 113569 Button changed: bRef=0, Joy=0, Btn=0, Pressed 113569 [buttons] 1=P0,0,C1001,0 113569 FSUIPC Control Action: Ctrl=1001, Param=0 113678 Button changed: bRef=0, Joy=0, Btn=0, Released 113678 [buttons] 3=U0,0,C1002,0 113678 FSUIPC Control Action: Ctrl=1002, Param=0 113772 Button changed: bRef=0, Joy=0, Btn=0, Pressed 113772 [buttons] 1=P0,0,C1001,0 113772 FSUIPC Control Action: Ctrl=1001, Param=0 113834 Button changed: bRef=0, Joy=0, Btn=0, Released 113834 [buttons] 3=U0,0,C1002,0 113834 FSUIPC Control Action: Ctrl=1002, Param=0 113928 Button changed: bRef=0, Joy=0, Btn=0, Pressed 113928 [buttons] 1=P0,0,C1001,0 113928 FSUIPC Control Action: Ctrl=1001, Param=0 114022 Button changed: bRef=0, Joy=0, Btn=0, Released 114022 [buttons] 3=U0,0,C1002,0 114022 FSUIPC Control Action: Ctrl=1002, Param=0 114084 Button changed: bRef=0, Joy=0, Btn=0, Pressed 114084 [buttons] 1=P0,0,C1001,0 114084 FSUIPC Control Action: Ctrl=1001, Param=0 114178 Button changed: bRef=0, Joy=0, Btn=0, Released 114178 [buttons] 3=U0,0,C1002,0 114178 FSUIPC Control Action: Ctrl=1002, Param=0 124661 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 124661 .. Key not programmed -- passed on to FS 124848 KEYDOWN: VK=67, Waiting=0, Repeat=N, Shifts=2 124848 .. Key not programmed -- passed on to FS 129060 System time = 25/11/2009 15:10:58, FS2004 time = 12:53:54 (17:53Z) 129060 *** FSUIPC log file being closed Memory managed: 0 Allocs, 366 Freed ********* FSUIPC Log file closed ***********
  7. I got it working!!!! The workgroup names showed the same on one computer (the client) but on the server when I drilled down I found that the workgroup name for the server was different. I'm not sure why that was - but in any event, we're up and running. I want to really thank you for your help and patience in working with me on this. It's wonderful support and again, I can't thank you enough. Take care, Chuck :D
  8. Yes, I did read that section specifically. I agree that it now appears that it has to do with the network. However, on both computers the network information is identical showing both computers (Corsair and Acer) and the workgroup is identified as "Workgroup" and the location is "Dreier" Again they are identical on both. I am really lost here. Again, thank you for bearing with me on this.
  9. I did a reinstall and the x86 program files is where I'd placed my WideFS folder originally. I have just moved it to the C: root directory. Here is the wideclient.log - actually there are two - one has a 0 attached but this is the log without the 0: ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 10/11/09, Time 18:33:36.368: Client name is ACER 375 Attempting to connect now 1389 Trying to locate server: Need details from Server Broadcast 1389 Failed to connect: waiting to try again 3432 Attempting to connect now 19921 ****** End of session performance summary ****** 19921 Total time connected = 0 seconds 19921 Reception maximum: 0 frames/sec, 0 bytes/sec 19921 Transmission maximum: 0 frames/sec, 0 bytes/sec 19921 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 19921 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********
  10. There is not a wideclient.log in either the FSX\modules on the server computer or in the WideFs directory on the client machine. I'm at a loss.
  11. First off, thanks for helping me with this. It appears that WideClient is running. It is in its own folder on the client machine along with WideClient.ini. The .exe is 50kb and .ini is 1kb. When I enable it, Task Manager shows it's running as "WideClient FS98 Eliminator - Waiting for a connection" using 8020k of memory. Yet, there's no connection! Here's my install log: Installer for FSUIPC4.DLL version 4.53 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: AppPath="E:\Program Files\Microsoft Games\Flight Simulator X\" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Program Files\Microsoft Games\Flight Simulator X\Modules\FSUIPC4.DLL ... Version 4.530 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Program Files\Microsoft Games\Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Chuck\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Chuck\AppData\Roaming" Found FSX.CFG in "C:\Users\Chuck\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Chuck\Application Data\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Contacts\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Cookies\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Desktop\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Documents\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Downloads\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Favorites\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Links\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Local Settings\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Music\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\My Documents\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\NetHood\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Pictures\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\PrintHood\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Recent\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Saved Games\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Searches\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\SendTo\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Start Menu\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Templates\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Tracing\Roaming" No FSX.CFG there Looking in "C:\Users\Chuck\Videos\Roaming" No FSX.CFG there Now installing additional files into the Modules folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Example LUA plugins.zip" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix programno longer relevant =========================================================== All installer tasks completed okay! Registration for WideFS was successful! (result code 00) *************** End of Install Log ***************
  12. One other thing.... in checking my install log for FSUIPC it appears that it couldn't find my fsx.cfg. I can post the log if you like. Thank you.
  13. I can't get WideFS/FSX (FSUIPC) to communicate. Both computers are running Win7 64-bit. FSX runs on its own drive (E:) while fsx.cfg and most everything else is on the C: drive. Here's the WideServer log - there's no WideClient log: ********* WideServer.DLL Log [version 7.53] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 09/11/09, Time 14:31:02.487: Server name is CORSAIR 15975 Initialising TCP/IP server 15975 Initialising IPX/SPX server 15975 IPX/SPX socket() failed [Error=10044] Socket type not supported 15975 Failed to start IPX/SPX Server 15975 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs 32823 Closing down now ... Memory managed: Offset records: 13 alloc, 12 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed ********* Here's the WideFS.ini file: ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] ServerName=Corsair Protocol=TCP Port=8002 Window=43,44,886,589 Visible=Yes ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== There's just nothing happening and I can't figure it out. Help or ideas, please. Thanks.
  14. Not a problem. I know it's a lot of work and it is much appreciated - without FSUIPC and WideFS a great many of us would be lost. Thanks for your work and for the support of the products!! :)
  15. Pete, does this mean another purchase - for both FSUIPC and WideFS?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.