Almost, the default boot drive is C:, everything gets mapped after that. So if you have a second HDD at D: and a disk reader at E:, any USBs you plug in would go to F:.
Still, I don’t get why’d you do that, all my windows installation automatically put boot files onto C: and did not allow me to touch them afterwards.
G: also seems completely arbitrary, and I’m the majority of windowa setups wouldn’t exist or be an external drive.
Simple as.
Plus Linux doesn’t limit you in the number of drives, whereas Windows limits you from A to Z.
You can mount drives against folders in windows. So while D: is one drive, D:\Logs or D:\Cake can each be a different disk.
What in the world? I don’t think I’ve ever seen that in the wild
It’s common in the server world. KB article on it is here.
For people who haven’t installed Windows before, the default boot drive is G, and the default file system is C
So you only have 25 to work with (everything but G)
G can be mapped after boot (usually to removable drives)
Almost, the default boot drive is C:, everything gets mapped after that. So if you have a second HDD at D: and a disk reader at E:, any USBs you plug in would go to F:.
Why do you copy the boot files from C and put them in G during install then?
I don’t think anybody does that, honestly.
You can have a helper script do it for you (the gui) but it still happening in the background
The boot files go into C:, not G:.
Windows can’t operate if you did that, it doesn’t let you.
Copy Boot Files to EFI Copy the boot files to complete the EFI partition to boot into our windows.
bcdboot c:\Windows /s G: /f ALL
Source: https://christitus.com/install-windows-the-arch-linux-way/
Fijn article, thanks for sharing!
Still, I don’t get why’d you do that, all my windows installation automatically put boot files onto C: and did not allow me to touch them afterwards.
G: also seems completely arbitrary, and I’m the majority of windowa setups wouldn’t exist or be an external drive.
Simple as.
Ok that would make sense tbh