JasonCoder
Golden Member
Hoping one of you has some insight for me...
I have a Vista x64 system that's been running like a champ since pretty much the release of Vista. I have some Hyper-V work I need to do. So my bright idea was to build an external e-sata enclosure and boot from this whenever I need to work in Hyper-V. The WinSrv2008 R2 setup went good and I noticed it added an entry to the boot loader.
Everything works fine, I choose WinSrv2008 R2 from the boot menu and I boot off the e-sata. Then I unplug the external HDD and try to reboot into my original Vista internal setup... says it can't locate the winload.exe. Huh? All I did was unplug the e-sata drive. After some momentary panic I found the I could still boot into Vista with the e-sata plugged back in.
I'd rather not have to have the e-sata on and connected every time I want to boot into Vista. If anyone has any insight that would be great. I've done some reading on BCDEdit, etc. but not quite making the connection yet.
Thanks.
I have a Vista x64 system that's been running like a champ since pretty much the release of Vista. I have some Hyper-V work I need to do. So my bright idea was to build an external e-sata enclosure and boot from this whenever I need to work in Hyper-V. The WinSrv2008 R2 setup went good and I noticed it added an entry to the boot loader.
Everything works fine, I choose WinSrv2008 R2 from the boot menu and I boot off the e-sata. Then I unplug the external HDD and try to reboot into my original Vista internal setup... says it can't locate the winload.exe. Huh? All I did was unplug the e-sata drive. After some momentary panic I found the I could still boot into Vista with the e-sata plugged back in.
I'd rather not have to have the e-sata on and connected every time I want to boot into Vista. If anyone has any insight that would be great. I've done some reading on BCDEdit, etc. but not quite making the connection yet.
Thanks.
