Difference between revisions of "Supported Operating Systems"

From ISBoxer
Jump to: navigation, search
m (Windows 8 and 8.1)
m (Windows XP)
Line 4: Line 4:
  
 
Windows XP support is no longer maintained at this time.  We have moved on.
 
Windows XP support is no longer maintained at this time.  We have moved on.
 
  
 
'''ISBoxer requires [http://www.microsoft.com/downloads/en/details.aspx?familyid=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en Microsoft .NET Framework version 2.0, 3.0, or 3.5]''', which comes pre-installed on both Windows Vista and 7 but not on Windows XP.  
 
'''ISBoxer requires [http://www.microsoft.com/downloads/en/details.aspx?familyid=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en Microsoft .NET Framework version 2.0, 3.0, or 3.5]''', which comes pre-installed on both Windows Vista and 7 but not on Windows XP.  

Revision as of 10:38, 23 December 2018

ISBoxer and Inner Space are 32-bit programs (though a 64-bit version of Inner Space will be installed if desired) designed to run on 32-bit or 64-bit versions of Windows 2000 or later.

Windows XP

Windows XP support is no longer maintained at this time. We have moved on.

ISBoxer requires Microsoft .NET Framework version 2.0, 3.0, or 3.5, which comes pre-installed on both Windows Vista and 7 but not on Windows XP.

  • Installing .NET 4.0 or later will not help: Version 4.0 and later of Microsoft .NET Framework is installed separately from (and does not include) 2.0-3.5.

If this is not installed, ISBoxer will give the following error message: The application failed to initialize properly (0xc0000135). Click on OK to terminate the application

Windows Vista and Windows 7

If User Account Control (UAC) is enabled in Windows, ISBoxer and Inner Space will warn that you need to run them as Administrator. If UAC is set to "Never notify" and ISBoxer and Inner Space are not explicitly allowed, the software may fail to operate.

Because Inner Space will be running as Administrator, and Inner Space launches your games for you, the games will also be running as Administrator. This means that other applications that normally override or interact somehow with the game, including Ventrilo for its push to talk hotkey or input device software for button mapping, those applications may also need to be run as Administrator while multiboxing with ISBoxer.

Windows 8 and 8.1

Windows 8 support is no longer maintained at this time. We have moved on.

ISBoxer requires Microsoft .NET Framework version 2.0, 3.0, or 3.5, which comes pre-installed on both Windows Vista and 7 but not on Windows 8.1. However, instead of producing a cryptic error as on Windows XP, Windows 8.1 provides a helpful message with a button to help you install the required files.

  • If you get a message about installing .NET the first time you run ISBoxer on Windows 8.1, click the install button, it is correct!

Windows 10

Windows 10 is supported by Inner Space and ISBoxer.

Windows 10 and Inner Space/ISBoxer play nice together for the most part. Unless you're playing a 64-bit game, most likely you can upgrade to Windows 10 without any negative effects as far as ISBoxer is concerned. Many people have been using ISBoxer successfully on Windows 10 with no issues for several months.

There is one known issue that may mostly affect WoW players: 32-bit Inner Space cannot currently launch a 64-bit application, specifically on Windows 10. I will correct the issue as soon as possible, but I'm out of town until next week so have a little patience for now and use one of the following simple workarounds if you are having trouble launching the game on Windows 10 with ISBoxer:

  1. If you're playing a 64-bit game, you can launch 64-bit Inner Space, found under InnerSpace\x64\InnerSpace.exe. It will use all of your settings from the 32-bit version.
    • If you're playing WoW, you will then need to make sure Inner Space is pointing at WoW-64.exe and not WoW.exe -- You can edit your existing Game Profile (http://isboxer.com/wiki/Game_Profile) and just type in WoW-64.exe where it says WoW.exe.
  2. Alternatively (also for WoW here) you can continue using the 32-bit Inner Space, and make sure it is pointing at wow.exe instead, but add -noautolaunch64bit to the "Main Executable Parameters" in your Game Profile. For other games, you would similarly need to find the option to launch it in 32-bit mode only.

About DirectX 9, 10 and 11

Inner Space supports DirectX 9, 10 and 11, all of which come installed with Windows 7 and Windows 8. However, the first time you launch Inner Space on either Windows 7 or 8, you may get a message about a required DirectX update. This is because Inner Space requires a supplement to DirectX 9 (even for DirectX 10 and 11) that comes installed with the DirectX updates, and does not come pre-installed with any version of Windows (that's right, even Windows 8, which again comes with DirectX 9, 10 and 11...).

  • If you get this message about installing a DirectX update, the best course of action is to use the DirectX web updater from Microsoft as advised!
  • Note: DirectX 10 is currently only supported for 64-bit games

DirectX 12

DirectX 12 is not yet supported by Inner Space. When DX12 becomes available with Windows 10, support will be forthcoming; however, only games that are designed or updated to use DirectX 12 will need (or use) this support, in the same way that games currently use Direct3D 8, 9, 10, or 11 depending on their age and design.

See Also