Hehe, one more submenu? The question from me was not asked very clear. Are u seeing any optimization oppurtinities or unneccessary lines in the upper code? btw: the XP_ALL.iso is 600Mbyte big and size-optimized by mkisofs. Extracted more than 2Gb. Interesting is, that my target Notebook with his 1Gbyte ram, is able to map the iso without problems. I thought, the iso is got unpacked during the mapping to the memory. seems to be not or maybe a thing of mkISO_RAMload_sort.cmd? anyway, very cool Edit: If you are using MultiBootIsos (with several Languages, with/without Driverpacks, etc..) u'll get inevitably a ISO more than 1Gbyte, despite the ISO size-optimized by mkisofs. In my Case 1,2Gbyte. Sorting makes neither sense, if you have several installation sources, like in a multiboot iso. So, it would be clever, if you could take the Driverpacks outside the ISO. I think the paths in driverpacks's i386/presetup.cmd must be edited for that. The loop is scanning all drives on the pc(physical hds, flashdisks, the mounted iso...). Would this work? Or am i missing something? Edit2: Just tested, works like a charm. Dont forget, u have to edit the presetup.cmd, which is located in SourceIso/i386 (or whatever). Advantages of outsourcing the driverpack from the iso file: if u have more than one iso with integrated driverpacks, u will save much space on the flashdisk because of the reduced iso sizes. In addition, with smaller iso sizes u can reduce the RAM-precondition.Updating of the driverpacks is much easier, just renew the files on the flashdiskLast but not least: u can use the driverpacks which are on the flashdisk, for postpone driver installation per wihu or so.