recover corrupted sequence file

[trout00]

help with recover sequence file corrupted.I change the value in a pre expression and the computer just reset.
and the corrupted file message appears. I have a lot of locals, fileglobal and pre-expressions...

[Ryan Ramcharan]

Hi trout00,

The sequence file contains no information. If you open it in Notepad, you will see that the file is empty. In fact it is not completely empty, but contains a whole lot of spaces (i.e. \s). Not sure what happened to this file, but the information in it seems to be gone.

Bob

[trout00]

I have win2000 and Teststand 2.01f, lately, I click on the run button in the sequence editor windows and the computer reset. This does not happen all the time, but about three times a day. I have to back up my work more often. What cause the run button to crash the win2000? How do I fix the problem?

[Ryan Ramcharan]

Hi trout00,

In all my years working with TestStand, I have never heard of this problem. To save yourself some headache, I would suggest uninstalling and reinstalling the software. Also, do you have any virus software running on that machine? You should probably do a scan for viruses. Just trying to rule out all possibilities 🙂

Bob

[Scott_Richardson]

To trout00 -
Typically if an action taken inside an application causes a computer reset, this suggests that the OS is hitting some sort of kernel level exception. The OS is not giving you a blue screen but instead it is set to auto reset.

Right click on the My Computer icon on your desktop and select Properties. On the System Properties dialog box, take a look at the Startup and Recovery settings located on the Advanced tab.

I suspect that some sort of event log will be registered in this case.

Kernel level exceptions typically occur when hardware drivers or low level services error or have a bug. In the case of the sequence editor, none of its code is low level, so any error the program causes would just cause the applicati
on to shutdown, not the OS.

With this in mind, it suggests that you might have a hardware problem with the computer system.

See if the event log gives you any additional information.

Scott Richardson (NI)