Overheating MBP Core Duo

Folks,
I know that the original Core Duo MBP's like mine ran hot. I'm accustomed to that. My MBP typically idled at about 46*C to 56*C. I had a problem about 2 years ago where it would spike to 80*C+ & it was suggested to me that I disable Spotlight. I did so & thereafter the only time it ran in the upper 70's to low 80's was when I was doing heavy calculating, like ripping movies.
However, lately it has been climbing into the low 80's for no apparent reason. Whereas, in XP in runs in the 40's to 50's.
I updated to 10.6.3 in the lame hope that it might have some moderating effect, but no.
Can anyone offer an explanation? I'm sure that letting this machine operate at these temps for an extended period will do it no good.
Thanks for any help.

S.U.
Yes! I checked the ActMon & one app was taking up way too much CPU usage. I didn't recognize the acronym so I Googled it.
Turns out it was iAntivirus. Once I disabled it my CPU temp dropped immediately to the high 40's *C. 45*C at the moment.
So, I did a little research & it seems many others have had the same complaint. I uninstalled iAv, installed ClamXAv & all seems fine now.
Oh, and just as an aside...the MBP sits on an aluminum/plastic cooling pad with its own fans & I keep it (the MBP) spotless & dust free; outside and in.
Thanks for the help! Cool!!
Regards,
C64

Similar Messages

  • OS X Reinstall DVD rejected by MBP Core Duo

    I am attempting to reinstall Mac OS X on my 15.4" MBP Core Duo. When I install the 1st disk while the OS is up, the system will eject the DVD after about 1 minute. It does recognize the 2nd disk, but not the first disk. There are no blemishes on the disk, it has been used once before. I have noticed that the DVD player on my MBP will randomly not recognize movie DVD's, and eject them after they are put in. These movie DVD's are original/new out of the box, and work in any other system.
    Is there a firmware issue, or a known issue with the super dvd players in the 15.4" Mac Book Pro's?
    I apologize ahead of time if this is addressed elsewhere, I looked for a few hours and didnt find what I was looking for.

    Firstly, try resetting PRAM and NVRAM…
    http://docs.info.apple.com/article.html?artnum=2238
    … as doing this has at times ben known to resolve SuperDrive issues. Beyond that though, I'd try contacting AppleCare which may however be difficult from Afghanistan.

  • Random Shutdowns on a MBP Core Duo, Suggestions/Help would be great

    I've had two random shutdowns of my mac since purchasing it back in August. The first happened on January 11th, when it said it was at 11-12% power. The second happened about two weeks later, at 23% power. I've been looking around these forums and other pages, and haven't really found anything that has helped so far.
    Details of the first crash:
    Open apps- Firefox (5 windows, two had about 20+ tabs open, the rest were single page, and yes, I know it crashes often with that many), Camino (1 window with 5 tabs), and Word 2004, as well as Quicktime open to the iPhone stream.
    I had an USB key plugged in, to which I was saving my Word document.
    So I was working in Word while in front of the TV and during an interesting bit, didn't do anything for a minute. So, like the many times earlier, it slept the display to conserve power (in "Better Energy Savings" mode). I moved my finger on the trackpad to wake it back up, and it turned back on the backlighting, and then stopped. I thought it had just went back to sleep, but after a few key presses and a check of the light that usually pulsates when it's sleeping (plus the USB key , I found out that the computer had turned off. I let it sit for a while, and when I plugged it back into AC power and turned it on, with my USB key still plugged in, and although it booted to my desktop, the Finder never started (so no desktop icons for anything), unplugging the USB key fixed this and everything returned to normal. I then installed the only update I was missing, one for iChat, restarted, and continued working.
    In the second incident, I only had my browsers open, nothing external plugged in, and my displayed was dimmed to the third darkest level. When it was at about 23% power, it once again randomly shut down. This time, I attempted to turn it back on, and nothing happened. After plugging it into AC power, it turned on and once logged in showed a very low (2-6%) power, so I guess it was reporting the power incorrectly?
    Anyways, went back to look at the battery exchange on Apple's website. I had checked before when they started it, and was pretty sure mine wasn't covered, and a second check confirmed that. My Mac's serial is W8618091VWX, which isn't covered by the recall.
    So, I have a few questions:
    1. Is there a toll-free number I can phone Apple (Canada) at? The only number I've found seems to be only free for those who bought their computer in the last 90 days, which I'm no longer covered by, and haven't been for a while. Talking to someone at Apple would be good.
    2. Otherwise, if I took my computer to an Authorized Service Provider, would they be able to take a look at it and answer some questions? I bought my MBP at a London Drugs and they aren't service providers, so how much would it cost to do this?
    3. Is there a definite cause for these random shutdowns? It seems to vary among other people, so it would be helpful if I could try something to eliminate one of the causes.
    4. Does Tiger report battery levels pretty accurately? In the past when I reached 6% I got a warning and was able to plug it into AC power and had no problems.
    Thanks for any help you can provide.
    Macbook Pro 2.16 GHZ Core Duo, 15.4", 1GB RAM   Mac OS X (10.4.8)  

    I had this problem of RSD fixed for a while after having had the battery replaced by Apple, till yesterday, when the MBP suddenly experienced a shutdown during a meeting presentation, while it was connected to the AC power. At the first restart, as coming back from a stop-mode, for a while appeared a warning of low-battery level, with battery level indicator flashing red and showing the empty icon but with a 86% of charge level and a new shut-down definitely put the MBP out of service, no way to have it functioning again. Obviously, AC power was OK, no problem with the microphone or the projector ( I was at the podium of an international meeting) and a lucky precaution ( double save of the same presentation on a friend's twin MBP, that worked correctly) saved the job.
    Then, a couple of hour later, my MBP started up normally and everything works fine, with or without MAGsafe connected to AC power, almost up to now.
    I've read the post with a link to the procedure for resetting the power controller chip on the mainboard, I'll do it in a minute, hoping that this will help.
    Any further suggestion?
    ambabu, Italy

  • A "stock" way to get 802.11n on MBP Core Duo?

    Is there anyway to get something to upgrade my Core Duo MBP to 802.11n without using an external card or anything like that. I can handle working on the software side of things but not the hardware. Is there anyone that i can send it to to have them to the upgrade for me? Thanks a lot.

    what about a third party company, would any of them
    do it?
    Hi, I'm an old Navy retired electronics technician and have been working on Macs since 1986 and am in the same boat as you. I have a 15" MBP that I have already taken apart once to install a larger Hard Drive and Williams procedure doesn't look all that more difficult. I have the card on order from Powermax and I expect to install it by the end of this week. If it works out for me and testing shows it works consistantly and if you are willing to trust me with your "baby" for the time it takes to install it and ship it back I would be glad to do the same for your machine for a small fee. If you are interested, contact me at my email [email protected]
    MBP 15" Core Duo   Mac OS X (10.4.8)  

  • "Dongle and MBP Core Duo 2 - Dongle"

    Hello everybody,
    I just recently purchased a new MPB Core Duo 2 and upgraded to the newest version of Logic Pro.
    I find that my dongle usually does not get recognized when I plug it into the usb on the right-hand side of the mac however it gets recognized every time when I plug it into the usb port on the left hand side.
    Has anybody else experienced this? Also I have tried to plug into the usb on the right hand side...jump drives, hard-drives, etc..and they all get recognized right off the bat...so I don't think that the actual USB port is defective.
    Any ideas why this might be happening? I also tried updating the firmware on the usb key (dongle) and it said that the key is fine and does not require an update.
    Thanks for any advice.
    Cheers,
    Norm

    What is the source of the DVD? Retail? DVD from a different computer?
    Stedman

  • MBP Core Duo 2.16Ghz Display Problem

    After watching an hour of steve jobs and bill gates D5, my MBP display now doesn't display normally anymore. The display is discolored, the color is all whacked out. I don't know what happen, i ran the hardware test and it found nothing. I suspect that it's a video card problem due to overheating, but i put it on a desk with proper ventilation and it's not like this is the first time I used the MBP more than an hour. Please let me know what is going on, thanks.

    I had a problem like this once and a PRAM reset fixed it.
    http://docs.info.apple.com/article.html?artnum=2238

  • MBP Core Duo 17" 2.16Ghz  - Why is 2GB the limit?  4GB?

    All the past and future Mac Notebooks allowed memory upgrades when the chips either became available or affordable. The Apple store advisor (when I purchased last year) said that like older Mac Notebooks they assumed that the MBP memory would be upgradeable later. I know, why did I believe the store clerk? I am a Photographer and I can't afford a notebook every year and I need more memory for PS3 and LR now. Is there any hope a firmware update will fix this or is this another penalty for being an early Apple adopter. Is the limit real or a way to artificially differentiate models?

    Sorry. No hope. It's a limitation of the Intel Chipset and applies to all machines based on these chips.
    Your best bet is to sell and buy a new one.
    Best of luck.

  • MBP CORE DUO 1.83GHZ SLOWING DOWN

    Hello everybody I have noticed that my MBP with 1.5 Gig of Ram is slowing down: I'm geting a lot of spinning wheels, and I'm experiencing an annoying delay of 1 sec when I click to open a folder and the actual opening...
    Any ideas?
    Thanks.

    Perhaps you could first try repairing permissions and restarting (if you have not tried it yet).
    If that does not fix, then you could look at other options.
    Here is how you repair permissions:
    http://docs.info.apple.com/article.html?artnum=152059

  • MBP Core Duo Checkerboard display lock-up

    I am having a frequent issue with my MBP that I just received in January.
    Right out of the box, the screen froze, and I had to force the machine off.
    Now, I am getting a checkerboard display or complete display lock with any of these scenarios:
    1. Cold-boot the MBP, locks up at the login screen. Need to restart again.
    2. Awake the MBP after being asleep for 20 minutes or more.
    My dealings with customer support have been frustrating. Their latest suggestion is for me to wipe the hard drive and reinstall the O/S. This seems like a "using ashotgun to swat a fly" approach.
    I don't want to waste my time in reloading third-party apps, so before I try this, has anyone tried this approach and have it resolve their display issues?
    From what I'm reading on the Net, the logic board is the suspect, but the support folks won't listen.
    Help!

    I have been having the same problem with my macbook for months now, i have tried everything.
    I've called customer care....who frankly couldn't care less, so am taking it into the apple store today to have a apparent genius have a look.
    To be honest, i wish i had just bought a normal windows based laptop as i dont need all this hassle.

  • Migration MBP Core Duo - MBP Core 2 Duo

    Hi everyone,
    I need to move everything from an older MBP CD (32 Bit) to a newer MBP C2D (64 Bit). Both Macs run 10.6.3 and both share the same model of HD (Samsung 250 GB 7.200). I know that the kernel runs in 32 Bit anyway on both Macs per default and that’s fine.
    I don’t need anything from the newer MBPs HD, so it can be deleted. What I’d like to know is what is the best way to migrate?
    • Exchange HDs
    • Use CCC to clone old MBP to new MBP
    • Install fresh system on new MBP and use Migration Assistant
    The reason I’m asking: I’m not sure if all binaries are installed both as 32 and 64 Bit when installed on a 32 Bit Mac. So I want to make sure that the new Mac won’t run anything unneccesarily in 32 Bit when it could use 64 Bit or has a degraded performance of any other kind.
    I’m pretty sure that all 3 solutions are OK and that all binaries usually are for both architectures, but I wanted to be absolutely sure before I need to do it again.
    Any recommendations are welcome!
    Björn

    Hi Björn;
    My suggestion is to connect the two MBP together with firewire cable and run Setup Assistant on first starting the new MBP. It will ask you what to migrate. It will migrate things correctly for you.
    Allan

  • MBP 1.83 Core Duo

    I currently have the MBP Core Duo 1.83.
    Question I have... Does anyone know if I am stuck with this processor or can I upgrade if purchase the Core 2 Duo Chip?
    Also is getting an external HD the best way to upgrade my capacity and speed?

    As everyone else has said, and as you can see in the following pic, the CPU is not like ones found in PC desktops. Laptops, because of their size and design, have very limited upgrade capabilities.
    http://www.ifixit.com/Guide/85/images_large/44.jpg
    If it makes you feel any better, the difference between a 1.83 GHZ and a 2.0 GHZ is nigh unnoticeable. More RAM and a 7200rpm drive will give you noticeable speed increases. Conversely, a handful of MHZ won't do much at all. Don't get caught up in the 2001 clock speed hype. A computer is much more than it's clock speed.
    Look at it this way. You have 3 dams, each lets through some water. The first lets through 100 litres of water a minute, the 2nd, 200 litres, the 3rd, 300 litres. If you are sitting at the first dam, and want more water, would it help you to increase the 2nd dam's size to 500 litres? Of course not. If you were sitting at the 2nd dam, you would see more water if you increased the size of the first dam. If you were at the 3rd, then increasing the size of one of the first two, or both, would help get more water to you.
    Basically it's the same thing with a CPU (obviously more complex). But, the analogy still holds. Most things slow down even before they hit the CPU, so it wouldn't matter making them any faster. There are components (such as hard drives) that are extremely far behind any other component.
    Remember, your PC is only as fast as its slowest component. Be it that some things you do, do sometimes circumvent that component, irregardless, it will still ultimately affect day to day use.
    Be aware that external hard drives are either USB 2.0 or firewire (400 or 800; the latter only supported in the 17" MBP or the new C2D 15" MBP).
    The data transfer rate of USB 2.0 is 60 MB/s. Firewire400 is 50 MB/s, while Firewire800 is 100 MB/s. SATA is 300 MB/s. As you can see, an internal hard drive is a much better choice as most hard drives advertise a transfer rate of around 150 MB/s.
    Here is a rundown on the latest Toshiba 200 GB, 4200rpm drive:
    http://www.techgage.com/article/toshiba200gb_4200rpm_25_harddrive

  • MBP 2.16 core duo networking slow

    Hi
    My 2.16 MBP Core duo seems to be having networking speed issues. When I first got it in September 2006, I was seeing bandwidth speeds on my home wireless network comparable to a wired computer on the same router (Apple Extreme base station, comcast cable modem), 2 to 2.5 Mbs. However now I'm only getting 600-700 Kbs on the MBP, yet the older (1 Ghz G4) iMac is still getting the higher rate. Thinking it was a wireless problem, I turned off the Airport card and connected the MBP directly to the cable modem. Unfortunately, I still get a bandwidth connection about one third that of the old iMac.
    Any troubleshooting ideas? Thanks!
    MacBook Pro 2.16 core duo   Mac OS X (10.4.8)  

    This problem has been on several threads. I thought the new release for the Airport update would fix it. To date I have:
    Retrograded back to 10.4.7. This fixed the speed problem.
    Today I reloaded 10.4.8, upgraded with the past 2 months of security fixes and the new Airport update. The speed problem has returned - about 1/10 the speed as before - really crawls.
    I still believe it is an issue with the original dual core (not the 2's) and 10.4.8. I will now go through the process of reloading the original OSX from the install disk, then run the 10.4.7 combo update. Thankfully I downloaded that 143 MB chunk before I went back to 10.4.8. Good luck, but I think there is a very deep problem with .8 that hasn't been addressed for us early intel adopters.

  • Fans running too fast on MBP Core II Duo

    Hi there,
    I'm starting a new post 'cause the older one was getting unfruitful. Let me wrap up quickly. I've got both a MBP Core Duo and a MBP Core II Duo. I had notice that the fans on my MBP Core II Duo were very noisy compared to the MBP Core Duo. So I ran smcFanControl (NO I HAVEN'T CHANGED THE SETTINGS AND NO smcFanControl ISN'T BAD FOR YOUR COMPUTER), I just used it for MONITORING PURPOSES. Ok.
    I've capture both results in movies so you can see the differences. I've used a cloned system and compiled some code to give the cpu some meat. Here are some behaviors I've noticed:
    http://web.mac.com/michaf/iWeb/MacBook%20Pro%20Fans/MacBook%20Pro%20Fans.html
    (Just run both movies at the same time)
    1) The MBP Core II Duo runs at a minimum of 2000 rpm vs 1000 for the MBP Core Duo
    2) The MBO Core II Duo shoots very quickly and hangs it's fans much higher.
    3) After a while the MBP Core II Duo has a temp of around 68 with fans running at 4500! The Core Duo instead at a similar temp is down to 2300!
    I'm recording with my machines and it's barely usable with the fans.
    Has anyone noticed the same thing or is it my machine?
    Micha

    The movies in your link don't appear to be working so can't comment on those.
    Your post confirms what I suspect is true about C2D temps compared to CD temps, which is that the C2D is fundamentally no cooler (possibly hotter) than the CD, but Apple have doubled the fan speed in the C2D to make the C2D run cooler.
    Seems to me that Apple bent over backwards to make the CD quiet, and this resulted in them running too hot, and with the C2D they have swung the other way.
    I am using Fan Control 1.1 on my CD to steer a middle course. I have left it with 1000 rpm min but set it to start ramping the fan speed earlier and more steeply as temp rises. So most of the time it is quiet, and high temps which can be reached with the Apple settings are avoided.
    Doesn't help your C2D problem much except to suggest that you use Fan Control 1.1 to devise settings to suit your purposes. I suggest you have Hardware Monitor on continuously (hidden) so that you see what has happened to the temp over typical working sessions using different settings in Fan Control. When you have found what works you don't need to keep Hardware Monitor active.
    C2D can't need 2000 rpm the whole time!
    Mike

  • Java Development issue/differences between Core Duo and Core 2 Duo (??)

    Hi Everyone,
    I am a Java developer that uses my 17" MBP Core Duo for all of my development. Lately, I've been trying to use both the Glassfish Application Server V2 (from Sun) and Maven 2.09 from the Apache project. I have configured identical scenarios on my MBP Core Duo and on a 15" MBP Core 2 Duo.
    The scenario involves compiling and running some webservices (at least on the Core 2 Duo) in a local development environment. Both machines use the default JDK 1.5.0_13 installed on the machine.
    On the 17" Core Duo, issuing a "mvn install" command produces the following error:
    [INFO] Compiling 1 source file to /Users/john/downloads/soabook-code-20070504/chap07/endpoint-provider/modules/en dpoint/target/classes
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Fatal error compiling
    Embedded error: Prohibited package name: java.lang
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 12 seconds
    [INFO] Finished at: Fri Sep 05 07:09:06 CDT 2008
    [INFO] Final Memory: 9M/17M
    [INFO] ------------------------------------------------------------------------
    Running Maven with the "-e" switch turned on produces the following stacktrace:
    org.apache.maven.lifecycle.LifecycleExecutionException: Fatal error compiling
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecyc leExecutor.java:564)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(De faultLifecycleExecutor.java:480)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycl eExecutor.java:459)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailure s(DefaultLifecycleExecutor.java:311)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Default LifecycleExecutor.java:278)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExe cutor.java:143)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
    at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java: 498)
    at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.j ava:443)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecyc leExecutor.java:539)
    ... 16 more
    Caused by: java.lang.SecurityException: Prohibited package name: java.lang
    at java.lang.ClassLoader.preDefineClass(ClassLoader.java:534)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:669)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassL oader.java:56)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:675)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassL oader.java:56)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler .java:398)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141 )
    at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java: 493)
    However, the exact same software setup on the Core 2 Duo produces this result (which I would expect on the Core Duo):
    [INFO] Installing /Users/john/Downloads/soabook-code-20070504/chap07/endpoint-provider/pom.xml to /Users/mjhart/.m2/repository/soabook/chap07-endpoint-provider/1.0/chap07-endpoi nt-provider-1.0.pom
    [INFO]
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO] ------------------------------------------------------------------------
    [INFO] CHAP07-ENDPOINT-PROVIDER-WSDL2JAVA .................... SUCCESS [1:35.885s]
    [INFO] CHAP07-ENDPOINT-PROVIDER-ENDPOINT ..................... SUCCESS [7.221s]
    [INFO] CHAP07-ENDPOINT-PROVIDER-CLIENT ....................... SUCCESS [16.525s]
    [INFO] CHAP07-ENDPOINT-PROVIDER .............................. SUCCESS [1.597s]
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESSFUL
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 2 minutes 1 second
    [INFO] Finished at: Fri Sep 05 07:07:23 CDT 2008
    [INFO] Final Memory: 16M/30M
    [INFO] ------------------------------------------------------------------------
    I have installed the same software versions and have the same configuration on a Windows desktop running XP SP2 and get the same successful result.
    Is this an issue between the Core Duo and Core 2 Duo? I can't see that it is since I don't believe the hardware influences the software to that degree. However, I am at a loss for what is causing the issue and the Apache Maven list insists that there are developers that are using Maven successfully on OS X.
    I really need to get past this issue, but I am at a loss. Please help.
    Thanks,
    John

    Have you repaired permissions? (/Applications/Utilities/Disk Utility.app)
    Are you sure you're using JDK 5? (Applications/Utilities/Java/Java Preferences.app or output of $ javac -version)
    --greg

  • MacBook Pro Core 2 Duo vs. MacBook Pro Core Duo

    I currently have a MacBook Pro 2.0Ghz Intel Core Duo. Is it worth it to upgrade to the most recent MacBook Pro Core 2 Duo? What will I gain by spending the money? Does the battery get as hot on the Core 2 Duo as it does on the Core Duo or was that issue resolved?
    Any insight and/or advice would be most appreciated.
    Thanks!

    I'm sitting here making a list of the helpful Mac software to download for my new 2.4 LED MBP Core 2 Duo (2 GB memory) with the Santa Rosa chipset, and looking through the Applications folder of my 1.83 MBP Core Duo (2 GB memory).
    I've actually been doing side-by-side comparisons throughout the day, and here are my admittedly subjective impressions. Please understand that I'm not doing benchmarking---you will soon find lots of places giving you those numbers, and they don't mean much to me anyway. I use my computers in my job and they are tools, albeit fascinating, but a tool nonetheless. My impressions are just that--what does it "feel" like to me. So, if you want benchmarks with numbers, I apologize.
    1. Everyday work-type use (Word, Excel, PowerPoint, Safari, e-mail): About equal in terms of speed and ability to manipulate large Word, Excel, and PowerPoint documents. The new MBP "feels" slightly faster but not that "wow, this is fast" that I experienced when going from my old Dell laptop to the MBP Core Duo. What I have experienced is a new appreciation for my old Core Duo--it has no trouble keeping up with the new one.
    2. Video and photo editing: Again, the new MBP feels slightly faster, and timing the rendering of a short video clip was faster on the new one compared with the old one, but not by much. In fact not enough of a difference to retire the old one for less demanding tasks---it will remain one of my main computers.
    3. Heat: Sometimes it feels like my old MBP could cook eggs on it after doing some video editing or after a long DVD session. The new one seems to run a lot cooler---a lot cooler, although I haven't had a real chance to stress it, but comparing the same tasks side-by-side for transferring and running through my photo collection, the difference in heat was very noticeable. The old one was hot, and the new one actually felt cool to the touch (a little warm, but compared to my old one, it felt cool). I suspect I will continue to see that the new one runs a lot cooler.
    4. Battery: In running the battery down to empty today, I got 4 hours and 40 minutes on the new one and 3 hours 10 minutes on the old one---quite a difference. I expect more once I calibrate the battery on the new one. I should say that when I run on battery, I shut down Bluetooth and Airport if I don't need them in order to save on power.
    I'll do some more comparing in the next few days, just to see if there are major differences. Right now, I like the LED screen but it looks the same as my old one---maybe I just can't tell the difference.
    All in all, the new one is fast and cool with a longer battery life, whereas the old one is fast and hot with a shorter battery life.
    I would recommend the new MBP to anyone considering a new computer. Would I recommend that people with the old Core Duo upgrade? Not really---the old one really holds its own against the new MBP--not that much difference in speed. I don't think the difference in operating temp and longer battery life is that big a deal nor enough to justify an upgrade yet. I did it because I wanted to, not because I thought I needed to. And as my day has proved to me, the speed difference perceptually is pretty slight--they are both fast and a pleasure to work on.
    I have a new appreciation for my old workhorse, the 1.83 MBP Core Duo--it's still a great computer. I almost gave it to my wife, but not after today.

Maybe you are looking for