That's really weird: 2.8+2.16 = 5gb roughly, plus extra files should be around 6gb, no matter if you're using an ISO or USB. Are you sure the USB is properly formatted and not reporting the wrong size?
It's weird but the USB works the aio in all aspects, so I would think it's ok. Like I said copying it will give you the original 6GB worth of files and it won't fit on a DVD5. If you try to make an .iso out of it that will come out as 6GB, too. Must be some sort of weird .esd optimization but not as complete as it is after running the batch.
Genenioo's problem is not the final ISO size. He knows the ISO places the same 3GB ESD file on 2 separate folders but both occupy the same physical space as 1 single file to save space. His problem is that if copying the files from inside the ISO to an USB flash drive, it should also occupy the same 7GB (due to 2x 3GB ESD + extra files) but for some reason it isn't, and even worse, the ESD aren't even equal... I'm guessing that the flash drive is reporting the wrong occupied space, probably due to corrupted file system or something similar.
I think you guys are referring to different things. Fkar's report looks like a normal result using the batch. The .iso 'shares' the space of the two .esds and it burns onto a DVD5 and occupies about 4 GB where on a USB it takes the space of both .esd and thus occupies almost twice the space. What johnye_pt is talking about was the result I got merely changing the .wims in murphy78's aio to .esds (not using the batch), and kind of got the opposite. It would occupy the normal 6GB on a DVD and also when copying the files off the USB but for some reason only reports 4GB under the properties of the USB. No big deal to me; just reporting anomalies in the event people are interested. The batch works great and the USB does, too. By the way I had another idea of just removing the .wims from murphy78's aio and replacing them with .wims run through the batch but that didn't work (ruins upgrade capability--get can't validate key error). I tried this because I don't know how to make an aio with separate x86 and x64 directories like the MCT ones, and the th1 one doesn't give you Home and Pro together, thus limiting upgrading capability to the original version you start with. Anyone know a quick way to configure such an aio from the multi-edition th1's?
Not sure how that works. I've never added anything to the description in the wimlist--just once edited it to conform to the original descriptions. Possibly johnye_pt can help you with this. Did the rest of my post help clear things up at all?
When imagex adds an image to install.wim, only the NAME field is changed. I then make the batch run through all images inside install.wim and compare each NAME with the last added description, and if it finds a match, it uses imagex /info to update the remaining info. Possibly the parenthesis might be interfering with the comparison line. I'll use your wimlist.txt this weekend to try to reproduce the error and fix it