This might help you to develop a script: https://www.tampermonkey.net/ In that you so easily edit and delete my postings you should be able to edit email postings of others.
Use the same approach you use to edit and delete my postings. Record each step: key pressed, option selected. Then try to write a script that walks you through those steps for next time. As a forum moderator on other forums I sometimes edit posts too; correct spelling for future seaches, spam links, bad words but rarely delete them unless they are spam.
Did you change it recently? Did it clear up Rob's thread? If not, you should do it manually.
While responding to postings is convenient using email, especially for members traveling, the responses can include all prior postings because of the way email works. It would be helpful if the forum admin would delete the old email portions in the email replies, making the threads more readable, and reflecting on the attention to detail he has with his app. Creating a script to do it would be perfect.
It would be helpful if you post the iso parms your using to boot each of the isos Rob. BTW Tails is indeed another Linux system. Tails is based on Debian GNU/Linux.
It would be helpful if you post the iso parms your using to boot each of the isos Rob.
So Rob, did you get your MX iso to boot?
The MX code you posted is basically the same parms I always use. And even with a new fresh download the MX iso is classified as unfound. In that I boot others isos from the same ISOs folder on the same drive I doubt the problem is a grub2 one. I suspect it's a MX bootparm ISO problem.
Dave, I am aware of how g2win searches for the isopath and set root, but boot parms like from= and findiso= sometimes need the root drive in the parm's isoparm. ISO booting is complicated. Ed
Hi Dave, I suspected the "Not" was a typo. But it could have had a word missing: "Not included ". Typos in comments or code .... I don't agree $isopath variable must reflect the location on the system other than the directory. The root value should handle the drive. But if used in bootparms iso references may require the root and isopath variables.
"Not that your Grub2Win EFI files will be upgraded to level 167." ??
So, anyone going to post the iso menu?? I did an actual defrag, so the app says, on my SSD NTFS Data drive and my iso boot still yields Drive Not Found. Gonna try redownloading the iso. If tha doesn't work I'll try copying it to a USB drive and booting the iso from there.
So, anyone going to post the iso menu?? I did an actual defrag, so the app says, on my SSD NTFS Data drive and my iso boot still yields Drive Not Found. Gonna try redownloading the iso. If tha doesn't work I'll try copying to a USB drive and booting the iso from there.
"Try entering the command from a GNU Grub prompt." Ok
"ls ($root)/ISOs/MX*.iso The GNU Grub ls command does not allow * wildcards so it fails." It displays fine in the screen shot I posted. :-)
Any ideas why this menu: menuentry " MX 25.1" --class custom --class icon-isoboot { set isofile='/ISOs/MX-25.1_Xfce_x64.iso ' set kernelpath='/antiX/vmlinuz' set initrdpath='/antiX/initrd.gz' set bootparms='fromiso='($root)$isofile' from=all ' echo root: $root ls ($root)/ISOs/MX*.iso search -f $isofile --set=root loopback loop $isofile linux (loop)$kernelpath $bootparms (loop)$initrdpath } results in this?
Any ideas why this menu: menuentry " MX 25.1" --class custom --class icon-isoboot { set isofile='/ISOs/MX-25.1_Xfce_x64.iso ' set kernelpath='/antiX/vmlinuz' set initrdpath='/antiX/initrd.gz' set bootparms='fromiso='($root)$isofile' from=all ' # bdev=/dev/nvme0n1p7 ' # ('$root') ' echo root: $root ls ($root)/ISOs/MX*.iso search -f $isofile --set=root loopback loop $isofile linux (loop)$kernelpath $bootparms (loop)$initrdpath } results in this?
How does a Windows user defrag their ssd drive Dave? Trim can be done. Old fashion defrag???
I saw Dave. I think trying to boot the iso as an install is a bad approach. Using the /boot/isolinux approach looks more promising.
I understand Rob. And this isn't necessarily a g2wiso problem. In the MX iso there is indeed a /boot/grub/i386-efi folder!!! By the same token, it is named i386-efi not i386/efi. Apparently MX installs a grub2 system, similar to what the Ubuntu iso does.
..../i386/efi/.... !!! I'm pretty sure EFI wasn't even thought of in the i386 days Dave. g2wisoboot may need some work. lol
/i386/efi/ !!! I'm pretty sure EFI wasn't even thought of in the i386 days Dave. g2wisoboot may need some work. lol
Surprised there isn't a set parms= option similar to set isopath=, set kernelpath= and set initrdpath= Dave. Making setparms one word seems inconsistent. 2022 for g2wisoboot is interesting. I know my last grub2win version wasn't current but surprised it was that old. Then again, I've been booting Isos without it for a long time so never had a need for it.
The ISO text looks good Dave. g2wisoboot must be a new function in Grub2Win. I don't recall ever using it in my versions.
I'm happy that Rob's MX link worked for you Dave.
I'm happy that Rob's MX link worked for you Dave. https://i.postimg.cc/65jm7bs4/Screenshot-2026-03-25-173128.png
I'm happy that Rob's MX link worked for you Dave.
I'm happy that Rob's MX link worked for you Dave.
I'm happy that Rob's MX link worked for you Dave. https://postimg.cc/Tpb9F93T
I'm happy that Rob's MX link worked for you Dave. [url=https://postimg.cc/Tpb9F93T][img]https://i.postimg.cc/65jm7bs4/Screenshot-2026-03-25-173128.png[/img][/url]
I'm happy that Rob's MX link worked for you Dave. [url=https://postimg.cc/Tpb9F93T][img]https://i.postimg.cc/65jm7bs4/Screenshot-2026-03-25-173128.png[/img][/url]
I'm happy that Rob's MX link worked for you Dave. [url=https://postimg.cc/Tpb9F93T][img]https://i.postimg.cc/Tpb9F93T/Screenshot-2026-03-25-173128.png[/img][/url]
Only one MX Xfce iso link shown on this MX page: https://mxlinux.org/download-links/ Dave. You shouldn't need a big Diagnostics file to boot an 500MB ISO file. It's not an install.
Hi Rob, Good to see you back. How are you setting the parms for the MX iso menu? Are you using a grub2win option or manually entering them? Your isopath looks ok but the others are way over done. If grub2win is creating the menu you may have to wait for drummerdp to look at his app. If you're looking for a quicker fix to try, I suggest manually editing the $prefix/windata/customconfigs/BootAnISOfile.cfg file with a text editor like Windows' Notepad and making it look like this: set isopath='C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso'...
You've been quiet Rob. Given up or working with MX?
From your grub.cfg file I see: # # Menu Entry For Custom Code 5 Boot An ISO file # # ** Grub will boot this entry by default ** # # Comment 'Boot An ISO file Hotkey=i' --hotkey=i --class isoboot --class icon-isoboot # source $prefix/windata/customconfigs/BootAnISOfile.cfg # The BootAnISOfile.cfg was what I was hoping to see.
What does a terminal command: dir c:/Users show? Do you see the Downloads folder?
Wrong! Just reviewed my iso scripts and found one for an old version of MX The paths are for files IN the iso not ON the harddrive. My old menu: menuentry " MX 23.2 " --class custom --class icon-isoboot { set isofile='/ISOs/MX-23.2_fluxbox_x64.iso' set kernelpath='/antiX/vmlinuz' set initrdpath='/antiX/initrd.gz' set bootparms='fromiso='$isofile' from=all ' search -f $isofile --set=root loopback loop $isofile linux (loop)$kernelpath $bootparms initrd (loop)$initrdpath }
'lo again Rob, I just reread your posting and noticed these lines: Variable isopath is set to /Users/Downloads/MX-25.1_xfce_x64.iso Variable kernelpath is set to c:UsersDownloadsMX-25.1_xfce_x64.iso Variable initrdpath is set to c:UsersDownloadsMX-25.1_xfce_x64.iso Variable bootparms is set to c:UsersDownloadsMX-25.1_xfce_x64.iso and see that your paths are not all the same. And that is the problem. I think c:/Users/ should be in all paths
Hi Rob, A couple of things would help: posting the contents of your iso boot menu that is in the /grub2/grub.cfg file telling us what menu/tool/example you used to create your iso menu. I boot iso files also and have never gotten the error you describe. Have you booted other isos? Ed
A menu that works for me. menuentry " Ubuntu ISO 25.10" --class ubuntu --class icon-ubuntu { set iso="/ISOs/ubuntu-25.10-desktop-amd64.iso" set bootparms="boot=casper iso-scan/filename=$iso nomodeset --- quiet splash " # search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt # echo root=$root # ls ($root) # ls ($root)/ISOs/ubuntu* loopback loop $iso echo Booting $iso linux (loop)/casper/vmlinuz $bootparms initrd (loop)/casper/initrd }
New install or upgrade?
file `/boot/grub/unicode.pf2' not found What I got with this menu: menuentry " minios" --class debian --class icon-debian { set iso="/ISOs/minios-trixie-xfce-standard-amd64-5.1.1.iso" # search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt loopback loop $iso # From ISO's /minios/boot/grub/x86_64-efi/grub.cfg file. # GRUB EFI bootstrap configuration insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod...
file `/boot/grub/unicode.pf2' not found What I got with this menu: menuentry " minios" --class debian --class icon-debian { set iso="/ISOs/minios-trixie-xfce-standard-amd64-5.1.1.iso" # From ISO's /minios/boot/grub/x86_64-efi/grub.cfg file. # search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt loopback loop $iso # GRUB EFI bootstrap configuration insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod...
file `/boot/grub/unicode.pf2' not found What I got with this menu: menuentry " minios" --class debian --class icon-debian { set iso="/ISOs/minios-trixie-xfce-standard-amd64-5.1.1.iso" # From ISO's /minios/boot/grub/x86_64-efi/grub.cfg file. search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt loopback loop $iso GRUB EFI bootstrap configuration insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod...
file `/boot/grub/unicode.pf2' not found What I got with this menu: menuentry " minios" --class debian --class icon-debian { set iso="/ISOs/minios-trixie-xfce-standard-amd64-5.1.1.iso" search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt loopback loop $iso GRUB EFI bootstrap configuration insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod part_plan insmod part_sun insmod part_sunpc search --file...
file `/boot/grub/unicode.pf2' not found What I got with this menu: menuentry " minios" --class debian --class icon-debian { set iso="/ISOs/minios-trixie-xfce-standard-amd64-5.1.1.iso" search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt loopback loop $iso GRUB EFI bootstrap configuration insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod part_plan insmod part_sun insmod part_sunpc search --file...
Have you looked at the minios's grub.cfg file in the ISO's /EFI/debian/ directory? It's almost like a grub2 ISO boot menu! And certainly shorter than the ISO's /minios/boot/grub/grub.cfg file. The /minios/boot/syslinux/bootinst.bat file is an interesting read also.
How did you install the OS Svai? Have you installed it before?
Any booting error messages? Where did you get the menu commands?
A menu that works for me. menuentry " Ubuntu ISO 25.10" --class ubuntu --class icon-ubuntu { set iso="/ISOs/ubuntu-25.10-desktop-amd64.iso" set bootparms="boot=casper iso-scan/filename=$iso nomodeset --- quiet splash " search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt # echo root=$root ls ($root) ls ($root)/ISOs/ubuntu* loopback loop $iso echo Booting $iso linux (loop)/casper/vmlinuz $bootparms initrd (loop)/casper/initrd } The bold lines are menu lines with a # in the front. ie co...
Hey Dave, Did you notice there were none in mine? Can you edit postings? Staying warm? A -2 here last night. On Mon, Feb 9, 2026 at 6:56 PM Drummer drummerdp@users.sourceforge.net wrote: Hey Ed, Perhaps you didn't notice the profanity. Dave Can't install Grub2win Sent from sourceforge.net because you indicated interest in < https://sourceforge.net/p/grub2win/discussion/general/> To unsubscribe from further messages, please visit < https://sourceforge.net/auth/subscriptions/>
A menu that works for me. menuentry " Ubuntu ISO 25.10" --class ubuntu --class icon-ubuntu { set iso="/ISOs/ubuntu-25.10-desktop-amd64.iso" set bootparms="boot=casper iso-scan/filename=$iso nomodeset --- quiet splash " search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt insmod ntfs echo root=$root ls ($root) ls ($root)/ISOs/ubuntu* loopback loop $iso echo Booting $iso linux (loop)/casper/vmlinuz $bootparms initrd (loop)/casper/initrd } The bold lines are menu lines with a # in the front....
A menu that works for me. menuentry " Ubuntu ISO 25.10" --class ubuntu --class icon-ubuntu { set iso="/ISOs/ubuntu-25.10-desktop-amd64.iso" set bootparms="boot=casper iso-scan/filename=$iso nomodeset --- quiet splash " search -f $iso --set=root set root='(hd0,gpt4)' insmod part_gpt insmod ntfs echo root=$root ls ($root) ls ($root)/ISOs/ubuntu* loopback loop $iso echo Booting $iso linux (loop)/casper/vmlinuz $bootparms initrd (loop)/casper/initrd }
This is what I see: I've added these commands to the menu: search -f $iso --set=root echo root=$root ls ($root) ls ($root)/ISOs/ubuntu* loopback loop $iso
This is what I see: [url=https://postimg.cc/WDPdMRBv][img]https://i.postimg.cc/WDPdMRBv/EB0EB9A5-68D7-4E05-B887-8D11D2F27CC6.jpg[/img][/url] I've added these commands to the menu: search -f $iso --set=root echo root=$root ls ($root) ls ($root)/ISOs/ubuntu* loopback loop $iso
When I try to boot Ubuntu desktop 25.10 on my 16 GB RAM system I get an error indicating I'm out of memory. Granted Ubuntu ISO is large, 4.3GB but I have 16GB! menuentry " Ubuntu ISO 25.10" --class ubuntu --class icon-ubuntu { set iso=/ISOs/ubuntu-25.10-desktop-amd64.iso set bootparms=`boot=casper iso-scan/filename=$iso quiet splash ` search -f $iso --set=root echo root=$root loopback loop $iso linux (loop)/casper/vmlinuz $bootparms initrd (loop)/casper/initrd }
Never mind the OP UEFI Firmware menu request. The reason why my boot menu doesn't show my Grub2 system as Grub2 is because Acer systems show grub2 as Linpus Lite. Very, very strange.
BTW & FYI I created a Windows 11 script to install Ubuntu's grub2 system on my 64 bit EFI system. If you're interested I posted it here: https://forum.porteus.org/viewtopic.php?f=39&t=11814&p=104480#p104480 I've created .bat and .cmd scripts for years but creating this one for Window 11 was definitely a learning experience. Windows 11's Powershell doesn't like some old commands.
BTW & FYI I created a Windows 11 script to install Ubuntu's grub2 system on my 64 bit EFI system. If you're interested I posted it here: https://forum.porteus.org/viewtopic.php?f=39&t=11814&p=104480#p104480 I've created .bat and .cmd scripts for years but creating this one for Window 11 was definitely a learning experience. Windows 11's Powershell doesn't like some old commands.
No problem Dave, enjoy your vacation. It's an open question so anyone can respond. :-)
In Windows 10/11 a menu entry like this: menuentry 'UEFI Firmware Settings' { fwsetup } boots the Firmware menu which is useful but it's not the Windows Boot Manager menu that booting with F12 invokes. Suggestions? In my EFI folder are 4 subfolders yet my Boot options only shows 2, I want to be able to add the other 2 as boot options. /EFI /Boot /Microsoft /Windows /Grub2
In Windows 10/11 a menu entry like this: menuentry 'UEFI Firmware Settings' { fwsetup } boots the Firmware menu which is useful but it's not the Windows Boot Manager menu that booting with F2 invokes. Suggestions?
In Windows 10/11 a menu entry like this: menuentry 'UEFI Firmware Settings' { fwsetup } boots the Firmware menu which is useful but it's not the as the menu booting with F2. Suggestions?
I wish Dave. lol Unfortunately that requires working with the grub2 system code directly and I failed trying last summer. Definitely over my head. That's why I took the Ubuntu approach while rebuilding my systems. Where are you going this year? Vacation or work? Ed
abssorb, I posted this option earlier: https://sourceforge.net/p/grub2win/discussion/general/thread/2b0f2358fc/#ba61 No AV problems, no download problems, no delete problems. It may interest you.
Hi Stefan, This option isn't as nice as grub2win but works for grub2 multi-booting. https://forum.porteus.org/viewtopic.php?p=104216#p104216 No restrictions.
This grub2 option may work for you perixious.. Definitely not as pretty as Dave's app but supports multi-booting and has no security issues. :-) https://forum.porteus.org/viewtopic.php?p=104216#p104216
Hello Mdid. The key I found to booting ISOs is searching through the files in the ISO for the boot parms it uses and ending up with things like these possibilities: Possible ISO boot parms: boot=/, from=all, from=$iso, fromiso=$iso, findiso=$iso, iso-scan/filename=$iso, bootfrom=/dev/sda6$iso The $iso refers to the name of the ISO file. hth
This grub2 option may work for you Amir. https://forum.porteus.org/viewtopic.php?p=104216#p104216 Definitely not as pretty or functional as grub2win but works booting Windows and Linux systems on EFI hardware.
Heitor, how are you, and SWS, downloading the preview release of Windows 11? And why are you doing it? Windows' security is very tight. and frequently impacts executable downloads and installs. Check it's security logs.
Check your Windows antivirus logs SWS. Windows' Defender usually blocks Grub2Win.
Hi Sarah, Be sure your notebook is plugged in before going to lunch. If the battery gets low Windows shutsdown the system which requires requires the rebooting after lunch. Ed
Yup! My Windows 11 Defender finds Win32/Sabsik.FLA!ml in it. SOP update.
Yup!