What could possibly cause a sequence file to be modified outside of the TestStand Operator Interface during execution?

[ATE_Dude_22]

I have a legacy test set at my work that was developed using LabVIEW 7.1/TestStand 3.1. This past weekend it threw TestStand pop-up prompt that I have not encountered before, and was wondering if anyone might have some insight into what could possibly cause it.

The pop-up read:

The file "C:\XXX\Temperature.seq has been modified outside of the operator interface. Do you want to reload it?

The problem is, this pop-up occurred on a Sunday morning (with no one touching the test set), on an ATE test set that had been running this very sequence for several days. No one would have done anything to modify this sequence file, so I am completey at a loss for why this happened??

I don't have the choice of upgrading this test set to current development SW, or to modify the existing code which has been running for years without this issue having occurred to my knowledge.

I'm simply looking for any plausible reason why this could have happened, so feel free to speculate, cause at this point that's more than I have.

[James_Grey]

Here is some pure speculation:

1. File is on shared drive or under some-sort of push scc system and was modified remotely

2. Time/Date and/or daylight savings time settings were modified on the machine while the file was loaded. (I've seen this happen with source code files in other ADEs, ...not sure if it can happen with TestStand).

[ATE_Dude_22]

I am leaning towards #2 myself. This ATE is not on a network. However I am having a difficult time proving my theory as I can't find anything in the TestStand documentation to support timestamps of a file already loaded in memory would cause such a condition.

Thanks for your offering.

[James_Grey]

Is your drive in Fat32 format? I have a vague recollection that this might be necessary for the condition to occur.  On the otherhand, this recollection is probably over a decade old and of dubious reliability.