Steve,
Sorry that you are giving up (temporarily) accessing the web thru
Compuserve. If you want to invest a few dollars in a toll call, I know that
Compuserve's Tucson access number (520-571-0207) works. I also know that one
of the San Diego access numbers also works as when I was in San Diego about 6
months ago, I used it. (I didn't try the other number, and I forget which
number I used.)
About a year and a half ago, Compuserve *did* implement an spam-guard, but
AFAIK, it didn't affect internet access. Some months before it was
implemented, I started having problems getting e-mail messages from a list
service that I subscribed to. I sent a message to Compuserve's support
asking if they were testing a spam blocker and they said (of course), No.
Then they sent out a message to their subscribers describing their spam
blocker and what to do to disable it. I have it disabled, and any spam that
I receive, I forward to Compuserve Support reporting it as unwanted spam.
Compuserve Support has been revamped and now has three different e-mail
addresses.
Remind me again about what happens when you "almost" get connected to the web
thru Compuserve. Do you have Arachne's home page start downloading, or do
you start loading Compuserve's first screen? Do you get/see any error
messages? Have you checked Compuserve for the phone number for the area code
you are calling from?
Roger Turk
Tucson, Arizona
Steve Evans wrote:
>>Sergei and all others,
I have given up on ISPs Freewwweb or Compuserve working in Los Angeles area
via Arachne for now. I got internet access from our local phone company,
Pacific Bell. They don't use the UUNET lines, so Arachne works beautifully.
I tried installing version 1.60b, but ran into memory problems (running a
small home network), so I went back to version 1.50src.
[Incidentally, are there known problems with version 1.60's setup wizard? I
couldn't even get past the video screen --always tabbed past the the
settings I wanted and then went nowhere when I ENTERed. Hit "O" for Options
and proceeded to act just as crazy on other setup screens.]
I don't know what Compuserve's problem was, but Freewwweb's use of UUNET
local access nodes (I understand that many ISPs use UUNET) is somehow
involved in tripping up Arachne within metro LA. Again, I was able to surf
with Arachne just fine on Freewwweb using an access number outside of my
area, also a UUNET node (per TRACERT) but obviously something different. Is
it possible that access nodes in Los Angeles have extra security or spam
blocking agents? Else it must be some variation in protocol or redirection
that standard browsers (IE/Netscape) are able to negotiate, yet Arachne
cannot. If Arachne is destined to fly in any metropolitan area like Los
Angeles, seems like a question worth pursuing. But I'm afraid I can't
spend any more time on it. On to other puzzles . . .
Thanks again everyone for your attention and creativity and patience.
Steve Evans<<
