i have the following Code: File: en_windows_95_4.03.1216_plus_oem.iso CRC-32: 8d5d51d6 MD4: 0b2aa347282b837496b30a1250c5c633 MD5: 9a8b57f60b13563f512b522e8120d310 SHA-1: b9b87cfedec356574b737e533ec667f0e42988b0 however it is only an iso image not physical media
Yes, got that one - and it may be a clean dump for all i know. Was that a redump of LostCrusader's dump? LoneCrusader's mdf after conversion to iso have a "tail" and also a buttload of wrong data's in the beginning. Seen a few with, what i consider modifications, but I can't tell the difference to be honest.
LOL Code: 7e3e56b117b3c0333a00c486170ffbd4fdadb9eb *Disc01.rar include 1143fc682c725a3d6123d8a6387d1bc0a101e73f *Disc01.log b73839f4d23ce8dcd645662d2cd671e3531723f6 *Disc01.mdf 9d2e22c794649603c439d82b1e8e2a0052760a7c *Disc01.mds Code: ####################### Dumping/Recording Progress Log ####################### ********* Time stamp of this log file: 1/19/2017 5:37:04 AM ********* 05:37:04 Processor info: Intel(R) Pentium(R) 4 CPU 2.66GHz (2666MHz) 05:37:08 Disc dumping: (F:) ATAPI DVD A DH20A4P (2:0) 05:37:11 Reading Mode: RAW + SUB-96 , Fast skip error blocks Selected reading speed: 8X (1200 KB/Sec) 05:37:11 Source Info: Session: 1, Track: 1, Length: 601.4 MB / 68:25:63 05:37:11 DPM measuring precision: High / 8X (1200 KB/Sec) 05:37:11 Wait for a while for DPM analysis. 05:46:04 Data Position Measurement - 00:08:55 05:46:04 Get DPM info from current disc successful! 05:46:04 Disc read error at: 0 05:46:18 Start Enhanced Weak Sector Scanner 05:46:18 Writing image file: C:\MDF\W95_OSR25P.mdf 05:48:43 C:\MDF\W95_OSR25P.mds: Image file writing completed! 05:48:43 Disc dumping completed! ############################################################################## 1. the rip was made with the "Wrong / Misleading" A120 riping setting!! Fast skip error blocks does not show extendet error information during Rip !!! this can lead the user to misinterprete the log file Disc read error at: 0 mean the riped CD has a Error at sector 0 A 120 fill each error sector with hex 0x55 2. after converting A120 image this 1. sector (Sector NR. 0) must be edit (fill with hex 0x00) 3. A120 always rip raw (incl. the lead out) -> converting to iso format the result iso is always overdumped !!! -> the result CD file is never ISO 9660 Ecma-119 conform !!! (exept the converting tool does this step) i dont know a converting tool that do this step during the convert Note: only CD/DVD with a UDF header (ISO 9660 TR-071) will be convert to the right size (coz TR-071 explizit define the last sector of the image - it is a backup sector ISO 9660 Ecma-119 also define the last sector, but not explizit 4. after converting A120 image the file with the extension iso must be convertted to ISO 9660 Ecma-119 usual known as Redump ->Volume has 307487 blocks of 2048 bytes each -> 307487 * 2048 = 629733376 bytes for a valid ISO 9660 Ecma-119 I do it with a small script that read the iso header, seek to the last sector and set a new EOF (i do not redump - i only do the work that other developer ignore!!!) my Log file for step 3 and 4 Code: step 1: convert to output raw iso image Input image format identified by Alcohol 120% Media Descriptor Structure. Output image format: Raw Disk Image. Converting media tag CD_FullTOC 307938 sectors to convert Converting sectors 307938 to 307938 in track 1 (100,00 % done) Closing output image. step 2: convert to ISO 9660 Ecma-119 image starting ISO9660 heder check: OK volume has 307487 blocks of 2048 bytes seek to last sector: OK set new EOF: done 5. bug fix for 1 Disc read error at: 0 open ISO 9660 Ecma-119 image and fill the first sector (2048 bytes) with 0x00 (using HXD editor - open the file in sector mode) -> B9B87CFEDEC356574B737E533EC667F0E42988B0 *[ENU] win95c_osr2.5_OEM-FullSetup_PLUS_cd_type09_19971201.iso Code: ;win95c_osr2.5 - ISO 97F66E77445CD4B1AC55508C36D0FDBC17F17F25 *[ENU] win95c_osr2.5_OEM-FullSetup_cd_type09_19971126.iso B9B87CFEDEC356574B737E533EC667F0E42988B0 *[ENU] win95c_osr2.5_OEM-FullSetup_PLUS_cd_type09_19971201.iso 795E3FBF2F993C4D6E875770555C061B55AB7690 *[DEU] win95c_osr2.5_OEM-FullSetup_cd_type09_19980130.iso F334ADFECCE6DBBDE068BFA7C7D838754F295D82 *[ESN] win95c_osr2.5_OEM-FullSetup_cd_type09_19980130.iso 2DD5B52A52ECE92CF29409DCBE119F7340571A39 *[FRA] win95c_osr2.5_OEM-FullSetup_cd_type09_19971212.iso 24C5738FBEA1B0A71E33570B7EC10115898C1758 *[ITA] win95c_osr2.5_OEM-FullSetup_cd_type09_19971212.iso BD7FFDBEFEB4B0D0C1852859CEB53F6A37DAD68A *[JPN] win95c_osr2.5_OEM-FullSetup_cd_type09_19980128.iso 44813FDE5CD5A8571935882ACFF64CE572754FBC *[JPN] win95c_osr2.5_OEM-FullSetup_cd_type09_19980403.iso E1B7C480DEB45129FFFE9452B4D39F5CB7B0348D *[NLD] win95c_osr2.5_OEM-FullSetup_cd_type09_19980130.iso A5C062CEE26D402E1DC6EEDB79C821AD762CB86E *[NOR] win95c_osr2.5_OEM-FullSetup_cd_type09_19980130.iso 3F903899B94F87BCB253FD0FC43BEFD38E7FAE32 *[KOR] win95c_osr2.5_OEM-FullSetup_cd_type09_19980403.iso 699B98EB700D54C97215A20A9A0976559E6DCFD9 *[PTB] win95c_osr2.5_OEM-FullSetup_cd_type09_19980129.iso 170F17D7C0498F8FB454595B933700F63250D40B *[CHS] win95c_osr2.5_OEM-FullSetup_cd_type09_19980415.iso B14E9636BA089E455321035D7962FEA212EEE864 *[CHT] win95c_osr2.5_OEM-FullSetup_cd_type09_19980415.iso Please work more carefully in the future And first read the log files (especially in for errors) If you rip original CD/DVD, you should always publish the log files !!! Actually everyone has to admit: The whole thread here is totally superfluous because it was worked too superficial
Therefore, in the future, those who understand these can publish correct images here, because the majority of people who do not understand. I don't understand either.
@vanelle Thank's. Luckily, for me anyway, I don't have to admit jack s**t to you just because that's your opinion. I raised the question initially for good reasons, unfortunately because of your arrogance some times, you could not even bother to get down off your high horse and simply ask why I raised the question. (or you did'nt even bother to notice) It's fine, could not care less.
Code: Release Version File dates Windows 95 retail, OEM 4.00.950 7/11/95 Windows 95 retail SP1 4.00.950A 7/11/95 OEM Service Release 1 4.00.950A 7/11/95 OEM Service Release 2 4.00.1111* (4.00.950B) 8/24/96 OEM Service Release 2.1 4.03.1212-1214* (4.00.950B) 8/24-96-8/27/97 OEM Service Release 2.5 4.03.1214* (4.00.950C) 8/24-96-11/18/97 Windows 98 retail, OEM 4.10.1998 5/11/98 Windows 98 Second Edition 4.10.2222A 4/23/99 Archive
Ok. #91 with links summarize ProductType (still missing minor bit's of information) #97 with links summarize how to create a valid key (additional info most welcome) That was'n really the point with this thread thoe, it was more about getting more unique confirmation's. Example: #37 - good image with NERO___BURNING_ROM, normally we would see CDIMAGE x.xx This one has official confirmed checksum through MVS. Typical would this one get dismissed as modified if offical checksum wasn't available. I don't mind making an ass of my self if i ask question(s), that obviously should not be asked, against established opinions if i have even slightest doubt.
Producttype=1 Does not ask for a product key. Used on some special Microsoft licensed media. ProductType=2 Retail CD Upgrade Install ProductType=3 Retail Floppy Upgrade Install. Writes name and company to the floppy. ProductType=4 Full Floppy disk install. Asks for retail Key. (shows product id number) 5? Not used? Non upgrade version. setup runs from DOS but can not read the disk at "setup options"? 6? Not used? Full version - installs from win3.1, dos, and blank. Product Key has "ignore" option? 7? Not used? Non upgrade version. setup runs from DOS but can not read the disk at "setup options"? I have an OEM Pre-Install that has this product type, but it is overridden as type 1 by an MSBATCH.INF. Without the MSBATCH it fails at "setup options". ProductType=8 OEM Floppy Install, Non-Upgrade. ProductType=9 OEM CD Install, Non-Upgrade. Extract setuppp.inf, usually located in precopy2.cab and put in same folder as install.exe or setup.exe and edit value @Sajjo