>Something is wrong with the OS/2 client timing's. The heavier the CPU load
>on my machine, the faster the client runs. Look at
>this:
>Processor 1 -- 2^29 complementary pairs of keys starting with
>6445D5C880010101
>................................................................
>................................................................
>................................................................
>................................................................ Processor 1
>-- Elapsed time: 2489 seconds
>Processor 1 -- Key not found
>Processor 1 -- 2^29 complementary pairs of keys starting with
>6162E52901010101
>................................................................
>................................................................
>................................................................
>................................................................ Processor 1
>-- Elapsed time: 1223 seconds
>Processor 1 -- Key not found
>On a completely idle system, the elapsed time is just over 2600 seconds for
>2^29 pairs. As the load increases (that is, I start other programs and less
>CPU is available to deschall.exe), the elapsed time decreases. In fact, now
>it's testing 2^30 pairs, because it thinks it's much faster now!
The reverse is true on my system.
>This might explaing why I only get 475k pairs/sec.
This number doesn't look right for a P6 200Mhz system.
-- Milton mwf@ibm.netOS/2 Warp V4 - Where I Want To Be Today! And the Magic Continues! ----------------------------------------------------------------------- For all your Web Space / Web Pages Design / Web Site Manager Software / Web Servers needs..... http://www.adgrafix.com/info/mforteii/ -----------------------------------------------------------------------