Making InnerSpace X64 the default

I've been using the 64 bit version of IS, for the last few months without any issues (Win 8.1).

I have a shortcut to IS X64 that I use to launch the 64bit version of InnerSpace before I use my games shortcuts from IS Boxer. However, sometime I forget, what can I say I'm old

Is there a way or setting that allows IS Boxer to always use/load the X64 version of InnerSpace, if it's not already running, rather than defaulting to the 32bit ??

[bob]

You can set the Innerspace folder in the ISBoxer Profile to point to "C:\Program Files (x86)\InnerSpace\x64" instead of "C:\Program Files (x86)\InnerSpace". If you select the ISBoxer node at the very top left there you will see the Innerspace folder setting.

It may complain that a few files are not there, like your GameConfiguration.xml, but if you copy them from the "C:\Program Files (x86)\InnerSpace" folder it looks like it would all work.

n.b. I have only tried changing the folder, not actually launching all the processes.

Not entirely understanding what you mean, however, I don't have IS/ISB installed on the C: Drive. I have a C: Drive (SSD) exclusively for Windows, System Files and other essential components. All backed up to an external HDD, making life easier in the event of drive and/or system crash. I have a separate D: Drive - another SSD, exclusively for games. So IS/ISB are installed into D:\Games\InnerSpace. Inside this directory there is a x64 folder that contains 64 bit versions of InnerSpace.exe, dxNothing.exe and a bunch of .dll's but not IS Boxer.

Do you think if I just copy the x64 folder contents, after copying the 32bit versions of ISBoxer/dxNothing etc. and those dll's with the same name as their 64 bit equivalents to somewhere safe, (eg IS-D3D9.dll, IS-Kernal.dll) and run the 64bit ISB exe & dll's from the 32bit folder would work ? Although think about I'd guess I'd likely to run into issues with LavishPatcher.

If there is a configuration file some that contains the folder locations that I can change, could you tell me which of the many .xml files its likely to be in ?

[bob]

I referred to the default installation paths. If you are not on the default, substitute as necessary.



What I meant was select the ISBoxer node at the top of your profile, and then set the Innerspace folder.

It might complain that your GameConfiguration.xml file is missing (it did when I tried it as above). This is because it will be in the Innerspace folder. You might need to copy it to the x64 folder. Probably not though if you have normally configured Innerspace to run the x64 version. You will need to try it.

The reason I suggested the above is because when you then launch from ISBoxer, or create desktop shortcuts, it sets it up to use the above folder as the launch location, and use the Innerspace.exe in the x64 folder.

You shouldn't need to move dll's or anything else as the appropriate x64 versions will already be in the correct location. It is only the potential for some of the xml config files that might need to be copied. I would just do them one at a time as they get whinged about.

edit:
A test shows the following get whinged about.
ISBoxerToolkit.GeneralSettings.xml
ISBoxerToolkit.RepeaterSettings.xml
ISBoxerToolkit.MenuManSettings.xml
ISBoxerToolkit.KeyMapperSettings.xml
ISBoxerToolkit.Clickbars.xml

These are actually in the Innerspace\Scripts folder. I copied the Innerspace\Scripts folder to Innerspace\x64\Scripts and it all worked for the export, and the launch appears to be good. This is the only thing I needed to copy.
A Symlink might be a better option than copying, but idk.

Yep, just figured that out, made the change to D:\Games\InnerSpace\x64, copied over the .xml files, then saved and exported, and ended up with about a dozen exceptions thrown up - mainly System IO folder not found error messages, so I'm guessing that's something to do with locations specified in the .xml files.

So I've tried, after copying and renaming InnerSpace folder, copying the 64bit .exe &.dll folders, running ISboxer to save and export, which worked OK, then tried to run Everquest 2, which promptly failed with an "unable to launch" error.

So I guess, for the moment I'm stuck with launching InnerSpace (x64) manually, until Lax can figure a way to provide an option to launch/default to 64bit or 32 bit versions of InnerSpace.

Bob, thanks for your help so far.

[lax]

Pretty sure it's coded in to always read from InnerSpace/Scripts rather than ever read from InnerSpace/x64/Scripts.

Do you think if I just copy the x64 folder contents, after copying the 32bit versions of ISBoxer/dxNothing etc. and those dll's with the same name as their 64 bit equivalents to somewhere safe, (eg IS-D3D9.dll, IS-Kernal.dll) and run the 64bit ISB exe & dll's from the 32bit folder would work ? Although think about I'd guess I'd likely to run into issues with LavishPatcher.

You can turn "Always patch" off in the IS Patcher window if you want to go this route. The patcher will always suggest there's updated files available, so Inner Space will start with the main window open. You would want to minimize the window.

[bob]

Pretty sure it's coded in to always read from InnerSpace/Scripts rather than ever read from InnerSpace/x64/Scripts.

It was the Export to Innerspace which threw up the missing XML file errors. No idea if the actual game launching was reading from Innerspace\Scripts as I was using the same profile that I normally use, just with the changed path.

So you know I wasn't going mad.


The other error to overcome is


Oh, and it doesn't read the InputDevices.xml either (but doesn't tell me about it), so my Logitech G keys are no longer in the Hotkey Picker drop down.


I guess this is why with Windows apps we usually end up with various configuration files in the AppData folder or the My Documents folder, so then it doesn't matter what bitness exe is running.

Pretty sure it's coded in to always read from InnerSpace/Scripts rather than ever read from InnerSpace/x64/Scripts.

Do you think if I just copy the x64 folder contents, after copying the 32bit versions of ISBoxer/dxNothing etc. and those dll's with the same name as their 64 bit equivalents to somewhere safe, (eg IS-D3D9.dll, IS-Kernal.dll) and run the 64bit ISB exe & dll's from the 32bit folder would work ? Although think about I'd guess I'd likely to run into issues with LavishPatcher.

You can turn "Always patch" off in the IS Patcher window if you want to go this route. The patcher will always suggest there's updated files available, so Inner Space will start with the main window open. You would want to minimize the window.

Lax, Did try that, and although save and export worked, and it did launch the X64bit version of IS, Everquest2.exe through it's hands up in horror with the "failure to launch" error. I have no problem with EQ2, by launching IS(x64) manually, then running the ISBoxer shortcut, in fact playing now. It looks I'm almost there, but something isn't quite right.

Thanks for the reply.

[bob]

Ok, tested this and it seems to work nicely (note file paths are the defaults, use your specific installation paths if different).


1 Close ISBoxer and Innerspace
2. Open an Admin command prompt
3. Change directory to "C:\Program Files (x86)\InnerSpace\x64"
4. Run the following

mklink /d Scripts ..\Scripts
mklink GameConfiguration.xml ..\GameConfiguration.xml
mklink InputDevices.xml ..\InputDevices.xml

5. Open ISBoxer and set your Inner Space Folder setting in the ISBoxer Profile to be to the x64 folder.
6. If you are using Desktop shortcuts, you will need to recreate them after changing the Inner Space Folder setting, so the shortcuts will now point to the new Inner Space location



You will get the below message if Inner Space is not running when you try to Launch directly from within ISBoxer (i.e. right click on your Character Set and select Launch). You get this regardless of the x64/x86 version, and just after it shows up, Innerspace launches, so it appears to be a sequence thing. After Inner Space starts up, hit Launch again.




edit: fixed up the symlinks which I typed in around the wrong way... doh!.

Bob,
Ok just tried this, but to be clear, I'm supposed to be creating symlinks in my X64 folder to point to the existing Scripts folder and the 2 .xml files in the InnerSpace (32bit) folder. Yes ?

I followed your instructions exactly, navigating to (in my case) D:\Games\InnerSpace\X64 then using the command mklink /d ..\Scripts Scripts which fails with "Cannot Create a file when that file already exists" - same with the two .xml files.

However, if I switch things around with mklink using mklink /d Scripts ..\Scripts and likewise with the 2 xml files, the symlinks are created within the X64 folder, export and save works, (pointing ISBoxer to D:\Games|InnerSpace\X64), launched EQ2 successfully from the ISBoxer shortcut worked, BUT loaded the 32 bit version of InnerSpace.

Changed ISBoxer to point back to D:\Games\InnerSpace, save and export and launched EQ2 from it's shortcut. Again it worked and again it loaded the 32 bit version of InnerSpace. Also I'm not see the "Failed to pass command" Popup box on either try.

Finally, as a last resort I altered the properties in the shortcut to both launch InnerSpace and start in D:\Games\InnerSpace\X64, after changing ISBoxer to again use D:\Games|InnerSpace\X64, and bugger me, but it worked. I have the game running and defaulting to InnerSpace(x64)

I think it's cracked, and a big thanks for your assistance.