Hello Sean,

Tuesday June 14 2005 10:41, you mumbled this to me:

 SD> I promise, this one will be short. 

You broke your promise. :)

My idea of short is between these
____________________________________________________________________________




____________________________________________________________________________

two lines. :) And that includes room for an answer/reply. ;)

 SD> Okay, thanks.  About losing the code: I understand.  I think I've lost
 SD> the source code to my own doors about three times (one of them I
 SD> completely rewrote and then, somehow, completely lost the source
 SD> again... ).

:)

 SD> No rush on that.

Good. ;)

 SD> Right now, just trying to get everything in order for my move.

Moving out of MiL's place?

 SG>> It may be incorrectly described in the help/docs but I *think* it
 SG>> is now - and not /. It's been a while since
 SG>> I've done anything to ETI as I lost the code I was working on -
 SG>> HD went south on me.

 SD> Let's see ... *jumps to a DOS window*

 SD> Yep, that's the ticket.  It's - instead of /.  Okay, well, that
 SD> mystery is solved.

Good.

 SG>> I've recently found a replacement drive and with a bit of luck, I
 SG>> will be able to retrieve the code off the old drive. Failing
 SG>> that, I still have an (much) older backup that I can try to bring
 SG>> up to date if I can remember how I did it all. :)

 SD> Heh, been there, done that.  I'm working on starting to save for a
 SD> brand new Certance (Seagate) DDS-3 12/24GB DAT tape drive ($379 for
 SD> the drive, but the tapes are CHEAP-$5 or less a piece).  I'm going to
 SD> make damn sure I start to back up EVERYTHING.  I don't want to lose my
 SD> stuff again (that includes the BBS!).

I'm currently using rewritable CDs to store my *important* stuff.

 SG>> Definately. ;)

 SD> When I worked as phone tech support for Sears, we had the ID-10-T and
 SD> the PEBKAC errors (Problem Exists Between Keyboard And Chair).  One
 SD> tech would actually tell people, "Sir/Ma'am, that's a PEBKAC error.
 SD> Those are difficult errors to fix, but we'll try to fix it."  What the
 SD> bad part was that the rest of us (there were four techs to a cubicle
 SD> and our mikes were so sensitive on the phones that we couldn't laugh
 SD> or other customers would hear us) had to sign off the phone, run to
 SD> the bathroom and laugh until we cried when he used it.  He was a brave
 SD> one. 

Hahahahaha...

 SG>> Worked both ways for me but yet to be confirmed.
 SG>> Plenty, but none as far as the above problem is concerned. The
 SG>> cmd line looks to be correct. I can't see anything in the message
 SG>> area options that would prevent it. 1:1/21 is a valid
 SG>> (nodelisted) address?

 SD> Yes, it is a valid nodelist address (it's the Elist bot address)... I
 SD> do have EZYNODE and all of my nodelists set up and compiled.

 SD> Here's what BONK says about that address:

 SD> S)ystem Title: THE INTERNATIONAL ECHOLIST
 SD> O)perator....: ECHOLIST
 SD> ÀÄindex key..: Echolist
 SD> G)eneral Info: SOUTH BAWLAMER MD
 SD> T)elephone...: 1-443-919-9251

 SD> (That's South Baltimore for non-locals. ;)

Yep, I checked it using T-Node (Terminate util).

 SG>> Is he having the same problem when testing it?

 SD> I don't know if he is or not.

Ok.

 SD> BTW, no netmails yet.

I'm checking on them... they definately left here.

Cheers,
      Stephen

--- GoldED+/W32 1.1.5-30413 - Ezycom Development Team.