Perhaps this might convince you I'm not the only one...at least the questioner got a polite reply!!
http://n.ethz.ch/student/mmoeller/fms/f ... php?t=3690
Computer crashing
24 posts
• Page 2 of 2 • 1, 2
by Michael_Moeller » Wed May 24, 2006 7:16 am
I don't want to comment about the argument, just a general thing: The more details you give about your problem and what is related with it (operatiny system, hardware, ...) the better are the chances to find a solution.
About the calibration not beeing saved. If you calibrate and then you do not exit the FMS without freezing your computer or crashing it, the calibration won't be saved to the registry. You need to exit the FMS the "normal" way for the calibration to be saved.
About your crashes. What kind of crash is it? Freezing the computer needing you to reboot manually? Automatic reboot of your pc? Freezing of the FMS application only (closeable with the task manager)? Are there any error messages?
What operating system do you use? (Assuming windows xp for the following).
From what you have written it looks very much like a problem with the graphics driver or the driver for the mainboard (agp-port). With windows xp it is very difficult to crash the operating system itself. An application problem normaly leads only to the crashing of the application itself, but not the operating system. If the operating system (windows xp) crashes this is usually due to conflicts between drivers or hardware. These conflicts can stay unnoticed for a long time when they are about 3d acceleration hardware. The "normal" desktop applications do not use any 3d accelerator funtionality. Even the dxdiag "test" are very often pointless. They are too simple running almost always (without erro) even if the 3d acceleration drivers are completely messed up.
My suggestion is (if you haven't done already): Get the newest drivers for your mainboard and graphics card from the website of the manufacturer. Get the latest directx 9.0c from microsoft. Install these. Check the correct installation by trying to run some mordern 3d game (flight sim, ...) that is based on directx. It just needs to be a bit more complicated then the super basic dxdiag test.
Michael Möller
About the calibration not beeing saved. If you calibrate and then you do not exit the FMS without freezing your computer or crashing it, the calibration won't be saved to the registry. You need to exit the FMS the "normal" way for the calibration to be saved.
About your crashes. What kind of crash is it? Freezing the computer needing you to reboot manually? Automatic reboot of your pc? Freezing of the FMS application only (closeable with the task manager)? Are there any error messages?
What operating system do you use? (Assuming windows xp for the following).
From what you have written it looks very much like a problem with the graphics driver or the driver for the mainboard (agp-port). With windows xp it is very difficult to crash the operating system itself. An application problem normaly leads only to the crashing of the application itself, but not the operating system. If the operating system (windows xp) crashes this is usually due to conflicts between drivers or hardware. These conflicts can stay unnoticed for a long time when they are about 3d acceleration hardware. The "normal" desktop applications do not use any 3d accelerator funtionality. Even the dxdiag "test" are very often pointless. They are too simple running almost always (without erro) even if the 3d acceleration drivers are completely messed up.
My suggestion is (if you haven't done already): Get the newest drivers for your mainboard and graphics card from the website of the manufacturer. Get the latest directx 9.0c from microsoft. Install these. Check the correct installation by trying to run some mordern 3d game (flight sim, ...) that is based on directx. It just needs to be a bit more complicated then the super basic dxdiag test.
Michael Möller
- Michael_Moeller
- Posts: 88
- Joined: Thu Feb 28, 2002 10:38 am
by Rolo » Wed May 24, 2006 11:04 pm
Thank you Michael for your reply. Yes I am running XP on a computer less than 3 years old and fully updated. I have a flight sim which works perfectly with a joystick and I also have other directX controlled programs which work fine. I have never had any problems with any other program, game, or disc installed on my computer.
The problem was that the computer was switching off and automatically rebooting. This was intermittent and a lot less of a problem with Beta 7 than it was with 8.3 or 8.5. Sometimes it crashed when I clicked to change planes or scenery and sometimes (nearly always) crashed when I clicked to come out of the program. No error messages just a total crash.
As a result of your advice I deleted FMS completely and downloaded the DirectX 9c as you suggested.
I have just tried to reinstall the original 8.3 disc and Esky and on this occasion I had a couple of warning windows. I can't remember exactly what the wording of these were but the first one told me that this program was not passed for use on XP and it could be dangerous to continue. The second warning was telling me that there was a problem with the joystick (Esky) connection and driver and to continue installing could cause serious damage to my computer.
I took the risk and installed it anyway, and this time I had intermittent connection with the controller and yet another crash. I tried downloading 8.5 and this was exactly the same.
With great respect to you and others who have offered suggestions I'm not prepared to take any more risks with my computer. It works perfectly for everything else I use it for. Having looked at other threads and the trouble other people are also having with this program - lots and lots of trouble it seems, and the suggestions that are being made regarding such things as updating drivers, disabling com ports, altering this that and the other, changing this and changing that....I just don't believe the trouble this program seems to be causing! This must be a unique and exceptionally intricate piece of software.
I'm afraid for the sake of a game it's just not worth the hassle.
Many thanks anyway but I've now deleted it and given up.
The problem was that the computer was switching off and automatically rebooting. This was intermittent and a lot less of a problem with Beta 7 than it was with 8.3 or 8.5. Sometimes it crashed when I clicked to change planes or scenery and sometimes (nearly always) crashed when I clicked to come out of the program. No error messages just a total crash.
As a result of your advice I deleted FMS completely and downloaded the DirectX 9c as you suggested.
I have just tried to reinstall the original 8.3 disc and Esky and on this occasion I had a couple of warning windows. I can't remember exactly what the wording of these were but the first one told me that this program was not passed for use on XP and it could be dangerous to continue. The second warning was telling me that there was a problem with the joystick (Esky) connection and driver and to continue installing could cause serious damage to my computer.
I took the risk and installed it anyway, and this time I had intermittent connection with the controller and yet another crash. I tried downloading 8.5 and this was exactly the same.
With great respect to you and others who have offered suggestions I'm not prepared to take any more risks with my computer. It works perfectly for everything else I use it for. Having looked at other threads and the trouble other people are also having with this program - lots and lots of trouble it seems, and the suggestions that are being made regarding such things as updating drivers, disabling com ports, altering this that and the other, changing this and changing that....I just don't believe the trouble this program seems to be causing! This must be a unique and exceptionally intricate piece of software.
I'm afraid for the sake of a game it's just not worth the hassle.
Many thanks anyway but I've now deleted it and given up.
- Rolo
- Posts: 27
- Joined: Sun May 21, 2006 2:22 pm
by ukuser » Fri May 26, 2006 10:18 pm
That will be me then 
Interesting, I also brought mine from Sandown, as did a hell of a lot of people however i knew before hand that the FMS software was supplied as just about every cheap helicopyer from the far east includes it
About my issue :-
Version 7 has never crashed, 8.3 and 8.5 will not run, i am getting to the stage of comparing registry entries between them for the differences, i have also tried swapping files from each install becuase there's definately something thats changed between the 7 and 8.x thats caused it.
I do think think you can compare peoples machine specs as much and update drivers as you like but bottom line theres machine specs here from all manufacturers pointing this to a software issue.
My only question is, is this still being developed ?, if its not i'll reluctantly change now
ukuser
Interesting, I also brought mine from Sandown, as did a hell of a lot of people however i knew before hand that the FMS software was supplied as just about every cheap helicopyer from the far east includes it
About my issue :-
Version 7 has never crashed, 8.3 and 8.5 will not run, i am getting to the stage of comparing registry entries between them for the differences, i have also tried swapping files from each install becuase there's definately something thats changed between the 7 and 8.x thats caused it.
I do think think you can compare peoples machine specs as much and update drivers as you like but bottom line theres machine specs here from all manufacturers pointing this to a software issue.
My only question is, is this still being developed ?, if its not i'll reluctantly change now
ukuser
- ukuser
- Posts: 10
- Joined: Tue May 23, 2006 8:17 pm
by Rolo » Sat May 27, 2006 12:10 am
The crashing problems certainly have nothing to do with the actual disc supplied with the set because I have just had another attempt at installing Beta7 without using the supplied disc and having deleted all trace of FMS from my comp.
All I did was download Beta7 then stuck the USB plug from the Esky into the USB socket. I then callibrated it and it seemed to be working fine...but after several flights with different planes I then clicked to change to another plane and my computer crashed. I tried again, having re-callibrated the Esky and again after a few flights it crashed. It also crashed when I clicked to exit the program.
I can only conclude that if FMS works ok with other types of transmitter (although I note that there have been some problems with those as well) then there can't be a problem with FMS itself...and it must be the Esky which is not compatible.
Either way, I don't think I am going to solve the mystery and we are just going round in circles....it ain't gonna work!
All I did was download Beta7 then stuck the USB plug from the Esky into the USB socket. I then callibrated it and it seemed to be working fine...but after several flights with different planes I then clicked to change to another plane and my computer crashed. I tried again, having re-callibrated the Esky and again after a few flights it crashed. It also crashed when I clicked to exit the program.
I can only conclude that if FMS works ok with other types of transmitter (although I note that there have been some problems with those as well) then there can't be a problem with FMS itself...and it must be the Esky which is not compatible.
Either way, I don't think I am going to solve the mystery and we are just going round in circles....it ain't gonna work!
- Rolo
- Posts: 27
- Joined: Sun May 21, 2006 2:22 pm
by alamo211 » Sun Jul 23, 2006 6:23 pm
Hi Rolo
You probaly have your problems corrected by now , but just a little input of my glitches if you have not, first I assume you are useing a purchased disk to down load the program ? this was what I did at first it wouldn"t work correctly and I had to download a new version of DirectX then keep working on the caliberation and resolution, fiddle with the frames per second and the view.It finally started working right.
But back to the disk,once I downloaded a AOL free minutes disk everything went just fine to the point of "click finish" which is exactly what it did! Locked the computer down would not re boot I had Aol, Emachine & Southern Bell on the phone for about 3 hours eventually got it back up.
However none of them could give me an answer as to what had happened other than it was a bad burn on the Aol disk. Perhaps this may also be the problem that you are experiencing? PS I now use all the free AOL disks that come for frisbees
You probaly have your problems corrected by now , but just a little input of my glitches if you have not, first I assume you are useing a purchased disk to down load the program ? this was what I did at first it wouldn"t work correctly and I had to download a new version of DirectX then keep working on the caliberation and resolution, fiddle with the frames per second and the view.It finally started working right.
But back to the disk,once I downloaded a AOL free minutes disk everything went just fine to the point of "click finish" which is exactly what it did! Locked the computer down would not re boot I had Aol, Emachine & Southern Bell on the phone for about 3 hours eventually got it back up.
However none of them could give me an answer as to what had happened other than it was a bad burn on the Aol disk. Perhaps this may also be the problem that you are experiencing? PS I now use all the free AOL disks that come for frisbees
- alamo211
- Posts: 2
- Joined: Sun Jul 23, 2006 5:40 pm
24 posts
• Page 2 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 1 guest