1st post updated with fixes for PIDGEN loading. Also this build has the WIP of full language translations. I have made a german and spanish language file, that has all translations in it. I got halfway through french and got tired. Feel free to complete the other languages and if possible upload here so I can add them. One thing that I haven't handled is the naming of the Generate, Validate and Scan buttons. They will appear in the correct language but after 1 click will revert back to english. I just haven't implemented it yet but I needed to fix PIDGEN issue and re-upload. I have had to move positions of controls because different languages were taking up different amounts of space. The issue will probably get worse but someone may have better translations than me.
yeah thats intentional. The way I understand it is that OEM versions of windows do not allow upgrading a previous version of windows. The OEM install will only allow you to delete old version and start clean, so no “Upgrade” version. Can you check the setup files on that cd and see if it has “CCP =1”.
@Dark Dinosaur It was so easy last time you did it with ChatGPT, like to do it again? Code: Arabic Chinese Simplified Chinese Traditional Czech Danish Dutch English Finnish French German Greek Hebrew Hungarian Italian Japanese Korean Norwegian Polish Portuguese Brazil Portuguese Portugal Russian Slovak Slovenian Spanish Swedish Turkish Thai
I have upgrade laying around somewhere, will check asap And no, that spesific cd is not in my possession but upgrades I have...
If the wants installation immediately and wont let you logon that means 100% you used a Product Key with an invalid Product ID for that version. That's why the Tables in dpcdll are not totally accurate, in that a Product ID range labeled Retail could be either for the actual Retail version of the oem-nonslp version but not both, so the table is not clear. Product ID ranges tagged as OEM are only for OEM-SLP versions, and thats why I used OEM-SLP in the Tool to try to make it clear.
Minor adjustments. Baseline: hex values starting with value "0" is normally omitted, I just added this value so it aligns. Cosmetic. Pidgen: reduced pidgen size in the series of 0x00 - 0x3F to roughly 1/3 and small adjustments to a few in the series from 0x40 - 0x89. Cosmetic. Bumping this one as well #199 Language folder not added in attached file. Fyi There was a request for a "one pidgen to rule them all kinda type" some times back. It's possible to create this, the issue is that tool will not give information about which BINK id key was validated against so this is kinda useless in this context.
This is possible. The Bink ID is already part of the data returned from the pidgen.dll when validating a key. I never tried to make a pidgen file with every Bink resource in it. Did you make such a pidgen? did it work with the tool?
I only did a brief test with 3 BINKs in one pidgen, tool reports back which pidgen was used with it's name but not BINK id specific (other than retail/oem) If I have two retail and one oem BINK or vice versa embedded the dilemma is soon getting obvious...
Yes because that's how I wrote the tool. It is a trivial change to make the tool report back the Bink ID. I already made a test build that does it but because of the filename already containing the BINK ID I didn't think it was necessary. I am working on another rewrite/version of the tool that will use a traditional menu for most of the options. This way the interface does get corrupted due to a different languages not being able to fit in the space provided in the window. I've never coded with menus before so I am learning along the way on this version.