Aspera Drive 1.1.1 Release Notes
Aspera Drive 1.1.1 Release Notes

Aspera Drive 1.1.1 Release Notes

  • Product Release Date: Sep 5, 2014
  • Release Notes Updated: Sep 8, 2014

WHAT'S NEW

Welcome to this release of Aspera Drive. Drive 1.1.1 is a maintenance release.

KNOWN ISSUES

  • #23230 - Send to Faspex: Aspera Drive cannot send packages to some valid Faspex usernames if those usernames contain the following special characters: < > ; ( ) &
  • #24193 - Send to Faspex: "Send to Faspex" option is not available for the first right-click attempt of a file after an Aspera Drive installation, but is available on all subsequent attempts.
  • #25913 - Sync: During a sync scheduled in Aspera Drive, even if files on the Shares server are changing (that is, are in the process of being downloaded), Aspera Drive nevertheless attempts to sync those files, resulting in file errors and conflicts.
  • #26641 - Sync: Cannot drag-and-drop files from the remote server when the files have the same name but different case (for example, aspera1 and Aspera1).
  • #26725 - Sync: An initial sync of a large number of files results in high CPU usage.
  • #27153 - Send to Faspex: If the host is unreachable while Aspera Drive is sending a Faspex package, Drive shows a "Not responding" error. The "Not responding" state persists for approximately one minute.
  • #27587 - Temporary files that applications (such as Microsoft Office) create are excluded from sync transactions. The affected files are those with names of the form ~$* or ~*.tmp.

SYSTEM REQUIREMENTS

Windows

On your Aspera Drive client:

  • Windows 7 or 8

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or higher with a Sync-enabled license.

Mac

On your Aspera Drive client:

  • OS X 10.8 or 10.9

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or later with a Sync-enabled license.

PACKAGE INFORMATION

Windows: AsperaDrive-1.1.1.92281.msi:
md5: e678985e2045614bf67c8e57c8eb8e04
sha1: b24c87994b8c36e72b7c9312dc6929aa3978e546
Mac OS X: AsperaDrive-1.1.1.92524.dmg:
md5: 283db0fbba8a6ff36809818d8a539db4
sha1: 1c769d62d669a9a82f8cbab572ddfb86f7db3357

PRODUCT SUPPORT

For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.