Upgrade issues

You should consider the listed issues when performing an upgrade.

Upgrading to release 10.3.4 requires a new activation. See Activating D3 to activate the D3 license for a multi-user environment.

Data and partitions overwritten

The upgrade installation process overwrites existing data and partitions on the target hard disk. To ensure no loss of data, we recommend these considerations:

Use a new hard disk drive for this installation, rather than writing over an existing Advanced Pick or D3 installation.
If there are hardware compatibility issues with the new platform of D3 Linux, or there is another issue which necessitates going back to the previous platform, the task is easier if that previous platform still exists on the original disk drive.
Perform a complete file-save of the source hard disk.

Warning: IT IS IMPORTANT TO BACK UP EXISTING DATA ON THE DISK. THE INSTALLATION OVERWRITES EXISTING PARTITIONS. ALL DATA WILL BE LOST.

CAUTION:

If you are using the original Advanced Pick or D3 hard disk drive, be sure to have at least one full, verified file-save tape before proceeding (two are preferred).

See Installation troubleshooting.

Removing files from a previous installation

Note: You should back up the old files or move them to another directory prior to using the tar utility for new files.

If a previous release of D3 has been loaded, D3 installation files might still be present in the /tmp directory. These are the files loaded from media with the tar command. These files must be removed before a new release of D3 is loaded.

Note: The specific directory to which the D3 installation files are loaded is the decision of the person performing the installation. The /tmp directory is the most common and is used for reference in this document.

To check for and remove old D3 files, enter:

 cd /tmp
 ls -l D3*
 rm D3*

Third-party products that use assembly code

You must obtain a new copy of any third-party product that uses assembly code. For example, Accuplot, PowerComm, Jet, and so on. Third-party products that use assembly code must be reassembled with the D3 10.3.4 assembler. All custom code needs to be reassembled.