FAQ

Answers to common questions on SplitView.

If this FAQ does not answer your question, let us know. We'll answer the question, and add it to the FAQ,


Installation

Yes, SplitView installation can be automated using SMS or Marimba.

SplitView installer accepts installation parameters and the license registration can be automated. The SplitView settings can be tweaked from HKLM\Software\SplitView and HKCU\Software\SplitView to provide full control of configuring SplitView during installation.

SplitView can be registered from the command line, using a syntax like:

SplitScr.exe register <Name>, <Key>

You can also suppress the "success" message-box by using QUIETREGISTER instead of REGISTER, but if you don't supply a valid name and key on the command line, the other dialogs will still be shown.)

By wrapping this command in a script, you should be able to easily register it in an automated fashion.

Alternatively, you can create an INI file called SplitScr.ini and place it in the same folder as SplitScr.exe. The INI file should have a [License] section containing the name and key, as shown below:

[LICENSE]
Key=<Name>, <Key>

If this entry is in the INI file, SplitView will try to silently enter the name and key you specify here when the program starts up. If it is successful, this line is removed from the INI file; if not, it is ignored. Note that the portion cannot contain spaces or any punctuation (other than the dashes that are part of a key to begin with). The comma between the name and key is optional, you can use a space instead if you wish.

The SplitView installer msi takes the following parameters:

HKLM - this property is disabled by default, and should be set to 1 for using the same settings for all users.

MULTIMON - this property is set to 2 for Terminal Server usage.
It should be set to 1 for Personal usage.

To install for all users, with the same settings for all users, in Terminal Server mode, the following command line can be used:
SplitView.msi ALLUSERS=1 HKLM=1 MULTIMON=2 /qn

When installing with per user settings, do not specify HKLM.

The SplitView installer can be configured to run in Personal Edition mode as well as Terminal Server more. This is an install option.

Additionally, the trial can be converted to licensed version by entering license key after purchase. The software will function differently based on the entered license key.

If a Personal Edition license is entered, only the Personal Edition features will be available, and SplitView will run for only one user on the computer. If a Terminal Server Edition or Site License key is entered, SplitView will enable the multi-user and Terminal Server features.

Sales

Yes, provided you are the only person accessing the work computer.

The SplitView options under "Multi-Monitor settings for remote Desktop/Citrix" are available when using the Personal Edition license. The Personal Edition license only allows one user to use SplitView on a computer at a time. It will not allow multiple users.

The computer being accessed with a Personal Edition license should be a workstation (i.e. not a Citrix or Terminal Server). You need one Personal Edition license for each (real or virtual) computer being accessed in this licensing mode.

SplitView should be installed on the computer/Terminal Server being accessed remotely, not the client PC where the remote session is accessed.

SplitView should be installed in 'Terminal Server mode' - this is an install option.

Users can connect to the terminal server where SplitView is installed using Remote Desktop client (version 6.0) in 'span' mode using the command line, as follows:
mstsc /span

For more details, please see here.

The site license covers the physical site of the Terminal Servers where SplitView is installed. Users may access these Terminal Servers remotely from anywhere, without requiring any additional SplitView licenses.

There is no yearly subscription fee for SplitView – it is purchased as a one time perpetual use license.

One year of free upgrades are included. If you buy now, you will get the latest update for free for one year.

The Personal Edition is licensed for one user, and does not allow multiple users to use SplitView on a server at a time. If you have only one user accessing the Terminal Servers with dual monitors, you may purchase Personal Edition license.

If more than one user will access the Terminal Servers, you should buy the Terminal Server license. If you have less than five people with multiple monitors connecting to a terminal server, we have a 5-user license for SplitView Terminal Services Edition that costs $199.00. This license may be purchased from the following URL:

http://www.regsoft.net/purchase.php3?productid=80463

We have partnered with RegNow, a leading e-commerce provider, to process purchase orders for SplitView. You may generate a formal invoice for SplitView and initiate the order from the URLs provided :

SplitView – Site License ($4980 per site):
https://www.regnow.com/softsell/nph-softsell.cgi?item=16972-2

SplitView - Terminal Services Edition ($729 per server):
https://www.regnow.com/softsell/nph-softsell.cgi?item=16972-1

Choose to buy using ‘Invoice’ for issuing PO.
Optionally, you may purchase SplitView online using Credit Card, Fax or over the phone using the information at the URL above.

Technical

SplitView can close automatically when all other Citrix published applications close, by adding the path to SplitScr.exe to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI

LogoffCheckSysModules=SplitScr.exe

When the last open normal app from that session is closed, Citrix will close SplitView and the session will be logged off.

We also have an application called SVclose.exe (download link) that can gracefully close SplitView when invoked. If you want to close SplitView through a batch file or script you can use this tool.

Yes, SplitView creates two instances of SplitScr.exe as part of it's normal operation.

It also creates one instance of SplitScrX64.exe on 64 bit systems.

You will need to publish SplitView by itself on the back-end server and start it prior to starting the other published applications. You can do so by publishing the 'start splitview' link from the start menu.

You can also create a batch file to point to the shortcut for SplitView then the shortcut for the app, and publish that. Many users find the batch file approach convenient. To start SplitView from a batch file, add the following commands in a batch file followed by commands to start the published application:

start /D "c:\Program Files\SplitView 2008\" splitscr.exe

OR

cd “c:\Program Files\SplitView 2008\"
start SplitScr.exe

To close SplitView automatically when all other Citrix published applications close, see the FAQ entry here.

One of the new features of the Terminal Server/Remote Desktop client in Windows Vista is the support for multiple monitors. This feature is also available in the Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP.

Microsoft’s Remote Desktop client (version 6.0) supports spanning across multiple monitors. Only some configurations are supported by Remote Desktop client in span mode. This is explained in a little more detail at:
http://blogs.msdn.com/ts/archive/2006/11/10/multi-monitor-support-in-the...

For this to work, SplitView should be installed on the computer/Terminal Server being accessed remotely, not the client PC where the remote session is accessed.

SplitView should be installed in 'Terminal Server mode' - this is an install option.

Only RDP 6.0 client supports spanning. Spanning is available on Windows XP as well as Vista. You can start the RDP 6.0 client in span mode using the command line, as follows:

mstsc /span
Span mode can also be configured in the RDP file by specifying “span monitors:i:1”

The client needs the following for span mode to work correctly:
o Equal resolution monitors
o Total resolution of all monitors not exceeding 4096 x 2048
o Top-left monitor being the primary

It is possible to span monitors with Remote Desktop with unequal resolutions, but requires some tweaking, as explained here.

When SplitView is installed on the remote computer being accessed using RDP in span mode, it will solve the problems that occur due to the desktop stretching across both monitors:
* When you maximize windows, they will maximize to just one monitor, not across both monitors.
* Windows will stop popping up in the middle of the two monitors. SplitView will cause them to appear on either the left or the right monitor, not in-between monitors.

Only some configurations are supported by Remote Desktop client in span mode. This is explained in a little more detail at: http://blogs.msdn.com/ts/archive/2006/11/10/multi-monitor-support-in-the...

The client needs the following for span mode to work correctly:
o Equal resolution monitors
o Total resolution of all monitors not exceeding 4096 x 2048
o Top-left monitor being the primary - the screen needs to be orientated [ 1 ] [ 2 ]

It is possible to span monitors with Remote Desktop with unequal resolutions, but requires some tweaking, as explained below.

Invoke remote desktop with the width and height arguments instead of span. Set the width to the combined width of your monitors, and set the height to the smallest monitor's height. For example, if you were using two monitors with 1680 and 1400 horizontal resolutions, use width=1680+1400=3080 and height=1050 (the smaller vertical resolution of the two monitors). Use the following on the command line to start remote desktop:

mstsc.exe /W:3080 /H:1050

You can reduce the height by a little bit to account for the local taskbar.

If the session came up maximized, un-maximize it.

Stretch(resize) the window to it’s full size and position so it fits both monitors from top to bottom.

The SplitView Options need to be configured as shown below:

Here you need to change the “Screen Division” so that the left monitor’s width is specified in “XXX” pixels on left, and use the second radio button instead of the first (which is for equal parts).

This will let you use Remote Desktop with two dual monitors of different resolutions. This works best if the height of the monitors is same or nearly same. If the height of the monitors is different, there is an empty spot on the larger monitor, that the terminal services client will not cover. This is more of a limitation of the RDP client than of SplitView.

SplitView should be installed on the computer/Terminal Server being accessed remotely, not the client PC where the remote session is accessed.

SplitView should be installed in 'Terminal Server mode' - this is an install option.

The SplitView buttons are disabled by default on Vista. To enable them, you can right click on the SplitView options, choose Options, and enable the buttons by checking the checkbox to “add the Go Left and Go Right buttons”. Please note that this option causes Windows to lose Aero transparency.

This can be done with SplitView. You need to use the keyboard shortcuts to move windows up or down.

Press Windows key + Up arrow (or number 8 on the number pad) to move a window to the top half of the screen.
Press Windows key + Down arrow (or number 2 on the number pad) to move a window to the bottom half of the screen.