Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux > #81454

Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board

Show all headers | View raw

On Sun, 4/27/2025 8:43 AM, bad sector wrote:
> On 4/25/25 12:42 PM, Paul wrote:
>> On Fri, 4/25/2025 8:33 AM, bad sector wrote:
>>
>>> That thick brown morass just keeps getting deeper and deeper...
>>>
>>> Were it not that the circumstances make this chore important to me I would long ago have tossed the whole thing out into the dump bin; that, alas, is not the case.
>>>
>>> So I caved in and bought Macrium (all-in-all close to $100cad) ......but can't even install it because the only window that boots is w7 but it doesn't have sha-2 and w10 is the one I want to salvage because it doesn't boot. Anyway, to get sha-2 I had to do another update but then the sha-2 update bombed on reboot and keeps reverting to 'uninstalled'. Still I managed to INITIATE a Macrium install before rebooting but could never complete it. It never ends for crissssake!
>>>
>>> Things have changed. This rentalware gets licensed to ONE computer so I think I will re-install a w-10 freshie this evening on my Ryzen box and take it from there beginning with making a rescue-CD.
>>>
>>
>> Unless they removed it, the link I gave you was for a free version
>> of Macrium. You didn't have to buy it. For example, if you had
>> a Win7 32-bit as your daily driver OS, you could install the
>> second link here if you wanted. The filename is reflect-setup-FREE...
>>
>> The three artwork links, correspond to the usage of this software.
>>
>>     https://download.macrium.com/reflect/v7/v7.3.6284/reflect_setup_free_x64.exe
>>
>>     Name: reflect_setup_free_x64.exe
>>     Size: 115,719,576 bytes (110 MiB)
>>     SHA1: B6724C7B6F5AF146406FAAA78F845A6C281D67D8
>>
>>     There is also a 32-bit one. For 32-bit setups.
>>
>>     https://download.macrium.com/reflect/v7/v7.3.6284/reflect_setup_free_x86.exe
>>
>> Use the three artwork links, for details as to how to fill out the dialogs.
>>
>> The 64-bit one, and Rufus, should be able to make a UEFI boot
>> stick. The 32-bit one looks a bit more of an issue that way.
>>
>>     Paul
> 
> It may have seemed like I was ignoring your advice but I was just staging for a 1st attempt with macrium. Ran into all manner of problems like my w7 legacy box not even knowing what wifi is in an environment that offers only 3 possibilities
> 
> 1 wifi hotspot off my phone
> 2 usb tether off my phone
> 3 radio link past my ethernet connected router
> 
> ALL of them useless in bad weather but after updating to the Crosshair board's ethernet driver #3 worked for a short while before packing up due to heavy rain. Enough complaining :-)
> 
> I had all your posts and images printed and laid out in front of me as I set out to test my luck. Session-1 running on the legacy-BIOS box was *not exactly a waste of time*. After having figured out that the w7 was a 64bit job, I ran the 64bit RESCUE against both w7 and w10 on a copy of disk-2 (the one with the 2 windows on it).
> 
> After clearing a few chickenshit items on w7 the run against w10 ended up failing but with some comments. It seems that some OS version mismatch is at fault (see wallpaper on my 1st EFI desktop).
> 
> https://imgur.com/WbDgBFZ.png
> 
> There's more over-my-head in this than if I were in the Titan but just a wild guess: the legacy-BIOS w10 locked up like a paranoid clam when I tried to boot it on an EFI machine, subsequent repair attempts failed because the installer was another 'version'? And what will MS do if I send them the dump, send my dead son an email in three months to attempt a repair with the builder dvd (no idea where "I" would find either that email with a failed w10 or the dvd)?
> 
> 
I'm seeing some Win7 and Win10 numbers there.
The Win10 era thing is doing the repair ? It really
should be able to detect legacy and UEFI boot. The
only thing I can think of, is maybe the Win7 was 32 bit
and the UEFI EFI contents are 64 bit, and the repair
isn't happen about trying to circle the squares on
mixing Win10 and Win7 at the same time ?

I probably don't test enough 32-bit combos, to know about
an issue like that.

Normally, when doing forensics, if the original machine
was 4GB or less, that gives the user an incentive to
install 32-bit. If the machine was, say, 16GB, they would
want to use all the RAM, so they would go with the 64-bit OS.

From the Macrium rescue CD booted, it would look like this. This is
an older reference, but still captures the essentials.

   https://reflect.macrium.com/help/v5/rescue_cds/fix_boot_problems.htm

You can see another example of the things you can attempt with
the Rescue CD, here. Putting the boot menu back at the end, is
pretty cheeky. I suppose it saves on doing some touchup with
bcdedit, to put Descriptions back and so on.

   https://www.tenforums.com/tutorials/85198-use-macrium-reflect-rescue-media-fix-windows-boot-issues.html

You could take a picture of the disk being repaired, with "gnome-disks",
so there's at least a hint what is in the mix.

Only when a disk like that boots, do you get decent labeling of
the partitions. But using "diskpart.exe" and assigning letters
to hidden partitions, you can "CD" to a hidden partition and
list the files in there.

  Paul

Back to alt.os.linux | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-12 19:50 -0400
  Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-12 20:40 -0400
    Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-13 22:42 -0400
    Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-22 16:40 -0400
      Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-23 09:38 -0400
        Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-24 00:23 -0400
        Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-24 03:52 -0400
        Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-25 08:33 -0400
          Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-25 12:42 -0400
            Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-25 23:01 -0400
            Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-27 08:43 -0400
              Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-27 11:20 -0400
  Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-14 04:27 +0000
    Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-14 03:29 -0400
    Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-14 06:03 -0400
      Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Paul <nospam@needed.invalid> - 2025-04-14 08:16 -0400
        Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-14 23:38 +0000
        Re: migrate triple-booting legacy-BIOS Linux-w7-w10 to EFI board bad sector <forgetski@_INVALID.net> - 2025-04-14 20:44 -0400

csiph-web