Had my computer pro here today that maintains our company machines. Took my standalone sim machine apart, and installed a new 17 7700k processor, new mobo and memory, 2 - new GTX 1080ti -s, and a Samsung 960 EVO additional SDD to give me one more hard drive. OS is Win7, computer refused to recognize the original SDD that has all my FSX stuff on it. Will not boot.

So I am dead in the water for now. He has taken it to his shop hoping to somehow clone the drive that is not responding and find out why?. Maybe I will be back in business with P3Dv4 before Christmas. However I will keep reading avsim and stories untill I can fly again!!

 

I'm a bit confused Lennie. You built a new computer, but kept your old bootable hard drive from your previous build and threw it in your new computer expecting it to boot up and leave where you left off? If that's the case, it won't. 

Always start over with new HD and OS like WIN 10. It is not fun reloading but it will be the best way. I'm doing a rebuild in near future. My XPLANE is on another drive already as is my FSX STEAM.

Only FSX on C drive so that will be total redo but with P3D v4. I did what you did years ago with fs2004. Took a long time to get it sorted out but it was never the same.

Hi Lennie,

My thoughts are along the same lines as Jack C and Timothy, although it is possible to boot with an OS disk for a previous machine, (new drivers would be installed by windows update and your new MOBO installation CD/DVD where chipset drivers would be installed) the existing drivers will always complicate the stability of your new hardware and old OpSys, (example: when you boot from a previous OS/hardware setup many of the drivers Chipset MOBO features and device drivers will need to be installed among all previous driver and setup).
To avoid such boot complications and general stability issues, you should install your OS and drivers fresh to a new or freshly partitioned/formatted disk. Failing to do this will always produce anomalous intermittent OS issues or unresolvable BSOD's with your partial installation process.

You should also seek out any firmware updates for your new SSD if it is not being recognised or preventing boot to OS.

I think you will find that a different system  is installed depending on the motherboard and chip features,  an amd installation would never work at all if placed in a windows box and vice versa.

Cloning that will not enable you to replace it.  You would need to put it into the original system and use the tools available to save your content etc ready for reinstallation.

In the case of putting the disk in a compatible box it may boot but will certainly require activation.  An OEM disk does not allow you to instal on a different system.

Kinda makes one wonder about the company IT guy... 

Thanks guys, I was hoping not to have to spend 2 weeks downloading and installing FSX stuff, but guess i will. Anyhow, at my age what else can i spend my time doing??

Yes, every company has at least one mysterious IT guy that comes around and magically fixes the office PC's and servers - but why do people in this Forum seem to know what really ails your new build?

A drive with an OS on it which is directed as the boot drive in the bios should work. As long as the new board and hardware is compatible with the OS, than in theory this should work. You should also be able to build a new box, install all that stuff you want and have it boot off of the old drive. Chipset drivers should install and it should work fine. There is something else going on here. Ive done this over the years many times and never had any huge issues, other than installing hardware drivers and chipset drivers during initial boot up. I have not tried this with an SSD yet though and dont plan on it any time soon. Next PC build will be with a cloned version of my old drive and still using WIN 7.