oskrypuch

Will try various values to the InitDelay value, and report back. The thought of trying older versions, was just an attempt to perhaps isolate what changes if any, are leading to the conflict. Also, someone else just posted on the RXP forums, they have RXP 530 and .751a, and are NOT noticing a problem. So, there is some other necessary condition. I've asked him details about his system and will post back when I hear. Thanks much for your efforts on this. * Orest

I didn't want to post extraneous stuff, so edited the file, looks like I just confused things instead! ;) Here is the full (current) file, after the last .751a installer run ... <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> -<Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>Level-D Simulations</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\LVLD.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>VistaMare Core</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\FlightSimulatorX\VistaMare\ViMaCoreX.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FeelThere EJetX Helper</Name> <Disabled>False</Disabled> <Path>FeelThere\E170\EJetH.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FeelThere LegacyX HUD</Name> <Disabled>False</Disabled> <Path>FeelThere\Legacy\LegacyXHUD.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FS Recorder</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\FSXaddons\FSRecorderFSX\FSRecorder_FSX.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FSCopilot</Name> <Disabled>False</Disabled> <Path>Modules\FSCopilot.dll</Path> </Launch.Addon> </SimBase.Document> * Orest

Here is another fellow with the identical problem, only with the latest version of FSUIPC. http://www.simforums.com/forums/gns-530-wont-load-with-new-fsuipc4_topic40873.html * Orest

OK, uninstalled the Reality XP 430W for FSX. Then with FSUIPC 4.751a reinstalled, FSX will startup and run fine. So, bottom line, the latest version of FSUIPC and the RXP 430W are incompatible. I will also drop them a line. I did update the RXP 430W to the latest version, no difference. * Orest

FSUIPC is the first item, but the second listed entry, just semantics. File was not edited. I posted it just for your possible reference. Well, I expect it is some sort of conflict in the dlls, obviously files don't disappear by themselves. As the filename suggests it may relate to the RXP modules, will try a note there as well. It might be interesting to note if anyone else with the RXP 430Ws has this same issue. It could well be even something else. As it only seems to occur with the latest FSUIPC version, it may be something yet to be discovered. At least I have 100% the sequence that triggers the fault. Is there access to some of the older FSUIPC build's DLL, that is newer than 70b, but older than 751a? BTW, thanks for your help thus far. * Orest

FSUIPC is #2 in the dll.xml .. <?xml version="1.0" encoding="windows-1252" ?> - <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> - <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon>

Here is the FSUIPC.LOG file from the "errant start" with 751a ... ********* FSUIPC4, Version 4.751a by Pete Dowson ********* User Name="Orest Skrypuch" User Addr="xxxxxxxxxx@xxxxxxx.com" (masked) FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows 7 Module base=61000000 718 System time = 17/12/2011 16:46:30 718 FLT UNC path = "\\CAMERA-4\C\Users\ows\Documents\Flight Simulator X Files\" 764 Trying to connect to SimConnect Acc/SP2 Oct07 ... 764 FS UNC path = "\\CAMERA-4\D\FlightSimulatorX\" 1638 LogOptions=00000000 00000001 1638 Wind smoothing fix is fully installed 1638 G3D.DLL fix attempt installed ok 1638 SimConnect_Open succeeded: waiting to check version okay 1638 Trying to use SimConnect Acc/SP2 Oct07

OK, not an installer problem, something else to sort .... First started up FSX with the (old) restored setup, all is OK. Then downloaded the separate .751a FSUIPC.DLL file from the downloads area here. Manually copied the 751a DLL into the modules directory, temporarily replacing the 70b contained there. On then starting up FSX again, get the following dialog ... RXPG1AE.EXE - system error The program can't start because cdp_annun_box_sim.dll is missing from your computer. Try reinstalling the program to fix this problem. And the startup of FSX halts with the twirling mouse icon. Shut it down with CAD tasklist, and then manually restored the older 70b DLL, it now starts up fine. 100% repeatable. There is obviously some sort of interaction in my setup, perhaps with my RXP stuff, but that may be a false lead. * Orest

My intention was to start from a restored disk image with the older FSUIPC installed, and then just replace the DLL alone, the way I have normally updated all these years. Just trying to ferret out where my problem occurs. It seems pretty definitely something unique in my setup. * Orest

Perfect, I see the ZIP with all the files. Will grab that, and let you know what I find. * Orest

The installer prompts for a "re-registration", that can be ignored, or maybe that is part of the problem somehow. When I respond to register both FSUIPC and widefs, it seems to proceed as normal. The previous/current version would be 4.6x. Sorry, I meant the DLL to drop into the modules folder. I will grab the discrete update file and drop that in, and let you know what I find. Are the rest of the doc files available in a ZIP as well? I do like to read through everything. There may be something farkled in my setup, triggering this, or it may be some odd Win7 interaction. Don't know. If no one else is reporting any trouble, then that is likely the case. * Orest

[Edit: not a FSUIPC "installer" issue, appears to be related to having an install of RXP modules together with this latest version FSIUPC] Grabbed what appeared to be the latest FSUIPC version (4.751). Once installed (and re-registered), the problem generated is a message on FSX startup indicating a DLL (belonging to RXP GPS) is missing, dismissing that message leaves the FSX splash screen up, with the mouse circle twirling, and that is it. I expect the message is misleading in a sense, and just suggests that some setup file may have been munged. I restored from a backup before the FSUIPC install, all is OK. I didn't realize it was the FSUIPC install at this point, and reinstalled, and bingo exactly that same problem. There doesn't appear to be available just the .EXE to drop in the modules folder. Win7 64bit, yes the installer was run "as administrator", and UAC is turned off. Anyone see this? * Orest