Release Notes for Xerox® DocuShare® Drive
DocuShare Drive Version 1.5 Revision 1
INSTALLATION
You must be an administrator on the computer to install and remove DocuShare Drive. Creating a system restore point prior to running the installer is recommended. To run the installer, use DSDriveSetup.exe on a 32-bit machine, or DSDriveSetup64.exe on a 64-bit machine. The setup program ensures that the installer runs with an approriately elevated administrator privilege.
The setup program is generated using the Microsoft IExpress self-extract technology. It supports the setup switches described in the article from below.
http://technet.microsoft.com/en-us/library/dd346761.aspx
To perform the installation silently, use the /Q switch.
If you want to pre-select a DocuShare server for auto-mapping during the installation, you need to override the default MSI launch command. To do so, use the /C switch. Here is an example.
DSDriveSetup /C:"msiexec /i DSDrive.msi /lv DSDriveInstall.log
DSURL=http://www.yourbusiness.com/docushare MAPFIRSTSERVER=1"
The above command pre-selects a DocuShare at http://www.yourbusiness.com/docushare for automatic mapping at the end of the installation process.
If you just want to extract the MSI file, use the /T switch (followed by specification of a destination
directory).
If you have customized the MSI and must run the MSI directly, start a command prompt with administrator privileges, CD to the directory of DSDrive.msi, and issue the command, msiexec /i DSDrive.msi. If the installation is not run with an elevated privilege, the installer will not be able to correctly update your machine's netwok configuration. The installation itself may complete. But, the runtime will likely malfunction. The setup program now supports installer customization and setup program creation in one step. Refer to FAQ for instructions.
If you are installing DocuShare Drive on a machine with DocuShare Client installed, you must disconnect all servers prior to running the installation. Also, when running the DocuShare Drive installer, make sure that the 'DocuShare Client update' feature is selected in the Custom Setup screen.
The installation requires pre-installation of Microsoft Visual Studio C++ 2008 SP1 Redistributable . DSDriveSetup does not include it. So, you must install it separately. If the target machine is 64-bit, make sure that both 32-bit (x86) and 64-bit (x64) editions of the redistributable are installed. If you have access to the DocuShare Client 6.5.x setup program, you can use that to download and install the right prerequisite library. As soon as the library finishes installing, quit the setup program, and come back to DSDriveSetup. The prerequisite is already met if the target machine has the DocuShare Client installed. The redistributables are available from these Microsoft sites.
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
http://www.microsoft.com/en-us/download/details.aspx?id=5582
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
http://www.microsoft.com/en-us/download/details.aspx?id=2092
WHAT'S NEW
Support for Microsoft Windows 10.
FIXES
Check-out and check-in works for Cloned Document objects (SPAR 97084).
Multiple DocuShare Drive users on the same computer no longer see each other’s documents. (SPAR 91101)
You can use the context, or right click, menu command Check in document(s) to check in custom documents. (SPAR 92392)
The Go to DocuShare URL command now works correctly. (SPAR 94251)
Dragging and dropping a document to DocuShare Drive installed on Windows 8.1 no longer creates two document versions. (SPAR 95082)
Double-clicking documents located in collections with short titles now locks the documents. (SPAR 95617)
When using Don’t prompt for the File check-in control, changes made to macro-enabled Office documents are now saved after check-in. (SPAR 96177)
When checking in multiple documents sequentially, the version comments for each document are saved correctly.
SYSTEM REQUIREMENTS
Microsoft Windows 7 with SP1 (32- and 64-bit), Microsoft Windows 8.1 (64-bit), or Microsoft Windows 10 (64-bit).
Microsoft Visual Studio 2008 C++ Redistributable SP1.
Microsoft Internet Explorer version 10 or 11.
1 GB RAM on 32-bit systems; 2 GB RAM on 64-bit systems.
20 MB free disk space for program files on 32-bit systems; 40 MB on 64-bit systems.
100 MB free disk space for work and temporary data.
TCP/IP network connection to a DocuShare server running version 6.6.1 Update 3 Patch 2, or higher.
KNOWN ISSUES
DocuShare Drive cannot check out a file in Microsoft Edge on Windows 10.
This version of DocuShare Drive only integrates with Internet Explorer for the DocuShare file check-out functionality. It does not integrate with any other web browsers including Edge.
Windows 10 does not show a padlock for a checked out DocuShare file.
Windows 10 installs 5 overlays for its OneDrive feature. Also, Microsoft Office 2013 and 2016 installs 3 additional overlays. DocuShare Drive installs a couple of custom icon overlay images as part of its desktop integration. One is a padlock image that is displayed after a server file is checked out and locked for editing. The other is a logo that is shown to identify a DocuShare network drive mapped by DocuShare Drive.
This is how the issue arises. The Windows GUI system allocates limited RAM space for storing custom overlay images and making them available to applications. Typically, the system has only enough space for 8 to 11 custom overlays after it loads preset system overlays. If the space is not large, the overlays of OneDrive and SkyDrive may squeeze out the DocuShare overlays. This leads to a display problem in File Explorer where DocuShare Drive does not show a padlock for a DocuShare file that's been checked out for editing. Or, it leads to a problem where a mapped DocuShare drive no longer receives the DocuShare logo. DocuShare Drive requests for the image, but the system cannot load the padlock or logo image because it has run out of space, and so the requested image does not show.
The overlay limitation is an issue of system resource constraint, and is a system issue. DocuShare does not offer a formal fix. Microsoft has documented the issue in this KB article (http://support.microsoft.com/kb/3106961). But, Microsoft does not offer a fix that makes the system to load and utilize all of the custom overlays added by Microsoft and 3rd party applications. However, there are a couple of methods that can be used for working around it and getting the DocuShare overlay images to show. Here they are.
Remove SkyDrive.
OneDrive and SkyDrive both represent the same Microsoft cloud-based file storage. If OneDrive is kept, SkyDrive could be removed without losing the ability to access the remote storage.
Rename the DocuShare overlays.
The system can load and make available to applications only as many overlays as those that can fit in a RAM storage space it allocates. This space is typically limited to 8 to 11 on Windows 10.