<--- zurück zu matchware.com
knowledge-base/de »

Autor: Peter Arnold

A viewer can be downloaded for OpenMind 2 (PC and Mac versions) from the links below:

OpenMind 2 (PC) Download Viewer (English, French, German and Danish)
OpenMind 2 (Mac) Download Viewer  (English)

This is most likely caused by a mismatch in version between the two copies of OpenMind you used to create and edit the document. Both copies must have the same version number; to check this you can use the help -> about menu item and take note of the build number. Higher build numbers of OpenMind can always open mind maps created in lower build numbers of OpenMind but the opposite may not be possible.

If the versions do not match you should immediately update to the latest service pack, on both copies if both build numbers are lower than the latest release.

A problem has been discovered in the file MAPI32.DLL inside C:WINDOWSsystem32 – this file is replaced by email clients that are installed on the computer. The version used by third-party email handling applications to replace the original MAPI32.DLL is an incompatible version which lacks important functions, hence the message “Ordinal 21 could not be located in the dynamic link library MAPI32.DLL” when attempting to run OpenMind 2 Business Edition.

Microsoft Knowledge Base has the following solution to the problem:

From the command prompt, type “%systemroot%system32 ixmapi.exe” (or use the start menu -> run). You will not see any feedback but this replaces the error prone MAPI32.DLL with a backup version. Your old MAPI32.DLL will be renamed to MAPI32x.DLL where “x” denotes a version.

Alternatively you can manually place a copy of MAPI32.DLL in the OpenMind 2 Business Edition folder – this file will then be used if the original MAPI32.DLL has errors. Use this method if the method above fails. Remember to restore your MAPI32.DLL by replacing it with the MAPI32x.DLL backup if the above method causes an email application to fail!

A fix for this problem to allow OpenMind 2 Business Edition to run even if the MAPI32.DLL file has errors will be released with the next service pack.

This happens for formatting such as bulleted lists and tables. The reason is that Mediator does not support this type of formatting and is uncapable of stripping incompatible formatting codes from the text. The result is that entire blocks of formatted text are removed when exporting from OpenMind 2 to Mediator.

Currently there is no fix or workaround for this except for manually removing formatting before the final export. Mediator 9 is expected to be tables- and bullet list compatible, at least.

A common problem when designing e-portfolios is how to use the “File link” feature to link to files from within the text editor: while this works fine when running the project inside OpenMind, after exporting to HTML most users find that the file links are now unusable.

The solution is to include the files in a special folder in the export, and then link to the files contained therein using URL links instead. A step-by-step guide is provided below:

  1. create a folder somewhere for the project you’re working on. To avoid any future frustration over missing files, please make sure the folder is located somewhere safe, like in the same folder as the project file itself (the desktop is a bad choice). For this example, let’s say the new folder is called “eportfiles”.
  2. copy all external files used by your project into the new folder. You can add more files later – just remember that all files in the folder will be included upon export, so try to keep it tidy to avoid having to upload several (hundred) megabytes of redundant data.
  3. add the “eportfiles” folder to the OpenMind project export, using the “Tools” -> “Additional folders” menu. This will ensure that the entire folder, including all files, will be included whenever the document is exported to something like HTML.
  4. create links like you usually do, but choose “URL link” instead of “File link”. Assuming you’d like to link to a file called “cv.pdf”, you’d input the following into the path field: “eportfiles/cv.pdf” (without the quotes, and without the default “http://”).


Now, when the project is exported, a relative hyperlink is created – and because the “eportfiles”-folder has been included in the export, this link will now point to the newly exported copy instead of the original on your own machine (or network).

A bug in the first release of OpenMind causes export to Word and PowerPoint to be disabled for underprivileged users. The symptom is that the file type selection box is greyed when choosing export to Word or PowerPoint. Administrators are allowed to use the export functions with no limitations.To correct this problem, install the latest service pack for OpenMind. This will allow underprivileged users to use the Word and PowerPoint export functions.

When copying and pasting content from Word the images that are copied are stored as embedded objects. These objects do not get copied upon HTML export, so any images that have been inserted in Word, they copied to OpenMind text notes, will not be included in the export.

To fix this problem you must remove the images in the text note and re-insert them using the image tool in the text note editor itself. This will cause the image to become registered as an attached media file and it will subsequently export as expected to HTML, making the export folder fully portable.

When exporting from OpenMind Business to MS Project, some users have experienced that tasks set at 0% completion show up as complete (100%) in Project. This is due to a bug in the transformation file used to communicate with Project – a fix will be included in all future releases, but can also be found here.

A ZIP-file has been attached to this page: download it and open it. Inside you will find a file called Project XML.xsl – this file should be extracted to the following path (depending on your operating system), overwriting the existing file:

Windows 2000 / XP / Vista:
C:Program FilesMatchWareOpenMind 2.0 BEXmlExport

Windows Vista 64b:
C:Program Files (x86)MatchWareOpenMind 2.0 BEXmlExport

(These are the default installation paths; if you installed OpenMind elsewhere, locate its installation folder and overwrite the file in the XmlExport subfolder)

Ein Problem mit dem MSI-Installation-Werkzeug führt dazu, dass das SP2 nicht auf vorhandene Installationen von OpenMind 2 Home nicht durchgeführt wird, falls SP1 bereits installiert wurde.

Um das Problem zu beheben, müssen Sie OpenMind 2 deinstallieren, dann neu von der Original-CD neu installieren (oder von einer downgeloadeten Installationsdatei). Nachdem OpenMind 2 erneut installiert ist, können Sie direkt SP2 installieren.

This is a problem with the first build of OpenMind 2 – the symptoms are that the application will ask for a serial even if it was entered during the administrative installation process. To rectify this problem, apply the latest service pack to the administrative installation before pushing it to clients. Below are the instructions for patching an administrative installation (for more information, see the manual or help file on “administrative installations”).

Applying a patch package to an administrative installation

  1. Choose Start – Run.
  2. Type:

msiexec.exe /p <path to .msp file> /a <path to administrative .msi file>

Members of the workgroup using OpenMind must then reinstall the application from the new administrative source image to receive the update.
To completely reinstall the application and cache the updated .msi file on their computer, users may enter either of the following commands:

  • msiexec.exe /fvomus //server/<administrative .msi file>
  • msiexec.exe /I //server//<administrative .msi file> REINSTALL=ALL REINSTALLMODE=vomus