Drummer

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

Hey Ed, Have you tried the MX Linux code I posted? Please let me know. Thanks, Dave

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

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,...

<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...

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