Problem Orbit MFD Grav indicator Yellow and zeroed

[Milkbone]

Hi Fellow Orbinauts

Don't think I have ever made a post if I have its been so long ago I dont remember

My problem is I had a system crash and reinstalled my xp/sp3 and up and running again. Since it was a system error I couldn't recover from (believe me I tried) the hard drive was left intack so my orbiter folder was ok.

And it played fine before

I move it to the new hard drive where I installed my system but the scenario I played has a slight flaw - nothing big and I can work around it fine but its not right so I thought I would ask. The Orbit MFD bottem Grav thingy which shows the amount of force on the ship at its current location is yellow and zeroed out
All the ships in this scenario (which worked before) are the same - if I play another scenario that i also play it works fine as it did on the other drive

I have changed the video settings through almost all of the ones I have ever used and it does the same in all with slight graphic changes in picture quality but the MFD is the same yellow and zero the other scenario continues to function OK

Any ideas on what or where to look - in order to try and correct it

Thanks in advance

 

[Milkbone]

Thx anyway I found a response somewhere already posted here - about missing dlls so I copied them and pasted them in the orbiter folder. It created other probs at first but I was able to regain the Grav at the bottom of the orbit MFD again and it appears to be working fine. Playing with the video settings after pasting these dll's fixed the problems created by placing them in the orbiter folder.

Now the one step beyond thingy - The Orbiter folder resides on my c Drive - the link to start it is on my e drive - for xp I boot from e and the link is on desktop- so Orbiter folder exist the way it was before the crash - when e crashed I only lost my link to orbiter - Yet these missing files where missing before the crash and I had no video problems.

Weird

 

[ADSWNJ]

What DLL's did you copy in? Hopefully not MSVC* ones.

 

[Milkbone]

MSVCP71, MSVCRTD, and MSVCR71 all .dll's They have appeared to correct the problem
and don't understand the response unless they will create further problems later