This is a check to see if anyone has ever corrupted a EG 4.1 project file when a network share you are writing to is lost? I'm running EG 4.1 on Vista Business and writing the project file to a Solaris 9 remote server, which has Windows-compatible network shares. The corrupted project files appear to be created filled with '00'x, then overwritten from the top with the project data, which is not completed, but error messages are not necessarily issued.
I'm now having to save my EG projects locally, then sync them with the network versions at the end of each day. Is this an EG or Vista problem?
When EG complained that the project file was corrupted on opening, I tried to open it with WinZip, and when that failed I eventually opened it with UltraEdit. However, any text editor that can display hex character would work just as well.
Currently I'm saving EG project files locally, then syncing them at the end of each day to the network share with FreeFileSync, which tells me when it is not successful.