Windows 8 is internally tagged as Version 6.2, and is essentially an update to Windows 7 (Version 6.1). In fact, it primarily is Windows 7 with the added "Metro" interface (or new Start Menu), with tiles and a separate mechanism for tile-based applications.

For proper operation, the IMG Standard Download as a self-extracting installation executable should be used. Program files must reside in the \Program Files (or \Program Files (x86) location for 64-bit) for correct operation in Windows (security/user-interface requirements in Windows 8).

• Additional Notes and product details regarding Windows 8
• Refer to the detailed notes on Windows 7 for common issues that also affect Windows 8
• Use Joystick-To-Mouse 2.80 for best results in Windows 8 - for 2.70, refer to: Joystick-To-Mouse 2.70 with Windows 8
• To appear at the Start Screen (Windows 8 Start Menu), the program must be executed from a secure location, e.g. \Program Files. If you download and run from your desktop (for example), the EXE will get an Access Denied result for uiAccess, and will not appear at the Start Menu (while if run from the \Program Files location, it will)
• There has been a report with an installation/operation conflct with Logitech SetPoint 6.61 - check with Logitech for updates/details.

Information on Windows

Windows Vista Information
Windows 7 Information
Windows 8 Information
Windows 10 Information

Windows 10 is internally tagged as Version 6.2 for executables without manifests for Windows 10, and is essentially an update to Windows 8.1 / Windows 8 (all tagged version 6.2)

For proper operation, the IMG Standard Download as a self-extracting installation executable should be used. Program files must reside in the \Program Files (or \Program Files (x86) location for 64-bit) for correct operation in Windows (security/user-interface requirements in Windows 10).

July 31, 2015 - The original Windows 10 release and IMG's Windows 8.1 release versions may be delayed at the final step of Setup during the installation process. Newer releases tested against the Windows 10 releases will resolve this delay - it may take several minutes, so please be patient and allow Setup to complete.

Information on Windows

Windows Vista Information
Windows 7 Information
Windows 8 Information
Windows 10 Information

Steps required to do customized painting
My-T-Touch used as an example

• 1) Download and install [and license if a permanent install] My-T-Touch
• 2) Install Developer's Kit
  • Go to Start Menu | Programs | My-T-Touch | Install Developer's Kit
  • If installed from CD, you can skip the update section that follows:
  • Check for Updates
  • Select "IMG Developer's Kit 1.78 Release 3"
  • Click on Next, then Next
  • Then click Finish, and then OK after finished downloading
  • Now: Extract Developer's Kit
• 3) Review the Paint DLL docs in the Developer's Kit Help for reference & more details on the following steps
• 4) Modify MYTTOUCH.INI
  • Go into My-T-Touch Setup | Configuration | Special Options | Edit My-T-Touch Initialization File
  • Then copy and paste this (from the Paint DLL overview in the Developer Kit documentation) into MYTTOUCH.INI at the end:

  [PaintDLL]
  
  DLLName=%PRODDIR%\PaintDLL\Release\PaintDLL.DLL
  PaintFrame=1
  PaintFrameFunc=PaintDLLPaintFrame
  PaintKey=0
  PaintKeyFunc=PaintDLLPaintKey
  PaintKeyBackground=1
  PaintKeyBackgroundFunc=PaintDLLPaintKeyBackground
  PaintKeyModBackground=0
  PaintKeyModBackgroundFunc=PaintDLLPaintKeyModBackground
  PaintKeyLabel=1
  PaintKeyLabelFunc=PaintDLLPaintKeyLabel
  

  Now Save the file
• 5) Make a few other changes in My-T-Touch Setup
  • Configuration | Keyboards | 104 United States Standard
  • Configuration | Size | 11, then OK
  • Configuration | Panels | Check 2 panels: Keyboard (ABC) Panel, and Edit Panel
  • then OK, OK, Exit
• 6) Open Visual Studio 6, or 2005, or 2008, and build PAINTDLL.DLL (make sure the Release folder matches the build location if converting to something newer than Visual Studio 6).
  
  Copy the PaintDLL\GrayKeys bitmaps into the PaintDLL folder (save the reddish key bitmaps to a subfolder if you wish to use these) (or make your own)
  
  Open the workspace PaintDLL.dsw (or convert)
  
  Now build the project (Build | Rebuild All) / solution (make the file PAINTDLL.DLL)
  Based on the DLLName entry used above, it should end up here: \Program Files\MYTTOUCH\PaintDLL\Release\PaintDLL.DLL
  
• 7) Run My-T-Touch

Here you can go into the menu (right-click Menu | Current Settings | Panels | Clear Tool bar), and you will have the keyboard shown on the website

If the programming aspect is beyond your skills, too difficult, or not desirable, then you can review options in IMG's Build-A-Board. Also, please feel free to contact us with your requirements. Note that graphics and making really neat looking keyboards has never been a high priority from our customers in the 16 years we've been providing on-screen keyboards. Almost all of our customers want (or demand) highly reliable, functional software. Because of the myriad of different systems, with vastly different video and graphics capabilities, keeping the graphics simplistic and functional have been more important than producing visual effects - eye-candy and visual display is relatively easy, while producing highly reliable software for all types of environments is a challenge. Even as recent as 2008 we've had customer issues with the built-in 3D key display option (due to rendering speed). Since many older systems and low cost systems don't have high powered video subsystems, keeping things simple seems to work better in practice.

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)

In order to make downloading & demonstrating IMG software as simple as possible, a single file, self-extracting, self-installing file approach is used, and is the preferred method of download software (see below for other methods).

• If you are having trouble downloading, review these items:
• Verify your internet connection is active/operational - try browsing to other websites, and verify they load as they normally would
• See if the IMG Downloads server is up and available - browse to the FTP site ftp://downloads.imgpresents.com
• Verify your hard disk is not full - if there is insufficient room to load the download file, it will fail
• Restart your system - There could be memory issues, conflicts, other configuration issues that will vanish if you reset/restart your system and reload the Windows operating system
• See details below - more information follows and covers more details on the specifics of the downloadable software and the installation approach.

Products that have versions that are different for different versions of windows have a Smart Download option - this single file runs, senses the version of windows, then downloads and runs the appropriate download. You do require internet access on the system you want to download the IMG software to use this option. If you are downloading for a different system, or will move the software before installing, you cannot use the Smart Download option. Below the Smart Download option, click on the link labeled with "To see all download options (EXE, USB, U3, MSI, Zip, etc.), click here " - the page will refresh, and there will be distinct links for ALL download options. Then select the correct file for the version of Windows you will install on, and your browser will prompt you to run or save the file. Save the file, and note the saved location. When ready to install, double-click or open the install file (EXE/MSI). If the standard EXE download does not work on your target system, try the MSI version.

The following is the general approach (along with some known issues) used by the downloaded files:

• The entire file must be downloaded & saved onto your hard disk (or network) prior to running the file.
• Note the location you are saving the file when prompted by your browser - you will need to use Windows Explorer, or specify this location to run the file after the download is complete.
• When the downloaded "EXE" file is executed it does the following (issues included in bold)
• The program checks the System Environment for a TEMP= setting (Environment Variable TEMP)
• If the TEMP setting exists, and there is at least 2MB free space, the first extraction expands into this location.
• If the TEMP setting does not exist, the software attempts to make an IMGLOAD folder in the Windows directory (e.g. C:\WINDOWS or C:\WINNT) Permissions or security issues can prevent this step from occurring - you may need an Administrator to extract the downloaded file!
• The following is for the EXE option - if unable to use the EXE option, try the MSI file
• The first extraction step creates files in the TEMP folder (as set in the environment) with a SETUP.EXE, INSTALL.XML script, and a PKG file (compressed package of files)
• The second extraction is performed by executing the SETUP.EXE file, and the install script is run, creating a folder in Program Files, copying, extracting, and deleting the package file, and then unzipping and performing post installation steps (such as Program Group for menus, desktop icon, licensing, etc.) Permissions or security issues can create issues, along with Read-Only attributes or files in use - For example, having a SETUP.EXE file in the TEMP folder copied from a CD may leave a SETUP.EXE file in the TEMP folder with a Read-Only attribute - when the extraction tries to write the IMG SETUP.EXE, it will fail. When the next phase occurs (i.e. running SETUP.EXE), the existing SETUP.EXE will be executed, and will leave the user dazed & confused, since they will see something quite unexpected. If something unexpected occurs at this point, remove all files from your TEMP folder, then start over.
• After the Setup program has completed its task, cleanup begins - all extracted files are deleted, and the system is restored to its original state. Note that the original downloaded file is left intact - you can either manually delete it, or store it in a Downloads file for future use.

Original ID: IW400319

This approach is becoming less common as CD-Rs are becoming cheaper, and floppy drives are getting harder to find. The following touches on a few key issues:

• The downloaded zip files are images of the files that below on the appropriate floppy disk.
• The intent is to extract the Disk 1 onto a floppy labeled Disk 1. Disk 2 onto a floppy labeled Disk 2.
• If you extract on a hard disk, all files should be extracted to the SAME FOLDER!
• ALL zips must be extracted before running SETUP.EXE

Original ID: IW400320

• Verify you have the most up-to-date and correct pointing device driver for your system
• Application Focus / input focus / typing into the desired window - most issues are caused by multiple windows or external manipulation of windows or use of the Developer's Kit. Refer to documentation in the Developers Corner. Also check the My-T-Soft Setup | Configuration | Operation Options & Help for more options in working with various input devices.
• ELO TouchSystems (95/98/Me/NT) - "Track Pointing Device Input at All Times" MUST be checked on to operate with ELO drivers - see My-T-Soft Setup | Configuration | Operation Options & read Help for more details
• eTurboWare Touchscreen drivers - "Track Pointing Device Input at All Times" MUST be checked on AND the "Button" Mode must be selected for their driver (NOT Desktop Mode) - see My-T-Soft Setup | Configuration | Operation Options & read Help for more details
• MicroTouch TouchWare Monitor - NT/2000. We have received a report that there is inconsistent operation of our software when opened from a minimized icon on taskbar in Windows 2000 when the TouchWare monitor has been removed from the StartUp Group. Check MicroTouch for the latest release.

Original ID: PC223713

Use updated IMGLM.EXE

• Download IMGLM.EXE (zipped as IMGLM177.ZIP) 110K 7/27/05 (MD5: 32BF258283DF171C5493C3EB1B216D80)
• Instructions:
• 1) On the server, Go into the IMG License Manager (Licensing Information icon), and "Stop" the service, then "Remove" the service. You may leave this open.
• 2) From the Command Prompt (CMD) or Windows Explorer, go into the MYTSOFT folder (\WINDOWS\MYTSOFT) (or \WINNT\MYTSOFT).
• 3) Rename IMGLM.EXE to IMGLM.177
• 4) Copy / extract the new IMGLM.EXE from the downloaded file and place updated IMGLM.EXE into the MYTSOFT folder
• 5) From the License manager, Select "Install", then "Start"
• Notes:
• Windows Server 2003, SP1 requires this update for proper operation. Earlier versions of Windows may also experience the license manager shutting down, in which case this update should be applied.
• Certain events may trigger the service control manager to contact the IMG License Manager, including user logons, or other activities on the server. At some point during Microsoft's updates, instead of ignoring the current state response of 0, the service control manager treated this as an error & shut down the service. Earlier versions of Windows simply ignored this response. The update to IMGLM.EXE changes the response code given to the service control manager, since it appears to have gotten very particular & reacts strongly to the default response of 0, which worked for many years prior to these updates by Microsoft.
• This update should only be applied if you experience the problem listed above. If there is any issue with the update, please revert back to the original file (e.g. rename IMGLM.177 to IMGLM.EXE) & contact IMG Technical Support.

Original ID: PC203358

Apply MTSTSFIX.EXE

• Download MTSTSFIX.EXE (zipped as MTSTSFIX.ZIP) 15K 7/26/05 (MD5: 6F2838344B55E797249F053254DCBE27)
• Instructions:
• 1) From the Command Prompt (CMD), go into the MYTSOFT folder (\WINDOWS\MYTSOFT) (or \WINNT\MYTSOFT).
• 2) Extract MTSTSFIX.EXE from MTSTSFIX.ZIP - must be in same folder as MYTSOFT.EXE/IMGVERS.DLL
• 3) From command prompt, run MTSTSFIX.EXE, e.g. C:\WINDOWS\MYTSOFT>MTSTSFIX[Enter]
• Notes:
• This update should only be applied if you experience the problem listed above.
• This may only affect the console operator, but may also affect terminal (remote) users

Original ID: PC203359

Use updated IMGLM.EXE

• Download IMGLM.EXE (zipped as IMGLM176.ZIP) 110K 7/27/05 (MD5: 4450AC49D1CDE47DA89C89C1D312FE5C)
• Instructions:
• 1) On the server, Go into the IMG License Manager (Licensing Information icon), and "Stop" the service, then "Remove" the service. You may leave this open.
• 2) From the Command Prompt (CMD) or Windows Explorer, go into the MYTSOFT folder (\WINDOWS\MYTSOFT) (or \WINNT\MYTSOFT).
• 3) Rename IMGLM.EXE to IMGLM.176
• 4) Copy / extract the new IMGLM.EXE from the downloaded file and place updated IMGLM.EXE into the MYTSOFT folder
• 5) From the License manager, Select "Install", then "Start"
• Notes:
• Windows Server 2003, SP1 requires this update for proper operation. Earlier versions of Windows may also experience the license manager shutting down, in which case this update should be applied.
• Certain events may trigger the service control manager to contact the IMG License Manager, including user logons, or other activities on the server. At some point during Microsoft's updates, instead of ignoring the current state response of 0, the service control manager treated this as an error & shut down the service. Earlier versions of Windows simply ignored this response. The update to IMGLM.EXE changes the response code given to the service control manager, since it appears to have gotten very particular & reacts strongly to the default response of 0, which worked for many years prior to these updates by Microsoft.
• This update should only be applied if you experience the problem listed above. If there is any issue with the update, please revert back to the original file (e.g. rename IMGLM.176 to IMGLM.EXE) & contact IMG Technical Support.

Original ID: PC203360

Use updated IMGLM.EXE

• Download IMGLM.EXE (zipped as IMGLM175.ZIP) 110K 7/27/05 (MD5: 4ACFB5D4E711FA3A5CCEC00CD6920963)
• Instructions:
• 1) On the server, Go into the IMG License Manager (Licensing Information icon), and "Stop" the service, then "Remove" the service. You may leave this open.
• 2) From the Command Prompt (CMD) or Windows Explorer, go into the MYTSOFT folder (\WINDOWS\MYTSOFT) (or \WINNT\MYTSOFT).
• 3) Rename IMGLM.EXE to IMGLM.175
• 4) Copy / extract the new IMGLM.EXE from the downloaded file and place updated IMGLM.EXE into the MYTSOFT folder
• 5) From the License manager, Select "Install", then "Start"
• Notes:
• Windows Server 2003, SP1 requires this update for proper operation. Earlier versions of Windows may also experience the license manager shutting down, in which case this update should be applied.
• Certain events may trigger the service control manager to contact the IMG License Manager, including user logons, or other activities on the server. At some point during Microsoft's updates, instead of ignoring the current state response of 0, the service control manager treated this as an error & shut down the service. Earlier versions of Windows simply ignored this response. The update to IMGLM.EXE changes the response code given to the service control manager, since it appears to have gotten very particular & reacts strongly to the default response of 0, which worked for many years prior to these updates by Microsoft.
• This update should only be applied if you experience the problem listed above. If there is any issue with the update, please revert back to the original file (e.g. rename IMGLM.175 to IMGLM.EXE) & contact IMG Technical Support.

Original ID: PC203361

Use updated IMGLM.EXE

• IMPORTANT: This may only be used in conjunction with Intellution's iFix, etc. This is only provided here as a convenience for IMG's My-T-Soft users. You may already have this update! ALL TECHNICAL SUPPORT ISSUES WITH THIS VERSION SHOULD REFER TO GE Fanuc Automation / Intellution.
• Download IMGLM.EXE (zipped as IMGLMINT.ZIP) 22K 7/27/05 (MD5: EB99308AB8D7ED33F77DF49A67F84DBD)
• Instructions:
• 1) On the server, Go into the IMG License Manager (Licensing Information icon), and "Stop" the service, then "Remove" the service. You may leave this open.
• 2) From the Command Prompt (CMD) or Windows Explorer, go into the MYTSOFT folder (\Dynamics) (or current location of IMGLM.EXE).
• 3) Rename IMGLM.EXE to IMGLM.173
• 4) Copy / extract the new IMGLM.EXE from the downloaded file and place updated IMGLM.EXE into the MYTSOFT folder
• 5) From the License manager, Select "Install", then "Start"
• Notes:
• Windows Server 2003, SP1 requires this update for proper operation. Earlier versions of Windows may also experience the license manager shutting down, in which case this update should be applied.
• Certain events may trigger the service control manager to contact the IMG License Manager, including user logons, or other activities on the server. At some point during Microsoft's updates, instead of ignoring the current state response of 0, the service control manager treated this as an error & shut down the service. Earlier versions of Windows simply ignored this response. The update to IMGLM.EXE changes the response code given to the service control manager, since it appears to have gotten very particular & reacts strongly to the default response of 0, which worked for many years prior to these updates by Microsoft.
• This update should only be applied if you experience the problem listed above. If there is any issue with the update, please revert back to the original file (e.g. rename IMGLM.173 to IMGLM.EXE) & contact IMG Technical Support.

Original ID: PC203362

Use updated IMGLM.EXE

• Download IMGLM.EXE (zipped as IMGLM170.ZIP) 110K 7/27/05 (MD5: C6143D86FBDC59D08D24DF3DE382D77E)
• Instructions:
• 1) On the server, Go into the IMG License Manager (Licensing Information icon), and "Stop" the service, then "Remove" the service. You may leave this open.
• 2) From the Command Prompt (CMD) or Windows Explorer, go into the MYTSOFT folder (\WINDOWS\MYTSOFT) (or \WINNT\MYTSOFT).
• 3) Rename IMGLM.EXE to IMGLM.170
• 4) Copy / extract the new IMGLM.EXE from the downloaded file and place updated IMGLM.EXE into the MYTSOFT folder
• 5) From the License manager, Select "Install", then "Start"
• Notes:
• Windows Server 2003, SP1 requires this update for proper operation. Earlier versions of Windows may also experience the license manager shutting down, in which case this update should be applied.
• Certain events may trigger the service control manager to contact the IMG License Manager, including user logons, or other activities on the server. At some point during Microsoft's updates, instead of ignoring the current state response of 0, the service control manager treated this as an error & shut down the service. Earlier versions of Windows simply ignored this response. The update to IMGLM.EXE changes the response code given to the service control manager, since it appears to have gotten very particular & reacts strongly to the default response of 0, which worked for many years prior to these updates by Microsoft.
• This update should only be applied if you experience the problem listed above. If there is any issue with the update, please revert back to the original file (e.g. rename IMGLM.170 to IMGLM.EXE) & contact IMG Technical Support.

Original ID: PC203363

Use updated MYTSOFT.EXE

• IMPORTANT: This may only be used in conjunction with Intellution's iFix, etc. This is only provided here as a convenience for IMG's My-T-Soft users. ALL TECHNICAL SUPPORT ISSUES WITH THIS VERSION SHOULD REFER TO GE Fanuc Automation / Intellution.
• Download MYTSOFT.EXE (zipped as MTS173INT.ZIP) 140K 9/4/08 (MD5: E8441D9CAD63132C6A0A769BBC355ECE)
• Instructions:
• 1) On the server, Go into the IMG License Manager (Licensing Information icon), and "Stop" the service. You may leave this open. In several minutes all My-T-Soft keyboards and MYTSOFT.EXE processes will close.
• 2) From the Command Prompt (CMD) or Windows Explorer, go into the MYTSOFT folder (\Dynamics) (or current location of MYTSOFT.EXE).
• 3) Rename MYTSOFT.EXE to MYTSOFT.173
• 4) Copy / extract the new MYTSOFT.EXE from the downloaded file and place updated MYTSOFT.EXE into the MYTSOFT folder
• 5) From the License manager, Select "Start"
• Notes:
• This update should only be applied if you experience the problem listed above. If there is any issue with the update, please revert back to the original file (e.g. rename MYTSOFT.173 to MYTSOFT.EXE) & contact IMG Technical Support.
• This fix was incorporated at the 1.75 release of My-T-Soft TS. This specific version is ONLY for users running the older GE Fanuc / Intellution iFix 1.73 version.

• Verify you have the most up-to-date and correct pointing device driver for your system
• Application Focus / input focus / typing into the desired window - most issues are caused by multiple windows or external manipulation of windows or use of the Developer's Kit. Refer to documentation in the Developers Corner. Also check the My-T-Touch Setup | Configuration | Operation Options & Help for more options in working with various input devices.
• ELO TouchSystems (95/98/Me/NT) - "Track Pointing Device Input at All Times" MUST be checked on to operate with ELO drivers - see My-T-Touch Setup | Configuration | Operation Options & read Help for more details
• eTurboWare Touchscreen drivers - "Track Pointing Device Input at All Times" MUST be checked on AND the "Button" Mode must be selected for their driver (NOT Desktop Mode) - see My-T-Touch Setup | Configuration | Operation Options & read Help for more details
• MicroTouch TouchWare Monitor - NT/2000. We have received a report that there is inconsistent operation of our software when opened from a minimized icon on taskbar in Windows 2000 when the TouchWare monitor has been removed from the StartUp Group. Check MicroTouch for the latest release.

Original ID: PC223740

• Verify you have the most up-to-date and correct pointing device driver for your system
• Application Focus / input focus / typing into the desired window - most issues are caused by multiple windows or external manipulation of windows or use of the Developer's Kit. Refer to documentation in the Developers Corner. Also check the My-T-Pen Setup | Configuration | Operation Options & Help for more options in working with various input devices.
• ELO TouchSystems (95/98/Me/NT) - "Track Pointing Device Input at All Times" MUST be checked on to operate with ELO drivers - see My-T-Pen Setup | Configuration | Operation Options & read Help for more details
• eTurboWare Touchscreen drivers - "Track Pointing Device Input at All Times" MUST be checked on AND the "Button" Mode must be selected for their driver (NOT Desktop Mode) - see My-T-Pen Setup | Configuration | Operation Options & read Help for more details
• MicroTouch TouchWare Monitor - NT/2000. We have received a report that there is inconsistent operation of our software when opened from a minimized icon on taskbar in Windows 2000 when the TouchWare monitor has been removed from the StartUp Group. Check MicroTouch for the latest release.

Original ID: PC223720

In the 1.78 release for GE-IP, the My-T-Soft executable (MYTSOFT.EXE) has a manifest set to highestAvailable, which will elevate the privileges of the executable when running. If a limited user is running in the session, the developer kit utilities will run asInvoker, meaning they will run in the context of the limited user, and will not be able to interact with the higher privileged My-T-Soft. In order to resolve this without changing security & privilege levels of the user, a different MYTSOFT.EXE should be used (one with a manifest set to asInvoker vs. highestAvailable). For the 1.78 release, the standard retail MYTSOFT.EXE will work - these are the steps needed to update/work with the different MYTSOFT.EXE.

1) Get the zip file with the retail MYTSOFT.EXE for 1.78R4

You can go to the Old Downloads area here:
http://www.imgpresents.com/olddemo.htm#11201 and look for:
Download My-T-Soft 1.78 compressed installation files (mts178r4_vista7.zip) - (5.53 MB) 11/24/2009
Select and Download the zip.
This is the direct download link:

http://downloads.archives.imgpresents.com/mytsoft/mts178r4_vista7.zip

2) Work with the Zip into a desktop folder or a temp location - unzip the file/extract files.

3) In the Proficy iFix folder, rename the existing MYTSOFT.EXE as MYTSOFT.GE or MYTSOFT.BAK

4) Copy the 1.78 R4 IMG/Retail MYTSOFT.EXE into the folder you found the original GE MYTSOFT.EXE

Run and test with this executable.

Notes:
It is recommended that the Developer's Kit 1.79 Release 1 be used with the 1.78/1.80 iFix releases - see IMG Developer's Kit Downloads
The installation location is C:\Program Files\Proficy\Proficy iFix vs. C:\Program Files\MYTSOFT
Configuration files are typically C:\Users\[UserName]\AppData\Roaming\Innovation Management Group\MYTSOFT - see My-T-Soft Setup | File menu | Show Config File Location

Older versions of the single-file/self-extracting executable install exe's must be run/installed from the system where they will be installed. If run from a network (or USB drive, or other media), the setup portion will not successfully extract the software files from the compressed package embedded in the EXE. The Setup portion will appear to run successfully (and probably rather fast), but the software will not be installed. You must copy the EXE to the desktop or documents or download location, and launch it from the system that you are installing the software on. Also note this may occur if there is not enough disk space, or possibly other system issues, so also verify your system. If downloaded, you may wish to verify the size/MD5 of the file to ensure the EXE is not corrupted.

The original /q or /i install options for unattended installs were done for customers wrapping the installation into their own installation approach, and the desktop/startup shortcut options were bypassed, leaving system configuration up to the master install. For customers that need this capability, an updated SETUP.exe is available that supports these options as specified in the INSTALL.XML (the existing settings are used for the standard install and indicate if the option is available, and if it is default checked (CAPS) or clear (lowercase)).

You can download a replacement SETUP.exe here:

Setup2016Sep06.zip (SETUP.EXE) 216KB (MD5: 525739BA93FC3E44A251BF5FFF143536) 9/5/2016

Download, extract, and replace SETUP.exe with the updated SETUP.exe (from zip)

Using My-T-Soft as an example, a typical install set will be SETUP.exe / INSTALL.XML / My-T-Soft.PKG (similar for other packages). To create the shortcut, the INSTALL.XML file must be changed in the GROUP Action item using the following conventions (case is used as indicator, comma is separator):
DESKTOP=Create Desktop Icon
desktop=Skip/Remove Desktop Icon
STARTUP=Create Startup Icon
startup=Skip/Remove Startup Icon
MTSICON=Use My-T-Soft keyboard Icon (My-T-Soft type installs)

As an example, the following text will create a Startup shortcut icon:

. . .
. . .
<SOURCE>
<TYPE>GROUP</TYPE>
<NAME>My-T-Soft</NAME>
<DATAFILE>desktop,STARTUP,MTSICON>/DATAFILE>
</SOURCE>
. . .
. . .

<DATAFILE>DESKTOP,STARTUP,MTSICON</DATAFILE> will create both a Desktop and Startup Icon.

• Use alternate Setup (below)
• Refer to Installation (Setup) support
• Download MTS177.EXE (6.2MB) (MD5: D48D68C71A2669F9017C4A119AD38644), follow instructions below.
• Instructions:
• Download EXE file (single file, self-extracting, Setup), Save in known location (or move/copy to destination system)
• Run MTS177.EXE, perform normal install.
• For full font support, a system restart may be necessary (if keys are blank, you will need to restart)
• Second alternate: Download MTS177M.MSI (4MB) (MD5: 2CFC01C27C52945594EF105A12E3F2E2), follow instructions below.
• We have also prepared an MSI file (Microsoft Installer), which should be better supported by Windows for those users who have had these difficulties.
• Download this file & accept defaults to install My-T-Soft.
• Support for the Windows Installer differs among versions of Windows - if there are any difficulties, verify you have the correct updates to the Windows Installer (msiexec)

Original ID: PI223722

• Verify Windows Up-To-Date or use alternate MSI (Microsoft Installer) File
• This only affects a small number of systems, Windows XP and later.
• Background: The single file self-extracting/self-installing is the same on the web as on the CD - the install approach has worked for years on all versions of Windows. In late 2005, we've received reports from Windows XP users having difficulties with this install file.
• The failure appears to be related to the PKZIP extraction process used - what exactly causes the failure on a small number of systems is not clear, but it is difficult for us to call this progress. However, backwards compatibility is not guaranteed in the Windows environment.
• Since this is just a simple install & doing nothing more than expanding compressed files, we have prepared an MSI file (Microsoft Installer), which should be better supported by Windows for those users who have had these difficulties.
• Download Build-A-Board Version 2.10 Install as a single file MSI based file 11/7/2005 (3.1 MB) (MD5: 39AD7DA04D793F94141E10F994D95609)

Original ID: PI223703

For Version 1.79 (prior to Version 1.79 Release 2, which this will roll into), update CADBTN.exe in \Program Files\MYTSOFT folder.

Download CADBTN.exe as cadbtn.zip (127KB) (3/7/2013) (MD5: 0476447532EDEE0E3343D4BE0E554AC3) and unzip/replace existing CADBTN.exe.

1. Download file and note downloaded location - unzip/extract if necessary
2. NOTE: For production machines, you may want to download on a separate machine, and copy over the network or through storage media so the Windows file warning about downloaded file does not appear - or check Group Policy / Local Security options
3. As Administrator, use Explorer (or CMD prompt) and go to \Program Files\MYTSOFT (or \Program Files (x86)\MYTSOFT)
4. Rename existing CADBTN.exe to CADBTN.179
5. Copy in updated CADBTN.exe
6. Enable (re-enable) Feature in Logon Utilities, restart system

Note - this update can be used with My-T-Touch, My-T-Pen, My-T-Mouse, OnScreen.

---

To use a custom starting position for the CTRL+ALT+DELETE Button, you can update StartParams in the registry (Use Regedit) at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Accessibility\Ats\img_my-t-soft_v220. Use " x=800 y=200" instead of " x=default y=default" (NOTE: use desired screen coordinates).

In the original 1.79 release, anytime the logon utilities are updated, and the Ctrl-Alt-Delete option is enabled, the registry key will be updated with the default settings (which will remove any custom settings). To preserve any customizations, you can use the updated IMGLOGON.exe (this will roll into 1.79 Release 2).
Download IMGLOGON.exe from imglogon_179update.zip (461KB) (3/8/2013) (MD5: E7CE95691921A7279BC17C30561535C1) and unzip/replace existing IMGLOGON.exe.

When extracted, you will find WIN32-BIT and WIN64-BIT folders - use the appropriate platform build, and select the appropriate folder (e.g. MYTSOFT for My-T-Soft), and then update the IMGLOGON.exe in \Program Files\MYTSOFT folder (for 64-bit, update \Program Files (x86)\MYTSOFT).

---

The CADBTN.exe utility needs to be configured to run from both the system and for the current user. When configured by an Administrator (or a new user is created), other users will not have the individual (HKEY_CURRENT_USER) configured, so this same issue can occur. To enable this for a particular user, refer to the Ease of Access Center - you can configure the user by going into Control Panel | Ease of Access | Ease of Access Center | Change how your keyboard works | Enable My-T-Soft Family Ease of Access Utility | Check ON Use CTRL+ALT+DEL Access Utility.

This registry setting must be there for each user that needs this functionality:

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Accessibility]
"Configuration"="img_my-t-soft_v220"

Note: Depending on other settings, the img_my-t-soft_v220 entry needs to be part of a comma-delimited list in Configuration.

Update executables to resolve system font code caused delays.

Using the Startup display troubleshooting option (Command Line Options) and the help of a customer, it was determined that the AddFontResource and WM_FONTCHANGE broadcast Windows message took an extremely long time to process, which delayed the startup sequence. To bypass these system calls, the RunAddFontResource Initialization entry was re-enabled (previously marked obsolete) and used to indicate if the system font code should be run. By default, the RunAddFontResource=0, so by updating the executables, the font code is not used, and this resolved the delay problem.

To resolve this problem, download the My-T-Soft & My-T-Soft Setup (My-T-Pen & My-T-Pen Setup) (My-T-Touch & My-T-Touch Setup) executables in mtsfontfix_2014mar28.zip

Download mtsfontfix_2014mar28.zip 2.97MB 3/28/2014 (MD5: 8B8008FD6A2DE799440368967D9D644C)

Download and extract from the zip file to expand 3 folders (My-T-Soft/My-T-Pen/My-T-Touch). Within these folders are 1.78 and 1.79 versions, and a 1.80 version for My-T-Soft. Be sure to use correct version of executable based on installed product and version.

For My-T-Soft
Make sure My-T-Soft & My-T-Soft Setup are not running. Copy/overwrite MYTSOFT.exe and MTSSETUP.exe from correct version folder (plus UAC exe's for My-T-Soft 1.80) in \Program Files\MYTSOFT (or \Program Files (x86)\MYTSOFT)

For My-T-Pen
Make sure My-T-Pen & My-T-Pen Setup are not running. Copy/overwrite MYTPEN.exe and MTPSETUP.exe from correct version volder in \Program Files\MYTPEN (or \Program Files (x86)\MYTPEN)

For My-T-Touch
Make sure My-T-Touch & My-T-Touch Setup are not running. Copy/overwrite MYTTOUCH.exe and MTTSETUP.exe from correct version folder in \Program Files\MYTTOUCH (or \Program Files (x86)\MYTTOUCH)

Notes: With these executables, RunAddFontResource=1 must be set in the INI file to run the font change system code. The code was removed back in Windows 95 1.6x versions, then re-instated 1.7x versions to ensure customers that installed using zip files, or their own installation instead of the standard retail installation had access to the MYTMOUSE.FON font for proper display in smaller sizes. For a normal installation, the bypassed code is not required - it was put back in because it should be benign, and not cause any system delays, and it helped resolve a font issue for some uses of the software. If necessary, the font can always be manually installed with the system.

If you reference the original Tech item, there is a strong possibility that some process does not handle this font broadcast message correctly, or starts a sequence of extreme processing before releasing back to the system - it may be possible to identify the offending process and look for updates or fixes to the process that causes the system delay. To resolve the issue without using these executable file updates, refer to this tech item: PC1107120533

Notes: You will want to copy these files as Administrator to ensure you are updating/replacing the actual executables. Also, it is recommended that you rename the old executables so you can revert to them if desired/needed (rather than overwriting these files). Depending on the version of Windows and settings, if you download the zip, and copy the file from the Downloads area, Windows may give a warning when running the executable. You may wish to work from a different system or a network to prevent this safety mechanism.

This problem was identified and resolved with an update to the HapticsFeedback.DLL in March 2020 and has been rolled into an update from Zebra Technologies - this is available as part of an update available here: CFE_VC80_W10_RS1_EN_V010400_e_WB (Zebra Portal Logon Required).

Background: The legacy My-T-Soft 1.x software has a different identifying class than the My-T-Soft 2.x software that operates custom layouts. The original HapticsFeedback library did not check for the My-T-Soft 2.x window (custom layout), so never sent physical bezel key event. The update resolves this issue.

For integrators or system administrators, the updated DLL is provided here:

zebravc80hapticslib20200326.zip (20K) March 26, 2020 (MD5: E80C78DD4EE54D6596F776002A8606BA )
NOTE: This download is provided as a convenience for testing/troubleshooting. It is recommended all updates be applied with supported / authorized updates via Zebra Technologies (see link above).

Download/extract zip file - it has one file, the updated HapticsFeedback.DLL

IMPORTANT: Preserve existing DLL file so you can revert to current system if necessary, and then drop in new one:

You will want to rename or backup the existing HapticsFeedback.dll, then unzip downloaded zip file, and drop in the DLL file to the correct location:

C:\Program Files\VCControlPanel\HapticsFeedback.DLL

Do this as Administrator or boot into safe mode to update the HapticsFeedback.DLL - if it is in use, you will not be able to overwrite/update it.

Once updated, you can reset the system, then test. With the original DLL, the physical Bezel keys will not trigger macros when using a custom Build-A-Board layout, but with updated DLL, macros will occur.

There are several possibilties using the IMG Developer's Kit - available here
OnScreen does not include the Developer's Kit by default, but it can be downloaded and unzipped as appropriate for the user/system. The DevKit sub-folder has useful utilities for manipulating the keyboard externally - specifically the FWCTLMTS.EXE (Find Window and Control), MINMZMTS.EXE (Minimize), OPEN_MTS.EXE (Open).
In the DevKit folder, the FWCTLMTS.EXE is designed to toggle OnScreen (My-T-Soft Family) off-screen (not visible)/ on-screen (visible). By creating a shortcut to this utility on the user's desktop, then go into the shortcut properties, you can add a Shortcut key (e.g. Ctrl-Alt-X) to trigger the shortcut itself. Then when a Ctrl-Alt-X occurs (via physical keyboard or OnScreen), the OnScreen keyboard window will be toggled "off-screen". Press Ctrl-Alt-X to bring it back. Ctrl-Alt-X will toggle access to OnScreen & control the screen real estate as desired by the user.
Alternatively, using a Minimize/Open (MINMZMTS.EXE / OPEN_MTS.EXE) approach with 2 different shortcuts (e.g. Ctrl-Alt-A / Ctrl-Alt-Z) can perform the same general operation, but leaves the software available in its minimized state.

If your font setting (Custom DPI Setting) is greater than 125%, the Windows API GetSystemMetrics does not perform as documented, and will return incorrect values for screen size, causing Joystick-To-Mouse's calculations to be incorrect. Requires SetProcessDPIAware system call. This update has rolled into 2.70 Release 5). To update, do one of the following:
If you have your license key/serial #, you can simply install the current Joystick-To-Mouse from here, then re-license:
http://www.joystick-to-mouse.com/joy2mse/jtmdemo.htm#Download

Alternatively, you can download the Zip file, extract, and then update the joy2mse.exe file. http://www.joystick-to-mouse.com/joy2mse/jtmdemo.htm?view=extended#download

With Joystick-To-Mouse closed, as Administrator, in \Program Files\Joystick-To-Mouse, rename JOY2MSE.exe to JOY2MSE.270R4
Copy in downloaded file, e.g. \Program Files\Joystick-To-Mouse\JOY2MSE.exe

Now run and test - operation should be correct for all DPI settings

Resolution: Update MYTSOFT.EXE to version 2.16

IMPORTANT: This is only a direct replacement to the Build-A-Board run-time component MYTSOFT.EXE. This may not be used in Windows CE, as MTS2.EXE, or MYTSOFT2.EXE!

• File provided as ZIPped EXE
• Instructions: Make sure Build-A-Board is closed. In Windows Explorer or command prompt, get to \Program Files\Build-A-Board\Bin\MSWIN folder, then rename existing MYTSOFT.EXE to MYTSOFT.210. Copy downloaded file into folder (extract if necessary). Also do the same for \Program Files\Build-A-Board\Bin\TEST folder, rename existing MYTSOFT.EXE to MYTSOFT.210. Copy downloaded file into folder (extract if necessary).
• Rebuild any projects to have update take affect, or copy MYTSOFT.EXE directly onto end-user run-time system (e.g. rename existing MYTSOFT.EXE to MYTSOFT.210, then copy in 2.16 version of MYTSOFT.EXE)
• Download My-T-Soft 2.16 as M216W32.ZIP 9/28/2004 (23k) (MD5: 916C8f87F4925CE52B10BCE28379116B) (unzips as MYTSOFT.EXE)
• Download SeeThru for My-T-Soft 2.16 as STHRU216.ZIP 9/28/2004 (14k) (MD5: 5D08ACF5F17DCE9E39D3CB47799D778D) (unzips as SEETHRU.EXE)
• Technical Notes
• This is a maintenance update / patch based on technical support issues and customer requests.
• Files tagged as 2.16.0.0, but licensing is the same as 2.10 (e.g. MTS210?????? serial numbers).
• Transparency
• To make My-T-Soft run-time transparent, on end-user system run SeeThru.exe with My-T-Soft running, Enable Transparency, and slide to transparency level.
• The settings are in the registry at HKCU\Software\Innovation Mangement Group\Build-A-Board. String Values: Transparency=1 for Enabled, Transparency=0 for Disabled. When Enabled, TransparencyLevel=??? - Range from 0 (completely transparent) to 255 (opaque).
• If you do not experience any of the above listed problems, there is no need for this update.

Original ID: PU225147

• Resolution: Use TYPEFILE.EXE and CMD:EXEC= to generate macro from file
• TypeFile will read a macro file, and process up to 2000 characters. By Using CMD:EXEC for Key Action, effective result will be the same as a normal Key Action keystroke macro.
• Download TYPEFILE.EXE 5/11/2009 (45k) (MD5: 66CB31F8CB435222F4A61E32BD0D9668) Only for Win32 Targets! (95 thru XP)
• Download TYPEFILE.EXE 11/2/2011 (45k) (MD5: 1CB5D3C3B7B4B7C4F1599C2CCB75306B) Only for 2.20 Win32 Targets! (MSWIN32 - 2000/XP/Vista/7) (See 2.20 Notes below)
• For Linux Typefile, see tech item ID2012120679
• Download and Note location on system where downloaded file is saved
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\Test
• Copy TYPEFILE.EXE into Program Files\Build-A-Board\Bin\Test Folder
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\MSWIN
• Also Copy TYPEFILE.EXE into Program Files\Build-A-Board\Bin\MSWIN folder
• After adding file, open your project, and rebuild to update TARGET folders.
• Using TypeFile:
• There are 2 key issues that must be addressed - 1) saving a macro in a file, and 2) using a shortcut with a command line as the EXEC= entry.
• 1-A) The easiest way to save a keystroke macro file is to use the Build-A-Board Macro Builder dialog - to get to this, create a temporary key (or use a temporary project). Hover over the key with the mouse cursor, then right-click, and open the properties. Find the Key Action entry, and click on the right-hand button (...) to open the dialog.
• 1-B) Build your macro as required, then click on Save.
• 1-C) The Save function will save files as .KMF files (Keyboard Macro File) - you should browse to the \Program Files\Build-A-Board\Target\[Your Project Name]\MSWIN folder & enter a name to save, e.g. MyMacro[Enter] The file saved will be MyMacro.kmf.
• 1-D) If you want to test with this from within the Builder, also save (or copy the saved file) to \Program Files\Build-A-Board\Target\[Your Project Name]
• 1-E) You can also open, edit, and save any Macro file from within the Build-A-Board Macro Builder dialog - just follow the steps above, but click Open, then browse to where you have saved the file. Save the file in the MSWIN folder under the project folder, and also remember to save (or copy) to Project folder (which is the test folder) if you want to test from within the Builder.
• 2-A) To specify the file name to TypeFile.exe, you must use a shortcut - You CANNOT use a command line within the CMD:EXEC function!!
• 2-B) To create a shortcut, use Windows Explorer and browse to the \Program Files\Build-A-Board\Target\[Your Project Name]\MSWIN folder
• 2-C) Right-click on TYPEFILE.EXE and select Create Shortcut - by default, the shortcut will be called Shortcut to TYPEFILE.exe
• 2-D) Rename the shortcut to something useful, e.g. TypeThis (or MyMacro1, Macro02, etc.)
• 2-E) Modify the shortcut to specify the macro file name that TypeFile will type - right-click on the shortcut, select Properties, and in the Target, enter the name of the Macro File, e.g. ...TYPEFILE.exe MyMacro
• 2-F) Now (in the project that needs this extra long macro), select the key that will type this extra long macro, right-click, and go to properties, and enter for Key Action: [CMD:EXEC=TypeThis] - then click OK. IMPORTANT NOTE: Shortcuts have a file extension of .lnk, and this is usually hidden in Explorer. In most cases, you will not need to specify this, but it can be a source of confusion - Windows Explorer WILL NOT show you the ACTUAL Operating System file name! You can use the Command prompt if necessary.
• Other Notes:
• The Key Action with CMD:EXEC will be compiled and be part of the project KBF file (e.g. KEYBOARD.KBF), but the files TYPEFILE.EXE, the keystroke macro files, and any shortcuts created are not part of the source files - be sure to save / backup these files. Suggestion: You can manually copy them into the Source folder for the project prior to Closing the project.
• The shortcut name shown in Windows Explorer will have the .lnk extension, but this is not necessary to specify with the CMD:EXEC command in Build-A-Board.
• TYPEFILE.EXE will look in the same folder it is running from for the file name specified in the command line. If the file specified does not have an extension, it will add the .KMF extension. If you include a path, it will only look for the file in the specified location (i.e. it will not look in the folder where it is located).
• If you experience any difficulties, break each action into pieces - to test with TypeFile.exe, My-T-Soft must be running, but you can run the sample (i.e. Start Menu | Programs | Build-A-Board | My-T-Soft), and minimize it, then test with TypeFile.exe. The macro file is just a text file - use Notepad, and enter a few characters, then save the file as test.kmf (i.e. ANSI, NOT Unicode). Also, you may want to follow the above steps in a new project, prior to trying to integrate into an existing project.
• You may also specify the macro on the command line (effectively about 128 character limit, although this could vary). This approach is primarly for external manipulation by an application, not for use within Build-A-Board. If using words (vs. commands), be sure a file name does not exist with the macro you use - the first check is to see if a file name is specified on the command line.
• Version 2.20 Notes. The file downloaded as typefile220.exe can be renamed to typefile.exe if desired. The Key Action macro limits do not apply to the 2.20 version. The typefile utility can still be helpful for external control of keyboard command, etc., i.e. using [CMD:NKBF=NewLayout.kbf] can be helpful to allow an external application or tool to externally select a new layout to be displayed.

Original ID: PU225149

There is an update to the SmartClick executable which introduces a delay during the SingleClicker operation that resolves this issue. Download and update SmartClick.exe from zip:

Download SmartClick exe update as smartclick_exe_160_2015aug18.zip (771KB) (MD5: A7A05FBD5672B4F106F0FC8F92F4505A)

As Administrator, with SmartClick closed (not running), you will want to unzip (right-click | Extract All), and copy all the exe files to \Program Files\SmartClick (or \Program Files (x86)\SmartClick) (this will overwrite the existing SmartClick.exe and add a few others). Once updated, SmartClick can be run as normal.

Notes: This update introduces a delay for the interface between real clicks (SingleClicker) and virtual clicks from SmartClick - drag, double-click, etc. For best results, the single click should be a "click" - as in a quick press/release. There may be an issue when working with Title bars, e.g. dragging a window by the title bar - a second single click may be required to correctly drag the window.

The additional exes (SmartClick.requireAdministrator.exe, etc.) can be used if User Account Control is enabled, and there are issues interfacing with certain windows. For users that do normal things, this should not be necessary - the User Interface Privilege Isolation issues would typically only affect system administrators or users that use system tools. If necessary, the SmartClick.highestAvailable.exe or SmartClick.requireAdministrator.exe can be copied to SmartClick.exe - by default, SmartClick.exe is SmartClick.asInvoker.exe).

This update is only for SmartClick 1.60.

You need the Build-A-Board Builder to create or modify layouts, change key properties/actions, and create/build the KBF (Data) file. For the Target (run-time) you need the My-T-Soft program (for the particular platform) on the run-time system. Drop in the KBF data (default KEYBOARD.KBF), and run the My-T-Soft program - the layout will be displayed to the user, and its operation will be defined by the layout properties / Key Actions (which, of course, are modifiable within Build-A-Board).

What is the Builder for?

The Build-A-Board Builder itself is just a front-end designer tool to allow you to drag & drop keys, resize, change properties, etc. It is a user-friendly front end to designing keyboard layouts. When you build, you are creating the single file KBF that can be dropped into a target system (which then contains the Keyboard layout/properties/etc.) The KBF layout is supported on Windows, Windows CE, Android, Linux, Mac OS X, etc.

As much as possible, the implementation is a Program operating on Data concept. The Data (KBF) is created within Build-A-Board. The run-time software (deployed/implemented/installed/located) on the run-time target reads this data, displays the layout to the user, and then processes user actions based on what the user selects. The "Regular" Key Action is to create the down/up events as if a physical key was pressed. This is seen as a keystroke by the underlying application. There are other actions available, including opening a new layout (New KBF command) and running an arbitrary program (Exec command).

What are the project files? What should I open? What is PROJECT.TXT?

The project files are simple text files that describe in human readable form the layout & keyboard properties. They are an interim step towards a complete database of layouts. The zip format is just to compress & reduce disk space. If you see both a PROJECT.TXT and a zip, open the PROJECT.TXT, as this means the Project is "Open" (i.e. unzipped) and may have modifications that haven't been "zipped" up again (File | Close Project). We recommend you use the front-end display of layouts to get around the whole project file issue - just pick a layout, and go with it.

When I "F9 - Build" what am I creating? An EXE somewhere?

You are creating the KBF file (KeyBoard File). This is a singe file representation of the layout that can be used by the run-time software. Because it is now cross-platform, this is the "Data" part of the Program & Data concept (like a .DOC file contains the "document"). You "get" the keyboard you just created by loading the KBF in the run-time software. When you select a target platform, it also copies over install/run-time files - so theoretically you could take these over to the platform, install the run-time files, run the My-T-Soft binary/executable (e.g. MYTSOFT.EXE on windows) and then get the display / operation of the KEYBOARD.KBF (default KeyBoard File). For a Windows target, refer to the MSWIN32 folder (Shift-F11 to view) to see the "run-time" files - these are what gets deployed on a Windows system (and similarly for other platforms).

What is required for the target system? What does Run-time mean? How do I integrate it with my application?

Here is a quick run-down - refer below for further details, and use the Product Guide for even more details.

1. Create or Modify a layout in the builder.
2. Select Target in the Run-Time menu (e.g. Windows 32)
3. Build (& execute to test)
4. Install the Target (run-time) files on your deployment target
5. Run My-T-Soft at a system level, or at application start (Shell/Exec/etc.)
6. Use Developer's Kit Tools (or concepts) to move keyboard window on-screen when needed/off-screen when not
7. Use an iterative approach to get the custom keyboard layout integrated into your application

Here is a more technical overview

1. The approach to the user interface is to have the executable display a topmost window that presents a keyboard (or arbitrary button display) to the user. It handles input focus issues so any virtual keystrokes are seen as standard keystrokes to the application. This is the My-T-Soft program, sometimes referred to as the "Build-A-Board run-time". For example, on windows, when you run MYTSOFT.EXE it reads the KBF (KeyBoard File - KEYBOARD.KBF) and displays the layout as designed and built in Build-A-Board.
2. The run-time software is an EXE (or program/binary process based). As such, it should be running at a system level, or at application startup (see more below)
3. The user interface aspect is separated from the actions. All external Key Actions are handled by the MacroBat process (Macro Batch Processor). This is implemented as a separate process. So the 2 processes (My-T-Soft and MacroBat) must both be on the run-time target to read the Data (KBF file), display the layout to the user, and process the actions when a button is pressed. Note that with the CMD:EXEC any arbitrary process can be launched when the user initiates this action by pressing a button on the layout. New layouts can be opened with the CMD:NKBF command - a common approach for user control is to have a single button layout that opens the full layout, and then a minimize button that returns to the single button layout.
4. In general, we recommend you run the keyboard (e.g. MYTSOFT.EXE in Windows) at system start, or application start - then during the life of your application, you can control access with the "MoveWindowMTS" function/concept - move it off-screen to remove it from the user, move it on-screen to display it for the user at the X/Y location you want. This keeps the process running, and you don't have any shut-down or startup delays. If done at the system level, StartUp group is typical, and if handled in the application, a Shell or Exec type function is typical.
5. The most effective way to handle "on/off" is to move on-screen/off-screen. Using the New KBF (CMD:NKBF) the user can select different layouts. Refer to the MoveWindowMTS function (MOVEWMTS.EXE for windows, etc.) See the DEVKTDOC folder to open the Developer's Kit Documentation.

For a more detailed view & terminology, refer the Quick Usage Notes in the Product Guide.

The underlying technology and coding was developed for the My-T-Soft family of products - because of strong demand by the visually impaired, IMG spun-off The Magnifier as a stand-alone product. In order to assist as many individuals as possible, IMG priced the product within easy reach of most computer users.

We get asked this question quite a bit, so here is a bit more technical information. Other competing magnfiication software interfaces with the system at a much lower level, and requires significantly more engineering and technical expertise than the approach used by IMG's The Magnifier software. There are distinct differences between the engineering approaches and trade-offs. For example, often people want the magnified portion to remain static, while allowing the mouse cursor to move within that magnified area, only moving when the mouse moves close to the edge - this is impossible within The Magnifier because of the approach used - when you move the mouse, the magnified image must move. However, there are keyboard panning options, tracking via typing, and external control via the IMG Developer's Kit. IMG has chosen to keep the price affordable, while doing the absolute best and providing every option given the limitations of the magnification approach used. For many users, these technical limitations mean nothing, since the end result is a magnified screen image that is helpful to them. For everyone that finds IMG's The Magnifier helpful, affordable, and useful, this product was created for you. For other users that need more sophisticated options, researching other products may be beneficial. IMG always recommends interested parties download and work the software to verify it meets their needs before committing to a purchase.
Original ID: QC202226

The following is excerpted from:
Help | My-T-Soft Help | My-T-Soft User's Guide | Section IV - Other Information | Advanced User Information = Files & File notes
For up-to-date details about the version, this is the preferred location to reference details about a particular release.

For the 1.77 releases:
These are the files required for operation of the My-T-Soft keyboard in the user (default) desktop:
MYTSOFT.EXE
MYTSOFT.INI
MYTLIB.DLL
MYTLIB32.DLL
IMGVERS.DLL
BWCC32.DLL
CW3215.DLL
KEYBOARD.KBF
KEYBRD01.KMF
KYBD0001.KMF (for Us 101 layout - change if necessary)
MAC00000.KMF
LICENSE.EXE
LICENSE.LIC

Note: For the smaller sizes, the MYTMOUSE.FON may be required. If you do a normal install, and delete all but the above, the font will be installed by Setup. If required, you may want to use Control Panel and add the MYTMOUSE.FON file.

For Logon (WinLogon desktop) (Windows 2000 / XP):

IMGLOGON.EXE (to configure/enable - once configured as desired, can be deleted)
IMGGINA2.DLL (DLL to integrate with secure logon)
MTS2.EXE - (My-T-Soft 2 executable to display LOGON\KEYBOARD.KBF)
MTSLIB.DLL - Support for MTS2.EXE / MYTSOFT2.EXE
BABDLL.DLL - Support for MTS2.EXE / MYTSOFT2.EXE, Build-A-Board common functions
STOCK.DLL - Support for MTS2.EXE / MYTSOFT2.EXE, Resources for 3D keys
LOGON folder (see details [in source] - some files (like KEYBOARD.SML, etc.) can be removed)

On very limited XP Embedded builds, this is a list of modules (DLLs) used by running MYTSOFT.EXE:
C:\WINDOWS\MYTSOFT\MYTSOFT.EXE
C:\WINDOWS\MYTSOFT\BWCC32.dll
C:\WINDOWS\MYTSOFT\MYTLIB.DLL
C:\WINDOWS\MYTSOFT\MYTLIB32.DLL

C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\GDI32.dll
C:\WINDOWS\system32\USER32.dll
C:\WINDOWS\system32\ADVAPI32.dll
C:\WINDOWS\system32\RPCRT4.dll
C:\WINDOWS\system32\WINMM.dll
C:\WINDOWS\system32\SHELL32.DLL
C:\WINDOWS\system32\SHLWAPI.dll
C:\WINDOWS\system32\msvcrt.dll
C:\WINDOWS\system32\COMCTL32.dll
C:\WINDOWS\system32\IMM32.dll
C:\WINDOWS\system32\VERSION.dll
C:\WINDOWS\system32\LPK.DLL
C:\WINDOWS\system32\USP10.dll
C:\WINDOWS\system32\uxtheme.dll

For the external DLLs, here are some quick notes/reference information:
CORE OS DLLS:
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\GDI32.dll
C:\WINDOWS\system32\USER32.dll

Other core DLLs:
C:\WINDOWS\system32\msvcrt.dll - Microsoft C run-time
C:\WINDOWS\system32\VERSION.dll - File & Version info

Shell & Windows oriented DLLs:
C:\WINDOWS\system32\SHELL32.DLL - Explorer Shell
C:\WINDOWS\system32\COMCTL32.dll - Common Controls
C:\WINDOWS\system32\WINMM.dll - Windows Multimedia
C:\WINDOWS\system32\SHLWAPI.dll - Shell LightWeight lib

Other DLLs:
C:\WINDOWS\system32\IMM32.dll - Input Method Editor Module
C:\WINDOWS\system32\ADVAPI32.dll - advanced API library
C:\WINDOWS\system32\RPCRT4.dll - Remote procedure call
C:\WINDOWS\system32\LPK.DLL - Language Pack
C:\WINDOWS\system32\USP10.dll - Uniscribe Unicode Script Processor Library
C:\WINDOWS\system32\uxtheme.dll - Compatibility with "Style XP"

Windows "Side-by-Side" (WinSxS) Compatibility COMCTL32.DLL:
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll

For MYTSOFT2.EXE (Build-A-Board layouts) & WinLogon (MTS2.EXE), these are the changes:

Only uses Local DLLs:
C:\WINDOWS\MYTSOFT\MTSLIB.dll
C:\WINDOWS\MYTSOFT\BABDLL.dll
C:\WINDOWS\MYTSOFT\STOCK.dll

Plus one other system DLL:
C:\WINDOWS\system32\Apphelp.dll - for Application Compatibility in XP/2003

Original ID: QC222198

The easiest way to accomplish this is to use a Developer's Kit tool, the Copy and Configure My-T-Soft on the fly (CPYCNMTS.exe). For a general overview, see this How To note in the IMG Developer's Kit: Configure My-T-Soft on the fly (from pre-existing configurations). My-T-Soft is considered an application, and is in control of the user and/or the application with input focus using Developer's Kit tools. If the system level input language layout needs to change in conjunction with the My-T-Soft Layout, refer to the extension of this example with the link at the bottom of this item.

The following outlines a step-by-step procedure to follow. The required ingredients are:

Location of Configuration files (e.g. C:\Users\User\AppData\Roaming\Innovation Management Group\MYTSOFT)
CPYCNMTS.exe from the IMG Developer's Kit (i.e. My-T-Soft "DEVKIT" folder)
2 Configuration file sets (KEYBOARD.KBF/MYTSOFT.INI named appropriately)

Step 1 - Obtain the Configuration File location. With My-T-Soft running, right-click or use Menu button on Tool bar, and open My-T-Soft Setup. In My-T-Soft Setup, use File menu and select "Show Config File Location" Use Windows File Explorer or command prompt (CMD) and change to that location

Step 2 - Obtain CPYCNMTS.exe - download the IMG Developer's Kit here: Developer's Corner Downloads, or use the direct link: IMG Developer's Kit 1.79 Release 1. Download, Extract files, and from DEVKIT folder, find CPYCNMTS.exe, then copy to the Configuration File location from Step 1

Step 3 - Create layout configuration files. The overview is that you select layout & configure My-T-Soft how you want it to appear, then you save these settings and its position, close My-T-Soft, and copy off the configuration files (KEYBOARD.KBF/MYTSOFT.INI). The specific example will be for Italian and Japanese layouts, but you should create the appropriate layout configurations for your needs.

• From My-T-Soft Setup | Keyboards | Select Layout - 104 Italian, then close My-T-Soft Setup
• Launch My-T-Soft, and from My-T-Soft (Control panel or Menu) configure panels, size, and position, then save Settings/position - Menu | Current Settings | Save Current Settings and Menu | Position | Save Position. Now close My-T-Soft.
• From Configuration File Location, copy KEYBOARD.KBF to ITALIAN.CFG and copy MYTSOFT.INI to ITALIAN.INI
• Repeat for Japanese - From My-T-Soft Setup | Keyboards | Select Layout - 104 Japanese, then close My-T-Soft Setup
• Launch My-T-Soft, and from My-T-Soft (Control panel or Menu) configure panels, size, and position, then save Settings/position - Menu | Current Settings | Save Current Settings and Menu | Position | Save Position. Now close My-T-Soft.
• From Configuration File Location, copy KEYBOARD.KBF to JAPAN.CFG and copy MYTSOFT.INI to JAPAN.INI

The example below is a test batch file to verify and ensure everything is configured and all files are correct - this can be tested/run from a command prompt or Explorer.

@echo off
cls
REM This toggles 2 layouts.
REM These files must exist:
REM JAPAN.CFG and JAPAN.INI for Japanese layout
REM ITALIAN.CFG and ITALIAN.INI for Italian layout
REM user is [Username] for current logged in user / application user
REM the actual path below is an example, will need to be updated for your usage

C:
cd "C:\Users\user\AppData\Roaming\Innovation Management Group\MYTSOFT"

IF exist LAYOUTJAPAN.CUR GOTO DOITALIAN
cpycnmts.exe JAPAN.CFG
copy JAPAN.CFG LAYOUTJAPAN.CUR
goto END
:DOITALIAN
cpycnmts.exe ITALIAN.CFG
DEL LAYOUTJAPAN.CUR

:END


The above batch file is not recommended as an ideal way to toggle these layouts. Ideally using the command "CPYCNMTS.exe [LAYOUT].CFG" directly would be the best way to trigger the visual change in My-T-Soft. If the batch file approach is used, creating a shortcut link to it and using the Run setting as Minimized may help with visual effects, and then running the shortcut (vs. the batch file directly) may be acceptable.

Typically the execution of the Developer's Kit Utility (CPYCNMTS.exe) would be done via an application, either embedded, or tied to an event like Field Exit or Field Enter, or under a button OnClick event.

Note there is a different utility called KeyboardSync (KYBDSYNC.exe) that monitors the current Input locale of an application, and can change My-T-Soft's layout to match the input locale. This utility is also in the IMG Developer's Kit

As a separate option, a key can be made to toggle layouts - refer to this Tech item for the steps required to setup a Key to run a Developer's Kit tool: Using Key Options

Note that using Developer's tools may depend on User Interface Privilege Isolation issues. If things do not operate as expected, it may be worth testing as Administrator and familiarizing yourself with these issues (see this blog post Understanding User Interface Privilege Isolation (UIPI) with My-T-Soft)

This approach just changes My-T-Soft. To externally change the current input language keyboard layout, a separate item that extends this example has been created - see How to Change the Current Input Language Keyboard Layout

This extends the "Change My-T-Soft Layout" example at How to externally Change My-T-Soft Layout. The first part below explains the mechanism provided by Windows, and then it ties into the example of the linked example above.

There is an unattended XMLfeature that can be used to manipulate regional and language settings. This example only uses the InputPreferences option, and there are many other aspects to this functionality that are not covered here. The example is from Windows 7. This also works for Windows 10, but the default input layout acts differently - note that [Win]-[Space] will roll through current input layouts.

This is an Example of an XML file that adds and removes layouts using Spanish, English US, and German layouts, setting English as the default

<gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend">
<!-- User List -->
<gs:UserList>
<gs:User UserID="Current" />
</gs:UserList>
<gs:InputPreferences>
<!-- Spanish -->
<gs:InputLanguageID Action="remove" ID="0c0a:0000040a" Default="false" />
<!-- en-US -->
<gs:InputLanguageID Action="add" ID="0409:00000409" Default="true" />
<!-- de-DE -->
<gs:InputLanguageID Action="add" ID="0407:00000407" Default="false" />
</gs:InputPreferences>
</gs:GlobalizationServices>


This file would need to be saved as an XML file, e.g. inputchange.xml, and care must be taken to make sure standard characters are used (text only type file), and then it can be implemented using the following:

control intl.cpl,, /f:"inputchange.xml"

Note: There are 2 commas, and there needs to be a space between the second comma and the /f switch. The quotes need to be normal double-quotes, and ideally a path would be specified - this example must be run from the same directory where the file inputchange.xml exists. The critical piece is the ID value for the InputLanguageID - refer to Microsoft documentation for additional ID values for language, region, and layout.

To use these tools, 4 XML files where created that do discrete actions - add and remove Italian and Japanese layouts. By removing the layout, if it is the default in an open application, it will be replaced by the new default layout. It is important to note how Windows handles input layouts - each Window can have its own input settings, and by changing focus between open applications, the current input language will stay with the current settings for an open Window. For example, you could have 3 instances of Notepad open, and each could have their own input language, and the keyboard layout will change based on which Notepad is the current active window. There are options for the input language to show on the task bar or as a floating window to indicate which input language is active. Note that most users set to the current locale, and operate with 1 input locale, so the issues of changing input settings would typically not apply, but when changing and working with multiple input locales, unique situations can occur, so awareness of which input locale is in use can be extremely relevant and useful.

IT.XML - Adds Italian (Italy) layout and sets as default

<gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend">
<!-- User List -->
<gs:UserList>
<gs:User UserID="Current"/>
</gs:UserList>
<gs:InputPreferences>
<!-- Italian -->
<gs:InputLanguageID Action="add" ID="0410:00000410" Default="true"/>
</gs:InputPreferences>
</gs:GlobalizationServices>


ITREMOVE.XML - Removes Italian layout

<gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend">
<!-- User List -->
<gs:UserList>
<gs:User UserID="Current"/>
</gs:UserList>
<gs:InputPreferences>
<!-- Italian -->
<gs:InputLanguageID Action="remove" ID="0410:00000410"/>
</gs:InputPreferences>
</gs:GlobalizationServices>


JP.XML - Adds Japanese layout and sets as default

<gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend">
<!-- User List -->
<gs:UserList>
<gs:User UserID="Current"/>
</gs:UserList>
<gs:InputPreferences>
<!-- JP-Japanese -->
<gs:InputLanguageID Action="add" ID="0411:{03B5835F-F03C-411B-9CE2-AA23E1171E36}{A76C93D9-5523-4E90-AAFA-4DB112F9AC76}" Default="true"/>
</gs:InputPreferences>
</gs:GlobalizationServices>


JPREMOVE.XML - Removes Japanese layout

<gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend">
<!-- User List -->
<gs:UserList>
<gs:User UserID="Current"/>
</gs:UserList>
<gs:InputPreferences>
<!-- JP-Japanese -->
<gs:InputLanguageID Action="remove" ID="0411:{03B5835F-F03C-411B-9CE2-AA23E1171E36}{A76C93D9-5523-4E90-AAFA-4DB112F9AC76}"/>
</gs:InputPreferences>
</gs:GlobalizationServices>


The following extends the batch file from the example linked at the top of this item

@echo off
cls
REM This toggles 2 layouts.
REM These files must exist:
REM JAPAN.CFG and JAPAN.INI for Japanese layout
REM ITALIAN.CFG and ITALIAN.INI for Italian layout
REM If changing Layouts, the it, itremove, jp, and jpremove XML files must exist
REM user is [Username] for current logged in user / application user
REM the actual path below is an example, will need to be updated for your usage
REM If the Input Language layout is not changing as expected, you may find events
REM that may show errors or warnings in the Event Viewer.
REM Go to Control Panel | System and Security | Administrative Tools | View Event Logs
REM and in the Event Viewer open Applications and Services Logs then go into
REM Microsoft | Windows | International and view the Operational log

C:
cd "C:\Users\user\AppData\Roaming\Innovation Management Group\MYTSOFT"

IF exist LAYOUTJAPAN.CUR GOTO DOITALIAN
REM This changes the My-T-Soft Layout
cpycnmts.exe JAPAN.CFG
REM This removes Italian Input Resource
control intl.cpl,, /f:"itremove.xml"
REM This adds & sets as default the Japanese Input Resource
control intl.cpl,, /f:"jp.xml"
copy JAPAN.CFG LAYOUTJAPAN.CUR
goto END

:DOITALIAN
REM This changes the My-T-Soft Layout
cpycnmts.exe ITALIAN.CFG
REM This removes Japanese Input Resource
control intl.cpl,, /f:"jpremove.xml"
REM This adds and sets as default the Italian Input Resource
control intl.cpl,, /f:"it.xml"

DEL LAYOUTJAPAN.CUR

:END


Notes:

• The add/remove settings could reside in a single XML file, but for clarity each step is done independently.
• Permissions and UIPI issues can limit system level changes - reference first part of example (link at top) and test as Administrator if limited user is not changing layouts as desired.
• If Input Layouts do not change, check Event Viewer (specific log referenced above in batch file) for potential text or syntax issues
• Testing with Administrator Command Prompt may be helpful
• This example adds/removes only the specified languages - it may be desirable to only have a single input layout in use, but care must be taken in ensuring there is at least 1 input layout available.
• The Japanese InputLanguageID uses GUID codes - for Asian languages past Windows 7, the GUID ID= settings are required - reference Microsoft documentation for other language identifiers
• Japanese uses an IME (Input Method Editor), and you may need to select Hiragana as the input method. If you are not familiar with the Hiragana input method, it should be noted that Latin characters (Romaji) may appear (use space bar for viewing input candidates) - using the Layout indicator on the Taskbar or as a floating window is the definitive way to determine what the current input layout/method is set at.
• This approach can be extended to additional languages as needed - reference Microsoft IDs based on current version of Windows
• These XML files just touch upon some of the capabilities of the unattended GlobalSettings changes. There are ways to change values for the system or other users, many more settings, and other options that are not covered here - this only uses the option to add and set as default the current input layout

My-T-Soft for Windows

The Transparency option dates back to features available in Windows 2000 and spans many versions of the software and versions of Windows. Here is a quick overview of the transparency settings:

For the 1.xx software, My-T-Soft uses MYTSOFT.INI settings. These can be manipulated via the SeeThru.exe tool (accessible to the user from the My-T-Soft Menu | Advanced | Transparency). Note that on some versions of Windows and User Account Control settings, a higher privileged MYTSOFT.exe may need to be run (Run as Administrator, or use MYTSOFT.requireAdministrator.exe (default privileges are asInvoker)). These settings can also be accessed via My-T-Soft Setup | Configuration | Special Options | Edit My-T-Soft Initialization File.

[Configuration]
...
Transparency=1
TransparencyLevel=175
...


Where Transparency is set to 1 for enabled, 0 for disabled, and TransparencyLevel ranges from 0-255 where 0 is completely transparent (invisible) and 255 is completely opaque (as if Transparency not enabled).

Here are additional notes for these intiialization file settings:

http://www.imgpresents.com/mytsoft/guide/html/mytsoftini.html#Transparency

In My-T-Soft 1.90 and 2.xx software, the SeeThru.exe updates the following registry key/values:

Registry file between ===== lines
=================================

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Innovation Management Group\Build-A-Board]
"Transparency"="1"
"TransparencyLevel"="111"


=================================

Seethru.exe is used by the 2.xx runtime software on Windows to enable Transparency and set transparency level. The 2.xx SeeThru.exe tool ONLY updates this registry setting. To obtain this executable (e.g. My-T-Soft Basic, refer to the BIN folder in Build-A-Board - use Windows Explorer and find file \Program Files\Build-A-Board\BIN\Seethru.exe)

NOTES:
If you have My-T-Soft 1.90 and use SeeThru.exe it updates both the INI and the registry, so either version (1.xx or 2.xx) that runs will reflect the same transparancy setting. If using custom layouts from Build-A-Board, only the registry setting needs to be manipulated.

As noted above, a higher privilege may be needed so the run-time SeeThru.exe has access to update registry settings. SeeThru.exe is in the \Program Files\MYTSOFT folder. For Build-A-Board, it is in the \Program Files\Build-A-Board\BIN folder.

My-T-Soft for Mac OS X

There is a SeeThru tool that operates similar to the Windows version available in the My-T-Soft folder

My-T-Soft for Android

The Transparency level is set via the My-T-Soft Settings via a slider - there is no enable/disable, this simply sets the level from completely transparent to completely opaque used to display the My-T-Soft layout (alpha level ranges 0-255)

This settings is part of the My-T-Soft_preferences.xml settings that can be exported/imported - it is an integer setting (number) that can range between 0-255. Note that very low numbers may result in an invisble keyboard, which may not be helpful, but can also create an interesting user interface.

Extract the developer's kit (Start Menu | Programs | My-T-Touch | Install Developer's Kit), then look in the \WINDOWS\MYTTOUCH\LOGOS folder. Note that the Custom Logo has to be On (My-T-Touch Setup | Configuration | Special Options - Custom Logo), and the logo files need to reside in the same folder as MYTTOUCH.EXE (e.g. \WINDOWS\MYTTOUCH).
In the LOGOS folder, you will find LOGO01.BMP, LOGO02.BMP, LOGO03.BMP, …, LOGO12.BMP. There are 12 base sizes in My-T-Touch, and for each size you want the custom logo displayed, the corresponding LOGO??.BMP must exist in the same folder as MYTTOUCH.EXE . For display sizes larger than 12, the LOGO12.BMP is scaled up. So the easiest way to display custom logos is to copy the LOGO??.BMP files from the Logos folder to the parent folder (e.g. from \WINDOWS\MYTTOUCH\LOGOS to \WINDOWS\MYTTOUCH). Now when you run My-T-Touch, you will see the "& Your Logo" example displayed at all sizes. There is additional information in the LOGOS.TXT file in the LOGOS folder.
To display your own custom logo, to the following:

• Close My-T-Touch
• Open My-T-Touch Setup, and turn on "Use Custom Logo" in Special options
• Unzip LOGOS.ZIP, then copy the LOGO??.BMP from the LOGOS folder to \WINDOWS\MYTTOUCH
• Establish which sizes you will be displaying, e.g. 10, 11, 12
• Modify LOGO10.BMP, LOGO11.BMP, and LOGO12.BMP in the \WINDOWS\MYTTOUCH folder
• Run My-T-Touch

This applies to My-T-Soft/My-T-Pen/My-T-Touch 1.70 and above.
Original ID: QD253207

This approach works with Build-A-Board layouts only when starting MYTSOFT.EXE - it does not allow you to change the layout from the already running process.

In MYTSOFT.EXE 2.10, you can select different layouts via a button using the CMD:NKBF (New KBF) if you want the user to switch on-the-fly. If you want to externally change the displayed layout on-the-fly, you need to do some dancing. It will make a bit more sense if I describe first what is going on, and then the details.

Assume there is a keyboard.kbf, and a mylayout.kbf.

In the code, everything is triggered off of an action (typically represented by a button press & the actual action is then generated by Build-A-Board). So the built-in way to change the layout is to execute the [CMD:NKBF=mylayout.kbf]. This can be put behind a button & this command (macro) placed into the Key Action in Build-A-Board. The trick is to generate this command externally. The TYPEFILE.EXE (see Tech Item PU2005120235, keystrokes longer than 30 characters) allows an external command to be triggered. The naming is unfortunate, since it can do more than just type a file. The salient point is that it can trigger a macro/command just as if the Key Action generated it. So the dance is to create a file with the [CMD:NKBF...] in it, save it as a file, then use TYPEFILE.EXE to execute from an external program - this will allow the layouts to change on the fly externally.

So here are the details. Download the TYPEFILE.EXE from our website (see link above). Place this & the mylayout.kbf in MSWIN folder of the project you are working with. Use a windowed command prompt to test, then once you have the syntax down, integrate it with your application.

• cd "\Program Files\Build-A-Board\Target\[My Project]\MSWIN[Enter]
• dir TYPEFILE.EXE
• ... TYPEFILE.EXE
• dir mylayout.kbf
• ... MYLAYOUT.KBF

Create 2 simple text files with the commands embedded in it (e.g. NOTEPAD or EDIT or COPY CON MYLAYOUT.KMF) Note I am using KMF for Keyboard Macro File, and the layout is KBF for KeyBoard File

• Here it is from the CMD prompt
>COPY CON MYLAYOUT.KMF
• [CMD:NKBF=MYLAYOUT.KBF]^Z
• (Ctrl-Z or F6 key to "end" file)
• Then do it again for KEYBOARD.KBF
• COPY CON KEYBOARD.KMF
• [CMD:NKBF=KEYBOARD.KBF]^Z
• (Ctrl-Z or F6 key to "end" file)
• Now run MYTSOFT.EXE
• MYTSOFT
• Now run "typefile MYLAYOUT.KMF"
• typefile mylayout.kmf
• This will switch the layout
• typefile keyboard.kmf
• This will switch it back.

You will want to download the KBFDUMP Utility, that can extract the data from the KBF file, and optionally, extract the data and re-create source files, usable by the Build-A-Board builder.

IMPORTANT - the following is ONLY for 2.10 KBF files

Download KBFDUMP.EXE command-line utility KBFDUMP.EXE (56K) (MD5: 6FD0E051602E06DDD7A50043CBEA3E83)
Download KBFDUMP.EXE command-line utility as ZIP file: KBFDUMP.ZIP (22K) (MD5: FAAC0E95FF3CCB37CB3FDAA165075F75)

IMPORTANT - the following is ONLY for 2.20 KBF files (see specific instructions below)

Download KBFDUMP.EXE (beta) command-line utility as ZIP file: KBFDUMP220.ZIP (22K) (MD5: 099D1FB026F9DA6630A76DD94B6D83C1)

---

KBFDUMP.EXE for 2.10 files Usage Notes:

Usage: KBFDUMP [KBFFileName]
(If no file name specified, KEYBOARD.KBF is used)
To extract SOURCE projects from KBF files, use "-extract"
Usage: KBFDUMP -extract [KBFFileName]
(If no file name specified, KEYBOARD.KBF is used)
Extracted project files will be saved to ExtractedKBFProject[#]
These source files will be located in Build-A-Board\Source folder

• Instructions (if running Build-A-Board 2.10 Version / Build-A-Board 2.20 NOT installed):
• Download the KBFDUMP.EXE utility, and place in the \Program Files\Build-A-Board\Bin folder
• From the command-line (CMD project), in \Program Files\Build-A-Board\Bin, run KBFDUMP on the existing KBF file you have, e.g. KBFDUMP -extract "\My Documents\KEYBOARD.KBF"
• Now go into the Build-A-Board Builder
• Use File | Open, and select and open ExtractedKBFProject
• From the opened ExtractedKBFProject, use File | Save As… and select a new name for the project (Example: MyLostProjectt)
• Use File | Close to close (& save) the project
• Now copy the \Program Files\Build-A-Board\Source\MyLostProject\MyLostProject.zip to a safe place, and repeat "I will always backup my source files" as many times as necessary

• Instructions (if Build-A-Board 2.20 installed):
• Download the KBFDUMP.EXE utility, and place in the \Program Files\Build-A-Board\Bin folder (or \Program Files (x86)\Build-A-Board\Bin if on a 64-bit system)
• Identify the 2.10 KBF file you want to convert
• Locate your SOURCE folder for your system (e.g. \Users\Public\Documents\Build-A-Board\SOURCE), then make a new folder for the project (i.e. OldLayout)
• Copy the 2.10 KBF into the OldLayout folder
• At the CMD prompt, change to the OldLayout folder, then run \Program Files\Build-A-Board\BIN\KBFDUMP.exe -extract KEYBOARD.KBF (or name of KBF file)
• Edit the new PROJECT.TXT to exactly match the folder you are in (here OldLayout) (e.g. Notepad PROJECT.TXT) The file should have one line and it MUST match the folder name, e.g. OldLayout) (Note: This should be an ANSI text file, not a UNICODE text file - if already UNICODE, you should restart and NOT convert before changing project file - once PROJECT.TXT is a Unicode file, Build-A-Board will treat it as non-2.10 project)
• Now go into the Build-A-Board Builder
• Scroll down and select the OldLayout project
• Note: If you get an Error Allocating Memory listing MWF00001.MWF, you did not name the PROJECT.TXT file correctly. The project has been converted incorrectly, you need to delete the folder (e.g. OldLayout folder) from the SOURCE folder, AND delete the "OldLayout original 2.10 files", and then close Build-A-Board, and start at the top).
• When prompted, select Yes to Convert to 2.20, or say No, and keep as a 2.10 target project

---

KBFDUMP.EXE for 2.20 files Usage Notes:

Usage: KBFDUMP [KBFFileName]
(If no file name specified, KEYBOARD.KBF is used)
To extract SOURCE projects from KBF files, use "-extract"
Usage: KBFDUMP -extract [KBFFileName]
(If no file name specified, KEYBOARD.KBF is used)
Extracted project files will be saved to ExtractedKBFProject[#]
These source files will be located in Build-A-Board\Source folder

• Instructions (Build-A-Board 2.20 must be installed):
• Download the KBFDUMP.EXE utility, and place in the \Program Files\Build-A-Board\Bin folder (or \Program Files (x86)\Build-A-Board\Bin if on a 64-bit system)
• Identify the 2.20 KBF file you want to convert
• At the CMD prompt, change to the folder that contains the KBF file you want to obtain the source, then run \Program Files\Build-A-Board\BIN\KBFDUMP.exe -extract KEYBOARD.KBF (or name of KBF file)(e.g. C:\SomeFolderwitha220KBFFile>\Program Files\Build-A-Board\BIN\KBFDUMP.exe -extract MyLostSource.KBF[Enter]
• Now run Build-A-Board (if Build-A-Board is running, right-click and Refresh View to update projects)
• Find the ExtractKBFProject[#] project and open it.
• Important Note: You may see some errors (STT file, etc.) These can be ignored, but the VERY FIRST thing you do once the project has been opened is select File | Save As... and rename/save as a different project, e.g. MySourceThatIWillSaveForever
• At this point, you should be able to build/modify/save/close project. If there are any errors, you will need to redo the kbfdump steps from the KBF file

---

Extracting File from KBF (Linux command line example)

In this example, we will use dd (Linux command line utility) to extract IMG00000.PNG from an existing KBF.
If you use kbfdump FILENAME.KBF[Enter] you will get a listing of headers, files, and offsets. Record the Startoffset from KBF header (1102), and the Startoffset from the file interested in (57534), as well as the file size (524138) - relevant output results below:
===========
KBF HEADER
===========
BYTE Sig[2] = M+
BYTE Ver[3] = 220
DWORD Startoffset = 1102 | 0x044E
BYTE Level = 2 | 0x0002
... ...
... ...
... ...
======================
KBF Files/Offsets 44
======================
BYTE FileName[13] = IMG00000.PNG
DWORD Startoffset = 57534 | 0xE0BE
DWORD Length = 524138 | 0x7FF6A

Now, at Linux command prompt in directory containing KBF file:
dd if=FILENAME.KBF of=WANTEDIMG.PNG bs=1 count=524138 skip=58636[Enter]
Explanation:

• dd - main command (Data Description/Disk Dump/Data Dump to copy/convert data)
• if=FILENAME.KBF - Input File is our KBF file name FILENAME.KBF
• of=WANTEDIMG.PNG - Output File is the PNG file name
• bs=1 - Block Size is 1 byte
• count=524138 - Count of blocks (here, bytes) - file size of wanted PNG file
• skip=58636 - Skip blocks 1102+57534 (data start offset + file start offset)

---

IMPORTANT NOTES

• Be sure to use a copy of the original .KBF file - save/copy/backup your original files before processing / using this sequence (the original will remain untouched, but it helps to have the original as a reference if you keep the same file name and build an updated .KBF with the same name)
• If needed, you can remove SOURCE folders with extracted files by using Windows Explorer and going to \Users\Public\Documents\Build-A-Board\SOURCE. If doing this, it is suggested to close Build-A-Board Builder first, and be careful deleting folders from the SOURCE folder - you may want to move to a different location rather than deleting. Also note there is a matching [Folder Name].BMP file that should be removed.
• For 210 KBFs: You will want to convert 2.10 files to the 2.20 version for best results - refer to Build-A-Board help for notes on staying/building 2.10 targets from the 2.20 Build-A-Board.

• Other notes:
• For 2.10 KBFDUMP.exe: This utility is also in the Developer's Kit 1.78 Release 2, available in the Developer's corner, and there are further detailed notes on the utility.
• For 2.20 KBFDUMP.exe: This utility is still in development and not available (except here as a beta) for any release prior to Build-A-Board 2.20 Release 5.
• By default, the utility also dumps to the screen the data values of the KBF file. You can use output redirection to save to a file, e.g. KBFDUMP > KBF.TXT
• We can't stress the importance of backing up your source files enough.

Simply run the downloaded EXE (executable) file. It will self-extract, and run Setup for you automatically.
Original ID: QI111316

Platform licenses are only available to customers who have purchased the appropriate IMG License. This item is for helping customers who know they have a Platform License, and wish to see step-by-step of how to obtain and work with this type of license. If you wish to purchase or learn more about the benefits of a Platform license, please contact IMG Sales at sales@imgpresents.com or refer to this general overview of license options.

How To License Build-A-Board and obtain your Platform License

On the system where you plan to develop boards (typically a developer or support system, i.e. not a system that will be deployed), install download and install Build-A-Board. After installation, run the IMG License Manager (Licensing Information icon) - either from the Program Group in Windows Explorer, or from the Start Menu in the Build-A-Board group.


When unlicensed, you will see the following screen - click on Retrieve System License to retrieve or apply a license to your system.


If this is a new or unrecognized system, a license cannot be retrieved without first adding the system to the existing account where the platform license is associated with - this is the account you must use when licensing a new system. Refer to the following screens to use your Build-A-Board.com credentials and license this system.


Once you've entered your login e-mail and password, and named your system (to help identify licenses in the Build-A-Board.com License Manager tab), click on "Add This System"

For Build-A-Board licenses, you will see the following screen to indicate that the system is now part of your account.


Return to the IMG License Manager, and click again on the Retrieve System License button.


After the license is retrieved from your account, you will see a "Licensed and Registered..." display. IMPORTANT: There must be a Serial Number of the form BAB220?????? Indicated in the serial number line for you to continue. If there is no serial number, or it indicates IMG Personal License, or other entry, and you have a Platform License, please contact IMG Customer Service at at cs@imgpresents.com


To retrieve your Platform license, click on the Expand >>> button to reveal the Platform License section.


Now click on Retrieve Platform Authorization to obtain the Platform License. The actual details displayed here will be determined by the license purchased. Once your Platform License is in place, all boards that will be deployed need to be opened and built from this Build-A-Board system (when a .KBF is built it will include the Platform License, which will allow licensed operation on all indicated platforms).

---

Build-A-Board Platform License Notes

The Build-A-Board Platform License allows you to create then build boards that have the license embedded in the board (KeyBoard File, the .KBF file). When deploying dozens, hundreds, or thousands of devices, this type of license greatly reduces the license management required to deploy and maintain boards at your site or across the enterprise.

This type of license required a Build-A-Board serial # (of the form BAB220??????), a Build-A-Board.com Account, and the appropriate IMG license, e.g. IMG Technology License, or an OEM/Distribution license, etc. These licenses require an Annual Maintenance program to keep the license active, and enable ongoing support, free updates, free upgrades, etc.

For detailed usage options using the IMG License Manager, refer to the product help here: http://www.imgpresents.com/bldabrd/guide/html/licensemanager.html

---

General Deployment steps for a Build-A-Board Platform License

1) On development machine, install current Build-A-Board (If the machine already has a free or other license, you should do the following steps - Open the IMG License Manager (Licensing Information icon/LICENSE.EXE) and click on "Additional License Options/Support", then click on "Delete (Reset) License File (LICENSE.LIC)" and confirm the deletion - this will clear out any existing license)

2) License Build-A-Board with account login (e-mail/password), and Retrieve Platform Authorization (Refer to step-by-step above)

3) Now in Build-A-Board, open all boards projects to be deployed, and Build - this will create KBFs with the license embedded. IMPORTANT - to get a licensed board, you must rebuild the project with the licensed Build-A-Board which has retrieved Platform license (the build process embeds the license into the .KBF file).

4) Collect all licensed custom Keyboards (.KBF files) - within Build-A-Board, use Shift-F11 to view Target run-time folders for current project, and refer to other projects to gather any other necessary KBF files. Remember KEYBOARD.KBF is default layout - the layout that will open when My-T-Soft is run.

5) To deploy to run-time target system:

To get My-T-Soft onto target system:

Windows: use MSWIN32 or MSWIN64 run-time target folder, or use My-T-Soft Basic install, or My-T-Soft 1.90 install
Android: use My-T-Soft for Android .apk install file
Linux: use My-T-Soft for Linux tar.gz file

After My-T-Soft installed, deploy these licensed .KBF files to target systems (remember KEYBOARD.KBF is default layout) - here are locations:

Windows: Public Documents, Build-A-Board, BOARDS folder - e.g. \Users\Public\Documents\Build-A-Board\BOARDS
Android: external storage, Build-A-Board, BOARDS folder - e.g. /sdcard/Build-A-Board/BOARDS
Linux: same folder as mytsoft executable, e.g. ~/my-t-soft

No when you run My-T-Soft, it will open the default KEYBOARD.KBF, which will be licensed with your platform license. So a Windows platform license will run licensed on any Windows system, but be unlicensed on Android or Linux, etc.

The issue is pretty simple - Ctrl-Shift-g is not the same as Ctrl-g. There are mentions in various places about lowercase being preferred, but this problem is inherent in computers doing what they are told. To generate a capital letter from a physical keyboard, the shift key needs to be held down, and when the macro handling part of the software sees an uppercase character it faithfully generates the sequence of keystrokes necessary to create the letter. When doing straight text, e.g. "Hello World" - ",Shift-h,e,l,l,o, Shift-w,o,r,l,d" this works just fine, all is well, and everyone is happy. When trying to use control/alt type sequences, this can sometimes cause problems, as the extra shift state causes the underlying application to treat it differently. To get a keystroke for g, and g alone, you must specify "g" in the macro, NOT G. G generates a [Shift-Down]g[Shift-Up] macro sequence. Therefore [Ctrl-down]G[Ctrl-Up] generates [Ctrl-down][Shift-Down]g[Shift-Up][Ctrl-Up], not the [Ctrl-Down]g[Ctrl-Up] sequence you want.

Some apps work fine in either upper or lower case, but when the app doesn't, you must stick with the lowercase letter in the macro.

Yes, although not directly with the mytsoft executable or by specifying a location directly. The approach is to use a symbolic link in the Linux file system to locate the actual log file in a different directory. As a quick background, the log file must be named mytsoft.log, and it is used as a flag to indicate the executable should log certain events. This must exist in the same folder as the executable. However, on some systems there may be a preferred log file location, or there could be other security issues that preclude using the executable location. So the solution is to use the ability in the Linux file system to create a symbolic link to the actual file.

Let's say you have a log location like:

/var/log/ourfiles/logs

First make sure no current mytsoft.log exists in the mytsoft folder (i.e. where the executable is).

Then do the following to match your speciifc situation:

cd /var/log/ourfiles/logs[Enter] (Change to log location)
touch mytsoft.log[Enter] (create empty file in log location)
cd /location/where/mytsoft/is/[Enter] (Change to where mytsoft is)
ln -s /var/log/ourfiles/logs/mytsoft.log mytsoft.log[Enter] (create symbolic link)

Run the mytsoft executable. The actual logged entries will be in the mytsoft.log in the /var/log location

Of course, permissions and all that needs to be configured so there is appropriate write access available to the user/process. Important to test and verify the proper functioning of this approach.

This works because the flag to enable logging is just the existence of the mytsoft.log file, and with the symbolic link, the mytsoft executable sees the symbolic link file as the flag, while the actual "file" is the one in the log location. The end result is the log data is placed in an external file in a different location (as specified).

If the version you are running does not have a Font button, you can download the update, or refer to the notes below for options.
To download TTSAPP.exe with Font button/Font support, select zip or exe and follow instructions.
Download TTSAPP.exe (820KB) (MD5: 480d4dd57627bfaa14f2bf844b46b22f) 9/13/2013
Download TTSAPP.exe as Zip TTSAPP.zip (72KB) (MD5: 050307397c304a7f53e6798c62b8d643) 9/13/2013

• Download selected file and note download location
• If zip, right-click, and Extract all to obtain TTSAPP.exe
• As Administrator, rename TTSAPP.exe in \Program Files\ONSCREEN or \Program Files\OnScreen with CrossScanner as TTSAPP.old
• Copy new TTSAPP.exe from download location into appropriate \Program Files location

Work with new version - Select Font as desired. Last selected Font will be used when opening Text-To-Speech

• Notes
• Font information is saved in TTSAPP.INI, which is saved in same folder as TTSAPP.exe - for newer versions of windows, actual file will be in Virtual Store location for user - see \Users\[User]\AppData\Local\VirtualStore\Program Files\ONSCREEN, etc.
• This update will roll into any future releases that are created from new builds

If using the older one without font support, you can refer to the following:

• Open WordPad (Start | type "wordpad" | Enter, or Programs | Accessories | WordPad)
• Select a font/size/bold that is easy to read.
• Type some text
• Select All/Copy (Ctrl-A | Ctrl-C)
• Switch to Text-To-Speech utility
• Paste into text area - it should keep the font

Now if you type/work with the text box, it should preserve the pasted font info.

There is no comprehensive way to build arbitrary keystroke macros similar to Shift or Ctrl macros. When you use a macro with the keystroke (e.g. [Insert]), it generates a down/up complete keystroke, so [Insert][Down] will generate an insert key then a down arrow key, i.e. Insert-Down Insert-Up Down Arrow-Down Down Arrow-Up. To do a shifted Down Arrow, you would use the macro [Shift-Down][Down][Shift-Up]. If you need an Insert-Down Down Arrow-Down Down Arrow-Up Insert-Up, something custom is required (i.e. there is no way in current versions of the software to create such a macro).

You can download a set of Executables that generate an Insert-Up Arrow, Insert-Down Arrow, Insert-Left Arrow, Insert-Right Arrow set of macros (4 executable files named KEYINS-UP.EXE, KEYINS-DOWN.EXE, KEYINS-LEFT.EXE, KEYINS-RIGHT.EXE). These generate the following sequence:
Insert-Down [Arrow]-Down [Arrow]-Up Insert-Up

Download Key Insert Macros in keyinsertmacros.zip (64KB) (10/11/2013) (MD5: 97906D2FD28455182FB3334886D49D47)
Download and then Extract, then as Administrator, copy into \Program Files\ONSCREEN

To use with OnScreen (or My-T-Soft/etc.) you can use the Key Options or a macro panel. To Use the Key Options, refer to the following steps:
1) In OnScreen Setup, make sure the Advanced option is set under User Options
2) Then go into Appearance | Key Options
3) Select an appropriate function key for the Macro executable in the Key drop down (e.g. F12)
5) Click on Disable Keystroke (you do not want to send the function key keystroke - this will undoubtedly cause different problems in different situations)
6) Click on Launch Key Executable.
7) Browse and select the KEYINS-DOWN.EXE file (e.g. C:\Program Files\ONSCREEN\KEYINS-DOWN.EXE)
8) Select Ok | Ok and Exit OnScreen Setup

Now when you run OnScreen, the F12 key will generate the Insert-Down Arrow macro.

Notes:At some point, the macro language will expand to allow down/up and latching type operation on arbitrary keys similar to the current Shift/Ctrl/Alt handling. Until that point, custom macros may be necessary if there are not options with the application to perform a keystroke macro. Note that menu options can all be accessed with the existing macro system, e.g. Alt-F, O for File | Open is simply [Alt-Down]f[Alt-Up]o.
You may want to reference other details/options/notes about the Key Options - see Item QU1106120501
If you have a special situation that you cannot resolve with the above information, please contact IMG Technical Support.

Make sure "Always prompt for password" setting is enabled on the server. At the server as Administrator, select Start | Administrative Tools | Terminal Services Configuration, then highlight the Connection entry on the left and double-click (or right-click | properties) on the RDP-Tcp entry on the right. Under the Logon Settings tab, verify the "Use client-provided logon information" is selected, and make sure the "Always prompt for password" is checked on.

Now at the client, in Remote Desktop Connection, select Options - under the General tab, make sure "Always ask for credentials" is clear (since you will be logging in at the server logon screen).

The first time you connect, you will have to specify [Domain]\user / password. Make sure the "Remember my password" is checked on. IMPORTANT: Make sure your saved credentials are of the form TERMSERVER\username, NOT username@TERMSERVER.

Note: If you are using My-T-Soft TS with the logon utilities, and your client requires a client based on-screen keyboard to accomplish this configuration, contact IMG Technical support for assistance.

Once you have successfully logged on, you will not need to enter name/password at the client, and will be prompted by the server at the normal logon screen. Also, once this is configured, you can also logon using "mstsc.exe /v:TERMSERVER".

• Notes

• Saving the name/password configuration on the client is not much different than the client entering this same information at the logon screen - the client has access to this information in both cases, and the server is authenticating in both cases. Refer to Microsoft for further information on why this is a more secure approach.

• Depending on the client, there may be other options available (e.g. older versions of the Terminal Services Client (note that the MSTSC.exe used to be an installable extra))
• Since the client may need an on-screen keyboard, and IMG has solutions for just about all known devices, the My-T-Soft TS license will be extended to provide this client based tool if required. Contact IMG Technical support for further information.

The issue is pretty simple - Ctrl-Shift-g is not the same as Ctrl-g. There are mentions in various places about lowercase being preferred, but this problem is inherent in computers doing what they are told. To generate a capital letter from a physical keyboard, the shift key needs to be held down, and when the macro handling part of the software sees an uppercase character it faithfully generates the sequence of keystrokes necessary to create the letter. When doing straight text, e.g. "Hello World" - ",Shift-h,e,l,l,o, Shift-w,o,r,l,d" this works just fine, all is well, and everyone is happy. When trying to use control/alt type sequences, this can sometimes cause problems, as the extra shift state causes the underlying application to treat it differently. To get a keystroke for g, and g alone, you must specifcy "g" in the macro, NOT G. G generates a [Shift-Down]g[Shift-Up] macro sequence. Therefore [Ctrl-down]G[Ctrl-Up] generates [Ctrl-down][Shift-Down]g[Shift-Up][Ctrl-Up], not the [Ctrl-Down]g[Ctrl-Up] sequence you want.

Some apps work fine in either upper or lower case, but when the app doesn't, you must stick with the lowercase letter in the macro.

Review the OPEN_MTS source code & executable in the DevKit folder (after extracting the Developer's Kit - Start Menu | Programs | My-T-Pen | Install Developer's Kit). When minimized, OPEN_MTS will "restore" the keyboard programmatically.
The other common methods using the Developer's Kit of controlling the visual display to the user are MOVEWMTS (uses the MoveWindow API), and CPYCNMTS (Copy and configure) which can use multiple configuration files to show different configurations & screen positions.
Original ID: QU253435

The workaround for this is to emulate the virtual key for the [ key. This is VK_OEM_4 on the US layout. The following macro performs what you are looking for.

[Ctrl-Down]x[Ctrl-Up]Me!%%v219[Ctrl-Down]v[Ctrl-Up]]

The reason this occurs, as you surmised, is the parsing code itself. Essentially the open bracket starts a reserved word, and there is no allowance for an open bracket, THEN a reserved word. The workaround above is required to work as you desire.

The issue is pretty simple - Ctrl-Shift-g is not the same as Ctrl-g. There are mentions in various places about lowercase being preferred, but this problem is inherent in computers doing what they are told. To generate a capital letter from a physical keyboard, the shift key needs to be held down, and when the macro handling part of the software sees an uppercase character it faithfully generates the sequence of keystrokes necessary to create the letter. When doing straight text, e.g. "Hello World" - ",Shift-h,e,l,l,o, Shift-w,o,r,l,d" this works just fine, all is well, and everyone is happy. When trying to use control/alt type sequences, this can sometimes cause problems, as the extra shift state causes the underlying application to treat it differently. To get a keystroke for g, and g alone, you must specifcy "g" in the macro, NOT G. G generates a [Shift-Down]g[Shift-Up] macro sequence. Therefore [Ctrl-down]G[Ctrl-Up] generates [Ctrl-down][Shift-Down]g[Shift-Up][Ctrl-Up], not the [Ctrl-Down]g[Ctrl-Up] sequence you want.

Some apps work fine in either upper or lower case, but when the app doesn't, you must stick with the lowercase letter in the macro.

The issue is pretty simple - Ctrl-Shift-g is not the same as Ctrl-g. There are mentions in various places about lowercase being preferred, but this problem is inherent in computers doing what they are told. To generate a capital letter from a physical keyboard, the shift key needs to be held down, and when the macro handling part of the software sees an uppercase character it faithfully generates the sequence of keystrokes necessary to create the letter. When doing straight text, e.g. "Hello World" - ",Shift-h,e,l,l,o, Shift-w,o,r,l,d" this works just fine, all is well, and everyone is happy. When trying to use control/alt type sequences, this can sometimes cause problems, as the extra shift state causes the underlying application to treat it differently. To get a keystroke for g, and g alone, you must specify "g" in the macro, NOT G. G generates a [Shift-Down]g[Shift-Up] macro sequence. Therefore [Ctrl-down]G[Ctrl-Up] generates [Ctrl-down][Shift-Down]g[Shift-Up][Ctrl-Up], not the [Ctrl-Down]g[Ctrl-Up] sequence you want.

Some apps work fine in either upper or lower case, but when the app doesn't, you must stick with the lowercase letter in the macro.

The user login screen (sometimes referred to as the LoginWindow or greeter) in X windows is separate from the user's desktop (logged on session). There are many possibilities, so this outlines the basics for a reasonably new distribution running GNOME or KDE for a workstation (hard drive boots and runs the operating system). The general approach is to run the mytsoft process prior to the appearance of the login window.
For different window managers/display managers, the process which handles the login (startup/init/greeter) is different, and the configuration files and locations are different.
GNOME uses gdm - most likely script location is /etc/gdm/Init/Default
KDE use kdm - most likely script location is /etc/kde4/kdm/Xsetup (or /etc/kde3/kdm or /usr/kde/version/share/config)
others may use xdm - most likely script location is /etc/xdm/Xsetup

Steps
Step 1) Locate mytsoft executable - for example, perhaps /home/user/Downloads/my-t-soft/mytsoft
Step 2) Identify and using your favorite editor, open & edit the appropriate script for your system
Step 3) Each script can be different, and it is recommended that you add the following line towards the beginning (or top) of the script in case some logic exits or quits the script
/home/user/Downloads/my-t-soft/mytsoft &
(The ampersand is important as it loads the mytsoft process as a background process and does not stop the execution of the script)

Notes:

• This assumes that the system is configured for a graphical startup using X Windows (typically run-level 5)
• The display manager (gdm/kdm/xdm) may have options that can determine if the Default or Xsetup script are run (or if there are overrides)
• If SELinux is enabled (Security Enhanced Linux, e.g. Fedora, Red Hat, CentOS, etc.) you may need to specifically "allow" the execution of mytsoft, especially determined by location - see additional notes below.

SE Linux notes
In the above example, with SE Linux set to enforcing (e.g. /etc//selinux/config, SELINUX=enforcing), the execution of mytsoft may be blocked. You can test the configuration by setting SELINUX=disabled, and reboot - if it works in that configuration, but not with SELINUX=enforcing, then the following approach may work (if system configured correctly).
Logged in as root at terminal console:
[root]# audit2allow -a -M mytsoft
[root]# semodule -i mytsoft.pp
The above commands extract the audit log (/var/log/audit) to determine blocked execution, and creates a policy file (e.g. audit2allow), and then installs the policy file (semodule install)

The SE Linux concepts are complex, but here are a few more details that may help grasp what is needed - essentially if an operation is "denied", it must be explicitly "allowed" - the following is a human readable version of the policy (again, for the above example/location):
mytsoft.te - text file

module mytsoft 1.0;

require {
type user_home_t;
type xdm_t;
class file execute;
}

# xdm_t
allow xdm_t user_home_t;file execute;

To create the policy file, you may be able to use the selinux Makefile (depending on system configuration), e.g.:
[root]# make -f /usr/share/selinux/strict/include/Makefile mytsoft.pp
To check the built file before installing, you can use checkmodule, e.g.
[root]# checkmodule -b mytsoft.pp

To manually build the policy file from the .te file, use the following:
[root]# checkmodule -M -m -o mytsoft.mod mytsoft.te
[root]# semodule_package -o mytsoft.pp mytsoft.mod
[root]# checkmodule -b mytsoft.pp
[root]# semodule -i mytsoft.pp

Depending on installed software, you may need the Microsoft C Runtime files used by the GDIKIT.DLL/system GDIPlus.DLL. For details, refer to Build-A-Board help about Images
To install the Microsoft C Runtime files, download the zip file ms_runtime_libs_2000xp.zip 580K (MD5: 258CBD61F2E32D2AA81D33E9523F5D3B)
Copy or Move this file to \Program Files\My-T-Soft Basic
Unzip or right-click | Extract All and be sure to extract files into \Program Files\My-T-Soft Basic

The gdikit.dll is an interface from My-T-Soft Basic to system graphics support provided by GDIPlus.dll which will be on Windows XP (For Windows 2000, it may need to be installed - see Microsoft Knowledgebase KB975337). The GDIKIT.DLL may need run-time support if not already available on the system - these Microsoft run-time file provide that support if not already part of your Windows 2000/XP system.

The file scanner.txt can be created in the /sdcard/Build-A-Board/My-T-Soft_Import folder and has various options and overrides. Please refer to the readme.txt (the only file that will reside in that location after install) for details (and perhaps updated options). This file is created when My-T-Soft for Android is first run. Below is the section on scanner.txt (2.20.32) for reference online:

readme.txt / scanner.txt section:
If the file scanner.txt exists in the /sdcard/Build-A-Board/My-T-Soft_Import folder when the My-T-Soft for Android service is started, it will be imported and overwrite default settings. This file will be preserved, but will only be read in when My-T-Soft is started.
Note: These settings are currently meant to override options when a Honeywell device is used.

These are the override settings
(internal defaults indicated)

TriggerKeyScanCode1=257
TriggerKeyScanCode2=261
TriggerKeyScanCode3=-1
TriggerKeyScanCode4=-1
TriggerMode=OneShot
ScannerType=dcs.scanner.imager
Prefix=
Suffix=

Notes (supported values):
The Trigger Key ScanCode can be a numeric value that indicates the Android scancode of the hardware button that will be monitored to initiate a scan trigger. The 257/261 match the Honeywell CT60 scan codes.
A value of -1 means not used.
The TriggerKeyScanCode3 and TriggerKeyScanCode4 allow for up to 4 hardware trigger keys.
The Trigger Mode can be OneShot, Continuous, Release, or SecondPress
The Scanner Type can be: dcs.scanner.imager or dcs.scanner.ring: for internal or external scanner.
The Prefix / Suffix overrides can contain text strings or the special keys [Tab] and [Enter]. These keys are processed based on the Scan Tab/Enter Keys setting in My-T-Soft Settings.

Example:
Prefix=[Tab]
Suffix=[Enter][Enter]


The following walks through adding a scanner.txt to a device, and configuring the Prefix / Suffix Scan keys setting.
Note: When connecting your device, you may need to swipe down and change the USB connection mode: Use USB to "Transfer Files" to see the storage / file view.
Note: My-T-Soft for Android must be installed, selected as current keyboard, and brought up as input method before doing these steps.














Note that My-T-Soft will need to be re-loaded to refresh from any changes to scanner.txt. Probably the easiest way to do this is to select an alternate keyboard input, then re-select My-T-Soft as the active/current virtual keyboard. Also the file name must be lowercase, and be truly named scanner.txt on the Android device.

---

Finally, be sure to select the correct Scan setting in My-T-Soft for Android Settings


Scan Tab/Enter Keys
This option provides selection of how the Tab and Enter keys will be handled during a scan event. Select "Send as Keys" to send the Tab and Enter as virtual keystrokes (key down/up events). Select "Send as Editor Actions" to process the Input Field and query the field for appropriate action to perform on Enter, and to perform an "Next Field" action on Tab.

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 ...