wow and inner space

[Grilor]

any one eles getting laged in inner space or cant load a second instance of i? whe i load up innder spance and wow i get major lag if i have 2 runnig or i get errors that i cant load it at all.

[Lax]

I can run several with no problems. What type of lag are you getting, and what errors are you getting? This is rather vague, so I cant really help solve the problem... Type "diag" in an IS console, which will open some diagnostic info in notepad, then paste the results here

[Grilor]

video lag is what im getting some thign nasty.. also the error im getting is i open one wow ( both are in 2 different paths and have there own directory) then when i go to open a second wow i get a crital error saying it cant opend and was forcfull closed do i want to send an error repot to blizzard.

[Grilor]

Inner Space Kernel 1.07 Build 4126

System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
Process Memory Usage: 19MB
System Physical RAM: 1444/2047MB
Page File: 3502/3941MB
Virtual Memory: 1926/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 Processor 3000+ @ 1999MHz
CPU Affinity Mask: 0x1
Video 1: \\.\DISPLAY1/RADEON X800 PRO
Video 2: \\.\DISPLAY2/RADEON X800 PRO Secondary
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 7.0.5700.6

Loaded Modules:
-----------------------------------
Module 0x00400000-0x00459000: C:\Program Files\InnerSpace\InnerSpace.exe (Tue Aug 29 15:11:38 2006)
Module 0x00890000-0x00895000: C:\WINDOWS\system32\wmfhotfix.dll (Mon Jan 02 21:23:17 2006)
Module 0x009B0000-0x009BF000: C:\WINDOWS\system32\ZoneLabs\vetredir.dll (Fri Apr 29 05:37:25 2005)
Module 0x00AF0000-0x00B05000: C:\WINDOWS\system32\ZoneLabs\isafeif.dll (Fri Apr 29 05:36:55 2005)
Module 0x00C30000-0x00C49000: C:\Program Files\Bonjour\mdnsNSP.dll (Sat Jul 23 00:21:06 2005)
Module 0x01050000-0x0106D000: C:\Program Files\InnerSpace\IS-D3D9Engine.dll (Sun Aug 13 19:10:10 2006)
Module 0x01090000-0x010C7000: C:\Program Files\InnerSpace\IS-VirtualInput.dll (Sat Aug 26 16:45:12 2006)
Module 0x010F0000-0x01350000: C:\WINDOWS\system32\d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x02A10000-0x02A19000: C:\WINDOWS\system32\Normaliz.dll (Thu Jun 29 15:05:42 2006)
Module 0x02C70000-0x02F36000: C:\WINDOWS\system32\msi.dll (Mon May 02 15:51:33 2005)
Module 0x02F40000-0x02F73000: C:\WINDOWS\system32\RadExe.dll (Wed Apr 27 03:49:28 2005)
Module 0x03000000-0x03125000: C:\Program Files\InnerSpace\IS-Kernel.dll (Tue Aug 29 15:11:18 2006)
Module 0x05000000-0x05134000: C:\Program Files\InnerSpace\ISUI.dll (Tue Aug 29 15:07:55 2006)
Module 0x070D0000-0x0710A000: C:\WINDOWS\system32\WMASF.DLL (Fri Jan 28 16:53:14 2005)
Module 0x086D0000-0x08916000: C:\WINDOWS\system32\WMVCore.dll (Fri Jan 28 21:00:47 2005)
Module 0x10000000-0x1001E000: C:\Program Files\InnerSpace\Lavish.dll (Mon Jul 31 02:20:01 2006)
Module 0x4FDD0000-0x4FF76000: C:\WINDOWS\system32\d3d9.dll (Wed Aug 04 07:56:03 2004)
Module 0x5AD70000-0x5ADA8000: C:\WINDOWS\system32\UxTheme.dll (Wed Aug 04 07:56:43 2004)
Module 0x5B860000-0x5B8B4000: C:\WINDOWS\system32\netapi32.dll (Fri Jul 14 15:31:39 2006)
Module 0x5D090000-0x5D127000: C:\WINDOWS\system32\COMCTL32.dll (Wed Aug 04 07:56:31 2004)
Module 0x5DCA0000-0x5DCE4000: C:\WINDOWS\system32\iertutil.dll (Wed Aug 23 07:09:40 2006)
Module 0x61410000-0x61531000: C:\WINDOWS\system32\urlmon.dll (Wed Aug 23 07:31:07 2006)
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 0x6D9A0000-0x6DAC8000: C:\WINDOWS\system32\d3d8.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 0x71BF0000-0x71C03000: C:\WINDOWS\system32\SAMLIB.dll (Wed Aug 04 07:56:29 2004)
Module 0x73DD0000-0x73ECE000: C:\WINDOWS\system32\MFC42.DLL (Wed Aug 04 07:56:21 2004)
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 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 0x768D0000-0x76974000: C:\WINDOWS\system32\RASDLG.dll (Wed Aug 04 07:56:28 2004)
Module 0x76B20000-0x76B31000: C:\WINDOWS\system32\ATL.DLL (Wed Aug 04 07:56:55 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 0x76D40000-0x76D58000: C:\WINDOWS\system32\MPRAPI.dll (Wed Aug 04 07:56:47 2004)
Module 0x76D60000-0x76D79000: C:\WINDOWS\system32\iphlpapi.dll (Fri May 19 12:59:41 2006)
Module 0x76E10000-0x76E35000: C:\WINDOWS\system32\adsldpc.dll (Wed Aug 04 07:56:13 2004)
Module 0x76E80000-0x76E8E000: C:\WINDOWS\system32\rtutils.dll (Wed Aug 04 07:56:36 2004)
Module 0x76E90000-0x76EA2000: C:\WINDOWS\system32\rasman.dll (Wed Aug 04 07:56:29 2004)
Module 0x76EB0000-0x76EDF000: C:\WINDOWS\system32\TAPI32.dll (Wed Aug 04 07:56:38 2004)
Module 0x76EE0000-0x76F1C000: C:\WINDOWS\system32\RASAPI32.dll (Wed Aug 04 07:56:25 2004)
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-0x771AC000: C:\WINDOWS\system32\OLEAUT32.dll (Wed Aug 04 07:57:39 2004)
Module 0x771B0000-0x7727C000: C:\WINDOWS\system32\WININET.dll (Wed Aug 23 07:31:07 2006)
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 0x77690000-0x776B1000: C:\WINDOWS\system32\NTMARTA.DLL (Wed Aug 04 07:57:02 2004)
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 0x77B40000-0x77B62000: C:\WINDOWS\system32\appHelp.dll (Wed Aug 04 07:56:36 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 0x77CC0000-0x77CF2000: C:\WINDOWS\system32\ACTIVEDS.dll (Wed Aug 04 07:56:03 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 0x77FE0000-0x77FF1000: C:\WINDOWS\system32\Secur32.dll (Wed Aug 04 07:56:49 2004)
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)
Module 0x7E1E0000-0x7E786000: C:\WINDOWS\system32\ieframe.dll (Wed Aug 23 07:31:07 2006)

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

[Grilor]

now i cant get 2 to load at all. i can load one but as soon as i go to open a second i get Crital error 134 unabel to astablish a connection was forceful rejected send to blizzard. or some thign along them lines.. but i got the lag fixed i put it in Full Screen.

[Lax]

You should be running them both from the same folder. Why do you have 2? That hurts performance, and could be the reason you're getting the error..

[Grilor]

i tryed that first thats why i thought id try fomr 2 different folders to see if that make a differance.. will try form the same folder again

[Grilor]

yea i get the saem error with them both coming frome the same dir.. this is straing to drive me nuts.. i get the same thing when i use Wineq2 aswell. the firs instance of wow load and runs perfectly BUT ass soon as i tell it to load the second one i get the error that it was focrfuly rejecter and please send this information off to blizzard. im about to pull my hair out.. this works great for EQ1 i have NO problems runniung 2 EQ1 at the saem time

[Lax]

Unfortunately I don't think I'm going to be able to solve the problem for you without exact error messages (not typed by you, sorry but your typing is impossible to decipher), or a copy of the WoW error log. Do you get this error launching 2 WoWs without using IS or WinEQ 2?

[Grilor]

yea i have 2nd deg dylixia sorry for they typing but w/e.. any way .. i got my problem fixed but adjusting the pagefile from 2075 to 5800

and yes i got the same mes in IS WINEQ and with out using it.. but now i get a new msg saying out of ram in data.pmq crital failure and then one of the wows windows close. so now i have to figure out why that is happening. im also runn 2gig DDRPC3200 ram