Running an Intel 1.6 Pent IV 845WN motherboard with 512 mb RAM, Windows XP.  CFS set to default which calls for display to be maxed for everything except ground shadows.

Fine!  Except that after a few minutes of really satisfying action, I am suddenly "warped" to the desktop.  Adding insult to injury, the desktop colors have changed to a light tan background (About the color of the one in CFS.) necessitating resetting the "Properties" for the desktop.

Anybody got any words of wisdom about how to fix this one?  It does seem to correlate with the complexity of he scenery and the number of a/c in the particular mission.

Many thanks,

Phil424

Not sure if this will help. Neither of you mentioned your Desktop resolution. The recommended setting for earlier sims like CFS1 is High Color (16 bit).
This setting is for Win98/Me. I have no knowledge of XP.

Sincemmy initial query, I have upgraded my video card to a Radeon 9000 Pro Series (64mb).  Now, my game sets itself upon the first running after installation.  I have not had enough time to evaluate the result of the new hardware.  Windows XP has a feature that alows game to be installed as if it were running at the last point at which it was reliable.  I chose Win 95.

We shall see!

Stay in touch,

Phil424

I finally asked Microsoft for help and they suggested un-installing CFS and re-installing with a clean boot in a directory all by itself.  I did all that they suggested, and what do you know?  It worked, at least after a few days of intensive playing it hasn't dumped me again. Go figure!

All three CFS programs seem to me to be inherently unstable, prone to all the ills of computerdom.  I'm not smart enough to know why, let alone how to fix it, so I'll just keep chuggin' along!

Cheers,

Phil

I have a question for Phil424:

What do you mean "re-installing with a clean boot in a directory all by itself"? Are you running the game under your new or old video card? If you changed the card this may be the reason that it is working, isn´t it?

Please let me know, i want to see my game working too.

Thanks!!!

Hi guys,
I reinstalled CFS and installed Enditall.( nice little program to close programs when flying)Utilities
No dumps so far  , installed Cfs in its own dir, not under program files. Finished Ef campaign  and startet new one. Me109 a bugger to land.

Quote:


I have the same chronic trouble with cfs1 and XP Home edition

I'm sure I mentioned this before but maybe not in this thread. There is a known conflict with some older FS98/CFS1 aircraft & WinXP. This is caused by them being animated with an early version of Aircraft Animator. They can be fixed by patching the MDL file with the MDL Repair Utility. http://www.simviation.com/fs2000utilities_gen2.htm

The conflict is with the aircraft & XP - not  a particular sim. The problem aircraft work fine in Win9x/Me. The utility has been tested for me by XP users & works for all current M$ sims except CFS3, for which it does not apply.

Quote:

Wish I could help but I can't figure that one out at all.  ???

I had the same problem running windows 98 second addition. Pentium 3 with a Voodo card. The gray  matter is thick so I will try to remember the problem.

Lets see I would be playing CFS_1 and It would dump to the desk top or shut down the game completley. when you looked at it it would be a pinkish brown light color (spalsh screens). If you shut down the game and opened les say Microsoft Word you would have the same pinkish tan colors on you windows. To correct this you would have to shut down and reboot the computer then you would be back to normal colors in the windows.

Windows 98 operats on a fat 32. If I remeber correctly the problem was not in the game but the operating system itself. I had a damaged kernal with in the fat 32. To correct this I flatened the hard drive and reinstalled the operating system. I tried a repair but that did not work.

Then I reinstalled, drivers, up dates for the 98 operating system, reloaded CFS_1 renamed it to CFS_1Old. Reinstalled CFS_1. this gave me 2 versaions of CFS_1 on the hard drive. Then I went into the main file for CFS_1 old and created a short cut to the desk top. Renamed the short cut to CFS_1 Old. This way I could test any 3 party addons on the CFS_1Old before installing them to the CFS_1.
I never found any problems with the third party addons as I remember. It was the kernal in the fat 32 that created the problem.

IM currently running XP_pro, 2 gig processor, Nvida TI 4600 with 1 gig of RD Ram. It happened to me one time the same issue. If the game dumps when flying a campain or what ever THE splash screens and windows  change. I always with flight simulators run 3 versions of the same game on one hard drive/ named CFS_1, CFS_old CFS_test. This way I always test 3rd party addons before putting them into my CFS_1 game. I do believe this is the problem. XP_Pro runs NTFS not FAT 32. How ever XP_pro has fat 32 and when you install the windows operating system you can select FAT_32 or NTFS. I strongly recomend running NTFS. I believe it still lies in a third party scenery, mission or aircraft that causes the problem by creating a broken thread making the computer to drop one or two decimals when counting in the Hex Decimal system system(all computers when computing any program counts binnary hex decimals. That would explain why when the game dumps the windows system changes colors as if you went into the control panel and changed them. Again I do not suggest that you reload the operating system.

I would use a process of elimination. Re name the game folder to old. Create a new Icon. Reload a fresh game strictly stock. Fly it a while and see if you have the same issue. If you do then I would check Microsofts websight for current updates. Then I would make sure all my drivers for the video card and so on are current. Then try thge stock game for a whille and see if that doesnt cure the problem. If it does then I would name that folder to test create another Icon and reload a new CFS_1 program. This gives you 3 CFS_1. Defrag the hard drive at this point. Move Gauges first, then move one aircraft at a time to the test game and fly it for a while and see if you can create the same issue. If not then I would install it to the new CFS_1. I would do this on aircraft, scenery, textures missions, sound wave files etc etc. and so on untill I found the problem. This process would keep your games running, computer running. Once I pin pointed the problem I would take a corrective action. If it was a third party addon then I would deleate it. But be kind and notify the creator so he or she would have an opertunity to correct the bug. This is only a suggestion and sometimes locating an isssue can be very long and tedious process but it is better than the alternative of flatening a hard drive and starting over from scratch and when your done you could still have the same issue after reinstalling everything.