As I talked about in today’s earlier post, one of the things I’ve been doing with my time is trying to figure out why in the nine hells I can’t get a Second Life viewer to work under Windows 7 – when I haven’t been chucking wood into the basement, of course.
After four hours of tossing wood around (I got a helluva lot into the basement, just in case you were wondering), I came back in and [after warming up] I sat back down at my computer to see if I couldn’t figure out this problem… I had to log in, because apparently windows updates had installed while I was outside, and first thing I noticed was that my Bluetooth drivers were screwed – reinstalled those, then reinstalled my favorite Alternate Viewer (from the Third Party Viewers directory on the Second Life wiki), Phoenix Viewer… I also installed Imprudence Viewer, Ascent Viewer, and downloaded a couple others, just in case. In this particular case, I chose the Phoenix Viewer with SEE2 support (taking into consideration that I’m running an Intel Core 2 Duo, and my chipset supports SEE2), and made sure I grabbed the Large Address Aware (LAA) version, since I’m running a 64-bit operating system, and plan on expanding over 2gb of RAM in the future.
Backtracking a little bit, the problem I was having with SL viewers (any SL viewer) is the program itself was slow – and by slow, I mean it took forever to load, and once it finally HAD loaded, it’s response time was almost zero. I could barely get into preferences to see if I could change anything in there to fix this problem. After a while of running, the program would crash, USUALLY bringing Windows (or at least Explorer) down with it. Over all, not a good experience.
So back to our little story here, I installed the Phoenix Viewer SEE2 LAA version, and just to be safe, I rebooted Windows. Logged back in, started the client, and…. it promptly did the same damned thing. I was stymied. Finally I went out on a limb and opened up the properties of the program. For those of you that may not be aware, Windows 7 (and Vista, for that matter, but Vista’s version was shite) has this wonderful little thing called “Compatibility Mode”. The way a person accesses this wonderful little invention, is by right clicking on your program’s shortcut (or directly on the program executable), choosing “Properties” from the context menu, and then clicking on the “Compatibility” tab.
There’s a ton of handy little features on this tab, mostly that deal with making older software work well under Windows 7. The “Run this program in compatibility mode for” option, gives you a fairly decent virtualization option, that tricks the running program into thinking it’s running on an earlier version of Windows. In my case, I chose “Windows XP (Service Pack 3)” from the drop down box. Below the virtualization, is a whole bunch of settings, that I really don’t understand, so I won’t attempt to explain them all to you. Some of them are self-explanatory, so I won’t explain those to you either.
The last option in the tab, is “Run this program as an administrator”. In case you don’t know, most applications that get installed on Windows 7, are prevented by default from performing actions that could harm your system (aka: administrative actions). For basic users that don’t do the level of things I do, usually when stuff like this happens you’ll see your UAC (User Access Control) box pop up, asking if you want to allow the application to perform whatever action it’s trying to perform… For people like me, the UAC just gets in the way – a lot – so I tend to disable it immediately after installing Windows (did it with Vista, and I do it with 7 – I’ll probably do it with the next version of Windows as well, if it has something similar). Anyhow, checking this “Run as administrator” box, allows you to bypass all that (to the best of my understanding – I’ve never actually tested it). I checked this too in my case, just to make sure.
Clicked “Apply” then “Ok” (just “Ok” would have worked, but I tend to take the extra step as a precautionary measure), tried to start Phoenix, and BOOM! It worked BEAUTIFULLY! Moral of the story? If you’re running Windows 7, and your SL client of choice is being extremely slow, make sure you turn on compatibility for at least Vista, if not XP. I’ll bet that will fix you problem right there.
Hi Gawyn! Thank you for sharing this info about windows 7–my problem however, is that I was running the new pheonix 1.5.2.1050 together with the Appfix they provided on windows 7, and my windows 7 has been crashing ever since:-( I had a wonderful time with phoenix 1.5.2.908 running on vista, so this was so unexpected. But having read your post, I think I will try to install the older version of phoenix on Windows 7, using the compatibility thing you mentioned, and see if it stops the crashes. Wish me all the best:-))
I can’t say as I’ve had that problem, so I can’t be much help, there. Hopefully you get that fixed!
Hi, thanks for the blog post, i am hopping this helps. I have an Alienware running windows 7 64-bit operating system with 4gb ram. The last few weeks have been hell on Second life. I’ll try your suggestions from your Nov. 2010 post. Wish me luck.
I do wonder if you have found any other viewers since that post that work better. I would love to know. It seems the better my laptop the worst Second life is.
Thank you for your openness
Flame_Emmons AKA Deb
I use strictly Phoenix and the Firestorm Beta myself – I’ve used the new Mesh Firstlook viewer a couple times under Linux, but eventually decided not to play around with that one until Mesh is on the Live Grid.
One other thing you might want to try, in addition to the suggestions that I gave previously, is check your anti-virus. I’m currently using Avast, and by default it automatically scans both incoming and outgoing connections. Which is great from a security standpoint. However, any high-bandwidth program (such as Second Life, World of Warcraft, Star Trek Online, and I’d assume other online games/worlds) get stuck at this point, as the anti-virus needs to work to keep up with scanning those millions of packets it’s sending out and receiving.
When I realized this, I went into my Avast settings, into the “Real-Time Shields” -> “File System Shield” area, “Expert Settings”, “Exclusions” and then added my Second Life client to the exclusion list (in my case: C:\Program Files (x86)\Phoenix Viewer\PhoenixViewer.exe – your file name and path may differ). I’d be very careful adding anything to this list, especially if you don’t trust the author of the program, as your AV program will no longer scan it in real time.
Thanks! That helped a lot!!! Happy times for me.
You’re quite welcome! Glad I was able to help at least one Second Lifer!
amazing !!!!!!!!! you are a genius i just bought a new pc and my sl viewer did not work and i found your post thank God
i already installed the phoenix viewer and it works great!!!!!!!!!!!!!!!!! i also instaled the fix and great
thank you so much
thank you, this totally solved my problem!! I had even been doing the compatibility “troubleshooter” but it wasnt choosing the right compatible version.. as soon as i followed your directions my second life is working again! xo 🙂
Great post Man,thank you! It is very helpful