PDA

View Full Version : Finding a File



NewsArchive
11-13-1997, 01:00 AM
I have a program that uses the Acrobat Reader. If I use express
extensions to wrap the installation of the reader program with my
program's install, it locks up. As a fall back, I am requiring a
separate install and asking the user for the Reader program location.

Is there an easy way to search the target computer for the existence of
the Reader program. I'm told that there are no registry entries for it.
I have considered a dll to search for the file, but don't want to write
one if there is something out there or an easier way to do it.

Any suggestions?????

Jeff McDonald

NewsArchive
08-10-2000, 12:00 AM
Mike,

Thanks for the response. I apparently forgot to mention that using a script
is not an option in this case, my hands are tied on this one. So spliting
or truncating the contents of MYPROP is unavailable to me via that mechanism
(I wish it were tho). Basically, I retrieve MYPROP's contents (containing
the full file spec) from the registry (successfully) and need to find the
existence of that file. I know the Signature table even allows you to
specify what min. and/or max. version is to be found. It seems incredulous
that given a full file spec you cannot (w/o resorting to scripts or a kluge)
search for said file using the Signature/DrLocator table mechanism, as
finding files and/or directories is what it's intended use is.

--
John C. Bowman
Software Systems Engineer
Nicolet Instrument Corp.


"Mike Berger" <mberger@veritas.com> wrote in message
news:3991ac09.0@208.30.171.38...
> Create a custom action to read the property and output
> two properties one with the path and the other with the file spec.
>
> -Mike
>
> "John Bowman" <bowman@nicolet.com> wrote in message
> news:39918ec1.0@208.30.171.38...
> > Hi,
> >
> > I've been scouring the NG and MSI help regarding using DrLocator,
> AppSearch,
> > Signature tables, etc. and cannot seem to find and make work the simple
> > finding of a file. I've got a public property that is known to contain
> the
> > FULL FILE SPEC (not just the path, and this cannot be changed).
> > Specifically, how do I search for the presence of this file? The MSI
help
> > only seems to address the cases where you have a path, or just the
> filename,
> > but not the full filespec. Assuming I have MYPROP containing the
desired
> > filespec, what exactly do I need to put into the respective tables to
get
> > this to work??? Nothing I've tried seems to get me there.
> >
> > TIA,
> >
> > --
> > John C. Bowman
> > Software Systems Engineer
> > Nicolet Instrument Corp.
> >
> >
> >
> >
>
>

NewsArchive
08-10-2000, 12:00 AM
Try setting the min version number to one below the version you are
looking for. I have found that it only finds numbers > min, not >=
like the docs describe. (Took me a whole day to figure that out.)

Sean

John Bowman wrote:
>
> Mike,
>
> Thanks for the response. I apparently forgot to mention that using a script
> is not an option in this case, my hands are tied on this one. So spliting
> or truncating the contents of MYPROP is unavailable to me via that mechanism
> (I wish it were tho). Basically, I retrieve MYPROP's contents (containing
> the full file spec) from the registry (successfully) and need to find the
> existence of that file. I know the Signature table even allows you to
> specify what min. and/or max. version is to be found. It seems incredulous
> that given a full file spec you cannot (w/o resorting to scripts or a kluge)
> search for said file using the Signature/DrLocator table mechanism, as
> finding files and/or directories is what it's intended use is.
>
> --
> John C. Bowman
> Software Systems Engineer
> Nicolet Instrument Corp.
>
> "Mike Berger" <mberger@veritas.com> wrote in message
> news:3991ac09.0@208.30.171.38...
> > Create a custom action to read the property and output
> > two properties one with the path and the other with the file spec.
> >
> > -Mike
> >
> > "John Bowman" <bowman@nicolet.com> wrote in message
> > news:39918ec1.0@208.30.171.38...
> > > Hi,
> > >
> > > I've been scouring the NG and MSI help regarding using DrLocator,
> > AppSearch,
> > > Signature tables, etc. and cannot seem to find and make work the simple
> > > finding of a file. I've got a public property that is known to contain
> > the
> > > FULL FILE SPEC (not just the path, and this cannot be changed).
> > > Specifically, how do I search for the presence of this file? The MSI
> help
> > > only seems to address the cases where you have a path, or just the
> > filename,
> > > but not the full filespec. Assuming I have MYPROP containing the
> desired
> > > filespec, what exactly do I need to put into the respective tables to
> get
> > > this to work??? Nothing I've tried seems to get me there.
> > >
> > > TIA,
> > >
> > > --
> > > John C. Bowman
> > > Software Systems Engineer
> > > Nicolet Instrument Corp.
> > >
> > >
> > >
> > >
> >
> >

NewsArchive
08-10-2000, 12:00 AM
Sean,

Thanks for tip, but alas that didn't work either. Any more ideas?

--
John C. Bowman
Software Systems Engineer
Nicolet Instrument Corp.


"Sean Lambert" <seanl@sea.checkpoint.com> wrote in message
news:3992E678.BD10B0AC@sea.checkpoint.com...
> Try setting the min version number to one below the version you are
> looking for. I have found that it only finds numbers > min, not >=
> like the docs describe. (Took me a whole day to figure that out.)
>
> Sean
>
> John Bowman wrote:
> >
> > Mike,
> >
> > Thanks for the response. I apparently forgot to mention that using a
script
> > is not an option in this case, my hands are tied on this one. So
spliting
> > or truncating the contents of MYPROP is unavailable to me via that
mechanism
> > (I wish it were tho). Basically, I retrieve MYPROP's contents
(containing
> > the full file spec) from the registry (successfully) and need to find
the
> > existence of that file. I know the Signature table even allows you to
> > specify what min. and/or max. version is to be found. It seems
incredulous
> > that given a full file spec you cannot (w/o resorting to scripts or a
kluge)
> > search for said file using the Signature/DrLocator table mechanism, as
> > finding files and/or directories is what it's intended use is.
> >
> > --
> > John C. Bowman
> > Software Systems Engineer
> > Nicolet Instrument Corp.
> >
> > "Mike Berger" <mberger@veritas.com> wrote in message
> > news:3991ac09.0@208.30.171.38...
> > > Create a custom action to read the property and output
> > > two properties one with the path and the other with the file spec.
> > >
> > > -Mike
> > >
> > > "John Bowman" <bowman@nicolet.com> wrote in message
> > > news:39918ec1.0@208.30.171.38...
> > > > Hi,
> > > >
> > > > I've been scouring the NG and MSI help regarding using DrLocator,
> > > AppSearch,
> > > > Signature tables, etc. and cannot seem to find and make work the
simple
> > > > finding of a file. I've got a public property that is known to
contain
> > > the
> > > > FULL FILE SPEC (not just the path, and this cannot be changed).
> > > > Specifically, how do I search for the presence of this file? The
MSI
> > help
> > > > only seems to address the cases where you have a path, or just the
> > > filename,
> > > > but not the full filespec. Assuming I have MYPROP containing the
> > desired
> > > > filespec, what exactly do I need to put into the respective tables
to
> > get
> > > > this to work??? Nothing I've tried seems to get me there.
> > > >
> > > > TIA,
> > > >
> > > > --
> > > > John C. Bowman
> > > > Software Systems Engineer
> > > > Nicolet Instrument Corp.
> > > >
> > > >
> > > >
> > > >
> > >
> > >

NewsArchive
08-10-2000, 12:00 AM
I think you're going to have to knuckle down and kludge it with a CA.
It is, after all, Install Shield that we are talking about. =]

Make sure you have the basics down first, though. It is easy to make
a small error that is hard to detect. When I forts tried it, I
couldn't get it to work. I started over, just searching the entire
drive for the file of any version, then narrowed the search
constraints one at a time and it worked. I have no idea what I did
wrong when I tried to do it all at once.

Maybe you should try puting the filename only in a temporary Property
and make sure you can at least find that. Then try putting in the
full path, then hook it up to read from the registry instead of the
temp property.

Then at least you'll know for sure what the problem is.

Good luck,
Sean


John Bowman wrote:
>
> Sean,
>
> Thanks for tip, but alas that didn't work either. Any more ideas?
>
> --
> John C. Bowman
> Software Systems Engineer
> Nicolet Instrument Corp.
>
> "Sean Lambert" <seanl@sea.checkpoint.com> wrote in message
> news:3992E678.BD10B0AC@sea.checkpoint.com...
> > Try setting the min version number to one below the version you are
> > looking for. I have found that it only finds numbers > min, not >=
> > like the docs describe. (Took me a whole day to figure that out.)
> >
> > Sean
> >
> > John Bowman wrote:
> > >
> > > Mike,
> > >
> > > Thanks for the response. I apparently forgot to mention that using a
> script
> > > is not an option in this case, my hands are tied on this one. So
> spliting
> > > or truncating the contents of MYPROP is unavailable to me via that
> mechanism
> > > (I wish it were tho). Basically, I retrieve MYPROP's contents
> (containing
> > > the full file spec) from the registry (successfully) and need to find
> the
> > > existence of that file. I know the Signature table even allows you to
> > > specify what min. and/or max. version is to be found. It seems
> incredulous
> > > that given a full file spec you cannot (w/o resorting to scripts or a
> kluge)
> > > search for said file using the Signature/DrLocator table mechanism, as
> > > finding files and/or directories is what it's intended use is.
> > >
> > > --
> > > John C. Bowman
> > > Software Systems Engineer
> > > Nicolet Instrument Corp.
> > >
> > > "Mike Berger" <mberger@veritas.com> wrote in message
> > > news:3991ac09.0@208.30.171.38...
> > > > Create a custom action to read the property and output
> > > > two properties one with the path and the other with the file spec.
> > > >
> > > > -Mike
> > > >
> > > > "John Bowman" <bowman@nicolet.com> wrote in message
> > > > news:39918ec1.0@208.30.171.38...
> > > > > Hi,
> > > > >
> > > > > I've been scouring the NG and MSI help regarding using DrLocator,
> > > > AppSearch,
> > > > > Signature tables, etc. and cannot seem to find and make work the
> simple
> > > > > finding of a file. I've got a public property that is known to
> contain
> > > > the
> > > > > FULL FILE SPEC (not just the path, and this cannot be changed).
> > > > > Specifically, how do I search for the presence of this file? The
> MSI
> > > help
> > > > > only seems to address the cases where you have a path, or just the
> > > > filename,
> > > > > but not the full filespec. Assuming I have MYPROP containing the
> > > desired
> > > > > filespec, what exactly do I need to put into the respective tables
> to
> > > get
> > > > > this to work??? Nothing I've tried seems to get me there.
> > > > >
> > > > > TIA,
> > > > >
> > > > > --
> > > > > John C. Bowman
> > > > > Software Systems Engineer
> > > > > Nicolet Instrument Corp.
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >

NewsArchive
08-11-2000, 12:00 AM
Sean,

Ground up approach, eh? I've other stuff start working that way, I'll give
it a shot.

BTW, this is making my knuckles get raw <g>!

--
John C. Bowman
Software Systems Engineer
Nicolet Instrument Corp.


"Sean Lambert" <seanl@sea.checkpoint.com> wrote in message
news:39930BE8.F72B5CBC@sea.checkpoint.com...
> I think you're going to have to knuckle down and kludge it with a CA.
> It is, after all, Install Shield that we are talking about. =]
>
> Make sure you have the basics down first, though. It is easy to make
> a small error that is hard to detect. When I forts tried it, I
> couldn't get it to work. I started over, just searching the entire
> drive for the file of any version, then narrowed the search
> constraints one at a time and it worked. I have no idea what I did
> wrong when I tried to do it all at once.
>
> Maybe you should try puting the filename only in a temporary Property
> and make sure you can at least find that. Then try putting in the
> full path, then hook it up to read from the registry instead of the
> temp property.
>
> Then at least you'll know for sure what the problem is.
>
> Good luck,
> Sean
>
>
> John Bowman wrote:
> >
> > Sean,
> >
> > Thanks for tip, but alas that didn't work either. Any more ideas?
> >
> > --
> > John C. Bowman
> > Software Systems Engineer
> > Nicolet Instrument Corp.
> >
> > "Sean Lambert" <seanl@sea.checkpoint.com> wrote in message
> > news:3992E678.BD10B0AC@sea.checkpoint.com...
> > > Try setting the min version number to one below the version you are
> > > looking for. I have found that it only finds numbers > min, not >=
> > > like the docs describe. (Took me a whole day to figure that out.)
> > >
> > > Sean
> > >
> > > John Bowman wrote:
> > > >
> > > > Mike,
> > > >
> > > > Thanks for the response. I apparently forgot to mention that using
a
> > script
> > > > is not an option in this case, my hands are tied on this one. So
> > spliting
> > > > or truncating the contents of MYPROP is unavailable to me via that
> > mechanism
> > > > (I wish it were tho). Basically, I retrieve MYPROP's contents
> > (containing
> > > > the full file spec) from the registry (successfully) and need to
find
> > the
> > > > existence of that file. I know the Signature table even allows you
to
> > > > specify what min. and/or max. version is to be found. It seems
> > incredulous
> > > > that given a full file spec you cannot (w/o resorting to scripts or
a
> > kluge)
> > > > search for said file using the Signature/DrLocator table mechanism,
as
> > > > finding files and/or directories is what it's intended use is.
> > > >
> > > > --
> > > > John C. Bowman
> > > > Software Systems Engineer
> > > > Nicolet Instrument Corp.
> > > >
> > > > "Mike Berger" <mberger@veritas.com> wrote in message
> > > > news:3991ac09.0@208.30.171.38...
> > > > > Create a custom action to read the property and output
> > > > > two properties one with the path and the other with the file spec.
> > > > >
> > > > > -Mike
> > > > >
> > > > > "John Bowman" <bowman@nicolet.com> wrote in message
> > > > > news:39918ec1.0@208.30.171.38...
> > > > > > Hi,
> > > > > >
> > > > > > I've been scouring the NG and MSI help regarding using
DrLocator,
> > > > > AppSearch,
> > > > > > Signature tables, etc. and cannot seem to find and make work the
> > simple
> > > > > > finding of a file. I've got a public property that is known to
> > contain
> > > > > the
> > > > > > FULL FILE SPEC (not just the path, and this cannot be changed).
> > > > > > Specifically, how do I search for the presence of this file?
The
> > MSI
> > > > help
> > > > > > only seems to address the cases where you have a path, or just
the
> > > > > filename,
> > > > > > but not the full filespec. Assuming I have MYPROP containing
the
> > > > desired
> > > > > > filespec, what exactly do I need to put into the respective
tables
> > to
> > > > get
> > > > > > this to work??? Nothing I've tried seems to get me there.
> > > > > >
> > > > > > TIA,
> > > > > >
> > > > > > --
> > > > > > John C. Bowman
> > > > > > Software Systems Engineer
> > > > > > Nicolet Instrument Corp.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >

NewsArchive
08-11-2000, 12:00 AM
> BTW, this is making my knuckles get raw <g>!

That's odd, I have been getting big red marks on my forhead...

NewsArchive
08-17-2000, 12:00 AM
Well,

So far, no luck. Anymore ideas? Can it really be that hard to retrieve a
full file spec path value from the registry and then use the AppSearch /
DrLocator / Signature tables to implement testing the version of the file
specified??

--
John C. Bowman
Software Systems Engineer
Nicolet Instrument Corp.


"Sean Lambert" <seanl@sea.checkpoint.com> wrote in message
news:399449EA.126A4809@sea.checkpoint.com...
> > BTW, this is making my knuckles get raw <g>!
>
> That's odd, I have been getting big red marks on my forhead...