I could easily change the advanced option "show all disks regardless interface" or add a new one to show all volumes, on logical partitions as well.
Just have to figure out what to do with the main boot files, where to place them, rather than dumping everything on the selected volume leave it to the user how that will be started, something I don't quite like. On the question "how and why do I use that" I have no answer yet, maybe you could help. Ditto for installing from a hidden partition, WinPreSetup could be easily modified to mount all partitions before searching for the ISO file, but I still don't understand what could be the practical use of that in order to spend time on implementing it.
Copying files is the trivial part of the whole process, problems are not expected there, nor ever had any, but are when preparing the source, and editing menu files is at the very end of that preparation.
Glad you got it going.
Well regarding the first option it would be useful in a situation like mine: when people want to integrate what your utility has to offer (windows installation from .iso) into an existing boot environment (SYSLINUX with YUMI in my case) but do not want to mess with ImDisk and such stuff.
Regarding the second - this is purely a safeguard. So that anyone who gets passed this flash drive would not blindly copy trash files onto the boot partition (it will simply be not there) but rather do that with first Storage partition. Also, if this partition gets virus infection or anything like that, boot partition will still work.
Boot volume serves only 1 purpose - booting. It should not be used anywhere else (yes I do realize that under Linux nobody will probably give a daym about the hidden flag and it will still show up)
Hope that helps
I got rid of any kind of variables for disks altogether. Just stuffed in all inside the loop you posted.
And %ERRORLEVEL% was introduced too.
Edited by Gear54rus, 01 May 2014 - 02:25 AM.