someone_else

You can do a All-in-one x86 + x64 ISO with Win Tools, but I think you shouldn't bother. Various reasons: -It's unlikely it will be small enough to fit in a DVD. I have a Ultimate x86 + x64 ISO (without any additional updates/addons/drivers and without SP1) that is around 4 gigs, for example. Will everything fit in 700 megs? hmmmmmm..... -DVD are slooow. DVDs are soo old school these days. Any computer that isn't 10+ years old can boot from USB, and any USB memory device (even HDDs) is pretty damn faster than any DVD. On the net you can find plenty of guides and programs to place your Win 7/8 ISOs on a bootable USB drive. The best so far seems to be YUMI since it allows you to multiboot and add tons of other useful tools in your USB drive. For the older BIOS that refuse to boot from USB, you just need a CD with plopboot. -I'd rather not make a All-in-one x86 + x64 ISO, since to do that most programs (and I think this one as well) let you decide the "main" WIM and add the other on top of that. This means you can use the ISO to install both, but does not allow you to use the ISO to troubleshoot/repair the added WIMs. That is, if you add a x64 WIM on top of a x86 WIM you can install both, but when it's time for fixing something, that's a x86-only disk. (and the same if you do the reverse). -------- My personal project (that brought me here) is to make two ISO files able to install all flavors (from starter to Ultimate, a fully-updated/addon/driver x86 and a fully-updated/addon/driver x64, then make a multiboot USB with YUMI to fit both on the same drive allowing both to be used for installation and troubleshooting, while being also bundled together with other useful tools like DBAN, Memtest, Offline NT password and registry editor, and a Linux Puppy just in case.

First, I'd like to have the "load all the stuff there is in this folder AND subfolders" there is when selecting drivers when selecting Addons and Updates as well. There is stuff tucked away under multiple subfolders in Updates and it's annoying to select them all. Second I'd rather not add invalid drivers to the list, even if marked in red, it only generates confusion imho. If you want to say "hey you are loading wrong drivers" it's better to add a error window like you have for wrong updates (maybe with a list of wrong stuff since drivers tend to be lots and lots). Now, I'm not saying I cannot live without these, but it would be cool.

Request filled

another question about how it handles drivers, the all-in-one integrator seems to load all drivers I point it to, even x64 ones when the WIM is for a x86 architecture. (while for example it loads only Addons for the right architecture) Then color-codes them in the window, red most x64 drivers, blue-gray-ish some x64 and x86 drivers, white most x86 drivers and cyan some x86 drivers. What do these color mean? (Yes, I can guess, but I'd like to get first-hand info) Also, does it integrate x64 drivers in a x86 WIM? I'm kinda sure they won't work (while x86 drivers on a x64 WIM should work). Btw, I'm making a hopefully dumb-proof "Use of the All-In-One Integrator" guide (with pics! and will post it in Guide section), since the documentation about this program is a bit too sketchy for its own good.

I just finished downloading the Win 7 Ultimate x86 iso, I extracted it in a folder and began working on it with the first step of AIO integrator (which is the WIM manager). Now it shows me a list of images, each is one of the various Win flavours. (STARTER, HOMEBASIC, HOMEPREMIUM, PRO, ULTIMATE), and each has a "stated" size of a round 8 GB (which sounds a bit weird since everything combined in that folder is less than 3 Gb). Let's say I want to make a ISO that can install each one of these flavors. I click on "remove ei.cfg", and that allows me to do that. Good. Now let's say I want to make an ISO that also contains addons, patches and drivers I downloaded. I remove ei.cfg, And then what WIM do I choose to get what I want? All? Only the ultimate? Does the same apply for unattended files? (i.e. if I want to have all flavors run unattended do I need to make enough unattended files for every flavor?)

Ok, using a win 7 iso I had around just to play with it. I seem to have found the issue. It does not like the drivers being into 7zip archives. Once they are extracted it loads them by just pointing at the folder containing their subfolders (which is awesome). Now, can you add this detail here or add something to let the program work with 7zip archives as well? It would be very useful for noobs. :please:

I have looked around and downloaded Win Toolkit, which is unbelievably awesome. I have also downloaded all Win7 driverpacks (both 86 and 64) from the same site Win Toolkit tells you to take them. I'm still downloading Win 7 ultimate x86 and x64 Isos. Now, if I wanted to place the abovementioned driverpacks into my win 7 iso do I have to use their utility (driverbase or somesuch) or there is a Win Toolkit function for it? If there is can you tell me where it is (and maybe make it more apparent?)