Actually, no. This is a very tough problem to correct depending on your configuration and installation disks. It is a Windows operating problem, as I recently experienced it on my daughter's laptop and it took me about two weeks to solve. Someone pointed me to a computer tips site, but I don't remember which one. I'm pretty sure you can Google missing (and) the name of the file and it will bring up the best sites to start you off. There are about four options to repair the problem, depending on, as I said, your configuration and original Windows installation disks. Hopefully you will find a solution that you can implement quicker than I did. Best wishes! Valerie On 4/4/05 8:51 AM, "Jim Robertson" <jamesrob at sonic.net> wrote: > On 4/4/05 6:39 AM, "Robert Nicholson" <robert at elastica.com> wrote: > >> Well it is pathetic to have ended up in a non-bootable configuration >> just because I had to reset via the power button. >> >> Can you imagine that happening in OSX? > > I'm sure you're frustrated, but you should remember two things: > > First, it was your Macintosh that locked up and needed rebooting. > > Second, what was corrupted and wouldn't work afterwards was information > ordinarily handled by a Macintosh program (the Windows emulator). So, > perhaps VPC isn't as robust as it should be. I don't think one can cite this > as yet another example of how the Mac OS is more robust than Windows. It's > entirely possible that Intel Hardware would have handled this crash with no > problems whatsoever.