rec.autos.simulators

Can anyone at Papyrus explain what the "Remote not available (timed
out)" error (ie., when I switch to Nascar) means?

To me this seems like a severe error, the kind of thing that might
happen if one of the computers in a modem race crashed; the error
seems to imply there's no communications happening at all.

I don't understand how this can happen in the context of a
multi-player Hawaii race, since Nascar is not initiating the modem
communication, eterm is. And eterm communications works fine.

Between Hawaii_Help and every hint on this forum I've tried everything
I can think of. Hawaii is installed in the Nascar directory. I've
tried it at both 9600 and 19200 baud, setting this both in the modem
init string and the eterm comm rate, and I've tried all the init
strings for turning off compression, error correction, variable
connect rate, etc. I've tried the exact init strings other USR 28.8
Sportster users are using successfully.

It just don't wanna go. Any suggestions or ideas would be much
appreciated.

Joe

We pump data bidirectionally at pretty close to 9600 BPS, and with error
correction disabled, it requires a very clean phone line to establish a
good connection.  My guess is the long distance link you're trying to
establish with Boston from BC isn't up to the task.  I'd like to be able to
give you a better software diagnostic than that, but as a practical matter,
I suspect you wouldn't be able to get any further if the message were more
specific.

Have you been able to establish a two-player modem connection with anyone
else?  It might be easier for you to work out your modem connection head to
head rather than through Hawaii.  You can also contact

Charlie Heath
Papyrus Design Group

Maybe so, but I hate to be guessing when the problem is severe enough
to prevent a customer from accessing the system. And for the problem
you've described wouldn't I expect a "Slow latency" error? Unless the
latency was so bad (like > 5 seconds) that it thinks there's no
connection - but I can see in eterm that it's no where near this bad,
when I make a keyboard selection the eterm server responds almost
instantly.

No, I'll see if I can find someone locally to try it. There's a local
BBS where a bunch of racing fans hang out.

Looks like my Nascar racing days are coming to a premature end. I
guess I'm back to reading threads about slippng FGPII release dates
for e***ment. :-(

Joe

        Wish,I could help you! Hope you get it figured out!

        Pete

But the interesting thing was the download itself. I was able to
easily sustain over 1000 CPS (at 19200) baud. What's more, the latency
rate is clearly not a problem - I can see how fast the packets are
arriving because of the numbers on the screen (i.e., X of X bytes).
Mostly they were updating too fast too read. If I had to guess I'd
estimate the latency at no more than 0.1 seconds.

So what is it that's different about Nascar (as opposed to eterm)
communications? Why would it work fine in eterm, but not at all when
it switches to Nascar?

Joe