please, I have not been able to get into SL for 6weeks. I have a Mac and all system requirements look good. I have an NVIDIA GeForce 320 M graphics card. I don't know if that's the problem. What happens is it just says "we are experiencing difficulties in this region" (I tried to log in to both Home and Last Location) and gives me a choice to quit or view IM and chat. Whatever I click, it quits. And that's all I know. I don't have any idea what could be so wrong for so long. I cleared my cache and tried several different viewers, all SL viewers, going back about 5 versions I think. Please help I am completely frustrated and really miss my friends and my avatar!!! Well I redownloaded a driver for my graphics card and it did nothing. I do not have a cable but I can get one. I don't understand why that is necessary. I don't know how to log into a specific location either... I guess I'm not very technically versed in computer matters I'm sorry. I just really want to see my friends and this is soooo frustrating for me..,.. And okay I tried to log into that region the adult sandbox and it said "cannot connect to simulator" The region I've been attempting to log into now for weeks is Hanja Welcome Area-Rez Zon, Gukyeol-General And please let me know how to log into the Linden areas, I copied the address that Karen suggested and it did not work as I report above. I don't know how to get to Smith or Pooley. This is the message "Darn. You have been logged out of Second Life. Please check your connection to the internet. This region might be experiencing difficulties." then the choices are "quit" or "View IM and Chat" so that means I guess that I am logging in for a brief second, and it immediately logs me out, right? Why would it be doing that over and over and over? After all this I finally got in after fifty or so attempts today. I was able to finally view IM and Chat and I then deleted about 2000 notifications and logged back out, and back in, and suddenly it worked fine. Thank you anyway to those who tried to help. This issue is now resolved I guess. I just don't know exactly how it worked.