You don't get duplicate entries. When you scan with, lets say, autoiso.g4b the command is autoiso.g4b .automenu /_ISO and in autoiso.g4b it has a line for wich extension to scan for, in this case .iso. I duplicated autoiso.g4b changing the string to (ie:) .gz and it scans that. As for ima and img, they are the same (just rename extention) so i opt for gz files usually to compress them and not have to worry about the img\ima difference. I also had to have a corresponding mnu for it in the menu (mainmenu), an lst "backup" (29k), and the blank mnu menu header. I unfortunatly rewrote all your code to my liking so all the paths and directories are different, but the actual changes for added functionality are so small it easy to implement.
First, my menu looks like this. I have my default menu added to main.mnu (menu.mnu in my case), i eliminated autoiso dir and just use _iso, but with an img dir added. From entry 20 (chameleo.iso) down it is just autoiso generated iso entries (no img or gz).
http://i49.tinypic.com/2mhv7ex.png
If you select entry 11 (boot iso files) it looks like this after scanning \_ISO
http://i50.tinypic.com/ak7nzm.png
If you select entry 15 (boot gz file) it looks like this after scanning _ISO\IMG
http://i50.tinypic.com/35b5l4m.png
And my layout of files is very different from your package, but only really in the file names and paths for organizations sake.
http://i45.tinypic.com/2aigdvt.png
If you want me to send you my grub4dos dir i can, or post an indepth example of one of my changes i can. This really is a great approach and i don't mind helping you to make it better and more robust for the masses.
Edit: I also want to mention that the main reason that led me to rewrite your file names are because of errors i was getting. I am using the newest grub4dos (grub4dos-0.4.5c-2013-04-01) and do most of my testing in VMware from ISO (i briefly worked for VMware). I noticed when it lists isos it truncates the names to 8 letters. When i tried to run some of your mnu menu entries, it would often give an error for 2 reasons.
1: Files (lst, mnu, g4b) with a number (like easy2boot) wont load (file not found). By removing the "2" it works.
2: Files (lst, mnu, g4b) longer than 8 characters would complain of file not found. Shortening them to 8 or less charachters would work.
By fixing these errors i ended up having to scour your code and ended up understanding it and learning its approach. After awhile, i ended up rewriting it all to make the layout less cluttered and logical. So, i hope you don't take offence of me rewriting everything, i did it purely to make it work and be more organized. After that, i tried to add features.
Do you ONLY test via USB, or from an iso too? Im wondering if i am the only one getting these errors, or if you simply don't know they exist because you primarily test via USB.
Also, if it matters, i boot to the bcd menu first, then chainload grub4dos as i still come across old hardware with USB1 drivers and grub4dos can take minutes to load, whereas the bcd is instant. I use bcd, grub4dos, Grub2, syslinux, isolinux, and EFI bcd, EFI grub2, EFI clover, loaded via EFI refind from a 32 gig usb with a 30 gig ntfs partition, and a small 1 gig fat32 second partition for EFI, and use the bios to decide which partition i boot to..
Edited by halikus, 03 April 2013 - 09:50 PM.