For the 5 grand, I expect better, but then I doubt MS Windows, Intel, & SolidWorks have more than a passing relationship. Given a choice, I'll stick with my Mac any day, because EVERYTHING JUST WORKS...and has done so very well for 3 years. (Vent over) So for some clues on what works and doesn't, I can offer a few things I see from the first couple days: 1. External FireWire Hard Drives: Partition & Format them in Windows XP, and the Macs will see the WinXP formatted drive in Mac OSX as a 'normal' hard drive. 2. Standby: Don't use it in Win XP or SolidWorks quits after coming out of Standby. 3. Hibernate: Wiley Gates made sure some of his apps would be OK on coming out of Hibernate, but SolidWorks, again, quits. 4. Battery Power & the Centrino Processor Cycling: Don't use it with SolidWorks. I understand that some people modify their BIOS to eliminate processor cycling. I'ld be interested in other users hints & tips on the M60. FWIW, the M60 @ 1.7ghz with a 7200 rpm HD & faster bus can save SolidWorks assemblies about 5-10 times faster than my old Inspiron 8000 @ 1 ghz. M60 rotations are about twice as fast as the I8000. Bo