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

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