Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.hardware > #3496
| Message-Id | <59lloh-942.ln1@aretha.foo> |
|---|---|
| From | Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> |
| Subject | Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops |
| Newsgroups | comp.os.linux.hardware |
| Date | 2021-06-03 10:44 +1000 |
| References | (2 earlier) <728f01bc-2b95-4a06-9a4e-b49558b70531n@googlegroups.com> <s22ldc$15v$1@dont-email.me> <s23h9p$1bk6$1@gioia.aioe.org> <3a71037c-45c3-45c3-8c7e-e1650c6aa091n@googlegroups.com> <s94gjb$8gd$1@dont-email.me> |
Groovy hepcat Henrik Carlqvist was jivin' in comp.os.linux.hardware on
Tue, 1 Jun 2021 03:29 pm. It's a cool scene! Dig it.
> On Mon, 31 May 2021 14:39:21 -0700, Wojciech Zabolotny wrote:
>> I have noticed that the problem is time-correlated with Windows
>> updates. I have found an interesting material about Windows trashing
>> the GRUB-based multiboot configuration:
>>
https://www.windowsphoneinfo.com/threads/now-mswin-will-trash-your-grub-
> just-by-booting.314139/
>>
>> Now the question is, how I can prevent it.
>
> The easiest way to prevent Windows from doing stupid stuff with your
> hardware is to avoid booting Windows on your hardware. Instead of dual
> boot, you can boot Windows in a virtual environment like qemu or
> virtualbox. On the other hand, if you really want to give Windows
> access to your hardware (like the graphics card if you need gaming
> performance in Windows), you can instead boot Linux in a virtual
> environment and hope that future Windows upgrades will not mess upp
> your virtual installations.
Another solution, which is the one I use, is to put Wind-oh!-s on a
second hard drive. Grub can remap the order of the drives so that you
can boot that dud system... if you really must. That way, if Losedows
messes with the MBR, it'll be messing with the MBR of the second drive,
leaving your grub installation alone on the first.
--
----- Dig the NEW and IMPROVED news sig!! -----
-------------- Shaggy was here! ---------------
Ain't I'm a dawg!!
Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar
Refreshing of BIOS FLASH memory - a cure for old computer that stops to boot? Wojciech Zabolotny <wzab01@gmail.com> - 2021-03-06 10:18 -0800
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Bob Martin <bob.martin@excite.com> - 2021-03-07 07:37 +0000
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Wojciech Zabolotny <wzab01@gmail.com> - 2021-03-07 01:33 -0800
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2021-03-07 13:45 +0000
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Andrew <Doug@hyperspace.vogon.gov> - 2021-03-07 22:41 +0100
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2021-03-07 17:45 -0500
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Scott Alfter <scott@alfter.diespammersdie.us> - 2021-03-16 19:10 +0000
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Wojciech Zabolotny <wzab01@gmail.com> - 2021-05-31 14:39 -0700
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Wojciech Zabolotny <wzab01@gmail.com> - 2021-05-31 14:47 -0700
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2021-06-01 05:29 +0000
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2021-06-03 10:44 +1000
Re: Refreshing of BIOS FLASH memory - a cure for old computer that stops Andrew <Doug@hyperspace.vogon.gov> - 2021-06-04 11:44 +0200
csiph-web