Rolig Loon

There is extreme danger for them. Once you can log in to their account, you will be able to empty their L$, transfer any transferable items from their inventory to yours, get all of their RL contact information, change their password to deny them access to the account, and do all sorts of illegal activities, for which THEY will be blamed. That was an incredibly stupid thing for the person to do. If you are a friend, the smartest thing you can do is to tell the person to change the password IMMEDIATELY and not let you or anyone else have it. Danger to you? Yes, of course. If things go wrong (they will, sooner or later), your friend can't blame you for messing up the account without implicating himself for giving you access. When he complains to Linden Lab to protect his stuff, though, you'll both go down. You're risking a friendship and access to SL for both of you.

Nvidia Video Driver Latest driver Last checked Feb 6th- Windows: 285.62 (Oct 24) beta: 295.51 (Jan 31) - Linux: 290.1 (Nov 22)ATI Video Driver Latest driver Last checked Feb 6th- Windows and Linux: 12.1 (Jan 25)Intel Video Driver Intel driver download page Intel does not have a universal driver set. Please go to Intel's site and select the appropriate download.

You can keep as many as 65 listeners open at once, but I have a hard time imagining a need to do more than a fraction of that. If you're hitting the limit, something isn't right. Do you perhaps have a llListen in a loop somewhere? Changing states will always close all listens, so that's one very sure way to avoid the problem. Using a timer is a good plan too, but you should also plan on other ways to kill a listen before the timer finally triggers. If you open a listener to start a dialog, for example, close it at the top of the listen event. BTW, people don't accumulate listeners. Scripts do.

If it works, it's coincidence. There's nothing about changing a viewer that will make a difference to your internet connection, which is the root of the bake fail problem.

Your guess is as good as anyone's. For a while last winter, it looked as if the Lindens were considering doing just that, but they have apparently backed off. In this Answers area, all we can do is provide advice about how Sl works (or why it doesn't). We have no insights into how the Lindens -- who never come here -- make corporate decisions. This area is not designed well for discussion anyway. If you'd like to debate this popular topic (again), you will probably find some enthusiasm over in the General Discussion forum. .

From the Terms Of Service (Sect 7.1), which you should read in full..... "You retain any and all Intellectual Property Rights you already hold under applicable law in Content you upload, publish, and submit to or through the Servers, Websites, and other areas of the Service, subject to the rights, licenses, and other terms of this Agreement, including any underlying rights of other users or Linden Lab in Content that you may use or modify. In connection with Content you upload, publish, or submit to any part of the Service, you affirm, represent, and warrant that you own or have all necessary Intellectual Property Rights, licenses, consents, and permissions to use and authorize Linden Lab and users of Second Life to use the Content in the manner contemplated by the Service and these Terms of Service. Because the law may or may not recognize certain Intellectual Property Rights in any particular Content, you should consult a lawyer if you want legal advice regarding your legal rights in a specific situation. You acknowledge and agree that you are responsible for knowing, protecting, and enforcing any Intellectual Property Rights you hold, and that Linden Lab cannot do so on your behalf." Whenever you create content in SL, you attach permissions which grant the next owner limited rights to copy, modify, or transfer the item they have acquired. Those permissions attach to the item itself. They do not constitute ceding your intellectual property rights to the concept on which the item is based. That is, you retain control over ownership to the creation even when you have sold a copy of it to someone else. Read about Permissions here >>> http://community.secondlife.com/t5/English-Knowledge-Base/Object-permissions/ta-p/700129 and learn more about intellectual property rights here >>> http://wiki.secondlife.com/wiki/Linden_Lab_Official:Intellectual_Property

You can ask the merchant who sold them to you, but don't expect miracles. Most merchants won't offer a refund unless there's something wrong with the item or there was a clear error in delivery. You're not likely to find many people who will take back something just because you don't want it any more. Sort of like RL, actually........... :smileywink:

Follow the advice that we gave the OP when this thread was started back in September 2011. We can't help much unless you give us more information to work with. Also, nobody is ever going to see your question if you tack it onto the and of someone else's VERY old thread. Start your own new one and tell us about your computer, your Internet connection, your viewer, and anything else that might give us a clue what's going on.

There's a bug, well-recognized by now, that makes it hard to rez objects in some Linden Homes >>> Problem of not being able to rez on my land continues . Essentially, the servers are having a hard time telling where the edges of your parcel are, so they assume incorrectly that you are trying to rez something on your neighbor's parcel. Until LL's developers find a way to repair the bug, the way to beat the problem is to rez stuff at the exact center of your parcel. Try rezzing a simple cube over and over and over and over again until you find a place where you can do it. You ought to be able to rez anything else at the same spot and then drag it to where you want it.

Often all that's wrong is that your locally cached copy of inventory is out of sync with LL's asset servers. The way to cure that is to go to Preferences >> Internet & Cache and click the Clear Cache button and then log out. Log back in at a nice quiet sim like Smith or Pooley and move away from the landing area so nobody lands on your head. Then open your inventory and type any letter at all in the search field to jump start a rebuild of your cached inventory. Go make a sandwich. It may take a while and you shouldn't do anything in SL until it finishes fetching the entire inventory. Most of the time, that clears up the problem, so you should find you missing stuff again. If not, see here for other suggestions >>> http://wiki.secondlife.com/wiki/Lost_inventory

Step #1: Don't go back there. There are plenty of other friendly spots. Step#2: The sandbox owner can ban or eject for for any reason whatsoever ... even a bogus one ... but that action only applies to his own sandbox, or at most the sim that it's on. So again... don't go back. Step #3: Relax. Even if the sandbox owner does report you to LL (which I doubt that he will), LL will not do anything at all with the AR unless there is solid evidence that you have violated the TOS. They certainly won't do anything without sending you a notice to let you know what they are doing.

You have found a well-known bug that is affecting many people in Linden Homes >>> Problem of not being able to rez on my land continues . The problem is that the servers are having a hard time telling where the edge of your parcel is, so they think you are trying to rez things on your neighbor's land. Until Linden Lab technicians find a cure, the best solution is to try rezzing items as close to the center of your home as you can. This may take some practice. Try rezzing a simple cube over and over and over and over again until you find a spot near the center of your home where it works. Then rez anything else at the same spot and drag it to where you want it.

Follow the link above

Your inventory icon looks like a suitcase (sort of). It's on your task bar. Start reading here >>> http://community.secondlife.com/t5/English-Knowledge-Base/Using-your-inventory/ta-p/1370823 Well, actually, if you don't know how to handle inventory, you probably missed learning some other things too, so start here >>> http://community.secondlife.com/t5/English-Knowledge-Base/Second-Life-Quickstart/ta-p/1087919 Welcome to Second Life, Heartman. :smileywink:

We are all SL residents like you. Therre are no Lindens here. Your viewer and SL's servers have temporarily lost the ability to talk to each other. Unless there's a problem with the servers (Always check http://status.secondlifegrid.net/ first), it's probably something on your end. If you are having a DNS problem, it is almost certainly for one of three reasons. ......... (1) Try shutting off your computer, unplugging the router and modem for a couple of minutes, and then plugging them back in and restarting. That simple step may clear up everything (2) Change your DNS settings from whatever your ISP assigns you as a default. Use Google's free public DNS servers instead. Here's how >>> http://code.google.com/speed/public-dns/ (3) If things are STILL messed up, contact your ISP. Maybe they are working on their Internet connections. Mine go down for about 20 minutes once a month or so while they are vacuuming dust out of their servers, or whatever they do.

Viewers play a minor part in voice functionality. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons: Your ISP is throttling or blocking the voice service; failure of the Vivox service; voice issues on the region you are on; voice being throttled by bandwidth set incorrectly - please check it by following the instructions here; voice hardware (mic, headset) not configured correctly in your operating system settings; voice hardware not configured correctly in the viewer; another application has your voice hardware in use (example, Skype); your anti virus software has “mangled” the voice application; see here. You can test voice by going to Voice Echo Canyon. If voice is working correctly for you, anything you say there will be echoed back to you. There's more to learn here >>> http://wiki.phoenixviewer.com/fs_voice

What kind of trouble? Does it seem like this >>> Wrong parcel name used with 'Can't rez object .. because the owner of this land does not allow it' error message ? If so, that's a well-recognized bug. Until Linden Lab fixes it, ty to rez objects as close to the center of your home as you can and then drag them from there to the place where you want them. You may have to try many times until you find the center of our parcel. If that's not what you meant, click on the Options link in the upper right corner of your question and select EDIT to add more information. Please do NOT start a new thread.

You might be able to clear it up by doing something as simple as using a different web browser. For some reason, IE and SL have never gotten along well together. Firefox and Chrome seem to work much better. Give one of them a try.

Peggy's right. I'm just saying that if you DID want to do that, you could. Just find the viewer's exe file on your hard drive, right click and select Properties >> Compatability, and then set it to run as if it were in Win XP.

Well, at least now you know what it isn't. Thanks for trying that. Unfortunately, that was the easy possibility.

64 bit runs fine. If you're worried, though, you can always set your viewer to run as a 32 bit application.

Different machines, different capabilities, who knows? Nobody here can diagnose your machine or connection accurately. All we can do is tell you where the most likely issues are, based on experience and the symptoms that you report. All I'm saying is not to dismiss the probability that your router is the problem. It's easy enough to test. Bypass the router completely. Run a cable from your PC directly to the modem. If it works, you'll know that the router is the problem spot. If not, then you can look at other possibilities.

Viewers play a minor part in voice functionality. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons: Your ISP is throttling or blocking the voice service; failure of the Vivox service; voice issues on the region you are on; voice being throttled by bandwidth set incorrectly - please check it by following the instructions here; voice hardware (mic, headset) not configured correctly in your operating system settings; voice hardware not configured correctly in the viewer; another application has your voice hardware in use (example, Skype); your anti virus software has “mangled” the voice application; see here. You can test voice by going to Voice Echo Canyon. If voice is working correctly for you, anything you say there will be echoed back to you. For more possibilities, see http://wiki.phoenixviewer.com/fs_voice

No, that's a false conclusion. Just because you can do simple things like e-mail or web browsing doesn't mean that your Internet connection is reliable enough for the sort of continuous data streaming that SL demands. Unlike online video games, most of which do much of their work client-side, SL passes data back and forth from its servers all the time because all environmental information -- which is constantly being updated -- resides on LL's servers. Router errors commonly create problems for SL residents, even when those residents have no trouble with other Internet applications. Wireless is particularly problematic because it is so easily disturbed by everything from cell phones and garage door openers to fluorescent light fixtures. If your router is almost good enough to handle SL, a little interference can make the difference between success and failure.

Ich vermute, dass vielleicht hast du Glück und manchmal finden Sie eine deutschsprachige Mitarbeiter, aber es gibt keine Möglichkeit, vorherzusagen, wann dies geschehen könnte. Viele Menschen wissen, eine zweite Sprache sprechen, aber Linden Lab kann nicht versprechen, dass einer von ihnen zur Verfügung stehen, wenn Sie anrufen.