Finally I went out on a limb and opened up the properties of the program. Logged back in, started the client, and…. So back to our little story here, I installed the Phoenix Viewer SEE2 LAA version, and just to be safe, I rebooted Windows. After a while of running, the program would crash, USUALLY bringing Windows (or at least Explorer) down with it. I could barely get into preferences to see if I could change anything in there to fix this problem. 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.īacktracking 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. 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.Īfter 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 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.
0 kommentar(er)
