for the type see .iso\WIN95\PRECOPY2.CAB\setuppp.inf ... [data] ProductType=? 2=CCP-Upgrade CD 3=CCP-Upgrade (3.5-DMF Floppy Disk) 4=OEM-Setup (3.5-DMF Floppy Disk) 9=OEM-FullSetup CD
reason for this is: Disk1 and Disk2 depend on type (3, or 4) Disk 3 - Disk X is shared between type 3 and 4 (same hash on both types ! ) eg. for english Code: ;Note the hash of Disk01 can differ coz hardcoded Key-part (winsetup.bin) ;Windows 95 (type= 4 OEM Full Install - Floppy) C8D1FAF83808047CD25DDAB5586AF8885F0AB12F *en_w95_Boot00_OEM_19950711.img A1CA01A508BF33AA38F62A11EBD9EC6B7D7CE278 *en_w95_Disk01_OEM_19950711_24261-294-0526976.img D70603F057A136C982374363160954BEB550A0E6 *en_w95_Disk02_OEM_19950711.img ; ;Windows 95 (type=3 Retail Upgrade - Floppy) 8F1C9EECD2DE6B288101A9444CDD9BC01FAF87A7 *en_w95_Disk01_CCP_19950711_24265-296-2157724.img 2B355C6024D6FB9A5983F4E872D34DCB34125371 *en_w95_Disk02_CCP_19950711.img ; ;Windows 95 (Shared OEM and Upgrade - Floppy) B262F7E8288C9EDEA8B799FAE84CD0DA5B3B203B *en_w95_Disk03_FRE_19950711.img B8D4CD9D67B58876B90F343F0D1702C4447456FD *en_w95_Disk04_FRE_19950711.img CF6EE31252E2A6316640E660F166112A43CE1E43 *en_w95_Disk05_FRE_19950711.img DD98687E263FB2AFACCCC77FEEAB817F42F14755 *en_w95_Disk06_FRE_19950711.img A98F0C9CCBD1C176BEDA9FFB6D0B4371A3D4F550 *en_w95_Disk07_FRE_19950711.img 5DEFF1D95E29E60DE3EE1B67DC0D5B9C2BC044DB *en_w95_Disk08_FRE_19950711.img CAFD8A635168C98FFF41162F629534BBFFEB8581 *en_w95_Disk09_FRE_19950711.img C64ECC7420D6766939DF4A689A23DBDC1FBD8946 *en_w95_Disk10_FRE_19950711.img AC390BB3E2FE058724472977D709254544B10B03 *en_w95_Disk11_FRE_19950711.img 4EA684304744607739C7EA659D8C4E590583F21C *en_w95_Disk12_FRE_19950711.img 0ECF904AE1F4B721B1063509AFD50D1AFFF366E6 *en_w95_Disk13_FRE_19950711.img THX again for CA57ED29E471E745E841A2F5FD300A5D264F4ED3 *[PTB] win95_CCP-Upgrade___cd_type02_00000000.iso
If they are untampered, they are for sure worth archiving (if you have a floppy disk reader of course) Just flip the "switch" to write protect first. And thank you for for the upgrade image.
I can give it a try. I find it much harder to examine floppies floating around thoe. Maybe someone other like to give it a try as well and we can cross-check our findings.
@kdesktop you did your job well i make some changes on some disk Windows 95 OSR2 (Disco 01).img: - defragment the img - remove the last access time (Volume last modified on 17.01.2022 13:03:58) - remove the last access time from all affectet files log file before changes Code: Image format identified by Raw Disk Image. Identified by Microsoft File Allocation Table. Microsoft FAT12 Volume has been modified by Windows 9x/Me Volume Tracker. 512 bytes per sector. 2880 sectors on volume (1474560 bytes). 1 sectors per cluster. 2847 clusters on volume. 1 sectors reserved between BPB and FAT. 2 FATs. 224 entries on root directory. Media descriptor: 0xF0 9 sectors per FAT. 18 sectors per track. 2 heads. 0 hidden sectors before BPB. Drive number: 0x00 Volume Serial Number: 14E93546 Filesystem type: FAT12 Volume last modified on 17.01.2022 13:03:58 Volume label: DISK1 Volume is bootable Boot code's SHA1: 6ea1de6b5c0b6932b40a376d66b0a3c0d20bd025 Unknown boot code. log file after changes Code: Image format identified by Raw Disk Image. Identified by Microsoft File Allocation Table. Microsoft FAT12 Volume has been modified by Windows 9x/Me Volume Tracker. 512 bytes per sector. 2880 sectors on volume (1474560 bytes). 1 sectors per cluster. 2847 clusters on volume. 1 sectors reserved between BPB and FAT. 2 FATs. 224 entries on root directory. Media descriptor: 0xF0 9 sectors per FAT. 18 sectors per track. 2 heads. 0 hidden sectors before BPB. Drive number: 0x00 Volume Serial Number: 14E93546 Filesystem type: FAT12 Volume last modified on 18.10.1996 16:00:00 Volume label: DISK1 Volume is bootable Boot code's SHA1: 6ea1de6b5c0b6932b40a376d66b0a3c0d20bd025 Unknown boot code. i do the same for Windows 95 OSR2 (Disco 01).img Windows 95 OSR2 (Disco 06).img Windows 95 OSR2 (Disco 07).img Windows 95 OSR2 (Disco 11).img Windows 95 OSR2 (Disco 12).img this images are OK, nothing change Windows 95 OSR2 (Disco 02).img Windows 95 OSR2 (Disco 03).img Windows 95 OSR2 (Disco 04).img Windows 95 OSR2 (Disco 05).img Windows 95 OSR2 (Disco 08).img Windows 95 OSR2 (Disco 09).img Windows 95 OSR2 (Disco 10).img Windows 95 OSR2 (Disco 13).img Windows 95 OSR2 (Disco 14).img Windows 95 OSR2 (Disco 15).img Windows 95 OSR2 (Disco 16).img Windows 95 OSR2 (Disco 17).img Windows 95 OSR2 (Disco 18).img Windows 95 OSR2 (Disco 19).img Windows 95 OSR2 (Disco 20).img Windows 95 OSR2 (Disco 21).img Windows 95 OSR2 (Disco 22).img Windows 95 OSR2 (Disco 23).img Windows 95 OSR2 (Disco 24).img Windows 95 OSR2 (Disco 25).img Windows 95 OSR2 (Disco 26).img hash for your clean br_win95b_osr2.0_type9_OEM_19961018 floppy set (it is a copy of the cd version on Floppy disk) Code: d2a0171f87514abb05d787df33159381cbc9aa96 *br_win95b_osr2.0_Boot00_OEM_19961018.img 299934bf25d95b38ca25f4a6d380304f311e15cb *br_win95b_osr2.0_Disk01_OEM_19961018.img 3d962ae4337ad1e5f4540c1ac0bdc743648d39da *br_win95b_osr2.0_Disk02_OEM_19961018.img 83d467e62f0162283554de22af289fc830c44104 *br_win95b_osr2.0_Disk03_OEM_19961018.img f9cf674305569d7fb04e92379775757b87a73f0e *br_win95b_osr2.0_Disk04_OEM_19961018.img 232ce88a47eb184fd7881200468c09ead441096f *br_win95b_osr2.0_Disk05_OEM_19961018.img 6e17460d553ef0275c85eb68909b6ba581c3f96e *br_win95b_osr2.0_Disk06_OEM_19961018.img 514f07bec4a69cf14f2e08d5068b74a0387cff8d *br_win95b_osr2.0_Disk07_OEM_19961018.img 0eef4f6d5d444bad1ea9731cd82ef77792c715ea *br_win95b_osr2.0_Disk08_OEM_19961018.img 6abf3018a8e2b38ba9e956f342932b0ab21e4b15 *br_win95b_osr2.0_Disk09_OEM_19961018.img 9acf2dd7f15a8c6a8ba63edc9844a8bd52bf4157 *br_win95b_osr2.0_Disk10_OEM_19961018.img 46983b73849467e9c86fa26928d841a2b29d535f *br_win95b_osr2.0_Disk11_OEM_19961018.img 4359f4131f013002066192a0bb1245c9c491d1ca *br_win95b_osr2.0_Disk12_OEM_19961018.img 565e163c7e4983398be0a064951569d000fb031b *br_win95b_osr2.0_Disk13_OEM_19961018.img 78c8b08f1add87baa92e681a25b00d3dc52a2ab3 *br_win95b_osr2.0_Disk14_OEM_19961018.img 0aa6c8932b91e2ef7e6bb06ea5e88a86bc7b933d *br_win95b_osr2.0_Disk15_OEM_19961018.img dd58aeccabc97ec038ec512248b998a188fdd4b2 *br_win95b_osr2.0_Disk16_OEM_19961018.img 20f111d6fb870d1df8fa7054f4fef48145121af4 *br_win95b_osr2.0_Disk17_OEM_19961018.img 54164e3430fc496966d583f0fbb97b21d8c0adcd *br_win95b_osr2.0_Disk18_OEM_19961018.img c229508a1030c574fb9a3082778d4c24a2435c13 *br_win95b_osr2.0_Disk19_OEM_19961018.img 501565f7e00112450946aec4b033baf42bab5e49 *br_win95b_osr2.0_Disk20_OEM_19961018.img a79b82356cbb67946eee9b021cc14311d5a123a6 *br_win95b_osr2.0_Disk21_OEM_19961018.img 53649276918b79593b0ba7902cbb91edb1ecad07 *br_win95b_osr2.0_Disk22_OEM_19961018.img 36caa6021492a603459eefa2869d094bc8eb4ea4 *br_win95b_osr2.0_Disk23_OEM_19961018.img b6a6306584a26f7703f71d79e404e9b663bbb346 *br_win95b_osr2.0_Disk24_OEM_19961018.img 06432b7350b358721961aed2fa356614606d4d21 *br_win95b_osr2.0_Disk25_OEM_19961018.img ce62d481a3a55d4e87846f9802f22e061bbe3128 *br_win95b_osr2.0_Disk26_OEM_19961018.img PS: i upload and send you a PM with download link for the clean set
That's some good looking, proper dumps. I think the volume label was odd compared with the english set but that might be correct for all that i know. How bad, was they unreadable or did they suffer from "earlier" use with write protection off? If possible I wouldn't mind a copy of them. It would be possible to test the whole disk set to see that all works. It would be a baseline searching for proper dumps. (if not possible to dump floppies, a partial hex dump would also help) I saw the pictures, a partial hex dump would be helpfull here... I feel bad for asking this but I would love to be able to read the details of the floppy labels. (i had a closer look on those other floppy dumps: Win95_4 repack, Win95_3 repack - UltraISO , Win95_2 repack - WinImage, Win95_1 - partial looks good. The bootdisk and disk 1 are modified)
@kdesktop Disk 6 - can probably repair (coz sectors of Fat12 header is ok) Disk 1 - can probably repair (depend on how much sector of the Fat12 header are intact ) please rip again (try some retry and after this click ignore) and send me the damaged file (mark file name as _damaged.<ext>
Excellent work. I will set up a virtual machine and test this upgrade version and see if all files are intact. Few notes from my side: OEM System Name differ between this set and the disk set from Win95_1 (product type 3 vs product type 4) Sector 0 seems intact so editing OEM System Name would in my opinion be approved (choosing correct header ofc ) Opening a clean image in Win 95 will alter OEM System Name and some time stamps but that is reversibel Serial ID is lucily not touched I ran several tests on this to understand better this behaviour. DISK1.VCP > switch to .ima - it's a raw dump Seems like vga-copy saved this one Will see how this one works... Where you able to compute SHA-1 of WIN95BR1 (diskette, not the image)? Is it matching DISK1.VCP?
Disk02 > Disk13 works like a charm. A few files on Disk01 is bent out of shape. MINI.CAB/INSTALAR.EXE is not happy, DOSSETUP.BIN and WINSETUP.BIN is a little wonky. And there is a registration that needs a reset, etc. Spoiler
Disk01 damaged files: DOSSETUP.BIN INSTALAR.EXE (Edit not damageged - RTM Version - but probably with Microsoft bugs MINI.CAB WINSETUP.BIN SCANDISK.EXE SCANDISK.PIF (depend on SCANDISK.EXE) PS: vgacopy is more or less nonsense, does't repair or read in a spetial way. only make it harder to find damaged sectors (coz damaged sectors not filled by zero byte) It makes sense to use different intern hardware floppy drives. USB Floppy drives are not particularly suitable for reading old floppy disks
Works, good candiate. I used same INSTALAR.EXE The one from original dump is twice the size - does the string examples from this one make sense If the one at ~ 21 kb is used there are no endpadding "F6" , which are seen on both corrupted images. I¨ve noticed the same pattern on disk1 english upgrade. Just an observation Code: 95aa4a0e894a75c1d83389b862b10b696e502d02 *INSTALAR.EXE 000030E5 64 3a 5c 63 68 69 63 6f 5c 70 61 6e 65 75 72 6f d:\chico\paneuro 000030F5 5c 73 72 63 5c 63 6f 64 65 5c 73 65 74 75 70 5c \src\code\setup\ 00003105 77 69 6e 5c 77 73 65 74 75 70 2e 63 00 00 00 01 win\wsetup.c.... 000050DD 64 3a 5c 63 68 69 63 6f 5c 70 61 6e 65 75 72 6f d:\chico\paneuro 000050ED 5c 73 72 63 5c 63 6f 64 65 5c 73 65 74 75 70 5c \src\code\setup\ 000050FD 77 69 6e 5c 77 73 65 74 75 70 2e 63 53 54 52 10 win\wsetup.cSTR. Thanks for cleaning it up, still contains some registration on previous user. Spoiler Thanks for showing where this info was stored. (annoying little bugger) Spoiler