Page 1 of 1

Moved to New Case and MoBo - Now FSX Won't Start

PostPosted: Tue Dec 16, 2008 9:15 am
by FlightHound
I moved hard drives from old system to new case, mobo, etc.  Now when I try to start FSX I get an APPCRASH with faulting module facilities.dll.  Will a repair of FSX fix this?  What will a repair do if Acceleration is already installed? :'(

Re: Moved to New Case and MoBo - Now FSX Won't Start

PostPosted: Tue Dec 16, 2008 9:31 am
by Daube
A repair with the original DVD will screw your Acceleration.
You moved the disk containing FSX to a new computer, ok. Does this disk also contain your operating system ?

Re: Moved to New Case and MoBo - Now FSX Won't Start

PostPosted: Tue Dec 16, 2008 10:14 am
by FlightHound
Three disks moved.

Re: Moved to New Case and MoBo - Now FSX Won't Start

PostPosted: Wed Dec 17, 2008 10:08 pm
by HarvesteR
yeah, most games don't like being separated from the OS they've been installed in because it messes with the registry and wreaks all sorts of havoc on your computer

usually the best practice when switching to a new mobo, is formatting/reinstalling Windows, and then everything else.. since windows too doesn't like to boot up one day and find new hardware in the pc it inhabits...

but, since it seems that your OS is booting up nicely anyways, i think you could possibly get by with a complete reinstall or maybe even just a repair of your FSX install, as that will create new registry entries and maybe fix some of the problems and hopefully FSX will start... i don't have acceleration, so i can't tell if using the repair function will mess with the expansion pack, so i would advise you do a complete uninstall/reinstall, just to be on the safe side

i too had some problems with FS following a dirty windows installation, and had to spend the day today reinstalling it...

Re: Moved to New Case and MoBo - Now FSX Won't Start

PostPosted: Thu Dec 18, 2008 8:56 am
by FlightHound
I did a repair of FSX and then a restore of the drive that had FSX on it from Acronis Image and now it starts.  Beats me!    All drives were just moved to new box, so OS didn't have anything new to deal with drive wise.  

Thanks for the reply.