All this having to do hard resets is getting a tad tedious. Isn't there at least some way to reliably slay the beast ( Vegas70.exe), even Task Manager cannot kill it. Most troubling is it sits there in some kind of internal fatal embrace with itself all that while accessing the disk.

Now here's something I've noticed since V4 days that says to me there's some badly written code. Open a new project. Drop some previously unopened media on the T/L and while Vegas is building its waveform file(s) hit File>Save. That's it. Vegas is locked up and the OS has lost control. If you wait until Vegas finished building those files then you can get control back.

Another thing. You cannot interrupt Vegas rendering a frame. Take a complex composite that takes seconds per frame at Best/Full. While it's ticking away rendering that frame for preview change to Preview/Auto. The change only occurs after the current frame is rendered. You cannot even move the playhead.

If some error occurs in that frame rendering like a mpeg-2 error that's when things really spin out of control.

Those two examples have been fairly obvious for many years, didn't seem that earth shattering until the HDV problems got heaped on top.

Bob.