Jump to content

Massman

Members
  • Joined

  • Last visited

Everything posted by Massman

  1. It was not fake or a cheat. The bot didn't scan the SLi tag he used. No need to start calling someone a cheater
  2. Massman replied to Massman's post in a topic in Team Discussions
    Left is the solid alu pot, on the right KP's evo
  3. Massman posted a post in a topic in Team Discussions
    Great news fellow benchers Blind, a faithful OCTB member, is getting his rig ready to use about 20l of ln²
  4. Massman replied to mtzki's post in a topic in Team Discussions
    octf is has gone shopping I see At octb we can only rely on one cascade and a few single stages. For ln² we have the dragon evo ready and some low-end pots
  5. Just put the peeps who did the benches in the comment box like here
  6. My cpu speed wasn't 1621, but 1921, so I changed it. The biggest difference however lies in the 64kb <-> 512kb l2 cache
  7. Massman replied to Tazzler's post in a topic in General overclocking
    Interesting, would be a nice feature.
  8. Not every wrong entry is cheating, eh
  9. Will block it until we have further information. His score is indeed way too high for his setup.
  10. Impressive work, isn't it? Best NV bencher in the world
  11. looks like everything is in order now
  12. Hausner, I verified all your results and they won't be changed again
  13. Can you give us the hwbot result link ?
  14. Massman replied to v|ady's post in a topic in Submission & member moderation
    Edited, thx for letting us know
  15. Massman replied to K404's post in a topic in Offtopic
    And to eat ... to eat more ... to eat too much
  16. His FM links say 512MB, so in fact they are 256MB.
  17. He has editted them, so I guess all scores are done with 256MB cards
  18. All fixed, thanks for letting us know.
  19. Checked, fixed and verified today, sorry about the delay, but I had some examination and of course all the alcohol afterwards
  20. thanks mate, this really helps when moderating the results. Great input, bro
  21. Some results inquiring the x1950xt(x) were reported today. Mostly it's just a scanning error and every reported results will be solved