23.11.2010 - 06:33
Linux made my computer ignite
into flames halfway thru the installation. My entire computer room
and the bathroom were gutted and the rest of the house sufferred
severe smoke and water damage. It took the fire department 2 1/2
hours to put out the blaze and the damages are in excess of $80,000.
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see Linux banned.
Vern
23.11.2010 - 06:42
On Tuesday 23 November 2010 06:33 in alt.os.linux, somebody identifying
as vernfolica@metro.com wrote...
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room
and the bathroom were gutted and the rest of the house sufferred
severe smoke and water damage. It took the fire department 2 1/2
hours to put out the blaze and the damages are in excess of $80,000.
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see Linux banned.
alt.net.kooks is that way --->
--
*Aragorn*
(registered GNU/Linux user #223157)
as vernfolica@metro.com wrote...
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room
and the bathroom were gutted and the rest of the house sufferred
severe smoke and water damage. It took the fire department 2 1/2
hours to put out the blaze and the damages are in excess of $80,000.
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see Linux banned.
alt.net.kooks is that way --->
--
*Aragorn*
(registered GNU/Linux user #223157)
23.11.2010 - 12:35
Responding to vernfolica:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room and
the bathroom were gutted and the rest of the house sufferred severe
smoke and water damage. It took the fire department 2 1/2 hours to put
out the blaze and the damages are in excess of $80,000. The insurance
company said the house may have to be demolished. The chief of the fire
department said that Linux fires are normal, and said they want to see
Linux banned.
Vern
Are you sure you /completely/ removed the original Barbiware first?
Widnos is famous for buggering up attempts to replace it y'know.
--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room and
the bathroom were gutted and the rest of the house sufferred severe
smoke and water damage. It took the fire department 2 1/2 hours to put
out the blaze and the damages are in excess of $80,000. The insurance
company said the house may have to be demolished. The chief of the fire
department said that Linux fires are normal, and said they want to see
Linux banned.
Vern
Are you sure you /completely/ removed the original Barbiware first?
Widnos is famous for buggering up attempts to replace it y'know.
--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
23.11.2010 - 14:42
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or vertical
scan frequencies in Xorg.conf beyond what a CRT can support.
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or vertical
scan frequencies in Xorg.conf beyond what a CRT can support.
23.11.2010 - 15:12
On Tue, 23 Nov 2010 13:42:54 +0000, J G Miller wrote:
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica
explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or vertical
scan frequencies in Xorg.conf beyond what a CRT can support.
No, no. The Vern doofus said his *computer* ignited, not his monitor.
This is what happens with the scenario you are referring to:
http://brandybuck.site40.net/pics/humor/meltedmonitor.jpg
Of course, that is usually a result of this:
http://brandybuck.site40.net/pics/humor/headsup.jpg
(which also applies to 'Vern').
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as Piglet refused to give him some Pooh-tang.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica
explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or vertical
scan frequencies in Xorg.conf beyond what a CRT can support.
No, no. The Vern doofus said his *computer* ignited, not his monitor.
This is what happens with the scenario you are referring to:
http://brandybuck.site40.net/pics/humor/meltedmonitor.jpg
Of course, that is usually a result of this:
http://brandybuck.site40.net/pics/humor/headsup.jpg
(which also applies to 'Vern').
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as Piglet refused to give him some Pooh-tang.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
23.11.2010 - 17:11
On 2010-11-23, vernfolica@metro.com <vernfolica@metro.com> wrote:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room
and the bathroom were gutted and the rest of the house sufferred
severe smoke and water damage. It took the fire department 2 1/2
hours to put out the blaze and the damages are in excess of $80,000.
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see Linux banned.
You were lucky. It is a little known fact that Linux has some secret
codes in it that cause some of the nuclear warheads in the American and
Russian arsenal to be targeted on the location of the system. So far
only a couple of houses in the wastes of Canada have been obliterated,
but one of these days... (No you have not heard about them-- there is
another Linux virus which wipes out all references to stories like this
in all the newsmedia of the world.)
;-)
Vern
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room
and the bathroom were gutted and the rest of the house sufferred
severe smoke and water damage. It took the fire department 2 1/2
hours to put out the blaze and the damages are in excess of $80,000.
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see Linux banned.
You were lucky. It is a little known fact that Linux has some secret
codes in it that cause some of the nuclear warheads in the American and
Russian arsenal to be targeted on the location of the system. So far
only a couple of houses in the wastes of Canada have been obliterated,
but one of these days... (No you have not heard about them-- there is
another Linux virus which wipes out all references to stories like this
in all the newsmedia of the world.)
;-)
Vern
23.11.2010 - 20:11
On Tuesday 23 November 2010 15:12 in alt.os.linux, somebody identifying
as Dan C wrote...
On Tue, 23 Nov 2010 13:42:54 +0000, J G Miller wrote:
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica
explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or
vertical scan frequencies in Xorg.conf beyond what a CRT can support.
No, no. The Vern doofus said his *computer* ignited, not his monitor.
This is what happens with the scenario you are referring to:
http://brandybuck.site40.net/pics/humor/meltedmonitor.jpg
Of course, that is usually a result of this:
http://brandybuck.site40.net/pics/humor/headsup.jpg
(which also applies to 'Vern').
My guess is that his computer ignited due to his hard disk overheating
after the repetitive but very futile attempts to defragment his Sea
Drive in Windwoes, so that the machine was already cooking before he
even put in the Ubuntu CD. ;-)
--
*Aragorn*
(registered GNU/Linux user #223157)
as Dan C wrote...
On Tue, 23 Nov 2010 13:42:54 +0000, J G Miller wrote:
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica
explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or
vertical scan frequencies in Xorg.conf beyond what a CRT can support.
No, no. The Vern doofus said his *computer* ignited, not his monitor.
This is what happens with the scenario you are referring to:
http://brandybuck.site40.net/pics/humor/meltedmonitor.jpg
Of course, that is usually a result of this:
http://brandybuck.site40.net/pics/humor/headsup.jpg
(which also applies to 'Vern').
My guess is that his computer ignited due to his hard disk overheating
after the repetitive but very futile attempts to defragment his Sea
Drive in Windwoes, so that the machine was already cooking before he
even put in the Ubuntu CD. ;-)
--
*Aragorn*
(registered GNU/Linux user #223157)
23.11.2010 - 20:39
On Mon, 22 Nov 2010 23:33:47 -0600, vernfolica wrote:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room and
the bathroom were gutted and the rest of the house sufferred severe
smoke and water damage. It took the fire department 2 1/2 hours to put
out the blaze and the damages are in excess of $80,000. The insurance
company said the house may have to be demolished. The chief of the fire
department said that Linux fires are normal, and said they want to see
Linux banned.
Vern
Aye - that's a constant problem for people with lower than room
temperature IQ - they can't do anything right.
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation. My entire computer room and
the bathroom were gutted and the rest of the house sufferred severe
smoke and water damage. It took the fire department 2 1/2 hours to put
out the blaze and the damages are in excess of $80,000. The insurance
company said the house may have to be demolished. The chief of the fire
department said that Linux fires are normal, and said they want to see
Linux banned.
Vern
Aye - that's a constant problem for people with lower than room
temperature IQ - they can't do anything right.
23.11.2010 - 22:00
On 2010-11-23, Mike Jones wrote:
Are you sure you /completely/ removed the original Barbiware first?
Widnos is famous for buggering up attempts to replace it y'know.
'tis too. The OP is giving us a joke ladies and gents and nothing more.
--
Bud
Are you sure you /completely/ removed the original Barbiware first?
Widnos is famous for buggering up attempts to replace it y'know.
'tis too. The OP is giving us a joke ladies and gents and nothing more.
--
Bud
23.11.2010 - 23:38
On 11/23/2010 5:42 AM, J G Miller wrote:
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or vertical
scan frequencies in Xorg.conf beyond what a CRT can support.
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or vertical
scan frequencies in Xorg.conf beyond what a CRT can support.
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
24.11.2010 - 05:46
On Tuesday 23 November 2010 23:38 in alt.os.linux, somebody identifying
as Thad Floryan wrote...
On 11/23/2010 5:42 AM, J G Miller wrote:
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica
explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or
vertical scan frequencies in Xorg.conf beyond what a CRT can support.
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
And virtually entirely eliminated by 2010, as all modern CRT monitors
effectively switch into powersavings mode when an out-of-sync is
detected, and most people - myself not included - are buying TFT
monitors these days instead of having to deal with bulky CRT displays.
I don't think there will be too many of those earlier, "fully analog"
CRT monitors from the late '80s to mid '90s going round anymore. Most
of them would be far beyond their initial life expectancy by now.
--
*Aragorn*
(registered GNU/Linux user #223157)
as Thad Floryan wrote...
On 11/23/2010 5:42 AM, J G Miller wrote:
On Monday, November 22nd, 2010 at 23:33:47h -0600, Vern Folica
explained:
I was trying to install Ubuntu Linux. My computer ignited and burst
into flames halfway thru the installation.
That is what happens when you put a value for the horizontal or
vertical scan frequencies in Xorg.conf beyond what a CRT can support.
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
And virtually entirely eliminated by 2010, as all modern CRT monitors
effectively switch into powersavings mode when an out-of-sync is
detected, and most people - myself not included - are buying TFT
monitors these days instead of having to deal with bulky CRT displays.
I don't think there will be too many of those earlier, "fully analog"
CRT monitors from the late '80s to mid '90s going round anymore. Most
of them would be far beyond their initial life expectancy by now.
--
*Aragorn*
(registered GNU/Linux user #223157)
24.11.2010 - 07:05
On Mon, 22 Nov 2010 23:33:47 -0600
vernfolica@metro.com wrote:
<snip>
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see a Linux band.
Vern
You know, if you tried to install Ubuntu again, you could probably finish
the job.
--
Slackware 13.1, 2.6.33.4-smp, Core i7 920
RLU #272755
vernfolica@metro.com wrote:
<snip>
The insurance company said the house may have to be demolished. The
chief of the fire department said that Linux fires are normal, and
said they want to see a Linux band.
Vern
You know, if you tried to install Ubuntu again, you could probably finish
the job.
--
Slackware 13.1, 2.6.33.4-smp, Core i7 920
RLU #272755
24.11.2010 - 10:14
On 2010-11-23, Thad Floryan <thad@thadlabs.com> wrote:
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
setting the sync rates to zero (which by the way is impossible)
would have the same effect as turning off the sync (which is possible)
and all that does is stop retriggering the sync and cause the monitor
to go into energy saving mode (or behave like the cable is unplugged)
thses days all CRTs have microcontrollers inside them that shut them
down if they see signals they don't like
if it's got pushbuttons on the front for setup it's not going to be
damaged by any sync signals.
--
⚂⚃ 100% natural
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
setting the sync rates to zero (which by the way is impossible)
would have the same effect as turning off the sync (which is possible)
and all that does is stop retriggering the sync and cause the monitor
to go into energy saving mode (or behave like the cable is unplugged)
thses days all CRTs have microcontrollers inside them that shut them
down if they see signals they don't like
if it's got pushbuttons on the front for setup it's not going to be
damaged by any sync signals.
--
⚂⚃ 100% natural
24.11.2010 - 20:07
On 11/24/2010 1:14 AM, Jasen Betts wrote:
On 2010-11-23, Thad Floryan <thad@thadlabs.com> wrote:
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
setting the sync rates to zero (which by the way is impossible)
would have the same effect as turning off the sync (which is possible)
and all that does is stop retriggering the sync and cause the monitor
to go into energy saving mode (or behave like the cable is unplugged)
[...]
Not in the 1980s (which is what I cited). "Energy savings" had
yet to be invented.
Back then, hardware was vulnerable and a malware-infected driver
could do nasty things.
On 2010-11-23, Thad Floryan <thad@thadlabs.com> wrote:
What you wrote is actually not a joke, with one difference.
Setting the (refresh) scan rate(s) to zero effectively places
DC on the CRT's coils causing them to heat up and glow (think
NiCr wire in a kitchen toaster) then burn-through or fracture
the glass neck of the CRT destroying it and igniting any close-by
combustible parts within the enclosure. This was allegedly a
real problem back in the 1980s with early PCs and malware.
setting the sync rates to zero (which by the way is impossible)
would have the same effect as turning off the sync (which is possible)
and all that does is stop retriggering the sync and cause the monitor
to go into energy saving mode (or behave like the cable is unplugged)
[...]
Not in the 1980s (which is what I cited). "Energy savings" had
yet to be invented.
Back then, hardware was vulnerable and a malware-infected driver
could do nasty things.
24.11.2010 - 20:44
Thad Floryan writes:
Not in the 1980s...
Yes, in the 1980s (and the 1970s). The horizontal deflection signal was
generated in the monitor by a free-running injection-locked oscillator.
Setting the sync to zero would merely have resulted in the oscillator
free running due to the absence of an injected sync signal.
Setting the horizontal sync too high, however, could damage some of
those monitors. Modern monitors are immune to this problem.
Back then, hardware was vulnerable and a malware-infected driver could
do nasty things.
I hope you don't labor under the delusion that modern hardware is
invulnerable.
--
John Hasler
jhasler@newsguy.com
Dancing Horse Hill
Elmwood, WI USA
Not in the 1980s...
Yes, in the 1980s (and the 1970s). The horizontal deflection signal was
generated in the monitor by a free-running injection-locked oscillator.
Setting the sync to zero would merely have resulted in the oscillator
free running due to the absence of an injected sync signal.
Setting the horizontal sync too high, however, could damage some of
those monitors. Modern monitors are immune to this problem.
Back then, hardware was vulnerable and a malware-infected driver could
do nasty things.
I hope you don't labor under the delusion that modern hardware is
invulnerable.
--
John Hasler
jhasler@newsguy.com
Dancing Horse Hill
Elmwood, WI USA
Ähnliche Themen
[News] Arium Releases AE Linux, Improvements Made to Linux Boot Time
04.03.2010 - 10:10 - Posts: 1
How to tell what computer an install DVD is made for?
27.04.2011 - 15:35 - Posts: 1
### COMPUTER MADE VERY EASY ###
10.07.2009 - 13:52 - Posts: 1
w to tell what computer an install DVD is made for?
27.04.2011 - 21:35 - Posts: 2
Apple Computer, Inc made mistake to do SHR?
13.07.2009 - 03:52 - Posts: 13
Computer hardware made in China - why?
09.09.2009 - 18:57 - Posts: 1
The best 8-bit computer Commodore ever made was... the MPS1200!
08.08.2011 - 18:12 - Posts: 14
More
Search
