@old navy,
Maybe try with new alpha stings. I managed to find some that worked. After initial observation like You. If You get one that is comparable measured You can IMHO calculate the rest.
Seems to work with a mixture of whitelist (wants a real browser name that it knows, did not accept KMlite name = Unknown browser) and keeps a has been measured already browser list.
Chrome 4.1.489.... / 1782 (used to compare my PC with the PCs already measured)
1.6.a4 / 1226
1.7.a1 / 1502
1.1.6 / 301 // maybe You can get an 1.1.4 or so string to work.
a. 1.5. / 318 // with GRE compiled to use mozcrt19.dll = slightly faster.
Pale Moon 3.6.3 / 1598
Pale Moon is a Firefox optimised for Windows - had to use another string to get it measured. Based on comparisons from the past I assume that a final K-Meleon 1.7 will be about 10 - 15% faster (when Dorian optimizes in the same way).
Edited 1 time(s). Last edit at 05/17/2010 01:23AM by guenter.