This only applies to releases prior to 2007

The Setup program currently remains a 16-bit application for support for Windows 3.x. In general, this does not cause any problems or issues, but the following may be relevant to certain individuals:

• Changing the default install location will require a short (8:3) naming convention - a long file name (such as "\Program Files" will cause problems - use (after verifying) "\PROGRA~1")
• In NT/2000/XP, a Virtual Machine is used with WOW (Windows on Windows) compatibility - make sure any appropriate Windows Service Packs are installed
• Supporting older versions of Windows - What a concept!

Original ID: PI300314

(NOTE: This has not been a common problem since Windows 98 SE, circa 1999)

There is a known compatibility issue with various video drivers when running our SETUP.EXE in certain resolutions / color depths. Any errors are related to an improper implementation with the driver's ability to perform the Windows API StretchBlt operation (GDI support). We apologize for any inconvenience, but this is NOT a problem with IMG software. If you experience any errors or difficulties while installing IMG software, we suggest you do one of the following:

• Obtain the most up-to-date driver from the manufacturer of your video adapter.

• Reduce (or change) the color depth / resolution of your video display and rerun SETUP.EXE (Display Properties | Settings)

• Change the video settings to the Standard VGA or Super VGA and rerun SETUP.EXE.

Original ID: PI300315

This only applies to releases prior to 2007.

The Setup program currently remains a 16-bit application for support for Windows 3.x (schools, hand-me-down systems, etc.). Please note that Microsoft no longer supports Windows 3.x at all - please consider this. Windows NT/2000/XP allow 16-bit progrmas via a "Windows on Windows" (WOW layer) compatibility subsystem. Normally this is transparent to the user.

• This is related to the file AUTOEXEC.NT located in the \WINDOWS\SYSTEM32 folder - it may be missing or corrupt.
• The best solution is to copy the file AUTOEXEC.NT from the \WINDOWS\REPAIR folder to the \WINDOWS\SYSTEM32 folder. If you are familiar with Windows Explorer, simply locate the file AUTOEXEC.NT in \WINDOWS\REPAIR, then copy and paste into \WINDOWS\SYSTEM32 (you may need to show files).
• To type the command directly:
• Start Menu | Run
• Type CMD, then click OK
• At the command prompt type COPY \WINDOWS\REPAIR\AUTOEXEC.NT \WINDOWS\SYSTEM32[Enter]
• Type EXIT[Enter]
• CONFIG.NT and COMMAND.COM can also cause this - For other information, see Microsoft's Knowledge Base Article 305521 and Article 324767.
• Supporting older versions of Windows - What a concept!

Original ID: PI300313

The Setup program looks for Windows with certain names, and one of these windows is the Welcome screen run when you first install the software. Unfortunately, the program looks at ANY window with Welcome in the caption, and reports this result. We have created a program that looks at the same items as Setup, and reports details so you can shutdown or remove the particular program causing this conflict. You can download VERIFY.EXE (MD5: 5BDBB80834BA96C52BA12C16184C4B1D) and run it on the system reporting this message to diagnose what particular program is causing this conflict. You can use Task Manager (or Add/Remove programs) to close or remove the problematic program. Once Setup is complete, you can reboot to reset the system, or restart the program, or re-install the program.

For downloaded demos, another solution is to use a different install approach, see Alternative Downloads for My-T-Soft.

Original ID: PI300316

The MSI files are essentially databases of information used by the Windows Installer to install the files and setup a system. The executable to use is "msiexec.exe" and any appropriate command line switches. In general, if you double click on an MSI file, Windows launches msiexec with the /i install option (e.g. "msiexec /i mts178_2000xp.msi").

For some basic, frequently asked for options, here are a few that can be used with the standard IMG MSI install files (these switches are not case sensitive):

In these examples, the msi file should be replaced with the msi file you want to operate on…

msiexec /i mts178_2000xp.msi
This installs My-T-Soft 1.78 (using the user interface)

msiexec /i /qn mts178_2000xp.msi
This silently installs My-T-Soft 1.78 (with NO user interface)

msiexec /x /qn mts178_2000xp.msi
This silently un-installs My-T-Soft 1.78 (with NO user interface)

msiexec /a mts178_2000xp.msi /qn TARGETDIR="C:\Documents and Settings\Full User\Desktop\Test"
This silently installs My-T-Soft 1.78 (with NO user interface) to a different target directory (for testing, etc.)

Further notes on command line switches:

/a = Administrative install - allows use of TARGETDIR override

/i = standard install

/x = standard un-install

/q? = user interface options

/qn = Displays no user interface.
/qb = Displays a basic user interface.
/qr = Displays a reduced user interface with a modal dialog box displayed at the end of the installation.
/qf = Displays the full user interface with a modal dialog box displayed at the end.
/qn+ = Displays no user interface, except for a modal dialog box displayed at the end.
/qb+ = Displays a basic user interface with a modal dialog box displayed at the end.
/qb- = Displays a basic user interface with no modal dialog boxes.

For further info on msiexec.exe, refer to Microsoft's documentation.

For safety reasons, certain drive letters will not be checked for a USB device. Using Disk Management (In Windows XP, the easiest way to get to this is: Control Panel | Administrative Tools | Computer Management, then select Disk Management), you can change the Drive Letter to a H: or K: or other drive letter, and then re-run the USB install. You must have the USB device installed, and it must be visible as a drive in the Computer view of Windows Explorer.

• Return to Technical Support