When performing an upgrade, the issues discussed in the topics below require consideration.
Upgrading to release 9.0 requires a new activation. See Product Activation to activate the D3 license for a multiuser environment.
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 the original Advanced Pick or D3 hard disk drive is to be used, be sure to have at least one full, verified file-save tape before proceeding (two are preferred). See Installation Troubleshooting. |
If a previous release of D3 has been loaded, D3 installation files may 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 that the specific directory to which the D3 installation files are loaded is the decision of the person performing the installation, but /tmp is the most common and is used for reference here.
To check for and remove old D3 files, enter:
|
cd /tmp ls -l D3* rm D3* |
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 updated if you are coming from a D3 7.3 or earlier release because of the frame size change. All custom code needs to be reassembled. If you have D3 7.4 or higher installed and already reassembled the custom code, there is no need to reassemble the custom code again. However, due to interface changes, it is recommended that 3rd party assembly code be recertified on D3 9.0.
See Also