Newsgroups: rec.autos.simulators
Path: news.jprc.com!dca1-feed2.news.digex.net!digex!btnet-peer!btnet!news.netkonect.net!peer.news.nildram.co.uk!peernews.cix.co.uk!cix.compulink.co.uk!usenet
From: pjgtech@cix.compulink.co.uk ("Peter Gagg")
Subject: Re: VROC: Suddenly Can't Connect!
Message-ID: <F2xDz0.FCK@cix.compulink.co.uk>
Organization: n/a
References: <3657604E.3B251046@worldnet.att.net>
Date: Tue, 24 Nov 1998 12:13:47 GMT
X-News-Software: Ameol - PC Zone
X-Url: http://www.ameol.com
Lines: 38
Xref: news.jprc.com rec.autos.simulators:59608

In article <3657604E.3B251046@worldnet.att.net>, 
bertrh@worldnet.att.net (Bertram Hoenigmann) wrote:

> Although I've joined a few races in the past week, I suddenly can't
> connect to VROC.
> 
> When I click on a race to join, I get one of the two foloowing 
> messages:
> 
> a) the race is no longer available, or
> b) "Address Book Backup Exists -- See Help File" or something to 
> that
> effect.

Easy peasy, I don't know the technicalities behind it, but....

When you use vroc and connect to a gpl race it puts a file in your 
gpl directory listing the ip addresses you have connected to. When 
you disconnect it deletes this file. If you get a hanged gpl on-line 
race and you have to reboot, or otherwise restart your pc, the file 
is *not* deleted and left on your system. The next time you start a 
vroc race, it sees this file and refuses to make the connection.

All you have to do is go to your gpl directory and delete the 
address.vro file (do *not* delete the address.ini file) you should 
then be able to connect ok.

If you suffer any future disconnections from a vroc gpl race, you 
should first go to your gpl directory and delete any address.vro 
files, before trying to reconnect to vroc races, or it will just 
throw you out again. 

8-)

BTW, there is a faq about this very issue somewhere on the 
vroc/Alison's site?

*Peter*   #:-)
