When things go bad on a MacBook Pro
04
August
2008
I have been using Microsoft products for a long time but recently i decided to give Apple(Mac OS X) a try. Well things started off great and i have been close to converting to a full time Mac user, but as with Windows i have not yet experienced a crash on my Mac.
I also decided that 2gb of memory for my MacBook Pro was no what i needed to a upgraded to 4gb. When i received the memory i installed it in my MacBook Pro as instructed in the installation guide on apples website.
Then i booted and things got weird, well to make a long story short one of the memory modules was BAD so it caused my drive to corrupt some files and also OS X. Now i was stuck with a MacBook Pro that will not boot and i cannot fix or repair the hard drive with the utilities online or on the Mac repair disk.
After 2days of searching on the internet and trying a few things i finally got my system back but running on a Firewire drive, this allowed me to recover my files from my mac and start from scratch again.
So i now have my system back but with a bad taste in my mouth. What i mean by this is that when you install a bad memory module in a Windows system and boot then it goes nuts and you reboot after you removed the module and life is good again but not on a mac, so now i understand why Apple only runs on Apple hardware as it is so sensitive.
Well this leaves me back with a better feeling of Microsoft and it made me think that we all have bad things to say about Microsoft but it is just because we have not gone thru the pains with other systems.
So for the average user Windows is still the safer platform.
Well back to my Mac as I need to get VMWare Fusion going with Vista to work on the ASPPortal code.
This item was created by Lead Developer on Monday, August 04, 2008 and published on Monday, August 04, 2008