By default, the My-T-Soft software reacts to dialogs, message boxes, and other windows by repositioning in order to ensure the dialog, etc. is visible. Depending on screen-resolution, dialog window size, My-T-Soft size & configuration, this may or may not meet everyone's needs. You should note the following:
In My-T-Soft Setup (Start Menu | All Programs | My-T-Soft | My-T-Soft Setup -or- Menu button (middle of tool bar) | My-T-Soft Setup), go into Configuration | Operation Options. The top setting "React to dialogs & other windows..." should be cleared. Click OK, OK, Exit
Additionally, the default screen position of My-T-Soft should meet your requirements. You can do the following:
Size & configure the panels in My-T-Soft as desired. Move the keyboard layout to the screen position you want it to open. From the Menu button (middle of toolbar), select Settings | Save Current Settings, then Position | Save Position. Now Close My-T-Soft, and re-launch - it should open in the same position. If it does not, then there may be issues with user permissions / read-only settings on files, etc (you can refer to help for more details), but in general, this is all that is required.
Original ID: IB253121

Depending on the version of Windows & the actual screen saver, the following applies:
In NT/2000/XP, the screen saver is an actual different desktop, so if it is a proper/standard screen saver in these versions of Windows, My-T-Soft won't be visible at all - UNLESS it is a custom screen saver, that runs in the context of the default user desktop. In that case, and the Win95/98/Me case, the screen saver is just a full screen program that is running. Since My-T-Soft needs to be on top to be useful, it can appear over a non-standard "screen saver" There are pre-programmed classes (e.g. WindowsScreenSaverClass) for the standard screen savers that ship with Windows, so My-T-Soft knows to stay behind these, but again, if it is custom or not the Microsoft ones, My-T-Soft may not see it as a screen saver, and stay "on-top". This gets pretty advanced & intense, but it is all documented in the Help & controllable via the MYTSOFT.INI file - for example, if you look in the INI file for WindowsScreenSaverClass, you can see how it is configured & setup - there is a listing in the Classes section, then an entry with an Action= setting. See My-T-Soft Help | My-T-Soft User's Guide | Section IV - Other Information | Advanced User Notes. There is also ClassWatch/WindowWatch settings in the INI to "look" at what class of window is running.
Original ID: IB253139

OnScreen defaults to basic mode, which limits the options (mainly for users who use it for primary text input). Go into OnScreen Setup | User Options, and turn on Advanced mode (e.g. Start Menu | Programs | OnScreen | OnScreen Setup). This enables the control panel, and access to all eleven panels.
Original ID: IB253112

In Windows 95/98/Me/NT, you may need to turn on "Track pointing device input all times" - see OnScreen Setup | Configuration | Operation Options - towards the bottom. In 95/98/Me/NT, for certain touchscreen drivers, this needs to be On to operate cleanly. Certain touchscreen drivers do not emulate the mouse correctly - this setting in OnScreen compensates for these problems.
Original ID: IB253311

Refer to Joystick-To-Mouse Help, and read the troubleshooting area about "Drift" This is a fairly common issue, and often "Center Range sensitivity" or settings on the joystick device itself can resolve the problem. Any calibration can be done via the Windows control panel - this may also require a joystick button press, but may be able to be walked through with mouse clicks.
Original ID: IB253211

In My-T-Pen, there are two common issues that may be related to this.
1) The save position only saves the top/left opening position, not the current layout. In general, we recommend the user save settings (which preserves size/layout configuration), and then save position. (This is original My-T-Pen)
2) Sometimes on XP/2000 the user only has read-permissions, and can't actually save to the file. Either an administrator has to do the update, or the user must be given proper permissions. This relates to My-T-Pen and custom layouts.
If this, on the other hand, is related to the custom layout built by Build-A-Board, then there are other options. In Build-A-Board itself, as part of the layout, the opening screen position can be set.
In all cases, the KEYBOARD.KBF determines the layout / screen position. If something is preventing (i.e. permissions) this file from being updated, then this needs to be resolved.
Original ID: IB253144

Most BIOS's have options to bypass, or ignore this error, but sometimes the wording is not necessarily obvious. Things like "Halt on All errors, but keyboard" may make sense, but others can be misleading. Also issues with USB & legacy support can affect this error. If you can't identify it, you may want to contact the system manufacturer, or BIOS manufacturer for support. Again, this has nothing to do with IMG software. Finally, we are aware of physical devices that can emulate a physical keyboard attached to a system. Things like KVM switches do this, and there are simple "plugs" that can also act as though a keyboard were attached.
Original ID: IB253105

Microsoft Windows Vista is a completely new and different operating system from Microsoft released in 2007 (available towards the end of 2006). In general, any IMG software released prior to 2006 was not written for Vista, meaning it technically is not compatible with this new operating system. However, there are compatibility workarounds available, as Microsoft has built in a mechanism to allow older software to run. Due to the nature of IMG software, the level of compatibility is based on Microsoft's ability to interface this compatibility mode to the new Windows Vista. In theory, every feature and capability of the IMG's software will operate correctly. In actuality, this may not be what you experience when running in this compatibililty mode. The ultimate comparison would be to operate the feature or capability in the older operating system, then compare with the appropriate compatibility selection in Windows Vista.

To enable this operation (e.g. to enable IMG's software to run in Vista), it must be first installed. If you receive a Windows Version warning or error, Vista may open a dialog suggesting a "Recommended Settings" - you may accept the recommendation (this essentially provides the compatibility mode for the setup program). Once installed, you will want to enable the compatibility mode for ALL the executable programs associated with the product. To do so, you will want to open Windows Explorer (or Start Menu | Computer) and browse to the installation folder, then sort by Type, select all Applications (e.g. .EXE or Executable programs), and open properties. To get to the properties, you may open the Organize menu, the select Properties, or open the context menu (right-click), and select Properties. In the Properties dialog, you can select the Compatibility Tab, then in the Compatibility Mode section, Enable the "Run this program in compatibility mode for:", and in the drop down select "Windows XP Service Pack 2"

Theoretically, the program will now operate as it would in Windows XP. If it does not, you may wish to do the following:

• Upgrade to the IMG "Windows Vista" version of the product (if available)
• Check Microsoft for Windows updates and any updates related to compatibility
• Verify the operation works correctly in Windows XP (if available) - if the operation works in XP, but not in Vista, then you can report this to Microsoft
• E-mail IMG tech support with information on what you experiencing - there may be work-arounds or other options we can suggest
• Note that if the operation works in Windows XP, but not in the compatibility mode of Vista, this is a Microsoft issue, not an IMG software issue.

Because of the maturity of the Windows operating system, and the anticipated slow "roll-out" of Windows Vista, IMG will be responding to customer demands for Windows Vista compatibility based on various factors. Always check the product pages and IMG's website for the most up-to-date information regarding available Windows Vista releases. Feel free to contact us directly with requests or concerns or details on your specific situation.

For further information on a specific product, click on the link(s) below:

• Build-A-Board 2.10 (Build-A-Board Keyboard Designer tool (Builder))
• Joystick To Mouse 2.60
• My-T-Pen 1.77
• My-T-Touch 1.77
• My-T-Soft 1.77
• My-T-Soft 2.10 (Build-A-Board run-time software)
• OnScreen 1.75
• The Magnifier 1.20
• TouchRight Utilities 1.20
• SmartClick 1.50

The largest issue has been familiarity with the product. Download a demo to test, and review on-line help and documentation.

The Automatic return to Left-Click (Single Right-Click Only option) uses System Level hooks. Any conflict with other software may require disabling this option from the TouchRight Menu.

In 95/98/Me/NT, there can be a conflict with IMG's My-T-Pen, My-T-Touch, My-T-Soft, OnScreen if the "Track Pointing Device at all times" is OFF, and the Automatic return to Left-Click (Single Right-Click Only option) in TouchRight is ON. Either turn this option off in the TouchRight Utilities, or set the "Track pointing device..." ON in Configuration | Operation Options.

Original ID: IC101366

• Unfamiliarity with the product options - Read the on-line help for configuration options, etc. You may wish to Print the documentation from the available PDFs, or purchase the user's guide.
• Track Cursor - if this option is turned on, you will find you cannot move the cursor over the Magnifier Window! In order to turn this option off, you must click on the small Magnifier icon in the tray (on task bar, near clock), or hold the mouse cursor in the extreme bottom-right of the screen for several seconds.
• Default Opening Options - Constantly changing settings and closing The Magnifier during run-time may lead to undesired settings when launched. Use Alt-Z to toggle full screen / windowed operation. Use Alt-D to return to defaults (in windowed mode). Use a second running Magnifier for different uses to eliminate this problem (up to 7 Magnifiers may be run at the same time).

Original ID: IC401308

SmartClick has been developed and tested for over 3 years prioir to release, using guidance from RJ Cooper for features and capabilities, and utilizing stable, field-proven technology from IMG. Any known issues are listed in the Help provided with SmartClick.
Original ID: IC202328

SmartClick is a windows compatible software program that uses the Microsoft Windows API, and conforms to all guidelines published by Microsoft. By definition, if SmartClick works with any windows application, it will work with all (properly written) windows applications. IMG can not provide compatibility with programs written in a way that do not conform to the Microsoft Windows operating system.

IMG does not have a list, nor do we exhaustively test any of the thousands of programs released every year - In order to keep our prices reasonable, we can not purchase, pay personnel to test, and provide changes to our software to work with companies that choose to ignore the published documentation regarding software interoperation. We apologize for any inconvenience, but we strongly recommend you download a demo and test the software before purchasing.

Original ID: IC202329

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

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

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

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

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

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

Original ID: IG223700

Click to open Build-A-Board 2.10 Support information

• A Valid License requires a Certificate of Authenticity or a blanket manufacturer (OEM) license - if you don't have a Certificate of Authenticity, you don't have a valid license UNLESS it is licensed through a manufacturer - if you believe you paid for a license, and don't have a Certificate of Authenticity, please contact the listed company in the Contact Information provided in the IMG License Manager - see the "Licensing Information" Icon in the Program Group. (NOTE: For certain licenses, IMG may not be able to assist you directly).
• What does a Certificate of Authenticity look like?
• To verify the license, run the "Licensing Information" Icon in the Program Group - it will say "This is a Licensed and registered Version..." if properly licensed. If you are asked to enter License Key & Serial # information, then the product is not properly licensed. Refer to the Contact Information for manufacturer contact information.
• If the software was provided on a system, but is not licensed, you should contact the vendor / manufacturer for further information. Some bundle (provide license with equipment), some offer (can license on request), and others simply include a demo version. Please note that just because you find IMG software does not necessarily mean that it is licensed for your use.

Original ID: IL800270

• A major system change, or moving to a different system requires a license transfer.
• Three items are required:
• 1. Serial # (from original Certificate of Authenticity)
• 2. License Key (from original Certificate of Authenticity)
• 3. System ID (from IMG License Manager on New System)
• Important Notes:
• If you have transferred the license before, you MUST use the most recent serial # / license key pair! Once a license has been transferred, the serial #/license key used to transfer will no longer be allowed for future transfers. Be sure to safely record your most recent license information.
• A hard disk re-format, or Operating System Upgrade / Re-install will generally cause the System ID to change. After these changes, re-install the IMG software and refer to the IMG License Manager to obtain the New System's System ID
• The software must be installed from the original media / original download
• To obtain the New System's System ID, run the IMG License Manager ("Licensing Information" icon)
• The software MUST be the same product / same version as the original license.
• Click here to Transfer a License. Be sure to have the 3 items indicated above.
• If you have copied (or restored from backup), it may be helpful to "reset" the license. For versions prior to 1.78, you can delete the license file (LICENSE.LIC) (use Windows Explorer, go into the Installation Directory, find the file LICENSE.LIC, then delete it), then run the License Manager twice, e.g. Start Menu | Programs | [Product] | Licensing Information - click Register later the first time (which will create an empty LICENSE.LIC file), then obtain the System ID the SECOND time you run the License Manager, and use this to perform the transfer. In the 1.78, there is an option to delete the LICENSE.LIC file from the Web License portion (within the License Manager).
• Other Notes:
• The License Manager updates the file LICENSE.LIC in the installation folder. In general, you want to be an Administrator (or privileged user) that can write to this file. Additionally, this file cannot be Read-Only (which can happen if it is copied or moved from a CD).
• There have been issues where the LICENSE.LIC file is corrupt, or if edited manually, it is saved as Unicode (it must be ANSI / single byte characters). The options are to do a re-install, or delete the file & recreate it by running the License Manager (you must run the License Manager twice for software released prior to 2007).

Original ID: IL800271

Please check the following:

• Certificate of Authenticity's must be used with the CD they were delivered with - if you are trying to license a downloaded version, or a different version number, the license will not be accepted. Contact IMG Customer Service to help resolve the situation.
• Certificate of Authenticity's must be used with the CD they were delivered with - if you have multiple CD's, you may need to match the Certificate's with the CD - contact IMG Customer Service to help resolve the situation.
• For version tracking, IMG does include a date with many licenses - if the date embedded in the license file has passed, the licensing step will fail. This is not a major limitation, since the system date can be set back to a date that is valid, the software can be licensed, and the date can be reset to the current date. Once licensed, the license will be valid as long as the hard drive is not reformatted, or Windows is not re-installed. To see if this is the case, you can open the LICENSE.LIC in a text editor (e.g. Notepad) - the FEATURE INSTALL line will have a date (e.g. 16-Jan-2005). If this date has passed, then you will want to set your system date to a date prior to this date, install/license the software, then reset your date to the current date.

Original ID: IL800272

Here are some items that have occurred that may help you resolve this issue...

• The license is actually valid, but the license manager was already running unbeknownst to you. Restart your system & run Licensing Information directly (without running the product).
• You did not copy the entire license information correctly. Between the ( =====…=====) lines actually means all the information between the 2 lines, including carriage returns (i.e. blank lines) If you end the license file prematurely by not including any trailing carriage returns (i.e. the trailing blank lines), the verification will fail.
• You saved the file directly to the LICENSE.LIC file, but it is in Unicode format (rather than ANSI). From Notepad, try a File | Save As… and verify the encoding is ANSI.
• The product and or version is not an exact match. It must be to license.

The license manager uses the System ID to track the unlock codes. The System ID on the Certificate must match the System ID shown in the license manager on the system you are trying to license. If it matches, please try the following:
1) Using Windows explorer, go into \WINDOWS\MYTTOUCH (or \WINNT\MYTTOUCH), and find the file LICENSE.LIC. Delete this file. 2) Run LICENSE.EXE (or Start Menu | Programs | My-T-Touch | Licensing information) - click Register later to close the license manager. Then Re-Run the license manager, and verify the System ID against the licensed System ID on the Certificate.
3) If correct, reboot your system - do not run My-T-Touch, and go directly back into the license manager - Enter the codes in the fields (you must enter some text in the customer field), and save.
If the System ID does not match, you can transfer the license via our website. You will need the new System ID, and the Serial # and License Key from the Certificate.
Original ID: IL253101

http://www.build-a-board.com/general/license.htm
You can also get to this by clicking on build-a-board.com / General button (at top), Company Policies, then on the IMG Standard License Agreement.
Original ID: IL253726

Keyword search supports single or multiple word searches. Quotes are supported for single or multiple keyword searches. If you are searching for a single keyword such as install it will return all entries containing the word install and most variations such as installed, installing, and installation. If quotes are used then the same results will appear since the word install in located in the words installed, installing, and installation. Using quotes versus not using them differs mainly when searching for multiple words. Searching for Joystick-To-Mouse drift using quotes will return all entries with the exact phrase "Joystick-To-Mouse drift" where not using quotes will return all entries containing Joystick-to-mouse drift and any entries containing single words within that phrase such asjoystick, mouse, drift and most variations such as drifts or joysticks. When not using quotes special characters will be removed. For example when searching for Build-A-Board the dashes are removed and all entries containing Build A Board and individual words such as Build and Board along with similar sounding words such as built will be displayed.
Original ID: IU100000

1. If you are automatically prompted to run setup.exe, then go ahead and select run. Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
   • Once the program starts, select “Install Software”
   • Select all the default options to install the software.

***if the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• go to the compatibility tab
• select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on “licensing info”
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok


• Do the same compatibility procedure for the remaining files in the My-T-Soft folder When asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

If OnScreen is running as a demo, after 1 hour or 250 keystrokes, it will stop operating and only type "demo". To verify your license, please go to Start Menu | Programs | OnScreen | Licensing Information. In general, once licensed to a system, nothing will affect the license unless you re-install windows or reformat the hard drive. If it reports as a demo, you can transfer a license on our website at http://www.imgpresents.com, Support | License | Transfer a license - you will need the Serial # / License Key from your Certificate of Authenticity, and the System ID reported by the IMG License Manager.
Original ID: IU253114

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on “licensing info”
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Do the same compatibility procedure for the remaining files in the OnScreen folder
• When asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on “licensing info”
• Go to properties
• Go to the compatibility tab
• Elect the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Do the same compatibility procedure for the remaining files in the My-T-Touch folder
• When asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with the program icons, right click on the Joystick-To-Mouse icon
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok


• If asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

For an on-screen keyboard to work, it can't fall behind other windows, so the design of the software prevents operation as other windows in the system. Here are a few options:
1) You can set a right or middle button to "hide" the keyboard (See My-T-Pen Setup | Mouse buttons | Button Actions | Look Through My-T-Pen
2) You can minimize the window prior to the screen shot (My-T-Pen Setup | Configuration (Minimize options)) If you are using My-T-Pen to "trigger" the screen shot.
3) You can set the right-button to be a key combo (e.g. Ctrl-PgUp), and then reconfigure your screen capture program to use this combo - if you minimize My-T-Pen to a button, you can right-click on the button to trigger the screen capture (note: you will still capture the image of the button)
4) You can review the Developer's Kit utilities - you could create a batch/script that moves My-T-Pen off screen, use the SendStringMacro (SDSTRMTS) utility to send the keystrokes, then move back on screen. This can get involved & require familiarity with the DevKit & time to test & verify.
Original ID: IU253404

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on “licensing info”
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Do the same compatibility procedure for the remaining files in the My-T-Pen folder
• When asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on “licensing info”
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Repeat the same compatibility procedure for the TouchRight Utilities icon
• If asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

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

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

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.

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on The Magnifier icon
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok


• If asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

You don't specify which version of Windows. There are some differences in appearance available between Vista and 2000/XP. You can use Alt-C to toggle the display of the cursor in the magnified window. You can refer to the cursor options here

Also, if you go into Control Panel | Mouse properties, and look at the Pointers tab, there are various schemes available - several are larger. Finally, the Cursor Lines options in The Magnifier can be enabled which help locate the mouse.

There are some limitations on what is possible due to the approach used by The Magnifier software, but hopefully one of the above options will address your requirements.

In Windows Vista, The Magnifier's capabilities rely on the video driver itself (and settings in Windows). I believe what you are describing is the screen smoothing Windows uses on LCD type monitors (ClearType). To change this setting in Windows (not a setting in The Magnifier), you can do the following: Right-Click on the Desktop | Select Personalize | Click on Window Color and Appearance | At bottom, click on "Open classic appearance properties for more color options" | Click on Effects button | Clear the checkbox "Use the following method to smooth edges of screen fonts" - you may also select Standard, or ClearType, to view the differences on your display. I believe if you clear this option, the text will be sharp and clear when magnified. Depending on how large your magnification setting is, the other settings may be acceptable. You should reload applications after changing this setting.

This is a function of the video display update. (NOTE: It is possible that this is enabled in the Mouse properties Control Panel applet, but then you would see mouse trails always)) One option is to use Alt-C to disable the magnified cursor displayed in The Magnifier window, but I don't think that will affect what you are describing. Another option may be to reduce the magnification, or use the windowed mode (not full screen). You can go into Windows Control Panel | Display Properties | Settings and try different resolutions or color depths (e.g. 16-bit color vs. 24-bit color, etc.) and you may find a setting that minimizes this result. Alternatively, you can buy a more powerful video adapter with more memory that can make video updates invisible to the human eye. On older systems, or systems with stock video cards, the video display may not be able to perform at a satisfactory level, especially when operating a video-intensive application like The Magnifier. As a software program, we have no real control over the physical hardware you have - it can only perform as well as the operating system and hardware allow it to. If you see the mouse cursor leaving cursor images arbitrarily (or just not leaving a clean display), then you are seeing video artifacts, which means your video is not updating at a speed that matches the performance of higher-end video adapters, which may be required to provide a more enjoyable result while using The Magnifier.

On different versions of Windows, and different applications, the default settings of The Magnifier may result in a conflict between the magnification following the mouse cursor, and the magnification following the text caret. By default, The Magnifier has keyboard input tracking On, specifically "Track Text Caret", and "Track Dialogs & Keyboard" in the Advanced Menu - see here for additional details.

What can happen is that the software you are running is creating an event that acts like you are typing (even though you probably aren't), and The Magnifier focuses on the position of the text caret (some field or text entry area). Since you aren't really typing, these actions can be annoying or frustrating. Also, this may only happen occasionally, or only in certain applications, or at certain screens.

The solution is to disable one or both of these settings in The Magnifier, so this automatic tracking doesn't affect the screen location that is being magnified. Simply go into the Menu, then Advanced Menu, and select "Track Text Caret" to disable it. If you still have difficulty, disable the "Track Dialogs & Keyboard" option.

On most newer applications, these events are better managed, so some users may never experience this type of problem. Also, it may only occur sporadically, due to different situations in an application or program. Note that it may be possible to click on some other area or section of the application you are using, so the keyboard focus is not on a control that has a text caret. Finally, if you use The Magnifier more for reading, rather than typing, you may wish to keep these settings off.

1. If you are automatically prompted to run setup.exe, then go ahead and select run.
   Otherwise go into windows explorer and find setup.exe from the cd and run it.
2. Windows will ask you if you want to allow the file. Select Allow.
• Once the program starts, select “Install Software”
• Select all the default options to install the software.

***If the install fails, then open the cd folder from windows explorer.***

• Right click on the setup.exe file and select properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” in the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Now execute the setup file, “setup.exe” and continue from step #2.
3. Once the window opens up with a list of icons, right click on “licensing info”
• Go to properties
• Go to the compatibility tab
• Select the check box that says “run this program in compatibility mode for:” In the drop-down menu select “Windows XP (Service Pack 2)”
• Then say ok
• Do the same compatibility procedure for the remaining files in the SmartClick folder
• When asked if you want to allow this program to run, select Allow.

For more information about Windows Vista Click Here.

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

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

• The entire file must be downloaded & saved onto your hard disk (or network) prior to running the file.
• Note the location you are saving the file when prompted by your browser - you will need to use Windows Explorer, or specify this location to run the file after the download is complete.
• When the downloaded "EXE" file is executed it does the following (issues included in bold)
• The program checks the System Environment for a TEMP= setting (Environment Variable TEMP)
• If the TEMP setting exists, and there is at least 2MB free space, the first extraction expands into this location.
• If the TEMP setting does not exist, the software attempts to make an IMGLOAD folder in the Windows directory (e.g. C:\WINDOWS or C:\WINNT) Permissions or security issues can prevent this step from occurring - you may need an Administrator do extract the downloaded file!
• The first extraction step creates a self-extracting ZIP file and a PIF file
• The second extraction is performed by executing the PIF file, and all files are extracted (these extracted files correspond to the MSWIN folder on an CD distribution) Permissions or security issues can create issues, along with Read-Only attributes or files in use - For example, having a SETUP.EXE file in the TEMP folder copied from a CD may leave a SETUP.EXE file in the TEMP folder with a Read-Only attribute - when the extraction tries to write the IMG SETUP.EXE, it will fail. When the next phase occurs (i.e. running SETUP.EXE), the existing SETUP.EXE will be executed, and will leave the user dazed & confused, since they will see something quite unexpected. If something unexpected occurs at this point, remove all files from your TEMP folder, then start over.
• After all files are extracted, SETUP.EXE is executed, and the default Setup begins (see Installation Support for any problems at this point).
• After the Setup program has completed its task, cleanup begins - all extracted files are deleted, and the system is restored to its original state. Note that the original downloaded file is left intact - you can either manually delete it, or store it in a Downloads file for future use.

Original ID: IW400319

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

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

Original ID: IW400320

There is a missing line of code in the save code in this dialog, and operation can be inconsistent - this only affects the character size adjust setting. Use the INI file (My-T-Soft Setup | Configuration | Special Options | Edit Initialization file) to change setting Keyboard1SizeCharAdjBase, Keyboard1SizeCharAdjMedium, Keyboard1SizeCharAdjLarge. This will be resolved in all future versions.
Original ID: PI225187

There is a missing line of code in the save code in this dialog, and operation can be inconsistent - this only affects the character size adjust setting. Use the INI file (My-T-Touch Setup | Configuration | Special Options | Edit Initialization file) to change setting Keyboard1SizeCharAdjBase, Keyboard1SizeCharAdjMedium, Keyboard1SizeCharAdjLarge. This will be resolved in all future versions.
Original ID: PB560216

There is a missing line of code in the save code in this dialog, and operation can be inconsistent - this only affects the character size adjust setting. Use the INI file (My-T-Pen Setup | Configuration | Special Options | Edit Initialization file) to change setting Keyboard1SizeCharAdjBase, Keyboard1SizeCharAdjMedium, Keyboard1SizeCharAdjLarge. This will be resolved in all future versions.
Original ID: PB225184

All configuration options are in Build-A-Board. Once built, the operator cannot do no more than you allow - there is a right-click menu to minimize/save position, but this can be disabled in the properties of the board in the Build-A-Board builder. If you want to access different boards, look at the New Keyboard File command (CMD:NKBF) for more details - the operator can select different sizes/layouts/configurations, etc. with this approach.
Original ID: PB259178

My-T-Mouse 1.52 is a 16-bit application, and only supports Windows 3.x, 95/98/Me. Please refer to the newer releases in the My-T-Soft family, including My-T-Soft/My-T-Pen/My-T-Touch, and the Assistive Technology version, "OnScreen"

For all practical purposes, no support is necessary with this software - it does everything it is supposed to on the supported versions of Windows

Version 1.52 released May 2, 1999.

• Maintenance release, match to commercial products.

Version 1.50 released September 1, 1998.

• Full Compatibility with Windows 98

Version 1.45 released September 15, 1997.

• Popup menus (especially on desktop with no active window) can cause operational delays / inconsistencies or lock-out in Windows 95 OSR2 B and Windows 98 - depends entirely on usage. Cause by underlying changes to operating environment by Microsoft - addressed in 1.50 release.
  Original ID: PC101364

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

Original ID: PC223713

• Verify you have the most up-to-date and correct pen driver for your system
• Try My-T-Soft Setup | Configuration | Operation Options "Virtual Pointer in use" set "On" (Checked) - if pointing device driver does not support Windows API GetAsyncKeyState for Mouse buttons, then this option will need to be on for moving My-T-Soft (This is currently the default in 1.70)

Original ID: PC223714

• Batch / Script used to run My-T-Soft with another Application: Use the START command prepended to the .EXE so Windows knows to start it as a GUI App (Windowed App)
• Example - Instead of this:
• C:\WINNT\MYTSOFT\MYTSOFT.EXE
• C:\MYAPPT\MYAPP.EXE
• Do This:
• START C:\WINNT\MYTSOFT\MYTSOFT.EXE
• START C:\MYAPPT\MYAPP.EXE
• Running Special Batches / configurations from a My-T-Soft Macro "Launch Application"
• The Launch Application sequence uses the barebones "WinExec" API call - to run a .LNK, or a .DOC (i.e. get "ShellExecute" functionality) you can use CMD /C or START prepended to the file name (Use CMD /C for BAT/CMD files).
• Example: [Application Field in Build-A-Macro] CMD /C "C:\Documents and Settings\All Users\RunMyApp.lnk"

Original ID: PC223715

• Full keystroke support via the virtual keyboard is not available for various pop-up menus in various versions of Windows - Microsoft has numerous "flavors" of menus, and since it is easier, more efficient, and better understood to use the pointing device to access menus, we have not devoted resources to address any of these issues.

Original ID: PU223716

• User rights: the user must have rights to the MYTSOFT installation directory and rights for the file LICENSE.EXE. This file is required during Logon to verify a valid license - if it is not available, eventually the logon will turn itself off assuming it is in demo mode. To prevent this, verify all users have rights/permissions to the LICENSE.EXE file in the install directory.
• Other Network Logons / Novell logon: If properly setup, the user name and password should be the same for all services / networks / resources required. If the WinLogon process cannot establish the appropriate logon using the Workstation logon user name and password, it will open a dialog to establish the logon to the other resource(s). To prevent this, verify that all resources use the same user name and password.
• Network Logon - works best in as clean a system as possible. Working with virus scans, secure desktops, or other non-standard windows software have been reported as causing lock-ups, or lack of proper operation.
• There can be a problem if the user logging on has limited rights.

Original ID: PC223717

There is a conflict with some program or service running. Use MSCONFIG.EXE (e.g. Start | Run | MSCONFIG.EXE). Selecting Selective Startup, you can disable "Load System Services" and/or "Load Startup Items" to try and determine if it is a service or startup program causing the conflict. In the Services and Startup tabs, you can individually add or remove specific items . We have heard about issues with anti-virus programs. For example, "Symantec AntiVirus client service" and "DefWatch", when disabled in the Services tab, has resolved this problem. Also a user running Ad Aware reported: "Apparently everything was fine until the fourth version. It wasn't the program itself. It was when I turned on Ad Watch that I had the problem." From our experience, conflicts of these types can be problematic, and difficult to identify the exact cause. In the case of an anti-virus program, it may be settings issues, or white lists & black lists. Because an on-screen keyboard works at a low level to generate keystrokes that are seen by other applications, an overreaching security solution may prevent it from operating. You may wish to check for anti-virus program updates, or try default (or different) settings within the anti-virus program to prevent this type of conflict, or try a different anti-virus solution. We always recommend running as clean a system as possible. Unfortunately, resolving these conflicts is time consuming, and when multiple third-parties are involved, it goes beyond the normal level of technical support available. Essentially if the software runs in safe-mode, but not in your normal environment, then there is some driver or other software running that is causing this problem. Since we don't have access to your environment, we can't effectively help beyond suggesting the above methods provided by the operating system.

• Verify you have the most up-to-date and correct pointing device (touch, pen, mouse, etc.) driver for your system
• Try OnScreen Setup | Appearance | Operation Options "Virtual Pointer in use" set "On" (Checked) - if pointing device driver does not support Windows API GetAsyncKeyState for Mouse buttons, then this option will need to be on for moving OnScreen (This is the default in 1.70)

Original ID: PC223771

• Verify you have the most up-to-date and correct pointing device (touch, pen, mouse, etc.) driver for your system
• Application Focus / input focus / typing into the desired window - most issues are caused by multiple windows - verify the desired window is selected and has the keyboard input focus. Also check the OnScreen Setup | User Options | Operation Options & Help for more options in working with various input devices.
• Network Logon - works best in as clean a system as possible. Working with virus scans, secure desktops, or other non-standard windows software have been reported as causing lock-ups, or lack of proper operation.
• ELO TouchSystems (95/98/Me/NT) - "Track Pointing Device Input at All Times" MUST be checked on to operate with ELO drivers - see OnScreen Setup | User Options | Operation Options & read Help for more details
• eTurboWare Touchscreen drivers - "Track Pointing Device Input at All Times" MUST be checked on AND the "Button" Mode must be selected for their driver (NOT Desktop Mode) - see My-T-Pen Setup | Configuration | Operation Options & read Help for more details
• MicroTouch TouchWare Monitor - NT/2000. We have received a report that there is inconsistent operation of our software when opened from a minimized icon on taskbar in Windows 2000 when the TouchWare monitor has been removed from the StartUp Group. Check MicroTouch for the latest release.

Original ID: PC223770

Full keystroke support via the virtual keyboard is not available for various pop-up menus in various versions of Windows - Microsoft has numerous "flavors" of menus, and since it is easier, more efficient, and better understood to use the pointing device to access menus, we have not devoted resources to address any of these issues.
Original ID: PC223772

• User rights: the user must have rights to the ONSCREEN installation directory and rights for the file LICENSE.EXE. This file is required during Logon to verify a valid license - if it is not available, eventually the logon will turn itself off assuming it is in demo mode. To prevent this, verify all users have rights/permissions to the LICENSE.EXE file in the install directory.
• Other Network Logons / Novell logon: If properly setup, the user name and password should be the same for all services / networks / resources required. If the WinLogon process cannot establish the appropriate logon using the Workstation logon user name and password, it will open a dialog to establish the logon to the other resource(s). To prevent this, verify that all resources use the same user name and password.
• There can be a problem if the user logging on has very limited rights.

Original ID: PC223773

There is a conflict with some program or service running. Use MSCONFIG.EXE (e.g. Start | Run | MSCONFIG.EXE). Selecting Selective Startup, you can disable "Load System Services" and/or "Load Startup Items" to try and determine if it is a service or startup program causing the conflict. In the Services and Startup tabs, you can individually add or remove specific items . We have heard about issues with anti-virus programs. For example, "Symantec AntiVirus client service" and "DefWatch", when disabled in the Services tab, has resolved this problem. Also a user running Ad Aware reported: "Apparently everything was fine until the fourth version. It wasn't the program itself. It was when I turned on Ad Watch that I had the problem." From our experience, conflicts of these types can be problematic, and difficult to identify the exact cause. In the case of an anti-virus program, it may be settings issues, or white lists & black lists. Because an on-screen keyboard works at a low level to generate keystrokes that are seen by other applications, an overreaching security solution may prevent it from operating. You may wish to check for anti-virus program updates, or try default (or different) settings within the anti-virus program to prevent this type of conflict, or try a different anti-virus solution. We always recommend running as clean a system as possible. Unfortunately, resolving these conflicts is time consuming, and when multiple third-parties are involved, it goes beyond the normal level of technical support available. Essentially if the software runs in safe-mode, but not in your normal environment, then there is some driver or other software running that is causing this problem. Since we don't have access to your environment, we can't effectively help beyond suggesting the above methods provided by the operating system.

All IMG Logon Module support issues are handled in IMG Logon Technical Support
Original ID: PC203357

Use updated IMGLM.EXE

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

Original ID: PC203358

Apply MTSTSFIX.EXE

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

Original ID: PC203359

Use updated IMGLM.EXE

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

Original ID: PC203360

Use updated IMGLM.EXE

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

Original ID: PC203361

Use updated IMGLM.EXE

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

Original ID: PC203362

Use updated IMGLM.EXE

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

Original ID: PC203363

• This product is no longer supported or sold, and is considered obsolete
• For link to product description / download, click here
• Version kept backwardly compatible to Windows 3.1 for support of schools, etc.
• Will operate in Windows 95 / 98 / Me - see My-T-Mouse, or the Assistive Technology version OnScreen if My-T-Mouse for Kids does not meet your needs or you are on a newer version of Windows.

Original ID: PC101365

Use updated version of DLL (originally for Windows Server 2003)

• DIRECTIONS:
• 1) Go into the Logon Utilities | Setup/Configure Logon Utilities and Disable Logon Utilities
• 2) You will need to reboot the system (this will revert to default MSGINA.DLL) - you may need a physical keyboard to logon!
• 3) Using Windows Explorer, find the installation folder, e.g. \WINDOWS\MYTSOFT (or \WINDOWS\MYTPEN, \WINDOWS\MYTTOUCH)
• 4) In this installation folder, find IMGGINA2.DLL
• 5) Rename IMGGINA2.DLL to IMGGINA2.XP
• 6) Find IMGGINA2.003
• 7) Rename IMGGINA2.003 to IMGGINA2.DLL
• 8) Go back into the Logon Utilities | Setup/Configure Logon Utilities and Re-enable the Logon Utilities
• 9) When you reboot, you will be back to where you started, and can now Enable the Remote Desktop feature
• IMPORTANT NOTES:
• The default IMGGINA2.DLL uses WinLogon Extensions 3, and supports NT/2000/XP.
• The file tagged as IMGGINA2.003 for Windows Server 2003 uses WinLogon Extensions 4
• You may need to be on Service Pack 1 for XP to use this

Original ID: PC205339

Download Patch for My-T-Pen, My-T-Soft, or My-T-Touch

• Download PATCH176.EXE file (220K) (MD5: A4D7738A414F1A4C577CEEEB90375A33)
• Alternate Download PATCH176.ZIP file (156K) MD5: 563F57D43799741369CA89AA12372C81)
• IMPORTANT NOTES:
• The Ctrl-Alt-Del option (Control Panel | Users and Passwords | Advanced | Require users to press Ctrl-Alt-Delete before logging on must be checked On to enable the My-T-Soft 2 keyboard display at logon.
• When the My-T-Soft 2 logon is enabled, the Un-install feature will not sense this. You must manually disable the logon utilities before attempting an un-install. This will be resolved in the 1.77 release.
• We have a report that the Patch Installation program (NOT the patch itself) has a problem when run in a portrait orientation. Please run PATCH176.EXE in the Landscape (standard monitor) layout. This also will affect the Logon Utilities setup program, and the Developer's Kit installation program. This will be resolved in the 1.77 release.
• INSTALLATION / SETUP NOTES:
• Use Windows Explorer to copy the file from the download location to the Installation folder, and after copy, execute the file from the Installation folder (e.g. \WINNT\MYTSOFT\PATCH176.EXE)
• The file MUST be run from within the Installation folder!
• This update is for version 1.75 of My-T-Pen, My-T-Touch, My-T-Soft (The update can be applied to versions 1.70/1.73, but these older versions have not been tested - if you do apply this patch, please report any issues to IMG technical support)
• A valid license is required for continued operation
• The layout position at logon is for a 640 x 480 screen - the keyboard may be moved as desired
• The layout is modifiable with IMG's Build-A-Board, or can use a KBF from later versions of the Logon Utilities
• The ZIP file contains (which updates or adds the following files)
• LOGON/KEYBOARD.KBF
• LOGON/KEYBRD01.KMF
• LOGON/MAC00000.KMF
• LOGON/MACROBAT.EXE
• BABDLL.DLL
• CTALTDEL.EXE
• IMGGINA2.DLL
• IMGLOGON.EXE
• MTS2.EXE
• MTSLIB.DLL
• STOCK.DLL

Original ID: PC205340

This is c