It has meanwhile been published by BA (Release Date 2024/06/23 - Uploader ssjkakaroto) Code: addfcc6d386ab7ccf08c1f4e01bde4efb65c8832 *artwork.rar 71760718feb07caa024162e61e16ae8c736f9922 *Disc01.rar The Damaged file (3 bytes differ) <- Ripping error or Pressing error (the log files only points out some subchannel fixes done by the ripping programm) c89169e6af3b0e8dba4be2d01749e294ef69a58c *PRODUCTS\DEMOS\OFFPRO\NEW.DIR valid file - can be taken from anny valid win 95 CD (rtm to osr2.5) a5fb435cdda46e9b2f0bb1ecb8d9051506f5c432 *PRODUCTS\DEMOS\OFFPRO\NEW.DIR it is a RIFX container file see my posting https://forums.mydigitallife.net/threads/info-windows-2000-and-9x-cd-info.88128/page-8#post-1840963 the redump of the WWPC version is the valid iso version (as i expected) 36808C3AFEC41387C899C9D7E761A60C1D0631FC *[ENU] win95a_osr1.0_OEM-FullSetup_PLUS_cd_type09_19960117.iso
So, this file of his, is a dump error, and an unrepairable file? The original file is still the same as before
I also have a question that needs to be answered, and some people say that it is possible to check the correctness of the ISO using isobuster software as a basis, and what is the chance of this error. If you have a new version of WinHEX, I hope you can share a copy with me, I heard that the files edited with the pirated registration code software will be corrupted
i coud not 100% say that is a dump error (may be it is a pressing error) from the log files Disc01.rar\ENG_CDPLUS_mainError.txt Code: Failed to read. readsize=2232, total_read=20805792/20808024 [F:ConvertScmToBin][L:3490] Failed to read. readsize=2232, total_read=20805792/20808024 [F:ConvertScmToBin][L:3490] Failed to read. readsize=2232, total_read=20805792/20808024 [F:ConvertScmToBin][L:3490] Failed to read. readsize=2232, total_read=20805792/20808024 [F:ConvertScmToBin][L:3490] Failed to read. readsize=2232, total_read=20805792/20808024 [F:ConvertScmToBin][L:3490] Disc01.rar\ENG_CDPLUS_subError.txt have a lot of Code: .. SubQ Reread [crc16 unmatch] -> NG. Fix manually the log files from discimagecreator are not user friendly (without first study the source code) I personally prefer ripp tools that mark each damaged sector as bad (even if only 1 or more bytes damaged) Tools who try to repair something are always suspect to me
I think the problem of optical discs and optical drives accounts for half and half. A good optical drive will also reduce a lot of errors.
it is the same problem like discimagecreator tool (see #166) all tools wich try to repair something during the ripping process are bad to me All raw images such as isobusters are usually not suitable for repair (must be convert to iso) ISO Images can be repaired (if the ISO header is not damaged) Principle procedure: - find the defect file(s) - You should know the defect sector(s) from log files (then it goes faster) - look for valid file(s) (from other valid disk) - replace the defect file using winimage (just override the defect file) all done
I remember the hunt for drives that could accurately and quickly rip data and Audio. I settled on TEAC (CD532E / CD540E) or PIONEER drives (PLEXTOR PREMIUM) back at that time. - DAO96+SUBCHANNEL - C2 Error detection - Configurable error correction (so you could disable it for creating forensic images) What's offered today is mediocre at best.
NEW.DIR_valid_to_invalid.svf Source: ;valid file - can be taken from anny valid win 95 CD (rtm to osr2.5) ;<CD-Root>PRODUCTS\DEMOS\OFFPRO\ a5fb435cdda46e9b2f0bb1ecb8d9051506f5c432 *NEW.DIR to Target (invalid file version with 3 byte differ): ;<CD-Root>PRODUCTS\DEMOS\OFFPRO\ c89169e6af3b0e8dba4be2d01749e294ef69a58c *NEW.DIR
mounted BA version Code: MSCDCRC 4.26 CD-ROM Disc Verification Utility Copyright (C) Microsoft, 1992-2004 DDP (R) is trademark of DCA Inc. and is Licensed from DCA Inc. MSCDCRC: Verifying disc in drive a: (616,775,680 bytes) 100% complete MSCDCRC: Computed CRC is 0xD56D9C4F MSCDCRC: SHA1 hash is 0x49728DBBCE1081AF8E9960A77D864A308D11C4B3
Switching those 3 byte in hexeditor and same checksum - excellent. And matching as our friend got from his physical disc #146 Second that, I'll keep checksum from both images. I may disable that "NEW.DIR" and see if I can learn something from it, a bit beyond my skill I must admit but who knows. Is best to open txt with notepad ++ (similare) Mostly difference is: BS - Backspace DLE - Data Link Escape
Name: FRN_COMP.iso Size: 448063488 bytes (427 MiB) CRC32: A587E0B6 CRC64: 648BC7A7D3253772 SHA256: 9afb9c6afe6e23d64692dc05103c0b667cad531fe847a51ba85c0a001b397392 SHA1: ad0a8a04c3f2b3e3e27b30dcd874903281c3808f BLAKE2sp: 6b51136659d41574888683485acfef4dd58ffdc9c3e8ff97b7381d97904fc80a XXH64: 53A57B22ED9A7D3C @vanelle Is there a problem with the file？
no AD0A8A04C3F2B3E3E27B30DCD874903281C3808F *[FRA] win95a_osr1.0_OEM-Companion_cd_type09_19960419.iso