Nobody can answer this??????

Using the icon that is installed to the desktop, SL repeatedly crashes. I'm not finding any tips on settings. No msg comes up saying firewall is blocking this program. I've never had any problems with IP interactions or any other internet connection dependent programs. No router. Cable internet.
Please help.
Thanks in advance

I'm no expert but I think the first question people that are will ask is what your PC specs and which version of the viewer are you using...

Launch SL from a console and see what is displayed when it crashes.

I think I've listed all the necessary specs in my signature. Here is what appears under "About Second Life" in the viewer. What else should I post about my PC?
Thanks
______________________________________________________________

Second Life 1.23.5 (136262) Oct 14 2009 12:08:26 (Second Life Release)
Release Notes

Built with MSVC version 1400

CPU: AMD (Unknown model) (2992 MHz)
Memory: 3071 MB
OS Version: Microsoft Windows Vista Service Pack 2 (Build 6002)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: ATI Radeon HD 4830 Series
Windows Graphics Driver Version: 8.60-090316a1-078237C-DNA
OpenGL Version: 2.1.8577


libcurl Version: libcurl/7.18.1 OpenSSL/0.9.8j zlib/1.2.3
_________________________________________________________
SIGNATURE

(ah OK.... I have signatures turned off!)

Try right-clicking on your desktop shortcut for SL, and opening the properties. At the end of the line that says "Target" add " --noprobe" which will keep SL from checking your graphics hardware. If it runs, you can then open properties and turn up the graphics settings from there, and be sure to uncheck the VBO setting in the Graphics Hardware options. This may help on new hardware as LL seems to have stopped updating their list of supported GPUs a couple of years ago.

It may also help if right after you try to launch SL, you go to Control Panel->Administrative Tools->Event Viewer and look for errors in the Applications and System logs.

http://jira.secondlife.com/browse/VWR-2610, maybe? The name Acer jumps out at me as a brand that has problems with SL - the extra software they install doesn't always play nice.

Anyone else? Yes I've read the Wiki and other associated threads. Still have NEVER been able to log in.
Thanks

My best guess is you've got a driver problem.

How recent are your video drivers? Did you download them straight from ATI, or did you let Windows Update mess things up? Did you completely uninstall any existing older drivers (via Driver Cleaner or Driver Sweeper) before installing your current one?

Same questions for your motherboard drivers, and for your network drivers.

And what version DirectX do you have installed?

You say it crashes.

How far does it get before crashing? Does it get to the login screen? Does it start to load (and in that case how far does it get before it crashes)?

Hopefully we can help more when the answers to these questions are known.

have you tried running the viewer in compatability mode ? if no then right click on the icon go to compatibility, and then select windows XP

Well, I was able to login and fly around a bit. Didn't have time to really check it out. Asriazh Frye suggested to start the program through the dos-prompt or command window. It started up just fine.

PROBLEM BEFORE (for others that may come across this)

It was crashing REPEATEDLY about 7 seconds after clicking the login button in the viewer. Nothing starts to load. The progress bar and some default messaging shows up, but then it would crash. Nothing else would show beyond that progress bar.

I do have somewhat current drivers. Had version 8.14.0010.0655 (3/16/2009) installed, straight from ATI, with a clean install using Driver Sweeper (and proper order of operations). Went to DNA's newest version to try and correct the problem (it didn't).

dxdiag.exe says I'm using DirectX10.

Acer's site says there are no new drivers for my motherboard. Even after hours of searching, I have not been able to find the support site for my MB. Network drivers-I haven't checked that out. Don't know where to start besides trying an update through device manager.

Thanks for your help guys. As far as I can tell, for now, this is resolved.