Mangomind Readme

Mangomind Version 3.5.1 README

This document describes new features in this release, known installation and operational issues, and describes how to contact Technical Support.

New In This Release

This release of Mangomind contains the following new and improved features:

Support for Windows Vista and Windows Server 2003
Improved Transfer Status - this window now gives better feedback regarding file upload, download, and metadata synchronization.
New "Copy as Link" feature - you can now easily create links to files and folders on a Mangomind drive by right- clicking them, selecting the Mangomind option, and then the new "Copy as Link" sub-option. This places a hyper- link to the document on your clipboard that you can then paste into a rich text document or email.

Minimum Requirements

Windows 95, 98, ME, NT 4.0, 2000, XP, Server 2003, Vista. Note that while Mangomind has been tested to run on older versions of Windows (95, 98, ...) use on such systems is supported only to the extent that Microsoft supports the underlying operating system.
32MB of RAM above and beyond the amount of memory required by your operating system and other applications.
100MB disk space recommended for caching files from your Mangomind drive.
Web browser. Microsoft Internet Explorer or Netscape versions 4.0 or higher recommended.
Access to email.

Known Issues

Online Help on Windows Vista

Mangomind Requires WinHelp for Online Help to Function On Windows Vista

WinHelp is not included with Windows Vista and is needed to view Mangomind online help. You can download WinHelp for Vista from http://go.microsoft.com/fwlink/?LinkID=82148

Installation of Software and Joining Mangomind Drives

Unable to Connect to the Mangomind Service Through A Locked Firewall

The Mangomind client software will attempt to access the Mangomind server using TCP/IP ports 7391 and 7392. Unfortunately, some companies block communications through TCP/IP ports for security reasons. These ports must be open in order for Mangomind to successfully communicate through TCP/IP. To open these ports, contact your Network Administrator.

In those cases when TCP/IP access is not allowed, Mangomind will try to connect through HTTP port 80 or HTTPS port 443, which are the default ports for web browsing. If your firewall supports HTTP 1.1, the client software will be able to communicate with the Mangomind servers. If HTTP/HTTPS access is not supported, Mangomind will try to connect through a SOCKS proxy.

Upgrading Client Software from Previous Versions

Drive Letter Mapping May be Lost During an Upgrade

When you upgrade your Mangomind client software to the latest version, certain Mangomind-specific files must be converted to the new version. This can take a few moments if you have a large Mangomind drive. If you log in to your computer before this conversion process is complete, Mangomind will not be able to map a drive letter to your Mangomind drive. To fix this problem, simply log out and log back in again. Your drive letter mapping should be re-established.

Upgrading from Windows 95/98/ME to Windows NT/2000/XP Requires Portable Identity File to be Saved Before Uninstalling the Mangomind Software.

Due to significant system changes during the upgrade, you will need to ensure you have created Portable Identity files for all of your Mangomind drives, and then uninstall the Mangomind client software prior to the upgrade. Once you have finished the upgrade, you can install the Windows NT/2000/XP version of the Mangomind client software, and then double-click each drive's Portable Identity file to restore full access to these drives.

Offline Use of Mangomind Drives

Some Applications May Not Support Offline Use

Certain applications like databases, accounting packages, personal organizers and other multi-user applications do not support offline use. Because of this restriction, working in offline mode with these applications may result in content conflicts that cannot be resolved.

Mangosoft recommends that the Drive Administrator(s) do one of the following to ensure the integrity of the data:

Make sure users only use these applications in online mode.
Set strict security so that only one user has Full access to the data, while all other users have Read access.
Prevent users from accessing the data while they are working offline by setting the Offline Access Policy to deny any offline access.