Just out of curiousity, I thought I'd try disabling Beamsync on my latest acquisition, my 1.5Ghz 12" Powerbook.
I'd tried this before on either my Quad or Dual G5 with no noticeable difference, using the Let 1K Windows Bloom benchmark as reference.
On my Powerbook, using the same benchmark tool, the score had gone from 11 seconds to 16 seconds once beamsync was disabled, oh well I thought, I'll re-enable it and be back to normal again.
Not so, the benchmark was still at 16 seconds after rebooting.
My solution was to remove the windowserver.plist file that had presumably been created by the Terminal beamsync adjustment - and now it's back to 11 seconds (the plist contained no data apart from the beamsync flag just made).
That was on Tiger, I wanted to see how this effected my 17" DLSD on Leopard. Similar story, 13 seconds without adjustment, 18 seconds with.
I realise this is all based on one crude benchmark but I've never felt any improvement in any other respect when tinkering with the beamsync settings - maybe best left alone useless you are using a CRT?
I'd tried this before on either my Quad or Dual G5 with no noticeable difference, using the Let 1K Windows Bloom benchmark as reference.
On my Powerbook, using the same benchmark tool, the score had gone from 11 seconds to 16 seconds once beamsync was disabled, oh well I thought, I'll re-enable it and be back to normal again.
Not so, the benchmark was still at 16 seconds after rebooting.
My solution was to remove the windowserver.plist file that had presumably been created by the Terminal beamsync adjustment - and now it's back to 11 seconds (the plist contained no data apart from the beamsync flag just made).
That was on Tiger, I wanted to see how this effected my 17" DLSD on Leopard. Similar story, 13 seconds without adjustment, 18 seconds with.
I realise this is all based on one crude benchmark but I've never felt any improvement in any other respect when tinkering with the beamsync settings - maybe best left alone useless you are using a CRT?
