When the first IBM PC clones that were clocked faster than the original at 4.77 MHz appeared in the eighties, games freaks noticed that many of their games became faster. The Cessna 182 of the Sublogic flight simulator flew at the speed of a Eurofighter. So the bus clock speed is in principle not a good source for real time.
Microsoft has now learned this, but clearly Apple has not. If you carry out benchmarks such as Cinebench or Geekbench after overclocking, the benchmarks do not indicate any improvement in performance at first. But if you resort to a stopwatch, the higher performance resulting from overclocking can indeed be verified. You also notice that the system clock runs significantly faster after overclocking the computer.
Mac OS with time problems after overclocking
Unlike Windows, Linux and many Hackintosh versions, Mac OS uses the bus clock speed as the time source. It is compared with real time when booting up. Nor does time correction by means of the Mac OS NTP daemon succeed: It simply no longer works with a large discrepancy between the bus clock and real time.
Whereas programmers of the IBM PC XT had to be forgiven for using the bus clock speed because of inadequacies of its Intel 8253 timer module, it should be reasonable to expect more from Apple, who now only offer computers with modern HPET timers. After all, multimedia applications use the HPET module. So videos do not run faster after overclocking.
The only option for „normalising“ the time of the Mac Pro again is to restart without switching off the computer. ZDNet Clock is fundamentally „reboot-proof“. But there are a few snags. The latest series of the Mac Pro (Mac Pro 3.1) can indeed be overclocked in the ZDNet test up to 3241 MHz while remaining stable. But a reboot without crashing is only possible up to 3178 MHz. Carefree overclocking fun does not exist beyond this frequency.
The first-generation machine (Mac Pro 1.1) is a little more problematic. If you program the clock chip the computer cannot be rebooted any more – not even if you select the factory-set frequency. So the clock running too fast becomes a permanent annoyance.
The fact that the latest version of Mac Pro (Mac Pro 3.1) can be booted after overclocking also means that a higher frequency is possible under other operating systems. That is of particular interest because there has to date been no functioning overclocking tool for Windows. In contrast, the first-generation machine (Mac Pro 1.1) can be overclocked under Windows with SysTool.
Problem with standby mode
After waking up the Mac Pro from standby mode, the clock chip is reset by the operating system to the standard setting, with the result that the computer runs at the standard clock speed again, despite the overclocking frequency. Repeated overclocking with ZDNet Clock also only works again if the kernel extension associated with the utility is first loaded from memory. That can be achieved very easily via terminal, by inputting the following command:
kextunload -b de.zdnet.kext.overclock
This bug will be remedied with a later version of ZDNet Clock.
Neueste Kommentare
36 Kommentare zu Exclusive: ZDNet overclocking tool enhances performance of Mac Pro
Kommentar hinzufügenVielen Dank für Ihren Kommentar.
Ihr Kommentar wurde gespeichert und wartet auf Moderation.
Underclocken fuers MacBook
Auch wuenchenswert waere die Moeglichkeit einen Processor zu underclocken. Die MacBook Pros naemlich laufen sehr warm (deshalb auch sehr laut) unter voller Belastung. Optimal waere wenn der underclockte Rechner eine grosse Aufgabe langsam waehrend der Nacht bearbeiten koennte, ohne dass der Ventilator sich kaputt spinnt.
Unable to download – no file in ftp://ftp.zdnet.de/pcpro/download/swlib/08/ZDNet_Clock.tar.bz2/ directory.
There is no file in this directory for download.
?
I cant download!
Overclock nicht arbeit mit Mac Pro 3.1
(nur ein bicien Deutch)
Ich habe ein MacPro mit 2 x 2.8GHz quad-core Intel Xeon (model 3.1), 4GB RAM, und OS 10.5.3. Overclock nicht arbeit: "You can’t open the application ‚ZDNet Clock.app" because it is not supported on this architecture." Was ist loss?
Hilfe, bitte. Vielen dank!
(My high school German is rusty so here’s the English version:)
I have an eight-core Mac Pro with two 2.8GHz Intel Xeon quad-core processors, 4GB RAM, running OSX 10.5.3. When I try to run Clock, I get the error message "You can’t open the application ‚ZDNet Clock.app" because it is not supported on this architecture." I’ve tried removing the non-Apple RAM I have installed but still get the same message.
Any help would be appreciated. Thanks!
Kind regards,
James Boodley
(Ithaca, New York, USA)
Hi,
did you solved this problem with ZDnet overclocking because i have the same problem/error message.
It would be nice if you have the answer for me to solve this problem.
please let me know if you have.
best regards,
Mario
Faster time
Something to keep in mind when using this, your system clock is going to run fast. That is your time clock will get ahead of itself proportionally to the amount you’ve overclocked your mac pro.
Just keep it in mind :)
OK 2 or 3 times, suddenly won’t work anymore…
… since I made the "kextunload -b de.zdnet.kext.overclock" trick in a root user terminal. ??? …
Is there any reverse action ?
It worked great before, on MP 3,1, I’m disappointed
Computer: MacPro 2.1 Crashes
Can`t take the bus clock to more than 340 MHz before it crashes that`s only 7 MHz up
; (
Bad Ram=Bad Overclocking
As mentioned in the article, oc depends on the memory-modules. A lot of users do have problems with RAM from OCW when they try to overclock their Mac pro. Apple-Ram is ok for oc. Modules from Transcend and Kingston are even better.
This screws the system clock
Overclocking my MacPro results in my system clock running too fast. At the end of one day my clock will be 20 minutes ahead.
Try to reboot
If you have a MacPro3.1 (2008-Model) you can reboot to get the clock running correct. For earlier version of mac pro there is right now no solution.
time fix
if people are worried about the system clock getting out of sync, just run this in the terminal:
sudo ntpdate -u
If you download Lingon and make a launchdaemon, you can have it do it automatically every x minutes.
AW: time fix
good
Funktioniert nicht mit MacPro Quadcores (Nehalem)
Tja.
Mac Pro 3.2 Overclocked at 3.6 working perfect!
I overclocked my mac pro 2008 generation at 3.6 and works perfect. I will keep trying more, but my question is how to keep the computer overclocked after shoot it down. I mean, do I have to overclock the computer after each time that I turn it off? There is any way to make a permanent overclock?
Any way,
Thanks for this tool!
AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
It worked fine until I upgraded to Snow Leopard.
Now it tells me that it’s not compatible with OS.
AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
try with kernel 32 bits and after reboot on kernel 64 bits
AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
I cant get this to run on Snow Leopard either… any plans for an updated version? Or a work-around for the version check?
AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
mmmm
start on leopard
overclock your computer
re-boot on snow leopard
for me start on snow leopard 32bits (default)
overclock my computer
re-boot on snow leopard 64 bits (keys 6+4)
AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
Boot into Leopard? That’s not possible once you’ve upgraded to snow leopard. And the overclock only lasts until your computer gets powered down.
AW: AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
It is possible. The overclock resets only if you shutdown your mac, not if you restart it. Just boot into Leopard, overclock it and then restart it through Snow Leopard.
I use it that way and it works. Although I have encountered some kernel panics on Snow Leopard at overclock speeds which didn’t give me any trouble through Leopard before. So you’ll probably need to do the tests again if the machine is stable through snow leopard.
AW: AW: AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
Anyone know how to request the author of this take a look at 10.6?
AW: AW: AW: AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
Actually, never mind it works fine in Snow Leopard, at least in 32 bit mode.
AW: AW: AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
Please explain how you boot into Leopard after upgrading to Snow Leopard? Unless you have 2 separate installs.
AW: AW: AW: AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
And xgman, how did you get it running in 32-bit snowleopard? When the application runs, it clearly states that it only supports 10.5.x
AW: AW: AW: AW: AW: AW: AW: AW: AW: Mac Pro 3.2 Overclocked at 3.6 working perfect!
Seriously, I am utterly confused… I’ve googled this issue over and over and it seems like I’m the only one with this problem. I cannot get this tool running in 10.6.x AT ALL. I’ve used 32-bit mode, doesn’t work. I dont see how people get this to work UNLESS they have a 10.5.x partition which they boot to run this program. If someone is running this in Snow Leopard, please give me some help on how they got it working.
ZDNET Clock version 2
Could someone make a 64-bit version of this? It won’t run when my Mac Pro is in 64-bit mode, running Snow Leopard.
AW: ZDNET Clock version 2
+1 for that
Seems a shame that it doesn’t work on 64-bit Snow Leopard :-(
64-bit bitte
Ein weiterer Antrag für ein 64-Bit dieses Tool zu kompilieren, bitte. (If only for Folding@home)
AW: 64-bit bitte
Could you please advice if it possible to over-clock Mac Pro 4.1
Thanka
Al
DWDKDEP
Please make a overclocking tool for MacBook Pro 13 Inch 2GB ram 2.26 GHz.
kext module is missing – error under Snow Leopard
Hi Guys,
I did try all of the methods above, with no success at all.
I’m under Snow Leopard and I’m keep getting the error ‚kext module is not found ..‘ (from the console messages).
is there any workaround for this?
thank you all.
Red
Lion + 64 bits
Any chance of seeing this us full tool ported to compatibility with Mac Os X.7 (Lion)?
Please 64-bit Version for Lion
This would be VERY apprechiated. I use this tool for years and I love it. BTW: Overclocking in Snow Leopard and restarting in Lion doesn’t work for me.
A prayer
I would just like to use RAM at 800MHz instead of 677MHz on both iMac and MacBook Pro Core 2 Duo, 2.4GHz, with 800MHz FSB (2007).
I think it would be a small thing to do for a utility of this power.
Thanks, hoping at least one answer.
64-bit, running a macpro 1.1 on mountain lion (through chameleon) would like to try this.
I had a freak unintentional overclock to 3.6Ghz from 2.0 after the first run of ML… Geekbench through the roof. Never reproduced it…