Well, interesting week...
 

On Feb 3, 3:52 pm, "RCE" wrote:
"BAR" wrote in message

. ..



Regardless of whether it has a sleep mode or not unless it is a server
class system it is not "designed" to be on 24x7. Server class means on
24x7. Desktop means on 9 to 5. Laptop means on when you are using it.

That might be what "they" say, but I don't buy it.

The killer for electronics, particularly high density power devices like the
CPU, is thermal cycling.
Components that consume power have a higher failure rate when they are
routinely cycled from operating temperature to ambient, then back to
operating temperature.

Other components, like the fan might fail, causing overheating and failure
of the electronic devices, but leaving electronics on all the time is better
for them in terms of life. An incandescent light bulb is the same deal.
One that is constantly turned on and off will fail sooner than one that is
left on all the time.

I suspect that may be true for some types of electronic equipment -
test
equipment comes to mind immediately and certain types of ovens and
such for manufacturing, but I'm not at all sure that is an absolute in
terms
of consumer electronics. I'm not an expert on thermal damage, nor do
I
play one on TV, but I've got to think that consumer CPUs are meant to
operate
within a range of temperatures - it just makes sense to me. I leave
the computer
on during the day and into the night - when I'm finished for the day,
it is shut
down and restarted the next morning.

Here's the way I look at it. TVs have a lot of the same components -
in
particular some of the newer HD TVs and higher end TVs - modern
stereos and amps also. Your radar and nav systems have a lot of
similar components. You don't leave those on 24/7/365 - why should
a computer be any different?

And think of this - even with shutting down the drives and monitor,
you
are still spending about $200 a year in electricity to keep the CPU
warm.
For that money, you could by a high end, full replacement service
policy
and probably save $50.

Well, interesting week...
 

Remember typing in all those addresses in the email for routing?

I never had to do that. On cserve, the nodes were designed for all traffic
to go to and from Ohio (their headquarters). 99% of the email that
originated from a cserve member went to a cserve member, so it was only a
matter of transferring it from one mailbox to another... on the same
network.

My duties had more to do with managing various file libraries, and
moderating forums. I was one of those guys that thought the www (netscape,
yahoo, etc) would never catch on.... oops. :-)

--Mike

wrote in message
ups.com...
On Feb 2, 9:33 pm, "Mike" wrote:
Truth is that many folks you might consider a**holes online, are usually
nice folks in person. The anonymity of the internet brings out the worst
in
some people. Maybe it's pent up agression from home or work... it doesn't
really matter.

I've been involved "online" since 1983, starting as a member of
Compuserve
and GeNie, then later as a staff member, then sysop, on a very popular
C'serve forum. I met quite a few folks as a result of my sysop duties. My
experience is that the biggest blowhards online, are generally the
opposite
in person. Of course, there *are* exceptions to every rule, and I've seen
that as well g Funny thing, is that the reverse can be true as well.
One
fellow, that I got along very well with "online" turned out to be a HUGE
butthead in person. Haven't talked to him since...

I never was involved with Compuserve, but I was a sysop for the CTPC
BBS
loop and ran a huge BBS on the old PC BBS system back then. I also
had
a node set up on the ARS Packet Relay Net with the Internet through
UCONN
which cost me a bundle in phone charges in those days. I also ran a
BBS
consortium and had sysop priviledges on the old Channel One system in
Boston which my brother was involved in.

Those were the fun days. I can remember sitting up for hours at night
testing
relay junctions for email - I still remember getting a straight
through route
from Woodstock to San Diego to San Francisco - took me all night and
Mrs.
Wave was not happy with me as I get grumpy if I don't get decent
rest. :)

Remember typing in all those addresses in the email for routing?

Well, interesting week...
 

"JimH" wrote in message
...

"BAR" wrote in message
. ..
JimH wrote:
wrote in message
oups.com...
On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

oups.com...





On Feb 2, 7:42 am, "JimH" wrote:
wrote in message
ups.com...
1 - Computer caught fire.
2 - Office smoke damage.
That sucks! Some here will blame it on bad karma. ;-)
Was it the power supply catching fire?
I guess - that's what the Fire Marshall said. Kind of a thermal
runaway.
How old was it?
Three years.


Are you going to notify the manufacturer of the computer and/or power
supply? It is useful information for them and may lead to a recall.

I would also pursue a claim against them to recover damages from the
fire. This failure and resulting fire is certainly not to be expected as
the power supply was certainly well within it's expected useful life.

The first question they will ask is if you turned it off before you left
the room. If it isn't a server class system it is not "intended" to be
turned on all of the time.



Wrong. Computers are made to be kept on 24x7. Why do you think they
have "sleep modes" on computers and monitors?



For "Green" listing. Power saving mode when you just leave it on for no
valid reason. I designed Disk Drives for a living for 10 years, disk drive
controllers for 15 years and apps engineer to the disk drive world for
another 5 years and we never looked at the system to have to be on 24x7.

Well, interesting week...
 

On 3 Feb 2007 15:03:16 -0800, wrote:

Flame wars can be fun and
if the participants keep it civil, it's much like having a "snap"
contest.

Civil is a concept which has proven elusive here in the past. Better
not to stir the pot too much.

Well, interesting week...
 

On Sun, 04 Feb 2007 01:28:59 GMT, "Mike" wrote:

I was one of those guys that thought the www (netscape,
yahoo, etc) would never catch on.... oops. :-)

Compuserve management thought the same thing until it was too late to
save the franchise.

Really big oops.

Well, interesting week...
 

Ain't that the truth. Then when AOL (the evil empire) bought compuserve, I
resigned.

--Mike

"Wayne.B" wrote in message
...
On Sun, 04 Feb 2007 01:28:59 GMT, "Mike" wrote:

I was one of those guys that thought the www (netscape,
yahoo, etc) would never catch on.... oops. :-)

Compuserve management thought the same thing until it was too late to
save the franchise.

Really big oops.

Well, interesting week...
 

Gene Kearns wrote:
On 3 Feb 2007 15:27:35 -0800, penned the following
well considered thoughts to the readers of rec.boats:

On Feb 3, 12:43 pm, Gene Kearns
wrote:
On 2 Feb 2007 05:17:57 -0800, penned the following
well considered thoughts to the readers of rec.boats:

4 - Purchase new computer - this time I'm building my own.
Does that mean you are rescinding your prior endorsements for
e-machine?
Not at all - it is what it is - a basic computer that works well.
Cheap
and easy to work with.

Just don't expect it to last forever.

Somehow.... I see a vast distinction between "not lasting forever" and
"bursting into flame".....

Maybe it was half full of dog hair and cigar ashes...

Well, interesting week...
 

JimH wrote:
"BAR" wrote in message
. ..
JimH wrote:
"BAR" wrote in message
. ..
JimH wrote:
wrote in message
oups.com...
On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

oups.com...





On Feb 2, 7:42 am, "JimH" wrote:
wrote in message
ups.com...
1 - Computer caught fire.
2 - Office smoke damage.
That sucks! Some here will blame it on bad karma. ;-)
Was it the power supply catching fire?
I guess - that's what the Fire Marshall said. Kind of a thermal
runaway.
How old was it?
Three years.

Are you going to notify the manufacturer of the computer and/or power
supply? It is useful information for them and may lead to a recall.

I would also pursue a claim against them to recover damages from the
fire. This failure and resulting fire is certainly not to be expected
as the power supply was certainly well within it's expected useful
life.
The first question they will ask is if you turned it off before you left
the room. If it isn't a server class system it is not "intended" to be
turned on all of the time.


Wrong. Computers are made to be kept on 24x7. Why do you think they
have "sleep modes" on computers and monitors?
Regardless of whether it has a sleep mode or not unless it is a server
class system it is not "designed" to be on 24x7. Server class means on
24x7. Desktop means on 9 to 5. Laptop means on when you are using it.


Are saying that computer manufacturers expect the users of their hardware to
turn it off each and every time they leave their computer? If so, that
alone is a major design fault which makes the claim even more valid.

When the lawsuit is served they are going to say that the produce
periodic use equipment, laptops and desktops, and continuous use
equipment, servers.

It has nothing to do with design faults it has to do with product liability.

Well, interesting week...
 

D.Duck wrote:
"BAR" wrote in message
. ..
JimH wrote:
"BAR" wrote in message
. ..
JimH wrote:
wrote in message
oups.com...
On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

oups.com...





On Feb 2, 7:42 am, "JimH" wrote:
wrote in message
ups.com...
1 - Computer caught fire.
2 - Office smoke damage.
That sucks! Some here will blame it on bad karma. ;-)
Was it the power supply catching fire?
I guess - that's what the Fire Marshall said. Kind of a thermal
runaway.
How old was it?
Three years.

Are you going to notify the manufacturer of the computer and/or power
supply? It is useful information for them and may lead to a recall.

I would also pursue a claim against them to recover damages from the
fire. This failure and resulting fire is certainly not to be expected
as the power supply was certainly well within it's expected useful
life.
The first question they will ask is if you turned it off before you left
the room. If it isn't a server class system it is not "intended" to be
turned on all of the time.


Wrong. Computers are made to be kept on 24x7. Why do you think they
have "sleep modes" on computers and monitors?
Regardless of whether it has a sleep mode or not unless it is a server
class system it is not "designed" to be on 24x7. Server class means on
24x7. Desktop means on 9 to 5. Laptop means on when you are using it.

What make a PC a "server class" system?

Twice the price.

Well, interesting week...
 

D.Duck wrote:
"BAR" wrote in message
. ..
JimH wrote:
"BAR" wrote in message
. ..
JimH wrote:
wrote in message
oups.com...
On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

oups.com...





On Feb 2, 7:42 am, "JimH" wrote:
wrote in message
ups.com...
1 - Computer caught fire.
2 - Office smoke damage.
That sucks! Some here will blame it on bad karma. ;-)
Was it the power supply catching fire?
I guess - that's what the Fire Marshall said. Kind of a thermal
runaway.
How old was it?
Three years.

Are you going to notify the manufacturer of the computer and/or power
supply? It is useful information for them and may lead to a recall.

I would also pursue a claim against them to recover damages from the
fire. This failure and resulting fire is certainly not to be expected
as the power supply was certainly well within it's expected useful
life.
The first question they will ask is if you turned it off before you left
the room. If it isn't a server class system it is not "intended" to be
turned on all of the time.


Wrong. Computers are made to be kept on 24x7. Why do you think they
have "sleep modes" on computers and monitors?
Regardless of whether it has a sleep mode or not unless it is a server
class system it is not "designed" to be on 24x7. Server class means on
24x7. Desktop means on 9 to 5. Laptop means on when you are using it.

What make a PC a "server class" system?

Twice the price.