NOTE: The English version of Delphi 2005 updates Internet Explorer with the English version of Internet Explorer 6.0 SP1. If you are running a localized operating system, run Windows Update to ensure that you get the proper localized version of Internet Explorer.
The bootstrap utility detects whether the following Delphi 2005 pre-requisites are installed on your system:
If you install Delphi 2005 using the installation launcher (install.exe in the root directory on Disk 1), the bootstrap utility runs automatically.
However, if you install Delphi 2005 using setup.exe in the "Install" directory on Disk 1, the bootstrap utility is bypassed. Borland recommends that you run the bootstrap utility before running setup.exe. Run prereqs.exe in the "Install" directory on Disk 1.
If the utility does not find the pre-requisite software on your system, it prompts you to install the software. Reply yes to the prompts to install the software required for Delphi 2005 to function properly. If you reply no, the Delphi 2005 installation will not continue if any of the pre- requisites are not found.
TopThe product is installed only once, by any licensed user with Administrator privileges, and is immediately available to all licensed users of the same machine. It is also available to any new licensed users you may add later.
You will be prompted to reboot your system at the end of the Delphi 2005 installation if you have chosen to install Internet Explorer 6.0 SP1 from the bootstrap utility (prereqs.exe) or MDAC 2.8 from the Delphi 2005 setup.
If the drive containing the folder specified in your TEMP environment variable is low on space, the Installer may halt with an error message noting the shortage. If this occurs, you'll need to assign your TEMP variable to a folder on a drive with more disk space, then rerun the installation.
Duplicate copies of assemblies installed in the GAC are provided in the <CommonFilesFolder>\Borland Shared\BDS\Shared Assemblies\3.0 directory. If C:\ is your Windows drive, the default <CommonFilesFolder> is C:\Program Files\Common Files\.
The assemblies in the GAC can be used to test deployment. The duplicate copy of the assemblies in the above mentioned directory can be used for development purposes.
Delphi 2005 stores assembly and Tool Palette configuration information in the file ApplicationSettings.xml, located in the user's home directory at "Documents and Settings\<username>\Local Settings\Application Data\Borland\BDS\3.0."
This file is not deleted during an uninstall and might cause assembly version errors in the IDE if you install another edition of Delphi 2005 (for example, Enterprise or Architect) on the same machine. To avoid this problem, delete ApplicationSettings.xml BEFORE installing another product edition.
Setup will generate BdpDataSources.xml and bdpConnections.xml depending upon the providers you choose during installation. If you choose the "Complete" setup type, all providers will be installed. At the end of the installation, setup will prompt you to overwrite or merge the bdpConnections.xml file if it exists in the destination directory. If you choose No for this prompt, the existing bdpConnections.xml file will be merged with the file being installed. If you choose Yes, setup will replace the existing bdpConnections.xml file with the new file. By default, the file is located at C:\Program Files\Borland\BDS\3.0\Bin.
TopProvides over one hundred grid, reporting, charting, data, user-interface, and e-Commerce components for .NET and ASP.NET.
A .NET obfuscation tool that assists in protecting intellectual property by making it difficult to reverse engineer managed code applications and assemblies.
Package
not found errors and Assembly not found errors. This
will automatically remove the correct assembly or package entries from
the registry and should prevent these errors when starting Delphi 2005.
This is the highly recommended option than the options outlined below
which involves editing the registry. Note: Read the WARNING at the end of this file before editing your system registry.
If you have BDE installed from any earlier version of Delphi or C++Builder Architect or Enterprise Edition that co-exists with Delphi 2005 Architect or Enterprise Editions, Borland strongly recommends that you perform a back up of the idapi32.cfg file in your BDE directory (by default C:\Program Files\Common Files\Borland Shared\BDE) before uninstalling Delphi 2005. The Delphi 2005 uninstallation removes some BDE files including idapi32.cfg and this causes all pre- configured BDE aliases to be removed after uninstallation. If you have performed a back up of idapi32.cfg, then you can restore the BDE aliases by renaming the back up copy to idapi32.cfg after Delphi 2005 uninstallation. You may also have to repair the earlier version of the Delphi 2005 or C++Builder product by using Add/Remove Programs to restore the other missing BDE files.
To uninstall the product, the Administrator who initially installed the product must open the Control Panel, select Add or Remove Programs, select Borland Delphi 2005 Architect Edition and click the Remove button. After uninstalling, in order to remove user-specific data from the Windows registry, all non- Administrator users of the product must log in and delete the following registry key:
HKEY_CURRENT_USER\Software\Borland\BDS\3.0
WARNING: Registry edits are performed at your own risk. This document and other documentation that accompanies this product describe how to edit your Windows registry. In most cases, Borland recommends that you use the Microsoft Regedit tool to perform editing. Whatever tool you use, however, you should, before making any edits, make backups of your registry and thoroughly familiarize yourself with the editing tool and the registry editing process. The registry is a critical component of your operating system, and any mistakes made while editing it can cause your machine to stop functioning.Top
Copyright (c) 2004 Borland Software Corporation.
All rights reserved.