Matches what I got: Code: File: en_win98_se_with_plus!_oem.iso CRC-32: 0fff0609 MD4: 1252cdc7c3a74d19859f3721c6897a0b MD5: 0ac28bfbb29df0b788482388f7d5b11d SHA-1: 2b68161b1fb2d905a6c05c82087fa1c20b47a8fd
What tools you guys use to dump this discs? I've read people complaining about "not done correctly", what does this mean? Why I'm asking? If I use something like readcd, a tool found in cdrtools, it will give me a signature and with dd we get another and if I use the clone options, we have another signature. Code: ./readcd -v dev=0,0,0 f=brzw95b_usb.iso # MD4 e6d261e6fe626b07fdf612961453656d brzw95b_usb.iso # MD5 eab47a2a132779b4ec623dc0c5615944 brzw95b_usb.iso # SHA1 f84fef21fdcec53eb3c5a22b14fa95e9ca321013 brzw95b_usb.iso # SHA256 b17ad6f991e94728f69def1ddd62c4eecfe6f213fe99014f8a1b69744d13b237 brzw95b_usb.iso # CRC32 ade63c7b brzw95b_usb.iso Code: dd if=/dev/sr0 of=brzw95b_usb-2.iso # MD4 0e38b55659c7315c2ac90e4d4fc60f63 brzw95b_usb-2.iso # MD5 eab47a2a132779b4ec623dc0c5615944 brzw95b_usb-2.iso # SHA1 f84fef21fdcec53eb3c5a22b14fa95e9ca321013 brzw95b_usb-2.iso # SHA256 b17ad6f991e94728f69def1ddd62c4eecfe6f213fe99014f8a1b69744d13b237 brzw95b_usb-2.iso # CRC32 ade63c7b brzw95b_usb-2.iso Code: ./readcd -v dev=0,0,0 -clone f=brzw95b_usb-3.iso # MD4 83fe466851e566a69cb356c5a8d9f32e brzw95b_usb-3.iso # MD5 51d636494cc6f56b88d5758f7d34553a brzw95b_usb-3.iso # SHA1 ff92bfb4c0664877cf7a92ef871efdb45bb0e070 brzw95b_usb-3.iso # SHA256 49be86608d2600b7fd5edb6439d1df52e4ec1265372716dc10a2327968d7320c brzw95b_usb-3.iso # CRC32 658f5bc5 brzw95b_usb-3.iso Code: sudo fdisk -lu brzw95b_usb.iso Disco brzw95b_usb.iso: 566,4 MiB, 593915904 bytes, 1159992 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (lógico/físico): 512 bytes / 512 bytes Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes Code: sudo fdisk -lu brzw95b_usb-2.iso Disco brzw95b_usb.iso: 566,4 MiB, 593915904 bytes, 1159992 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (lógico/físico): 512 bytes / 512 bytes Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes Code: sudo fdisk -lu brzw95b_usb-3.iso Disco brzw95b_usb-5.iso: 677 MiB, 709914624 bytes, 1386552 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (lógico/físico): 512 bytes / 512 bytes Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes So, between copy and clone, witch one is correct?
all iso dumping tools padd "00" bytes (sectores) at the end of the iso we call this 'overdumped' only UltraIso has an option "Enable ISO Filter" ON: UltraISO will detect size of ISO image by logical volume parameters on a CD/DVD disc (ISO-Header). OFF (default): Size reported by hardware (your CD/DVD-ROM drive) will be used to get an ISO image. you have to set this option to ON to avoid overdumping
In Windows 10 I use UltraISO with option "Enable ISO Volume Filter" checked. ImgBurn does exactly the same but adds padding (extra 00 bytes) at the end of the image. The best way to check what tool might be working best is comparing the images with an hex editor. If they only differ at the end, the smaller image is probably the correct one. You should also check around 0x833D to confirm if the header mentions cdimage or if the program changed/added something to it.
UltraISO clones the CD byte by byte. The padding we talk about has nothing to do with the header or image content, it's just a bunch of 0x00 bytes that some programs add to the end of the image, usually around 300kb. Those bytes will change the final crc/md5/sha1 of the image so using a program that doesn't add them in the first place is better and safer than deleting them manually. So yes, if I create an image from a CD with UltraISO and you do the same to an identical CD, both images will have the same crc/md5/sha1. Heck, even if I copy the cd content to a folder, I can even recreate the original cd image down to the last byte if I use the correct cdimage version, parameters and boot sector.
I believe that UltraISO is a copy tool, it doesn't do a 1:1 copy of the disc. For that you need something else, to do a 1:1 copy you need a tool to do a RAW copy of the 2352 bytes per sector of the disc, this tool only copy the 2048 bytes. This extra bytes are used for error detection and correction, because of that you'll have a very different hash signatures.
we are talking about data cd / dvd based on ISO9660 and not about Music CD therfore the sector sice is usual 2048 bytes ad the iso stucture based on ISO9660 structure UltraISO is a clone tool RAW copy of the 2352 bytes per sector is nonsense because data cd / dvd based on ISO9660 for techical details see eg. Ecma-035 Ecma-107 Ecma-119 udf260 (in case of osta UDF format extension) etc. EDIT: UltraIso with Enable ISO Filter option read the exact info from the Primary Iso Header - sector-size (usual 2048) - and Volume_Space (sector count) sector-size * Volume_Space = absolute size of the original Image in bytes the padded image is cut of at this exact ISO size (based on the PrimaryVolumeDescriptor of iso header)
Understood. I want to collaborate and share the floppy images and the CD images, but I don't want to copy this files, upload and someone say that my files are copied the wrong way. What options do I have on Linux?
The trick is to recreate the same ISO that M$ would have generated when using there own tool CDIMAGE, which generates 2048 byte sector sizes. See if you have a normal English CD that is already dumped and try and get the same SHA1 as posted. Failing that, if you do a normal dump of one we can look at it and tell you the correct size/sha1 and you can work on reproducing that under Linux.
Does anyone has a database or hash list for WIndows 2000 Pro US so I can run some tests? Or point me out to one? Code: Setupp.ini ExtraData=64766769766D6B766768820497EA44 Pid=51873OEM Code: # MD4 94c94bea36fe89a256af3c2f2aba1de3 W2POEM_EN.iso # MD5 550bb80bd073c84f12f649aaa8ae473a W2POEM_EN.iso # SHA1 7f1d073523056e0f616f6d577f4bcb344883ef3b W2POEM_EN.iso # SHA256 3946aaabf9aeab48d0fd4a50107e40f5e5f9153065ba0e4097802cbc2817f232 W2POEM_EN.iso # CRC32 ffffffff W2POEM_EN.iso Code: sudo fdisk -lu /dev/sr0 Disco /dev/sr0: 360,9 MiB, 378402816 bytes, 184767 setores Unidades: setor de 1 * 2048 = 2048 bytes Tamanho de setor (lógico/físico): 2048 bytes / 2048 bytes Tamanho E/S (mínimo/ótimo): 2048 bytes / 2048 bytes
Code: File: W2POEM_EN.iso CRC-32: ffffffff MD4: 7b0e071c7f183b9877248cab9a4571ba MD5: 9cbf5a4f29418c5385c86664cee2d2ae SHA-1: 072f93598bae729e8abec10fb97f71abd3315948 360 MB (378,075,136 bytes) It looks like yours has about 320kb of padding on the end.
Thanks! Looks like we have a option for linux using free/open source software and WinISO might not be needed anymore. I've compiled the readcd tool for windows a few years ago and also it works with dd, all I had to do was to remove the extra padding at the end with the source code for the dtn tool I've post earlier. We have a match: Code: # MD4 7b0e071c7f183b9877248cab9a4571ba W2POEM_EN.iso # MD5 9cbf5a4f29418c5385c86664cee2d2ae W2POEM_EN.iso # SHA1 072f93598bae729e8abec10fb97f71abd3315948 W2POEM_EN.iso # SHA256 7a4f79f615a7a3629d00875a2c203dd9040fd868611fbd8680b4c1d04ef6a604 W2POEM_EN.iso # CRC32 ffffffff W2POEM_EN.iso Code: sudo fdisk -lu W2POEM_EN.iso Disco W2POEM_EN.iso: 360,6 MiB, 378075136 bytes, 738428 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (lógico/físico): 512 bytes / 512 bytes Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes
if you can code in linux (c /c++) i can give you the header structure it is quite simple to code a small tool wich check the PrimaryVolumeDescriptor and read the 2 member Volume_Space_Sice (32bit Both-Byte order uint) Logical_Block_Sice_int (16bit Both-Byte order) Volume_Space_Sice * Logical_Block_Sice_int = size of the iso image rip the image with your tools and run this small tool to cut of the file at the right place
Sorry, I don't code. Maybe the guys at the Linux forum could help to create a specific tool for this or, customizing the "readcd" to do all this at once with a switch. But the tool exist and I've posted as a source code, this tool rip off the padding at the end. You can use "readcd" to dump the ISO and run the tool to strip the zeros. Code: ./dtn win.iso For dd you can do the same: Code: sudo fdisk -lu /dev/sr0 Disco /dev/sr0: 360,9 MiB, 378402816 bytes, 184767 setores Unidades: setor de 1 * 2048 = 2048 bytes Tamanho de setor (lógico/físico): 2048 bytes / 2048 bytes Tamanho E/S (mínimo/ótimo): 2048 bytes / 2048 bytes Code: dd if=/dev/sr0 of=win.iso bs=2048 speed=20 count=378402816 status=progress 376416256 bytes (376 MB, 359 MiB) copiados, 247,014 s, 1,5 MB/s 184767+0 registros de entrada 184767+0 registros de saída 378402816 bytes (378 MB, 361 MiB) copiados, 247,924 s, 1,5 MB/s With readcd or dd is the exact same result after you strip the zeros.
Great! I'll not dump the ones already dumped like the W2k Pro, witch one from that list people doesn't have?
please all except 072F93598BAE729E8ABEC10FB97F71ABD3315948 *[ENU] en_w2k_W2P_OEM_19991207-0xE0.iso and make a sha1 list for the iso's without the vali hash we can't compare what we have TIA
All striped. Windows 95 JPN Upgrade 274,7 MiB, 288018432 bytes Code: # MD4 84e2f5377f1b452ce86736dcaa7b51bc WINDOWS_95U_JP.iso # MD5 306acbfc7a20764e5fb18f5a84fe76e8 WINDOWS_95U_JP.iso # SHA1 f84faba4d73d6206b9c4e7fe0dac9891e03e2600 WINDOWS_95U_JP.iso # SHA256 0d746646ed5e98082c355fdb2f7c6e65bc9edbf2329b9692c186964bac5980aa WINDOWS_95U_JP.iso # CRC32 8049a316 WINDOWS_95U_JP.iso Windows 95 PT-BR OEM SR2 565,8 MiB, 593300480 bytes Code: # MD4 1a139c5e2b43054d862d7991987919b9 BRZW95B_USB.iso # MD5 a417339aa040ec63756d8a5133a026a0 BRZW95B_USB.iso # SHA1 8f2c3d0b7da794fb0edaf4f1c4786469a29e6ea8 BRZW95B_USB.iso # SHA256 bba688e0651a6d70a8998be69faf620d5f45c67de91caeb84f13a202fd27249d BRZW95B_USB.iso # CRC32 eb254de3 BRZW95B_USB.iso Windows 98 JPN OEM 312,1 MiB, 327215616 bytes Code: # MD4 e3a9da30acab50c1249b79e96000b6cd WINDOWS98_JP.iso # MD5 6df3affe238b34efbb1c90aeec7a0c75 WINDOWS98_JP.iso # SHA1 1b42db1c7b4902bf3e4404041050e05e4712e96a WINDOWS98_JP.iso # SHA256 cc9906dc4d0746fd2dd826810a3fad952367f83cfd960730baa0c8cae1adef83 WINDOWS98_JP.iso # CRC32 07ba2c71 WINDOWS98_JP.iso Windows 98 SE PT-BR RETAIL 559,3 MiB, 586447360 bytes Code: # MD4 6ef68d5d099324e6396042d2cf769672 WINDOWS98_BR.iso # MD5 56a378638ba274b8474009c74bf8e7fc WINDOWS98_BR.iso # SHA1 4421c97cc25f43a211dde2a7aaf8729011409bcf WINDOWS98_BR.iso # SHA256 425664b672703bdf75a0b534210553db644d8b8bcc5b69803fbe9c29be4d1908 WINDOWS98_BR.iso # CRC32 dc7608a7 WINDOWS98_BR.iso Windows ME RETAIL PT-BR 378 MiB, 396306432 bytes Code: # MD4 21457d68f02eda7ca064079f951b7f99 WINDOWS_ME.iso # MD5 b350ec6dbf319100d7a96aa1233d50e8 WINDOWS_ME.iso # SHA1 51511d0f3ea683ccf4e3a488bfc141d90548e392 WINDOWS_ME.iso # SHA256 1792ab124ca81b71352233fc39724927162211c2742e88a0f749b6c0cc8af9e2 WINDOWS_ME.iso # CRC32 12f892a3 WINDOWS_ME.iso Windows XP RETAIL PT-BR 536,1 MiB, 562165760 bytes Code: # MD4 0a21f6ba3379d01c778483d9ed56cfaa X1APOEM_BR.iso # MD5 d83ed52909293cac394176210bc992ba X1APOEM_BR.iso # SHA1 553e737ab36cc501275fe5e33405375d6f30b45a X1APOEM_BR.iso # SHA256 fce0eea87e603446f7421cb640279016278f8bd8ad19002b4ee4b8972f994e4c X1APOEM_BR.iso # CRC32 ffffffff X1APOEM_BR.iso