FAQ  •  Register  •  Login

Iboxer and Sony's Station Launcher problem

Moderator: MiRai

<<

svaberendk

Posts: 5

Joined: Sun Aug 08, 2010 8:23 pm

Post Sun Aug 08, 2010 9:08 pm

Iboxer and Sony's Station Launcher problem

Hi all.

I just purchased Iboxer and been fiddling with it all night trying to get it to work but running into a few problems. I bought it to use with Vanguard Sage of heroes after reading on the webpage Iboxer supports it.

I should probably start with mentioning the steps i have taken and what problem I'm getting.

I use windows 7 64bit fully updated.


My first step is doing what the 40 second WoW instructional video says. My first wall comes when i have to choose the launcher. Vanguard doesn't have it's own launcher but is launched through sony's station launcher. Only one instance of the launcher can run at any given time. I assume this is what's causing my grief since inner space/Iboxer can't launch the game from it. Or I'm not doing it correctly.

1. Wizards > Quick Setup > Choosing Vanguard from dropdown menu > choosing Vanguard yet again below under "game" > add game from inner space task bar icon choosing the station launchpad since Vanguard doesn't have it's own working executable > choosing vanguard default profile in Iboxer "game profile" > choosing character names to group > choosing window layout style ..finish

After i choose my team in the inner space systrey menu ..station launcher runs and I am able to click on the vanguard link which takes me to the patcher check where i can launch the game. This is where i crash. After the crash another attempt is made by iboxer/inner space to run the second instance where it again crashes.


I can run multiple instances of the game on 1 PC by logging in via station launcher. Logging out of the station launcher itself and logging in with other handles. The station launcher is not required to run with the game.


Any help would be appreciated

Thank you
Last edited by svaberendk on Mon Aug 09, 2010 12:19 am, edited 2 times in total.
<<

svaberendk

Posts: 5

Joined: Sun Aug 08, 2010 8:23 pm

Post Sun Aug 08, 2010 9:37 pm

Re: Iboxer and Sony's Station Launcher problem

I have found an old launcher here http://vanguard.station.sony.com/install/ that works without the station launcher. but still the same issue. As the game is launching it crashes right before the game enters character select

I have now tried to delete the game .ini files, download the test build of IS. Use forced windowed mode in IS game configuration, turning off shaders and other graphical options in the game and changing different resolutions still to no avail
Attachments
ISBoxerToolkitProfile.XML
(4.41 KiB) Downloaded 787 times
<<

lax

User avatar

Site Admin

Posts: 7303

Joined: Tue Nov 17, 2009 9:32 pm

Post Mon Aug 09, 2010 9:34 am

Re: Iboxer and Sony's Station Launcher problem

Thanks for reporting back with what you found. You can try getting me some diagnostic information from Inner Space. To do so, right click IS and select Console. In the console, type the command "diag" with no quotes. This will open up some info in notepad, which you can paste to me here or in email (lax@lavishsoft.com). I may be able to offer suggestions based on that information. I know of people that use IS with Vanguard but I don't know any specifics about how they run it, I don't think you're doing anything wrong.

Another thing you can try is to install an older version of Inner Space (on top of the current installation) that MAY work better for some people. Here's how:
1. Right click IS and select Patcher
2. Uncheck "Always patch" and close IS
3. Extract http://www.lavishsoft.com/downloads/Lavish.InnerSpace.5039.zip over your Inner Space folder

Your settings will be kept in tact.
<<

svaberendk

Posts: 5

Joined: Sun Aug 08, 2010 8:23 pm

Post Mon Aug 09, 2010 10:19 am

Re: Iboxer and Sony's Station Launcher problem

This is the info via the console using "diag". I should note i have also tried Inner Space Kernel 1.10 Build 5212


Inner Space Kernel 1.10 Build 5170

System:
-----------------------------------
Windows Version: Windows 7 Home Premium//7600.win7_gdr.100226-1909
Process Memory Usage: 51MB
System Physical RAM: 2912/4095MB
Page File: 6895/8188MB
Virtual Memory: 1857/2047MB (Extended: 0MB)
CPU 1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz @ 2500MHz
CPU 2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz @ 2500MHz
CPU 3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz @ 2500MHz
CPU 4: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz @ 2500MHz
CPU Affinity Mask: 0xF
Video 1: \\.\DISPLAY1/NVIDIA GeForce 9600 GT
Video 2: \\.\DISPLAY2/NVIDIA GeForce 9600 GT
Video 3: \\.\DISPLAYV1/RDPDD Chained DD
Video 4: \\.\DISPLAYV2/RDP Encoder Mirror Driver
Video 5: \\.\DISPLAYV3/RDP Reflector Display Driver
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 8.0.7600.16385

Loaded Modules:
-----------------------------------
Module 0x00400000-0x004B1000: C:\Program Files (x86)\InnerSpace\InnerSpace.exe (Sat Jul 03 19:40:58 2010)
Module 0x02540000-0x0255E000: C:\Program Files (x86)\InnerSpace\IS-D3D9Engine.dll (Mon Jun 28 13:02:18 2010)
Module 0x03000000-0x0318B000: C:\Program Files (x86)\InnerSpace\IS-Kernel.dll (Sat Jul 03 19:40:47 2010)
Module 0x04F30000-0x04F93000: C:\Program Files (x86)\InnerSpace\IS-VirtualInput.dll (Tue Jun 29 23:58:19 2010)
Module 0x05000000-0x0515F000: C:\Program Files (x86)\InnerSpace\ISUI.dll (Thu Jul 01 14:42:03 2010)
Module 0x10000000-0x1001E000: C:\Program Files (x86)\InnerSpace\Lavish.dll (Fri Apr 16 01:58:33 2010)
Module 0x60610000-0x60616000: C:\Windows\Microsoft.NET\Framework\v2.0.50727\fusion.dll (Thu Jun 04 05:16:14 2009)
Module 0x6F690000-0x6FF93000: C:\Windows\system32\nvd3dum.dll (Tue Jan 12 05:38:18 2010)
Module 0x6FFA0000-0x70163000: C:\Windows\system32\d3d9.dll (Tue Jul 14 01:04:41 2009)
Module 0x70170000-0x70527000: C:\Windows\system32\d3dx9_37.dll (Wed Mar 05 00:54:53 2008)
Module 0x70530000-0x70AC1000: C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll (Thu Jun 04 05:23:52 2009)
Module 0x71720000-0x717BB000: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCR80.dll (Thu Jun 04 04:52:15 2009)
Module 0x717C0000-0x71950000: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_72fc7cbf861225ca\gdiplus.dll (Tue Jul 14 01:03:50 2009)
Module 0x71950000-0x71BB7000: C:\Windows\system32\WMVCore.dll (Tue Jul 14 01:09:30 2009)
Module 0x72320000-0x72350000: C:\Windows\system32\DINPUT8.dll (Tue Jul 14 01:05:05 2009)
Module 0x72350000-0x7239A000: C:\Windows\system32\mscoree.dll (Fri Nov 06 05:09:24 2009)
Module 0x723A0000-0x723DD000: C:\Windows\system32\WMASF.DLL (Tue Jul 14 01:12:08 2009)
Module 0x72AC0000-0x72CD8000: C:\Windows\AppPatch\AcGenral.DLL (Tue Jul 14 01:03:54 2009)
Module 0x72DC0000-0x72DC9000: C:\Windows\system32\hid.dll (Tue Jul 14 01:05:48 2009)
Module 0x72DD0000-0x72DD6000: C:\Windows\system32\d3d8thk.dll (Tue Jul 14 01:04:40 2009)
Module 0x72DF0000-0x72E02000: C:\Windows\system32\MPR.dll (Tue Jul 14 01:07:02 2009)
Module 0x72E10000-0x72E1D000: C:\Windows\system32\sfc_os.DLL (Tue Jul 14 01:10:26 2009)
Module 0x72E20000-0x72E23000: C:\Windows\system32\sfc.dll (Tue Jul 14 01:10:25 2009)
Module 0x72E80000-0x72E92000: C:\Windows\system32\dhcpcsvc.DLL (Tue Jul 14 01:04:53 2009)
Module 0x72EB0000-0x72EC4000: C:\Windows\system32\MSACM32.dll (Tue Jul 14 01:07:26 2009)
Module 0x733B0000-0x733B6000: C:\Windows\system32\rasadhlp.dll (Tue Jul 14 01:09:42 2009)
Module 0x733C0000-0x733F8000: C:\Windows\System32\fwpuclnt.dll (Tue Jul 14 01:06:15 2009)
Module 0x73400000-0x73412000: C:\Windows\system32\pnrpnsp.dll (Tue Jul 14 01:10:14 2009)
Module 0x73420000-0x73430000: C:\Windows\system32\napinsp.dll (Tue Jul 14 01:07:57 2009)
Module 0x73430000-0x73438000: C:\Windows\System32\winrnr.dll (Tue Jul 14 01:11:32 2009)
Module 0x73440000-0x73450000: C:\Windows\system32\NLAapi.dll (Tue Jul 14 01:08:12 2009)
Module 0x73450000-0x73457000: C:\Windows\system32\WINNSI.DLL (Tue Jul 14 01:11:31 2009)
Module 0x73460000-0x7347C000: C:\Windows\system32\IPHLPAPI.DLL (Tue Jul 14 01:06:35 2009)
Module 0x73500000-0x73513000: C:\Windows\system32\dwmapi.dll (Tue Jul 14 01:06:15 2009)
Module 0x73520000-0x73564000: C:\Windows\system32\DNSAPI.dll (Tue Jul 14 01:05:29 2009)
Module 0x73570000-0x7357F000: C:\Windows\system32\samcli.dll (Tue Jul 14 01:09:47 2009)
Module 0x73A70000-0x73A87000: C:\Windows\system32\USERENV.dll (Tue Jul 14 01:11:13 2009)
Module 0x73D30000-0x73D35000: C:\Windows\System32\wshtcpip.dll (Tue Jul 14 01:11:54 2009)
Module 0x73D40000-0x73D7C000: C:\Windows\system32\mswsock.dll (Tue Jul 14 01:08:07 2009)
Module 0x73EE0000-0x73EEB000: C:\Windows\system32\profapi.dll (Mon Jul 13 23:12:01 2009)
Module 0x74000000-0x74080000: C:\Windows\system32\UxTheme.dll (Tue Jul 14 01:11:24 2009)
Module 0x74230000-0x7426B000: C:\Windows\system32\rsaenh.dll (Tue Jul 14 01:09:52 2009)
Module 0x74270000-0x74286000: C:\Windows\system32\CRYPTSP.dll (Tue Jul 14 01:07:09 2009)
Module 0x742A0000-0x742A9000: C:\Windows\system32\VERSION.dll (Tue Jul 14 01:11:07 2009)
Module 0x742D0000-0x7431B000: C:\Windows\system32\apphelp.dll (Tue Jul 14 01:04:54 2009)
Module 0x74760000-0x74765000: C:\Windows\system32\MSIMG32.dll (Tue Jul 14 01:08:48 2009)
Module 0x757D0000-0x757F5000: C:\Windows\system32\powrprof.dll (Tue Jul 14 01:10:36 2009)
Module 0x75800000-0x75832000: C:\Windows\system32\WINMM.dll (Tue Jul 14 01:11:30 2009)
Module 0x759E0000-0x759EC000: C:\Windows\syswow64\CRYPTBASE.dll (Mon Jul 13 23:12:01 2009)
Module 0x759F0000-0x75A50000: C:\Windows\syswow64\SspiCli.dll (Fri Dec 11 07:36:33 2009)
Module 0x75A50000-0x75AFC000: C:\Windows\syswow64\msvcrt.dll (Tue Jul 14 01:07:59 2009)
Module 0x75B00000-0x75B19000: C:\Windows\SysWOW64\sechost.dll (Tue Jul 14 01:10:28 2009)
Module 0x75B20000-0x75B4D000: C:\Windows\syswow64\WINTRUST.dll (Tue Dec 29 06:53:28 2009)
Module 0x75B50000-0x75C6C000: C:\Windows\syswow64\CRYPT32.dll (Tue Jul 14 01:07:05 2009)
Module 0x75C70000-0x75D0D000: C:\Windows\syswow64\USP10.dll (Tue Jul 14 01:11:14 2009)
Module 0x75D10000-0x75D22000: C:\Windows\syswow64\DEVOBJ.dll (Tue Jul 14 01:05:09 2009)
Module 0x75D60000-0x75E2C000: C:\Windows\syswow64\MSCTF.dll (Tue Jul 14 01:07:53 2009)
Module 0x75E30000-0x75F30000: C:\Windows\syswow64\USER32.dll (Tue Jul 14 01:11:24 2009)
Module 0x75FE0000-0x75FE6000: C:\Windows\syswow64\NSI.dll (Tue Jul 14 01:09:45 2009)
Module 0x75FF0000-0x76125000: C:\Windows\syswow64\urlmon.dll (Thu May 06 12:39:25 2010)
Module 0x76140000-0x76339000: C:\Windows\syswow64\iertutil.dll (Tue Jul 14 01:06:20 2009)
Module 0x76340000-0x763BB000: C:\Windows\syswow64\COMDLG32.dll (Tue Jul 14 01:06:45 2009)
Module 0x764C0000-0x76517000: C:\Windows\syswow64\SHLWAPI.dll (Tue Jul 14 01:10:29 2009)
Module 0x76520000-0x77169000: C:\Windows\syswow64\SHELL32.dll (Tue Jul 27 13:57:01 2010)
Module 0x77170000-0x771FF000: C:\Windows\syswow64\OLEAUT32.dll (Tue Jul 14 01:09:30 2009)
Module 0x77200000-0x7720C000: C:\Windows\syswow64\MSASN1.dll (Sat Aug 29 06:52:40 2009)
Module 0x77210000-0x773AD000: C:\Windows\syswow64\SETUPAPI.dll (Tue Jul 14 01:10:22 2009)
Module 0x773B0000-0x77410000: C:\Windows\system32\IMM32.DLL (Tue Jul 14 01:11:21 2009)
Module 0x77410000-0x77510000: C:\Windows\syswow64\kernel32.dll (Tue Jul 14 01:14:06 2009)
Module 0x77510000-0x775B0000: C:\Windows\syswow64\ADVAPI32.dll (Tue Jul 14 01:03:58 2009)
Module 0x775B0000-0x7770C000: C:\Windows\syswow64\ole32.dll (Tue Jul 14 01:09:27 2009)
Module 0x77710000-0x7771A000: C:\Windows\syswow64\LPK.dll (Tue Jul 14 01:11:23 2009)
Module 0x77720000-0x77747000: C:\Windows\syswow64\CFGMGR32.dll (Tue Jul 14 01:04:38 2009)
Module 0x77750000-0x77785000: C:\Windows\syswow64\WS2_32.dll (Tue Jul 14 01:11:38 2009)
Module 0x77820000-0x77910000: C:\Windows\syswow64\RPCRT4.dll (Tue Jul 14 01:11:23 2009)
Module 0x77910000-0x779A0000: C:\Windows\syswow64\GDI32.dll (Tue Jul 14 01:11:20 2009)
Module 0x779A0000-0x779E6000: C:\Windows\syswow64\KERNELBASE.dll (Tue Jul 14 01:14:07 2009)
Module 0x779F0000-0x77A74000: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16385_none_ebf82fc36c758ad5\COMCTL32.dll (Tue Jul 14 01:06:44 2009)
Module 0x77E50000-0x77E55000: C:\Windows\syswow64\PSAPI.DLL (Tue Jul 14 01:09:34 2009)
Module 0x77E80000-0x78000000: C:\Windows\SysWOW64\ntdll.dll (Wed Mar 24 06:35:08 2010)

Display
-------------------------------------
Driver Info: NVIDIA GeForce 9600 GT/nvd3dum.dll/8/17/11/9621
Adapter display mode: 1680x1050 D3DFMT_X8R8G8B8
Current display mode: 784x562 D3DFMT_X8R8G8B8 (windowed)
Window viewable size: 784x562
Display Scale: 100.0%x100.0%, Distortion: 0.0%
MaxFPS Foreground: 60 (Calculate)
MaxFPS Background: 30 (Absolute)
<<

svaberendk

Posts: 5

Joined: Sun Aug 08, 2010 8:23 pm

Post Mon Aug 09, 2010 11:58 am

Re: Iboxer and Sony's Station Launcher problem

I just tried a program called Keyclone with Vanguard and it crashes just as ISboxer does. Could it be the the Window layout styles that is somehow crashing it?. Keyclone uses a similar method of merging game windows for easy multiboxing.
<<

svaberendk

Posts: 5

Joined: Sun Aug 08, 2010 8:23 pm

Post Tue Aug 10, 2010 10:11 pm

Re: Iboxer and Sony's Station Launcher problem

I got it to load the game using build 5039. Now I have another issue with one of the two boxes being completely black ..it doesn't load like illustrated under windows layout either. I'm too tired tonight to experiment with it but will try tomorrow and see if I have my settings wrong or something. If I can't fix it myself I'll post again :)

Return to General

Who is online

Users browsing this forum: No registered users and 7 guests