- Joined
- Feb 18, 2007
- Messages
- 12
- Reaction score
- 1
- Points
- 3
- Your Mac's Specs
- iMac 24", 2.33GHz, 2GB, 7600GT/256MB, 500GB
I'm on my first ever Mac (iMac 24", 2.33Ghz, 2GB, 500GB, Nvidia 7600) and already some niggles are eating away at my initial euphoria. On a computer which I primarily bought for its much renowned stability, I experienced no less than 4 software crashes, all within the first 24 hours of booting the system for the first time, and all with software from Apple.
I'm not a troll and while this may seem like a bit of a rant, it's actually just a bit of frustration from a new kid on the block, so please bear with me.
First, when playing around with a very small test project in iMovie HD, the application quit on me unexpectedly. Fortunately, no data was lost but still, it came as some of an unpleasant surprise.
Next up was Aperture, which is the only application I installed on my virgin OS X configuration. While it was creating thumbnails in the background and I was browsing through some photos: boom.
The third one to go was a Dashboard widget of all things. I was trying if the sticky notes widget would resize its font when I typed more text than the note could hold. I did that by repeatedly pasting some boilerplate text in it and thar she went.
And the final crash was especially disheartening. I was copying some files over from my PC to the Mac using my wireless network. For some reason the connection was lost but the copy dialog didn't budge: it just stopped reporting progress. I tried to cancel it by clicking on the small x, but no response. I then tried to reboot OS X (old habits die hard) but it wouldn't let me because the Finder was still busy copying files (or so it thought). I then tried force quitting the Finder (remembering all the hype about being able to do that without affecting OS stability). I didn't get a Quit, but Relaunch option which seemed logical because the Finder is always active. The Finder did quit alright, only to relaunch in its same unresponsive state. It also took down the menu bar with it, so the Apple system menu was gone. Luckily, there were still some stray icons in the upper right hand corner and I managed to launch an application using Spotlight which restored the menu. I then tried to reboot the system using the Apple menu but... no response.
Even though Spotlight still worked and OS X didn't crash technically, it might as well have because for all intents and purposes, it's quite useless if one of its core components (the Finder) stops working and the system can no longer be shut down.
I didn't expect my PC to Mac transition to be all smooth sailing, and fully realize that no system is entirely flawless, but 4 crashes on a Mac that came out of the box just 24 hours before... man, that doesn't sit well with me...
Is this something I'm supposed to live with? Can anyone relate to my experiences, or is this actually as unusual as I would like it to be?
I'm not a troll and while this may seem like a bit of a rant, it's actually just a bit of frustration from a new kid on the block, so please bear with me.
First, when playing around with a very small test project in iMovie HD, the application quit on me unexpectedly. Fortunately, no data was lost but still, it came as some of an unpleasant surprise.
Next up was Aperture, which is the only application I installed on my virgin OS X configuration. While it was creating thumbnails in the background and I was browsing through some photos: boom.
The third one to go was a Dashboard widget of all things. I was trying if the sticky notes widget would resize its font when I typed more text than the note could hold. I did that by repeatedly pasting some boilerplate text in it and thar she went.
And the final crash was especially disheartening. I was copying some files over from my PC to the Mac using my wireless network. For some reason the connection was lost but the copy dialog didn't budge: it just stopped reporting progress. I tried to cancel it by clicking on the small x, but no response. I then tried to reboot OS X (old habits die hard) but it wouldn't let me because the Finder was still busy copying files (or so it thought). I then tried force quitting the Finder (remembering all the hype about being able to do that without affecting OS stability). I didn't get a Quit, but Relaunch option which seemed logical because the Finder is always active. The Finder did quit alright, only to relaunch in its same unresponsive state. It also took down the menu bar with it, so the Apple system menu was gone. Luckily, there were still some stray icons in the upper right hand corner and I managed to launch an application using Spotlight which restored the menu. I then tried to reboot the system using the Apple menu but... no response.
Even though Spotlight still worked and OS X didn't crash technically, it might as well have because for all intents and purposes, it's quite useless if one of its core components (the Finder) stops working and the system can no longer be shut down.
I didn't expect my PC to Mac transition to be all smooth sailing, and fully realize that no system is entirely flawless, but 4 crashes on a Mac that came out of the box just 24 hours before... man, that doesn't sit well with me...
Is this something I'm supposed to live with? Can anyone relate to my experiences, or is this actually as unusual as I would like it to be?