Announcement

Collapse
No announcement yet.

Search For File option

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Search For File option

    Obviously I have done something wrong but not sure where.

    In Actions, Before Installing I have a set an action of "Search for File". Store result in %AIMSInstalled%, Default value is FALSE, Search for file AIMS*.EXE, Scope is Search Specific Directory (F:\AIMS) no recursion. Other scope options unticked.

    In F:\AIMS I have a number of files beginning with "AIMS" but don't care what they are called as only checking to see if system is installed. (F:\AIMS could exist but system not be installed unless files in there).

    In File Properties on CD-ROM tab, have an entry to install a file to F:\AIMS (overwrite if older or same) with condition of %AIMSInstalled% <> "FALSE".

    Now the way I see this is that %AIMSInstalled% should have picked up the path\files in F:\AIMS starting with AIMS and put into that variable. Then the condition should have said "OK, %AIMSInstalled% is not equal to the word 'FALSE' so let's install the file". But it does not. (There are no security implications as logged on as ADMIN on a Novell server). Other files without a condition install fine...

    HELP!

    Thanks

    John

  • #2
    Re: Search For File option

    Hi

    Try this:
    Default value is NOT FOUND
    in condition "%AIMSInstalled%" <> "NOT FOUND"

    Comment


    • #3
      Re: Search For File option

      I will have a go but any reason why this should make any difference other than FALSE may perhaps be a keyword in SUF6?

      Thanks

      John

      Comment


      • #4
        Re: Search For File option

        The FALSE is boolean value in SF6.

        Comment


        • #5
          Re: Search For File option

          Hi Laslie.

          What version are you using? There was a bug fixed in 6.0.1.0 that prevented run-time conditions from working properly when a variable was used.

          (The variable was being expanded too soon; we changed the code to expand variables within the expression parsing class a couple versions back, but when we removed the old calls that expanded the variables earlier, we missed one...unfortunately, none of our test cases caught it. We've made an effort to fix that as well. )
          --[[ Indigo Rose Software Developer ]]

          Comment


          • #6
            Re: Search For File option

            Lorne,

            This was my question originally. The EXE was built using 6.0.0.4 (I am now on 6.0.1.0) but has already been dispatched to various ships across the world. Not a major problem as the Captain's can manually copy the files from the CD but I will rebuild/test the project with the later version.

            Rgds

            John

            Comment


            • #7
              Re: Search For File option

              Ah, right you are John. Hello to you as well.

              It seems to me there was a workaround of sorts, but I don't remember off-hand what it is...and it's ultimately better to upgrade to 6.0.1.0 anyway.
              --[[ Indigo Rose Software Developer ]]

              Comment


              • #8
                Re: Search For File option

                Just to confirm that recompiling in 6.0.1.0 fixed the variable not being processed correctly.

                Thanks John

                Comment

                Working...
                X