Hi all... I reported this to Parallels already but figured I would post here too. I'm using Beta 6 1812.7 build and my guest OS is WinXP Pro SP2. The only thing I'm doing in my guest OS is running two primary things: Starteam from Borland (file check in/check out system) Borland Delph V7 I am using Parallels to run the Delphi compiler and compile SW for work. I have a tool that we have written that accesses machines we build for the biomedical industry over a network and it downloads debug logs. I can view and edit these logs in this tool. The first file corruption I had was back in Beta 4. I did get one kernel panic and after that no matter what I did, a particular source file for our tool would get truncated. Even if I deleted it and rechecked it out from Starteam it would be truncated it. I chalked this up to the kernel panic and went back to a previous backup of the VM. Everything was fine after that. Two days ago I was in this same tool and I had downloaded a fairly small debug log that was approximately 3.1mb in size. Our viewer can page to disk so we can open and view 100mb plus files easily. There is a poorly implemented save function in the tool that copies the text to the windows clipboard then saves the clipboard to disk. We plan to change the way it works. But in this case I got an error that the clipboard could not be accessed. I figured it was a size problem or something and didn't worry about it. Then this morning. Running the same tool I went to exit the tool and got an IO error from windows. I'm sure it was during the write of our binary configuration file. I restarted the tool and got a "read beyond end of file" error. I went and deleted the configuration file and the tool started fine. So this is like another type of corruption that results in truncation of the file. I have had no kernel panics and no problems so it makes me a little worried that the file system that is acting to update the VM hdd file is not totally robust. I've reported this to parallels but I thought I might see if others have experienced anything similar. I'm on a MBP, 2.16 ghz, with 2gb RAM and 120gb HD.
