h hmmm u may need to fiddle with ur dpi scaling. alternatively it should have created a settings.ini file. you could try to change the mode option from 0 to 1 and save it.
@Hacker?pcs You don't really need the script to compute N, by far the fastest way that currently exists was the one I mentioned :
amazing job on this tool! you wouldn't happen to still have a copy of the source code would you? mostly looking to compare notes on the algorithms
I probably missed that and feel silly now. Thought I really needed an old forum account for it to work. My bad and thanks!
There are several factors that influence this, some of them without mentioning them all: - ECDLP Solver with CUDA or NOT. - Type of Curve. - Number of CPU cores. - P size - Order size n For XP it's relatively fast. Regards,
Maybe is worth to mention this.... For XPE there are a few subranges, Also for wepos, posready and wes2009. There are some ranges for XPE setups. I will update list when i have some more time.
PID Sequences for PosReady 2009: 620 BINKID_0D OEM 621 BINKID_0D VOL 622 BINKID_0D 125 Days 623 BINKID_0D 370 Days
PID Sequences for WES 2009: 900 BINKID_0D Setup WES OEM 992 BINKID_0D Setup WES Evaluation 995 BINKID_0D Setup WES Academic Alliance 996 BINKID_0D 125 Days Runtime Image Licensing PID WES Evaluation 997 BINKID_0D 370 Days Runtime Image Licensing PID WES Academic Alliance 940 BINKID_0D No Expiration Runtime Image Licensing PID WES OEM