A few months back I made an awesome custom multi boot drive using the awesome 'easy2boot' tool by Steve, it worked perfectly based on using iso files mostly. I recently got a new jump drive and instead of copying everything directly over, I noticed e2b has been updated and supports uefi now if you use a new image partition thing Steve has developed (kudos to him btw great developer), so I am updating my setup as I am loading the new drive.
anyway in my testing of the new way he has to easy2boot working, I see it dose some fancy partition mapping and prevents access (sort of by design due to necessity of what is being accomplished) to the normal files on the e2b drive.
Problem is most of my bootable environments look to that as I keep a mass of driver packs there for maximum pc support (6gigs of drivers), to add them to the image of each environment that uses them would be highly redundant and prevent normal windows from also benefiting if some driver is missing.
Doing some research I found a way to make a removable drive have 2 partitions, and found a filter driver that masks the removable disk as a local disk.(it works in 64 bit pe3, found another same folks supposedly for 32 bit haven't tested yet, oddly full windows says better driver already present and wont load it but I have an idea how to deal solve not the problem but the effects that I care about) However in various PE3 builds I need this driver (a ini & sys file) to find a very particular flash drive (the one its booting from) and get loaded as its driver by some manner of scripting.
Alas I don't know how to even attempt to install a driver via script much less detect the proper drive, I suppose it could be hard coded some how via device ID or something, any help on this would be Greatly appreciated.
Attaching the 64 bit drivers (I know where to find but have not yet procured the 32 bit drivers)(ok apparently only the ini as the .sys file isn't allowed to be uploaded...)