I have not been so fortunate with VB6 Enterprise sitting on the same
box as VS2005.

VS2005 launches and closes just fine...no problem there.

Before I encountered this error I rebooted cold, then simply launched
VB6 without ever launching VS2005.

I launch VB 6.0, the standard "New Project" window displays.
Clicked 'cancel' and close VB6 without opening any projects.

Upon closing VB6, VB6 crashes & I receive an error:
"Visual Basic has encountered a problem and needs to close.
Options here are "Debug", "Send Error Report", or "Don't Send".

If I click "Debug"  a "Visual Studio Just-In-Time Debugger" form is
displayed that says:
"An unhandled win32 exception occurred in VB6.EXE [5036]
Then "New instance of Visual Studio 2005" is listed as a "Possible
Debugger"
Check boxes available:
- Set the Currently selected debugger as the default.
- Manually choose the debugging engines.

Finally it asks
"Do you want to debug using the selected debugger?  (Yes/No buttons as
choice)

Answer 'yes'  and you receive an error from VS2005:
Unhandled exception at 0x0055a8ea in VB6.EXE: 0xC0000005: Access
violation reading location 0x608af85c.

Any ideas short of uninstalling /re-installing VB6?

Thanks.