Quoth perdurabo, on Tue, 22 Mar 2005 12:38:08 -0800: > >From then on, you will get the BSOD where you can ascertain what > driver is causing the crashes. Visio/any other modern app shouldn't be > corrupting files like that, so it leads me to believe that its an hdd > controller driver/hardware issue. This is true for any OS, even the > mighty Linux, where I discovered an aggravating, obscure > kernel/SATA/XFS bug that trashed any file it touched.
I rather doubt it's a hard drive issue, and in fact I think I may after all have fixed it by swapping in an old video card of mine (a Viper 7700): no reboots since then. But you're right, Visio shouldn't be corrupting the file like that. Who's to blame? In doubt of your IDE controller theory, I'm left to think Visio is editing the file on the fly, holding it open in invalid states. > BTW, Microsoft didn't write Visio. They recently bought it from > another company. As of the latest version, about all they've done is > just s/oldcompanywhosnameicantrecall/microsoft/g'd the source. Knew that, thanks. I was using it before it was M$'s, and it was then pretty much the same tool. Someone else really needs to come up from behind and kick Visio's arse, if you track me. --Jason -- Due to management cuts, the light at the end of the tunnel will now be switched off. _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
