Last fix is Who knew: suddenly the "old" ( ~21 kb) INSTALAR.EXE worked when i't got served correct MINI.CAB. I only had the newer one dated 1995-11-20 so that was really cool you had that one. End of image looks much better. Ok. This one is still present: Code: User name: FEDERAÇÃO NAC. DOS PORTUÁRIOS Converted to hex: 46 45 44 45 52 41 C7 C3 4F 20 4E 41 43 2E 20 44 4F 53 20 50 4F 52 54 55 C1 52 49 4F 53 20 To summarize: - MINI.CAB was broken - DOSSETUP.BIN/WINSETUP.BIN was broken, I tried them with the old ones, nogo. Old DOSSETUP.BIN would'nt start installation, WINSETUP.BIN could'nt start progman. - SCANDISK.PIF - corrected date/timestamp, corrected 2 bytes, is now binary identical with old one. No issues observed. See diff patch. Checked against DISK1.VCP and WIN95BR1_damaged.IMA - all files aligned. Diffs are now only inside these 3 broken files. Diff patch + svf Code: 000027D6: 60 43 000027D7: B4 4E 000027D8: 48 18 000027D9: 26 1F 0015CD6B: 80 30 0015CD6D: 90 77 If anyone like to install Win 95: This upgrade type only runs from floppy, if you run the "win95FIX95CPU" it will mess up the installation (files not found on diskxx) Emulator highly recommended. If irc an oem cd type will not have this issue. You need Dos and Win 3.11 (localized) for this set. If the "log on" window is annoying - "Win95_98 Turn off login prompt Microsoft Network.reg" Code: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Network\Real Mode Net] "AutoLogon"=hex:00
Tested some Windows 95 discs this weekend, 12 in total, I didn't find OSR1.0 or OSR2.0 versions on any of them. I wonder if this dumped OSR1.0 wasn't partially modified. In fact, I didn't find anything about these two versions in pt-br. If they exist they are extremely rare, the OEM versions, OSR2.1 and 2.5 are easier. I'll keep looking....
80A6C3BE800F5910C8E094F0586C291F09FA422C *[PTB] win95a_osr1.0_OEM-FullSetup_cd_type09_00000000.iso 80A6C3BE800F5910C8E094F0586C291F09FA422C *[PTB] win95a_osr1.0_OEM-Companion_cd_type09_00000000.iso sorry my mistake (have not opdate my hash table) Companion cd : - no setup.exe, OEMsetup.exe - need a breanstalled win95a_osr1.0 on the PC - only for repair (or add stuff from the CD). damaged HD => Companion cd is not usable for new clean install (always need a recover of a HD-Backup first)
homebrew floppyset's based on montly shipment cd's - MSDN-Developer Network and / or - MSDN-Development Platform Windows 95 floppy (pt-br)_Win95 2 (mix of all) Windows 95 floppy (pt-br)_Win95 3 Windows 95 floppy (pt-br)_Win95 4 seems valid GDR OEM-Floppyset Windows 95 floppy (pt-br)_Win95 1 @kdesktop do you have artwork for this set ? Hash for clean up Images (defragmented, Last access Timestamps removed, etc.) Code: ;Windows 95 GDR (OEM Full Install - Floppy type 4) 7C8CB9525055EAD374971C628793D20E7FFF85C3 *br_win95_Boot00_OEM-GDR_19951121.img 78D0E3630089225E55E8DB1DBAA3B9DD894CB5F7 *br_win95_Disk01_OEM-GDR_19951121_56019-461-0103145.img 8E1048B3EF1E94033DB3592495A484E4C6A2D345 *br_win95_Disk02_OEM-GDR_19951121.img ;Windows 95 GDR (Retail Upgrade - Floppy type 3) ;MISSING *br_win95_Disk01_CCP-GDR_19951121_XXXXX-XXX-XXXXXXX.img ;MISSING *br_win95_Disk02_CCP-GDR_19951121.img ;Windows 95 GDR (Shared OEM and Upgrade - Floppy) 96D8EC6BC66955293EDDDCEB9253BE305C280D5E *br_win95_Disk03_FRE-GDR_19951121.img BC19A1586D7A996523ABA119572314FFC8D666EE *br_win95_Disk04_FRE-GDR_19951121.img 6D251DC2746B37FD8F76B67845BFE91FB71DD727 *br_win95_Disk05_FRE-GDR_19951121.img F02CBECECA7C512941D82D44C813075F056FF5A1 *br_win95_Disk06_FRE-GDR_19951121.img A42227FD5CE954683ED2A867E430889AC760484F *br_win95_Disk07_FRE-GDR_19951121.img AD1334846B3F55401D905F1FEBB14025AC40164A *br_win95_Disk08_FRE-GDR_19951121.img 0E6B2AEF50580989602025BF155023C9A44BFE49 *br_win95_Disk09_FRE-GDR_19951121.img 55B3CE7B7786A36C89EA5CF4AFC6119B36D08157 *br_win95_Disk10_FRE-GDR_19951121.img 6D67C0C64197D091D7F37B6E2966FE3BD56CDA64 *br_win95_Disk11_FRE-GDR_19951121.img 73F2CB5C6CD6673035573F1E5C092526F87CB343 *br_win95_Disk12_FRE-GDR_19951121.img B91112D2B0C845F771F227BCB143182F8919A9DC *br_win95_Disk13_FRE-GDR_19951121.img
Win95 4 seems like it was originally from/destined for 1200 kb "5.25" floppies Some of them are promising candidates but have'nt really looked closely at them yet. You would think that the DMF images atleast are good but...: Windows 95 (Disco 02).img and Windows 95 (Disco 03).img share same sector 0 Windows 95 (Disco 02).img have the header for Disk 3 but the file content for these two images are correct.
Sorry, I blaim my keyboard for my writing. I agree, what I meant is that sector 0 is identical between these two. It's "uniqueness" is a timestamping - a DWORD. It's not a universal blueprint thoe. Meaning: you find it on Microsoft dos 4 > and I don't know for how long this was used. *.nix has their own trickery afaik. Agree.
it loocks like a mocrosoft bug on disc 2 coz bootsector say ofset 0x002B ÐBRWIN95_D3 Root Directory say ofset 0x0E00 ÐBRWIN95_D2 such things usualy never happen on homebrew images not always it depend on the masterring software it is only a timestamp if you use Format.com however i fixed ofset 0x002B ÐBRWIN95_D3 -> ÐBRWIN95_D2 (now it is unique) ofset 0x0027 FA -> FB (now Volume Serial Number is different) new hash for cleand up and fixed Disk02 1a0cc469edf7b432251bae04a89ffdfb87c860c7 *br_win95_Disk02_OEM-GDR_19951121.img
Product type Property (alternative interpretation / info) An entry in the "Setuppp.inf" file stipulates which type of serial number is requested. Windows 95/ A/B version Product type = 9 This is the normal entry in Setuppp.inf. It means that the setup queries the 4 partial OEM series number. xxxxx-oem-xxxxxx-xxxxx The setup will not continue without a correct number. Product type = 2, = 5 and = 6 These entries cause the setup to query a 10-digit product number. This can be ignored with 'ignoring' and the installation continues. The setup does not carry out an update test with any of these entries. This indicates that there is at least one more difference in the update version. Producttype = 1 Used for installations of Windows on computers where the license is bought extra (e.g. campus licenses for universities). There is a separate CD edition (depending on the language in different colors; Europe has the color brown) with which employees of e.g. EDP centers can install the computers and then only have the number of computers (or their software) licensed. This is also available for all other Microsoft products (Windows NT, Office). With this entry there is no question about a serial number and there is no examination for an existing Windows. Info at least of the ProductType = 1 can also be used in the MSBatch.inf and then has priority before the entry in Setuppp.inf. Different numbers (in the MSBatch.inf) than the mentioned lead to an error message and the demolition of the setup.
Only verified reference I have is from the OPK image in the installation package Code: ;This batch is used for testing setup from OPK. [Setup] ProductType=1 Since Windows 98 and ME use product type 100 as reference to Microsoft Internal and that a 98 internal also has: Code: setuppp.inf ProductType=1 UPI=24264-XXX-XXXXXXX setupc.inf CCP=0 my logical assumption would suggest that product type 1 is Internal.
@Sajjo Very interesting discussion, I took a closer look after your post Win98 Win98 (100) Code: setupx.dll : hardcoded 100 (MS intern) setuppp.inf [data] ProductType=1 UPI=24264-XXX-XXXXXXX Win98 (111) Code: setupx.dll : hardcoded 111 (MSDN) setuppp.inf [data] ProductType=1 UPI=24264-XXX-XXXXXXX ProductType discribe only the Key System used on the SetupMedium (setupx.dll) different SetupMedium (like 100 and 111) have the same ProductType=1 (KeySystem) on win95 setupx.dll does not exist (or have no hardcoded medium) -> ProductType primarily only discribes the Key System SetupMedium is not definded, only the WIN95_04.CAB size (and the layout.inf) leave a conclusion to the SetupMedium I had not yet noticed such a distinction But this also explains things like ProductType = 8 who e.g. appear at OSR2 (on some languages)
I'm updating #91 and #97 as it goes... Atleast that seem to appear on enu floppies dated back to 1995-07-11 ProductType=5, 6 and 7 is (for me) a riddle, wrapped in a mystery, inside an enigma atm.
Code: ;Microsoft Windows 95 Year 2000 Update (1999-11) D763D66A954C10CD1BBB9FFA5CAB54C1D652A91F *[ENU] W95Y2K.exe 3A252A0D4457A4024B769DFFCF348ECAFD01BB1C *[ARE] W95Y2K.exe 0224B6E8D6E1266D7957C816C6532355E0E5F623 *[ARL] W95Y2K.exe 2FC132E8231C5F38DA3DC90F001CBC988566D15A *[CSY] W95Y2K.exe 3A0035F40752F4BD52AAF0C35D89377955339204 *[DAN] W95Y2K.exe 9BE0CA6EFF45E7ED7F3C66CE513734806B3A7890 *[DEU] W95Y2K.exe 3391390F291E912AC779B01BB324CCAEC892A5FF *[ESN] W95Y2K.exe 25A1617D93825345AA52215C945129D01CA3F585 *[ESN] W95Y2K_OEM.exe F9F56E681EB0F58A8B5E37BE3D7B26B6B995D1ED *[FIN] W95Y2K.exe A475933FAEC95B5F6BB1F93633E5CEF595292625 *[FRA] W95Y2K.exe ;MISSING Greek *[GRK] W95Y2K.exe 900BB37E46FBEECE6F2275A71826C86349ACE0E9 *[HEE] W95Y2K.exe 5294408BC5D01BD5C24E63D180253E0A4E534547 *[HEL] W95Y2K.exe D1E39FA06AB1F9C2A8545812C64056360AD233F2 *[HUN] W95Y2K.exe 202AA78813FAFE9FFA962C91DC478CAFCD9E4734 *[ITA] W95Y2K.exe C2A998B6424AEF1A88134DEF765F2AA3F00F1C18 *[JPN] W95Y2K.exe FFB0B889A06AFC55123953F843229863D138F6AD *[JPN] W95Y2K-NEC.exe 765F51D07AF93E3FC16A8E28920A24C39814243A *[KOR] W95Y2K.exe DDC32B13B775CF16DDF888A4050EF9AEAFF81B06 *[NLD] W95Y2K.exe F38E8423AE147B9CD61692661C44C96198CA16BD *[NOR] W95Y2K.exe F75C8ABB38F6F8071F7DBBA874A7255648806C66 *[PLK] W95Y2K.exe 3CE9E9CE994954ACE79DB3898226A7874E0576E9 *[PLK] W95Y2K_OEM.exe BBCD247B99E5EF15B60A1267A79363E6D78178F7 *[PTB] W95Y2K.exe 14DDA41C3A9AE711B3AF458BD9150C3CBDD1478A *[PTG] W95Y2K.exe 55AB2AFEB8AEEB078411863920ABFEBD6A91B6C1 *[RUS] W95Y2K.exe ;MISSING Slovak *[SLK] W95Y2K.exe ;MISSING Slowenien *[SLO] W95Y2K.exe 789D1C986BAE80E6DED54EAAE69010036CE3F648 *[SVN] W95Y2K.exe 417A89A1179D28904F555537BFF4EE69B4DF06F2 *[THE] W95Y2K.exe ;MISSING Thai locally *[THL] W95Y2K.exe ;MISSING Turkish *[TRK] W95Y2K.exe 534F31AFA6FB5157F18ECAEEBDF964C2AFC41A5D *[CHS] W95Y2K.exe F1838CB0427432CDBB9A37E53AB942A552384E7E *[CHT] W95Y2K.exe It would be great if the missing files still appear