TARGETDIR Property pls help

Davide

unread,

Sep 19, 2002, 11:39:37 AM9/19/02

to

Hi to all, help will be appreciated, i've set the
TARGETDIR with a Custom Action:

Property Table
PRIMARYFOLDER TARGETDIR

CUSTOM ACTION TABLE
DIR_CA_TARGETDIR 51 TARGETDIR [FSDIR][WindowsVolume]
MYPATH\XXXX

NOW the problem is the property [FSDIR] is set by App
Search, first look in registry then scan hard disk for a
file, i want to if the [FSDIR] find nothing it sets the
root dir like [WindowsVolume], if [FSDIR] is found then
exclude [WindowsVolume], how to manage that?

As in example above the problem is if [FSDIR] is found
then there is a messed up with [WindowsVolume]. And this
error appear Error 1606. Could not access network
location MYPATH\XXXX

Please help!

Michael Sanford

unread,

Sep 19, 2002, 9:25:20 PM9/19/02

to

AFAIK, AppSearch only sets the value of the property specified if a match is
made. That being the case, initialize FSDIR to [WindowsVolume] before your
AppSearch runs. If the search succeeds, it will have the new value,
otherwise it will still contain [WindowsVolume].

"Davide" <cut...@tin.it> wrote in message
news:2ba101c25ff2$c2bbd810$37ef2ecf@TKMSFTNGXA13...

Davide

unread,

Sep 20, 2002, 9:21:17 AM9/20/02

to

How to do that?

>.
>

Michael Sanford

unread,

Sep 20, 2002, 4:00:40 PM9/20/02

to

1. Create an AppSearch to locate the file. Name the Signature "SIG1" and
the property "FSDIR_FILE"
2. Create another AppSearch. This time don't add the file info. Just add
a row to AppSearch with "SIG2" for the Signature and "FSDIR" for the
property. Add a row to DrLocator with "SIG1" in the Signature column and
"SIG1" in the Parent column.
3. Add a Custom Action (51) BEFORE AppSearch to set "FSDIR" to
"[WindowsVolume]"
4. Add a Custom Action (51) AFTER AppSearch to set "TARGETDIR" to "[FSDIR]"

That's it!

I admit it may be a little confusing at first, but once you get the hang of
it....

Basically Here is what happens

1. FSDIR is set to "C:\" (WindowsVolume)
2. AppSearch runs and tries to locate your file.
If it is found, it sets FSDIR_1 to the fullpath of the file.
If it is not found the property FSDIR_1 is = "".
3. The second AppSearch sets FSDIR to the parent folder of FSDIR_1
(Unless FSDIR_1 is empty, in which case FSDIR is left unchanged...)
4. TARGETDIR is the set to the value of FSDIR.

Note that you could elimnate FSDIR and use TARGETDIR in it's place directly,
thus simplifying the process a little...

"Davide" <cut...@tin.it> wrote in message

news:39a401c260a8$9a3063f0$36ef2ecf@tkmsftngxa12...

Davide

unread,

Sep 21, 2002, 6:13:16 AM9/21/02

to

Tnx for the explanation, will try but there is anothor
question, how two separate the two Apps Search? I have in
the main property page this line APPS_TEST | 1, then in
InstallUISequence
Apps Search | APPS_TEST
in Apps Serach table:
FSDIR | Appfolder <--this look in Drlocator
FSDIR | Appreg <--this look in Reglocator

Now the problem is that the two search will start one
after the other, how i can separate this two to look in
Regloc and if the FSDIR property is set then don't
execute the second search.

Bye and tnx for your help.

>.
>

Michael Sanford

unread,

Sep 21, 2002, 7:54:56 AM9/21/02

to

Not sure I completely understood, but Searches execute in this order:
Component
Registry
INI
Directory

If an entry with the same signature exists if the RegLocator table, then the
registry will be searched first and processing will stop if a match is made.
If not it continues on down the line. So, make AppFolder and AppReg have
the same name.

"Davide" <cut...@tin.it> wrote in message

news:4d7f01c26157$803cc330$35ef2ecf@TKMSFTNGXA11...