Hi Bob,
I experience similar issues lately
ALT-F4 and windows task manager can help to prevent from rebooting your PC.
In my case this behaviour occurs when object ID's are changed or removed from the kepler input files. Lately we had Kicksat, Phonesat and other cubesats that burned up in the atmosphere and therefor where removed from the DB.
To solve the issue I check and edit the satellite group files and remove them by hand.
Some extra information for Erich:
I create my own kepler input files direct from Space Track (with the help from HaloKepler) here an example (http://www.pe0sat.vgnet.nl/kepler/mykepler.txt) and use multiple groups that use there own kepler input when object ID's are no longer available or have changed and satellites are active in the group file SatPC32 reacts with the message "Ungultige gleitkommaoperation"
Maybe it is possible to have SatPC32 act different when object ID's are changed or removed from the kepler input file and active in one of the group files.
73 Jan PE0SAT
On 05-06-2014 21:49, Bob- W7LRD wrote:
This is on different computer- I get Ungultige gleitkommaoperation marching across the screen. I must shut the computer down to stop it. I had just downloaded new keps. The last time (other computer) I had to delete the entire program and start from scratch with everything. Is there something I am doing/not doing?? Becoming a PITA to keep everything running. from the digitally challenged 73 Bob W7LRD _______________________________________________ Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb