An on-screen keyboard is a software only approach that creates a virtual keyboard emulator. A keyboard image is visually displayed to the user, where the keys are "typed" (clicked) via the pointing device (whether mouse, trackball, pen, touchscreen, etc.). The software interfaces with the operating system, which is "told" that keystrokes are being generated (as if by a physical keyboard). Any underlying software application used by the operator then reacts as though the keystrokes were typed from a physical keyboard. This creates an entirely new way for computer operators to work with applications. For example, with a touchscreen interface and an on-screen keyboard, the user can operate the system without the need for a mouse or physical keyboard.
Original ID: IG223456

If you are asking this question, there is a good chance you don't - however, numerous companies around the world are taking advantage of the advanced human interface that allows interaction with a computer from one interface device. The intuitiveness of pointing & clicking that made the Graphical User Interface (GUI) so widely accepted, has evolved to become a complete solution by enabling names, passwords, and quick text/character entry via the pointing device utilizing an on-screen keyboard. With the advent of voice-recognition enabling dictation for extended text entry, the on-screen keyboard becomes an integral part of advanced systems. If you are a touch-typist and use your keyboard exclusively for word processing, you may never need an on-screen keyboard. However, this is only one of thousands upon thousands of uses for computers.
Original ID: IG223500

The original product developed in 1992 was My-T-Mouse - "My Typing Mouse". As time went by and the pen and touchscreen interfaces became more popular, we were questioned if our "Mouse" product worked with these devices - My-T-Pen and My-T-Touch were born. To address other virtual pointing device and technologies, My-T-Soft ("My Typing Software") was created - the name with no reference to any pointing device. Currently, My-T-Pen / My-T-Touch / and My-T-Soft (and numerous other private label versions) contain the same features, and are aimed at the commercial / industrial world. My-T-Mouse is for the home mouse / trackball user. OnScreen is the name for the Assistive Technology version of My-T-Soft (originally released as My-T-Soft AT).

As a software based virtual keyboard, our customers have requirements that address a wide-range of uses. Stop for a minute, and think about all the places in the world that have physical keyboards, keypads, or buttons. Then imagine all the flexilbility that a pure software implementation provides. Then realize that as individuals, specific needs and requirements can change for different applications. Finally add-in business and commercial aspects of creating an economically viable technological solution, and hopefully you can begin to appreciate why there are so many options.

For Windows, the 2 main options are My-T-Soft Professional and My-T-Soft Basic. My-T-Soft Professional contains both the original capabilities of the software as well as the Build-A-Board Run-time customization capabilities, while My-T-Soft Basic can only run Build-A-Board created layouts. If you only are going to run custom layouts, the Build-A-Board run-time licensing options or My-T-Soft Basic is all you need. If you need system logon and legacy capabilities, along with a full featured user interface/keyboard, then My-T-Soft Professional is what you want.

Original ID: IG223600

The standard retail product is licensed via Certificate of Authenticity, or electronically with unlock codes. As long as you go through the setup and use the License information provided, you should have no problems. The reason we license our software is to keep our prices reasonable - prior to the license schemes we dealt with legitimate users & companies who had no problem using the software without paying for each installation. This lost revenue prevented us from feeding our programmers, and they complained - as long as food, clothing, and shelter cost money, we need to charge for our licenses to support existing software, address the constantly changing computer industry, develop new desirable features, and continue to focus our efforts on productive endeavors.

IMG has been in business since 1995, and the only way to be successful for that long is to consistently provide value to our customers. We do understand that the license requirements sometimes affects our customers, but overall this is a relatively small inconvenience, and it is balanced by providing our customers with high-quality product & technical support (which is often appreciated!). We also appreciate all of our customer's efforts, and are always open to suggestions.

We have numerous licensing schemes to make our customer's lives as easy as possible, and have regularly updated the license process to resolve any issues. If you feel the licensing requirements on your part is difficult, please let us know - there may be an existing scheme available that will meet your needs.

Original ID: IG223700

For all support & technical issues, click to open Build-A-Board 2.10 Support information

My-T-Soft 2.10 was never released as a stand-alone product. The only way to obtain the software is from the run-time target for Windows in Build-A-Board. If you are trying to restore a system that had My-T-Soft 2.10, ideally you would obtain the software and custom keyboard layouts from the original Build-A-Board deployment. Alternatively, you can copy the software from a backup or a different system (if possible).

To license a new system, you need a Certificate of Authenticity with a MTS210?????? Serial number or will need to transfer the license - see Transfer a License (a serial number and license key are required to transfer a license).

The 2.20 release of Build-A-Board is the first to include targets for Linux, UNIX, and Mac OS X, along with Windows (95 thru 7) and Windows CE. It also is fully Unicode compliant, supports images on panels and keys, and provides many enhancements over the 2.10 capabilities. Custom on-screen keyboards and visual interfaces can be quickly and easily built, and then deployed on any supported target system. Application Integration is also easy & quick using the IMG Developer's Kit. Refer to the product pages or contact IMG for deployment and license options.

License Options

Build-A-Board 2.20 will still support run-time license options for users that need only 1 or a small number of licenses. The platform license options are based on company size and type of rollout required. Platform licenses cover the deployment OS, and are royalty free per device.

Because of the wide range of customers and differing requirements, we offer a wide range of license and usage options - if you don't see a satisfactory option, please contact IMG directly.

You should first select a Run-Time target before performing any build once the Builder is started.

The ;; (double semi-colon) as a line break for the Key Label is not documented. To obtain a line break on a key, use the ;; sequence within the text at the point you wish the line break to occur.

The Key Label {IMG:ACMD} is not documented. This presents the unicode character for the Apple Command character on the Mac OS X run-time (see Source examples: Mac Keyboard, Mac Large). This character is displayed in the Panel font, and it is not drawn internally like the other IMG: Key Label entries - it is a special label for the Mac OS X run-time. This is not supported on other platforms.

Linux run-times: will only type with 2.10 layouts, even though 2.20 layouts will display. Build-A-Board 2.20 projects must target ANSI 210 (MSWIN). New NKBF layouts must be different sizes to repaint correctly. The HiRes key type will not scale to the key size. PNG images work best with 24-bit color. Contact IMG for status if deploying Release 3 Linux run-times and 2.10 layouts aren't sufficient. (Refer to updated Linux run-times)

Many sample layouts from the previous 2.10 version do not have the Shifted Key Label set - as such, Caps and Shift will function correctly, but not change the displayed layout. For a working 2.20 samples, refer to the Keyboard Numpad Sample 2 or Windows CE Keyboard layouts.

Within the builder, multiple key selects for Key Hover/Key Press will not set back to None/0 - you must do individual keys.

For certain User Account Control settings in certain versions of Windows, the Run option after a build may not launch the test board. The Program Compatibility Assistant will establish this registry entry to allow normal operation:
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Program Files\\Build-A-Board\\BIN\\builderu.exe"="ELEVATECREATEPROCESS"

For certain custom DPI settings, the Key Properties dialog will not display a scroll bar, preventing access to all options. Use a standard DPI setting, or adjust your custom setting to allow proper display of the dialog.

If you do a 2.20 install over an existing 2.10 install, the TEST folder will have incorrect files, and the "Run My-T-Soft" option after successfully building a board will not operate correctly (Recommended to Un-Install 2.10).

The Key Action is limited to 128 characters, although using the zoom dialog allows longer macros, which can cause memory issues if longer macros are created - be sure to watch character limit and make sure macros remain less than 128 characters. If TypeFile/PlayMacro type external macros have non-character data (line feed/carriage returns/control characters) the macro may not work, and can cause the process macrobat in Linux to stop.

There is a system workaround for the issue noted in Build Process Notes in the User's Guide - see Tech Item PU2011120667

Running in Windows 8/8.1:
You will want to install on Windows 8, and then right-click on the Build-A-Board icon, select Properties | Compatibility Tab | Compatibility mode - Run this program in compatibility mode for: Windows 7. Also do this for the Licensing Information icon.

Running in Windows 10:
You will want to install on Windows 10, and then right-click on the Build-A-Board icon, select Open File Location (\Program Files\Build-A-Board\BIN) then do the following for BUILDERU.EXE, LICENSE.EXE, LICENSE2.EXE - select the file, right-click, select Properties | Compatibility Tab | Compatibility mode - Run this program in compatibility mode for: Windows 7.

There is no automatic way to select a platform when ordering on the web - contact IMG Customer Service to select a Platform license for your BAB220?????? License.

Note: The specifics are in regards to Windows platforms, but similar concepts apply to all platforms.

A critical aspect of the design of Build-A-Board and its run-time components is the ability to separate the Key Label (what the user sees), and the Key Action (what happens when the key is selected). The user-friendly Key Action for normal keyboard keys (i.e. A-Z, 1-9, etc.) typically uses the same character in Key Action as in the Key Label. This is intuitive, and in normal circumstances provides the builder and the end-user what they expect - click on a key labeled A, and get an A typed into the application they are typing into.

When working with different input locales in Windows, you have options for a floating tool bar, or using a tool on the system task bar that allows you to select the current input for the active window (i.e. the application that has the input focus). Each application can be assigned its own input locale. When the input locale changes, the same keystroke can generate different characters (based on the current input locale).

To accommodate the user-friendly Key Actions (i.e. the character is used rather than a scan code/virtual key code), a lookup is required. This lookup use the Windows API (specifically VkKeyScan) and takes place in the context of the input locale - but the actual input locale used for this lookup is critically important. There are various issues involved and has to do with the assignment of the default input locale to the process that is running. A physical keyboard is a system device, and remains static. So it always generates the same scan code, and how it is interpreted depends on the input locale for the current application that has the input focus. However, the virtual keyboard displayed by My-T-Soft is at its core, a process in the system, and bound by the way the system handles processes. When you run MYTSOFT.EXE it runs in the context of the current default input locale - which may or may not synchronize with a different locale/input as selected for another running application.

For example, let's say you want a Greek layout, but are testing on your development system that has an English default layout, and you select Greek when testing in Notepad. When you run MYTSOFT.EXE it will run (and look up keystrokes in the context of the English layout).

If you use the Greek alpha α character in both Key Label and Key Action, it will not operate correctly. It turns out the correct scan code gets looked up if the Key Action is a (rather than the Greek alpha α). So if you build a layout with the Greek alpha α and use a as the Key Action, it will type correctly when the App you are typing into is selected as Greek. On the other hand, if you put both the Key Label and Key Action as Greek alpha α, and then change the system to be default Greek, then run MYTSOFT.exe, it will type the Greek alpha α into a newly opened app (i.e. everything is in the Greek locale).

The scan code of 65 (hex 0x41) will generate an a in English and a Greek alpha α in Greek, so the better choice would be to just use this scan code (virtual key code) (e.g. %%s065) as the Key Action, because the lookup (which depends on the default locale for input) can change from system to system.

Because the Windows API is used and can change based on the user and system, the user-friendly Key Action as a character isn't as portable as specifying a key code - and much has to do that the "input" is an actual process running on the system rather than a system device.

You can download the IMG Developer's Kit, or just KEYWATCH.exe at ftp://downloads.my-t-soft.com/downloads/KEYWATCH.exe, and use that with different locales, the physical keyboard, and My-T-Soft to identify results based on different settings. This also can be used to identify the scan code (virtual key code) required.

One critical factor is the system default settings - if this is something other than what the builder system is running on, then testing the resultant layout on the actual target is critical to determine operation in that environment. As mentioned above, the approach of changing the input locale for the application works for key codes, but not lookups based on actual characters because of system process issues and the default input locale.

In order to provide backwards support for the 2.20.32 release that can run on Android 5.1 to 8.1 (API 22-27), and due to required code changes for updating to Android 9 (API 28), there are now 2 distinct Android releases. The original release and update notes continue after the notes on the current release.

This release is built targeting Android 9 (API 28), and no attempt was made to provide backwards compatibility. There were several key deprecated API calls that required updating the code, and with additional changes anticipated for Android 10, it made sense to take this targeted approach.

The main update revolves around adding an undocked, or floating keyboard option (under My-T-Soft Operation options). When enabled, the keyboard is displayed as a floating "popup" window, and with the appropriate move option (Keyboard Moving), it can be dragged as needed. It will still operate as any standard IME in terms of hiding and showing due to text input. Note that in Multi Window mode (where multiple windows are visible on the screen), the floating keyboard must be over the window you want to type into.

My-T-Soft for Android 2.20.102 (first Android 9 release, November 2020)

My-T-Soft for Android 2.20.32 Release Notes

The release has full support for 2.20 Unicode KBFs (Customized layouts / KeyBoard File) created with IMG's Build-A-Board, but there are a few limitations partially due to the limits of the Android platform and partially due to design choices during the development of the software.

Fonts - custom fonts specified in Build-A-Board are not carried through, and the default/system font is used for all text display. Additionally various logic is used to address key and board scaling and to ensure that all text fits into the available space.

Key Images - Key Image data selected and used in Build-A-Board is not used - the Key Image selections in the My-T-Soft Keyboard Settings | Key Images are used as overrides, and there is no way to select/use the Boards Key Image. Note that the HiRes Key Type and Key Image Frame is required to enable use of these Key Images on the device. For the Regular Key Type, the frame options and text/face/highlight/shadow colors are fully supported.

When the Revert to Default Layout on Long Key Press is On, this effectively disables the repeatable key type for backspace or delete, as holding down the key triggers the Long Key press event.

Keys - Caps aware/shift states are handled internally based on single letter Key Labels/Key Actions. Various keys (e.g. arrows) use text handling logic vs. generating actual keystrokes to be interpreted by the text control. Due to the nature of how keys are translated and interpreted, the interface should clearly be understood as a virtual keyboard vs. a keyboard/keystroke emulator. If there are specific key issues, please contact IMG Technical Support.

Keyboard Moving - this option will act differently on different devices, so it may not be the best choice for all situations. You will not be able to move a board off the top or sides, and this will limit the usefulness on smaller screens.

Undocked / Top of screen layouts prevent actual touch/clicks directly below the displayed keyboard layout window.

The 2.20.16 update supports base key events using the [CMD:KEYCODE=???] where ??? is a decimal number specifying an Android internal keycode (e.g. KEYCODE_1 is decimal 8). This also provides support for the %%knnn syntax for these Android virtual codes.

My-T-Soft for Android 2.20.32 (November 2018) - license issue when not in apk, support default layout from Build-A-Board.com account in addition to favorites.
My-T-Soft for Android 2.20.30 (September 2018) - addresses Long Press setting at device reboot.
My-T-Soft for Android 2.20.28 (September 2018) - correct Bar Code Scanner Interface setting for Zebra/Honeywell devices at startup / BOARDS folder logic to prevent KBF overwrites.
My-T-Soft for Android 2.20.26 (September 2018) -Scan Tab/Enter Key feature to handle as keystrokes or editor actions. Additional scanner.txt overrides (additonal 2 hardware key triggers, prefix/suffix options).
My-T-Soft for Android 2.20.24 (September 2018) - Additional support for Honeywell barcode scanners and scanner.txt overrides (hardware key triggers, trigger options, external scanner).
My-T-Soft for Android 2.20.22 (September 2018) - Additional support for Honeywell barcode scanners and auto-import options for account/preferences (My-T-Soft_Import folder).
My-T-Soft for Android 2.20.20 (August 2018) - Adds support for Honeywell barcode scanners and embedded license options.
My-T-Soft for Android 2.20.18 (July 2018) - Includes Force Visibility option and has Import/Export options for settings. Also support for Android 8 (Oreo)
My-T-Soft for Android 2.20.16 (June 2018) - Updates [F1] - [F12] interpretaton to be key events (F1 = Keycode 131, etc.) Also resolved key event constructor issue.
My-T-Soft for Android 2.20.14 (June 2018) - adds CMD:KEYCODE support for raw key events. (Also begins version tagging that odd versions are development, even versions are public releases)
My-T-Soft for Android 2.20.12 (March 2017) - adds Editor Input interpretation for tab and enter characters fed from DataWedge scanned data
My-T-Soft for Android 2.20.11 (November 2017) - adds logic for managing DataWedge profiles from within My-T-Soft
My-T-Soft for Android 2.20.10 (October 2017) - includes support for Zebra Technologies DataWedge utility (Bar code scanning)
My-T-Soft for Android 2.20.9 (first public release, September 2017)

The supported logon option for Windows 2000/XP is tagged as "My-T-Soft 2 Keyboard (Windows 2000 and later)" in the "My-T-Soft Logon Utilities" provided by the software. This feature uses an integration to the MSGINA.DLL (or possibly other third party GINAs, if so configured) where the software only monitors specified events (as supported by the Microsoft API for working within the GINA (Graphical Identification aNd Authentication)), so the keyboard can be shown during the logon screens, in the context of the secure WinLogon desktop. In short, this means that there is no security actions taken at all by our software - all that happens is the virtual keyboard is brought up within the GINA/WinLogon desktop, and can be used by the user to generate keystrokes for entering name/domain/password - ALL authentication takes place as it normally would by the underlying Microsoft software. The My-T-Soft software just provides a mechanism to enter text into the required fields in the secure WinLogon desktop.

The Secure Attention Sequence (SAS) is generated via the Microsoft provided API programming interface, so a physical keyboard Control-Alt-Delete keystroke is not required. However, the software does require a physical touchscreen press / mouse click event (assuming there are no other virtual event software capabilities present).

The security of this approach hasn't really been much of concern to those familiar with the technical aspects of what is going on at this level. Microsoft specifically publicly provides the GINA/WinLogon API for smart cards, biometric, and other identification schemes, but ALL authentication is done by the Microsoft software. In no way, shape, or form does this level have access to, or perform any authentication - My-T-Soft's particular implementation just provides a mechanism to enter the name/domain/password to the underlying security levels. So if you accept Microsoft's security, all that happens with the My-T-Soft software is it provides another way to enter the text (name/password) that is used to submit to the authentication system. Here is their documentation regarding this: MSDN - WinLogon and Gina

If there are further questions, or need for clarification, please contact IMG Technical Support.

With standard defaults, all user data (MYTSOFT.INI/KEYBOARD.KBF/Macro files) are saved in the Application Data area for the current user (for each user). For tools to find / Export / Import, use the File menu in My-T-Soft Setup. You can refer to the general information in the help for My-T-Soft Setup for details. When exported, all user data is compressed to a single zip file that is saved on to the desktop. This file can be saved/moved to a new system/installed version and used to import the old settings to the new installation of My-T-Soft. It is also a good idea to use this as a way to backup settings once you have everything configured the way you like it, and for people that invest a lot of time building macros.

My-T-Soft is My Typing Software - on-screen keyboards and user interface utilities used throughout the world - from individuals to global enterprises. Licensed by device, bundled with devices, and deployed with platform, site, company, and enterprise licenses.

There are many platforms, and it all started in 1993. Because some customers use validated systems that can run for many years, older versions continue to be supported and are still available - but the software continues to evolve to meet new customer needs. In order to meet all customer and market requirements, multiple products and feature sets are available. Below is a quick overview:

• My-T-Soft for Windows
  • My-T-Soft Professional
    • pre 1.90 - 1.xx software, be sure to match correct release version with your version of Windows (32-bit)
    • 1.90 - includes 1.xx and 2.xx software - Windows 11, 10, 8.1, 8, 7 (32-bit/64-bit)
      • Legacy software capabilities PLUS latest Build-A-Board run-time version (My-T-Soft original (1.xx) + My-T-Soft Basic (2.xx, Build-A-Board Run-time)
      • IMG License Manager can license from Build-A-Board.com account (internet) or via unlock codes (no internet required) or Build-A-Board Platform Licensing
  • My-T-Soft Basic
  • Build-A-Board run-time software with full install capabiltity (2.xx software) - Windows 11, 10, 8.1, 8, 7
  • This is the 32-bit Windows run-time for custom boards created by Build-A-Board
  • Includes IMG License Manager for per device licensing from Build-A-Board.com account (internet access required for licensing) or Build-A-Board Platform Licensing
  • My-T-Soft TS
    • Windows Server version (Terminal Server). Allows My-T-Soft to run on Remote Desktops, Terminals, Clients, etc. (1.xx and 2.xx software) 64-bit - Windows Server 2012, 2016, 2019, 2022
  • My-T-Soft CE
    • Various versions for Windows CE versions. Check with IMG for more info.
• My-T-Soft for Android
  • Support for Build-A-Board custom layouts - transparency, scaling, etc. (Android 5.1 and higher)
  • Licensed per device from Build-A-Board.com account or Platform Licensing.
• My-T-Soft for Linux
  • 32-bit/64-bit support for almost all Linux distributions with graphical Windows managers / Desktop Environments
  • Also Raspberry Pi (3 & 4 / armv6l, armv7l / raspbian) support
• My-T-Soft for Mac OS X
  • Mac OS X 10.4 and higher

With standard defaults, all user data (ONSCREEN.INI/KEYBOARD.KBF/Macro files) are saved in the Application Data area for the current user (for each user). For tools to find / Export / Import, use the File menu in OnScreen Setup. You can refer to the general information in the help for OnScreen Setup for details. When exported, all user data is compressed to a single zip file that is saved on to the desktop. This file can be saved/moved to a new system/installed version and used to import the old settings to the new installation of OnScreen. It is also a good idea to use this as a way to backup settings once you have everything configured the way you like it, and for people that invest a lot of time building macros.

The supported logon option for Windows 2000/XP is tagged as "My-T-Soft 2 Keyboard (Windows 2000 and later)" in the "My-T-Soft Logon Utilities" provided by the software. This feature uses an integration to the MSGINA.DLL (or possibly other third party GINAs, if so configured) where the software only monitors specified events (as supported by the Microsoft API for working within the GINA (Graphical Identification aNd Authentication)), so the keyboard can be shown during the logon screens, in the context of the secure WinLogon desktop. In short, this means that there is no security actions taken at all by our software - all that happens is the virtual keyboard is brought up within the GINA/WinLogon desktop, and can be used by the user to generate keystrokes for entering name/domain/password - ALL authentication takes place as it normally would by the underlying Microsoft software. The My-T-Soft software just provides a mechanism to enter text into the required fields in the secure WinLogon desktop.

The Secure Attention Sequence (SAS) is generated via the Microsoft provided API programming interface, so a physical keyboard Control-Alt-Delete keystroke is not required. However, the software does require a physical touchscreen press / mouse click event (assuming there are no other virtual event software capabilities present).

The security of this approach hasn't really been much of concern to those familiar with the technical aspects of what is going on at this level. Microsoft specifically publicly provides the GINA/WinLogon API for smart cards, biometric, and other identification schemes, but ALL authentication is done by the Microsoft software. In no way, shape, or form does this level have access to, or perform any authentication - My-T-Soft's particular implementation just provides a mechanism to enter the name/domain/password to the underlying security levels. So if you accept Microsoft's security, all that happens with the My-T-Soft software is it provides another way to enter the text (name/password) that is used to submit to the authentication system. Here is their documentation regarding this: MSDN - WinLogon and Gina

If there are further questions, or need for clarification, please contact IMG Technical Support.

The supported logon option for Windows 2000/XP is tagged as "My-T-Soft 2 Keyboard (Windows 2000 and later)" in the "My-T-Touch Logon Utilities" provided by the software. This feature uses an integration to the MSGINA.DLL (or possibly other third party GINAs, if so configured) where the software only monitors specified events (as supported by the Microsoft API for working within the GINA (Graphical Identification aNd Authentication)), so the keyboard can be shown during the logon screens, in the context of the secure WinLogon desktop. In short, this means that there is no security actions taken at all by our software - all that happens is the virtual keyboard is brought up within the GINA/WinLogon desktop, and can be used by the user to generate keystrokes for entering name/domain/password - ALL authentication takes place as it normally would by the underlying Microsoft software. The My-T-Touch software just provides a mechanism to enter text into the required fields in the secure WinLogon desktop.

The Secure Attention Sequence (SAS) is generated via the Microsoft provided API programming interface, so a physical keyboard Control-Alt-Delete keystroke is not required. However, the software does require a physical touchscreen press / mouse click event (assuming there are no other virtual event software capabilities present).

The security of this approach hasn't really been much of concern to those familiar with the technical aspects of what is going on at this level. Microsoft specifically publicly provides the GINA/WinLogon API for smart cards, biometric, and other identification schemes, but ALL authentication is done by the Microsoft software. In no way, shape, or form does this level have access to, or perform any authentication - My-T-Touch's particular implementation just provides a mechanism to enter the name/domain/password to the underlying security levels. So if you accept Microsoft's security, all that happens with the My-T-Touch software is it provides another way to enter the text (name/password) that is used to submit to the authentication system. Here is their documentation regarding this: MSDN - WinLogon and Gina

If there are further questions, or need for clarification, please contact IMG Technical Support.

With standard defaults, all user data (MYTTOUCH.INI/KEYBOARD.KBF/Macro files) are saved in the Application Data area for the current user (for each user). For tools to find / Export / Import, use the File menu in My-T-Touch Setup. You can refer to the general information in the help for My-T-Touch Setup for details. When exported, all user data is compressed to a single zip file that is saved on to the desktop. This file can be saved/moved to a new system/installed version and used to import the old settings to the new installation of My-T-Touch. It is also a good idea to use this as a way to backup settings once you have everything configured the way you like it, and for people that invest a lot of time building macros.

The supported logon option for Windows 2000/XP is tagged as "My-T-Soft 2 Keyboard (Windows 2000 and later)" in the "My-T-Pen Logon Utilities" provided by the software. This feature uses an integration to the MSGINA.DLL (or possibly other third party GINAs, if so configured) where the software only monitors specified events (as supported by the Microsoft API for working within the GINA (Graphical Identification aNd Authentication)), so the keyboard can be shown during the logon screens, in the context of the secure WinLogon desktop. In short, this means that there is no security actions taken at all by our software - all that happens is the virtual keyboard is brought up within the GINA/WinLogon desktop, and can be used by the user to generate keystrokes for entering name/domain/password - ALL authentication takes place as it normally would by the underlying Microsoft software. The My-T-Pen software just provides a mechanism to enter text into the required fields in the secure WinLogon desktop.

The Secure Attention Sequence (SAS) is generated via the Microsoft provided API programming interface, so a physical keyboard Control-Alt-Delete keystroke is not required. However, the software does require a physical touchscreen press / mouse click event (assuming there are no other virtual event software capabilities present).

The security of this approach hasn't really been much of concern to those familiar with the technical aspects of what is going on at this level. Microsoft specifically publicly provides the GINA/WinLogon API for smart cards, biometric, and other identification schemes, but ALL authentication is done by the Microsoft software. In no way, shape, or form does this level have access to, or perform any authentication - My-T-Pen's particular implementation just provides a mechanism to enter the name/domain/password to the underlying security levels. So if you accept Microsoft's security, all that happens with the My-T-Pen software is it provides another way to enter the text (name/password) that is used to submit to the authentication system. Here is their documentation regarding this: MSDN - WinLogon and Gina

If there are further questions, or need for clarification, please contact IMG Technical Support.

With standard defaults, all user data (MYTPEN.INI/KEYBOARD.KBF/Macro files) are saved in the Application Data area for the current user (for each user). For tools to find / Export / Import, use the File menu in My-T-Pen Setup. You can refer to the general information in the help for My-T-Pen Setup for details. When exported, all user data is compressed to a single zip file that is saved on to the desktop. This file can be saved/moved to a new system/installed version and used to import the old settings to the new installation of My-T-Pen. It is also a good idea to use this as a way to backup settings once you have everything configured the way you like it, and for people that invest a lot of time building macros.

Notes:

• Depending on product, release version, OS version, and specific technical issue, some tech items are very specific, and some may span to other products/versions
• Downloadable files can also be accessed by anonymous FTP at ftp://downloads.imgpresents.com
• Older files are moved into a separate archive location - see notes/details/new location in *.archived.txt text file

• Return to Technical Support

As seen in ...