Thanks for taking the time to write your feedback. I will try to address the points:
1. Remove all of the dummy help files. And merge all read-me files into a single read-me file.
Well - originally there weren't any files scattered around. But then people did 'stupid' things like put windows installer isos in the \_ISO\WINDOWS folder (instead of the appropriate sub folders), etc. So I added these extra files to get the message across.
I could delete them all as they are not needed, but I would have deal with lots of people asking why certain things didn't work. Besides what harm are they doing and you can always delete them if you don't like them.
2. Don't create autorun.inf and icon files. It clutters the root of the drive and is just annoying.
Many people like the icon appearing on the E2B drive in Explorer.
Rufus uses the same thing.
You can always delete them if you don't like it.
(although they do cause false positives for some AV programs!)
3. Create a main/master config script that will allow users to define their image folder location, if they want a different folder organization. Don't hardcode everything. This tools needs to be flexible.
I had considered this but:
1, How do I document it - 'copy the iso to whatever folder name you happened to have chosen'
2. The Zalman/IODD needs all ISOs to be in folders below \_ISO - this is why I chose the \_ISO folder specifically. I don't like the name either, but we are stuck with it if we want to support Zalman\IODD drives
3. Consistency across different users E2B sticks
4. Difficulty - to soft-code the images folder is bound to cause many bugs because it is embedded in 100's of places. I had considered it a couple of times, but I am sure it would introduce loads of bugs due to the complexity.
4. The directory and file struct should be changed. Current structure is non-intuitive and you get lots of questions like: where should I put X, what is the difference between folder A and folder B, etc.
Actually I get very few Q's about that.
Many people like the arrangement of ready-made menus and menu folders. It makes it easy to know where to place ISOs, etc.
I don't see how anyone is going to know what they are supposed to put in a menu called 0000 or a find that more user friendly than having specific menus for AV, backup, utilities, Winpe, etc.
Granted that the WINDOWS and WIN folder names are somewhat obtuse! I would prefer to rename the WINDOWS folder to WIN_INSTALL, but it is too late now. If I changed it, then anyone who updates E2B would be in trouble!
E2B also has menu headings in different languages because they are pre-defined.
If a user has 100 ISOs, how will he know where to find the one he is looking for?
E2B allows you to make your own menu folders and you can delete any you don't want.
The Windows Installer folders need to be in a 'known' location because they need special treatment.
Only critical files in root - three extra .cmd files will be present in the root and a readme.txt. They are there so people can easily find them. You are welcome to delete them. Equivalents are in the \_ISO\docs folders.
your \easy2boot\bin is equivalent to the current \_ISO\e2b folder.
re. XML answer files should be same name as ISO file. - but this would limit you to one answer file to one ISO! The whole point of E2B is that you can use one ISO and use any XML file (install home, pro, different partitioning, different SDI_choco configs, etc.).
If there are any XML files you don't want - simply delete them.
You can also create a .mnu file for any windows iso+XML file. That way you won't be prompted to choose a key or XML file, it just runs whatever menu entry you select.
If I could start again, I would change the folder structure a bit, but it is too late now.