Possible installation problems and the MATLAB Compiler Runtime

The vast majority of WarpPLS users do not have any installation problems, but some users do. One possible cause is an incompatibility between the MATLAB Compiler Runtime and their computer's operating system setup. This is explored in more detail below.

Another possible cause of installation problems is one or more software applications that interfere with the proper running of WarpPLS. There have been reports from users suggesting that the following software applications may do that: Panda Antivirus, Norton Antivirus, and XLSTAT.

Yet another possible cause of installation problems are security software tools (to stop malware) that prevent users from making modifications in the folders in their computers that store data about programs. Closely aligned with this cause are security restrictions placed on computers by their organizations' IT offices.

The MATLAB Compiler Runtime

The MATLAB Compiler Runtime is for MATLAB programs what the Java Runtime is for Java programs, and what the Microsoft .NET Framework is for .NET-based programs. That is, it is a set of executable modules that are called by executable files compiled using MATLAB.

WarpPLS is an executable file compiled using MATLAB, and thus requires the MATLAB Compiler Runtime (version 7.14) to run properly. Like many other runtime libraries, the MATLAB Compiler Runtime has originally been developed in C and C++.

MATLAB does not have to be installed for WarpPLS to run

The MATLAB Compiler Runtime is provided in the self-extracting executable file used for the installation of WarpPLS. It is free of charge. MATLAB does not have to be installed for WarpPLS to run, only the specific MATLAB Compiler Runtime that accompanies WarpPLS.

In theory, the MATLAB Compiler Runtime should allow for a “compile once, run everywhere” approach to programming. That is, code that uses the MATLAB Compiler Runtime would be developed on one operating system, compiled, and then deployed, together with the MATLAB Compiler Runtime, to computers running any operating system.

This approach works well in theory, but not always in practice. This comment applies not only to MATLAB but also to Java and .NET applications – you are probably well aware of this if you are a Java or .NET programmer.

Seek professional IT support if you are using an organizational computer

It is possible that a specific user’s computer configuration will prevent the proper installation of the MATLAB Compiler Runtime, by blocking certain operating system configuration changes (e.g., Windows registry changes), as a security measure. This is often the case when organizational computers are used.

Also, a user may not have administrator rights on a computer, or have limited administrator/power user rights, which may prevent certain operating system configuration changes necessary for the proper installation of the MATLAB Compiler Runtime. Having professional IT support in this type of scenario is a must.

Here are a few steps to take if you are having problems installing and running WarpPLS on a Windows computer:

1) Run WarpPLS as administrator.

Some users solved their installation problems by simply doing this: Right-clicking on the WarpPLS icon and choosing the option to run it as administrator.

2) Reinstall WarpPLS using the larger file containing the MATLAB Compiler Runtime (approximately 170 MB), choosing the option “Repair”.

There have been reported cases in which users cannot start WarpPLS or move beyond WarpPLS’s first screen. This may happen even if the user has a valid license, with the software behaving as though it is not licensed at all. This may also happen before the user acquires a valid license, while trying to use WarpPLS within the trial license period.

A possible solution here that has worked well in the past is to reinstall WarpPLS using the larger file containing the MATLAB Compiler Runtime. When the MATLAB Compiler Runtime installation software pops up, choose the option “Repair”, and proceed with the full reinstallation.

3) Do the above, but change the folder where the WarpPLS program is installed, choosing a folder that is not in a protected area.

As a possible variation to the above, you may change the folder where the WarpPLS program is installed, choosing a folder that is not in a protected area. For example, you may choose the folder “C:\WarpPLS” or the folder “C:\WarpPLS [version]”. Being outside a protected area prevents certain software, such as antivirus software and malware, from interfering with WarpPLS’s execution.

4) Completely uninstall the MATLAB Compiler Runtime and WarpPLS, disable any antivirus software currently running, reinstall the MATLAB Compiler Runtime and WarpPLS, and then re-enable the antivirus software.

To uninstall the MATLAB Compiler Runtime, follow the following procedure (or a similar procedure, depending on the version of Windows you are using): go the “Control Panel”, click on “Add or Remove Programs” or “Programs and Features”, and uninstall the MATLAB Compiler Runtime.

To uninstall the main software program (i.e., WarpPLS), simply delete the main software installation folder. This folder is usually “C:\Program Files\WarpPLS [version]” or “C:\Program Files (x86)\WarpPLS [version]”, unless you chose a different folder for the main software program during the installation process. Then delete the shortcut created by the software from the desktop.

5) Check the "Program Files" and the "Program Files (x86)" directories (assuming that the MATLAB Compiler Runtime is installed on the C drive), to see if one of the following folders is there.

C:\Program Files\MATLAB\MATLAB Compiler Runtime\v714\runtime\win32

C:\Program Files (x86)\MATLAB\MATLAB Compiler Runtime\v714\runtime\win32

If not, make sure that you are logged into your computer with full administrator rights, and reinstall the MATLAB Compiler Runtime. You can do that running the self-installing .exe file (approximately 170 MB) for WarpPLS, which includes the MATLAB Compiler Runtime. Or, contact your local IT support, and ask them to help you do so.

6) Go to the Command Prompt and type “PATH”, to see if one of the following paths shows on the list provided.

C:\Program Files\MATLAB\MATLAB Compiler Runtime\v714\runtime\win32

C:\Program Files (x86)\MATLAB\MATLAB Compiler Runtime\v714\runtime\win32

If not, on the Command Prompt, type one of the following commands, depending on the folder in which the MATLAB Compiler Runtime is installed:

set PATH=C:\Program Files\MATLAB\MATLAB Compiler Runtime\v714\runtime\win32;%PATH%

set PATH=C:\Program Files (x86)\MATLAB\MATLAB Compiler Runtime\v714\runtime\win32;%PATH%

Then type “PATH” again, and make sure that the new path has been added. This will change the Windows registry; a minor and pretty harmless change. If you are concerned about making registry changes yourself, or cannot do that due to limited rights or any other reason, please contact your local IT support, and ask them to help you do so.

7) Try to install WarpPLS on a different computer, and see if it runs well there.

This last step is annoying but important because there are certain computer-specific configuration setups, or even malware allowed in by those setups, that may prevent the MATLAB Compiler Runtime from properly installing or executing. This is rare, but does happen sometimes. Comparing computers can help solve problems like these.

If you can install and run WarpPLS on one computer, but not on another, there may be a computer configuration or malware problem that is preventing you from doing so. If you have access to good-quality local IT support, you should contact it, and ask them to help you identify and solve the problem.

Error writing on System.sys at WarpPLS 1.0 start

(Note: This post refers to version 1.0 of WarpPLS only. The System.sys file has been renamed System.wrp in version 2.0 to avoid this problem.)

Some users may receive an error message on the WarpPLS command prompt window indicating that the System.sys file cannot be updated. This issue occurs when WarpPLS is launched, and seems to happen with a few Windows 7 users.

Even with this error, WarpPLS runs normally on the trial version. However, it does not allow a user to update the license information.

To solve this problem on Windows 7, follow the steps below. Similar steps related to granting users full control over a file should be followed with other Windows operating systems.

1) Go to the folder containing the WarpPLS program. Typically this will be:

    C:\Program Files\WarpPLS 1.0

2) Right-click on the file System.sys, and then choose properties.

3) Click on the Security tab.

4) Click on the Users group, and then on the button to change permissions.

5) Check the option to give the group Users full control on the System.sys file.

This problem occurs because Windows 7 does not seem to grant all computer administrator rights to new users, even when those users are included in the Administrators group.

By following the instructions on this post, you will essentially be allowing any user to change the System.sys file while running WarpPLS. This should not be a problem, as long as no user decides to manually delete the System.sys file.

Incompatibility between WarpPLS and XLSTAT

Most users seem to have no problems installing and running WarpPLS. A minority have problems with the MATLAB Compiler Runtime, which can be addressed by following the instructions on this post.

A very small number of users seem to be unable to properly install and run WarpPLS, even after following the instructions above. A common, but not exclusive, error message in this case is: “An application has made an attempt load the C runtime library incorrectly”.

One common characteristic among these users is that they have the software XLSTAT installed on their computers. I have already received a few reports suggesting XLSTAT changes operating system settings in such a way as to prevent WarpPLS from properly running.

When those users removed XLSTAT from their computers, they were able to run WarpPLS without problems.

WarpPLS running on a Mac? Sure!

When WarpPLS was first made available, I told a colleague of mine that it would probably run on a Mac without problems. Without trying, he said: No way Jose!

Then he really tried (using virtualization software, more below); it worked, and his response: Maybe u wuz royt eh!?

I have since received a few emails from WarpPLS users who own Mac computers. They run WarpPLS on those computers, without problems, even though WarpPLS was designed to be used with Windows.

How is that possible?

Those users have virtualization (a.k.a., virtual machine) software installed on their computers, which allow them to run WarpPLS on different types of computers, including Mac computers.

The virtualization software actually allows them to run the Windows operating system (typically the XP or 7 versions) on a Mac computer. They then install WarpPLS on the Windows virtual machine created by the virtualization software.

It seems that VMware is one of the most popular virtualization software systems in this respect.

Windows Vista issue with WarpPLS 1.0: mclmcrrt710.dll was not found

(Note: This post refers to version 1.0 of WarpPLS only.)

Some Windows Vista users have reported a problem installing and running WarpPLS 1.0. The error message  looks like this:

"WarpPLS_1_0.exe - Unable To Locate Component: This application has failed to start because mclmcrrt710.dll was not found. Re-installing the application may fix this problem."

This seems to be a problem of incompatibility between the MATLAB Compiler Runtime and Windows Vista. The problem appears to occur in some computer configurations, but not all of them.

The solution below has worked so far for all users that contacted me with this problem:

- Check your "Program Files" directory, and make sure that you have this folder there: C:\Program Files\MATLAB\MATLAB Compiler Runtime\v710\runtime\win32.

- If yes (usually the case when this problem occurs), go to the Windows command prompt, and enter this:

set PATH=C:\Program Files\MATLAB\MATLAB Compiler Runtime\v710\runtime\win32;%PATH%

(See screen snapshot below).

- Then restart the computer, and try to run WarpPLS again.

- If only restarting the computer does not work; reinstall WarpPLS, and then try to run WarpPLS again.