Jump to content
HWBOT Community Forums

DrSwizz

Members
  • Posts

    111
  • Joined

  • Last visited

Everything posted by DrSwizz

  1. There are already plenty of hwbot submissions that are not 100% correct that are being given rewards (just browse the databse and you will see it yourself) It is not what I desire, but it is the reality that we have to deal with. What I proposed is just one way of handling all those faulty submissions.
  2. Instead of thinking "all or nothing" regarding benchmark scores that are not 100% correctly validated I think it would make more sense to add a 20-30% point penalty to such scores of they don't seem to be suspiciously high. That way those scores could still remain in the database and be awarded some points, but the incentive to always submit correctly validated scores would still remain more or less the same, even in relation to future rule changes. :-)
  3. Client software: http://www.distributed.net/Download_clients Tables with benchmarking data: http://n1cgi.distributed.net/speed/ Run the client with the prameter "-benchmark" from a command prompt/terminal window.
  4. I was positively surprised to see that it did work just fine on my old Pentium I. I did not take very long to run either. :-) I wonder how cheat-proof it is though? I'd rather see that you add the distributed.net client benchmark to HWBot though (you can benchmark multiple OSes, CPU architectures and GPUs with a single benchmark and it is as simple as pifast). :-)
  5. Perhaps you could make it possible for this to be selected when each individual thread is created? That would allow both an open "general discussion" as well as anonymous reports of cheating. (or is that difficult to implement without modification of the forum software?)
  6. I noticed that the first generation of K6 CPUs are missing from the hardware database. Please add 200 and 233MHz "model 6" CPUs to the database to the database and change the entry for the 166MHz "little foot" CPU to 166MHz "model 6". Information regarding the the different K6 models can be found at wikipedia: http://en.wikipedia.org/wiki/AMD_K6#Models
  7. Try using the "Force recalculation of best submissions" button, that worked for me when my achievements failed to update automatically. :-)
  8. Yes I am using version 1.55. I might not have installed the CPU-Z 1.44 "library" on some of the rigs though (I don't really remember). At first I thought the systems "only" where unstable, but two weeks ago I began experimenting with underclocking for a contest a Xtremesystems. At one point I was running wPrime on three systems simultaneously and wPrime detected that "I had cheated" on all of them more or less at the same time. All the systems where underclocked and had relaxed timings for memory/cache/system busses. That convinced me that this must be an issue with wPrime and not with my software/hardware.
  9. I have had this issue on several systems: I have used NT 4.0sp6, XP SP1 & XP SP2
  10. The manual copy-waza was really funny!
  11. I was not aware there was a difference between them. I never adjust the clock thru windows, I only set it in the BIOS.
  12. I have been benching some old system (mostly 486 and early Pentium) and I have been having serious issues with wPrime. No matter what I do wPrimes cheat detection system seem is being triggered around midnight. I have experimented with with different settings for the system (cache/system/memory timings; over/underclocking etc), but no matter what I do the anti-cheating system still gives me false positives. Could someone please help me out?
  13. You are not alone. :-) For me it is the joy of tinkering with "new" hardware that is most rewarding.
  14. Thanks for the input. You are right about the window placement. I am going to try to improve my result little a bit too :-)
  15. Would somebody please give me some feedback on this screenshot I made: http://hwbot.org/signature.img?iid=425287&thumb=false&iehack=.jpg (It is for a SuperPi run on an 486DX2-66 @80MHz) Is it alright? Should I use some other indentification utility for the CPU?
  16. As I wrote in the title: Could you please add: Intel 486 DX-25 Intel 486 DX2-50 Overdrive Edit: Please add "TMC PAT48PG" and "J-403TG 486 GREEN VLB" motherboards too :-)
  17. I cannot seem to find anything called "sepcs" in the GPU-section in Everest. It doesn't really matter though, as Everest was not capable of detecting the real clock speed for the GPU. It assumed the GPU was running at the same speed as the memory was. A GPU-Z validation: http://www.techpowerup.com/gpuz/7eepk/ :-)
  18. Please don't disable the points for the old benchmarks entirely; It is fun to benchmark old hardware too you know. :-) Instead you could make those benchmarks give no points or a low amount of poings to newer cards, but still make it possible to recieve points when you benchmark older hardware.
×
×
  • Create New...