KMremoteControl for PC/Windows 1.23 2004-Jan-05 ===== Thank you for downloading KMremoteControl, the program that lets you use one system's keyboard and mouse to operate all the PCs and Macs on your desk. We hope you find that it adds value to your computing experience. What Does KMremoteControl Do? ----- In short, KMremoteControl enables you to operate/"remote control" all the PC/Windows and/or Mac OS X systems from the keyboard and mouse on one of those systems. If you have multiple such computer systems on your desk, KMremoteControl: * enables you to operate all the systems from the keyboard and mouse on one of those systems (especially useful for laptop users) * enables you to recover the space used by multiple keyboards, mice and mouse pads * lets you use your preferred keyboard and mouse - increased comfort (may reduce repetative stress injuries) - increased productivity - use your Mac's keyboard/mouse to run a PC - use your PC's keyboard/mouse to run a Mac * can save money when working with multiple systems located on your desk - no need to buy a KVM switch * lets you use your preferred seating position and location - use the location that provides the best lighting - stop shuffling back and forth ... save your carpet! * when used in conjunction with ClipCommControl: - automates clipboard transfers between Mac OS X systems System Requirements ----- KMremoteControl operates "cross-platform" and runs on: Windows 2000 and XP and later Macintosh OS X 10.2 and later KMremoteControl requires that the computer systems be connected to a network. Integration with our ClipCommControl product is currently only supported for Mac OS X. Installing KMremoteControl ----- To install KMremoteControl, simply: PC/Windows: Run the downloaded setup application (e.g., KMremoteControl1.00Setup.exe). It is a self-extracting executable that runs the installer. If appropriate, you'll be given the opportunity to remove the version of KMremoteControl that is currently installed. Follow the installer's instructions to complete the installation. Mac OS X: Drag the KMremoteControl application from the disk image to a folder of your choosing (e.g., the Applications folder). Other than its preference files (located in your home folder's Library/Preferences folder and the /Library/Application Support/LicenseControl folder and /Library/Preferences folder), KMremoteControl does not install any files outside it's own application/package structure. On Mac OS X, the first time you use KMremoteControl, it will ask for the Administrator password. This is required in order to create the "/Library/Preferences" entry and the "LicenseControl" folder in the "/Library/Application Support" folder and to set the file permissions on both the "/Library/Application Support/LicenseControl" folder and its contents and the KMremoteControl application package and it's contents. This is required so KMremoteControl can operate properly. Setting Up and Using KMremoteControl ----- The keyboard mapping between PC and Mac keyboards is: * ALT <=> CMD (Alt key and Command/Apple key are equivalent) * WIN <=> OPT (Windows key and Option key are equivalent) * I.E., the keyboard mapping is based upon physical position Install and start KMremoteControl on all the systems that are to remote control another system(s) or are to be remote controlled by another system. Setting up systems that will be remote controlled by another system: * on the Being Controlled tab in the Preferences, choose one of the Permit this system to be remote controlled... options in the Activation section * on the KMremoteControl application window, press the Enable button in the Being Controlled section and the Status: in the Being Controlled section will indicate that "this" system can be controlled Using a system to remote control another system: * enter the the IP address (e.g., 192.168.1.100) or Windows computer name or the (fully qualified) domain name (e.g., mySystem.myDomain.com) of another system you set up to be remotely controlled (see the KMremoteControl Help for additional naming options and more detail about which system naming applies in different situations) * either press the Activate Remote Control button on the KMremoteControl application window, or use the "hotkey" indicated to the right of the Activate Remote Control button and the Status: in the Remote Controlling section will indicate which system you are controlling For information about the preferences, application operation and menus, select the KMremoteControl Help item on the Help menu while in KMremoteControl or visit http://www.derman.com/. *** If you are using firewall software, see http://www.derman.com/KMremoteControl1.00/KMrC-FAQ.html for information about setting up firewalls to allow KMremoteControl to operate. Mac OS X Only: Using Switcher and Other Hotkeys with KMremoteControl ----- When controlling a system from a Mac OS X system, certain keys will be processed by the operating system and provided to other applications. This is actually a feature and operates beyond KMremoteControl's control. As such, certain keystrokes will be processed by other applications, regardless of what KMremoteControl might prefer. Application switcher "hotkeys" are a prime example of this situation. This means that if you use an application switcher hotkey (e.g., cmd-tab), it will be processed by OS X's application switcher with the result being that the KMremoteControl application will be placed in the background and some other application will be brought into the foreground. If you wanted to switch the application on the remotely controlled system, this is not what you get. To support application switchers and other uses of (OS-registered) hotkeys that are used by various applications, you can use a combination of features to establish two different operational modes. However, please note that, regardless of what KMremoteControl does, the hotkey will still be sent to all applications that have registered to receive it and they will still "do their thing" on the controlling system. There is nothing (we know of) that can prevent this. Operational Mode 1: use different switcher keys on the controlling system and the system being controlled. This mode has the advantage of allowing you to use a switcher keystroke to switch to other applications on both the controlling system and the controlled system. It has the disadvantage that you need to use two different switcher keys. To set up your controlling system to use this mode: * uncheck/turn off the option Keep KMremoteControl in front, while controlling, located in the Activation and Presentation section of the Remote Controlling preferences Operational Mode 2: use the same switcher key on the controlling system and the system being controlled. While this mode allows you to use identical switcher keys, which many people find desirable, it also has the following characteristics: * applications will still get "switched to" on the controlling system, but will immediately be switched out by KMremoteControl * to switch out of KMremoteControl you deactivate remote control To set up your controlling system to use this mode: * check/turn on the option Keep KMremoteControl in front, while controlling, located in the Activation and Presentation section of the Remote Controlling preferences * press the Edit Key Substitutions... button on the KMremoteControl application window (or select the Key Substitutions... entry on the Edit menu) * press the Add button on the Key Substitutions window * specify the keystroke you use as your switcher keystroke * check/turn on the This key combination is also defined as a hotkey item * press the Next button * (again) specify the keystroke you use as your switcher keystroke (it will be the same as in a previous step) * press the Done button If you have other "hotkeys" that are defined in various applications, you may also want to set up additional key-substitution entries. In addition, you may also want to set up other key-substitution entries. For example, you can define entries to send function keys that you don't have on your laptop's keyboard and/or you can define a keystroke, say ctrl-option-cmd-esc that will send opt-cmd-esc to enable you to invoke the "force quit" dialog on a Mac OS X system being controlled (since the operating system will not supply opt-cmd-esc to other applications). Licensing KMremoteControl ----- Install KMremoteControl as indicated above then: * purchase the required number of licenses (see below) via http://www.derman.com/ * start KMremoteControl and select the Licensing... item under the KMremoteControl menu * open your Kagi email containing your KMremoteControl License ID and select/copy the License ID * paste the License ID into the License ID entry box on the Licensing window * press the Install a License button on the Licensing window KMremoteControl licenses are cross-platform: * a License ID works the same on either PC/Windows or Mac OS X * licenses can easily be moved from one system to another (KMremoteControl uses our LicenseControl product) To move a license from one system to another: * start KMremoteControl and select the Licensing... item under the KMremoteControl menu * press the Relinquish a License button to remove the license from that system * follow the instructions, above, to install/re-use the License ID on another system How Many KMremoteControl Licenses Do I Need? ----- One KMremoteControl License enables one PC/Windows or Mac OS X system to remote control another PC/Windows or Mac OS X system that is running a licensed KMremoteControl (and vice versa). That is, one license is required per participating system (either controlling and/or being controlled) so a minimum of two licenses are required to use the software. When using ClipCommControl to add Mac OS X clipboard sharing that is limited to sharing only when activating and deactivating KMremoteControl, you require a licensed ClipCommControl only on the systems being remotely controlled (i.e., not on the system from which you are doing the remote controlling). As always, you can easily move a license to any applicable system. You are in control. KMremoteControl can be purchased both as a 2-license "Starter Pak" and as a 1-license "Add-On" (see http://www.derman.com/). Updating or Re-Installing KMremoteControl ----- If you currently have a licensed KMremoteControl on your system, simply install the updated version as indicated above then: * start KMremoteControl and select the Licensing... item under the KMremoteControl menu * use the Reinstall an Existing License button on the Licensing window Evaluating KMremoteControl ----- When you first install and use KMremoteControl, it will be running in Trial mode where it has the following limitations: * both the controlling system and the controlled system will quit after 15 minutes of operation, but you are welcome to restart and continue your evaluation at that time * if either the controlling system and/or the controlled system are unlicensed, once they have communicated, both will operate as though they are in Trial mode (even if one is licensed) * the Trial will expire 4 weeks after being installed KMremoteControl will remind you of these limitations, when applicable. On Mac OS X, where appropriate, KMremoteControl presents tooltip-style help whenever the cursor is stationary, for the required duration, over an item. On PC/Windows and Mac OS X, the Help menu provides access to the HTML-style documentation. The documentation's "web" pages are contained within the application and are also available at: http://www.derman.com/. Note that there are non-documentation links within the documentation pages that will require an Internet connection to access. Only the specific product-documentation page-links are accessible, locally (i.e., without Internet access). Purchasing KMremoteControl ----- When you are satisfied that KMremoteControl has value, you can purchase a License ID for KMremoteControl via http://www.derman.com/ (we use the fine e-store services provided by Kagi). Once you have received your License ID from Kagi (via email) and the notification message from our licensing server, you can license KMremoteControl as indicated above. More Information ----- For the product documentation, select the KMremoteControl Help item on the Help menu while in KMremoteControl. More information about KMremoteControl, including the current History, Frequently Asked Questions, Known Issues and complete detail regarding the licensing process, can be found at: http://www.derman.com/. KMremoteControl Release History ----- KMremoteControl 1.23 (2004-Jan-05) : * helps prevent a problem where some systems would experience intermittent license failures due to bogus and multiple MAC addresses being reported by that system's APIs * fixed a problem where a license could not be installed with some proxy setups KMremoteControl 1.22 (2003-Oct-23) : * fixed a problem where some systems could intermittently be incorrectly identified, causing intermittent license failures * fixed a problem where a license could not be installed with some proxy setups KMremoteControl 1.20 (2003-Sep-22) : * added ability to maintain a collection of keystroke substitutions that cause a keystroke on the controlling system to be sent as a specified keystroke to the controlled system * added an option to keep KMremoteControl in front, when remote controlling, to allow full use of application switcher keys * added an option to support a single-button mouse by sending a right-click instead of a control-click when controlling a PC/Windows system * significantly reduced KMremoteControl's startup time KMremoteControl 1.10 (2003-Sep-15) : * a loss of license due to disk defragmentation is now identified and an option is presented to allow the license to be automatically reinstalled KMremoteControl 1.10 (2003-Sep-09) : * added two new options that, when used together, cause the activation/deactivation hotkey to "activate and show" then "deactivate and hide", thus keeping KMremoteControl available but out of the way when it's not activated * added an option to invoke a workaround necessary for some interfering, third-party, mouse/tablet drivers * improved smoothness of response under conditions of heavy processor load * fixed a problem that could cause interruption of remote controlling * fixed a problem where being controlled could not be easily disabled KMremoteControl 1.00 (2003-Sep-03) : Initial release. ___ Acknowledgments Portions of the code in this product are: Copyright (c) 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved. (See then Copyright.rtfd file inside the application package, for more information) ___ Any trademarks mentioned herein are the property of their respective owners. Copyright 2003-2009 Derman Enterprises Inc., All Rights Reserved