Re: what is the //gs?

[phoenyx <quazar@dcnet2000.com>]

Frank Carney wrote:

> >That was not my point. I use PC's too. The point I was trying to make
> >was the methods used by the industry giants to dupe the PC users to
> >beta test products and pay for the privilege.
>
> Honestly, I don't understand, please explain.
>

As the buying public, we purchase software and hardware which has
very little if any testing done. Our purchases serves two purposes. We
beta test products for companies as well as fund new projects which
make our current systems obsolete. Thus the cycle continues.


>
> >By the way, over clocking cpu's has been around for quite awhile. It
>
> I know, I was just proud that I could get the bus speed to 66 Mhz.  As
> for reliability,
> lets just say I have not run it for very long.
>
> >the manufacturers tested speeds. Higher speeds can cause data
> >loss, system instability as well as premature system failure.
>
> Yes, but who cares with a 486.  I can replace the chip for $10.  As for
> data loss, really
> only if it crashes while I am doing something.  Chances are it will not
> effect stuff on the
> hard drive.

Lot's of luck on the over clocking. I have had success and failure with
this. For instance, I have a Celeron 350 which will overclock up to
450 for about an hour. The hardware reports 450 but the OS I use
(Linux) reports the actual CPU speed at 383 mhz. After about an
hour the system gets stupid. I always have better luck with the older
cpu's. Simply because it either works at the new speed or it fails
right away. I got rid of all my older hardware, but I gave my daughter
a 486 133 running at 160 with an extra fan to keep things cool. It's
been going strong for about a year now. Of course it's an AMD, a
much better cpu, IMHO.

Actually it can affect data to the drives and you may not know
until you need that data again.

Phoenyx