OS/2, eCS & ArcaOS - Technical > Setup & Installation

UEFI: Dual Boot - Windows 11 and ArcaOS 5.1

<< < (9/10) > >>

Dave Yeo:

--- Quote from: Rich Walsh on November 02, 2023, 08:40:17 pm ---
What really amazes me is that seemingly no one has tried to simply use 'os2ldr.efi' to boot a BIOS-based install in the exact same fashion as a UEFI install. Had they done so, they would have found that all text-mode output is hosed: inital bootup messages and all full-screen sessions are just colored dots at the top of the screen. However, the Desktop comes up just fine and Win/OS2 works as well. The fix I referred to above (if it still works) simply restores text-mode video. Neil has my instructions on how to do so. If it works, I'll post them in a new thread.

--- End quote ---

Tried this, the BIOS install came up at 640x480, which stuck when I rebooted through airboot and used the screen object to fix.

Neil Waldhauer:
Rich, your instructions do work, and I can boot ArcaOS 5.0 directly from rEFInd.
I can also boot ArcaOS 5.1 directly as I did before.

As you pointed out, DOS window does not work in ArcaOS 5.1, and it never worked in ArcaOS 5.0. This is fine for me, as I rarely use DOS.




Rich Walsh:

--- Quote from: Neil Waldhauer on November 03, 2023, 02:22:31 am ---Rich, your instructions do work, and I can boot ArcaOS 5.0 directly from rEFInd.
I can also boot ArcaOS 5.1 directly as I did before.

As you pointed out, DOS window does not work in ArcaOS 5.1, and it never worked in ArcaOS 5.0. This is fine for me, as I rarely use DOS.

--- End quote ---

Just to confirm: "success" means you can see whatever messages are displayed during bootup and that you can open full-screen DOS and OS/2 sessions. Is that what you see on both the 5.1 and legacy installs? And yes, if DOS windows didn't work under 5.0, they shouldn't work under this arrangement because you've reverted to 5.0-style video support.

OS4User:
I was recently shown such a layout on ESP:

--- Code: ---EFI
    BOOT
        LAUNCHER.CFG
        LAUNCHER.EFI
    WINDOWS
        {all stuff without changes}
    OS2
        OS2LDR.BIN
        OS2LDR.EFI
    QSINIT
        qsinit.efi
        qsinit.ldi

--- End code ---

Here is no bootx64.efi at all.

LAUNCHER.CFG:

--- Code: ---[menu]
ArcaOS (C:) = \EFI\OS2\OS2LDR.EFI C:
Windows 11  = \EFI\Microsoft\Boot\bootmgfw.efi
QSINIT      = \EFI\QSINIT\qsinit.efi

--- End code ---

Rich Walsh:

--- Quote from: OS4User on November 03, 2023, 08:43:33 am ---I was recently shown such a layout on ESP:
[...]
Here is no bootx64.efi at all.

--- End quote ---

BOOTX64.EFI is a fall-back that is only used if:
* the firmware finds an ESP that has no entries in its boot list but does have this file
or
* the firmware is booting an MBR disk, in which case it always boots this file regardless of the boot list

Basically, the firmware assumes that if it is looking at an MBR disk, it must be a removable disk (i.e. USB stick or the like) that is being used to install an OS. This isn't unreasonable given that 99.9% of all UEFI installs are to GPT disks while most install media are still MBR.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version