To me it seems to be better to keep the sources genuine MSDN/VLSC (i prefer publicly downloadable source iso, like windows10 iso/techbench).
yeah updated post, it finally went. I think it was just giving me big ones because I abused the hell out of it yesterday lmao I've mirrored in my sig.
The size of SW_DVD5_WIN_ENT_10_1607_64BIT_English_MLF_X21-07102.ISO is 3,910,021,120 The size of Iso from esd is 3,866,384,384 The different between them is 43,636,736 bytes. It will be greatly appreciated if somebody's here who have both the files above ( esd iso and msdn iso ), make the svf patch. Of course if none, i'll have to get the msdn iso. Thanks
esd is encrypted, it will be enormous. Its not the size difference for SVF, its the bit for bit difference. the ESD is totally different in bits than the iso, even if both contain the exact same thing. if one file is 1234 and another is 1235 the difference is the 5 (Small patch) if one file is 1234 and the other is 4567 the difference is the 567 (big patch) esd to iso is like 1234 XYQF
the reply by EFA11 is very good. i would like to add a bit. the real reason why "iso from esd" to msdn iso SVF didnt exist here is because we deduce that different computer that generates ISO from same ESD might have different SHA-1 hash. of course i havent tested, maybe because i dont have time nor motivation to do it. we need to prove the feasibility of ESDISO to MSDNISO SVF first before it can be done. idea to think about ============= computer A generate ISO from ESD using ESD decrypter computer B generates ISO from same ESD using the same eSD decrypter. 1. we need to confirm iso generated by computer a is same with computer B with SHA1 hash or MD5 2. if its different SHA1, where is it different? we use file splitter to split it into multiple blocks and hash all the blocks, and get to know which part is different (different block will have different hash) 3. then we need to ask everyone that will use the "esdiso to msdniso" SVF to download the different blocks. if u ask me, there already too much work.....
I thought iso from esd has the same exact file with msdn iso, the differs only "something" that generated differently by each computer and generates different hash. Esd iso file is 1234x5 msdn iso file is 1234y5 The different should be x and y, But judging from the comment i get, i guess it may not be possible atm. ------- The Initial File ( iso from esd and msdn iso) which vsf recognize might be differ because of different hash, then the vsf will be useless because there'll not be same hash generated from esd->iso per computer I thought two files with same exact size ( different hash ) may works with vsf. ------- Thanks anyway...
totally dependent on the content of the files, not the size. 2 exact size files can result in a larger file than both. But I think you guys have grasped the basic idea of it now anyway. Still, iso to esd would be very big file. You are best to get the MSDN file. We can make SVF to different MSDN files much better.
hm...i think i get your point now.. [vsf 1] Hash from 1st comp esd iso -> msdn iso is 1234x5 [vsf 2] Hash from 2nd comp esd iso -> msdn iso is 1234y5 [my comp] Hash from 3rd comp esd iso is 1234z5, then vsf1 and vsf2 will be useless in my computer, because the initial esd iso file is different from the beginning. Thanks anyway for the explaination...
@crazeann If MSDN = 123456 and I have 1234x6 and you have 1234y6 It doesn't matter that we have different parts (x != y). Your patch (y -> 5) can be applied on mine ISO, and my (x -> 5) on yours. Because offset from beginning of the file is the same. But the problem is that size of your file mismatches with mine This means that ESD->ISO conversion even worse than I thought The End