You can skip this in seconds

Click here to continue

Download Now!

DroboPro Firmware 1.1.4

DroboPro Firmware DroboPro Firmware 1.1.4

DroboPro Firmware Publisher's Description

DroboPro Firmware 1.1.4 descriptionFixes:
Corrected a performance problem that could occur in a small number of situations
Improved compatibility with the latest Unibrain FireWire driver
Fixed problem with formatting EXT3 volumes greater than 2TB (up to 8TB)
This release is VMware ESX 3.5 certified

General Issues
-Symptom: DroboPro takes a long time to startup when in the process of protecting data (#5497).
Condition: If the DroboPro has dual disk protection enabled and was in the middle of protecting data, it can take up to five minutes for the DroboPro to completely start up after a power loss.
Workaround: None. Wait for the DroboPro to finish its startup process.

Windows XP Specific
-Symptom: Windows XP may become unstable with a FireWire-connected DroboPro (#6117).
Condition: Windows XP may become unstable when the DroboPro has more than 12 volumes and is connected using FireWire.
Workaround: If you must use more than 12 volumes, then switch to either iSCSI or USB.

Windows Vista Specific
-Symptom: The iSCSI connection does not work without SP1 or later installed (#5056).
Condition: The iSCSI initiator built into Windows Vista does not work with DroboPro until SP1 has been installed.
Workaround: Update the installation of Windows Vista to SP1 or later by running Windows Update.

-Symptom: Full format does not complete with Windows Vista (#1651).
Condition: DroboPro does not support a full format from Vista for a volume bigger than the space available.
Workaround: Choose the quick format option if you use Windows Vista to format DroboPro.
Windows Server 2003 Specific

-Symptom: A volume formatted as FAT32 or NTFS is not detected by Windows Server 2003 (#2496).
Condition: If DroboPro is formatted in FAT32 or NTFS using the Drobo Dashboard or a different OS, such as XP, Windows Server 2003 does not recognize the FAT32 or NTFS volume.
Workaround: Use the Disk Manager OS utility on Windows Server 2003 to manually assign the FAT32 or NTFS volume a drive letter.


It is highly recommended to always use the most recent driver version available.

Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.

Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.

Look for Similar Items by Category

Feedback

Popular Downloads