On Tue, 9 Oct 2001, Samuel W. Heywood wrote:
> I just tried to access the URL named below. What happened is
> that I got a 404 error which identified my browser, in this case
> Arachne 1.70, rev 3, my operating system (DOS), my ISP, and my IP,
> the resolution of my monitor, and the fact that I
On Tue, 09 Oct 2001 11:27:52 -0500 Samuel W. Heywood"
<[EMAIL PROTECTED]> wrote:
>Hello Arachnids:
>I just tried to access the URL named below. What happened is
>that I got a 404 error which identified my browser, in this case
>Arachne 1.70, rev 3, my operating system (DOS), my ISP, and my IP
On Tue, 09 Oct 2001 12:12:59 -0500, Samuel W. Heywood wrote:
> On Tue, 09 Oct 2001 11:27:52 -0500, I had written:
>> Hello Arachnids:
>> I just tried to access the URL named below. What happened is
>> that I got a 404 error which identified my browser, in this case
>> Arachne 1.70, rev 3, my o
Hi Sam and all,
On Tue, 09 Oct 2001 12:12:59 -0500, Samuel W. Heywood wrote:
> On Tue, 09 Oct 2001 11:27:52 -0500, I had written:
>> Hello Arachnids:
>> I just tried to access the URL named below. What happened is
>> that I got a 404 error which identified my browser, in this case
>> Arachne
On Tue, 09 Oct 2001 11:27:52 -0500, I had written:
> Hello Arachnids:
> I just tried to access the URL named below. What happened is
> that I got a 404 error which identified my browser, in this case
> Arachne 1.70, rev 3, my operating system (DOS), my ISP, and my IP,
> the resolution of my mon
Hello Arachnids:
I just tried to access the URL named below. What happened is
that I got a 404 error which identified my browser, in this case
Arachne 1.70, rev 3, my operating system (DOS), my ISP, and my IP,
the resolution of my monitor, and the fact that I had a WATTCP.CFG
configuration file,
