RESOLVED FTX Central doesn't work [after manually moving FSX install]

[Sundog]

...and it's completely my fault. Orbx installs outgrew my original install on my original EHD, so I bought a new larger EHD and copied and moved FSX over, but I renamed the drives so the path name still remained the same. Of course, this screwed up all of my shortcuts. I ran the FSX registry shortcut fix, however, my FTX shortcut still goes to the drive where I store my download files. I realize the registry fix was just for FSX.

So I tried updating the shortcut for FTX by placing the following shortcut in it

"J:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\Scripts\FTXCentral\FTXCentral.exe"

But when I run it the FTXCentral.exe still tries to find the files in my HD that has FSX downloads, instead of the one where I have my FSX installed.

How do I "reset" FTXCentral.exe to find the correct path?

Or where is the correct FTXCentral.exe I need to make a shortcut from to fix the problem?

Thanks.

[Sundog]

The path it uses was the path last used for my last install (Dino's F-35).

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.IO.DirectoryNotFoundException: Could not find a part of the path 'H:\FSX Files\Downloads\FSX\Purchases\Dino\New F-35A_B_C\Install-v2\ORBX\Scripts\FTXConfigurator.exe'.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)

at FTXCentral.PublicDefs.SyncFTXConfigurator()

at FTXCentral.PublicDefs.InitFTXEnv()

at FTXCentral.FTXC.InitSystem()

at FTXCentral.FTXC.InitAll()

at FTXCentral.FTXC.Timer1_Tick(Object sender, EventArgs e)

at System.Windows.Forms.Timer.OnTick(EventArgs e)

at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

FTXCentral

Assembly Version: 1.0.2.4

Win32 Version: 1.0.2.4

CodeBase: file:///J:/Program%20Files%20(x86)/Microsoft%20Games/Microsoft%20Flight%20Simulator%20X/ORBX/Scripts/FTXCentral/FTXCentral.exe

----------------------------------------

Microsoft.VisualBasic

Assembly Version: 8.0.0.0

Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5462 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System.Runtime.Remoting

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

----------------------------------------

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

eethyxak

Assembly Version: 1.0.2.4

Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

[Ian Routley]

It still seems that your registry entries are not fixed.

There are a couple of tools to fix the Registry entries. It might be worth running one of the other ones.

The main trunk of your path

"'H:\FSX Files\Downloads\FSX\Purchases\Dino\New F-35A_B_C\Install-v2\ ... "

suggests that one of the products you have installed has altered the FSX registry key to that "trunk" entry.

This is not a path that FTXCentral would ever look in, unless your Reg key is wrong.

As an aside, if you have kept your drive letters the same, there is NO reason to muddle with registry entries at all, as all the path names are preserved.

[Tim Harris]

This is one of the best registry tools if you haven't tried it already http://tweakfs.com/download/fsx_reg_utility.zip

[Sundog]

This is one of the best registry tools if you haven't tried it already http://tweakfs.com/d...reg_utility.zip

Thanks, that did it. My "User" key had the correct path, but the "HKey" had the wrong path.

Go ahead and close this one out and I'll get back to my updating all of my Orbx installs with the latest patches.