yet another twist in the tale

The possible solution noted before seemed to work with no problems over the last two weeks. But P noted that earlier, the downloads had the path to D: hard-coded into the asp, so the files in D: were being accessed though IIS pointed to E:. This might have led to the earlier problems, he said. To test this out, we put back the 4 GB of stuff to the playout folder in E: - and the streams continued to work fine. Now we have deleted the stuff in D:, and that drive is pending a Scandisk. But that needs a reboot, so probably we'll keep it pending. Or maybe we can move all the data to E: and do it without a reboot - will think about it.