Clover startup.nsh content rules?

[sambul13]

Hello,

I'm trying to boot NVMe drive hooked on a card to PCIe-2.0 slot on a legacy Windows 11 PC with BIOS Gigabyte Mobo using Clover. I tried several Clover releases, and found that r5070 boots OK from ISO via boot7 renamed as boot file, and recognises my NVMe every time. But after preparing a USB thumb with BDU tool using same r5070.iso, the thumb boots to Clover but doesn't see my NVMe drive.

I tried using the following commands in shell, and the loaded at Clover startup NVMe driver finally connects to the NVMe, maps it and boots OK :
reconnect -r
map -r
fs0:\efi\boot\bootx64.efi

Now I want to execute the script automatically upon the thumb boot. I tried to modify Clover config.plist, but googled that map -r command can't be used in it. I then created startup.nsh file with the above commands and saved it in EFI\Boot or _EFI_ folder, but Clover ignores it at startup, and stops when trying to run the file in shell from Clover UI.

How I can modify the startup.nsh so Clover can autorun it successfully upon boot? Changing letters to Capital in path doesn't help. Should I load shell with it first? Is there any guide or discussion about that file content and usage? Why nothing mentioned about that file in Clover Manual?

startup.nsh
reconnect -r
map -r
fs0:\efi\boot\bootx64.efi

[SergeySlice]

Newest boot6/boot7 does contain NVMe driver. Not revision 5070.

[sambul13]

@SergeySlice
Newest boot6/boot7 does contain NVMe driver.

Of course you know better, but can't test all available Mobos. I tried ALL published Clover releases, and found just 3 or 4 older releases that recognise the NVMe drive hooked to my legacy Mobo GA-EP45-UD3P PCIe 2.0 slot.

Current release v5164 (if it's newest for you) doesn't auto recognise my NVMe drive with this Mobo, but it can be manually reconnected to NVMe driver from Clover shell. In contrast, booting Clover V5070 from Ventoy, if successful, shows my NVMe drive in Clover UI and can likely be set as Default with timeout 0.

It looks like Ventoy may be setting NVRAM with proper drive entries, since booting only v5070 via boot7 from flash drive prepped by BDU tool doesn't show the NVMe drive in Clover UI, though it can start from shell.

It looks like v5164 needs some work to support more popular legacy BIOS Mobos like mine.

[sambul13]

@SergeySlice
Not revision 5070

What I suggest is may be to enable support for startup.nsh and post some guide, so various old Mobo users won't bother you, but rather modify that file as needed. I read that Clover config.plist doesn't support map -r command, so some workaround must be suggested to auto map the reconnected drive without using startup.nsh