At 02:05 PM 7/02/2005 +0000, you wrote:

>You say to set up
>the "environment path variables". Could you be more specific. In the
>Delphi Options, Library-Win32 there is a Library Path, a Browsing
>Path, and four other paths. Which path, or paths, do you mean?

You can open the BPG file and set them in Project > Options... (BPG =
Borland Project Group). Then they *should* be use for all of the
packages...though with some editions of Delphi it can be hit or miss, which
is why I always use global settings.

Alternatively, you can set them at the global level in Tools > Environment,
if you're not regularly installing other packages - just as long as you
remember to change the output paths when you do install sthg else.

The Environment library path has to be able to find everything when you use
the components, so you need to put the output paths in there as well as in
the (global or project level) individual fields. The system is designed to
read paths outward from package level through project level through
environment level. It uses the first path found for each path it searches
for; if it doesn't find entries anywhere, it uses the Delphi defaults or,
ultimately, the system defaults (system32 for some stuff, current directory
for others).

As I commented earlier, the new installer depends on having an orderly
global path system set up. If the global settings are set up for some
weird locations (as the installers for some VS plug-ins apparently do) and
the locations are not in the global library path, then the results are
going to be weird too. I guess it's a given for installers that
programmers keep their environment in a condition where every compile
delivers files to predictable places. In reality it's more likely to be a
mixture of conditions: left-overs from installing other stuff, forgotten
preferences, neglect, ignorance, blah, blah, blah.

Helen