Grub2Win Activity
Brought to you by:
drummerdp
Activity for Grub2Win
-
Drummer modified a comment on discussion General Discussion
Hey Ed, The only control I could find on SourceForge was to disallow future email responses to posts, so the user must actually log into SourceForge to post to the forum. This was done earlier today to prevent future email posts. It does nothing to clear up Rob's past thread. If you know how to "clear it up manually" or "create a script to do this" please post detailed instructions . Screenshots of any web actions involved would be most helpful. Please let me know. Thanks, Dave
-
Hey Ed, The only control I could find on SourceForge was to disallow future email responses to posts, so the user must actually log into SourceForge to post to the forum. This this was done earlier today to prevent future email posts. It does nothing to clear up Rob's past thread. If you know how to "clear it up manually" or "create a script to do this" please post detailed instructions . Screenshots of any web actions involved would be most helpful. Please let me know. Thanks, Dave
-
Ed P posted a comment on discussion General Discussion
Did you change it recently? Did it clear up Rob's thread? If not, you should do it manually.
-
Hey Ed, I agree with you 100%. I'm not sure, but I believe the email reply setting is proper now. Thanks, Dave
-
Hey Ed, I agree with you 100%. However, I haven't found any way to do this within SourceForge. Either manually or with a script. If you know the procedure to manage whether postings include prior responses, please send me details. Thanks, Dave
-
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.
-
Grub2Win updated /changelog.legacy.txt
-
-
-
-
-
Rob Lehmann posted a comment on discussion General Discussion
Will gladly do so once back from Sicily. Le mercredi 1 avril 2026 à 16:49, Ed P edphere@users.sourceforge.net a écrit : It would be helpful if you post the iso parms your using to boot each of the isos Rob. Errors in my config to boot from iso file 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/
-
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.
-
Yes, thanx, it does boot, and I am very thankful for everyone’s help. BTW, I have also tried Tails, an OS that keeps you anonymous - as long as you don’t log into specific accounts. Different from Linux, but worth checking. Best. Le mercredi 1 avril 2026 à 06:04, Ed P edphere@users.sourceforge.net a écrit : So Rob, did you get your MX iso to boot? Errors in my config to boot from iso file Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/grub2win/discussion/general/...
-
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.
-
Hey Ed, Have you tried the MX Linux code I posted? Please let me know. Thanks, Dave
-
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
-
Hey again Ed, The whole point of the $isopath variable is that the g2wisoboot function searches for the file in the $isopath variable and sets root automatically. This greatly simplifies things for the user, since booting .iso files can be quite challenging. They only need set the four variables, then the g2wisoboot function takes care of setting root, loopback and everything else. Have you tried the MX Linux code I posted? Please let me know. Thanks, Dave
-
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.
-
Hey again Ed, "Not that your Grub2Win EFI files will be upgraded to level 167." ? This was a typo, should have said "Note" instead of "Not". Fixed this morning and the new level is 168. Over the last couple of days, I have updated g2wisoboot in an attempt to detect these fragmentation errors. g2wisoboot now provides the suggestion to defrag or move the .iso file. Fragmentation errors are now much more common because users don't defrag SSD disks much anymore. Note that even after I defragged the partition,...
-
-
-
"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
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hey Ed, Try entering the command from a GNU Grub prompt. It fails for me every time. Dave On 3/27/2026 12:28 PM, Ed P wrote: <meta http-equiv="content-type" content="text/html; charset=UTF-8"> "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. :-) Errors in my config to boot from iso file Sent from sourceforge.net because you indicated interest in...
-
"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. :-)
-
Hey Ed, Couple of observations on your menuentry. ls ($root)/ISOs/MX*.iso The GNU Grub ls command does not allow * wildcards so it fails. You should add a loopback -d loop before your loopback command to prevent duplicates. As to why the file is not found. I have no way to tell without directory listings etc from your system. Hope this helps, Dave
-
Hi again Rob, I'm going to continue this through email instead of web postings. The posting thread is getting too long for me to find messages easily. Also this is very specific to your particular machine. Dave
-
What is the ' the /boot/isolinux approach'? Can I try it, somehow?
-
Thanks Dave. I uninstalled the previous version before installing the new one, It does not install properly - apparently because I use a W11 Preview build (26220 to be precise) for which it has, of course, not been tested. The Grub2 folder is installed, but no way to run Grub2Win, nor is there a desktop icon. Maybe we should quit here, because I cannot waste your time to make your great software work on a particular W11 version, just because it is what I use. Otherwise there will be thousands of...
-
Thanks Dave. I uninstalled the previous version before installing the new one, It does not install properly - apparently because I use a W11 Preview build (26220 to be precise) for which it has, of course, not been tested. The Grub2 folder is installed, but no way to run Grub2Win, nor is there a desktop icon. Maybe we should quit here, because I cannot waste your time to make your great software work on a particular W11 version. Otherwise there will be thousands of guys with specific personal requests...
-
Thanks Dave. I uninstalled the previous version before installing the new one, It does not install properly (apparently because I use a W11 Preview build (26220 to be precise) for which it has, of course, not been tested). The Grub2 folder is installed, but no way to run Grub2Win, nor is there a desktop icon. I think we should quit here, because you cannot waste your time to make your great software work on a particular W11 version. Otherwise there will be thousands of guys with specific personal...
-
Thanks Dave. I uninstall the version I have before installing the new one, and let you know, Best.
-
Thanks Dave. Should I uninstall the version I have before installing the new one, please, or just download and install the new one? Best.
-
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???
-
Hi again Rob, After considerable research, I think I have identified the problem. It appears that the filesystem where your .iso file resides is too fragmented for GNU Grub to read. This is a known bug in GNU Grub which hopefully will be fixed soon. I have just uploaded version 3.0.2.3 of Grub2Win which detects this error. Also, the g2wisoboot parameters have changed slightly. I have attached new custom code for you to test. If you still get the kernel read error, you will have to move your .iso...
-
-
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.
-
My config: EliteBook745G5 Processeur AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx (2.20 GHz) OS 64 bits, processeur x64
-
Hey Ed, The 386 messages are from the GNU Grub kernel, not Grub2Win or g2wisoboot. There is a library called i386-efi included in GNU Grub. This is likely because the GNU Grub kernel initializes in 32 bit mode then later switches to 64 bit mode. So some error messages early in the process show as 32 bit. The i386-efi module implies 32 bit operations. The pre EFI library is named i386-pc. 'Nuff said. Dave
-
Hey Ed, The 386 messages are from the GNU Grub kernel, not Grub2Win or g2wisoboot. There is a library called i386-efi included in GNU Grub. This is likely because the GNU Grub kernel initializes in 32 bit mode then later switches to 64 bit mode. So some erroro messages early in the process show as 32 bit. The i386-efi module implies 32 bit operations. The pre EFI library is named i386-pc. 'Nuff said. Dave
-
..../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
-
Thanks very much. I get this (see attached). I did "Select ISO File" with the green button.
-
Thanks very much. I get this (see attached).
-
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.
-
Hey Ed, The g2wisoboot function was introduced to Grub2Win in 2022, so four years ago. It is documented in the Advanced Topics section of Grub2Win help "ISO File Boot". I just realized that I need to update the Ubuntu URL's in that help text. Will be fixed tomorrow. Thanks, Dave
-
The ISO text looks good Dave. g2wisoboot must be a new function in Grub2Win. I don't recall ever using it in my versions.
-
Hi again Rob, I made some changes to your custom code and it seems to work well now. There were a couple of errors in your code. Grub at boot time uses forward slashes / not back slashes \ setparams is a command, not a variable The updated code is attached. You should copy it as your custom code for the ISO. I had to guess at your isopath. The easiest way to set it is to click the green "Select ISO File" button when you edit the custom code. It should set up the isopath properly. Please let me know...
-
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]
-
I am in no hurry at all, be assured. And very thankful for your precious help. It can take the time it needs, no pb at all.
-
I am in no hurry at all, be assured. And very thankful for your precious help. I can take the time it needs, no pb at all.
-
I am in no hurry at all, be assurer. And very thankful for your precious help. I can take the time it needs, no pb at all.
-
Hey again Rob, Thanks, I got the diagnostics and have downloaded the correct .iso from your link. It may take me a day or so to set up your environment and figure this out. I'll keep you posted. Thanks for your patience, Dave
-
Hey again Rob, Thanks, I got the diagnostics and have downloaded the correct .iso from your link. It may take me a day or so to set up your environment and figure this out. I'll keep you posted. Thanks for your patience, Daver
-
Sorry, then I misunderstood the Diag procedure. I'll do it right away. As for the iso file, it is from here: https://sourceforge.net/projects/mx-linux/files/Final/Xfce/MX-25.1_Xfce_x64.iso/download. Diag file is now uploaded.
-
Hey Ed, There are several downloads on that page. I want to be sure of the exact URL so as not to waste time on assumptions about which one was actually downloaded. Several desktops are there as well. The diagnostics file typically runs well under 1MB, usually about 200KB. So not a "big Diagnostics file" at all. It takes a minute or two to run the diagnostics and upload. It contains the relevant configuration info to understand where the failure is. Again, I don't want to make assumptions, the diagnostics...
-
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 again Rob, I really need the full diagnostics as it includes data about your BCD, hardware, EFI listings and Grub2Win configuration files etc. The partition list is useful, but not nearly enough to diagnose your issue. This is crucial to help fix your problem. I need the full diagnostics. I'm not sure I understand about "entering info manually" to run the diagnostics. All that is required is an email address so I can contact you and a couple of lines describing your issue. Your email address will...
-
Thanks so much for your help. The iso is the latest from the MX Linux site. Clicking on Diagnostics in Grub2Win opens a window where I am supposed to enter info manually. Is there another way to run diagnostics ...? All I got is the attached drive info.
-
Hi Rob, Let's see if we can get this resolved. Please run the Grub2Win diagnostics and send them to me. This will give me info on your partitions, hardware configuration etc. I also need a link to the site where I can download the .iso file you are trying to boot. Then I can download the .iso and re-create your environment to assist you. Please let me know. Thanks, Dave
-
Thanks so much for your help, I hope he will help. Best. Le mardi 24 mars 2026 à 20:00, Ed P edphere@users.sourceforge.net a écrit : As I'm sure you see in the email version of your thread with my prior posting, drummerdp is back to deleting online postings. LOL Eventually he may try to answer your Grub2Win problem. Good luck. Errors in my config to boot from iso file Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/grub2win/discussion/general/ To unsubscribe...
-
I have not been able to locate $prefix/windata/customconfigs/BootAnISOfile.cfg. Furthermore, applying your script inside Grub2Win generates the same error: Grub did not find a root partition with file /Users/Downloads/MX-25.1_xfce_x64.iso Maybe I need to write /Utilisateur/Téléchargements/MX-25.1_xfce_x64.iso. rather than /User/Downloads/MX-25.1_xfce_x64.iso ?
-
I found and modified BootAnISOfile.cfg. Same problem.
-
I have not been able to locate $prefix/windata/customconfigs/BootAnISOfile.cfg. Furthermore, applying your script inside Grub2Win generates the same error: Grub did not find a root partition with file /Users/Downloads/MX-25.1_xfce_x64.iso But the correct isopath, such as scripted, is /Users/Utilisateur/Downloads/MX-25.1_xfce_x64.iso. Why does it say /Users/Downloads/MX-25.1_xfce_x64.iso when the script says /Users/Utilisateur/Downloads/MX-25.1_xfce_x64.iso?
-
I have not been able to locate $prefix/windata/customconfigs/BootAnISOfile.cfg. Furthermore, applying your script inside Grub2Win generates the same error: Grub did not find a root partition with file /Users/Downloads/MX-25.1_xfce_x64.iso But the correct isopath, such as scripted, is /Users/Utilisateur/Downloads/MX-25.1_xfce_x64.iso. Why does it say /Users/Downloads/MX-25.1_xfce_x64.iso wheen the script says /Users/Utilisateur/Downloads/MX-25.1_xfce_x64.iso?
-
I have not been able to locate $prefix/windata/customconfigs/BootAnISOfile.cfg. Furthermore, applying your script inside Grub2Win generates the same error: Grub did not find a root partition with file /Users/Downloads/MX-25.1_xfce_x64.iso But the correct path is /Users/Utilisateur/Downloads/MX-25.1_xfce_x64.iso.
-
ok, thanks so much. I try this and let you know asap. Best. Le dimanche 22 mars 2026 à 21:13, Ed P edphere@users.sourceforge.net a écrit : 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...
-
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'...
-
Maybe I can adapt the script above to my situation ...?
-
Not at all 😁 Catching up. Thanks so much. Will get back to you. Le dimanche 22 mars 2026 à 06:45, Ed P edphere@users.sourceforge.net a écrit : You've been quiet Rob. Given up or working with MX? Errors in my config to boot from iso file 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/
-
But dir c:/Users/Utilisateur shows the Downloads folder.
-
This is my custom code for the iso boot: set isopath='C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\boot\isolinux\' # The Selected ISO File is C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso set kernelpath=C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\antiX\vmlinuz # Example set kernelpath=/vmlinuz set initrdpath=C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\antiX\initrd.gz\ # Example set initrdpath=/initrd.img setparams 'C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\EFI\BOOT\'...
-
Also, we have a jetlag, I am in France.
-
This is the custom code for the iso boot: set isopath='C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\boot\isolinux\' # The Selected ISO File is C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso set kernelpath=C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\antiX\vmlinuz # Example set kernelpath=/vmlinuz set initrdpath=C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\antiX\initrd.gz\ # Example set initrdpath=/initrd.img setparams 'C:\Users\Utilisateur\Downloads\MX-25.1_Xfce_x64.iso\EFI\BOOT\'...
-
see file attached
-
Not at all - linuxforever. Just catching up, sorry.
-
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?
1 >
