The license algorithm uses a date embedded in the default (installation) license file. Build-A-Board 2.20 has been released and it is recommended that users upgrade, or refer to their annual maintenance options (or contact IMG Customer Service regarding Maintenance options). However due to standardization, validation issues, and the stability of the software, some customers require the use of 2.10 version.

• Set the System Date to 2009 (or any date prior to July 2010). Then run the IMG License Manager, license using the Certificate of Authenticity, and then reset the system date to the correct, current date. Once licensed, there is no date issue - it is only during the license process that the date be set prior to July 2010
• Transfer the license If this is a single license, or a few licenses, perform a transfer on the website: Click here to Transfer a License
• Upgrade to the most current version or contact IMG Customer Service about Annual Maintenance and additional support options

When running the 95-XP run-time in Vista, you will get an "Improper Windows Version" message. You can enable the built-in compatibility mode for the software. For MYTSOFT.EXE, MACROBAT.EXE, LICENSE.EXE you can right-click, select properties, select the Compatibility tab and enable the compatibility mode for operation as Windows XP SP2. As an alternate workaround, you can download and overwrite the existing IMGVERS.DLL with this updated IMGVERS.DLL for Vista. (MD5: 4B235A355DAAF9E204F626EDB27175A9) Please note that this simply reports that Vista is the same as 2000/XP - this allows the software to run without the message, but no other accommodations for Vista (e.g. User Account Control/enhanced security/software manifests, etc.) occur.

Be sure to use the MSI (alternate download) install, e.g. BAB210.MSI

You must be an Administrator to install Build-A-Board. If Limited User, and User Account Control (UAC) is on, then SETUP.EXE should escalate and ask for an Administrator password. If UAC is Off, then it will not install. You must logon as Administrator to install Build-A-Board.

If using the 64-bit version, replace the \Program Files with \Program Files (x86) in the instructions below

Once installed, you must set compatibility to run, set permissions for licensing and operation, and move SOURCE and TARGET folder to a Public location

NOTE: Do not do this step for 64-bit Vista, i.e. do not set compatibility Use Windows Explorer, go into \Program Files\Build-A-Board\BIN, then Select BABTC.EXE, and Right-Click | select Properties, then select Compatibility Tab and select:
Run this program in compatibility mode for:
Windows XP (Service Pack 2)
Now do the same operations for BUILDER.EXE and LICENSE.EXE.

Now you must change Permissions - Under Program Files, select the Build-A-Board folder, and right-click | Properties. Under security tab, click on the Edit button below the users/groups list. It will ask for Administrator password. Then select the Users group, and give full control to the Build-A-Board folder. Then OK, OK.

At this point, you may update the IMGVERS.DLL, indicated at this help link - Updating IMGVERS.DLL for run-time MYTSOFT.EXE 2.10 to run in Vista. This file can be updated in \Program Files\Build-A-Board\BIN, \Program Files\Build-A-Board\BIN\MSWIN, and \Program Files\Build-A-Board\BIN\TEST.

Now you will be able to License Build-A-Board (License starting with BAB210??????). After Compatibility and permissions set, run \Program Files\Build-A-Board\BIN\LICENSE.EXE, and enter license code. You must be able to save to the file \Program Files\Build-A-Board\BIN\LICENSE.LIC, and the Permission step above should allow this. You can verify you have sufficient permissions by opening the LICENSE.LIC in Notepad, and enter a line, and save it, then re-open - the changes should be visible. Clear the line, and save it back in its original form, then run LICENSE.EXE

Working folders - For best results, move the SOURCE and TARGET folders to a public place (or your local user folders), and update Build-A-Board settings to reflect this change.

In Explorer, open another window and go into Users then into Public then into Public Documents, then create a folder called Build-A-Board. Now copy SOURCE and TARGET folders from \Program Files\Build-A-Board to \Users\Public\Documents\Build-A-Board

So now you should have 2 folders at:
\Users\Public\Documents\Build-A-Board\SOURCE and
\Users\Public\Documents\Build-A-Board\TARGET

Now run the Builder - Start Menu | All Programs | Build-a-Board | Build-A-Board Builder. Now select Edit menu | Properties, and click on the Global Settings Tab. Click on the ... button next to the source folder and select Public | Public Documents | Build-A-Board | SOURCE, and it should show C:\Users\Public\Documents\Build-A-Board\SOURCE for the Source.

Click on the ... button next to the Target folder and select Public | Public Documents | Build-A-Board | TARGET, and it should show C:\Users\Public\Documents\Build-A-Board\TARGET for the Target. Now click OK.

Once Build-A-Board is licensed by an Administrator, and the folders are moved to an area without limitations (the Program Files location is not available for storing data files in Windows Vista), you will be able to save projects, and operate Build-A-Board as a normal user - refer to the new location created above for Source files, and for Target files for built projects.

For more information about Windows Vista Click Here.

When running the 95-XP run-time in 7, you will get an "Improper Windows Version" message. You can enable the built-in compatibility mode for the software. For MYTSOFT.EXE, MACROBAT.EXE, LICENSE.EXE you can right-click, select properties, select the Compatibility tab and enable the compatibility mode for operation as Windows XP SP3. As an alternate workaround, you can download and overwrite the existing IMGVERS.DLL with this updated IMGVERS.DLL for Windows 7. (MD5: 6EF6AD0215549E697B8A56B5C5B1C266) Please note that this simply reports that 7 is the same as 2000/XP - this allows the software to run without the message, but no other accommodations for 7 (e.g. User Account Control/enhanced security/software manifests, etc.) occur.

You must be an Administrator to install Build-A-Board. If Limited User, and User Account Control (UAC) is on, then SETUP.EXE should escalate and ask for an Administrator password. If UAC is Off, then it will not install. You must logon as Administrator to install Build-A-Board.

Once installed, you must set compatibility to run, set permissions for licensing and operation, and move SOURCE and TARGET folder to a Public location

After install you must change Permissions - Under Program Files, select the Build-A-Board folder, and right-click | Properties. Under security tab, click on the Edit button below the users/groups list. It will ask for Administrator password. Then select the Users group, and give full control to the Build-A-Board folder. Then OK, OK.

At this point, you should update the IMGVERS.DLL, indicated at this help link - Updating IMGVERS.DLL for run-time MYTSOFT.EXE 2.10 to run in 7. This file can be updated in \Program Files\Build-A-Board\BIN, \Program Files\Build-A-Board\BIN\MSWIN, and \Program Files\Build-A-Board\BIN\TEST.

Now you will be able to License Build-A-Board (License starting with BAB210??????). After Compatibility and permissions set, run \Program Files\Build-A-Board\BIN\LICENSE.EXE, and enter license code. You must be able to save to the file \Program Files\Build-A-Board\BIN\LICENSE.LIC, and the Permission step above should allow this. You can verify you have sufficient permissions by opening the LICENSE.LIC in Notepad, and enter a line, and save it, then re-open - the changes should be visible. Clear the line, and save it back in its original form, then run LICENSE.EXE

Working folders - For best results, move the SOURCE and TARGET folders to a public place (or your local user folders), and update Build-A-Board settings to reflect this change.

In Explorer, open another window and go into Users then into Public then into Public Documents, then create a folder called Build-A-Board. Now copy SOURCE and TARGET folders from \Program Files\Build-A-Board to \Users\Public\Documents\Build-A-Board

So now you should have 2 folders at:
\Users\Public\Documents\Build-A-Board\SOURCE and
\Users\Public\Documents\Build-A-Board\TARGET

Now run the Builder - Start Menu | All Programs | Build-a-Board | Build-A-Board Builder. Now select Edit menu | Properties, and click on the Global Settings Tab. Click on the ... button next to the source folder and select Public | Public Documents | Build-A-Board | SOURCE, and it should show C:\Users\Public\Documents\Build-A-Board\SOURCE for the Source.

Click on the ... button next to the Target folder and select Public | Public Documents | Build-A-Board | TARGET, and it should show C:\Users\Public\Documents\Build-A-Board\TARGET for the Target. Now click OK.

Once Build-A-Board is licensed by an Administrator, and the folders are moved to an area without limitations (the Program Files location is not available for storing data files in Windows 7), you will be able to save projects, and operate Build-A-Board as a normal user - refer to the new location created above for Source files, and for Target files for built projects.

For more information about Windows 7 Click Here.

• 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

The 2.10 MSI install does not establish the registry entries for the Target and Source locations. To do this, after install, run the Build-A-Board builder, go to Edit | Properties, click on the Global Settings tab, then make some modification to the settings so the Apply button is enabled (e.g. click on the . . . Button, then click on Cancel, or click on the Single File Keyboard Layout button), then click Apply. This will save the settings for the Source, Target and Bin folders.

• ELO TouchSystems (95/98/Me/NT) - "Track Pointing Device Input at All Times" MUST be checked on to operate with ELO drivers
• 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)

Original ID: PU225145

Resolution: Update BABTC.EXE to version 2.11

This only affects a small number of systems - see technical notes below.

Since 2005, this update has been rolled into the available 2.10 versions.

• File provided as EXE or 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 folder, then rename existing BABTC.EXE to BABTC.210. Copy downloaded file into folder.
• Download Build-A-Board Text Compiler as BABTC.EXE 6/4/2003 (49k) (MD5: DD9456D9ADE005EF4DC1FBC3FA9B0CEB)
• Download Build-A-Board Text Compiler as BABTC211.ZIP 6/4/2003 (17k) (MD5: E71548D0EDBC1C7556EBDC2915D574B6) (unzips as BABTC.EXE)
• Technical Notes
• This update affects a buffer size issue in a Win32 API call, which worked correctly on most versions of Windows, but not all & depended on video driver, font, resolution, and possibly other factors.
• File tagged as 2.10.0.0 for compatibility with 2.10 version, but File Version / Product Version in Version Info section indicate 2.11.
• If you do not experience any of the above listed problems, there is no need for this update.
• 3 changes include File API calls, buffer size issue, and Word wrap setting for text buffer.

Original ID: PU225146

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

Character keys do not generate characters in application
I need support for a different processor
My application is topmost and above the My-T-Soft window
I need an "L" layout or a framed layout
I need the Alt combination keys for my application and wan't user control vs. pre-built macros

• Resolution: Update MYTSOFT.EXE to version 2.14 (or 2.17) - see below for supported processors
• Version 2.14 is compiled with Embedded Visual C++ 4.0, so more processors are supported. See Download notes below for important information for integrating with Build-A-Board 2.10!
• Some OEMs do not include a full keyboard driver, so not all keyboard events can not be translated into characters. Also issues with available characters on device. Version 2.14 now supports full virtual operation to accommodate systems without physical keyboard support - CHARMAP.KMF file is required, and toggles operation mode when included with MYTSOFT.EXE - if present, "soft" or "virtual" keystrokes are used rather than emulating physical keyboard events. This is for use in Windows CE ONLY!
• Download My-T-Soft CE 2.14 for ARM V4 M214AR4.EXE 11/26/2002 (69k) (MD5: D892C3EC54048AF51C24CFB4EB7D150B)
• Download My-T-Soft CE 2.14 for ARM V4I M214AR4I.EXE 11/26/2002 (69k) (MD5: A9AA2E66E503C20A28A6C71508E8ED5C)
• Download My-T-Soft CE 2.14 for ARM V4T M214AR4T.EXE 11/26/2002 (56k) (MD5: 195C86967F01486CA3DD08238E932063)
• Download My-T-Soft CE 2.14 for MIPS 16 M214MI16.EXE 11/26/2002 (57k) (MD5: 65239BF2B070EF178057786964925F86)
• Download My-T-Soft CE 2.14 for MIPS II M214MIII.EXE 11/26/2002 (71k) (MD5: A1B349B7A49F7EFDBBF98336E7C22FD9)
• Download My-T-Soft CE 2.14 for MIPS IV M214MIIV.EXE 11/26/2002 (80k) (MD5: B56964DEA1576DC98B6ADD85289243B8 )
• Download My-T-Soft CE 2.14 for SH3 M214SH3.EXE 11/26/2002 (56k) (MD5: FD124CA2CBB434585D7040AF8A3ED4C3)
• Download My-T-Soft CE 2.14 for SH4 M214SH4.EXE 11/26/2002 (56k) (MD5: 68B436E40D8E9007DC4045232C43C1BC)
• Download My-T-Soft CE 2.14 for X86 M214X86.EXE 11/26/2002 (46k) (MD5: 6763F6F40976FA0186BCDC0210E64A7B)
• Download My-T-Soft CE 2.14 for X86 WinCE3 M214X863.EXE 11/26/2002 (46k) (MD5: 6010F0577DE08A0583721A2A178E7143)
• Download and Note location on system where downloaded file is saved
• The next release of Build-A-Board will have a flexible way of adding targets. Currently, you will need to "take-over" an existing configuration (MIPS, ARM, SH3, SH4) and use this for your target - the only real difference is the MYTSOFT.EXE executable file - it must be compatible with run-time processor (data / lookup files are compatible across all CE platforms).
• "Windows CE - WCE SH4 - 32 bit" used as an example, folder is Program Files\Build-A-Board\Bin\WCE_SH4
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\WCE_SH4
• Rename the existing MYTSOFT.EXE to MYTSOFT.210
• Copy downloaded from download location into this folder (\Program Files\Build-A-Board\Bin\WCE_SH4)
• Rename downloaded file name (e.g. M214X86.EXE to MYTSOFT.EXE)
• In Build-A-Board, select Target System as "Windows CE - WCE SH4 - 32 bit"
• Download CHARMAP.KMF 11/26/2002 (6k) (MD5: F6FE33891B9835F8B2EB33F6DD0DC516)
• Download CHARMAP.ZIP (Zipped CHARMAP.KMF) 11/26/2002 (1k) (MD5: 082466209E64D9DB520A81F38D657783)
• Download and Note location on system where downloaded file is saved
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\WCE_??? where the correct WCE_ platform is selected
• Copy CHARMAP.KMF from download location into this folder (\Program Files\Build-A-Board\Bin\WCE_???)
• IMPORTANT: If this file is present with MYTSOFT.EXE on the CE device, My-T-Soft will operate in a completely different mode! This should only be used when the OEM has not included support for the physical keyboard.
• By default, all the files in the folder (\Program Files\Build-A-Board\Bin\WCE_???) will be copied into the Synchronized folder. By placing CHARMAP.KMF in the BIN\WCE_??? folder with the 2.14 MYTSOFT.EXE for the correct processor, the file will automatically be transferred to the CE device, and the "mode" of My-T-Soft CE will be changed. Delete the file from the CE device to observe standard operation, and/or remove it from the BIN\WCE_??? folder to disable its affect on My-T-Soft CE.
• After replacing file(s), open your project(s), and rebuild to force re-sync with your CE unit.

2.17 Notes
Please refer to the above regarding the replacement/updating of the MYTSOFT.EXE appropriate for your system. For the following processors, you can download the 2.17 version, which includes the following options:

• Standard - use this unless the other options apply to your situation
• AllowMultipleLayouts - this option (separate build, separate EXEs), will allow you to run multiple processes and show multiple layouts. It is recommended you use duplicate folders, with the only difference being the KEYBOARD.KBF layout file for each layout you need. Customization via Build-A-Board is a requirement to work with layouts like this.
• ForceTopmost - this option (separate build, separate EXEs) forces the topmost setting of the keyboard window. See the README.TXT in the zip for other notes.
• AltToggle - this option (separate build, separate EXEs) adds latching capability to the Alt key for applications in Windows CE that use the Alt key. See the README.TXT in the zip for other notes.

The following processors are supported with the 2.17 versions

• ARMV4
• ARMV4I
• MIPSII
• MIPSIV
• SH3
• SH4
• x86

• Download My-T-Soft CE 2.17 as mtsce_217.zip (700KB) (MD5: 123A1D4BD5554FBB68527B60A7DD0434)
• Download My-T-Soft CE 2.17 (Build-A-Board BIN) as mtsce_bab_217.zip (967KB) (MD5: 73D9333DD009E8517F70B1DB83054935)

Note: If your processor is supported, the 2.17 is preferred to the 2.14 version

Original ID: PU225148

• 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

• Problem: Trying to Pause macro while typing, or need other capabilities
• Resolution: Replace MACROBAT.EXE with 2.16 version
• Download MacroBat.EXE 4/11/2005 (56k) (MD5: 21C066193E5D558A2EC100600DE72BF9) Only for Build-A-Board 2.10 Win32 Targets! (95 thru XP) (Build-A-Board 2.20 has these features - see Usage notes below)
• Download and Note location on system where downloaded file is saved
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\Test
• Rename MACROBAT.EXE to MACROBAT.210
• Copy downloaded MacroBat.EXE into Program Files\Build-A-Board\Bin\Test Folder
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\MSWIN
• Rename MACROBAT.EXE to MACROBAT.210
• Also Copy MACROBAT.EXE into Program Files\Build-A-Board\Bin\MSWIN folder
• After adding file, open your project, and rebuild to update TARGET folders.
• Usage Notes:
• The 2.16 supports the following commands (Bold is macro entry required in Key Action, plain text is description)...
• [Mouse:LCLICK]
• Generates a Mouse Left Click (Left-button down, left-button up) (at the current location of the mouse cursor)
• [Mouse:LDBLCLK]
• Generates a Mouse Left Double Click (Left-button down, left-button up, Left-button down, left-button up) (at the current location of the mouse cursor)
• [Mouse:RCLICK]
• Generates a Mouse Right Click (Right-button down, right-button up) (at the current location of the mouse cursor)
• [Mouse:RDBLCLK]
• Generates a Mouse Right Double Click (Right-button down, right-button up, Right-button down, right-button up) (at the current location of the mouse cursor)
• [Mouse:CHORDCLICK]
• Generates a Mouse Left & Right Click (Left-button down, Right-button down, right-button up, left-button up) (at the current location of the mouse cursor)
• [Mouse:MCLICK]
• Generates a Mouse Middle Click (Middle-button down, middle-button up) (at the current location of the mouse cursor)
• [Mouse:MDBLCLK]
• Generates a Mouse Middle Double Click (Middle-button down, middle-button up, Middle-button down, middle-button up) (at the current location of the mouse cursor)
• [Mouse:LDOWN]
• Generates a Mouse Left Button Down event (Left-button down) (at the current location of the mouse cursor)
• [Mouse:LUP]
• Generates a Mouse Left Button Up event (Left-button up) (at the current location of the mouse cursor)
• [Mouse:MDOWN]
• Generates a Mouse Middle Button Down event (Middle-button down) (at the current location of the mouse cursor)
• [Mouse:MUP]
• Generates a Mouse Middle Button Up event (Middle-button up) (at the current location of the mouse cursor)
• [Mouse:RDOWN]
• Generates a Right Middle Button Down event (Right-button down) (at the current location of the mouse cursor)
• [Mouse:RUP]
• Generates a Right Middle Button Up event (Right-button up) (at the current location of the mouse cursor)
• [Mouse:WDOWN]
• Generates a Wheel Down event (The Wheel Down/Up use one "delta" for each "entry")
• [Mouse:WUP]
• Generates a Wheel Up event (The Wheel Down/Up use one "delta" for each "entry")
• [Mouse:X1DOWN]
• Generates a Mouse XButton1 Down event (XButton1-button down) (at the current location of the mouse cursor)
  (X buttons require Win 2000 or higher)
• [Mouse:X1UP]
• Generates a Mouse XButton1 Up event (XButton1-button up) (at the current location of the mouse cursor)
  (X buttons require Win 2000 or higher)
• [Mouse:X2DOWN]
• Generates a Mouse XButton2 Down event (XButton2-button down) (at the current location of the mouse cursor)
  (X buttons require Win 2000 or higher)
• [Mouse:X2UP]
• Generates a Mouse XButton2 Up event (XButton2-button up) (at the current location of the mouse cursor)
  (X buttons require Win 2000 or higher)
• [Mouse:X1CLICK]
• Generates a Mouse XButton1 Click (XButton1-button down, XButton1-button up) (at the current location of the mouse cursor)
  (X buttons require Win 2000 or higher)
• [Mouse:X2CLICK]
• Generates a Mouse XButton2 Click (XButton2-button down, XButton2-button up) (at the current location of the mouse cursor)
  (X buttons require Win 2000 or higher)
• [Mouse:MOVE=x,y]
• (The move command uses the = (equal sign) character and the , (comma) character to separate the x and y values. Internally, the atoi call is used to covert the text to an integer value. There should be no spaces in this (or any) command. Some examples:
  [Mouse:MOVE=0,0] (top left)
  [Mouse:MOVE=1000,344] (far right, center)
  [Mouse:MOVE=25,760] (e.g. Start menu)
  
• [Sleep:n]
• (n in milliseconds) - calls API Sleep() call
  Examples:
  [Sleep:1000] (sleep 1 second)
  [Sleep:5500] (Sleep 5-1/2 seconds)
  

Original ID: PU225150

• Resolution: Replace MYTSOFT.EXE for these platforms with Downloads Available here
• A compiler issue caused these EXE files to be incorrect for these platforms. The correct versions are available here.
• Download MTSSH3.EXE 8/6/2002 (49k) (MD5: 8C4EFEAD794A028437D7D7E777138964)
• Download and Note location on system where downloaded file is saved
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\WCE_SH3
• Delete the existing MYTSOFT.EXE
• Copy MTSSH3.EXE from download location into this folder (\Program Files\Build-A-Board\Bin\WCE_SH3)
• Rename MTSSH3.EXE to MYTSOFT.EXE
• Download MTSSH4.EXE 8/6/2002 (49k) (MD5: 0C58177BCBBAA6E756A2665A1817CE14)
• Download and Note location on system where downloaded file is saved
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\WCE_SH4
• Delete the existing MYTSOFT.EXE
• Copy MTSSH4.EXE from download location into this folder (\Program Files\Build-A-Board\Bin\WCE_SH4)
• Rename MTSSH4.EXE to MYTSOFT.EXE
• After replacing file, open your project, and rebuild to force re-sync with SH3/SH4 unit.

Original ID: PU225151

• Resolution: Replace MYTSOFT.EXE for this platform with Download Available here
• This processor requires the Handheld PC 2000 updates for CE Version 3.
• Download MTSX863.EXE 2/25/2003 (46k) (MD5: EE935D50766115D833A67435988AAA30)
• Download and Note location on system where downloaded file is saved
• The next release of Build-A-Board will have a flexible way of adding targets. Currently, you will need to "take-over" an existing configuration (MIPS, ARM, SH3, SH4) and use this for your target - the only real difference is the MYTSOFT.EXE executable file - it must be compatible with run-time processor (data / lookup files are compatible across all CE platforms).
• "Windows CE - WCE SH4 - 32 bit" used as an example, folder is Program Files\Build-A-Board\Bin\WCE_SH4
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\WCE_SH4
• Rename the existing MYTSOFT.EXE to MYTSOFT.210
• Copy downloaded from download location into this folder (\Program Files\Build-A-Board\Bin\WCE_SH4)
• Rename downloaded file name (e.g. MTSX863.EXE to MYTSOFT.EXE)
• In Build-A-Board, select Target System as "Windows CE - WCE SH4 - 32 bit"

Original ID: PU225152

• Resolution: Do not Open a Closed Project when an Open project is available - Opening a Closed project will overwrite current files, destroying whatever information may have been there...
• When you see a PROJECT.TXT (Open Project) and PROJECT.ZIP (Closed Project), ALWAYS open the PROJECT.TXT file (this is the current Open project)
• Get into the habit of Closing your projects (File Menu | Close) when you are through working on them - this will preserve disk space, and prevent this problem.
• The next update will add a warning when this situation occurs.

Original ID: PU225153

• Resolution: Review Virtual Key code generation options in Macrobat Notes (%%s???) or wait for a later release.
• We are aware of these issues, and most are documented in the help notes.
• As the first public release, this version met certain customer requirements. This version was released to address those needs.
• Watch for later releases with even more functionality as Build-A-Board begins to realize its potential...

Original ID: PU225154

• Problem: Working with Remote Desktop Connection, Shift-State acts inconsistent, or lowercase/uppercase characters not sent as expected (especially longer sequences of characters). Works fine in Terminal Server Client to the remote machine, or locally.
• Resolution: Replace MACROBAT.EXE with 2.17 version
• Download MacroBat.217 11/1/2006 (56k) (MD5: 09EFB9E1F726D413F20081332BE9840C) Only for Win32 Targets! (95 thru XP)
• Download and Note location on system where downloaded file is saved
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\Test
• Rename MACROBAT.EXE to MACROBAT.210
• Copy downloaded MacroBat.217 into Program Files\Build-A-Board\Bin\Test Folder
• Rename MacroBat.217 to MACROBAT.EXE
• Using Windows Explorer, Open Program Files\Build-A-Board\Bin\MSWIN
• Rename MACROBAT.EXE to MACROBAT.210
• Also Copy MACROBAT.217 into Program Files\Build-A-Board\Bin\MSWIN folder
• Rename MacroBat.217 to MACROBAT.EXE
• After adding file, open your project, and rebuild to update TARGET folders.
• Usage Notes:
• The 2.17 version adds on to the existing update to 2.16 - see MacroBat.exe 2.16 update.
• We recommend you only use this update only if you experience the problem indicated. Otherwise, the 2.16 version is preferred.
• Apparently the rapid generation of virtual keystrokes sometimes could cause a synchronization problem with the Remote Desktop Connection. This update inserts a 1 ms pause (Sleep) during the generation of the keystrokes, and this resolved this synchronization issue. Note that operation may be noticeably slower.
• This update also incorporates a BlockInput API call prior to the generation of virtual keystrokes.

• Verify the Screen resolution - if you have a relatively small board located towards the bottom or right it will not be visible if you move to a smaller screen resolution.
• The layout KBF contains the X and Y location, and it may be positioned off-screen on purpose, especially if the layout is integrated with an existing application using the Developer's Kit Utilities. You can use a Developer's Kit Utility like "MOVEWMTS.exe X:0 Y:0" to position the layout at the top left corner of the current screen.
• Build a Test layout in Build-A-Board and set the Top and Left settings to 0. To run this with MYTSOFT, run "MYTSOFT.EXE TEST.KBF"

My-T-Soft with blank cursor

Use updated MYTSOFT.exe with default cursor as "blank" or "null" cursor - this will display no cursor when mouse pointer is over the keyboard window (My-T-Soft window).

Download MYTSOFT.exe with blank/null cursor as M217W32.ZIP (MD5: 0AD220CFFB98B23687499D515AF8B751) (26KB) (Unzips as MYTSOFT.exe)

For installation notes, and additional capabilities in this update, refer to this item: PU2005120233

Notes: The version is tagged as 2.17, but will work with 2.10 licenses - this is a direct replacement for the MYTSOFT.exe in Build-A-Board 2.10 (or Build-A-Board run-time Win32) - it should not be used for any other purpose. This is essentially similar to the 2.16 update (see link above), except it uses the blank cursor, and has a version of 2.17.

My-T-Soft with forced topmost

Use updated MYTSOFT.exe with a forced topmost action so My-T-Soft window will position above other topmost windows.

Download MYTSOFT.exe with blank/null cursor as M219W32.ZIP (MD5: A987A44B790F5CED834ADDEEC8B86132) (30KB) (Unzips as MYTSOFT.exe)

For installation notes, and additional capabilities in this update, refer to this item: PU2005120233

Notes: The version is tagged as 2.19, but will work with 2.10 licenses - this is a direct replacement for the MYTSOFT.exe in Build-A-Board 2.10 (or Build-A-Board run-time Win32) - it should not be used for any other purpose. This is essentially similar to the 2.16 update (see link above), except it has the forced topmost code, and has a version of 2.19.

By default, the topmost attribute is used when creating the My-T-Soft window, and if My-T-Soft is launched after other topmost windows, will be the topmost window. However, if other windows position themselves as topmost, My-T-Soft may fall behind. This build uses a timer and sets itself as topmost, which will overcome this type of normal action. However, if another window forces itself to be topmost, you may get a flickering type action, as the windows will constantly swap topmost position. Because of the cooperative type of environment in use, this solution may not be ideal for all situations.

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.

Build a single button layout & use the CMD:NKBF, rather than the CMD:MINIMIZE - there is no regular icon available (part of this is that the keyboard window does not have a caption bar, it is not a normal application window). Here is a quick overview of what would be involved:

You will need a new project, e.g. BUTTON. For example, lets say your current project is NUM. Instead of CMD:MINIMIZE, use CMD:NKBF=BUTTON.KBF, then save & build your NUM project. Now create a new project, and call it BUTTON. Create a single button, and set its action to CMD:NKBF=NUM.KBF - label / size / position as desired. Now save & Build BUTTON. From \Program Files\Build-A-Board\Target\BUTTON\MSWIN copy BUTTON.KBF to the \Program Files\Build-A-Board\Target\NUM\MSWIN folder. (In the end, make sure BOTH KBF FILES (NUM.KBF / BUTTON.KBF) are in the same folder as MYTSOFT.EXE. Now when you run the keyboard, and hit "minimize" it will go to the layout as managed in BUTTON. When the single button in BUTTON is pressed, it will reopen the NUM layout.

The key thing to manipulating Build-A-Board is to realize each display presented to the user is just another layout (which can have 1 or (typically) more buttons). By using a single button layout, the "minimize to button" result can be achieved using the built-in "New KBF" command, e.g. CMD:NKBF=???

You can assign a sound to run with the [CMD:SND=???.wav] entry in the key action (uses the Windows API PlaySound internally). If used at the end of the key action, you will still get the keystrokes, along with the wave sound playback.
For example, in Key Action: Test[CMD:SND=click.WAV]
This will type Test & play the CLICK.WAV, (The click can be any wave file, or you could copy the file from our My-T-Soft software - the current version includes a KEYCLICK.WAV file in the Sounds folder in the installation folder - you would have to download & install, get the file, then un-install).
Notes:
There is a 31 character limitation in the action, so naming it to c.wav, will still work, and save 4 characters in the action.
It needs to be the last entry in the key action, as the commands are treated special, and no further interpretation of the action will be performed once a CMD is processed.
The appropriate wave file needs to be in the same folder as MYTSOFT.EXE. In Build-A-Board, the "test" version is \Program Files\Build-A-Board\TARGET\[Your Project Name]\, and for a standard windows target, it is \Program Files\Build-A-Board\TARGET\[Your Project Name]\MSWIN\ - you manually need to copy the wave file(s) into the target folders.

You should refer to the notes & reference material in Build-A-Board Help | My-T-Soft Macrobat

The %%s162 will generate the scan code for the left control and the %%s163 will be the right control. It is possible you will need an extended attribute for the right control, which would be %%e163. Using our tool KEYBOARD\KeyWatch.exe (in the developer's kit - see C:\Program Files\Build-A-Board\SDK) you can watch what the physical keyboard generates & see what the virtual keys generate for comparison. The latching keys (Shift/Ctrl/Alt) can be problematic in that they can need handling & support from the virtual keyboard software MYTSOFT.EXE. For example, the Shift key needs to "latch" the shift state down, e.g. press the shift key & release. Press a letter & release. You will get an unshifted character. On the virtual keyboard, due to the pointing device, nothing "latches" the key (i.e. you can't press 2 keys at once with 1 pointing device). If the keys are discrete & the application software is triggered by Windows virtual key codes, then the existing implementation will work. If software monitors the physical keyboard, or requires latching capabilities, then there may be issues. If so, please let us know & we will try to assist further.

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.

In general, and in most cases, leaving the user in charge of the keyboard focus is recommended. In cases where you have a fixed screen resolution/fixed situation, and want to move and select, using a "fake" mouse click can accomplish this goal. We have modified our mouse click utilities (available in the IMG Developer's Kit) to add some flexibility. You can download MSCLK.EXE here:
Download MSCLK.ZIP (MSCLK.EXE/MSCLK.INI) (17K) (MD5: B0FA955741C130EA2E4A5F13768070D4)
There are various notes in MSCLK.INI (or you can run "MSCLK.EXE HELP").

Here are implementation notes for integrating with Build-A-Board.
You will want to assign an EXEC command function to the appropriately labeled key in Build-A-Board, e.g. [CMD:EXEC=MSCLK.EXE]. If the file MSCLK.INI exists, this will generate the action used by MSCLK.EXE. The files MSCLK.EXE/MSCLK.INI MUST be in the same folder as MYTSOFT.EXE when running. If developing, you will need to place these files in the \Program Files\Build-A-Board\TARGET\[Your Project] and \Program Files\Build-A-Board\TARGET\[Your Project]\MSWIN folders.

Because the full Alt-Tab key sequence releases the Alt state, the Window Manager "resets" the window Z order, and so the next Alt-Tab just switches to the next window in-line, pushing the current topmost window down. This results in each event switching correctly, just not as expected, or desired. You can duplicate this with a physical keyboard by simply releasing the keyboard after a window switch - only the top 2 windows will switch. You should try Shift-Alt-Tab, which will switch to the bottom window, and switch among all the windows. Because of the key action text limit in 2.10, use the "@@[Tab]" macro for Alt-Tab and "[Shift-Down]@@[Tab][Shift-Up]" macro for Shift-Alt-Tab without having to use TYPEFILE.

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