Installations

mfd9_logo_135x149.png

Any Manifold Release 9 installation, whether it is a pre-release build, Cutting Edge build or officially published build, requires a Release 9 serial number with available activations.   If you do not have a Release 9 serial number with available activations you can procure a serial number on the Manifold Online Store.  All Release 9 serial numbers are x64, fully 64-bit serial numbers and will authorize both 64-bit and 32-bit installations.    Manifold Viewer is a free product based on Manifold Release 9 that does not require any serial numbers.

 

Manifold Release 9 and/or Manifold Viewer and/or other Manifold products such as Release 8 can be installed on the same machine with Manifold Release 9, Viewer and Manifold 8 being launched at the same time without conflict.   All types of Manifold and/or Manifold Viewer installations can run at the same time.  For example, all at the same time we can launch 32-bit Manifold, launch a 64-bit Manifold session, launch Viewer in 32-bit or 64-bit mode and also launch a Manifold .exe from a portable installation folder, and we can do so at the same time as launching a Manifold 8 session.

Cutting Edge Builds

Cutting edge builds are published to the Cutting Edge section of the georeference user forum and are known as Release 9 Edge or Viewer Edge,.   They are experimental builds that try out new ideas and provide an opportunity to beta test proposed new features before they appear in an official build.   Cutting Edge builds are published only as portable installations.

 

Cutting Edge builds are not supported in any way.  They are provided for advanced users who wish to experiment with the absolutely latest Release 9 build.    After a few such builds are explored and beta tested by advanced users who have a taste for the latest and greatest, Manifold incorporates changes from them and fixes into the next, formally supported and officially published Release 9 build.

 

Most Manifold and Viewer users will use Cutting Edge builds: they have been exceptionally stable and are the first to incorporate bug fixes and new features.  tech_ravi_sm.pngThis documentation tracks Cutting Edge builds and, at times, may include topics and information for features that are found in Cutting Edge builds but not in official builds.

 

Important:  Cutting Edge builds are time-limited in operation, with a timelock generally aligned to the end of the month in which the build was issued.   The time lock ensures that experimental builds which rapidly become obsolete do not continue in use long past obsolescence.  If a Cutting Edge build fails to launch, download and utilize whatever is the current Cutting Edge build.

 

Two Different Styles of Installation

Manifold provides two different ways to install Manifold, so we can pick the installation style we prefer: installations that utilize Windows Installer, or so-called "portable" installations.  Both styles have advantages and disadvantage, and both styles of installation can coexist on the same machine at the same time.

Windows Installer Installations

We can download a Manifold Release 9 installation in the form of a pre-packaged .exe file that utilizes Microsoft's Windows Installer facility. Installation .exe files are published for 64-bit Windows systems and 32-bit Windows systems.  Running the .exe installation file will perform an installation that installs require pre-requisites, un-installs older versions of Release 9 or Radian Studio installed with Windows Installer, and then uses Windows Installer to install Release 9 using an .msi file that is embedded within the .exe.

 

Advantages - Windows Installer is great both for unskilled consumers as well as skilled users in a hurry who want to install an application in the usual Windows way:

 

 

Disadvantages - Windows Installer attempts to protect unskilled users from themselves can lead to complications:

 

Portable Installations

We can download a Manifold Release 9 installation in the form of a .zip file that unzips into a set of folders containing both 64-bit and 32-bit versions of Manifold Release 9, ready for immediate launch with no further installation required.  This completely avoids the Microsoft Windows Installer system and has no effect whatsoever on any previous version of Manifold or Radian Studio that has been installed.  Portable installations are published both for the current, official build and also for any Cutting Edge builds that provide open beta-test access to innovative new builds before they are published as official releases.

 

Advantages - Portable installations do not use Windows Installer.  Portable installations thus avoid all of the complications that can occur when measures intended to protect unskilled consumers from themselves go astray.  Unzip the portable installation to whatever location we want, even a portable USB drive, and then launch from that location and Manifold is running.

 

 

Disadvantages - Portable installations are unsuited for totally unskilled users, and they require more effort.

 

 

For a step-by-step example of installation and activation see the Installation and Activation topic.

For Radian Studio Users

ico_nb_arrow_blue.png  Important:  Installing or activating Release 9 will remove and de-activate any Radian Studio or Manifold Future installation.    Release 9 is an upgrade from Radian Studio and replaces Radian Studio on your machine.

System Requirements

Manifold products are produced and licensed for true PC compatible hardware, running on the actual physical machine, and are not supported for PC emulators or virtual machines or other software which claims to mimic a real PC.  

 

Your hardware must support your proposed use.  For example, you must have 64-bit Windows running on 64-bit hardware in order to operate 64-bit Manifold.  You must have enough free space in storage to host the size projects you wish.   Available space and other resources must be configured sensibly to match the requirements of projects you wish to undertake.  For example, available user TEMP space should be three times the size of the largest data set to be processed.  See the  Performance Tips topic.

 

Release 9 and Manifold Viewer run on Windows 10, 8, 7 and Windows Server 20xx editions, both 64 bit and 32 bit. Release 9 explicitly supports Windows 10 with no need to run in a Windows 7 compatibility sandbox within Windows 10.  Release 9 will use DirectX12 when run on Windows 10 for improved display performance.   Manifold recommends Windows 10 or more recent.

 

You must login with genuine and full Administrator privileges to install Release 9.   Being a member of the Administrators group often is not enough as some Windows versions by default do not give full Administrator privileges to users who are members of the Administrators group.  It is best to login as THE Administrator login to install Release 9.

 

Machines running Release 9 or Manifold Viewer must have the following Microsoft packages installed:

 

 

Release 9 and Manifold Viewer .exe installation files include C++ Redistributable and will install it automatically if required.  Portable installations (packaged as a .zip file) do not include the C++ Redistributable.  For links to .NET and Visual C++ Redistributable installations, visit Manifold's System Requirements web page.

Release 9 Installation Files

There are three types of Release 9 installation files:

 

 

All Release 9 serial numbers are 64-bit and will authorize both 64-bit and 32-bit installations.  If you have 32-bit Windows, please make sure to download and install the 32-bit Release 9 installation file.   If you have 64-bit Windows, download and install the 64-bit Release 9 installation file.

 

Important: Installation files do not contain viruses.  Each file is published with an SHA1 checksum that you can use to verify the file you download is virus-free.   See the Using SHA Checksums topic for step by step instructions on how to verify an SHA1 checksum.

 

Installation using .exe installation files is described in the Installation and Activation topic.   .exe files will install the product as a regular part of your Windows system, accessible from the Start button and uninstalled by the Windows Control Panel's Programs and Features applet.  Use the .exe files if you want to install Release 9 and/or Manifold Viewer in the usual way.

Installing Release 9 or Manifold Viewer from a .exe File

Uninstall any prior installation before installing a new Manifold Release 9 installation. If Windows Installer reports any problems, read the  Windows Installer Problems page for advice.

Installing Release 9 from an .exe File

  1. Download the correct .exe file.

  2. Double-click on the .exe file to launch.

  3. If Windows 10 launches a Windows protected your PC dialog.

  4. Follow the installation dialog steps.

  5. Save the .exe file for future use.  We may need it some day to uninstall or to repair an installation.

 

For a step-by-step example of installation and activation see the Installation and Activation topic.

 

Before using Release 9 please review the short Read Me First topic.   

Portable Installations

Portable installations are for technically knowledgeable users.  Portable installations are self-contained zip files that do not utilize or otherwise interact with Windows Installer.  They provide a way to quickly launch Release 9 or Viewer without doing any Windows installation or having to remove a previously-installed Manifold package.  Users who want to try out Cutting Edge builds without altering their main Release 9 installation will use a portable installation.  Users who want the very latest software, a Cutting Edge version known as Release 9 Edge or Viewer Edge, will use a portable installation.    Multiple, different portable installations can be run side by side so users can launch different Release 9 builds at the same time.

 

To use a portable installation download the .zip file, unzip the file to create a folder hierarchy.   The 32-bit executable is in the bin folder (short for "binary") and the 64-bit executable is in the bin64 folder.  To launch Release 9 in 64-bit mode, double-click on the manifold.exe file found in the bin64 folder of the resulting folder hierarchy.   If we like, we can right click on the manifold.exe file and choose Pin to Start to add it to our Windows 10 Start button choices.  If we do that, we have to remember to unpin it if we prefer to switch to using a different portable installation.   To launch Release 9 in 32-bit mode, double-click on the manifold.exe file found in the bin folder of the resulting folder hierarchy. If Release 9 has been activated on that machine, then Release 9 will run from a portable installation without any further need to activate.   If Release 9 has not been activated, then on first launch the Activation dialog will pop open.  Viewer is exactly the same except that since it is free and does not use a serial number or activation there is never an activation dialog that pops up.

 

For portable installations, if you do not have a recent C++ Redistributable installed on your computer, you must download and install the appropriate C++ Redistributable to run a portable installation.   See Manifold's System Requirements web page to get C++ Redistributable installation packages.

 

 

 

If any of the above is confusing, do not use the portable installation but instead use a regular .exe installation that will install Release 9 as part of the Windows Start menu system.

64-bit Windows Limits on 64-bit Manifold

Due to a lack of required Microsoft facilities in 64-bit Windows systems, in most such systems Manifold in 64-bit mode cannot export, import or link to DB, HTML, MDB, XLS or WKx format files.

 

The workaround for importing or exporting such files is to utilize the 32-bit version of Manifold that is automatically installed in every 64-bit Manifold installation in addition to the 64-bit version of Manifold.   To import  we launch Manifold in 32-bit mode and import into a Manifold .map project file.   We can then launch Manifold in 64-bit mode and open that .map project file or link to that .map project file.  To export, we launch Manifold in 32-bit mode, open the .map project desired and export to the desired format.

 

For important information and discussion please see the Essay on .mdb files and 32-bit or 64-bit Manifold.

V8, CUDA and External Libraries

Release 9 installations include V8 and CUDA.   There is no need to download or install other files to turn on either built in JavaScript or GPGPU capability.  Manifold Viewer is not GPU parallel and does not support scripting so it neither installs nor uses either V8 or CUDA.

 

External libraries are loaded using a shared service. Libraries that are part of the operating system are loaded from system paths.   Other libraries are loaded from both system paths and Manifold paths. The results of loading are reported in the log with successful loads of system libraries reporting nothing, successful loads of non-system libraries reporting the full path of the loaded module (useful when there are multiple modules with the same name) and failed loads report errors both for failed loads of system libraries as well as failed loads of non-system libraries.

Hardware

System memory is cheap and your time is expensive.   Manifold is very fast and faster still with more memory.  Load up your computer system with the most memory you can afford, ideally to maximum system RAM.  Larger memory is much more important than paying disproportionately more for a slightly faster processor.

 

TEMP storage space will be used if operations do not fit into memory available.  For maximum performance, specify the Windows TEMP location to the fastest local disk drive, for example, a fast SSD drive.

 

Large disk drives have become very cheap, while your time is getting ever more expensive.  Release 9 is designed to happily trade off making files and saved projects larger if that helps to improve performance and to make your work go faster.    Data sets often used with Release 9 are huge, with data sets in the tens of gigabytes size being typical.   When Release 9 imports and saves such data sets in projects the resulting project files will be even bigger.   

 

Invest in large disk drives that can store terabytes of information.   Big disk drives are not only cheaper for the storage they give, they are also faster than smaller disk drives.    Disk drives are so cheap you should always have at least two so you can configure RAID mirror storage for an automatic backup if a disk drive fails.

 

Anybody working with big data is likely to already have a reasonably powerful processor with at least four cores and more likely eight or more hypercores.   If you can afford it, it doesn't hurt to buy a faster processor with many more cores.    Release 9 parallelizes just about everything so if you have more cores Manifold can usually put them to work for better performance.

 

Do not go crazy spending a lot of money to get just a slight increase in performance.   Instead of spending twice as much for a processor that has a clock rate only 10% faster than a less extreme version, put the extra money into more system memory and into larger and faster hard disks.

 

GPGPU

 

Release 9 uses GPUs for massively parallel computation, known as General Purpose GPU or GPGPU.  Manifold Viewer does not use GPGPU.   GPGPU capability requires installation of an NVIDIA GPU of at least Fermi architectural generation or more recent.  Since you must have graphics display in any event it is crazy not to have a GPGPU capable graphics card.   Unless you are a Manifold expert and know for sure the extra cost is worth it, there is no need to spend a fortune to buy the most extreme possible GPGPU card.   Virtually any sensibly middle-of-the-road GPGPU card will be fine.    For greater discussion of GPGPU use and configuration, see the GPGPU topic.

 

Notes

Why .EXE and not .MSI?  - Manifold Release 9 installations that use Windows Installer are .exe files and not the usual .msi files that are often used for Windows Installer installations.  An .exe file is used because .exe files allow the installation to perform preparatory steps,  such as installing C++ redistributables if required, that cannot be accomplished with an .msi.  Once those preparatory steps are accomplished the .exe launches an .msi file that is contained within the .exe so Windows Installer can go to work with that .msi.

 

See Also

Installation and Activation

 

Using SHA Checksums