Hello all, Sorry for bumping this thread, but it pertains to it, and it seemed best to reply here. I have the en_winme_full.exe, SHA1 hash D4B5A202D116FED20CE8279C035BFC2D480E7590, that I extract to a folder and use CDIMAGE to create the ISO. However, when I go to use the provided xdelta patch MSDN to Retail, it fails because my source is invalid. My sha1 hash, of 5FBC08C8F24623E24019D7836472FEE386720546, doesn't match the one listed of 7e13981281e3a08416bb94fec654c176f3a891e5. What am I doing wrong? Best regards
common errors: 0. your source is wrong ? (i dont find sha-1 1D4B5A202D116FED20CE8279C035BFC2D480E7590) post (upload) win9x\w9xsetup.bin from your en_winme_full.exe. and 1 hash-file fom all files inside en_winme_full.exe 0.a your cdimage version is wrong ? (i use a9cc81d821e1de3ac4fd0beb3173a4e230ae7bcb *cdimage-2.39.exe) 1. you use the wrong timezone setting ? (before iso create) 2. you use wrong cdimage settings? (post your settings) 3. you total mismatch your source and your xdelta patch MSDN to Retail (did you exact know wich version is en_winme_full.exe - 101_rtm_cd, winme_102_rtm_cd, 111_msdn_cd, 112_stepup_cd, or 115_oem_cd (boot) 4. e.g if your patch is for a 115_oem_cd you need also a valid boot sector file (its not included inside en_winme_full.exe) give more info
A dump of all hashes from my source iso can be found here: h xx ps dl.dropboxusercontent.com/u/108284406/en_winme_full_iso.html Also, w9xsetup.bin here: h xx ps dl.dropboxusercontent.com/u/108284406/w9xsetup.bin (Sorry for the improper link, I need 20 posts first.) Could be my CDIMAGE-2.39.exe, as mine has hash of F613C539290BD7B89387A4B9248276E6BBF57F3D I'm doing this on a test box that is running Windows XP SP3. I do not know if I am supposed to change the time zone on Windows? I am using the -g setting on CDIMAGE. cdimage -l"Windows Me" -t6/8/2000,17:00:00 -h -j1 -g0 WINMEMSDN WINMEMSN.iso I do not know which version it is. Supposedly it is from MSDN/TechNet? It has a msbatch.inf inside the win9x folder. The en_winme_full.exe: Size: 381,268,248 bytes SHA1: D4B5A202D116FED20CE8279C035BFC2D480E7590 MD5: 9EC24B54BCCC679D22C2A5D2399B9EAA CRC32: 56DE4AC6 I downloaded the xdelta patch that ibmpc5150 made. MSDN_to_Retail (SHA1: C6352784106E0C7F7260B88660463B8A0747F63).
Sorry about that. I was not sure what you were quite asking for the first time, but now I do. I have downloaded several copies of cdimage 2.39 but they all have the same hash. I can not find the one with your hash. If you are feeling generous, I will gladly accept a link to it. Thanks for explaining the difference to me. I tried with and without the -o switch. The one I copied at the time just happened to be without the -o switch. I was playing with the time stamp and date and clock on the test system. What seemed to work for me was changing the year to 2000 and the zone to GMT, London. I have successfully achieved this hash. Thank you for your detailed responses. They have helped me greatly!
if you make a binary compare you see the crap F613C539290BD7B89387A4B9248276E6BBF57F3D has cdimage.dbg at the end and differ also on top. if this was a true debug compiled version, then the whole file must be total diffrent and has a lets say "debug structur". if you general compile a exe in debug-mode and in normal-static-mode and compare the two binary you will see what i mean. in my opinion somebody patch the A9CC81D821E1DE3AC4FD0BEB3173A4E230AE7BCB version (may be for privat analyse). the changes on top looks like chanched entry points. i woud never trust the F613C539290BD7B89387A4B9248276E6BBF57F3D version until it was verified as valid by MSDN. the www is full of nonsense .