Several of us have had disagrements with daniel in the past…especially regarding windows systems
That is OK . I just dont want it to get heated.
Agree to differ . It is that easy.
Daniel does have more in depth knowledge than most of us.
FWIIW: I triple boot Linux, with secure boot on. One current (13), one backup and one testing other distros (LMDE at the moment). I run Windows (as far back as XP for a database program that won’t run on current W11) in virtual machines. We run VMware (both Workstation and ESXi). Some Debian updates bork the Workstation application from starting (with a less than helpful error message). Fortunately, an FAQ outlines how to use a MOK to sign the modules during the next reboot (host system). Nuisance, but works. I have been known to bork up the system boot order, efibootmgr and grub-customizer to the rescue. I don’t recall ever dual booting Windows and Linux in the 20 years or so running Linux, started with a box edition of SUSE.
Will it not run on lmde using wine or bottle ?
I don’t think I ever tried. I did try a few programs with Wine (codeweavers version) and was less than impressed. I still support some programs I wrote for a client, including that database program. But, you are right, I should give that another look. When I can get a round tuit.
No excuse here is one I prepared for such an occasion
Just in case someone did not understand the words
There is also distrobox … run the XP in a container rather than a VM.
It ain’t broke…
The thing I noticed is that Windows doesn’t like sharing its disk with another os.
It would be wise to put a different os on another disk, including its EFI partition. Otherwise some update of Windows is going to “update” the contents of the partition sooner or later and the only os you can boot is windows.
I’m talking from bitter experience here.
2 of my friends hade the same thing you did Xander and its well known that Windows do this some times. and its amazing that Microslop get away so easily with what they do.
Sorry. just cannot see your point here, has more to do with common sense on how to run Windows and Linux on the same PC, has nothing to do with Microsoft!! This is nothing new, Windows and Linux on the same disk, will eventually bite you!! I also speak with a few years of experience, but do not take my word, try it!! If you must run Windows, and I do, then keep it isolated on it’s own PC, Linux can be ran on older PC.s than Windows will ever touch!! Just like this Dell XPS that is happily running Gentoo!!
no its not Common sense microslop does with some of their updates do so you cant use the distro you dual boot with,you can look it up your self its well known .
??? No, but it should be common sense for anyone to keep Windows and Linux isolated!!
Whether it is common sense or hard earned experience does not matter.
Just keep advising people not to do it unless they have the experience to cope with a boot failure.
Just had that experience recently, but it was just after installing Win 11 on my PC with Linux on it. Not sure if it was because of the install or an update of Win later. I jump over to Copilot to ask about my Linux OS. Windows 11 had actually changed the boot order in BIOS to boot Win first. Copilot told me the fix and it was an easy one. The simple change was to place Linux first in the boot order.
After that, grub came up and all was fine.
I dont understand what changing the boot order in the bios would do to grub?
In my bios there are direct uefi boot entries as well as grub boot entries. Is yours like that ? Maybe you needed to put a grub boot entry first?
When installing Windows alongside an existing GNU/Linux installation, Windows places it’s boot-loader first in the boot order so it will boot as if it’s the only installed OS. While it doesn’t mess with or corrupt the previously existing grub boot loader, until you set your grub boot loader to be first in line you’ll never see the grub boot loader onscreen. After making that change, you must also update grub to add Windows to it’s boot menu.
Does windows use uefi direct boot. ?
Or is there a Windows bootloader?
Linux can boot with either efi or grub, but most people use grub.
My bios boot list shows both the efi direct boot, and the grub boot entries. … it can be confusing.
On my system, Windows uses what’s identified as the Windows Boot Manager, so based on it’s name, I suspect that it’s Windows own boot loader.
I tend to agree with my namesake - i.e. in my experience - when I did dual boot - I had Windows (XP and/or 7) on a separate physical disk to Linux… And I did see / experience where some service pack would trash grub…
So I stopped even relying on grub too… I’d select which disk to boot from the BIOS to get to Windows or Linux…
But that was a loooong time ago… I haven’t dual booted since 2012/2013 (which co-incided with Valve making a Linux native Steam Client, and top shelf game titles available in Linux native versions…
i.e. only ever have one Linux distro installed at any one time…
If I want to play with / test other distros - VirtualBox or QEMU/KVM…
