LaunchMFD missing .DLLs

[mbartley]

I recently did a fresh format-and-reinstall of Windows XP on one of my computers, the primary use of which is to run Orbiter, so I installed that and started installing critical (to me) add-ons.

Orbiter 2006P1 malfunctioned in the usual way until I installed two .DLL files. I can never remember their names, nor can I remember where to look up what is required. Fortunately I've run into this several times before and had copies of the ones I needed in a backup directory.

Next I found that LaunchMFD could be activated in Orbiter LaunchPad -> Modules, but it wouldn't show up in the MFD selector when Orbiter was actually running. On a guess, I installed .NET Framework version 2, and that solved the problem.

Is there a way to determine which .DLL file(s) actually caused this? This should be a well documented requirement for LaunchMFD. Would .NET Framework version 2 have solved the problem with Orbiter itself?

 

[MeDiCS]

To avoid headaches I always install Visual Basic Runtime, DirectX, .NET Framework (version 3) and Visual C++ Runtimes (2005 and 2008). This avoid 99% of this kind of problems.

 

[agentgonzo]

I've just done a dependency walker on LaunchMFD. It require MSVCP80.DLL and MSVCR80.DLL. You can download these easily from the web.

I'm not sure what part of it requires them, but I'll make sure that it's not there for the next release, or they're included in the zip file.

 

[Enjo]

This should be a well documented requirement for LaunchMFD.

It IS documented... Check section 2) of the manual.

 

[mbartley]

It IS documented... Check section 2) of the manual.

"If Orbiter complains about missing DLLs, then you'll need to install VC++ Redistributable Package."

Trouble is, it didn't complain. I looked in the orbiter.log file - nothing there.