Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Windows and motherboards
- Date: Mon, 28 Oct 2024 00:25:40 +0000
- From: Raymond Wan <rwan.kyoto@example.com>
- Subject: Re: [tlug] Windows and motherboards
- References: <CAAhy3ds28w++AhmxUHmaMSXvnrsvuc=1NeONx8Kncj2CsHLtSg@mail.gmail.com> <76db8dbd-c995-422f-8dea-26c7d2b675f0@jp.sometwo.net> <CAFNLySuk4jS2Ftn+v7Afhjo4AUqObjGKrX9XTFoa1=1_6YK36Q@mail.gmail.com>
On Sun, Oct 27, 2024 at 12:17 PM AbH Belxjander Draconis Serechai <belxjander@example.com> wrote: > I have *never* had Windows boot on any rebuild without the CPU+Motherboard and drives being the same combination. > > If I remember correctly, this was doxumented *published**behavior* ever since the Windows95 original release on floppies and CD. I think I have, but I can't remember how long ago was it. Perhaps I am remembering it incorrectly. Having said that, recently, I was able to install Windows into a virtual machine and move that virtual machine (running under either QEMU or Virtualbox under Ubuntu) to another computer. And, it ran fine. So...this means that the Windows-based VM is somehow fooled and/or when installed on a VM, it no longer cares? Since we can clone a drive and save it as a VM drive, I wonder if it can be somehow fooled the same way? Of course, not something I have the time to figure out "for fun". Only if work requires it will I go down that rabbit hole again... Ray
- References:
- [tlug] Windows and motherboards
- From: Raymond Wan
- Re: [tlug] Windows and motherboards
- From: Furkan Mustafa
- Re: [tlug] Windows and motherboards
- From: AbH Belxjander Draconis Serechai
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] linux installed on lenovo ideapad
- Next by Date: Re: [tlug] linux installed on lenovo ideapad
- Previous by thread: Re: [tlug] Windows and motherboards
- Next by thread: [tlug] Call for presenters Nov 9th
- Index(es):