Jump to content

Massman

Members
  • Joined

  • Last visited

Everything posted by Massman

  1. => Waouh! What a wonderful cooling or what a great score! <=
  2. That shouldn't be the rule :-/
  3. I had to reboot the server twice today :-)
  4. If you're aiming for points in very popular hardware categories, it's indeed a bit difficult to get a lot of points fast. However, in most low-end categories, there are points to grab with hardware on air cooling . Note that with air cooling, you'd better go for 3D benching
  5. http://www.hwbot.org/result.do?resultId=785656 ?
  6. For those who're interested: http://www.xbitlabs.com/news/video/display/20030523152718.html
  7. The driver is indeed bugged for 44.03. This is a pretty weird situation. On the one hand, this driver is an official bugged driver (actually, an Nvidia cheat driver), but on the other hand, it's available to all. Hmm ...
  8. Massman replied to ReverendMaynard's post in a topic in Team Discussions
    Remove the person without scores and team from where?
  9. Super iniative to post a thread here, I love it!
  10. No, you have problems. Using a software based ramdisk has been cheating ever since it came out, lying to the hwbot crew in the forums is definitly not appreciated let alone the aggressive language you used in this (and other) threads.
  11. Try to contact futuremark, maybe they can help you make that link public. The screenshot misses too much vital information to serve as propper verification, though .
  12. Do you have a verification link? For proper screenshot verification, you really need the 3Dmark03 program openen + settings of the benchmark must be visible + subtest details must be visible.
  13. That virus scan is quite high, especially for just 4 x Iram
  14. Incorrect: http://hwbot.org/forum/showpost.php?p=30254&postcount=185
  15. So, even though you find it rediculous to block a score because of missing subtest details, you will be reporting all scores because yours got blocked as well? //edit: don't start with justice ... we're not some kind of government or court of justice
  16. We're talking years. Making GPU-Z absolutely obligatory was one of the very first written rules here at Hwbot. I distinctivly remember a crew member blocking KP's AM3 world record because GPU-Z was not present (summer '08).
  17. GPU-Z is just absolutely mandatory for 3D benchmarks. Rivatuner/atitool and other sort-a-like programs are only enough verification when GPU-Z fails to recognise the videocard.
  18. Memory specs are chosen from our Memory database, which includes both graphic memory as 'normal' memory. There's no real point in spending resources to change that :-P
  19. We don't block scores older than 6 months exactly to prevent people from reporting just to gain points. As this score is from 2006 (!), it won't be blocked because of the lack of propper verification.
  20. We're not talking about the hardware sharing issue here. We're talking about the reason why the score was suspicious and got blocked. It's pretty simple: suspicious + not following rules = blocked score. I believe no one is still on the sharing issue, so only problem is the subtest at the moment. But, does solving the first issue automatically solves the second one? If a man is brought to justice for murder and theft and turns out he didn't kill, does that mean he shouldn't be convicted for theft?
  21. 1/ It's not upto Hwbot to prove fault, it's upto the user to point out that we're incorrect. I believe the crew is very, very easy on this subject. 2/ It's not because we can't prove it's okay. If we have doubts, we want to know what's up.
  22. That's NOT what I said! And I believe I made that very clear.
  23. They were suspicious because of hardware sharing, hence this thread.