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?

On Feb 3, 8:07 am, "Chuck Gould" wrote:
On Feb 2, 5:25?pm, wrote:

On Feb 2, 12:45 pm, "Mike" wrote:

ROFLOL! The way this guy just showed up and started popping off to anyone he
could, ?seemed strange. Now it makes sense, and is actually kind of funny.

It could have been real fun - we've had some real battles in the good
old
days - all very civil and all very nasthy. ?:)

Oh well, it seemed like a good idea at the time. ?:)

I think I'd disagree that trying to start flame wars, simply because
it might be fun, would be a good idea.

Of course you would - which is fine, but (and I mean no offense here
you must understand - just an opinion) you and others here lack a
certain sense of "whimsy" if you will. Flame wars can be fun and
if the participants keep it civil, it's much like having a "snap"
contest.

On the other hand, all here are good people even if a little odd from
time to time so it's a wash in the end. :)

On Feb 3, 8:11 am, "JimH" wrote:
wrote in message

oups.com...





On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

groups.com...

On Feb 2, 7:42 am, "JimH" wrote:
wrote in message

roups.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.

Yes I have and they have requested the power supply back for
examination.

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.

Nah - stuff happens you know?

I'm not the sue type - it really serves no purpose.

wrote in message
ups.com...
On Feb 3, 8:11 am, "JimH" wrote:
wrote in message

oups.com...





On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

groups.com...

On Feb 2, 7:42 am, "JimH" wrote:
wrote in message

roups.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.

Yes I have and they have requested the power supply back for
examination.

Good.


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.

Nah - stuff happens you know?

I'm not the sue type - it really serves no purpose.


Suing is one thing.............making an insurance claim to 'make right' is
another and there is nothing wrong with it, especially when the product
failed with potential catastrophic consequences.

But glad to see things are back to normal.

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.

On Feb 3, 3:01 pm, BAR wrote:
JimH wrote:
wrote in message
roups.com...
On Feb 2, 7:52 am, "JimH" wrote:
wrote in message

egroups.com...

On Feb 2, 7:42 am, "JimH" wrote:
wrote in message
legroups.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.

They were very cooperative.

For the record, I still have the owner's manual and there isn't a
statement
anywhere in the manual that states that the computer cannot be left on
24/7.

On Feb 3, 5:05?pm, wrote:
Nah - stuff happens you know?

I'm not the sue type - it really serves no purpose

Good reading for the can:

http://www.snopes.com/legal/lawsuits.asp

http://www.cjac.org/publications/new...es/120899.html

What make a PC a "server class" system?

You see, that's the real question, which refutes BAR's statement. I have a
P-3 500mhz system running Windows Server 2003, and it serves my son's
website, my business website, and the associated mail servers. It's been
doing that for 7 years. That's ALL it does. I would call that a "server
class" system, because the software was able to be installed on the
hardware, and the hardware runs it adequately. The computer itself is a
piece of junk by todays standards, but it is doing the job.

Now, if BAR's statement were correct, then Microsoft would have to make
sure that their server software could only be installed on a system designed
for 24/7 operation, not just any off the shelf computer. The fact is that
most (if not all) desktop systems are designed for 24/7 operation, and it's
simply a matter of choice as to whether or not you shut it off.

--Mike


"D.Duck" wrote in message
...

"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?

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

On Feb 3, 8:07 am, "Chuck Gould" wrote:
On Feb 2, 5:25?pm, wrote:

On Feb 2, 12:45 pm, "Mike" wrote:

ROFLOL! The way this guy just showed up and started popping off to anyone he
could, ?seemed strange. Now it makes sense, and is actually kind of funny.

It could have been real fun - we've had some real battles in the good
old
days - all very civil and all very nasthy. ?:)

Oh well, it seemed like a good idea at the time. ?:)

I think I'd disagree that trying to start flame wars, simply because
it might be fun, would be a good idea.

Of course you would - which is fine, but (and I mean no offense here
you must understand - just an opinion) you and others here lack a
certain sense of "whimsy" if you will. Flame wars can be fun and
if the participants keep it civil, it's much like having a "snap"
contest.

On the other hand, all here are good people even if a little odd from
time to time so it's a wash in the end. :)

Key words - "...keep it civil..."


--
***** Have a super day! *****

John H

"Mike" wrote in message
et...
What make a PC a "server class" system?

You see, that's the real question, which refutes BAR's statement. I have a
P-3 500mhz system running Windows Server 2003, and it serves my son's
website, my business website, and the associated mail servers. It's been
doing that for 7 years. That's ALL it does. I would call that a "server
class" system, because the software was able to be installed on the
hardware, and the hardware runs it adequately. The computer itself is a
piece of junk by todays standards, but it is doing the job.

Now, if BAR's statement were correct, then Microsoft would have to make
sure that their server software could only be installed on a system
designed for 24/7 operation, not just any off the shelf computer. The fact
is that most (if not all) desktop systems are designed for 24/7 operation,
and it's simply a matter of choice as to whether or not you shut it off.

--Mike

Exactly....

"D.Duck" wrote in message
...

"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?