Last night I posted that VROC was not working for me.
I discovered later that the vroc.ini file had reverted back to the old site
address. Not only that, but the same had happened on my host network
computer.
1. I had not once opened the VROC dir nor changed anything since installing
2. No other person has access to these computers
The only thing I had done between VROC working and not was to download,
install and play N4.
This is pretty weird, huh?
Alan
"Alan Coates" <[email hidden]> wrote:
What are the proper settings in the ini file?
I have:
[VROC]
Address=vroc.ods.org
I ask because I cannot get VROC to log in for server info, either.
Chat works, but no server log in. I d/l N4 demo, too, but have not
installed it yet.
Just tried again and still unable to connect to server, except for chat.
Quoted text (11 lines)
> Last night I posted that VROC was not working for me. > > I discovered later that the vroc.ini file had reverted back to the old > site address. Not only that, but the same had happened on my host > network computer. > > 1. I had not once opened the VROC dir nor changed anything since > installing 2. No other person has access to these computers > > The only thing I had done between VROC working and not was to > download, install and play N4.[email hidden] wrote:
Just checked further into documentation and found the setting should be:
[VROC]
Address=209.53.20.177
What is really odd is that this is what the setting used to be!
I remember going through this when installing VROC a few months ago.
Somehow in the last 24 hours this got changed, though the file date/time
show 9/13/00 - yet somehow the data changed. Very, very strange.
Quoted text (8 lines)
>> The only thing I had done between VROC working and not was to >> download, install and play N4. > > What are the proper settings in the ini file? > I have: > > [VROC] > Address=vroc.ods.orgHmmm. I haven't been able to log into WVROC today either. I tried changing
the address in my ini file from vroc.ods.org to the 209.53.20.177 address,
and now it works again. I've never looked at it before, so I'm not sure what
the setting was before.
Worked Wed. evening, and I haven't changed anything. I haven't downloaded
N4.
Kevin Caldwell
Calgary, Canada
<[email hidden]> wrote in message
news:[email hidden]...
Quoted text (21 lines)
> [email hidden] wrote: > > >> The only thing I had done between VROC working and not was to > >> download, install and play N4. > > > > What are the proper settings in the ini file? > > I have: > > > > [VROC] > > Address=vroc.ods.org > > Just checked further into documentation and found the setting should be: > > [VROC] > Address=209.53.20.177 > > What is really odd is that this is what the setting used to be! > I remember going through this when installing VROC a few months ago. > Somehow in the last 24 hours this got changed, though the file date/time > show 9/13/00 - yet somehow the data changed. Very, very strange. >Same thing here. I haven't been able to connect for severral days. The
only answer seems to be that the WinVROC app changed the ini file.
Switched it to the "fixed" address and it connected right away.
As added protection, I've made the ini read-only.
SB.
--
---------------
return e-mail address invalid
reply to me in the newsgroup
---------------
"Alan Coates" <[email hidden]> wrote in message
news:QabW5.1221$[email hidden]...
> Last night I posted that VROC was not working for me.
>
> I discovered later that the vroc.ini file had reverted back to the old
site
> address. Not only that, but the same had happened on my host network
> computer.
>
IIRC there was a similar case of WinVROC "resetting" reported here quite a
while back. I didn't follow the thread, but if you can work Deja news (I
can't make sense of it) you might be able to find it.
BTW, Kevin: I highly recommend downloading the demo. Even though I can't get
it to work properly on my "outdated" sound/3D setup, it's convinced me. The
feel is just so familiar, yet ever so subtlely tweaked and adapted. Another
true masterpiece IMNSHO.
Jan.
=---
Kevin wrote...
Quoted text (11 lines)
> Hmmm. I haven't been able to log into WVROC today either. > I tried changing the address in my ini file from vroc.ods.org > to the 209.53.20.177 address, and now it works again. I've > never looked at it before, so I'm not sure what the setting > was before. > > Worked Wed. evening, and I haven't changed anything. I haven't > downloaded N4. > > Kevin Caldwell > Calgary, CanadaIn article <_vgW5.32412$[email hidden]>, "Kevin"
<[email hidden]> writes:
>Hmmm. I haven't been able to log into WVROC today either. I tried changing
>the address in my ini file from vroc.ods.org to the 209.53.20.177 address,
>and now it works again. I've never looked at it before, so I'm not sure what
>the setting was before.
That's weird. One out of my three systems at work stopped working Friday, and
I didn't know why. They're all on the same hub, so they should have all been
affected by 'whatever'....<shrug>
Eldred
--
Tiger Stadium R.I.P. 1912-1999
Homepage - http://www.umich.edu/~epickett
GPL hcp. +44.17
Never argue with an idiot. He brings you down to his level, then beats you
with experience...
Remove SPAM-OFF to reply.
Glad I'm not the only one to experience this problem
Alan
"EldredP" <[email hidden]> wrote in message
news:[email hidden]...
> In article <_vgW5.32412$[email hidden]>, "Kevin"
> <[email hidden]> writes:
>
> >Hmmm. I haven't been able to log into WVROC today either. I triedchanging
> >the address in my ini file from vroc.ods.org to the 209.53.20.177address,
> >and now it works again. I've never looked at it before, so I'm not surewhat
> >the setting was before.
>
> That's weird. One out of my three systems at work stopped working Friday,and
> I didn't know why. They're all on the same hub, so they should have allbeen
you
> with experience...
> Remove SPAM-OFF to reply.
Quoted text (9 lines)
> affected by 'whatever'....<shrug> > > Eldred > -- > Tiger Stadium R.I.P. 1912-1999 > Homepage - http://www.umich.edu/~epickett > GPL hcp. +44.17 > > Never argue with an idiot. He brings you down to his level, then beatsWonder if you could host N4 on VROC?
MM
Alan Coates wrote:
Quoted text (15 lines)
> Last night I posted that VROC was not working for me. > > I discovered later that the vroc.ini file had reverted back to the old site > address. Not only that, but the same had happened on my host network > computer. > > 1. I had not once opened the VROC dir nor changed anything since installing > 2. No other person has access to these computers > > The only thing I had done between VROC working and not was to download, > install and play N4. > > This is pretty weird, huh? > > AlanSounds like the name service that points the vroc domain name to the server ip
address is down. Or something like that.
This has happened before. This explains why changing the vroc.ini from the
domain name to the actual ip fixes the problem.
As I understand it, the reason a domain name has been used instead of the
actual ip address is so the vroc hosting could be changed (different ip) if
necessary and the name service would be changed to point to the new address
without everyone having to edit their .ini.
So much for good intentions. I should add the hosting of vroc has been superb
even though the guy doing it is no longer actively involved with gpl.
Thanks Chaz. You're a prince, even if you prefer the homicidal thrills of UT to
GPL these days. :-�
Marty
Alan Coates wrote:
Quoted text (15 lines)
> Last night I posted that VROC was not working for me. > > I discovered later that the vroc.ini file had reverted back to the old site > address. Not only that, but the same had happened on my host network > computer. > > 1. I had not once opened the VROC dir nor changed anything since installing > 2. No other person has access to these computers > > The only thing I had done between VROC working and not was to download, > install and play N4. > > This is pretty weird, huh? > > Alan
"Marty" <[email hidden]> wrote in message
news:[email hidden]...
> Thanks Chaz. You're a prince, even if you prefer the homicidal thrills ofUT to
> GPL these days. :-�
Ummm, and consequently, probably won't see this message??
:O)
Geordie


































