![]() I probably won't be back until next Monday (I have time off from work), but I will check into whatever you guys have. You could try, while it's still in VirtualBox, mounting the VMGUEST.ISO and installing If the error has changed from not being able to find NTLDR, then you've hit the right ARC name but there's another problem, like not being able to read the IDE driver. Since you mounted the VHD/X on your host you should be able to look into disk management to see which partition NTLDR is actually sitting on, but you should also hit itįairly quickly by starting at 1 and counting upward, too. Part - I made an error in my previous post when I said 1). "rdisk" must always be zero for an IDE drive and Hyper-V can only boot from IDE controller 0 (which is the "multi" part), disk 0 (which is the "disk" If you want to stick with it, I can promise that the first three numbers have to be 0. It's been a long time since I've done this and it was a long shot anyway. If you've put a lot of effort into this, then go Brian's path. I am solely responsible for the content of my posts. I am an independent blog contributor, not an Altaro employee. Double-check the entire line, both words and numbers. Since Hyper-V boots from IDE Controller 0 Disk 1, you would change your entries to:ĭon't just swap "scsi" for "multi" and stop. Change the "default" entry and the one that's just like it under. That does not exist, or is at least not the one that you intended. If you've moved the volume from a SCSI controller to an IDE controller but left the boot.ini intact, then it will attempt to boot from a drive SCSI and IDE are very distinct under ARC. Windows 2000 Server used the ARC convention for designating boot paths. Maybe someone else will have a better idea. I haven't had to think about this in a very long time, so take this with a grain of salt. I need to Switch the Windows 2000 VHD over from SCSI to IDE and it should work, but because I get the BSOD, the only thing that works is the Buslogic SCSI Adapter in Virtualbox. NOTE: THIS LINK BELOW DID TAKE OUT THE OLD HARDWARE WHEN I REBOOTED, but it still CRASHES, if use anything other than SCSI "Buslogic". I have tried the instructions here to take out the old drivers and rebooting according to the link below, but it still bluescreens no matter what I do. However, on Hyper-V it won't allow you to boot from SCSI unless you have 2012 R2 and it's on a Generation 2 VM, this is obviously a problem because I need SCSI to be able to boot the image and we are using Windows 2000. I have no issues here when I set Virtual Box to "BusLogic" However, I am having issues with it booting on hyper-V because it has the BSOD, however, I can get it to boot under Virtual Box by using SCSI boot using "BusLogic" SCSI controller. So, I have an application that I don't have any way of updating it or reinstalling it on another new VM. This app happens to be on Windows 2000 and I am trying to do a Physical to Virtual Conversion of it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |