HotShift uses the latest (Service Pack 6) VB runtime files.

If you have problems running HotShift, it is possible that the installer could not install the one or more of the VB6 runtime files.

You may try uninstalling HotShift and installing the VB6 runtime files first.

This will prepare your PC for any program which uses these files. Check the following link for more info. 

VB6 Service Pack 6 Runtime Files support page.

Installing on a Server

Error 2755 is a generic or system-specific error. This error occurs on some systems triggered by the combination of how the setup is run on certain machines and how the machines are configured internally. Following is a list of common causes of this error:

  1. There is a corrupted version of Windows Installer engine on the machine.

     

  2. The setup does not have access to the Temp directory or if the default Temp directory of the machine is not clean or does not have enough space to run the setup.

     

  3. The setup is being run over a terminal Server via a mapped network drive.

     

  4. The setup is unable to create or write to the Installer directory in a Windows NT system environment.

     

  5. The setup has some custom actions that are not configured properly.

Resolution

 

Listed below are suggested solutions to the causes in the order in which they appear above:

  1. To ensure that the Windows Installer service is properly installed and configured, it is recommended that users install the file InstmsiA.exe on Windows 95/98/Me or InstmsiW.exe on Win NT systems. The file InstmsiA.exe and InstmsiW.exe are Microsoft redistributables that install the Windows Installer service on the machine. You can download the latest version of Windows Installer Service from Microsoft's Web site at:

    Windows 9X/ME

    Windows NT 4.0 & Windows 2000 SP1 and lower

    Windows 2000 SP2 and Higher and Windows XP

     

  2. Make sure that the default Temp directory is clean. To look for the default Temp on the machine, launch the command prompt, type 'Set' and press enter. This lists all of the environment variables, including Temp. Go to the path specified by Temp on the machine and delete all files in this folder.

     

  3. If the error occurs while running on a Terminal Server, users should use a UNC path to point to Setup.exe or the MSI package, rather than a mapped drive. (A UNC path has the format: \\myserver\myfolder\package.msi, while a mapped drive has the format: M:\package.msi.)

     

  4. In the Windows NT environment (Windows NT, 2000, XP), check to make sure that you have write access to the C:\WINNT folder. To have write access to this folder, you must have administrative privileges on the system. In the absence of this privilege, setup fails to create or write to the Installer directory located inside the C:\WINNT directory, causing the error. Users can contact their system administrators for more information on administrative privileges.