Sorry, Cider. Other than not having .NET Framework 3.5 installed, that's the only time I've had the same problem.
On 9/14/11, Cider Jack <[email protected]> wrote: > Hi Sarge, > Looked in seven .ini files and couldn't find 'SYSTEMIP' anywhere, and > all IP addresses I did find were already pointing to 127.0.0.1. If I > misunderstood and 'SYSTEMIP' was used as a placeholder in this > context, I still didn't see any IP addresses that weren't pointing > home. > ~!CJ > > On 9/13/11, Sarge Misfit <[email protected]> wrote: >> Make absolutely sure that all of the IP addresses in the relevant .ini >> are 127.0.0.1. If you leave them saying SYSTEMIP, it looks for the >> default that is used to connect to a network. >> >> On 9/11/11, Cider Jack <[email protected]> wrote: >>> That's actually a very plausible explanation. Probably if that step >>> were placed a bit later in the connection process would fix it. That >>> is, check to see which grid the viewer is pointing to before sending >>> the ping, and then only send that ping if it's aimed at SL. Sounds >>> like a basic if-then statement might solve it, but then I'm no >>> programmer! Who knows, LL might even appreciate recovering the >>> bandwidth that must burn. Although, it does allow them to keep an eye >>> on their competition... >>> >>> ~!CJ >>> >>> On 9/12/11, Mimetic Core <[email protected]> wrote: >>>> That's a strange one. I'm by no means familiar with that aspect of the >>>> viewer code, but my best guess would be that since Imp is a hybrid >>>> viewer >>>> it needs to stop and send out that precious ping before it moves on to >>>> the >>>> final connection phase - regardless of which grid you're headed for - to >>>> maintain Linden's seal of approval. If a particular viewer was geared >>>> ONLY for OpenSim grids it probably wouldn't need this extra procedure. >>>> I'm sure someone here can give you a definite answer. >>>> >>>> -core >>>> >>>> On Sun, 11 Sep 2011 22:04:01 -0500, Cider Jack <[email protected]> >>>> wrote: >>>> >>>>> IThe question I've seen asked on on this list before, but searching >>>>> through archives I'm not finding it. It regards SoaS, and how to use >>>>> it on a computer that isn't online. It seems to need an active network >>>>> connection to be able to log in. So what do I need to change to be >>>>> able to use SoaS when not connected to the network? It was a really >>>>> simple fix, if I recall. >>>>> >>>>> Something related to share that the tin-foil-hatters among us may find >>>>> curious (if it's not already common knowledge and I'm just living >>>>> under a rock). I recently installed PeerBlock (formerly PeerGuardian) >>>>> to supplement my firewall. When connecting to OpenSim grids (including >>>>> SoaS), it seems Imprudence sends an outbound HTTP connection to Linden >>>>> Lab and won't allow login to any grid as long as that connection is >>>>> blocked. I haven't tried this with any other TPVs. It's difficult to >>>>> imagine any reason for LL to be notified anytime someone logs onto an >>>>> OS grid with a TPV. Probably just totally benign left-over code from >>>>> the original SL viewer that nobody's gotten around to removing, would >>>>> be my guess. Anyway, that's actually what sparked the fruitless >>>>> archive dig and the subsequent question above! >>>>> >>>>> Cheers, >>>>> ~!CJ >>> _______________________________________________ >>> Opensim-users mailing list >>> [email protected] >>> https://lists.berlios.de/mailman/listinfo/opensim-users >>> >> _______________________________________________ >> Opensim-users mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/opensim-users >> > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > _______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
