Timeline for Old ish motherboard not booting from nvme
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4 at 6:10 | comment | added | Seamus Pitcher | So then should I be able to load the windows boot manager from the HDD and then configure the boot manager to load the boot loader from the nvme drive (thus essentially booting windows from the nvme drive)? When I try this, I get "unable to find /Windows/system32/winload.efi", which I assume is because it hasn't properly initialised the disk yet for reading and writing. | |
| Jul 2 at 15:11 | comment | added | Marcus Müller | it does a chain-loading of an operating system that knows how to read data from nvme devices. | |
| Jul 2 at 13:14 | comment | added | Seamus Pitcher | Thanks for your answer, why would it be possible to load chain-load the windows boot manager (which could reside on the NVME drive, if I'm getting you correctly) from a boot loader (such as GRUB)? Is it something to do with the fact that grub already did all of the "heavy lifting" in making the NVME drive usable by the time it comes time to boot from the windows boot loader, so it isn't actually performing a "cold boot", and already has access to the NVME drive?. | |
| Jun 27 at 9:22 | history | answered | Marcus Müller | CC BY-SA 4.0 |