New Macbook Pro Checklist

[poke4christ]

So I've got my new 15" Macbook Pro 2.4 shipping in now. I've been hearing about problems with them, but I haven't kept up with any of the threads. What is a thorough checklist to go through upon receiving the laptop. I want to make sure I don't get a lemon.

[mad jew]

Just use it as you would normally use a laptop and problems will become apparent quite quickly if present. Congrats on the new Mac! :D

[AdeFowler]

I have to agree with mad jew, just use it normally. Too many people actively go searching for problems. Just enjoy your mac ;)

[poke4christ]

excellent point. I'll take it to heart. Oh, and thanks on the congrats. It's my first mac and I can't wait to get it in. Afterwards, I think I'm going to dual boot my old laptop to be a Ubuntu/windows machine. I think I'll just use windows when I need it. Otherwise, I'll keep the old machine running linux.

[John01021988]

Just enjoy ur mac! I have 3 weeks with my macbook and I havent used windows during this time (just when installed through parallels the first day)

[Illicit]

sorry for stealing your thread, but I really don't want to make a new one for this question :p
Suppose IF you find a problem, bent case, dead pixels, stuck keys, etc.
what's the fastest standard procedure to request a replacement? call them and ship it back and forth, or do you just bring it to the nearest apple store and request one there?

congrats on your first mac, poke4christ :)

[r1400sch]

^ I'm wondering about that too.
If you order a MBP from say, your college's store but the school store is far away from where you live, can you just take the MBP to the closest apple store if you have the yellow screen problem or stuck keys?

[Wolfpup]

I like running Memtest on a new system overnight (or for a few hours at least), which can at least show if the memory system is working well.

I've seen that there's a Memtest for OS X, though I don't know how it works (or if it works on Intel Macs), since the one for normal PCs boots from a disc, totally bypassing the OS, and I think the OS X one somehow ran from inside the OS?

Should return zero errors. If there are errors, it's usually the RAM itself, though I think it's possible it could be the memory controller.