Jump to content
The simFlight Network Forums

Recommended Posts

Posted

This is a great one! I mildly overclocked my CPU (I'm talking about 10Mhz on an XP2400). FS crashed when loading. I rebooted, reset the CPU, and boom, no more FS. I can boot with FSUIPC and FSNAV.DLL removed from the modules folder. With either of them in, FS will not start. I have removed every file I can see that relates to FSUIPC and downloaded the latest version. Still a no starter.

I know I'm probably looking at a reinstall of my 20Gb FS folder (and a wasted weekend :roll: ) , but on the off chance that anyone has seen this, and knows a cure, please post here!

Thanks,

Gareth Evans

Posted
This is a great one! I mildly overclocked my CPU (I'm talking about 10Mhz on an XP2400). FS crashed when loading. I rebooted, reset the CPU, and boom, no more FS. I can boot with FSUIPC and FSNAV.DLL removed from the modules folder. With either of them in, FS will not start. I have removed every file I can see that relates to FSUIPC and downloaded the latest version. Still a no starter.

It sounds like something else has got corrupted. Possibly your FS9.CFG file, or a weather-related file. Try, as an experiment, removing the FS9.CFG file (or renaming it), so that FS makes another. Then, in the initial menu do NOT select an existing Flight but make a new one.

If that fixes it then one or more of your Flight or Weather files are corrupted, or the FS9.CFG file contains something suspicious, or both.

If it makes no difference then it gets more complicated. It could be something in the Scenery files, the Sounds files, or the Aircraft files -- but really selecting a complete new flight and starting with a complete new CFG file should eliminate most of those as possibilities. In the end a re-install of FS may actually be quicker than trying to find the specific cause.

Regards,

Pete

Posted

Thanks for the help Peter, unfortunately I'm no nearer a solution. I tried renaming the .cfg, but I get a CTD during the initial loading. I'v also tried to your suggestions about the flight files to no avail. I can't think of anything else so it looks like a long day of reinstalling FS.

All this for a small experiment in overclocking! I blame Mr. Talisker!

Posted

All this for a small experiment in overclocking! I blame Mr. Talisker!

Yes, something has evidently been corrupted, but identifying what can be a very difficult process. When you do re-install, after uninstalling FS, don't forget to delete the stuff it leaves -- all your add-ons, created flights, and so on. It only uninstalls what it installed, but your corrupted data MAY be in one of the files created or added later.

Regards,

Pete

Posted

If I haven't had the weirdest weekend of computing......

Friday night, looking at some BIOS settings while trying to get my new CPU working correctly, I get some very odd messages after booting in to windows. I get 'Delayed Write Failure' errors spontaneously from files and folders I haven't been near in months, all on my second hard drive. I go to check it out, only one file shows on a half full 80Gb drive (which contains all my photographs :shock: )

Fearing hard drive failure I reboot, and Windows fails to start, I reboot again, get the boot options menu, select start normally, Windows fails to boot again. Next time I try 'last known good configuration' and get a successful boot (remember that bit!). My drive has not failed, the CPU is working correctly, and I make a very long and grumpy audit of my flight sim directory and addons ready for a reinstall the next day, and go to bed.

On saturday morning, I make coffee, and check my mail. Dad has sent me some photos, using his new found winzip skills, and while I'm browsing them, an unseasy feeling comes over me. PowerArchiver didn't throw the .dll error it has been complaining about for the last week.

FSUIPC.DLL and UNACE.DLL - related? Maybe....put FSUIPC back in FS, and it starts! All I can say is 'What in the name of sanity is going on?'

But once on the runway, all my 2D panels are black, just like when I first got FS9 last year. Remembering that it was a video driver problem, I go to update, and see that the driver has stepped back to sometime last summer! Eh?! I reinstall a current driver, cross my fingers, and FS is fine! :o

Only after several minutes of pondering what in Dog's name has happened, does the 'last known good configuration' come hazily back to my memory. Then the penny drops......

All I have to do is check all my other drivers, jump in to FS and enjoy....

Posted
If I haven't had the weirdest weekend of computing

...

All I have to do is check all my other drivers, jump in to FS and enjoy....

Ahwell, I'm glad things are coming together again. I think we all go through these horrible experiences once in a while.

Good flying!

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.