Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Linux DESTROYS Computer Hardware
1,867 views
Skip to first unread message
anon...@online.com
Feb 19, 2013, 3:51:09 AM2/19/13
to
I dont like Microsoft operating systems and wanted to try something
different. The computer had a working installation of Windows, which
had been running well despite being from MS. Rather than delete it, I
just changed to another hard drive. I installed Linux. The
installation process was very painful. Getting it to cooperate with the
hardware was worse, and of course there is no real support. I finally
got it halfway working. At that point, I found it was hard to learn,
harder to get used to, and hardest to do anything useful since none of
the programs were familiar.
Two days later the computer stopped working entirely and would not even
boot. I spent hours fighting with it, tried to reinstall linux and it
simply would not work. I removed the hard drive that linux was on,
plugged back in my Windows hard drive, and could not make the computer
boot up. I finally took it to a computer repair place, and was told the
CPU was dead. Cost to replace was more than another computer.
Hundreds of dollars later, I had another computer, with more power than
before. Once again, I removed the hard drive, and installed that same
spare harddrive with linux on it, only to discover that hard drive was
permanently damaged. So, I purchased another harddrive, installed it,
and installed another distro of linux that was listed to be one of the
best ones. A week of fighting with installing it, and trying to make it
work, I finally had a semi-working computer. Another week of struggling
with trying to learn and use Linux, I was ready to give up on it and put
the original Windows hard drive back. The next day I removed the linux
drive and put back the Windows drive, and found the computer would not
boot.
Once again, I took it to the repair shop and was told the CPU was
damaged, and there was damage to the RAM too. Total cost was more than
I paid for the computer. I also took along the linux harddrive, and was
told that the drive had permanent damage (a brand new drive). The
repairman asked me what I was doing with these computers. As soon as I
mentioned the word "Linux", he told me that's my problem. He said Linux
destroys computer hardware, and said he wont even allow it in his shop.
He said that simply installing a self booting Linux CD can wreck a
computer in minutes. mostly destroying the CPU and drives. This is
caused because Linux sends the wrong voltages to components and burns up
the CPU and other chips. It also plays havoc with harddrives, and
causes them to lose their ability to read and write data.
So, here I sit with 2 ruined computers, 2 dead harddrives, and around
$1200 worth of damages and repair bills. (Not including many hours of
wasted time). Since Linux is made by a bunch of computer geeks and
idiots with no real business address, there is no one to sue. Both my
computer repairman and lawyer said it's worthless to even try a lawsuit.
It's just one of those hard lessons to learn in life.
All I can do is warn others, to avoid Linux like a deadly disease. Dont
even try it, unless you want to intentionally destroy your computer.
From now on, I'll just stick with Microsoft, even if their operating
systems are bloated. At least they dont destroy computers, and they
operate from an actual business that exists in brick and mortar, not to
mention having actual online and phone support.
different. The computer had a working installation of Windows, which
had been running well despite being from MS. Rather than delete it, I
just changed to another hard drive. I installed Linux. The
installation process was very painful. Getting it to cooperate with the
hardware was worse, and of course there is no real support. I finally
got it halfway working. At that point, I found it was hard to learn,
harder to get used to, and hardest to do anything useful since none of
the programs were familiar.
Two days later the computer stopped working entirely and would not even
boot. I spent hours fighting with it, tried to reinstall linux and it
simply would not work. I removed the hard drive that linux was on,
plugged back in my Windows hard drive, and could not make the computer
boot up. I finally took it to a computer repair place, and was told the
CPU was dead. Cost to replace was more than another computer.
Hundreds of dollars later, I had another computer, with more power than
before. Once again, I removed the hard drive, and installed that same
spare harddrive with linux on it, only to discover that hard drive was
permanently damaged. So, I purchased another harddrive, installed it,
and installed another distro of linux that was listed to be one of the
best ones. A week of fighting with installing it, and trying to make it
work, I finally had a semi-working computer. Another week of struggling
with trying to learn and use Linux, I was ready to give up on it and put
the original Windows hard drive back. The next day I removed the linux
drive and put back the Windows drive, and found the computer would not
boot.
Once again, I took it to the repair shop and was told the CPU was
damaged, and there was damage to the RAM too. Total cost was more than
I paid for the computer. I also took along the linux harddrive, and was
told that the drive had permanent damage (a brand new drive). The
repairman asked me what I was doing with these computers. As soon as I
mentioned the word "Linux", he told me that's my problem. He said Linux
destroys computer hardware, and said he wont even allow it in his shop.
He said that simply installing a self booting Linux CD can wreck a
computer in minutes. mostly destroying the CPU and drives. This is
caused because Linux sends the wrong voltages to components and burns up
the CPU and other chips. It also plays havoc with harddrives, and
causes them to lose their ability to read and write data.
So, here I sit with 2 ruined computers, 2 dead harddrives, and around
$1200 worth of damages and repair bills. (Not including many hours of
wasted time). Since Linux is made by a bunch of computer geeks and
idiots with no real business address, there is no one to sue. Both my
computer repairman and lawyer said it's worthless to even try a lawsuit.
It's just one of those hard lessons to learn in life.
All I can do is warn others, to avoid Linux like a deadly disease. Dont
even try it, unless you want to intentionally destroy your computer.
From now on, I'll just stick with Microsoft, even if their operating
systems are bloated. At least they dont destroy computers, and they
operate from an actual business that exists in brick and mortar, not to
mention having actual online and phone support.
Aragorn
Feb 19, 2013, 6:58:58 AM2/19/13
to
On Tuesday 19 February 2013 09:51, anon...@online.com conveyed the
following to alt.linux...
> I dont like Microsoft operating systems and wanted to try something
> different. The computer had a working installation of Windows, which
> had been running well despite being from MS. Rather than delete it, I
> just changed to another hard drive. I installed Linux. The
> installation process was very painful. Getting it to cooperate with
> the hardware was worse, and of course there is no real support.
Which is of course a bold-faced lie. But you knew that.
> I finally got it halfway working. At that point, I found it was hard
> to learn, harder to get used to, and hardest to do anything useful
> since none of the programs were familiar.
>
> Two days later the computer stopped working entirely and would not
> even boot. I spent hours fighting with it, tried to reinstall linux
> and it simply would not work. I removed the hard drive that linux was
> on, plugged back in my Windows hard drive, and could not make the
> computer boot up. I finally took it to a computer repair place, and
> was told the CPU was dead. Cost to replace was more than another
> computer.
Then you obviously have bought a bad computer. That happens. One of
the downsides of industrialization is that quality assurance drops
significantly.
> Hundreds of dollars later, I had another computer, with more power
> than before. Once again, I removed the hard drive, and installed that
> same spare harddrive with linux on it, only to discover that hard
> drive was permanently damaged. So, I purchased another harddrive,
> installed it, and installed another distro of linux that was listed to
> be one of the best ones.
And which one would that have been then, liar?
> A week of fighting with installing it, and trying to make it work, I
> finally had a semi-working computer. Another week of struggling with
> trying to learn and use Linux, I was ready to give up on it and put
> the original Windows hard drive back. The next day I removed the linux
> drive and put back the Windows drive, and found the computer would not
> boot.
>
> Once again, I took it to the repair shop and was told the CPU was
> damaged, and there was damage to the RAM too. Total cost was more
> than I paid for the computer.
That's not possible. And in addition to that, all computers come with
at least a 1- or 2-year warranty - 2 years is the legal minimum in the
part of the world where I reside - so it wouldn't have cost you
anything, unless there was unmistakable evidence that you yourself have
screwed up the hardware. Which, judging by your report on having
swapped out hard disks, you might as well have, both on your first and
your second computer.
> I also took along the linux harddrive, and was told that the drive had
> permanent damage (a brand new drive).
Some hard disk drives ship from the factory with permanent damage. I've
had one of those in this very machine here; it died within a month, and
the shop made no problem of swapping it out with a brand new one under
the warranty terms.
> The repairman asked me what I was doing with these computers. As soon
> as I mentioned the word "Linux", he told me that's my problem.
Oh, he knew that you were not mentally equipped to handle GNU/Linux?
> He said Linux destroys computer hardware, and said he wont even allow
> it in his shop.
Which is a gross lie, and if he ever did say such a thing, then he's as
incompetent as you are.
> He said that simply installing a self booting Linux CD can wreck a
> computer in minutes. mostly destroying the CPU and drives.
Bullshit. The only problem there has been where computers would become
useless after having booted GNU/Linux was with certain laptop models
manufactured by Samsung, because those laptops had UEFI firmware instead
of a BIOS, and there was a serious bug in the Samsung implementation of
that UEFI.
Samsung are working on the problem, and they acknowledge that the
problem was not caused by GNU/Linux, but by their own buggy firmware.
> This is caused because Linux sends the wrong voltages to components
> and burns up the CPU and other chips.
Another gross lie. GNU/Linux does not do such a thing. Voltages are
controlled and set by the machine's firmware at machine cold-boot time.
In a machine with a BIOS firmware chip, this happens with the processor
in so-called systems management mode, which is a low-level kind of real
mode. Operating systems cannot even switch the processor into that
mode; only the firmware can do that. However, since we are currently
talking of BIOS and BIOS runs in real mode, which no modern operating
system uses anymore - neither GNU/Linux, nor any of the BSDs, and not
even the NT-based (and thus current) versions of Windows - there is no
chance in the world that the Linux kernel (or that of any other
operating system on the x86 architecture) could be doing anything in
real mode, let alone in systems management mode.
In a machine with an UEFI firmware chip, the voltages /may/ - at least,
in theory - still be regulated while the operating system is already
booted, because the UEFI firmware runs in protected mode and could thus
in theory also still be active in the background after the operating
system has already booted. But then still, voltages are still a matter
of systems management mode, not of protected mode or long mode, which is
what the Linux kernel runs in.
The bottom line is that the Linux kernel does not control the voltages
on the motherboard, and that it can thus also not ruin the hardware by
setting an incorrect voltage, and that as such, and as was already to be
expected from you [*], you're full of shit.
[*] For the lurking GNUbies: This joker is one of the notorious nym-
shifting trolls from comp.os.linux.advocacy who recycles this same
old troll FUD every once in a while, sending it off to GNU/Linux
newsgroups where many GNUbies dwell. This tactic is commonly known
as /astroturfing/ - i.e. a tactic where a large corporation sends
off undercover shills to post negative stuff about what said
corporation perceives as being a competing product, under the
pretense that the negative stuff comes from grass roots. Microsoft
has already been doing this since the days of OS/2 - do a Google
search on "the Barkto Incident" - and they are still doing it today.
They must be really terrified over the fact that the real grass
roots - i.e. the Free/Libre & Open Source Software community - has
managed to create an operating system which is, has always been and
will always be so vastly superior to their bloated and insecure
vendor lock-in payware.
> It also plays havoc with harddrives, and causes them to lose their
> ability to read and write data.
Bullshit again.
> So, here I sit with 2 ruined computers, 2 dead harddrives, and around
> $1200 worth of damages and repair bills.
Next time, try buying computers from shops that do offer you a warranty.
But of course, you may discard this advice entirely, since nothing of
what you've written is actually true.
I am only replying to this troll FUD for the sake of the GNUbies,
because you and I both know that you are nothing but a filthy liar [*] -
which is also why you are using the anonymizing aioe.org as a gateway
for posting to Usenet, as virtually all of the trolls do - and that it
is therefore pointless to try and argue with you.
[*] Whether you are actually on Microsoft's payroll or whether you're
simply mentally deranged - as many Win-trolls are - is up for
debate, but personally I don't give a hoot about your motives. What
I do care about is that you are deliberately trying to sway the
GNUbies away from GNU/Linux and (back?) onto Microsoft Windows by
coming up with pseudo-technical explanations of why GNU/Linux would
be bad. And you just happen to be unfortunate enough that there are
people dwelling these newsgroups who actually know their shit a lot
better than you ever will in your pathetic, trolling life.
> (Not including many hours of wasted time).
If time is so important for you, then I would suggest that you spend far
less of it trying to write the perfect troll message, which, in being a
lie, is going to get refuted with documented technical facts in a matter
of hours anyway.
> Since Linux is made by a bunch of computer geeks and idiots with no
> real business address, there is no one to sue.
Gee, I guess that Oracle, Novell, RedHat, Canonical, IBM, Intel, AMD,
Hewlett-Packard, Dell, QLogic, SGI, Adaptec, 3Ware, 3Com, Broadcom,
Realtek and all those other companies who submit code to the development
of GNU/Linux must all be operating from within tents on a camping ground
then somewhere? Or maybe a trailer park?
> Both my computer repairman and lawyer said it's worthless to even try
> a lawsuit.
Yes, on that I would fully agree with them, because you simply don't
have any facts except those that you've made up on the spot.
> It's just one of those hard lessons to learn in life.
Somehow you don't strike me as the kind of person who actually learns
anything from life at all, given how many times you've already attempted
to perpetrate this very same nonsense (but with slightly different
wording and under different Usenet pseudonyms) in GNU/Linux newsgroups
over the years.
> All I can do is warn others, to avoid Linux like a deadly disease.
> Dont even try it, unless you want to intentionally destroy your
> computer.
I am very grateful that you're warning me about this, because my
computers have so far been running GNU/Linux for 13 years without any
problems at all, and with all hardware fully functional.
> From now on, I'll just stick with Microsoft, even if their operating
> systems are bloated. At least they dont destroy computers, [...
But, there /is/ scientific evidence that the use of Microsoft software
does destroy braincells and induces psychosis. Just look in the mirror!
> ...] and they operate from an actual business that exists in brick and
http://www.redhat.com/support/
https://www.suse.com/support/
http://www.oracle.com/us/support/index.html
http://www.mandriva.com/en/support/
http://www.ubuntu.com/support
http://www-304.ibm.com/support/operations/us/en/?lnk=msdCS-1-usen
...
--
= Aragorn =
(registered GNU/Linux user #223157)
following to alt.linux...
> I dont like Microsoft operating systems and wanted to try something
> different. The computer had a working installation of Windows, which
> had been running well despite being from MS. Rather than delete it, I
> just changed to another hard drive. I installed Linux. The
> installation process was very painful. Getting it to cooperate with
> the hardware was worse, and of course there is no real support.
> I finally got it halfway working. At that point, I found it was hard
> to learn, harder to get used to, and hardest to do anything useful
> since none of the programs were familiar.
>
> Two days later the computer stopped working entirely and would not
> even boot. I spent hours fighting with it, tried to reinstall linux
> and it simply would not work. I removed the hard drive that linux was
> on, plugged back in my Windows hard drive, and could not make the
> computer boot up. I finally took it to a computer repair place, and
> was told the CPU was dead. Cost to replace was more than another
> computer.
the downsides of industrialization is that quality assurance drops
significantly.
> Hundreds of dollars later, I had another computer, with more power
> than before. Once again, I removed the hard drive, and installed that
> same spare harddrive with linux on it, only to discover that hard
> drive was permanently damaged. So, I purchased another harddrive,
> installed it, and installed another distro of linux that was listed to
> be one of the best ones.
> A week of fighting with installing it, and trying to make it work, I
> finally had a semi-working computer. Another week of struggling with
> trying to learn and use Linux, I was ready to give up on it and put
> the original Windows hard drive back. The next day I removed the linux
> drive and put back the Windows drive, and found the computer would not
> boot.
>
> Once again, I took it to the repair shop and was told the CPU was
> damaged, and there was damage to the RAM too. Total cost was more
> than I paid for the computer.
at least a 1- or 2-year warranty - 2 years is the legal minimum in the
part of the world where I reside - so it wouldn't have cost you
anything, unless there was unmistakable evidence that you yourself have
screwed up the hardware. Which, judging by your report on having
swapped out hard disks, you might as well have, both on your first and
your second computer.
> I also took along the linux harddrive, and was told that the drive had
> permanent damage (a brand new drive).
had one of those in this very machine here; it died within a month, and
the shop made no problem of swapping it out with a brand new one under
the warranty terms.
> The repairman asked me what I was doing with these computers. As soon
> as I mentioned the word "Linux", he told me that's my problem.
> He said Linux destroys computer hardware, and said he wont even allow
> it in his shop.
incompetent as you are.
> He said that simply installing a self booting Linux CD can wreck a
> computer in minutes. mostly destroying the CPU and drives.
useless after having booted GNU/Linux was with certain laptop models
manufactured by Samsung, because those laptops had UEFI firmware instead
of a BIOS, and there was a serious bug in the Samsung implementation of
that UEFI.
Samsung are working on the problem, and they acknowledge that the
problem was not caused by GNU/Linux, but by their own buggy firmware.
> This is caused because Linux sends the wrong voltages to components
> and burns up the CPU and other chips.
controlled and set by the machine's firmware at machine cold-boot time.
In a machine with a BIOS firmware chip, this happens with the processor
in so-called systems management mode, which is a low-level kind of real
mode. Operating systems cannot even switch the processor into that
mode; only the firmware can do that. However, since we are currently
talking of BIOS and BIOS runs in real mode, which no modern operating
system uses anymore - neither GNU/Linux, nor any of the BSDs, and not
even the NT-based (and thus current) versions of Windows - there is no
chance in the world that the Linux kernel (or that of any other
operating system on the x86 architecture) could be doing anything in
real mode, let alone in systems management mode.
In a machine with an UEFI firmware chip, the voltages /may/ - at least,
in theory - still be regulated while the operating system is already
booted, because the UEFI firmware runs in protected mode and could thus
in theory also still be active in the background after the operating
system has already booted. But then still, voltages are still a matter
of systems management mode, not of protected mode or long mode, which is
what the Linux kernel runs in.
The bottom line is that the Linux kernel does not control the voltages
on the motherboard, and that it can thus also not ruin the hardware by
setting an incorrect voltage, and that as such, and as was already to be
expected from you [*], you're full of shit.
[*] For the lurking GNUbies: This joker is one of the notorious nym-
shifting trolls from comp.os.linux.advocacy who recycles this same
old troll FUD every once in a while, sending it off to GNU/Linux
newsgroups where many GNUbies dwell. This tactic is commonly known
as /astroturfing/ - i.e. a tactic where a large corporation sends
off undercover shills to post negative stuff about what said
corporation perceives as being a competing product, under the
pretense that the negative stuff comes from grass roots. Microsoft
has already been doing this since the days of OS/2 - do a Google
search on "the Barkto Incident" - and they are still doing it today.
They must be really terrified over the fact that the real grass
roots - i.e. the Free/Libre & Open Source Software community - has
managed to create an operating system which is, has always been and
will always be so vastly superior to their bloated and insecure
vendor lock-in payware.
> It also plays havoc with harddrives, and causes them to lose their
> ability to read and write data.
> So, here I sit with 2 ruined computers, 2 dead harddrives, and around
> $1200 worth of damages and repair bills.
But of course, you may discard this advice entirely, since nothing of
what you've written is actually true.
I am only replying to this troll FUD for the sake of the GNUbies,
because you and I both know that you are nothing but a filthy liar [*] -
which is also why you are using the anonymizing aioe.org as a gateway
for posting to Usenet, as virtually all of the trolls do - and that it
is therefore pointless to try and argue with you.
[*] Whether you are actually on Microsoft's payroll or whether you're
simply mentally deranged - as many Win-trolls are - is up for
debate, but personally I don't give a hoot about your motives. What
I do care about is that you are deliberately trying to sway the
GNUbies away from GNU/Linux and (back?) onto Microsoft Windows by
coming up with pseudo-technical explanations of why GNU/Linux would
be bad. And you just happen to be unfortunate enough that there are
people dwelling these newsgroups who actually know their shit a lot
better than you ever will in your pathetic, trolling life.
> (Not including many hours of wasted time).
less of it trying to write the perfect troll message, which, in being a
lie, is going to get refuted with documented technical facts in a matter
of hours anyway.
> Since Linux is made by a bunch of computer geeks and idiots with no
> real business address, there is no one to sue.
Hewlett-Packard, Dell, QLogic, SGI, Adaptec, 3Ware, 3Com, Broadcom,
Realtek and all those other companies who submit code to the development
of GNU/Linux must all be operating from within tents on a camping ground
then somewhere? Or maybe a trailer park?
> Both my computer repairman and lawyer said it's worthless to even try
> a lawsuit.
have any facts except those that you've made up on the spot.
> It's just one of those hard lessons to learn in life.
anything from life at all, given how many times you've already attempted
to perpetrate this very same nonsense (but with slightly different
wording and under different Usenet pseudonyms) in GNU/Linux newsgroups
over the years.
> All I can do is warn others, to avoid Linux like a deadly disease.
> Dont even try it, unless you want to intentionally destroy your
> computer.
computers have so far been running GNU/Linux for 13 years without any
problems at all, and with all hardware fully functional.
> From now on, I'll just stick with Microsoft, even if their operating
But, there /is/ scientific evidence that the use of Microsoft software
does destroy braincells and induces psychosis. Just look in the mirror!
> ...] and they operate from an actual business that exists in brick and
> mortar, not to mention having actual online and phone support.
Guess you've never heard of these then?
http://www.redhat.com/support/
https://www.suse.com/support/
http://www.oracle.com/us/support/index.html
http://www.mandriva.com/en/support/
http://www.ubuntu.com/support
http://www-304.ibm.com/support/operations/us/en/?lnk=msdCS-1-usen
...
--
= Aragorn =
(registered GNU/Linux user #223157)
Peter Köhlmann
Feb 19, 2013, 7:50:23 AM2/19/13
to
Idiot.
Flatfish, just give it up. You will not fool anyone with your inane lies.
How talk about what is at fault here, you cretin?
Could it perhaps be that there is a faulty UEFI, which does not adhere to
the standards?
Flatfish, just give it up. You will not fool anyone with your inane lies.
How talk about what is at fault here, you cretin?
Could it perhaps be that there is a faulty UEFI, which does not adhere to
the standards?
Bit Twister
Feb 19, 2013, 12:05:11 PM2/19/13
to
On Tue, 19 Feb 2013 02:51:09 -0600, anon...@online.com wrote:
> I dont like Microsoft operating systems and wanted to try something
> different. The computer had a working installation of Windows, which
> had been running well despite being from MS.
Sounds like it took you long enough to make a decision.
> I dont like Microsoft operating systems and wanted to try something
> different. The computer had a working installation of Windows, which
> had been running well despite being from MS.
> Rather than delete it, I just changed to another hard drive.
going to be a royal pain in the derriere to re-install windows,
drivers, updates, reboot, more updates, reboot, yet more updates, reboot....
> I installed Linux. The installation process was very painful.
complaining about it hurts here, and here, and here.
Doctor say, Oh I see. The first thing is to fix that broken finger.
> Getting it to cooperate with the hardware was worse,
> and of course there is no real support.
to pay a Linux Vendor for support. We understand. But that is your
fault, not Linux.
> I finally got it halfway working.
> At that point, I found it was hard to learn,
whatever it is called.
> harder to get used to, and hardest to do anything useful since none of
> the programs were familiar.
much choice, as seen here,
http://www.linuxlinks.com/article/20070701111340544/Equivalents.html
> and application names are different.
Yep, names have to be different otherwise M$ would have their legal
beagles filing lawsuits left and right.
> Two days later the computer stopped working entirely and would not even
> boot.
> I spent hours fighting with it, tried to reinstall linux and it
> simply would not work.
installer and had not "stopped working entirely".
> I removed the hard drive that linux was on,
> plugged back in my Windows hard drive, and could not make the computer
> boot up.
> I finally took it to a computer repair place, and was told the
> CPU was dead.
dead. I would have stuck the linux media in the system, booted and
called the repairman a liar.
> Cost to replace was more than another computer.
> Hundreds of dollars later, I had another computer, with more power than
> before. Once again, I removed the hard drive, and installed that same
> spare harddrive with linux on it, only to discover that hard drive was
> permanently damaged.
> So, I purchased another harddrive, installed it,
> and installed another distro of linux that was listed to be one of the
> best ones. A week of fighting with installing it, and trying to make it
> work, I finally had a semi-working computer. Another week of struggling
> with trying to learn and use Linux, I was ready to give up on it and put
> the original Windows hard drive back. The next day I removed the linux
> drive and put back the Windows drive, and found the computer would not
> boot.
and you plugging in the Window$ drive and it crapped your hardware.
> Once again, I took it to the repair shop and was told the CPU was
> damaged, and there was damage to the RAM too. Total cost was more than
> I paid for the computer. I also took along the linux harddrive, and was
> told that the drive had permanent damage (a brand new drive).
1. Your panty hose is rubbing up against your wool socks and trousers
creating a lot of static electricity which is punching out chips in
your system. Or
2. the repair shop knows they have a gold bearing customer who has no
clue about troubleshooting.
> The
> repairman asked me what I was doing with these computers. As soon as I
> mentioned the word "Linux", he told me that's my problem. He said Linux
> destroys computer hardware, and said he wont even allow it in his shop.
> He said that simply installing a self booting Linux CD can wreck a
> computer in minutes. mostly destroying the CPU and drives. This is
> caused because Linux sends the wrong voltages to components and burns up
> the CPU and other chips. It also plays havoc with harddrives, and
> causes them to lose their ability to read and write data.
that hardware, now isn't it.
> So, here I sit with 2 ruined computers, 2 dead harddrives, and around
> $1200 worth of damages and repair bills. (Not including many hours of
> wasted time). Since Linux is made by a bunch of computer geeks and
> idiots with no real business address, there is no one to sue. Both my
> computer repairman and lawyer said it's worthless to even try a lawsuit.
Linux Vendor. That is your fault.
> It's just one of those hard lessons to learn in life.
work done and I would have taken the system to another repair shop for
an estimate.
> All I can do is warn others,
disk/memory tester. If it boots and runs memory test, 90% of your
hardware is running. If memory test works, it is not a cpu/ram problem.
Testing the disk will tell you if it bad or not.
> to avoid Linux like a deadly disease.
> Dont
> even try it, unless you want to intentionally destroy your computer.
have bad bios firmware which can be bricked if the Windows or Linux
software probes the wrong addresses. Samsung is working hard to find their
problem.
> From now on, I'll just stick with Microsoft, even if their operating
> systems are bloated. At least they dont destroy computers, and they
> operate from an actual business that exists in brick and mortar, not to
> mention having actual online and phone support.
mortar vendor. That is your fault.
Troll meter reading, about .6
[12345678910]
\
.
Facts: non-existent
Data: none
Bullshit: way too much
Go ahead, give us the repair shop name, address, phone number, which two
Linux distribution you were too stupid to be able to comprehend.
Also give us make/mode of the two systems you hosed up and same for
the linux disk.
I am pretty sure we will find numerous people running linux on the
same hardware.
Hurtlin' Squirty
Feb 19, 2013, 2:20:18 PM2/19/13
to
On 02/19/2013 12:51 AM, anon...@online.com wrote:
> All I can do is warn others, to avoid Linux like a deadly disease. Dont
> even try it, unless you want to intentionally destroy your computer.
I know! I started my truck and a Linux CD was on the seat and then the
> All I can do is warn others, to avoid Linux like a deadly disease. Dont
> even try it, unless you want to intentionally destroy your computer.
check engine light turned on and the engine exploded!
philo
Feb 19, 2013, 5:24:17 PM2/19/13
to
As soon as I put Linux on my machine, the chassis shorted to ground,
all my fuses shorted out...and worst still, the transistors on-board
became semi-conductors.
--
https://www.createspace.com/3707686
cipher
Feb 19, 2013, 5:30:20 PM2/19/13
to
On Tue, 19 Feb 2013 02:51:09 -0600, anonymous Inscribed upon the Golden
Tablets of Usenet thusly:
Lying Ass WinTroll.
I run a business on Linux, no troubles, no money to Microsoft.
Fuck you, begone. No one is buying this shit....
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
)\ ( ) /( Cipher/Proud Member, Netscum Alumni Association
)-(0^^0)-( Bungmunch U./AHM Memorial Institute of F@x0r1n6/Dean
)/ \\// \( Colonel/1st Virginia Volunteers/CeSium Brigade
(oo) Registered Linux User #556617
/ ~~ \ Empire of APDD/#6-5p07/VLNOC Cohort #1407
o@o o@o Keeper of the alt.CeSium FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tablets of Usenet thusly:
I run a business on Linux, no troubles, no money to Microsoft.
Fuck you, begone. No one is buying this shit....
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
)\ ( ) /( Cipher/Proud Member, Netscum Alumni Association
)-(0^^0)-( Bungmunch U./AHM Memorial Institute of F@x0r1n6/Dean
)/ \\// \( Colonel/1st Virginia Volunteers/CeSium Brigade
(oo) Registered Linux User #556617
/ ~~ \ Empire of APDD/#6-5p07/VLNOC Cohort #1407
o@o o@o Keeper of the alt.CeSium FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Darklight
Feb 19, 2013, 7:05:22 PM2/19/13
to
full of it.
Whiskers
Feb 19, 2013, 7:19:15 PM2/19/13
to
some others, currently Arch) on this laptop for almost ten years. It is
definitely showing signs of wear, eg the letters have worn off most of the
keys and the paint has rubbed off where my hands rest on the case, but if
Linux is destroying anything it's taking its time about it.
No version of Windows has ever been installed, although it did ship with
enough PC-DOS to splash a message about not having an operating system when
first booting it up (and mentioning the free Mandrake 9 CD to be found in
the packageing).
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
kcGSH6nC
Feb 20, 2013, 12:20:28 AM2/20/13
to
Bit Twister wrote:
> Dumbass of the Year projectile-shat upon usenet with:
mortar vendors. Hell the first time I heard of Linux was seeing a RedHat
on a shelf.
> Dumbass of the Year projectile-shat upon usenet with:
>> From now on, I'll just stick with Microsoft, even if their operating
>> systems are bloated. At least they dont destroy computers, and they
>> operate from an actual business that exists in brick and mortar, not to
>> mention having actual online and phone support.
>
> Look out, you made to choice to not buy support from a brick and
> mortar vendor. That is your fault.
The best part about this is I have actually seen Linux in brick and
>> systems are bloated. At least they dont destroy computers, and they
>> operate from an actual business that exists in brick and mortar, not to
>> mention having actual online and phone support.
>
> Look out, you made to choice to not buy support from a brick and
> mortar vendor. That is your fault.
mortar vendors. Hell the first time I heard of Linux was seeing a RedHat
on a shelf.
dx...@albury.nospam.net.au
Feb 20, 2013, 5:13:49 AM2/20/13
to
One worked on a piece of radio equipment which had a "live" chassis
..... that had been shorted to ground by a blown capacitor.
By-the-by, also worked on an oscillator where the screwdriver adjusted
fine tune capacitor was connected to 240V!!
Daniel
Aragorn
Feb 20, 2013, 5:38:58 AM2/20/13
to
On Wednesday 20 February 2013 06:20, kcGSH6nC conveyed the following to
alt.linux...
I didn't even have an internet connection at home yet when I started
using GNU/Linux, so my first distribution was also a shrink-wrapped
retail box - Linux-Mandrake 6.0 PowerPack, back in 1999 - which I bought
at a software shop at a mall in the nearby city. I did get an internet
connection at home several months later on, but for as long as I could,
I chose to buy the shrink-wrapped retail boxes instead of downloading
the .iso files, so that I could give something back to the community.
Also those shrink-wrapped retail boxes came with printed manuals inside,
/and/ an official 90-day support contract (which I've never ever
needed), and the retail price for such a shrink-wrapped box with all the
CDs - some of which contained just the raw source code - and the manuals
and the support contract was only about 20% of what I had paid for my
bare-bones Windows NT 4.0 Workstation [*] license in 1997, not to
mention that Windows NT 4.0 all by itself was pretty useless without
buying additional application software and an anti-virus suite.
[*] I've used NT 4.0 for about two years, and it was the only Windows
version I've ever really used. My very first PC came preloaded
with DOS 5.0 and Windows 3.0, but I only used it like that for
about six months, pending the official release of the 32-bit
generation of OS/2, which I have subsequently used for over five
years. I only went with Windows NT because OS/2 was dead in the
water by 1997 and proprietary UNIX was way too expensive for
private use - allegedly there was a free (as in "free beer")
version of Solaris for x86 at the time, but I was not aware of that
then, or else I would have chosen that instead.
alt.linux...
using GNU/Linux, so my first distribution was also a shrink-wrapped
retail box - Linux-Mandrake 6.0 PowerPack, back in 1999 - which I bought
at a software shop at a mall in the nearby city. I did get an internet
connection at home several months later on, but for as long as I could,
I chose to buy the shrink-wrapped retail boxes instead of downloading
the .iso files, so that I could give something back to the community.
Also those shrink-wrapped retail boxes came with printed manuals inside,
/and/ an official 90-day support contract (which I've never ever
needed), and the retail price for such a shrink-wrapped box with all the
CDs - some of which contained just the raw source code - and the manuals
and the support contract was only about 20% of what I had paid for my
bare-bones Windows NT 4.0 Workstation [*] license in 1997, not to
mention that Windows NT 4.0 all by itself was pretty useless without
buying additional application software and an anti-virus suite.
[*] I've used NT 4.0 for about two years, and it was the only Windows
version I've ever really used. My very first PC came preloaded
with DOS 5.0 and Windows 3.0, but I only used it like that for
about six months, pending the official release of the 32-bit
generation of OS/2, which I have subsequently used for over five
years. I only went with Windows NT because OS/2 was dead in the
water by 1997 and proprietary UNIX was way too expensive for
private use - allegedly there was a free (as in "free beer")
version of Solaris for x86 at the time, but I was not aware of that
then, or else I would have chosen that instead.
Aragorn
Feb 20, 2013, 5:43:06 AM2/20/13
to
On Tuesday 19 February 2013 23:24, conveyed the following to
alt.linux...
All of the above is absolutely normal whenever you bootstrap a nuclear
reactor. :-D
alt.linux...
reactor. :-D
philo
Feb 20, 2013, 11:21:42 AM2/20/13
to
On 02/20/2013 04:13 AM, Dani...@teranews.com wrote:
<snip>
but back *many* years ago I had an "AC-DC" regenerative receiver that
would have a "hot" chassis if plugged in to the AC "the wrong way".
This was in the years before there were polarized plugs.
Yes, I got shocked from it.
Oh what fun those days were!
>
> One worked on a piece of radio equipment which had a "live" chassis
> ..... that had been shorted to ground by a blown capacitor.
>
> By-the-by, also worked on an oscillator where the screwdriver adjusted
> fine tune capacitor was connected to 240V!!
>
> Daniel
>
--
https://www.createspace.com/3707686
<snip>
>>
>> Yeah...I had a similar problem...
>>
>> As soon as I put Linux on my machine, the chassis shorted to ground,
>> all my fuses shorted out...and worst still, the transistors on-board
>> became semi-conductors.
>
> Quote "the chassis shorted to ground" End Quote
An obvious joke on my part...
>> Yeah...I had a similar problem...
>>
>> As soon as I put Linux on my machine, the chassis shorted to ground,
>> all my fuses shorted out...and worst still, the transistors on-board
>> became semi-conductors.
>
> Quote "the chassis shorted to ground" End Quote
but back *many* years ago I had an "AC-DC" regenerative receiver that
would have a "hot" chassis if plugged in to the AC "the wrong way".
This was in the years before there were polarized plugs.
Yes, I got shocked from it.
Oh what fun those days were!
>
> One worked on a piece of radio equipment which had a "live" chassis
> ..... that had been shorted to ground by a blown capacitor.
>
> By-the-by, also worked on an oscillator where the screwdriver adjusted
> fine tune capacitor was connected to 240V!!
>
> Daniel
>
https://www.createspace.com/3707686
philo
Feb 20, 2013, 11:22:19 AM2/20/13
to
bad sector
Feb 21, 2013, 10:58:12 PM2/21/13
to
On 02/19/2013 03:51 AM, anon...@online.com wrote:
> I dont like Microsoft operating systems and wanted to try something
> different.
http://www.youtube.com/watch?v=OYpiQvkfBnU
> I dont like Microsoft operating systems and wanted to try something
> different.
TJ
Feb 27, 2013, 9:12:31 PM2/27/13
to
The most amusing piece of fiction I've seen in a very long time.
Thanks for the good laugh!
TJ
Thanks for the good laugh!
TJ
unruh
Feb 27, 2013, 11:20:36 PM2/27/13
to
true. Samsung laptops have a bug in their bios which Linux triggers
(and Windows can trigger) which destroys the ability of the laptop to boot at
all.
According to this
http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
it seems to alter the bios to make the machine unbootable-- ie
it alters the firmware on the chip. Whether the alteration is in the
part that the cmos battery protects or is on the nand part of the bios
is apparently unclear. It is like if you update the bios in
your system, but instead of writing the new bios, you write garbage.
Nothing for it but to either throw it away or let the manufacturer
reinstall the bios.
So it might be possible that you could open up the laptop (not exactly
an easy thing to do with modern laptops) pull the cmos battery and
things would work again. Or it might not.
Anyway, it is a Sumsung bug, which is triggered by Linux (but not
usually by Windows).
Richard Kettlewell
Feb 28, 2013, 4:07:10 AM2/28/13
to
unruh <un...@invalid.ca> writes:
> According to this
> http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
> it seems to alter the bios to make the machine unbootable-- ie it
> alters the firmware on the chip. Whether the alteration is in the
> part that the cmos battery protects or is on the nand part of the bios
> is apparently unclear. It is like if you update the bios in your
> system, but instead of writing the new bios, you write garbage.
> Nothing for it but to either throw it away or let the manufacturer
> reinstall the bios.
It doesn’t involve modifying firmware. The bug is actually that the
> According to this
> http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
> it seems to alter the bios to make the machine unbootable-- ie it
> alters the firmware on the chip. Whether the alteration is in the
> part that the cmos battery protects or is on the nand part of the bios
> is apparently unclear. It is like if you update the bios in your
> system, but instead of writing the new bios, you write garbage.
> Nothing for it but to either throw it away or let the manufacturer
> reinstall the bios.
device won’t boot if too much UEFI variable storage space is used. For
more detail see http://mjg59.dreamwidth.org/22855.html
--
http://www.greenend.org.uk/rjk/
TJ
Feb 28, 2013, 9:41:02 AM2/28/13
to
On 02/27/2013 11:20 PM, unruh wrote:
> On 2013-02-28, TJ <T...@noneofyour.business> wrote:
>> On 02/19/2013 03:51 AM, anon...@online.com wrote:
>>
>> The most amusing piece of fiction I've seen in a very long time.
>>
>> Thanks for the good laugh!
>
> Had you kept reading the thread you would have discovered it is actually
> true. Samsung laptops have a bug in their bios which Linux triggers
> (and Windows can trigger) which destroys the ability of the laptop to boot at
> all.
>
>
I read the whole thread before posting. The OP had the ring of fiction
> On 2013-02-28, TJ <T...@noneofyour.business> wrote:
>> On 02/19/2013 03:51 AM, anon...@online.com wrote:
>>
>> The most amusing piece of fiction I've seen in a very long time.
>>
>> Thanks for the good laugh!
>
> Had you kept reading the thread you would have discovered it is actually
> true. Samsung laptops have a bug in their bios which Linux triggers
> (and Windows can trigger) which destroys the ability of the laptop to boot at
> all.
>
>
about it, and still does. The best fiction, especially the best comedy,
has at least a bit of plausibility in it. But that doesn't make it true.
TJ
Maurice Batey
Feb 28, 2013, 12:01:44 PM2/28/13
to
On Thu, 28 Feb 2013 04:20:36 +0000, unruh wrote:
> Samsung laptops have a bug in their bios which Linux triggers
> (and Windows can trigger) which destroys the ability of the laptop to boot at
> all.
*Certain* Samsung laptops...
> Samsung laptops have a bug in their bios which Linux triggers
> (and Windows can trigger) which destroys the ability of the laptop to boot at
> all.
--
/\/\aurice (Samsung NC110 user - no UEFI Linux problem)
(Replace "nomail.afraid" by "bcs" to reply by email)
unruh
Feb 28, 2013, 12:35:07 PM2/28/13
to
On 2013-02-28, Richard Kettlewell <r...@greenend.org.uk> wrote:
> unruh <un...@invalid.ca> writes:
>> According to this
>> http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
>> it seems to alter the bios to make the machine unbootable-- ie it
>> alters the firmware on the chip. Whether the alteration is in the
>> part that the cmos battery protects or is on the nand part of the bios
>> is apparently unclear. It is like if you update the bios in your
>> system, but instead of writing the new bios, you write garbage.
>> Nothing for it but to either throw it away or let the manufacturer
>> reinstall the bios.
>
> It doesn???t involve modifying firmware. The bug is actually that the
> unruh <un...@invalid.ca> writes:
>> According to this
>> http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
>> it seems to alter the bios to make the machine unbootable-- ie it
>> alters the firmware on the chip. Whether the alteration is in the
>> part that the cmos battery protects or is on the nand part of the bios
>> is apparently unclear. It is like if you update the bios in your
>> system, but instead of writing the new bios, you write garbage.
>> Nothing for it but to either throw it away or let the manufacturer
>> reinstall the bios.
>
> device won???t boot if too much UEFI variable storage space is used. For
It must involve modifying firmware since the it survives a reboot. (that
is the death survives a reboot). From what I understand once one has
tried to load Linux, the machine will refuse to boot even to Windows.
And your web page says that it does. It writes to the nram and what is
written causes the system to never boot again. And noone yet knows why.
Note that, as you know, the difference between hardware and firmware is
pretty small. If your cpu goes into an internal loop because the
firmware on the chip has a bug in it, is that a hardware or software
bug? There is no way of changing the firmware on the chip.
For you to laugh at someone who interprets a firmware bug as a hardware
bug, when the difference is completely irrelevant (the machine needs to
be sent in to Samsung to be fixed-- no user fixes possible).
>
unruh
Feb 28, 2013, 12:36:29 PM2/28/13
to
was true. Sometimes truth is as strange as fiction.
>
> TJ
Aragorn
Feb 28, 2013, 2:22:35 PM2/28/13
to
On Thursday 28 February 2013 18:36, unruh conveyed the following to
alt.linux...
That which the OP - the troll - said is *not* true, Bill. He wasn't
even talking about UEFI, but about Linux somehow sending the wrong
voltages to the CPU.
And, as Bit Twister showed, the OP's report was full of inconsistencies
and contradictions - such as attempting to install GNU/Linux on a
machine of which the OP earlier on had said that it couldn't boot
anymore - which were clearly indicative of how he - the OP - made it all
up on the spot.
The failure of Samsung machines with a UEFI after attempts to install
GNU/Linux on them is an entirely different debate, and the failure of
the machines is not due to any misbehavior from GNU/Linux, but due to a
serious bug in Samsung's implementation of UEFI.
The fact that this bug surfaced when people were trying to install
GNU/Linux on those Samsung machines *is not a corroboration* of what the
troll claimed, and it doesn't help The Truth (tm) if someone of your
caliber goes about and exclaims that - and I quote - "it was true".
There's enough anti-GNU/Linux FUD going round already, thanks to the
idiots in the mainstream media and the idiots who write columns in
computer magazines - ZDnet for instance - and who are themselves all too
prone to fall for the FUD spread by Steve "Monkey Dance" Ballmer and his
shills.
GNU/Linux has never ruined anything in its entire existence, except
Microsoft's aspirations for world domination.
alt.linux...
even talking about UEFI, but about Linux somehow sending the wrong
voltages to the CPU.
And, as Bit Twister showed, the OP's report was full of inconsistencies
and contradictions - such as attempting to install GNU/Linux on a
machine of which the OP earlier on had said that it couldn't boot
anymore - which were clearly indicative of how he - the OP - made it all
up on the spot.
The failure of Samsung machines with a UEFI after attempts to install
GNU/Linux on them is an entirely different debate, and the failure of
the machines is not due to any misbehavior from GNU/Linux, but due to a
serious bug in Samsung's implementation of UEFI.
The fact that this bug surfaced when people were trying to install
GNU/Linux on those Samsung machines *is not a corroboration* of what the
troll claimed, and it doesn't help The Truth (tm) if someone of your
caliber goes about and exclaims that - and I quote - "it was true".
There's enough anti-GNU/Linux FUD going round already, thanks to the
idiots in the mainstream media and the idiots who write columns in
computer magazines - ZDnet for instance - and who are themselves all too
prone to fall for the FUD spread by Steve "Monkey Dance" Ballmer and his
shills.
GNU/Linux has never ruined anything in its entire existence, except
Microsoft's aspirations for world domination.
Richard Kettlewell
Feb 28, 2013, 3:21:50 PM2/28/13
to
unruh <un...@invalid.ca> writes:
> Richard Kettlewell <r...@greenend.org.uk> wrote:
>> unruh <un...@invalid.ca> writes:
>>> According to this
>>> http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
>>> it seems to alter the bios to make the machine unbootable-- ie it
>>> alters the firmware on the chip. Whether the alteration is in the
>>> part that the cmos battery protects or is on the nand part of the bios
>>> is apparently unclear. It is like if you update the bios in your
>>> system, but instead of writing the new bios, you write garbage.
>>> Nothing for it but to either throw it away or let the manufacturer
>>> reinstall the bios.
>>
>> It doesn’t involve modifying firmware. The bug is actually that the
> Richard Kettlewell <r...@greenend.org.uk> wrote:
>> unruh <un...@invalid.ca> writes:
>>> According to this
>>> http://www.anandtech.com/show/6734/samsung-laptop-uefi-bugs-not-just-for-linux
>>> it seems to alter the bios to make the machine unbootable-- ie it
>>> alters the firmware on the chip. Whether the alteration is in the
>>> part that the cmos battery protects or is on the nand part of the bios
>>> is apparently unclear. It is like if you update the bios in your
>>> system, but instead of writing the new bios, you write garbage.
>>> Nothing for it but to either throw it away or let the manufacturer
>>> reinstall the bios.
>>
>> device won’t boot if too much UEFI variable storage space is used.
>> For more detail see http://mjg59.dreamwidth.org/22855.html
>
> It must involve modifying firmware since the it survives a reboot.
> (that is the death survives a reboot). From what I understand once one
> has tried to load Linux, the machine will refuse to boot even to
> Windows. And your web page says that it does. It writes to the nram
> and what is written causes the system to never boot again.
That’s not “modifying the firmware” as I’d understand the term. It’s
>
> It must involve modifying firmware since the it survives a reboot.
> (that is the death survives a reboot). From what I understand once one
> has tried to load Linux, the machine will refuse to boot even to
> Windows. And your web page says that it does. It writes to the nram
> and what is written causes the system to never boot again.
using the firmware to store data in persistent storage. The firmware
itself is not changed any more than (for instance) the Linux kernel is
changed when you use it to modify persistent storage such as a hard
disk.
> And noone yet knows why.
more than that without either the source code or time spent
disassembling it.
> Note that, as you know, the difference between hardware and firmware
> is pretty small. If your cpu goes into an internal loop because the
> firmware on the chip has a bug in it, is that a hardware or software
> bug? There is no way of changing the firmware on the chip.
updates for less integrated devices are completely routine of course.
> For you to laugh at someone who interprets a firmware bug as a hardware
> bug, when the difference is completely irrelevant (the machine needs to
> be sent in to Samsung to be fixed-- no user fixes possible).
--
http://www.greenend.org.uk/rjk/
George Csahanin
Mar 3, 2013, 12:00:16 PM3/3/13
to
OK. Thanks for the heads up, anonymous.
GeorgeC
(many, many working linux installs on desktops/workstations...including my
Android phone and tablet)
<anon...@online.com> wrote in message
news:e0f6i8hn6idlkcddh...@4ax.com...
GeorgeC
(many, many working linux installs on desktops/workstations...including my
Android phone and tablet)
<anon...@online.com> wrote in message
news:e0f6i8hn6idlkcddh...@4ax.com...
michel thomas
Mar 5, 2013, 2:18:42 AM3/5/13
to
One doesn't need a computer for a living. Cheers, Michel
Nun Giver
Mar 22, 2013, 8:41:39 PM3/22/13
to
Vista destroyed the functionality of this machine. I replaced it and
have had no problems for years.
Even if it cost me extra, I'll get a machine that is loaded with
a linux distro next new machine.
China is going to cook the MS goose and go Ubuntu.............Trig
have had no problems for years.
Even if it cost me extra, I'll get a machine that is loaded with
a linux distro next new machine.
China is going to cook the MS goose and go Ubuntu.............Trig
frackel...@gmail.com
Feb 8, 2014, 1:58:05 PM2/8/14
to
> It's just one of those hard lessons to learn in life.
>
>
>
>
>
>
> All I can do is warn others, to avoid Linux like a deadly disease. Dont
>
> even try it, unless you want to intentionally destroy your computer.
>
> From now on, I'll just stick with Microsoft, even if their operating
>
> systems are bloated. At least they dont destroy computers, and they
>
> operate from an actual business that exists in brick and mortar, not to
>
> mention having actual online and phone support.
Your fucking stupid!
>
> even try it, unless you want to intentionally destroy your computer.
>
> From now on, I'll just stick with Microsoft, even if their operating
>
> systems are bloated. At least they dont destroy computers, and they
>
> operate from an actual business that exists in brick and mortar, not to
>
> mention having actual online and phone support.
Lee Berry
May 14, 2015, 9:46:17 AM5/14/15
to
Sir why are you still fighting with your computer's HD? Most likely the HD had platter issues, and is more than 3-yrs old. I'm lucky if I get that much life out of hardware these days. Stop crying over spilled milk and get a cloud solution for your data. Boot the OS using a Linux preview USB thumb drive, and never ever carry your important data on your PC's HD. Once you find a flavor of Linux you like then use remix-tools to make your own tool set. A good place to start is with a copy of the Ultimate-recover CD/DVD or the Ultimate-boot-disk (UBCD). you can google those terms if your confused. My HD also recently died and yes i lost some data which caused me to rethink my back up strategy. Bone up, man up what ever you call it and stop blaming others for your mistake.
LinuxDevDog
Mar 24, 2016, 6:32:41 AM3/24/16
to
Linux does not damage hardware in any way. Please don't scare the Linux newbies by telling fake stuff. My laptop has been running Linux for about 6 months and it is working perfectly. If you didn't know that Android is based on Linux so all those phones and tablets should have broken by now.
And the installation process was very easy (easier than Windows 10). And it is not hard to use (if you don't want to play with the terminal (if you play with the Windows terminal)
If this is real then maybe your PC does not like Linux like those Samsung PCs (the problem is fixed)
And the installation process was very easy (easier than Windows 10). And it is not hard to use (if you don't want to play with the terminal (if you play with the Windows terminal)
If this is real then maybe your PC does not like Linux like those Samsung PCs (the problem is fixed)
J.O. Aho
Mar 26, 2016, 3:14:03 AM3/26/16
to
On 03/24/2016 11:32 AM, LinuxDevDog wrote:
> Linux does not damage hardware in any way. Please don't scare the Linux newbies by telling fake stuff.
The OP is just working for Microsoft and does FUD posts as Microsoft
> Linux does not damage hardware in any way. Please don't scare the Linux newbies by telling fake stuff.
feels threaten by Linux dominance as primary OS for the majority of
devices in the world, so they do what ever they can to scare people from
using worlds most used OS.
--
//Aho
Aragorn
Mar 26, 2016, 1:59:49 PM3/26/16
to
On Saturday 26 Mar 2016 08:14, J.O. Aho conveyed the following to
alt.linux...
> On 03/24/2016 11:32 AM, LinuxDevDog wrote:
>
>> Linux does not damage hardware in any way. Please don't scare the
>> Linux newbies by telling fake stuff.
>
> The OP is just working for Microsoft [...
Probably not directly anymore. Microsoft got more careful after the
Barkto Incident, and these days, governments, corporations, pressure
groups et al make use of independent shill companies which offer their
services for hire.
Even the business of trolling has been industrialized nowadays.
> ...] and does FUD posts as Microsoft feels threaten by Linux dominance
it, quoted in your post, because I wouldn't even have seen it if you
hadn't replied to it ;) ─ but to be honest, I don't even think that
Microsoft itself would be involved in this anymore, given that even
Microsoft has now developed its own (Debian-based) GNU/Linux
distribution for use in their Azure cloud. I still wouldn't trust
Microsoft any farther than I can throw it, but there is a significant
difference between the Microsoft of today and the Microsoft that used to
be run by Steve Ballmer.
That said, there has been a flurry of threads and posts from Win-droid
trolls from C.O.L.A. again, trying to disrupt as many GNU/Linux
newsgroups as they can. I suspect that this is is some sort of
coordinated attack which they agree upon in C.O.L.A. (or via e-mail or
social media).
These are not actual shills working for Microsoft (or some third-party
shill mercenary corporation) but rather a group of generally reactionary
ultra-right-wing zealots ─ most of them are racists, and most of them
are US American ─ afflicted with several mental conditions, such as...
- sadism
- narcissism
- sociopathy
They are schoolyard bullies, and they are afraid of GNU/Linux because
they are so stupid that they can't use anything other than a smartphone
interface, and so they bully everyone who uses and likes GNU/Linux for
what it is and what it was designed for, i.e. an alternative to
proprietary UNIX.
They've been going at it again for a few months already now, but their
offensive seems to have escalated again in the last two weeks. Maybe
the mental ward has let them out on a spring break or something. ;)
--
= Aragorn =
http://www.linuxcounter.net - registrant #223157
alt.linux...
> On 03/24/2016 11:32 AM, LinuxDevDog wrote:
>
>> Linux does not damage hardware in any way. Please don't scare the
>> Linux newbies by telling fake stuff.
>
Probably not directly anymore. Microsoft got more careful after the
Barkto Incident, and these days, governments, corporations, pressure
groups et al make use of independent shill companies which offer their
services for hire.
Even the business of trolling has been industrialized nowadays.
> ...] and does FUD posts as Microsoft feels threaten by Linux dominance
> as primary OS for the majority of devices in the world, so they do
> what ever they can to scare people from using worlds most used OS.
The post is most definitely FUD ─ at least, that which I am seeing of
> what ever they can to scare people from using worlds most used OS.
it, quoted in your post, because I wouldn't even have seen it if you
hadn't replied to it ;) ─ but to be honest, I don't even think that
Microsoft itself would be involved in this anymore, given that even
Microsoft has now developed its own (Debian-based) GNU/Linux
distribution for use in their Azure cloud. I still wouldn't trust
Microsoft any farther than I can throw it, but there is a significant
difference between the Microsoft of today and the Microsoft that used to
be run by Steve Ballmer.
That said, there has been a flurry of threads and posts from Win-droid
trolls from C.O.L.A. again, trying to disrupt as many GNU/Linux
newsgroups as they can. I suspect that this is is some sort of
coordinated attack which they agree upon in C.O.L.A. (or via e-mail or
social media).
These are not actual shills working for Microsoft (or some third-party
shill mercenary corporation) but rather a group of generally reactionary
ultra-right-wing zealots ─ most of them are racists, and most of them
are US American ─ afflicted with several mental conditions, such as...
- sadism
- narcissism
- sociopathy
They are schoolyard bullies, and they are afraid of GNU/Linux because
they are so stupid that they can't use anything other than a smartphone
interface, and so they bully everyone who uses and likes GNU/Linux for
what it is and what it was designed for, i.e. an alternative to
proprietary UNIX.
They've been going at it again for a few months already now, but their
offensive seems to have escalated again in the last two weeks. Maybe
the mental ward has let them out on a spring break or something. ;)
--
= Aragorn =
http://www.linuxcounter.net - registrant #223157
Time Traveler
Mar 27, 2016, 1:14:41 PM3/27/16
to
Aragorn wrote:
> On Saturday 26 Mar 2016 08:14, J.O. Aho conveyed the following to
> alt.linux...
>
>> On 03/24/2016 11:32 AM, LinuxDevDog wrote:
>>
>>> Linux does not damage hardware in any way. Please don't scare the
>>> Linux newbies by telling fake stuff.
>> The OP is just working for Microsoft [...
> On Saturday 26 Mar 2016 08:14, J.O. Aho conveyed the following to
> alt.linux...
>
>> On 03/24/2016 11:32 AM, LinuxDevDog wrote:
>>
>>> Linux does not damage hardware in any way. Please don't scare the
>>> Linux newbies by telling fake stuff.
>> The OP is just working for Microsoft [...
> The post is most definitely FUD ─ at least, that which I am seeing of
> it, quoted in your post, because I wouldn't even have seen it if you
> hadn't replied to it ;)
You probably just forgot, as the "original" post was 3 years ago! :)
> it, quoted in your post, because I wouldn't even have seen it if you
> hadn't replied to it ;)
Aragorn
Mar 27, 2016, 1:36:07 PM3/27/16
to
On Sunday 27 Mar 2016 19:15, Time Traveler conveyed the following to
Either way, what is true is that this kind of FUD and other troll
material are still being posted in high frequency to a lot of newsgroups
these days. There's a periodicity to it. Probably related to spring
break at the mental asylum. :p
alt.linux...
> Aragorn wrote:
>
>> On Saturday 26 Mar 2016 08:14, J.O. Aho conveyed the following to
>> alt.linux...
>>
>>> On 03/24/2016 11:32 AM, LinuxDevDog wrote:
>>>
>>>> Linux does not damage hardware in any way. Please don't scare the
>>>> Linux newbies by telling fake stuff.
>>> The OP is just working for Microsoft [...
>>
>>
>> The post is most definitely FUD ─ at least, that which I am seeing of
>> it, quoted in your post, because I wouldn't even have seen it if you
>> hadn't replied to it ;)
>
> You probably just forgot, as the "original" post was 3 years ago! :)
That explains why it wasn't visible in the newsfeed. ;)
> Aragorn wrote:
>
>> On Saturday 26 Mar 2016 08:14, J.O. Aho conveyed the following to
>> alt.linux...
>>
>>> On 03/24/2016 11:32 AM, LinuxDevDog wrote:
>>>
>>>> Linux does not damage hardware in any way. Please don't scare the
>>>> Linux newbies by telling fake stuff.
>>> The OP is just working for Microsoft [...
>>
>>
>> The post is most definitely FUD ─ at least, that which I am seeing of
>> it, quoted in your post, because I wouldn't even have seen it if you
>> hadn't replied to it ;)
>
> You probably just forgot, as the "original" post was 3 years ago! :)
Either way, what is true is that this kind of FUD and other troll
material are still being posted in high frequency to a lot of newsgroups
these days. There's a periodicity to it. Probably related to spring
break at the mental asylum. :p
Message has been deleted
luongs...@gmail.com
Apr 23, 2016, 3:00:23 AM4/23/16
to
On Saturday, 23 April 2016 13:56:01 UTC+7, luongs...@gmail.com wrote:
> Absolutely correct, kill one wifi card and a battery in my Asus laptop. Ruin my Lenovo laptop heat due to bug in Nvidia driver can not turn it off.
CPU always run at max frequency, fan speed not controllable, HDD head park ruin, firmware ruin.....etc ...etc.....
Linux is worst in term of hardware compatibility ACPI power management
CPU always run at max frequency, fan speed not controllable, HDD head park ruin, firmware ruin.....etc ...etc.....
Linux is worst in term of hardware compatibility ACPI power management
J.O. Aho
Apr 23, 2016, 4:35:41 AM4/23/16
to
On 04/23/2016 09:00 AM, luongs...@gmail.com wrote:
>> Absolutely correct, kill one wifi card and a battery in my Asus laptop. Ruin my Lenovo laptop heat due to bug in Nvidia driver can not turn it off.
> CPU always run at max frequency, fan speed not controllable, HDD head park ruin, firmware ruin.....etc ...etc.....
> Linux is worst in term of hardware compatibility ACPI power management
ACPI power management will not affect the life of your hardware, in
>> Absolutely correct, kill one wifi card and a battery in my Asus laptop. Ruin my Lenovo laptop heat due to bug in Nvidia driver can not turn it off.
> CPU always run at max frequency, fan speed not controllable, HDD head park ruin, firmware ruin.....etc ...etc.....
> Linux is worst in term of hardware compatibility ACPI power management
worst case it will not take down hardware to a power saving mode which
results in that you need to recharge your battery more often.
Don't forget that approximate 20% of all hardware manufactured nowadays
has hardware issues already at the factory, but they are delivered to
end customers, this number used to be 10%.
The OS which kills most hardware is still the closed source operating
system called microsoft windows.
No need to keep on FUD:ing a OS which has nothing to do with your issues.
highlandham
Nov 6, 2016, 8:10:44 AM11/6/16
to
To support the above, I just have installed Linux MX16 (formerly Mepis)
on a 12 years old Acer Travelmate 6000 laptop with a Pentium M CPU ,
1.256GB RAM and a 40GB hard drive. Running very well with so much
free software available incl the latest LibreOffice,version 5 suite.
Also run Lubuntu 16.04 on a AD2005 Compac Presario desktop PC again
with all the latest free software I need
It all shows that old hardware (if necessary)augmented with low cost
memory from eBay suits 99.9% of all software requirements by individuals
and even most corporate entities.
Frank , in northern Scotland Radio Amateur GM0CSZ / KN6WH in IO87AT
0 new messages