LMDVCL-Install - Revision history

Rafael: /* After Installation: Package XXXXYYYY.dpl not found */

2022-06-05T19:54:24Z

After Installation: Package XXXXYYYY.dpl not found

← Older revision		Revision as of 21:54, 5 June 2022
Line 28:		Line 28:
	[[file:install2.png]]<br>		[[file:install2.png]]<br>
	Usually the installer tries to install packages into the default package output path and everything should be fine. If not, possible causes could be:		Usually the installer tries to install packages into the default package output path and everything should be fine. If not, possible causes could be:
	* installer was not able to determine your default BPL path (check your configuration settings - package ouput directory. See screenshot below). If there is valid path, installer should normally detect this path. You can certainly copy all packages manually to this folder and re-add them in Install Components dialog. <b>Hint:</b> If you want to re-add ppackages manually from a new folder, starting IDE can be a pain (error message for each designtime package which was not found. In this case remove LMD package entries from registries beforehand. E.g. for Delphi 7 registry path is <code>HEY_CURRENT_USER\Software\Borland\Delphi\7.0\Known Packages </code>.<br>		* installer was not able to determine your default BPL path (check your configuration settings - package ouput directory. See screenshot below). If there is valid path, installer should normally detect this path. You can certainly copy all packages manually to this folder and re-add them in Install Components dialog. <b>Hint:</b> If you want to re-add ppackages manually from a new folder, starting IDE can be a pain (error message for each designtime package which was not found. In this case remove LMD package entries from registries beforehand. E.g. for
			* Delphi 7 registry path is <code>HEY_CURRENT_USER\Software\Borland\Delphi\7.0\Known Packages </code>
			* Delphi 11.X registry path is <code>HKEY_CURRENT_USER\Software\Embarcadero\BDS\22.0\Known Packages</code>
	[[file:install1.png]]<br>		[[file:install1.png]]<br>
	* you used a custom path for packages which is <b>not</b> a system path: But then you HAVE to make sure that custom path is a system path. After adding this path to PATH variable, packages will be loaded without problems (if you need instructions for adding a custom path to PATH variable, check following [http://www.computerhope.com/issues/ch000549.htm page]).		* you used a custom path for packages which is <b>not</b> a system path: But then you HAVE to make sure that custom path is a system path. After adding this path to PATH variable, packages will be loaded without problems (if you need instructions for adding a custom path to PATH variable, check following [http://www.computerhope.com/issues/ch000549.htm page]).

Rafael at 23:20, 11 March 2021

2021-03-11T23:20:15Z

← Older revision		Revision as of 01:20, 12 March 2021
Line 13:		Line 13:

	Please note:		Please note:
	* No component or package was removed. ~~But some~~ packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)		* No component or package was removed. Certain packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)
	* If you still receive message about missing TextPack packages (like screenshotnbelow) after start of IDE, simply enter the "Install Components..."-dialog and remove both TextPack entries.		* If you still receive message about missing TextPack packages (like screenshotnbelow) after start of IDE, simply enter the "Install Components..."-dialog and remove both TextPack entries.
	[[file:Missingtextpack.png]]<br>		[[file:Missingtextpack.png]]<br>

Rafael at 23:19, 11 March 2021

2021-03-11T23:19:39Z

← Older revision		Revision as of 01:19, 12 March 2021
Line 14:		Line 14:
	Please note:		Please note:
	* No component or package was removed. But some packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)		* No component or package was removed. But some packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)
	* If you still receive message about missing TextPack packages after start of IDE, simply enter the "Install Components..."-dialog and remove ~~the~~ both TextPack entries.		* If you still receive message about missing TextPack packages (like screenshotnbelow) after start of IDE, simply enter the "Install Components..."-dialog and remove both TextPack entries.
	[[file:Missingtextpack.png]]<br>		[[file:Missingtextpack.png]]<br>

Rafael at 23:18, 11 March 2021

2021-03-11T23:18:23Z

← Older revision		Revision as of 01:18, 12 March 2021
Line 15:		Line 15:
	* No component or package was removed. But some packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)		* No component or package was removed. But some packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)
	* If you still receive message about missing TextPack packages after start of IDE, simply enter the "Install Components..."-dialog and remove the both TextPack entries.		* If you still receive message about missing TextPack packages after start of IDE, simply enter the "Install Components..."-dialog and remove the both TextPack entries.
			[[file:Missingtextpack.png]]<br>

	= Installation Target (Package Installation Options) =		= Installation Target (Package Installation Options) =

Rafael at 23:11, 11 March 2021

2021-03-11T23:11:49Z

← Older revision		Revision as of 01:11, 12 March 2021
Line 11:		Line 11:
	* No LMD packages are shown in "Install Components..."-dialog		* No LMD packages are shown in "Install Components..."-dialog
	* No LMD packages (file pattern is e.g. lmd.bpl) are located in your default BPL path (or your preferred package path)		* No LMD packages (file pattern is e.g. lmd.bpl) are located in your default BPL path (or your preferred package path)

			Please note:
			* No component or package was removed. But some packages like e.g. '''LMD TextPack''' were moved to the new extended legacy package (which need to be explicity enabled during installation, so that no new customer uses them)
			* If you still receive message about missing TextPack packages after start of IDE, simply enter the "Install Components..."-dialog and remove the both TextPack entries.

	= Installation Target (Package Installation Options) =		= Installation Target (Package Installation Options) =

Rafael at 20:50, 7 December 2020

2020-12-07T20:50:14Z

← Older revision		Revision as of 22:50, 7 December 2020
Line 3:		Line 3:
	This section describes new features of LMD 2014 and higher installers regarding package installation.<br>		This section describes new features of LMD 2014 and higher installers regarding package installation.<br>
	For common problems refer to [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation troubleshooting section].		For common problems refer to [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation troubleshooting section].

			= Updating to LMD 2021 platform or higher =
			It is required to uninstall any previously installed packages into the same IDE when precompiled installers are used.
			If an existing installation is overwritten with new packages, it is very likely that various version mix up errors are seen when IDE is started.
			To avoid this, make sure that:
			* Uninstaller of the previous LMD installation was executed
			* No LMD packages are shown in "Install Components..."-dialog
			* No LMD packages (file pattern is e.g. lmd.bpl) are located in your default BPL path (or your preferred package path)

	= Installation Target (Package Installation Options) =		= Installation Target (Package Installation Options) =

Rafael at 23:38, 6 February 2017

2017-02-06T23:38:10Z

← Older revision		Revision as of 01:38, 7 February 2017
Line 2:		Line 2:

	This section describes new features of LMD 2014 and higher installers regarding package installation.<br>		This section describes new features of LMD 2014 and higher installers regarding package installation.<br>
	For common problems refer to [[http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation troubleshooting section]].		For common problems refer to [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation troubleshooting section].

	= Installation Target (Package Installation Options) =		= Installation Target (Package Installation Options) =

Rafael at 17:14, 17 October 2015

2015-10-17T17:14:31Z

← Older revision		Revision as of 19:14, 17 October 2015
Line 1:		Line 1:
	{{Head-Overview}}		{{Head-Overview}}

	This section describes new features of LMD 2014 ~~installer~~ regarding package installation.		This section describes new features of LMD 2014 and higher installers regarding package installation.<br>
	For common problems refer to [[http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation troubleshooting section]].		For common problems refer to [[http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation troubleshooting section]].

Rafael at 19:43, 8 October 2013

2013-10-08T19:43:10Z

← Older revision		Revision as of 21:43, 8 October 2013
Line 8:		Line 8:

	* <b>Default BPL output dirctory</b>. When selecting option please check whether correct default BPL output path was determined. If path contains IDE macros, you can check detected path by pressing the "Check Settings" button.		* <b>Default BPL output dirctory</b>. When selecting option please check whether correct default BPL output path was determined. If path contains IDE macros, you can check detected path by pressing the "Check Settings" button.
	* <b>Custom Path</b>. Select this option when you prefer to install packages into a common path. Please make sure that this path is a <b>system path</b>.		* <b>Custom Path</b>. Select this option when you prefer to install packages into a common path. Please make sure that this path is a <b>system path</b>.<br><br>

	= After Installation: Package XXXXYYYY.dpl not found =		= After Installation: Package XXXXYYYY.dpl not found =
	This issue is also covered in another [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation section]~~, but because~~ a ~~very~~ large number of tickets is raised for ~~it we want to point to the cause which is responsible in almost all cases for the~~ "Package not found" ~~problem~~ after installation.<br>		This issue is also covered in another [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation section]. However a large number of tickets are raised for this problem ("Package not found" after installation), which usually have all the same source of problem.<br>
	As mentioned in previous section, runtime packages <u>have</u> to be installed in a <b>system path</b>. This is also explicitely mentioned in installer:		As mentioned in previous section, runtime packages <u>have</u> to be installed in a <b>system path</b>. This is also explicitely mentioned in installer:
	[[file:install2.png]]<br>		[[file:install2.png]]<br>

Rafael: /* After Installation: Package XXXXYYYY.dpl not found */

2013-10-08T19:41:24Z

After Installation: Package XXXXYYYY.dpl not found

← Older revision		Revision as of 21:41, 8 October 2013
Line 13:		Line 13:
	This issue is also covered in another [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation section], but because a very large number of tickets is raised for it we want to point to the cause which is responsible in almost all cases for the "Package not found" problem after installation.<br>		This issue is also covered in another [http://wiki.lmd.de/index.php/LMD_VCL_-_General_FAQ#Installation section], but because a very large number of tickets is raised for it we want to point to the cause which is responsible in almost all cases for the "Package not found" problem after installation.<br>
	As mentioned in previous section, runtime packages <u>have</u> to be installed in a <b>system path</b>. This is also explicitely mentioned in installer:		As mentioned in previous section, runtime packages <u>have</u> to be installed in a <b>system path</b>. This is also explicitely mentioned in installer:
			[[file:install2.png]]<br>
	Usually the installer tries to install packages into the default package output path and everything should be fine. If not, possible causes could be:		Usually the installer tries to install packages into the default package output path and everything should be fine. If not, possible causes could be:
	* installer was not able to determine your default BPL path (check your configuration settings - package ouput directory. See screenshot below). If there is valid path, installer should normally detect this path. You can certainly copy all packages manually to this folder and re-add them in Install Components dialog.		* installer was not able to determine your default BPL path (check your configuration settings - package ouput directory. See screenshot below). If there is valid path, installer should normally detect this path. You can certainly copy all packages manually to this folder and re-add them in Install Components dialog. <b>Hint:</b> If you want to re-add ppackages manually from a new folder, starting IDE can be a pain (error message for each designtime package which was not found. In this case remove LMD package entries from registries beforehand. E.g. for Delphi 7 registry path is <code>HEY_CURRENT_USER\Software\Borland\Delphi\7.0\Known Packages </code>.<br>
	* you used a custom path for packages which is <b>not</b> a system path: But then you HAVE to make sure that custom path is a system path ~~(see screenshot 2)~~. After ~~you added~~ this path to PATH variable ~~you~~, will be ~~able to add packages~~ without problems (if you need instructions for ~~this~~, check following [http://www.computerhope.com/issues/ch000549.htm page]).		[[file:install1.png]]<br>
			* you used a custom path for packages which is <b>not</b> a system path: But then you HAVE to make sure that custom path is a system path. After adding this path to PATH variable, packages will be loaded without problems (if you need instructions for adding a custom path to PATH variable, check following [http://www.computerhope.com/issues/ch000549.htm page]).

	To make it short: Simply make sure that packages are installed into a system path. Otherwise runtime packages can not be found (this is a Delphi requirement) and installing designtime packages will fail.		To make it short: Simply make sure that packages are installed into a system path. Otherwise runtime packages can not be found (this is a Delphi requirement) and installing designtime packages will fail.

	[[Category:FAQ]] [[Category:Installation]]		[[Category:FAQ]] [[Category:Installation]]