Innerspace not attaching to WoW

BioUser · Post by **BioUser** » Sun Oct 23, 2005 12:38 am

I was running innerspace fine a few days ago. When i tried to run innerspace, it failed to attach to the game. The game window still says World of Warcraft instead of the 1sc-Alt or whatever it says, and the memory/frame HUD elements do not appear. I have tried reinstalling innerspace but have not got it to work yet. Any ideas on what i could be doing wrong, or what type of information do you need? If i try to open the console/patcher through the IS icon on the system tray, all i get is a black screen. It allows me to log in just fine though.

evil_necro_01 · Post by **evil_necro_01** » Wed Nov 09, 2005 9:15 pm

I am having this same issue. Not sure what is wrong

Post by **Lax** » Wed Nov 09, 2005 10:20 pm

Well, here's the thing... IS hasnt patched in a week.

When you reinstalled, did you uninstall first or did oyu just run the installer? The installer would not replace your settings files, which are probably what would be causing this for you. Instead of reinstalling, you can actually just delete the XML files in the main Inner Space folder, and it will effectively revert to "Factory" settings

kennies · Post by **kennies** » Wed Jan 03, 2007 2:32 pm

I've got the same problem lax. I've tried deleteing IS and doing a complete brand new reinstallation and still have the same problem as the OP.
I tried readding wow to the game list but when I run wow through IS, it still does not attach itself. Thus I cant access the console through wow. I even tried the auto load ISXWarden from Configuration too but that does not help.
I can access the console from the IS window but just not through wow. Any other suggestions?

Mishima · Post by **Mishima** » Thu Jan 04, 2007 9:36 am

Mine doesnt get anything on the 'Uplink' screen, it just stays blank

Post by **Lax** » Thu Jan 04, 2007 1:34 pm

I've got the same problem lax. I've tried deleteing IS and doing a complete brand new reinstallation and still have the same problem as the OP.
I tried readding wow to the game list but when I run wow through IS, it still does not attach itself. Thus I cant access the console through wow. I even tried the auto load ISXWarden from Configuration too but that does not help.
I can access the console from the IS window but just not through wow. Any other suggestions?

In the future, please refrain from posting on 2 year old threads claiming the "same problem".

Make sure you dont have firewall software or such blocking it. You can also try shutting down other programs to make sure they're not interfering. I would lean toward virus/spyware in your case. Run virus and spyware scans. You can also open the console in the uplink and type "diag" and paste the results that open in notepad here. If there's modules loaded that look forboding, then that would help pinpoint the problem with your system.

Mine doesnt get anything on the 'Uplink' screen, it just stays blank

And you, please start a separate thread next time for completely unrelated issues.

Close IS, delete InnerSpace.xml, restart IS

kennies · Post by **kennies** » Thu Jan 04, 2007 2:33 pm

My diagnostics as per your request.

Inner Space Kernel 1.08 Build 4299

System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp.050928-1517
Process Memory Usage: 21MB
System Physical RAM: 469/1014MB
Page File: 1245/1672MB
Virtual Memory: 1969/2047MB (Extended: 0MB)
CPU 1: Genuine Intel(R) CPU T2050 @ 1.60GHz @ 1600MHz
CPU 2: Genuine Intel(R) CPU T2050 @ 1.60GHz @ 1600MHz
CPU Affinity Mask: 0x3
Video 1: \\.\DISPLAY1/Mobile Intel(R) 945GM Express Chipset Family
Video 2: \\.\DISPLAY2/Mobile Intel(R) 945GM Express Chipset Family
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180

Loaded Modules:
-----------------------------------
Module 0x00400000-0x00458000: C:\Program Files\InnerSpace\InnerSpace.exe (Mon Jan 01 19:16:53 2007)
Module 0x00DD0000-0x01030000: C:\WINDOWS\system32\d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x011C0000-0x011DD000: C:\Program Files\InnerSpace\IS-D3D9Engine.dll (Wed Nov 29 03:31:56 2006)
Module 0x01BB0000-0x01BE8000: C:\Program Files\InnerSpace\IS-VirtualInput.dll (Thu Nov 30 18:39:56 2006)
Module 0x03000000-0x0314F000: C:\Program Files\InnerSpace\IS-Kernel.dll (Mon Jan 01 19:16:48 2007)
Module 0x05000000-0x05135000: C:\Program Files\InnerSpace\ISUI.dll (Thu Nov 23 00:21:26 2006)
Module 0x070E0000-0x0711B000: C:\WINDOWS\system32\WMASF.DLL (Thu Aug 04 01:14:06 2005)
Module 0x09980000-0x09BBF000: C:\WINDOWS\system32\WMVCore.dll (Thu Aug 04 01:14:15 2005)
Module 0x0FFD0000-0x0FFF8000: C:\WINDOWS\system32\rsaenh.dll (Wed Jul 07 02:17:12 2004)
Module 0x10000000-0x1001E000: C:\Program Files\InnerSpace\Lavish.dll (Wed Oct 18 20:27:28 2006)
Module 0x4FDD0000-0x4FF76000: C:\WINDOWS\system32\d3d9.dll (Wed Aug 04 07:56:03 2004)
Module 0x5D090000-0x5D127000: C:\WINDOWS\system32\COMCTL32.dll (Wed Aug 04 07:56:31 2004)
Module 0x60610000-0x60616000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\fusion.dll (Fri Sep 23 07:13:18 2005)
Module 0x629C0000-0x629C9000: C:\WINDOWS\system32\LPK.DLL (Wed Aug 04 07:56:26 2004)
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 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 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 0x77120000-0x771AC000: C:\WINDOWS\system32\OLEAUT32.dll (Wed Aug 04 07:57:39 2004)
Module 0x773D0000-0x774D2000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll (Wed Aug 04 07:55:56 2004)
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 0x77D40000-0x77DD0000: C:\WINDOWS\system32\USER32.dll (Wed Mar 02 18:09:29 2005)
Module 0x77DD0000-0x77E6B000: C:\WINDOWS\system32\ADVAPI32.dll (Wed Aug 04 07:56:23 2004)
Module 0x77E70000-0x77F01000: C:\WINDOWS\system32\RPCRT4.dll (Wed Aug 04 07:56:30 2004)
Module 0x77F10000-0x77F57000: C:\WINDOWS\system32\GDI32.dll (Thu Dec 29 02:54:35 2005)
Module 0x77F60000-0x77FD6000: C:\WINDOWS\system32\SHLWAPI.dll (Fri Jun 23 11:25:30 2006)
Module 0x78130000-0x781CB000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd\MSVCR80.dll (Fri Sep 23 06:44:37 2005)
Module 0x79000000-0x79045000: C:\WINDOWS\system32\mscoree.dll (Fri Sep 23 11:30:38 2005)
Module 0x79E70000-0x7A3D1000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll (Fri Sep 23 11:33:00 2005)
Module 0x7C800000-0x7C8F4000: C:\WINDOWS\system32\kernel32.dll (Wed Jul 05 10:55:00 2006)
Module 0x7C900000-0x7C9B0000: C:\WINDOWS\system32\ntdll.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C9C0000-0x7D1D5000: C:\WINDOWS\system32\SHELL32.dll (Thu Jul 13 13:33:24 2006)

Display
-------------------------------------
Adapter resolution: 1280x800
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)