View Full Version : New WinXP based system FS2K2 issues
06-27-2002, 10:54 AM
The need to optimize FS2K2 performance drove me to build a new WinXP based system with Athlon 2.1 XP processor, 512 Megs of DDR RAM, ABIT N-7 133 MB, ASUS/Nvidia 8460 video card, Hercules Gamesurround XL audio card, 100 Gig 7200 RPM WD HDD. I finally got things running, aircraft and scenery transferred from old system, latest drivers downloaded and installed, sound problems overcome, and FS2K running well. Now suddenly screen savers lock up and go into a slide show sort of mode where one image persists for several minutes, then cuts to another, etc. I must use Task Manager to end the task, and sometimes that won't even work. Also it takes several minutes for a print command to execute. An advisor is suggesting a reformat and clean install, but it has taken days to to get FS set up the way I had it. Has anyone had a similar problem? This really is a Flight Sim topic.
06-27-2002, 01:37 PM
Just my thouhgts based on experience with other Operating Systems. This may help you get started. Some logical things to try until someone replies with a solid solution for you.
Not familiar with XP, but sounds like you have a TSR program running that causes the problem. It may be looking for a file that it can not find causing the cpu to be so busy that the IO requests from other programs have to "wait" in line for execution.
You point to the screen saver. Try turning the screen saver features off completely at first to see if this makes a difference. If it does, you will know the screen saver settings
BTW, after you use "End Task" to free up the system, does the system run okay from that point on, or does the problem come back a few minutes later? If "End Task" does fix the problem until you reboot, then the problem is associated with the program which you ended. At that point the fix depends on whether the program is a part of XP, or is another program installed separately.
CTL - ALT - DEL one time to access a list of running programs.
"End Task" programs one at a time until you find the offending program. Make notes as to which programs you ended so as to know which one is causing the problem. The fix depends on the program and its setup proceedures.
Pardom me if you already know these steps and have tried them.
Good luck! Hope this will help you.
06-27-2002, 08:09 PM
Thanks. I use Task Manager to break out of this condition. You led me to suspect a TSR thing associated with my cordless mouse, but I don't think that's it. I'll try again with Enditall, as there was still something from the mouse manufacturer running after End Task.
06-28-2002, 09:10 AM
Check under Programs, Accessories, System Tools, System Information, Tools, System Configuration Utillity. (Whew)
Look for the Startup tab. You can play with these settings.
Note the changes you make so you can put them back when you've fixed problem, if you find it.
There is also an "Automatic Skip Driver Agent" option to play with as well. Again, make notes so you can put things back to original.
Keep in mind that some programs require files or drivers to be loaded at boot and/or Windows startup. You can ignor those programs for testing purposes. If the system performs as it should with certain boot variables disabled, then you know at least which ones are working and which ones are giving problems.
At that point you can try to find the exact variable causing the problem from the list of those you did not load. If the varibles in question points to a program seperate from Windows, you can remove and reinstall that program paying close attention the setup options.
I know it's a real pain to have to start from scratch, but if finding the problem becomes too time consuming, that might be the best way to go. After all, when you do find the problem that may be your only choice anyway.
Good luck. I'm sirprised that no one else has offered any help to you.
06-28-2002, 10:24 PM
LAST EDITED ON Jun-28-02 AT 10:25PM (EDT)[p]I upgraded three months for the same reason and built my own Athlon (a 1.9) & WinXP based system. I was thrilled to have the fastest processor desktop, consumer processor for about a week. (AMD released the 2000 on me. #$#*@#* !!! )
I would vote for the clean install but do it in a very deliberate manner. Tarball/zip your old flight sim directory. Do a base install. Install FS2K2. Verify that all is kosher. Then unzip your old your flightsim directory into the new. You'll have your planes, scenery.. everything should be just as it was. Verify it again. Then do your updates one at a time and see which is screwing up the works. Yeah, this is a pain but it will settle your issues definitively.
Oakland Hub Manager -- Southwest Virtual
** Real Time Stats you gotta LUV! **
Powered by vBulletin® Version 4.2.2 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.