He already gave you one. To make sure the Mac is in good working order before you add more to it. I had memory waiting when my Mac arrived, but I fired it up first to make sure it was A-OK before dropping the new memory in.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Just got my Imac 2.8 from Fedex....Nightmare ensued!!
- Thread starter ba07
- Start date
- Sort by reaction score
He already gave you one. To make sure the Mac is in good working order before you add more to it. I had memory waiting when my Mac arrived, but I fired it up first to make sure it was A-OK before dropping the new memory in.
Don't you undestand that the problem would have happened regardless if i "checked to see if it was A-OK" first or not? The ram was bad, it doesn't care if you start it before or after the setup.
Yes, I see that. But you wouldn't have posted a long rant about how your Mac didn't work "out of the box", because that would not have been the case.
I'm sorry to hear about your troubles. I plan to do the same (in 2 more weeks), order 2.8 with 1gb and put in 2gb sticks. Look on the bright side, you have helped me make sure I don't make the same mistake. I guess i won't be buying owc ram and I'll boot it up before tinkering with it.
I hope you get ur memory in there soon and back in action. good luck.
I hope you get ur memory in there soon and back in action. good luck.
Oh Oh I can!!!
Prior to starting the machine you spend ohhh lets say 20 mins installing your new ram.
You read the instructions - 5m
You get everything you need ready - 5m
You position the iMac and proceed to remove the old ram - 10m
You start to install the new ram on a system that you have never done it before, assume things will go one way when in fact they do not and you have trouble and continue to keep trying and finally get it installed (or so you thought - 30m (I would go sarcastic and say "Priceless" but I'm trying to prove a point and this isn't a Mastercard moment)
You boot up, things do NOT go well, glitches, bad boots, etc. Now what do you do? Start from square one removing the memory and assuming your an idiot (which I do) you think the whole computer is bad when in fact the memory you installed may be bad. You then proceed to disect the memory and reinstall the old stuff and then what? You take the Mac back thinking it's bad, or you may turn it on and go "hmm now why does it work now?"
Bottom line, COMMON SENSE would say, make sure the machine is good, it boots up, all is hunky dorey and then shutdown and proceed with the upgrade. Otherwise you may either be wasting time OR worse case scenario damage the Mac and no matter what you do it won't work again. Patience is a virtue and I'm not exactly the most patient person but in the computer realm, it really pays off. Make sure it's working first, make sure it's to your satisfaction. Then upgrade.
Bah now I'm wasting my time. This is an id 10 t moment.
Well, because then you'll know if the machine as delivered is healthy and in full working order. That's despite the fact that the probability of receiving a defective unit is quite low.
I make it a policy of mine to ensure all components of my computer are in full working order when I receive it, regardless of whether or not I plan to use everything. For example, my MBP included a remote, but I haven't used it in months. However, I made sure to use it when I first received my computer just to make sure it works in the rare event I need to use it in the future.
Now let's assume for a moment that your computer works for a few years with the OWC RAM installed, but after a few years, the RAM fails. Had you checked the computer as delivered, then you would have known that you have a spare set of good RAM modules that can be used while you wait for replacement modules. And if in the rare case the Apple-supplied RAM was defective upon receipt, then you would have already received replacements. If you never checked them, and they turned out to be faulty after your warranty expired, then you'd be out a set of good RAM modules -- something that was completely avoidable.
This isn't a hard concept to grasp. It's always a good idea to ensure everything functions correctly immediate after purchase.
I had NO problems installing my OWC ram, so don't take this one incident out on OWC.
Well, it really is just common sense. If you do a quick test of the iMac without the OWC RAM installed, and (for example) the iMac doesn't boot up, you'll know that it's an iMac problem and not an OWC RAM problem.
When I got my new iMac, I first powered on and checked for dead pixels, general operations, etc. I then powered off, installed my OWC RAM, and re-booted. Very simple.
Hoped...
This is like beating up on the convenience store clerk because he failed to sell you the winning lottery ticket you hoped for.
Yep, it is preinstalled for machines made after a certain date -- but there is a warehouse running in FIFO mode 3rd party stores, and waiting for new one from China to replace floor stock. So the only way to be sure of getting Leopard preinstalled is a custom ordered machine.
Hoped...
This is like beating up on the convenience store clerk because he failed to sell you the winning lottery ticket you hoped for.
Yep, it is preinstalled for machines made after a certain date -- but there is a warehouse running in FIFO mode 3rd party stores, and waiting for new one from China to replace floor stock. So the only way to be sure of getting Leopard preinstalled is a custom ordered machine.
Funny thing is, he got what they told him he'll get. WIth or WITHOUT it preinstalled. He even confirmed what several reps told him it may or may not come pre-installed.
Doublecheck your PO and check if the "installed" OS is Tiger or Leopard. I priced a machine last week and it had OS X TIGER as the OS down in the details of it.
Just do this guy a favor, let him be, he obviously isn't going to be happy one way or another. I for one would be happy if say I bought a Dell and got XP Pro AND Vista, 2 OS's for the price of one. Wow, yah I'd be pretty pissed about it. Dammit, I only paid for one, I should only GET one. Damn Apple for sending me 2, one stable one almost stable.
I know this isn't gonna make things easier. But do you know the pain to changing something even as easy as software on the product line. The ECO's you gotta do and signatures you need. The process is not smooth because it involves two companies and their mangement okaying agreement and costs to switching it over, the servers with the image on it, and so forth. Yes, it's good to plan, but if you already have a huge stock of hard drives with tiger image on it, you will not want to reimage them. That is an extra cost, and i doubt you want that extra cost to be passed onto you.
Please be patient with how production is run, you'll know how much of a pain it is when you work on the line, manage a line, or is an engineer that has a product on the production line.
My point is that...things take time to change, don't expect it to switch over quick, and there are bound to be issues when switching over as well.
Please be patient with how production is run, you'll know how much of a pain it is when you work on the line, manage a line, or is an engineer that has a product on the production line.
My point is that...things take time to change, don't expect it to switch over quick, and there are bound to be issues when switching over as well.
same here. i was a bit apprehensive about installing the RAM chips myself, but i was shocked at how easy it was. unscrew the bottom plate. take the old memory out. slide the new memory in. screw the plate back on. literally 5 minutes start to finish and i was back up and running.
I built my own PCs for years before buying my iMac a few weeks ago. First of all, getting faulty sticks of RAM is far from uncommon, and in the PC world you even need to make sure your RAM plays nicely with your particular motherboard (or vice versa, depending on which you'd rather return).
In any case, when I first built something I'd try to make debugging as simple as possible. Leave as much extraneous crap out as possible until everything is running smoothly. Then, as you add stuff it's easier to tell where problems start.
That's why I think it defies common sense to install new RAM in a pre-built machine like the iMac before you even power it on. At least power it on first, get through setup and make sure everything is OK before modifying what you've already got. At least then you don't risk corrupting something during setup or anything like that.
Still, the tone of the entire first post just rubbed me the wrong way. You happened to get some faulty RAM so suddenly OWC is the devil. Yeah, ok, whatever, tons of us on here have had no issues with anything we've bought from them, so to each his own.
Finally, as someone who's built a ton PCs back in the Windows world, both for himself and for other people (whether they choose to use Windows or Linux), I can tell you this experience is far from a "nightmare" compared to what can happen on a self-build PC - of course, that's part of the fun for dorks like us that do that sort of thing.
In any case, when I first built something I'd try to make debugging as simple as possible. Leave as much extraneous crap out as possible until everything is running smoothly. Then, as you add stuff it's easier to tell where problems start.
That's why I think it defies common sense to install new RAM in a pre-built machine like the iMac before you even power it on. At least power it on first, get through setup and make sure everything is OK before modifying what you've already got. At least then you don't risk corrupting something during setup or anything like that.
Still, the tone of the entire first post just rubbed me the wrong way. You happened to get some faulty RAM so suddenly OWC is the devil. Yeah, ok, whatever, tons of us on here have had no issues with anything we've bought from them, so to each his own.
Finally, as someone who's built a ton PCs back in the Windows world, both for himself and for other people (whether they choose to use Windows or Linux), I can tell you this experience is far from a "nightmare" compared to what can happen on a self-build PC - of course, that's part of the fun for dorks like us that do that sort of thing.
First off I never said that OWC is the devil. If I have a problem with my OWC ram, don't you think that people should know about it? Would you rather I would have kept my mouth shut and let other people think that OWC was always perfect? Really I'm trying to provide potential buyers with a different angle of the whole installling your own ram situation. I thought my first post was a little dramatic with the nightmare comment, but that's how it felt 3 am after getting a brand new computer I worked so hard to get.
Secondly, what's the difference between what I did and building your own white box by installing ram on a motherboard, connecting the HD to the motherboard, attaching a power supply, powering it on, then loading the OS? You put new ram in there...sooo...I just don't get where you guy's are making up this magical "its common sense to not install ram before you boot it up before the first time". Really my point in my initial post was to tell a story. The problem with the ram would have happened regardless of which order i put it in.
Lastly,
I don't see how I could have rubbed you the wrong way unless you work in a manufacturing plant for OWC. Can't us consumers just defend or acknowledge each others problems instead of defending the corporations all the time?
When I got my iMac, I let it run for several hours to make sure it worked in the stock configuration. After pulling my 1GB stick, I compared the pin configuration and size between the new sticks and the old one to make sure the new ones would fit. Next I installed them. I certainly would not have forced them in for fear of damaging the slots.
And I don't see the hassle with installing Leopard for someone that builds their own PC's.
And I don't see the hassle with installing Leopard for someone that builds their own PC's.
Let it go.
In 40 posts you've acquired very little support for your problem. Why do you think that is?
You are going to defend your OP to the death. It's becoming clearer now that your intent was to stir up an argument and that's what this thread has become.
Let it go.
In 40 posts you've acquired very little support for your problem. Why do you think that is?
You are going to defend your OP to the death. It's becoming clearer now that your intent was to stir up an argument and that's what this thread has become.
Let it go.
Someone else beat me by a post...
Putting everything else said aside, from someone who has built their own PCs in the past - you should know better than most how much easier it is to install Leopard.
I can't think of a single PC I've owned, fixed, or even used that is completely up and running with ONE disc and less than 3 minutes of my attention. This goes for both custom builds, and COTS PC systems. No separate video, sound, wifi, and printer drivers to load from discs or download. No bios settings to correct, jumpers to switch, voltages to set... I think you see the point.
As for the ram fit issue, yes it stinks, I can understand why you are miffed over that. But you've NEVER encountered a form/fit issue on a PC before? Especially with a discount vendor?
I do sincerely hope the rest of your Apple experience is positive, I know since my born-again switch almost 2 years ago, I have no desire, or need to go back. Though I still use Bootcamp and Parallels.
Dealing with Windows was akin to a 3 year old child. It asked dumb questions, continuously stated the obvious, and was extremely vulnerable to the outside world. Not to mention, both seem to $h!t themselves on a semi-regular basis.
"Hey! Hey!.... You just plugged in a mouse! I found a mouse!... And, you just plugged one in.
Do you want to use this mouse as an input device?"
The difference is with a DIY PC, the builder has assumed all the risks of the overall computer build, and with the iMac you have the luxury of Apple carrying those risks for you. When you buy a product where some one else has contractually agreed to carry that responsibility, it makes sense to fire up what they delivered, as they delivered it, to hold them accountable for what they agreed to. You must agree that if the first thing you do is crank in a bunch of 3rd party products, and the iMac fails to work when you turn it on, when you call Apple, the first thing they are going to do is request that you restore it to original factory equipment? No? Doesn't that fact alone make this pretty obvious? Or are you going to claim that Apple should be responsible for troubleshooting 3rd party upgrades?
I too had 4 GB RAM waiting for my 24" iMac when it arrived last Monday, and I ran it for a couple of hours stock before putting in the RAM. Common sense. It was OWC RAM and went in perfectly.
I keep looking at these posts
First, let me say that I am sorry for your "nightmare." Yet, I don't see what happened to you in the scheme of things to be all that terrible. Second, I have always tested booted a new machine before a ram upgrade, makes troubleshooting a lot easier.
First, let me say that I am sorry for your "nightmare." Yet, I don't see what happened to you in the scheme of things to be all that terrible. Second, I have always tested booted a new machine before a ram upgrade, makes troubleshooting a lot easier.
You like to EXAGGERATE!!! We get it
You're failing your English class. We get it.
You're new RAM doesn't fit very well when it's upside down and backwards. We get it
You've taken apart a PC and put it back together in Information Technologies 101. We get it
You don't understand anything about the computer industry or business logistics. We get it.
You're mad as hell and expected everyone to join in your pitchforks and torches quest to OWC's doors. We get it
You can't take constructive criticism. We get it.
You have to look up "common sense" in the dictionary. We'll wait.
ba07
Join Date: 11-01-2007
You've had quite a busy day.
You're failing your English class. We get it.
You're new RAM doesn't fit very well when it's upside down and backwards. We get it
You've taken apart a PC and put it back together in Information Technologies 101. We get it
You don't understand anything about the computer industry or business logistics. We get it.
You're mad as hell and expected everyone to join in your pitchforks and torches quest to OWC's doors. We get it
You can't take constructive criticism. We get it.
You have to look up "common sense" in the dictionary. We'll wait.
ba07
Join Date: 11-01-2007
You've had quite a busy day.
You expect the minimum wage workers who put the machines in the shipping boxes to load the new OS?
As any real techie knows, you never introduce more variables into a problem. So first boot up out of the box and make sure the machine is working.. Then install the RAM..
Tell me this.. If the OWC RAM fit perfectly, and the Mac started up crashing.. Who is the culprit? The Mac? The RAM? The drop in Leopard not installed? Come on.. Standard troubleshooting... Its like buying a car.. Before even starting it up, you add your own fuel.. When you try to start it and it doesn't start, who do you blame?
From the drive issue, I ordered my 24" 2.8Ghz.. I don't EXPECT it to have Leopard on it. If you know anything about a typical manufacturing process, these drives are imaged independently from the machines. (sorry to burst your bubble if you thought someone actually installed the OS manually after the machine is assembled).
The drives are imaged in mass quantities. If there's 10,000 500GB drives with the Tiger image still in the China factory, those are 10,000 iMacs that will ship with Tiger.. Once that stock is depleted, thats when Leopard would be imaged.. I would say the factories are probably stamping thousands of images as we speak.. Also, if you just look at basic accounting.. It's a matter of FIFO (or if any of you have programmed in Assembly)