hallo, VB 6.01 installiert mit extension pack., vhd datei hinzugefügt: vM bootet nicht. versuch cd hinzuzufügen misslingt, da angeblich nicht verbunden. bootreihenfolge auf cd geändert bringt nichts. win 10, 32 iso auf usb stick kopiert> wird jetzt als "cd" angenommen (sata port 1), win 10 wird bei start in VM installiert,,,aber: beim start der VM startet nur windows bis zum desktop(leer) , die eingebundene VM (sata port 0) wird nicht berücksichtigt. was mach ich falsch? gruss und dank!
log datei wurde erst ohne dateierweiterung seitens virtBox gespeichert. nach hinzufuegen hats geklappt? nein , zu groß,,, jetzt gezippt
VB 6.1.32 mit ext. pack VM bootet nicht oder nur win 10
VB 6.1.32 mit ext. pack VM bootet nicht oder nur win 10
- Attachments
-
- PC32-2022-02-20-17-47-02-log.7z
- (22.73 KiB) Downloaded 9 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VB 6.1.32 mit ext. pack VM bootet nicht oder nur win 10
You need to add a CD/DVD drive to the VM recipe if one is not already present. You will then be able to mount CD images (ISO files).
It must be said that it isn't clear to me why you are talking about CD's while discussing a VHD file. CD/DVD images are ISO files. VHD files are hard disk images, you can't mount them in a CD drive.
It seems that you have a VHD file of unknown origin, do we even know that it is intended to be bootable? In order to be bootable the VHD must have boot sectors and an Operating System installed on it. And unless that Operating System was installed into a VirtualBox VM there is no guarantee that it will ever run in VirtualBox.
The file name "Gamer-PC.vhd" suggests that you might have an image of a physical (gamer) PC created using Disk2VHD or similar. In that case you might get further if you enable EFI support in the VM settings, since a modern disk image is almost certainly from a UEFI/GPT system. Be warned that a Windows 10 image will lose activation when moved to new hardware (a VM counts as new hardware).
It must be said that it isn't clear to me why you are talking about CD's while discussing a VHD file. CD/DVD images are ISO files. VHD files are hard disk images, you can't mount them in a CD drive.
It seems that you have a VHD file of unknown origin, do we even know that it is intended to be bootable? In order to be bootable the VHD must have boot sectors and an Operating System installed on it. And unless that Operating System was installed into a VirtualBox VM there is no guarantee that it will ever run in VirtualBox.
The file name "Gamer-PC.vhd" suggests that you might have an image of a physical (gamer) PC created using Disk2VHD or similar. In that case you might get further if you enable EFI support in the VM settings, since a modern disk image is almost certainly from a UEFI/GPT system. Be warned that a Windows 10 image will lose activation when moved to new hardware (a VM counts as new hardware).