XPost: uk.comp.os.linux   
   From: user@example.net   
      
   On 15/04/2024 15.56, Java Jive wrote:   
      
   > However, after modifying the partition table and reimaging all the   
   > partitions, W7 wouldn't boot, complaining that 'a device needed was   
   > unavailable' or something similar.  I tried fixing it using the W7 DVD,   
   > which has always worked in the past, but the problem remained, so, as a   
   > temporary fix, I ran a repair from the Windows 10 boot, which did allow   
   > me to boot into Windows 7, but by a desperately convoluted process, viz:   
   > choose the GRUB Windows 10 option, which almost completely boots W10   
   > before giving an option to boot into W7, which if you choose reboots the   
   > PC from scratch going straight into W7.  And next time you want to boot   
   > into W7 you have to go through the whole rigmarole again.   
      
   I would say your "fix" was in the win10 bootloader and the reason why   
   it's generally recommended to have each mswin on it's own HDD is that   
   you can disable it in the BIOS and do repairs on another mswin without   
   affecting the other installations.   
      
   Alternative would be use KVM or XEN, then you know the instance will not   
   see any other devices than those assigned to it, running the repair will   
   not affect any other installation and you don't have the risk of mswin   
   taking over mbr from GRUB. The other benefit is that you don't have to   
   dual boot, for hardware rendered 3D graphics you would need a dedicated   
   graphics card for the guest you want to be able to run at the same time   
   (if you have the cash there are those graphics cards that allow you to   
   have vGPU, which is a good thing if you have multiple guest needing   
   hardware rendered 3D graphics or CUDA).   
      
      
   >   
   > Writing the above prompted me to check the GRUB configuration of the   
   > machine that works.  The file /etc/default/grub is exactly the same, but   
   > the resulting /boot/grub/grub.cfg is different in the specification of   
   > the two menu options.  Here, both have the drivemap option, and further   
   > the GUIDs, as I presume they are, differ in the 'if' statements:   
      
   If you haven't cloned the partitions from the other computer (this tend   
   to work poorly with the closed source OS), then the UUID will be different.   
      
   I hope you don't have network drivers for the ms-winxp (EOL 2014-04-08)   
   and ms-win7 (EOL 2020-01-14), don't care if something happens to you,   
   just thinking of everyone else.   
      
   --   
     //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)