15 Apr
1999
15 Apr
'99
2:58 p.m.
Personally, I tend to draw the line at the 386. In a
Windows and GUI world,
I really don't want the aggravation to trying to teach someone text mode
apps or of having to listen when they can't find *any* software. This is
the same reason I will never give another person an Apple II unless they
already know about and want one.
OTOH, most 386 class sytems can share enough hardware and software with
later brethren that the issue is more one of speed.
Of course, I'm also a person who's been known to travel with a 386SX-16
notebook (recently replaced with a 386SLC-25 one).
The key to old systems is that the combustable mixture for them to run,
knowledgable help, manuals, software, hardware, etc., can't be missing any
of the critical parts. With newer systems its reasonable to expect a person
to have some support outside of yourself, radio shack has a cable, neighbor
kid can reinstall Windows, etc. With an older system the first link that
breaks and you are generally sunk. Radio Shack may have the blinkity cable,
but the saleguy will not know it and tell them its too old just replace it.
A couple local guys do nothing but cheap 386 systems, and they succeed
because they offer support, and a very complete install of software. To do
that you need to spend a fair amount of time getting a procedure and
software all ready to quickly put on to new systems. If these two guys
didn't do it, it would be straight to the dumpster. It only "works" though
when you have a pretty good tech, like they are, willing to work very very
cheap.