LaunchPad.exe Error when using InnerSpace to start VG

[ForsakenOne]

I'm assuming this is an InnerSpace-related error, some sort of obscure conflict, because it also happens before installing ISXVG or VGCraftbot. -- Meaning I get the very same error on a clean install of InnerSpace after completely removing everything else. Have tried removing, deleting folders, and reinstalling numerous times.

What happens is that as soon as the LaunchPad.exe tries to load, I get the standard, annoying, useless WinXP error:

"LaunchPad.exe has encountered a problem and needs to close. We are sorry for the inconvenience. ... " etc. etc.

Anyone have any suggestions? This is probably something simple, but after several days is still eluding me.

.NET 20 is installed, and working fine for other games that use it. I am logged on as system admin. VG starts up just fine without using InnerSpace.

[Lax]

It's probably related to something else installed on your system. Inner Space itself doesn't require .NET, the only time it's required is when you want to run a .NET app through Inner Space.

If you open the main IS console and type "diag", a diagnostic report should open in notepad. If you can paste that here or to me in email ( lax@lavishsoft.com ) I may recognize something for you to try disabling. The most common things that come to mind are Spyware Doctor or Spycatcher. I would just try closing apps a few at a time until you discover something that, for whatever reason, is interfering, and if you find one, then I may be able to fix the problem (though some I cannot fix as they are simply incompatible by nature).

[ForsakenOne]

Thanks so much for replying. Here's the info from Notepad:

Inner Space Kernel 1.09 Build 4598

System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.070227-2254
Process Memory Usage: 16MB
System Physical RAM: 671/1023MB
Page File: 2180/2460MB
Virtual Memory: 1970/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 Processor 3200+ @ 2010MHz
CPU Affinity Mask: 0x1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 7600 GS
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180

Loaded Modules:
-----------------------------------
Module 0x00400000-0x004A2000: C:\Program Files\InnerSpace\InnerSpace.exe (Sat Oct 06 14:00:52 2007)
Module 0x00980000-0x0099F000: C:\WINDOWS\system32\nvappfilter.dll (Wed Nov 10 17:41:04 2004)
Module 0x01040000-0x012A0000: C:\WINDOWS\system32\d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x01880000-0x0189E000: C:\Program Files\InnerSpace\IS-D3D9Engine.dll (Fri Jul 20 14:16:07 2007)
Module 0x01BC0000-0x01BF8000: C:\Program Files\InnerSpace\IS-VirtualInput.dll (Sun Oct 14 13:56:54 2007)
Module 0x03000000-0x03162000: C:\Program Files\InnerSpace\IS-Kernel.dll (Sat Oct 06 14:00:44 2007)
Module 0x05000000-0x05148000: C:\Program Files\InnerSpace\ISUI.dll (Mon Aug 20 16:25:03 2007)
Module 0x0FFD0000-0x0FFF8000: C:\WINDOWS\system32\rsaenh.dll (Wed Jul 07 02:17:12 2004)
Module 0x10000000-0x1001E000: C:\Program Files\InnerSpace\Lavish.dll (Fri Aug 17 14:48:03 2007)
Module 0x11C70000-0x11CA9000: C:\WINDOWS\system32\WMASF.DLL (Thu Oct 19 05:47:23 2006)
Module 0x15110000-0x1536A000: C:\WINDOWS\system32\WMVCore.dll (Thu Oct 19 05:48:18 2006)
Module 0x20000000-0x202C5000: C:\WINDOWS\system32\xpsp2res.dll (Wed Aug 04 07:56:41 2004)
Module 0x4FDD0000-0x4FF76000: C:\WINDOWS\system32\d3d9.dll (Wed Aug 04 07:56:03 2004)
Module 0x5D090000-0x5D12A000: C:\WINDOWS\system32\COMCTL32.dll (Fri Aug 25 15:45:58 2006)
Module 0x60610000-0x60616000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\fusion.dll (Fri Sep 23 07:13:18 2005)
Module 0x662B0000-0x66308000: C:\WINDOWS\system32\hnetcfg.dll (Wed Aug 04 07:56:16 2004)
Module 0x688F0000-0x688F9000: C:\WINDOWS\system32\HID.DLL (Wed Aug 04 07:56:12 2004)
Module 0x6CE10000-0x6CE48000: C:\WINDOWS\system32\DINPUT8.dll (Wed Aug 04 07:56:32 2004)
Module 0x6D990000-0x6D996000: C:\WINDOWS\system32\d3d8thk.dll (Wed Aug 04 07:56:02 2004)
Module 0x71A50000-0x71A8F000: C:\WINDOWS\system32\mswsock.dll (Wed Aug 04 07:59:20 2004)
Module 0x71A90000-0x71A98000: C:\WINDOWS\System32\wshtcpip.dll (Wed Aug 04 07:57:49 2004)
Module 0x71AA0000-0x71AA8000: C:\WINDOWS\system32\WS2HELP.dll (Wed Aug 04 07:57:39 2004)
Module 0x71AB0000-0x71AC7000: C:\WINDOWS\system32\WS2_32.dll (Wed Aug 04 07:57:38 2004)
Module 0x73080000-0x7309C000: C:\WINDOWS\system32\rsvpsp.dll (Sat Aug 18 05:33:29 2001)
Module 0x74720000-0x7476B000: C:\WINDOWS\system32\MSCTF.dll (Wed Aug 04 07:57:30 2004)
Module 0x74D90000-0x74DFB000: C:\WINDOWS\system32\usp10.dll (Wed Aug 04 07:56:42 2004)
Module 0x755C0000-0x755EE000: C:\WINDOWS\system32\msctfime.ime (Wed Aug 04 07:57:31 2004)
Module 0x75E90000-0x75F40000: C:\WINDOWS\system32\SXS.DLL (Thu Oct 19 13:56:28 2006)
Module 0x76380000-0x76385000: C:\WINDOWS\system32\MSIMG32.dll (Wed Aug 04 07:58:31 2004)
Module 0x76390000-0x763AD000: C:\WINDOWS\system32\IMM32.DLL (Wed Aug 04 07:56:30 2004)
Module 0x763B0000-0x763F9000: C:\WINDOWS\system32\comdlg32.dll (Wed Aug 04 07:56:32 2004)
Module 0x76B40000-0x76B6D000: C:\WINDOWS\system32\WINMM.dll (Wed Aug 04 07:57:10 2004)
Module 0x76BF0000-0x76BFB000: C:\WINDOWS\system32\PSAPI.DLL (Wed Aug 04 07:56:58 2004)
Module 0x76C30000-0x76C5E000: C:\WINDOWS\system32\WINTRUST.dll (Wed Aug 04 07:56:41 2004)
Module 0x76C90000-0x76CB8000: C:\WINDOWS\system32\IMAGEHLP.dll (Wed Aug 04 07:56:25 2004)
Module 0x76D60000-0x76D79000: C:\WINDOWS\system32\iphlpapi.dll (Fri May 19 12:59:41 2006)
Module 0x76F20000-0x76F47000: C:\WINDOWS\system32\DNSAPI.dll (Mon Jun 26 17:37:10 2006)
Module 0x76F60000-0x76F8C000: C:\WINDOWS\system32\WLDAP32.dll (Wed Aug 04 07:56:43 2004)
Module 0x76FB0000-0x76FB8000: C:\WINDOWS\System32\winrnr.dll (Wed Aug 04 07:56:35 2004)
Module 0x76FC0000-0x76FC6000: C:\WINDOWS\system32\rasadhlp.dll (Mon Jun 26 17:37:10 2006)
Module 0x76FD0000-0x7704F000: C:\WINDOWS\system32\CLBCATQ.DLL (Tue Jul 26 04:39:44 2005)
Module 0x77050000-0x77115000: C:\WINDOWS\system32\COMRes.dll (Wed Aug 04 07:56:36 2004)
Module 0x77120000-0x771AB000: C:\WINDOWS\system32\OLEAUT32.dll (Thu May 17 11:28:05 2007)
Module 0x773D0000-0x774D3000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll (Fri Aug 25 15:45:55 2006)
Module 0x774E0000-0x7761D000: C:\WINDOWS\system32\ole32.dll (Tue Jul 26 04:39:47 2005)
Module 0x77920000-0x77A13000: C:\WINDOWS\system32\SETUPAPI.dll (Wed Aug 04 07:56:32 2004)
Module 0x77A80000-0x77B14000: C:\WINDOWS\system32\CRYPT32.dll (Wed Aug 04 07:56:01 2004)
Module 0x77B20000-0x77B32000: C:\WINDOWS\system32\MSASN1.dll (Wed Aug 04 07:57:23 2004)
Module 0x77C00000-0x77C08000: C:\WINDOWS\system32\VERSION.dll (Wed Aug 04 07:56:39 2004)
Module 0x77C10000-0x77C68000: C:\WINDOWS\system32\msvcrt.dll (Wed Aug 04 07:59:14 2004)
Module 0x77DD0000-0x77E6B000: C:\WINDOWS\system32\ADVAPI32.dll (Wed Aug 04 07:56:23 2004)
Module 0x77E70000-0x77F02000: C:\WINDOWS\system32\RPCRT4.dll (Mon Jul 09 13:09:42 2007)
Module 0x77F10000-0x77F57000: C:\WINDOWS\system32\GDI32.dll (Tue Jun 19 13:31:19 2007)
Module 0x77F60000-0x77FD6000: C:\WINDOWS\system32\SHLWAPI.dll (Wed Aug 22 12:55:38 2007)
Module 0x77FE0000-0x77FF1000: C:\WINDOWS\system32\Secur32.dll (Wed Aug 04 07:56:49 2004)
Module 0x78130000-0x781CB000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.163_x-ww_681e29fb\MSVCR80.dll (Mon Jun 05 21:10:49 2006)
Module 0x79000000-0x79045000: C:\WINDOWS\system32\mscoree.dll (Fri Apr 13 07:13:02 2007)
Module 0x79E70000-0x7A3D6000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll (Fri Apr 13 07:15:54 2007)
Module 0x7C800000-0x7C8F5000: C:\WINDOWS\system32\kernel32.dll (Mon Apr 16 15:52:53 2007)
Module 0x7C900000-0x7C9B0000: C:\WINDOWS\system32\ntdll.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C9C0000-0x7D1D7000: C:\WINDOWS\system32\SHELL32.dll (Fri Oct 26 03:33:59 2007)
Module 0x7E410000-0x7E4A0000: C:\WINDOWS\system32\USER32.dll (Thu Mar 08 15:36:28 2007)

Display
-------------------------------------
Adapter resolution: 1280x1024
Current display mode: 792x573 (windowed)
Window viewable size: 792x573
Display Scale: 100.0%x100.0%, Distortion: 0.0%
MaxFPS Foreground: 60 (Calculate)
MaxFPS Background: 30 (Absolute)

[ForsakenOne]

I've now tried ending or disabling everything else that's running, but with the same result as before. I hope you can spot something I'm missing here.

[Lax]

Unfortunately no, it looks squeaky clean.

There's a few things I recommend trying in situations like this, see the following post (the bottom one on the thread) for a few things that are known to help.
http://www.lavishsoft.com/forum/viewtop ... 2887#12887

If you complete items 1 and 2 in the list, and nothing turned up and it still fails, see if any further information can be gleaned from the crash box. Typically there's some technical wizardry described that looks something like this:

Code: Select all

AppName: explorer.exe       AppVer: 6.0.2800.1106       ModName: unknown
ModVer: 0.0.0.0       Offset: 04446fe8 

You may need to click a link in the error box to find it. Given that information, I may be able to track down the crash.

[ForsakenOne]

My DEP was already set to the top option, and a full scan for virus/spyware turned up only three harmless cookies.

Here's the info from the crash box, for what it's worth:

AppName: launchpad.exe AppVer: 0.0.0.0 ModName: launchpad.exe
ModVer: 0.0.0.0 Offset: 0007d833

[Lax]

Sorry for the delay looking into this. After checking out the address of your crash, I'm not sure there's anything I can immediately do. If you can find the minidumps from the crash I can hopefully at least determine if it is in fact Inner Space's fault, or just happens to be exhibited using Inner Space.

Here's instructions (I googled to find them, these are copied from a grouplogic.com knowledge base article and spiced to taste):
To retrieve the mini dump file when an application crashes.
- After an application crashes a dialog with the following title will be displayed:
"(Application Name) has encountered a problem and needs to close. We are sorry for the inconvenience."
- Click the "click here" hyperlink
- Click the "click here" that follows "To view technical information about the error report".
- A third dialog with 2 complete paths will be displayed. They usually follow the format of:
(System Partition):\DOCUME~1\ADMINI~1\LOCALS~1\Temp\(Folder name starting with W)\(File name)
- Open Windows Explorer and navigate to the folder the starts with "W"
- (Do not dismiss any of the dialogs; doing so will remove the folder)
- ZIP or RAR the contents of the folder, and email to lax@lavishsoft.com

[ForsakenOne]

Thanks much, I'll send you the .zip file this morning.

[ForsakenOne]

Okay, ran into a problem, or possibly two problems.

First, there is only one path displayed in the technical information dialog. That one path is the \temp folder itself. Four files are created there in the course of attempting to create the minidump.

The second problem is that while all the other dialogs are still up, I can only copy one of the four files, a file with the .txt extension. The three others are "in use" and can't be copied or archived. and believe me, I tried every way I could think of. And, of course, if I close the other dialogs, the files disappear. One of these three files have a .tmp extension, and the third has a .dmp extension.

So, is it the .txt file that you need? because if it's one of the others, I'm at a loss how to get it into a ZIP file ...

[ForsakenOne]

Oops, my previous message should have said: "TWO of these three files have a .tmp extension, and the third has a .dmp extension. "

[fearless]

did you try the command line? IE Start > Run > cmd?

[ForsakenOne]

Using a command line, I am able to copy one of the .tmp files and the .txt file. The other .tmp file and the .dmp file result in the message:

"The process cannot access the file because it is being used by another process."

[fearless]