I found the following information in my records. But the ISO images themselves are missing. Code: Партийные номера дисков: (OEM) - Part numbers of discs: (OEM) Windows XP Media Center Edition 2005 CD1 0604 Part No. X10-73976 (WinXp Pro) Windows XP Media Center Edition 2005 CD2 0604 Part No. X10-74283 (Media Center) Update Rollup 2 Windows XP MCE 2005 CD3 0605 Part No. X11-41447 (KB900325) Windows XP MCE 2005 Localization Pack CD4 0805 Part No. X11-41497 RU (Russian) (НЕ НАЙДЕНО) - (missing) Windows XP MCE 2005 Localization Pack CD4 0805 Part No. X11-41492 CS (Ceský) 0805 Part No. X11-41495 PL (Polski) Windows XP Media Center Edition Multimedia Feature Pack 0804 Part No. X10-73988 Media Center Bonus CD-ROM (Multimedia Feature Pack for Microsoft Windows XP Media Center) Windows XP Media Center Edition 2005 Digital Media Content Feature Pack Label : MRMPS_EN CRC32: 66D9F767 MD5: 1611EB08FAC4EA11BAD1E8BE844F6916 SHA-1: 3C756B1244B1773836370BB10DF66640ADE6F1E1 New Windows XP Media Center Edition 2005 Digital Media Content Feature Pack Label : MRMRMPS_EN CRC32: 913E9339 MD5: B739A7AA60EE12C39E6F14625C1E32E9 SHA-1: F8E6169C21684A6ECA480AAD902464B9C2398D22
In regard to this post (https://forums.mydigitallife.net/th...nfo-for-collectors.52771/page-22#post-1592079) and the script included, is there a way to reverse the process? What I mean is this: Is it possible to take the original, correctly hashed original iso, and pad it with this script after modding it to reverse the process? The padded redumped iso, must match a certain hash. So in other words, take the original iso, and pad it so that it matches a certain hash different from the original. If so, could someone with the ability and know how take a look at it and modify the script to do exactly that? Thank you.
If I remember right, most of the "overpadded" images just include a few extra rows of 00000000000 at the end. Could try and manipulate one by opening in a hex editor and add zeros at the end. Has to do with the ripping program, how well it ends the iso, some go to far and adds the zeros. If you know how big a file you're aiming for, as in bytes, keep adding to the file to match the size you are after.
Thank you for your reply. Yes, I actually have tried that, adding zeros at the end, but it never works. That is why I thought perhaps I'm doing something wrong, and that the script might do it better. I used a hexeditor for adding zeros manually, but I cannot hit the correct hash. Don't know or understand why.
Do you know the exact size in bytes that you are aiming for? Without knowing that it's million in one chance of getting it it right. I don't really want to ask why you are doing this, but maybe mention what you are after, or google the hash you are aiming for. Maybe, just maybe someone has the iso you want
I know the bytesize and the hash (sha1), and I have tried with the original file (or at least what I belive to be the original file from MS) and then added the zeroes at the end, until the bytesize matched, then saved the file (with a hexeditor). But still, the hash does not match. I believe that the .iso I am trying to create (match the hash) was imaged from a real dvd, thus padded, but I can't manually make it work. I think I have tried way more than a hundred times with slighty different approaches, but no success. Perhaps there are some settings I have overlooked when saving the file, or something? That is why I thought that perhaps reversing the before mentioned script might actually do the trick. I have tried for an extremely long time to find the correct iso to download in some way, but it does not seem to be available like that. So I thought I would try to recreate it myself.
I appreciate your time and efforts towards trying to help me. Thank you. This is what I believe to be the original MS image: en_install_disc_windows_small_business_server_2011_standard_x64_dvd_611535.iso The original MS image above has the hash sha1: 74764b29f6c5bafcb680d000f43e138c38a9a414 I already have the above image downloaded directly from MS subscription by myself. This is the hash I am trying to target sha1: 701d42b09ba372b1a4025103d4e3ef978fc7480e The byte size read from the target file should be: 6.662.362 KB as read from the folder in windows. This file is corrupt/empty, but the file/size is allocated by the system as such. However, if I use a tool to list the contents of the folder containing the target file, the size of the file is listed as 6.822.258.688 and I assume that is in bytes, though not specifically indicated. When I tried to manually create the file, I loaded the original MS image in a HexEditor, and added a bunch of zeroes to the end of the file until I reached this bytecount. But as mentioned earlier, this was not successful as the hash of the target file was wrong. And for good meassure, let me just mention, that I am not 100% sure, that the original MS image is the same as the target file, with the only difference beeing padding at the end. This is just what I assume from my research and work with trying to recreate the target file. Perhaps the target file was padded from an even earlier/older original MS file? MS has a history of changing the isos from time to time. If that turns out to be the case, I am at a complete loss, as I don't know how to attack the problem then.
So you are attempting to go: 74764b29f6c5bafcb680d000f43e138c38a9a414 *en_install_disc_windows_small_business_server_2011_standard_x64_dvd_611535.iso ----> 701d42b09ba372b1a4025103d4e3ef978fc7480e *en_server_install_disc_windows_small_business_server_2011_standard_x64.iso Both checksums can be found and I actually have the first one, same as you Second one though, only gets one hit, but it exists, with a typo in name, So is that what you are trying to get, just an updated version of what you have?
I am not exactly sure what you are asking when you say "updated version". The one we both have is downloaded directly from MS. The other one, are you saying that it is also an original MS image and it exists as such? What I want is to take the first image and convert it to the target image, if that is what you are asking, then yes, correct. I have never seen the second image (only as filename and hash). The isos are very similar in size and name, thus I assumed that both images are the same, except for the second image that may have been imaged from an actual DVD. And that would be why the file size on that image is a bit larger. Perhaps my assumptions are completely wrong, and the two isos are actually not the same, but are updated, or different older/newer actual official MS versions?
As far as I know, the SBS2011 operating system does not have problems with internal image updates and re-releases. But it has an OEM version from the hardware manufacturer, a Microsoft OEM version, and I want to rule out a problem with the image, nothing more than this result. I'm not talking nonsense, because I have the original Dell 2011 and the COEM 2011 version of the European language, so I judged this way.
Interesting. Could you please check if the isos you have, are identical or different from this?: 701d42b09ba372b1a4025103d4e3ef978fc7480e Thank you.
Mine is definitely different from this one, because I am a Dell OEM. I guess that if there is no problem with the file, the SHA should belong to the COEM channel image. Because I don’t have this file for the time being, I can only guess like this. To answer your question, I just want to tell you that there are other channel files. 2011 is not just on the MVS or VLSC channels. SBS2011 STD -------- MSDN=VLSC=EVAL Only the file name is different, the checksum is the same SBS2011 ESSENTIALS --------MSDN=VLSC≠EVAL So according to the file name you identified, it is the standard version series So excluding file errors, it can only be from the OEM channel. As for which hardware manufacturer or COEM it is from, it is unknown. My English DELL does not match the SHA you provided, but I can't tell it. It must be wrong So you have to have the files to judge. I currently lack the English image of COEM.
As for what you said, it is impossible for the modified file to match the check value you want, because you don’t even understand the basic differences between the original files, so how can you get the final result?
Yeah, I see your point. My idea for a convertion between the two isos, would only be possible, if the image above (original MS image) actually is the same as the target image + the padded extra zeros. But sinse that has not been 100% determined, I am back to scratch. Well, I will try to keep working at it, and see what I can come up with. Thank you to all of you for taking your time and for your patience in assisting me with this.