Just wanted to let everyone know in case they ever have to deal with this obnoxious bug that I found the solution on MS's support website. I did a search on the error code and got back two articles, the first of which detailed a procedure for fixing the problem, which had something to do with WinSock 2.0. I guess the lesson to be learned here is that, to their credit, what MS lacks in obvious documentation they make up for on their website at least. Sorry for the off-topic crap. Sellam Alternate e-mail: dastar(a)siconic.com ------------------------------------------------------------------------------ Don't rub the lamp if you don't want the genie to come out. Coming this October 2-3: Vintage Computer Festival 3.0! See http://www.vintage.org/vcf for details! [Last web site update: 05/25/99]