查看文章 |
Windows Vista 如何使用ghost 对Vista RC1系统使用ghost恢复后,重新启动会出现winload.exe错误,解决办法参考了msdn上面的一篇文章http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=181082&SiteID=1 Vista and Symantec Ghost 8.x Ever since build 5231, I've found myself unable to use Ghost (8.0 or 8.2) "as I've always been able to". By which I mean with 5219, XP, 2000, etc., I can just create a partition backup, restore a partition backup, no muss, no fuss, all successful. (I have an XP-compatible boot manager, have four independant partitions that are always hidden from one another, and I restore just one partition based on what OS/test/scenario I need to create.) Now with 5231 and later, creating a Ghost image of a partition always results in the "unable to access \windows\winload.exe" (or whatever that exact full-screen message from the Vista boot manager is). Regardless of whether I'm restoring back to exactly the same partition as I backed up from, etc. If I perform a DISK backup and then perform a DISK restore AND use the -FDSP switch, I can bring back my Vista 5270 image successfully. But still cannot just bring back Vista into a single/specific partition. What is the "unable to access \windows\winload.exe" error actually trying to tell me? I've been scrolling through all the BCDEDIT data and options trying to put together a scenario that makes sense. Is SysPrep going to get me out of this, or is there something more simple I could do given that I'm not restoring to a different machine or anything; just trying to bring back a partition that was working for me previously. FWIW, I guess since Ghost has it, there is some scenario where -FDSP was necessary even previously. In my own experience, I've never had to modify Ghost's default behavior. I just perform a partition backup, restore the partition backup, without any special/additional switches, and this works great for XP, 2000, NT 4.0, etc. Thanks for any insight. Yes, I've been playing with XIMAGE too, but only concerned with what approach might work with Ghost in this thread. -Alan
|