@Babass_ It's a combination of tools that I have incorporated in batch script past 4-5 years, it works very well for me but it's not given that it will work for everyone. I can pack them together and post a copy in convo with some instructions.
Yeah or you can just PM me with the stuff so I can try. I have a quick script that allows me to drag & drop ISO file to test it with MSCDCRC so maybe I can simply adapt it.
Hiya b55b2c4be3274829214b961446487f30bf2ae35f *Windows_98_PL.iso Indeed it's first edition 115 oem with java, but incorrectly dumped so with ultraiso signature. Other than that it looks as you would expect. (will keep this one, hopefully a good dump will surface in the future)
I noticed that there is few different bytes in setupx (apart from the product type of course). Sometimes only the product type is different, sometimes there are few more bytes here and there, not a lot maybe 5-6. Also setuppp is different between retail and upgrade I don't know if it has any impact. Also you noticed that on the message asking for the serial key the image on the left changes between OEM et Retail. On Retail versions it shows that CD cardboard sleeve with the yellow sticker on it, while on OEM versions it shows that printed certificate of authenticity paper with the serial on it.
Yeah, i didn't care to much about the details since i was changing file But it seems like the setupx deserves a little more investigation. It would be nifty to find a 103 set of French or a 104 set of English to better compare.
I remember doing a quick conversion on the floppy upgrade to make a full retail version, I just changed the product type in setupx and setuppp. It works and asks for a retail key. I expect setupx to have some more differences on original media tho.
But i don't understand setuppp.inf, only changing product type (and that is based on Win 95 style) And they seems in "reversed" order Code: ProductType=3 - SETUPPP.INF ProductType=3, SETUPC.INF CCP=1 - RTM CCP Floppy ProductType=4 - SETUPPP.INF ProductType=4 - UPI=(Product ID) - OEMUP=1, SETUPC.INF CCP=0 - RTM FPP Floppy and Code: 103 - Retail Floppy FPP 104 - Retail Floppy CCP
The UPI number also sometimes change but I think it's the case between different languages. I think it was different between English 104 set and French 103 set. In SETUPX I just changed 103 to 104. In SETUPPP I changed : Code: ProductType=3 To : Code: ProductType=4 UPI=24261-XXX-XXXXXXX OEMUP=1 And it seemed to work. Wonder if having just the product type different between 2 SETUPX enough to qualify the CAB as suspicious and likely homemade. I'll have to compare everything in French (better do it in the same language, I don't have any English ISO rn).
Most likely. But I don't think it's in play for this validation at all. Fun fact if you didn't know: 24261-aaa-bbbbbbc-ddeee If this was a retail key you were testing, "eee" is would always be generated by date and time when validating/generating/checking. Try it out and see how values change... Oem keys don't utilize this in this manner.