no i want you to see how to product id is displayed in wondows posready 2009 when u go to properties of my computer
oh so the tool is generating it as oem product id but when u validate it is retail. weird? obviously i’ll have to look over it and see whats happening
I'll give it a spinn with channel ID 620 again as well since @un user listed that as OEM - stay tuned
hi @pottzman I have installed posready 2009, when you made ECC tool, and, indeed it does display values, identical with your tool.
Got it, that's a cool feature Fyi: With "wrong" prefix - can not cancel. "N" was added later (Windows 7 era? sorry, Windows 8 era) anyway, have not tested them all but i know "O" is not valid, same behaviour. Spoiler
You can customize up to 4 alpha numeric characters in product key at the beginning with a valid characters of "BCDFGHJKMPQRTVWXY2346789" Setting 1 is okay, 2 sure, 3 and you will get a notable delay in generating key etc.
ok think I fixed it. yeah with XP era product keys you can enter up to 3 prefix characters......(but specifying 3 characters can and probably will take a very very long time to calculate) better to limit it to only 2 characters. with 2003 era product keys you can only enter 1 prefix character OR you can tailor the first 3 character by entering a decimal value from 0 up to 1023. with 0 putting bias on the product key starting with "BB" up to 3 it will then change to "BC" etc all the way to 1023 will bias "XV" I have also thought about Windows Embedded POSReady 2009 and the way it displays the product key. I am not going to change the fundamental way the tool represents Product IDs as this appears to be an exception to the rule which has always been an "even" BINK ID number is for retail product keys and an "odd" BINK ID is for OEM product keys and if another software uses BINK ID 0x0D there is no guarantee that it will follow this one off exception, thus creating another problem. I have however made changes to the way the product will display Product ID when generating and validating as follows. If the "Base Line" option is selected and you generate a product key it will display using the standard rules : even is retail, odd is oem. Also if the Base Line option is checked when validating product keys the Tool will only validate the product key(s) against pidgen dlls that follow the naming convention of "PIDGEN-BINK ??????.dll" where "??????" is any name eg) "PIDGEN-BINK ID00-01.dll". So the name MUST start with "PIDGEN-BINK". If the "Base Line" option is not selected and you generate a product key it will follow the standard rules again except for a product key that uses BINKID 0x0D to account for this 1 exception. Also when validating when "Base Line" is not selected the product key(s) will only validate against pidgen dlls that do not start with "PIDGEN-BINK" but use any other name eg "PIDGEN-Windows 98.dll" Spoiler: checksum Code: File: EllipticCurveTool.exe CRC-32: 33cd12a0 MD4: 386a3c21b771c225829b26e240d0933a MD5: 6d2f4a715ccb8fe0244b575712020573 SHA-1: 2ef718a868920ed4861ba000ef46770289386256
Please revert back. It is not a good improvement. It is not possible to generate without select base line. This means we will not ever can use validate option. When there is 4 binks will put 4 same pidgen named every binks? It is so silly. You can do better improvements. Everytime i need to manually enter n and k values. It need to save them. But when saving should do that pidgen name/location, all binks, all n, k values of all binks together. It will be more easy to select just a pidgen and all binks and differenet n, k values comes automatically and matched, and saved. I found a better idea. When a pidgen selected software wilk read bink name for example 0D. There will be a value.ini something file in program folder. It contains n,k values per bink ids matched like this 0D n= 0D k= Etc. Will take matched value from ini file and put into software when related bink selected. Other values normally autofilled now else then n and k. User manually fill n, k values by hand
Why not? Have you saved a Keyset and specified minimum and maximum Product ID ranges, given it a name of the software it is for eg) Windows XP Professional? and pressed "Save Keyset". It will save a new keyset file in the "Keyset/Software" subfolder. now when "Base Line" is not checked your new keyset you just made will be available with the specidic Product ID Ranges for that particular product rather than just a basic list of BINK IDs that cover Product IDs from 000-000000 to 999-999999. Kind of the same as the above point only it is for validating not generating. You mean everytime you run the program? Maybe.....but as an example, Someone wants to do it how you described but for the software "Office 2007" ok. they import the file and it enters n and k values and sets a minimum Product ID of 000-000000 and a maximum of 999-999999. the user generates a product key and the Product ID is XXXXX-246-3416786-65XXX. when the user tries to install the software it will fail.....why? because office 2007 only accepts Keys that have a Channel ID from 777 to 999. Then people will be telling me the program doesnt work because the product key didnt work. If you want to use the program import your own pidgen or mso file, calculate your own n and k values only once, narrow down the Product ID ranges to suit your program, Enter a "useful" name (do not put "bink" in the name) in the "Name" box and press save. Congratulations, you just made a keyset for your particular software, that will be available if the "Base Line" option in NOT checked, that you can use over and over again.
Why not release a complete software for everyone to use, just like XP Calculator, open and ready to use
When pidgen selected it creates keybase folder. If there is saved data program will not overwrite it? It will overwrite only when save bink clicked? If a pidgen selected how the user will know which bink is used? Saved or the one new created from pidgen? Think about a value.ini that contains n, k values. Will not affect how u design your current software but will be very usefull for me. If the user does not create a value.ini program will work as it is works now. I do not use keybase folder. For me it is useless. Also never seen the program created any file inside software folder. It is everytime empty. (One time i have seen a file but could not resee again) I just desire everytime i select physical pidgen and bink of it the program autofill my saved n, k values for that bink. If the user does not know to change ranges he can not use the software too. There are too many stuff he needs to know that is not written anywhere. Also i does not know how the program works. Trying to learn by myself last a few weeks. None of the hundred different rage keys i generated work. I needed to find real ranges that mic. used in their real keys. There is also need knowledge. You can not give users everything prepared. If you think rages so much you can add value.ini range option too. User can edit and save desired ranges per bink in it. When bink selected program also can read value.ini and fill ranges too. I also change everytime range values by hand. Your program do it automatically per bink? No. Also can not do because there are different ranges. Maybe can ask which range determined from pidgen do you want to select. It can be far future development for now. This program for expert users. I personally like it to be complex. I can customise eveything in a key. If it will be very easy for normal day users we can not customise so many parameters. Normal day users can use 4in1 It is very easy. For key checking you can do what you want. I just said my idea. I can continue to use CHKPIDS. It support x64 bits. Or i can use previous old version. It makes what i want for now.
@pottzman Thank you I see what you mean and last change did improve - others should chime in their opinion as well Spoiler Use EllipticCurveTool with provided keysets just for comparison and notice the behaviour. Try with both Base Line ticked and without @pottzman - the more I learn about the features the more i love it. This is a very advanced and powerfull tool, far better than others. And with ks2 files properly configured and placed in right folder: the gui is so tiny and provides exactly what you need (nothing more, nothing less) I admit there is a learning curve but that's just part of the fun
You do not need to have PID ranges in your Curve Name.........you can use the "Add" "Del" buttons to add or delete Product ID ranges as you see fit. For "BaseLine" keysets just leave Product ID range Min and Max as "000" and "999" so it covers everything, then create specific keysets for specific software that has 1 or more Product ID ranges stored in its own keyset that is specific to that software. I think you are starting to understand how it works.
not if you select the "Prompt" option. If a keyset file already exists it will give you a prompt warning you that a keyset already exists and you can select "no" so it does not overwrite it.