General Support Information

• Problems typing:
  • 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)

Support Issues for Version 2.10

• Build-A-Board Installation
• Problem: Downloaded File / CD Install Hangs
• Problem: Install completes, but Program Group Shortcuts do not point to valid files
• Resolution: 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)

• Build-A-Board Builder
• Problem: Unable to open projects
• Problem: Unable to build projects (Builder hangs)
• Problem: BABTC.EXE processes do not complete (Task Manager)
• Problem: Build-A-Board Text Compiler Errors (Windows visible indicating compile problems)
• Resolution: Update BABTC.EXE to version 2.11
• This only affects a small number of systems - see technical notes below.
• 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)
• Download Build-A-Board Text Compiler as BABTC211.ZIP 6/4/2003 (17k) (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.

• My-T-Soft Run Time (Win32 - Version 2.10)
• Problem: Caps Lock / Shift state operation problems
• Problem: Stuck keys (dragging off board while button down)
• Problem: Transparency (Requires Windows 2000 or later)
• 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) (unzips as MYTSOFT.EXE)
• Download SeeThru for My-T-Soft 2.16 as STHRU216.ZIP 9/28/2004 (14k) (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.

• Windows CE - Problems typing on CE.NET (CE Version 4), Processor needed is not in Build-A-Board 2.10
• Problem: Character keys do not generate characters in application
• Problem: I need support for a different processor
• Resolution: Update MYTSOFT.EXE to version 2.14 - 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)
• Download My-T-Soft CE 2.14 for ARM V4I M214AR4I.EXE 11/26/2002 (69k)
• Download My-T-Soft CE 2.14 for ARM V4T M214AR4T.EXE 11/26/2002 (56k)
• Download My-T-Soft CE 2.14 for MIPS 16 M214MI16.EXE 11/26/2002 (57k)
• Download My-T-Soft CE 2.14 for MIPS II M214MIII.EXE 11/26/2002 (71k)
• Download My-T-Soft CE 2.14 for MIPS IV M214MIIV.EXE 11/26/2002 (80k)
• Download My-T-Soft CE 2.14 for SH3 M214SH3.EXE 11/26/2002 (56k)
• Download My-T-Soft CE 2.14 for SH4 M214SH4.EXE 11/26/2002 (56k)
• Download My-T-Soft CE 2.14 for X86 M214X86.EXE 11/26/2002 (46k)
• Download My-T-Soft CE 2.14 for X86 WinCE3 M214X863.EXE 11/26/2002 (46k)
• 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)
• Download CHARMAP.ZIP (Zipped CHARMAP.KMF) 11/26/2002 (1k)
• 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.

• Need Keystroke Macro longer than 30 characters
• Problem: 30 character limit is too short for the macro I need
• 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 4/4/2005 (40k) 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
• 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.

• Need Pause or other macro capabilities
• 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) 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.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)
  

• Run-Time Errors on SH3 / SH4 platforms
• Problem: Run Time error (indicated as KEYBOARD.KBF)
• 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)
• 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)
• 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.

• X86 Processor for CE 3 platforms
• Problem: Need X86 Processor Support, Windows CE 3
• 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)
• 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"

• Current Project replaced by Older Project
• Problem: You lost current changes
• 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.

• International Character problems
• Problem: Not all characters in Build-A-Macro portion operate (or generates an incorrect keystroke)
• 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...

• Return to Build-A-Board Product Information
• Return to Technical Support