> > First, I suppose you posted this message from a month in the future. So I guess I should have waited a month before I replied... It's March, y'know. :-p
> >

*Thwack* yeah, your right. Oops. Well, I'll just pretend to overlook that detail right now....and change my computer clock so that it's right. (I change my computer clock quite often. Get the most out of 30 day trials, you know.)

> > Anyway, what OS do you use? The only place I remember seeing an error like that is, oddly enough, on a Macintosh... And I'm quite a computer geek, too (and primarily a PC user), so I've been asked about all sorts of problems. But I think I've seen an error like that only once, and it was only temporary at that...
> >
> > Anyone else got more of a clue than I do?
> >
> > -- codeman"stump the computer geek"38
>

I'm running a strange version of Windows 98 on a Packard Bell (Bleh) computer. By 'strange' I mean that it was the one that come with the computer, that included not only windows put countless other Packard Bell 'nessesities' which I neight want nor like. Well, I'll assume that it's Win98 becasue that's what the splash screen says, as well as windows help/about section.

> I'd suggest using a search engine. Using NS Search, I found about 302 pages, but I don't know enough of the particulars.
>
> Nyperold
> 28 Adar 5760

Ok, I'll go through those. With a little skill and a lot of luck, maybe I can get my computer fully functional again. (Did I mention that this is my 3rd time writing tis paticular post due to 'socket notification errors'?)

-Ka"I'll see what I can do...."z!