From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: unbootable HD, the solution
Date: Wed, 29 Jan 2003 14:47:48 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0301291447130.3431-100000@igueths> (raw)
In-Reply-To: <5.1.0.14.2.20030129122304.02463ba0@198.144.194.210>
I'll have to agree with you on that one. Remember I was one of the
subscribers? And yes I was the one playing Tradewars and Terra Firma.
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
On Wed, 29 Jan 2003, Charles Crawford wrote:
> Heh. I used to be the sysop for the MCB BBS fpr almost 9 years. PCBOARD
> with up to ten users. Those were the days. I miss them.
>
> -- charlie Crawford.
> At 06:29 AM 1/29/03 -0500, you wrote:
> >Of course I remember most of those pkgs... I've been running a bbs for
> >over a year now.
> >
> >--
> >A message from the system administrator: "I've upped my priority, now up
> >yours!"
> >On Tue, 28 Jan 2003, Scott Howell wrote:
> >
> > > Ah, this reminds me of a very interesting problem I ran into.
> > > Mind you this is from the days when most chips were socketed and
> > > actually cost some money. Yes, this was an old 386-SX 25 I was running
> > > my bbs and Fidonet mail service on.
> > > I bet some of you remember Fidonet, BinkleyTerm, node lists, RBBS,
> > > Maximus, Opus, and so on. Hell does anyone remember bonk and the node
> > > list mungers?
> > > In any case this old 386 was crankin' for its time, but it had one
> > > incredibly odd problem. You could put a floppy in, read, copy from it,
> > > and all that no problem. If you attempted to write to it the trouble
> > > would start. Files on the disk would disappear or the disk would just
> > > turn out trashed. Months went by with every possible diagnostic trick
> > > done and never did find the problem. I ended up deciding it was the DMA
> > > chip on the board, but never got a chance to replace it. Ended up
> > > tossing the board or giving it away I can't remember, but upgraded to a
> > > screamming 386-DX 33.
> > > And to think I ran that bbs on an AST 286 with 130Mb hd and that was
> > > considered one of the largest bbs systems in the area. Oh yes screamming
> > > along at 9600 baud.<grin>
> > > I've not heard a story yet that has surprised me about hardware
> > > failures. I can remember when failures were common whereas now they are
> > > rear.
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Igor Gueths
` Chuck Hallenbeck
` Scott Howell
` Janina Sajka
` Shaun Oliver
` Scott Howell
` Adam Myrow
` Scott Howell
` monte single
` Scott Howell
` Alex Snow
` Alex Snow
` Charles Crawford
` Igor Gueths [this message]
` Jude DaShiell
igueths
` Jude DaShiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0301291447130.3431-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).