SecondLife.exe - Bad Image

Whenever I try to run SL, I get this message:

C:\Windows\system32\OPENGL32.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.

I've tried:

Uninstall / Reinstall Second Life
Uninstall / Reinstall Graphic Card Drivers
Ran Virus Scan (Clean)
Ran Spyware Scan (Clean)
Ran HijackThis (No odd results)
Defragmented Computer
Rolled back to a earlier restore point
Tried different copies of OPENGL32.dll and glu32.dll

I've tried everything I can think of short of reistalling Windows Vista Home Premium from my installation DVD, but I am trying to avoid that since my original disk is missing (Stored away in a box in the garage). Is there anything any of you can suggest for me to try that I haven't done yet?

I think your video card driver is corrupted. Uninstall it and install a new copy.

I've already done that, several times.

try getting a third party viewer such as snowglobe or emerald and see if they work.

If your windows is up to date, and your drivers are as well, maybe you somehow fail to meet the specifications to run SL.

Already tried Emerald, they have the same requirements as the first party client and it gives me the same error. I use to run Second Life just fine and then on this past Christmas Day it gave me the above error and wouldn't run SL anymore. Strangely enough, it happened after I turned my computer back on after it had only been off for 15 minutes (Before I shut it off, it was working fine), and then when I tried to run SL after I turned it on, it gave me that error.

This could a case where a driver cleaner is in order. That is a system error message that has little to do with SL other than SL is an OpenGL program. It's almost certainly a video driver problem.

/me also votes video driver-related.

Opengl32.dll is a Windows component, not part of your graphic card driver. You mentioned you tried several different copies of this as well as glu32.dll, so likely you messed up with the correct driver version corresponding to your Windows release or the dll's are corrupted.

You could try to find the correct version on your Windows install CD, extract it and replace the existing one, but this may have been replaced with a newer version from a service pack or hotfix. Also try if an installation in repair mode fixes it, but it may well be that you have to reinstall your OS.

Where would I get such a driver cleaner?

Here is a link: http://www.guru3d.com/category/driversweeper/

But it will not fix problems with your broken Windows components.
Here is another thing you could try, the built in system file checker. You still need the installation DVD to fix possible errors.
http://vistasupport.mvps.org/system_file_checker.htm

Here's a link to a thread that sounds similar:
http://forums.worldofwarcraft.com/thread.html?topicId=22048898638&sid=1

Here's an oddball bit of info on OpenGL32.dll:
http://www.pro-hl.com/column_sandman15.shtml

What made you try a different copy of glu32.dll?

Where did you get your copies of opengl32.dll and glu32.dll?

There is a chance that auto updates installed different DLL's somewhere on your system, which were then replaced the orginals when you cold booted.

With that usless rubbish Vista (or ME2 as I call it), not everything installs, even though it may say so. Vista has a way of blocking installations and partial installations.
Turn off the UAC (User Account Control), its at best an annoyance. Then reinstall Graphic Drivers (if a nVidia, then always uninstall the previous driver, before updating) by downloading the driver, right mouse button click, and choose 'run as admin'.

Oh, in Vista, simply replacing a file, will not ensure it remains. Vista auto checks its own internal database for file versions, if it finds its own has been replaced, it will swap it back to its orginal.

Call me synical, but, I wonder if a hacker/exploit has delivered a DLL to your system that allows them to 'share' your screen. To an unprotected system, its possible it would work, the average joe is marginaly protected these days, so it would maybe simply fail to run programmes by blocking the dll.