Software Has Anyone Come Across This?

[Niall]

For some strange reason, and without any additions to Orbiter in the last 24 hours, on program initialisation I get this....

http://www.waddayano.org/images/screenshot12.PNG

Buggered if I know what it is or means because I've done nothing to the program itself. I've run virus scans, malware scans, defrags & registry checks but it's still there on startup of Orbiter. Strangely, the program runs, but does CTD after a few minutes of running the scenario I'm trying to finish. I haven't run any others.

I'd love to know what it means.

 

[Quick_Nick]

Mostly a guess, but it seems like your Orbiter is corrupted... Try reinstalling. (at least the exe first, so you can keep your addons)

 

[orb]

Something is wrong with entry point to this function in Orbiter.exe:

public: virtual void __thiscall MFD2::Update(struct HDC__ *);

Like Quick_Nick said try replacing Orbiter.exe with the original taken from zip file.

 

[garyw]

I've seen that before when an addon compiled for Orbiter 2006P1 is used in Orbiter 2006 so I'd suggest making sure you have the Orbiter 2006P1 edition.

If that's not it try setting orbiter.exe to read only in case something is changing it.... very odd if that's the case!

 

[Niall]

thanks for the feedback and suggestions. Been there & done that but no joy. I guess there's nothing else for it but to delete & re-install :thumbsdown:

 

[Niall]

an update for those interested. I wound up deleting everything, and re-installing on a separate drive, which I'd intended to do last time, but in my usual rush, didn't. Fate is a funny thing. Anyway, in my new install, instead of simply activating all modules in the startup frame, I decided to activate them one at a time, and BINGO....that error message suddenly appeared when I activated the LaunchMFD module. I deactivated it, activated all the others and no reoccurrence. I then re-activated LaunchMFD and there it was again. I've left it deactivated and have not had any instance of the error since.

Perhaps it's something the author of LaunchMFD can explore?

 

[Kveldulf]

an update for those interested. I wound up deleting everything, and re-installing on a separate drive, which I'd intended to do last time, but in my usual rush, didn't. Fate is a funny thing. Anyway, in my new install, instead of simply activating all modules in the startup frame, I decided to activate them one at a time, and BINGO....that error message suddenly appeared when I activated the LaunchMFD module. I deactivated it, activated all the others and no reoccurrence. I then re-activated LaunchMFD and there it was again. I've left it deactivated and have not had any instance of the error since.

Perhaps it's something the author of LaunchMFD can explore?

Stupid question perhaps, but have you tried downloading a new copy of LaunchMFD? I use it with no problems, so perhaps something with your copy is bugged?

 

[tblaxland]

Perhaps it's something the author of LaunchMFD can explore?

LaunchMFD is available in two versions, one for 2006P1 and one for 2009RC1. My guess is that you are trying to run the 2009RC1 version under Orbiter 2006(P1?). It sure explains the entry point problem since the MFD2 class interface does not exist in 2006P1.