Jump to content

jfpoole

Members
  • Content count

    16
  • Joined

  • Last visited

About jfpoole

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL
    http://www.geekpatrol.ca/

Profile Information

  • Location
    Waterloo, Ontario
  1. Geekbench only detects 1 core and 1 thread

    What version of Geekbench are you using?
  2. Leopard not running in 64-bit?

    Geekbench 2 is only available as a 32-bit application on Mac OS X because it uses some APIs that aren't available to 64-bit applications under Tiger. Once Leopard is released there will be a 64-bit version for Mac OS X (although like other platforms the 64-bit version will only be available to registered users).
  3. Geekbench 2.0

    Geekbench 2.0.2 is out; it should fix the issues people are seeing on AMD-based systems.
  4. Geekbench 2.0

    Thanks for the offer, but I don't think it's necessary. There's a known problem with Geekbench 2.0.1 on AMD-based Hackintoshes which I'll hopefully be able to fix for Geekbench 2.0.2 (which I'm hoping to release sometime over the next couple of weeks). I'll keep you guys posted.
  5. Geekbench 2.0

    There is a 64-bit version in the works, and it'll be made available around the time Leopard is released (it'll be Leopard-only, too, given the 64-bit limitations present in Tiger).
  6. Geekbench 2.0

    I really think that as the developer behind Geekbench, I should be the one that gets the system. Speaking of scores, you can view my Geekbench scores here.
  7. Geekbench 2.0

    Hi folks, I'm John, the developer behind Geekbench. I thought I'd let y'all know that there's a new version of Geekbench available. I think Geekbench 2.0 is a huge improvement over Geekbench 2006, and I hope you'll think so, too. You can download both the Mac OS X and Windows versions of Geekbench 2.0 from the Geekbench website. If you've got any questions, please let me know.
  8. Geekbench 2.0 Beta

    Hi folks, I'm John, the developer behind Geekbench. Since there are a lot of people here that use Geekbench I thought I'd let everyone know that I'm setting up a private beta for the next version of Geekbench. If you're interested you can sign up here. If you've got any questions, please let me know.
  9. Performance Comparison of Most Current CPUs

    I mentioned this over at Geek Patrol, but I think it bears repeating here.
  10. I propose this to be the new standard benchmark

    I've got a similar configuration under Windows (with an Intel DQ965GF motherboard and 1GB OCZ DDR2-667 4-4-4-12) and I get a score of 220.2 in 32-bit mode and a score of 253.2 in 64-bit mode. I'm amused the 32-bit scores are so close!
  11. I propose this to be the new standard benchmark

    I'm the developer behind Geekbench, and I'm glad you guys find it useful! I must say it's been interesting seeing the results from both Hackintoshes and Macintoshes. Anyway, here are my Geekbench scores for my iMac Core 2 Duo: Mac OS X 32-bit: 206.7 Mac OS X 64-bit: 220.7
  12. If setting the FSB speed incorrectly causes the system clock to go slow or fast (depending if the speed was over-exaggerated or under-exaggerated) then it makes sense that benchmark scores will be, well, wonky since Geekbench (and I'd imagine Xbench) uses the system clock to time benchmarks. For example, if the FSB is over-exaggerated, then the system clock will run slow. A benchmark that takes a second to run will appear to take, oh, a half-second to run to the computer (and Geekbench), so the benchmark scores are double what they should be. At least I now know what's up with the 12GHz Xeon....
  13. Yeah. Geekbench uses high-resolution timers that aren't always accurate on virtual machines, which is why some of the results look reasonable, while other results look quite unreasonable. If you want accurate timers under VMWare (say if you want somewhat accurate benchmarks using Geekbench), you can set monitor_control.virtual_rdtsc = false in the virtual machine configuration file. It might cause the guest OS to crash, though, so be careful!
  14. Applications with identity crisis

    ./ just tells the shell (i.e., the command line) to look for the specified executable (in this case geekbench) in the current directory. Most Unix variants (including Mac OS X) don't look for executables in the current directory for security reasons; you have to tell 'em to look in the current directory explicitly.
  15. Applications with identity crisis

    Try running "./geekbench" instead of "geekbench" at the command line -- that should get it to work.
×