[plug] Help overclocking celeron 300A required

[Bill G. Gruff]

On Tue, 30 Mar 1999 david.buddrige at mitswa.com.au wrote:
> I've no problem with non-computer-people per-se... but it's a falacy to say
> u don't need to understand computers to make 'em work properly  (u at leas
> gotta know what those icon's you're pointing and clicking on actually 
> mean... ;-)
Anyone can understand an icon, but text interfaces are just designed to
make it impossible for us people without a computer science degree to use
a computer. Apart from that, they're useless, which is why Windows will
always be the best operating system.
I don't know anything about computers, but I am still a very good Access
programmer. Is anyone on the list looking for a Access expert?

> > I can do very complex things in windows. You can do almost anything with
> > Visual Basic, and you don't even have to know anything abot programming.
> Read "The dumbing down of programming"... it's an article u should find if
> you search on those words at most web-search-engines... it's a fallacy u can
> program (anyting other than the _very_ simple applications) without knowing
> what you're doing.
The woman who wrote that article was just trying to show off cause she'd
cracked your codes and was let into your childish Unix clique.
I don't have to know anything about programming or computers because
Microsoft knows everything about them and their software can do it all for
me.

> > > Point 2: I've never found Windows help-systems useful. 
> > But it's so easy, you just point and click and it will tell you about all
> > of the cool features of the program. 
> Which don't work properly, and have no way of fixing them.
Better a feature that doesn't work than no feature at all.
For instance, most Unix editors don't even have a built-in spellcheck.
They have to call another program to do it, and of course then your
computer will be slow because it is trying to run two programs at once.

> For whch I can write a GUI front-end (if I want to), to take the messy
> command-line out of my life,
So you admit GUI frontends are the superior system? I told you so.
And anyway, you'd have to use Visual Basic to write the frontend, and
Linux doesn't run Visual Basic properly.

> > Yeah, Windows is so easy to use it probably puts tech-support people out
> > of jobs. They must hate it.
> Actually, this is not the case  -- you need to do sooooo much work to keep a
> windows machine alive and well...
Only because Microsoft come up with improved versions of their software so
frequently. Linux is only up to version 2, and if you remember how bad
Windows 2 was, you'll know what I mean.

> (I've worked as an NT administrator for two years before I met Linux 
> - it was love at first sight!!! At last, a system that _works_.... 
If I'd spent all that time to work out your stupid text commands and
out-of-date interface, I'd be so embarrassed I'd have to claim i like it,
too.

> My first experience was setting up a 486-DX-2 running at 66Mhz (with 32mb
> RAM) Proxy server that blew away a Pentium 150 with 80MB running 
> NT + MS-proxy... after that, I was hooked... 8-) 
You should upgrade to the latest versin of NT. It would be much faster.

> BTW, In the time after this, I had _no_ significant troubles with this proxy
How could you have problems with a machine if you can't even make it do
anything in the first place?

> - indeed many of the subsequent fixes for the exchange server (Pentum 200 with
> 80Mb RAM) at that site involved diverting the work to the linux box.... 
I bet you just wanted to be the only person who could fix it when things
broke so you would have better job security.

> it never "yawn" hickuped... and I just loved to log in every morning to
> the Linux box just to gloat over the uptime variable which grew and grew
> day by day... 
That's nothing. I've had an NT box that ran 12 hours a day for 3 months
without crashing.

> (OTOH, the highly paid NT consultants we hired to try and get the
> Exchange box to work properly suggested rebooting every week or so
> _even_if_nothing_had_broken_  just to be safe.... (ie. better to schedule a
> reboot than have it happen when u don't want it too)...
Of course it is. Your system needs to go through checks every now and then
to make sure everything's right. That's why you need scheduled reboots, so
you can make sure it happens regularly.
I would have thought someone in your profession would know that.

> Linux lets me get a life outside of tech-support... 8-)
Yeah, your life is going to Linux meetings and talking to other no-lifers
about Linux 'cos you've spent so long figuring it out you've forgotten
what the rest of life is about.

-Bill G. Gruff <Thought.Assassin at hotmail.com>