Split Second program crash

Try downloading the SST Club software and see if that is more stable. Both programs work the same from a mechanical standpoint. Use the USSA for primary and the Club for your backup PC and see if there is a change.

What timer are you using?

We use an S4 on the primary & a Timy on the secondary.

I have experienced the same thing multiple times on multiple computers. I have seen this with W2000, XP on IBM/Dell/Toshiba laptops. Also I often get a "buffer" full/empty type errors that keep looping and reapearring. This has happened with all flavors of SST, ussa,club and nastar.

We have also experienced HUGE delays between impulses and what happens on the screen. This delay increases as the race goes on. I think I would attribute this to SST writing of the xml file in real-time. Most races I run are very large races (with 200-500 racers) and I don't think the software is reliable and efficient in it's programming for this task.

The other day I was timing a NASTAR race and noticed that after I installed the NASTAR software things starting going wonky with my two computers that have NASTAR loaded (one with Remote). All my updates for my virus software started to fail to update. When I also tried to update the NASTAR database, the software would upload the race, download the database and on it's install "please wait" message the computer program would hang and crash. This was repeated many times. I checked my windows crash log and noticed that all my errors where somehow related to the NASTAR install. Rolled back my computer and everything is fine now. Don't know what all this means, except to me that I will no-longer being utilizing SST and will use a much more reliable and stable timing software for my large races.

I for one experience an occasional rare problem. Usually easy to fix, and Geoff is always available to help fix it. How many times when you have a problem with Microsoft does the programmer answer the phone and work with you? No one else in the industry is continually adding features and making software so robust. With that robustness comes changes and the occasional issue. Who is testing the software? We are, and we all need to work together to make it work.

Now, lets talk cost. How much did you pay for the software? Well, the software is free, and online timing is less than $200 bucks. Not bad in my book. You can buy other stuff, but not with the same features and nowhere near the usability or ease to train new users.

I believe Bill's problem come from something Geoff and I discussed tonight. Even though you are probably not using a floppy as the location for the data file, when a page is printed from the timing log, this may happen without the floppy (or USB) in the drive. Leave it in, and see if the problem still persists.
J

I apologize for the tardiness of this reply, but this problem worked itself out before I saw your reply - could have been through program upgrades, dumb luck, or maybe we starting leaving the disks in. I'll pay attention this year and let you know. Thanks for your input.