Looks normal to me, Alex. With a faulty drive, the health display would show some warning values and the graph may read some spikes. Means where the transfer rate seriously drops to single digits. Well, that's how my failed drives showed up back then.

 

If the self diagnose shows serious trouble, your bootup screen and later normal Windows will give you warnings on the S.M.A.R.T. status. You can't miss those.

 

So far, normal mechanical drives showed to really benefit from that self monitoring. So e.g. slowly arising mechanical problems can be spotted before it's too late.

 

There's a health and error scan tab. You may want to use those too. Here's another normal looking WDC640.

Looks very similar to yours. Not the exact same type and interface maybe. But, this is how they usually look like.

Looks normal to me, Alex. With a faulty drive, the health display would show some warning values and the graph may read some spikes. Means where the transfer rate seriously drops to single digits. Well, that's how my failed drives showed up back then.

My issue now is just FSX locking up on the interface [not neccessarily in flight]. Changing aircraft, etc.

 

Alex

Yikes. Did you try that one already?

You could temporarily move your dll.xml and exe.xml away. This will lead to a sort of clean boot for FSX, no addon modules.

If the clean FSX works then, some addon causes the problems. Hence that check.

Dont know if it is the same issuenfor you, but I found the problem on my system. The speed was restored when I removed the dll.xml file so it was related to one of the dll file installed as part of dll.xml. In my case, fscopilot was the cause of the problem. When i removed that dll, the speed increased by a factor of three.

 

I dont know why suddently fscopilot started to create problems as it was working fine before and i seldom use it recently. The last modification i have made to my system before the problem apeared was to move ORBX sceneries from drive C to D using mklink window function. Maybe its related in some obscure way.

 

 

 

the problem apeared was to move ORBX sceneries from drive C to D using mklink window function

 

You can move ORBX sceneries to another HDD? I was told that was not possible and FTX/Orbx may come up with a solution to do this one day. I would love to move mine to another HDD as I currently have them on my SSD which is slowly filling up.

 

Best regards,

 

Jim

Yes it is possible,

 

You first move the orbx forum to the other disk. There should be no orbx folder on your drive C after the move. So its not a copy operation but rather a move.

 

Then you have to use the DOS utility to go to the fsx folder and you write the DOS Command; mklink /J "ORBX" "d:\yournewOrbxfoldername".

 

In the command above, replace the origin and destinationn path by the name of your fsx folder on drive c and the name of your orbx folder name.

 

I'm not in front of my fsx computer so better check those instruction on google. One of the key world is DOS Symbolic link or just moving orbx to another drive.

 

This worked great for me. In principle there is a slight reduction in speed but in my case not noticeable. I freed 15 GB from my drive C.

 

Some people on the forums also reported problems with some add-on having difficulties with this type of links. I experienced no down side personnally.

 

Pierre