I erased stuff from yesterday but will do over to check your questions. They were both 3GB. They almost have to be the same because I copied the same file into the x86 and x64 directories. Apparently, it's something that's preventing the 'sharing' that sees them as one. Could it be the fact that I used a combination of WIMs/ESDs, so using all wims might work?
It should work with any combination of ESDs and/or WIMs. This is what the batch does: 1. move DVD\x??\sources\install.esd or install.wim to WIM\, renaming if necessary 2. convert WIM\*.esd to WIM\*.wim, renaming if necessary 3. create wimlist.txt from the WIM\*.wim 4. created install.wim from the wimlist.txt <- should be around 4GB or 5GB 5. convert install.wim to install.esd <- should be around 3GB 6a. copy install.esd to DVD\x64\sources\ 6b. move install.esd to DVD\x86\sources\ 7. make Win10_AIO.ISO ISO from DVD\ Try running the steps one by one and see if they're doing what is supposed to be doing.
I have a flash drive that I put it onto from yesterday. They're both 3,177,425kb--the hashes match. I did it step-by-step and it all seemed to work. Again, you're way ahead of me on this but is it something that the .iso is not "sharing" them the way it should? As I said, using even my modified guide yesterday gave me a 4GB .iso.
If both install.esd files have the same hash then yes, the final ISO should be using the optimization ( -o ) feature, which makes identical files occupy the same physical space on the ISO. Are you using cdimage 2.53 included in the 7z? If yes, then the problem must be on step 7, that's when cdimage is used.
Yes, I'm using cdimage.exe 2.53. I think I got it from a different place but here's the SHA-1 hash: 69225FCE2C34B20BF4791D94B2533B7FCF772D20. When it did the optimization with the batch file it reported only a 2% shrinkage where when I used the guide a week or so ago I remember something like a 45% shrinkage.
Try opening a command line, change to the folder where the batch is, then run: Code: TOOLS\x86\cdimage.exe -u2 -udfver102 -bootdata:2#p0,bDVD\boot\etfsboot.com#pEF,ebDVD\efi\microsoft\boot\efisys.bin -o -lWin10_AIO -t10/30/2015,12:32 "DVD" "Win10_AIO.ISO"
Re-doing it with all WIMs, converted to those from the original download and from Edu and Ent. Will use the code just above instead of step 7.
Since the batch supposes that you have the MS aio (separate x86 and x64 folders) I'm not sure that it would be easy to skip that step (unless you could recreate it otherwise). Did you ever get the disc made and try to boot it on a UEFI system?
Wow! Now that's weird! Suppose if I use it again I'll just use the command line. What was your thinking giving it to me if it was the same? Would there be any relation to the problem using all WIMs instead of ESD/WIM combos I used the first time (you seemed to think not before)? Also, don't know what you could change in step 7 in the batch if it's the same. Thanks so much for everything--I finally have my ultimate aio!
That's great that your English is so good. I've always admired people who could speak more than one language (one of the very few things I admired about George W. Bush!). I've always wished I could but have never put in the effort that's necessary. Spanish would of course be the logical choice for me living in So. California, even though I've always really liked French (I almost failed the one semester of it I took in college!). I was a very poor English student in my early years in school but then worked on it and ultimately it became one of my best skills and most enjoyable subjects.
Nope my C drive is not large enough and no enough space for the MCT to do its stuff which btw it's a shame this tool doesn't have an option to change drive for its working folder. Anyway I grabbed a spare HDD to install Win8.1 for the sole purpose of creating such disc with double architecture, I'll be testing later tonight
Nah, if I've learned a bit in life is that every person who is very skilled or talented on doing something is due to intellectual capabilities. Environmental factors does matter I could agree but it's the person itself and his brain For instance, I've been trying for lustrums to achieve some medium level of technique on shred guitar (metal guitar) and my limited talent suffocates me
I played around with another aio with the separate x86 and x64 directories--a th1--and it also worked. There was something I noticed both times it worked so I was wondering if it would give you any clue. Both times when creating the .iso the percentage would kind of stall at 95% or 96% and then finish where I believe (not 100% sure) that when it didn't optimize as we wanted it went smoothly to 100%. Again, I could be wrong, but if this is true I was wondering whether it might tip you off as to what the problem might have been. By the way, this .iso was 8,193,761,280 bytes and now is 4,664,119,296 and looks like it will just fit on a DVD5. Has a lot of stuff--here's the wimlist: x64,Core,Windows 10 x64 Home,10240,1,install.wim x64,CoreN,Windows 10 x64 Home N,10240,2,install.wim x64,CoreSingleLanguage,Windows 10 x64 Home Single Language,10240,3,install.wim x64,Education,Windows 10 x64 Education,10240,6,install.wim x64,EducationN,Windows 10 x64 Education N,10240,7,install.wim x64,Enterprise,Windows 10 x64 Enterprise,10240,8,install.wim x64,EnterpriseN,Windows 10 x64 Enterprise N,10240,9,install.wim x64,EnterpriseS,Windows 10 x64 Enterprise 2015 LTSB,10240,10,install.wim x64,EnterpriseSN,Windows 10 x64 Enterprise N 2015 LTSB,10240,11,install.wim x64,Professional,Windows 10 x64 Pro,10240,4,install.wim x64,ProfessionalN,Windows 10 x64 Pro N,10240,5,install.wim x86,Core,Windows 10 x86 Home,10240,1,install(1).wim x86,CoreN,Windows 10 x86 Home N,10240,2,install(1).wim x86,CoreSingleLanguage,Windows 10 x86 Home Single Language,10240,3,install(1).wim x86,Education,Windows 10 x86 Education,10240,6,install(1).wim x86,EducationN,Windows 10 x86 Education N,10240,7,install(1).wim x86,Enterprise,Windows 10 x86 Enterprise,10240,8,install(1).wim x86,EnterpriseN,Windows 10 x86 Enterprise N,10240,9,install(1).wim x86,EnterpriseS,Windows 10 x86 Enterprise 2015 LTSB,10240,10,install(1).wim x86,EnterpriseSN,Windows 10 x86 Enterprise N 2015 LTSB,10240,11,install(1).wim x86,Professional,Windows 10 x86 Pro,10240,4,install(1).wim x86,ProfessionalN,Windows 10 x86 Pro N,10240,5,install(1).wim
My v10240 also has the same 22 versions in pt-PT and it's 4.05 GB (4*351*574*016 bytes), probably the language files are smaller hence the 300mb difference. The v10586 has 18 versions and it's 3.89 GB (4*187*179*008 bytes), so it's small enough to fit on my bootable fat32 flash drive and replace both untouched x86 and x64 that I have there, saving me 2.38 GB of space. XP is also on one CD ISO, I was using grub with a menu to choose between Home and Pro but recently discovered there was an official MSDN CD which both Home and Pro, it uses a different boot from the other XP ISOs. I only wish I could do the same with Vista and 7, and with that I mean a UEFI/MBR bootable ISO with all versions, without patching files and below 4GB. That way there would be only one ISO for each Windows version: XP Home/Pro, Vista SP2 AIO x64/x86, Win7 SP1 AIO x64/x86, Win8.1U AIO x64/x86 and Win10 b10586 AIO x64/x86. I wonder if I can mix them with some files from the Win10 ISO?
That th1 .iso I shrunk seems to work fine unless I try to upgrade with it in which case it gives me a Windows failed to validate the product key error and of course won't continue. The original .iso burned onto a dual layer DVD works fine as well as all the ones we've done with the batch file. I did a little research and got a suggestion to add an ei.cfg file to the sources directory, but that didn't help either. Any ideas? Appreciate your help.
Did you integrate any keys in the indexes? Or used a ei.cfg? The wrong ei.cfg would be a probable cause for the error, in 7 and 8.x it is. Edit: I don't use ei.cfg in any of my big 10 AiO iso's. And only integrate the gVLK in enterprise editions because of the eula it will get if I don't. So the iso can be used by legal users (insert the 10 key at initial setup to autoselect the edition to install), for upgrade and pirates.
No, didn't integrate any keys but it's a huge Win 10 aio (see back a few posts). If I integrate a key (you mean a .pid?) wouldn't that limit upgrading to just the version that the key is for?