Then if you combine that with there is no way to 'restore' a laptop to its original OS install if you've re-partitioned and overwritten the 'recovery partition' on the hard drive. Nobody bothers to send recovery CDs any more, that is $3.85 in plastic they can't (or won't) put into the box. So now if you install Linux you've made it effectively impossible for the vendor to even attempt to start from a 'known good OS' and determine suitability. It does kinda suck.
That said, I prefer Amazon's policy as well and as more folks move there NewEgg will either adapt or die.
[1] Evil doer activity (documented) - get some bad memory (generally for free from some scrap pile, 'buy' a laptop, take its good memory out, put dead memory in, 'return' the laptop. Sad really. All the engineering effort that goes into thwarting the petty schemes of evil people.
Just worth checking.
The problem you describe is not a matter of an 'improper config' wrecking a laptop due to the awful user-unfriendliness of Linux. It is a matter of you messing with something you didn't understand, jamming the machine in a bag to overheat, and then having to replace the battery.
There does not exist an operating system which is impervious to this kind of nonsense.
Linux distributions (keyword: distributions) have often shipped in a default configuration which can result in damage from overheating. There's no need to accuse the OP of "messing with something he doesn't understand."
Vendors often perform QA on hardware to ensure that it operates properly in conjunction with an operating system. When hardware is designed such that it requires particular operating system behavior to prevent damage then it is absolutely reasonable to require that operating system be used to maintain the warranty. Closing the lid of a laptop is completely normal behavior -- and it's a fact that many linux distributions ship with a configuration that will not properly suspend the device, leading to potential damage.
This is not a matter of "user unfriendliness." This is primarily a matter of hardware vendors limiting their testing to the behavior of certain operating systems (and thus limiting their warranty -- you can't warranty what you haven't tested; what isn't well-specified). I wouldn't be surprised if Apple refused to warranty a device which had Windows installed on it.
There's no need to get religious here. It's merely an issue of vendor support, and hardware which relies on particular OS behavior to operate safely.
So as it turns out, Linux may really be bad for your hardware. Still, there's no way I'm going to stick with Windows on my new notebook.
Annecdotally, heavy graphic card use on any laptop (yes even running windows) will cause a heat death in a shorter ammuont of time than normally expected.
Any rebuttal you might throw at this reality would make me to look at you more and more like this. :)
So why don't you just freaking avoid enabling that feature?
Is it Linux's responsibility to absolutely prevent you from shooting yourself in the foot after taking very special effort to research the best way to blow it off?
Question: does OS X fully support every possible bit of hardware which you can technically make to run with it, with every feature you want? Is it absolutely impossible to shoot yourself in the foot with OS X?
Wrong.
https://help.ubuntu.com/community/AsusZenbook#Suspend
>If this workaround not used, there have been reports that the laptop's memory controller setting may be screwed. After an incorrect suspend, if the corruption happens, many memory blocks starting with ~1G will be corrupt. Good way to see it is to use "memtest86+". The only way to fix controller setting is to open the case and plug off the battery. Please note that on this ultrabook the battery is not a user serviceable part and this could mean that by opening you can get your warranty void! If you start Windows or Linux with a corrupted controller, you will get system crashes or/and damaged file system. More info here: https://bugzilla.kernel.org/show_bug.cgi?id=42728 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/962798
I was only trying to show that the OS and Software can play a big role in the health of the hardware. Software bugs can cause hardware failure, and a notebook not going to sleep when the lid is closed is usually a bug unless it is specifically configured to do that.
Same distro, same config, and half the batch has a death wish, shutting down the fan in response to increased CPU temp.
Didn't we just have an article about how great Amazons UX is? Well, i guess this is the Newegg version of that, just inverted.
I certainly wouldn't expect, nor trust, Amazon to do this.
Haven't used a Macbook, though, so can't compare.
I do find it interesting that newegg isn't using a CD loaded testing suite anyways, using windows PE or a DOS based environment. (like Eurosoft's PC-Check software.)
There's also the fact that it should take about, ten to fifteen minutes just to slip the hard drive out, hook it to an imaging workstation, and image the default OS over to it. (My imaging station takes 5 - 10 minutes). To the best of my understanding it's pretty much assumed that when you send stuff in you are waiving your right to have the same data sent back anyways.
It was surprising my backpack didn't catch on fire.
For example, I had a battery become unusable because Linux often failed to sleep when the lid was closed because some dialog box was blocking. It would run in the bag with no ventilation when I didn't realize it until the battery drained and it would fail to shutdown until the hardware fail-safes took over and I realized my backpack was too hot to hold. Did this a few times and the last time, the battery wouldn't charge anymore. After getting a new battery I became very conscientious about whether it actually was asleep before I put it in the bag.
I have had this happen in Windows before as well, in one case it would wake up if I forgot to turn off my Bluetooth mouse when I put it away. Since it was already closed, there was no trigger to go back to sleep so it would run itself dead in the bag and eventually the plastic near a hot component melted. Turns out there is an option in the Windows device manager to tell it not to wake on Bluetooth that prevents this.
However a defect in the factory-installed operating system that causes failure is something you have to warranty. A defect in the user-installed operating system is not. However, I have no idea how they could trace the problem to the operating system. Not sure how they would ever know that Linux is installed. Any good Linux user would wipe the hard disk before returning a computer to the manufacturer for repair :)