Announcement

Collapse
No announcement yet.

Custom Runtime Module Problems

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

  • Custom Runtime Module Problems

    I have created a custom runtime module for LeadTools 12.1. It works fine; it is successfully configured by Setup Factory and I successfully add it's component files to a project via the "Runtime Support" feature. The project seems to build o.k., but when the setup exe is run on another machine, something strange happens. It appears as if none of the files added from the runtime module are extracted. In fact, the "logfile.txt" that is generated has all of the files as "Skipped" (in the "[Installing from Archive]" section). Does anyone know what is going on?

    Thanks!

    Sincerely,
    Terry Rasmussen

  • #2
    Re: Custom Runtime Module Problems

    Hi Terry,
    Sorry but I'm really not sure what the problem here is.

    Do the files already exist on the Test machine? Where are you installing the files to? Are they system files? What OS did you test this on?

    Perhaps you could e-mail me a copy of your project file and an installation log, so that I can see exactly what is happening. You can send your e-mail to: [email protected] along with a brief explanation of the problem.

    mark.
    MSI Factory The Next Generation Intelligent Setup Builder

    Comment


    • #3
      Re: Custom Runtime Module Problems

      Mark,

      Thank you for your reply. I will be emailing indigorose support with the requested files and information shortly.

      Sincerely,
      Terry Rasmussen

      Comment


      • #4
        Re: Custom Runtime Module Problems

        Hi Terry,

        I have just e-mailed you this information, but I will post it here for the other users:

        *****
        This problem arises because you used 64 as the OS condition in your RTConfig.INI file. 64 is what it should have been before support for Windows ME was added. Now if you want to select the "Any" OS condition you will have to use 128 instead.

        Here is an updated OS list:

        Windows 3.1=1
        Windows 95=2
        Windows 98=4
        Windows NT 3=8
        Windows NT 4=16
        Windows 2000=32
        Windows ME = 64

        I have tested this out on my system and everything appeared to work properly.
        *****

        Again, I apologize for the out of date documentation Terry, this will be fixed shortly.

        mark.

        [This message has been edited by Mark (edited 06-04-2001).]
        MSI Factory The Next Generation Intelligent Setup Builder

        Comment


        • #5
          Re: Custom Runtime Module Problems

          Mark,

          Thanks for looking into the problem; I will adjust any custom runtime modules I have created.

          Just as a suggestion, it might have helped if the logfile had listed "Skipped because of invalid OS" instead of just "Skipped".

          Thanks!

          Sincerely,
          Terry

          Comment

          Working...
          X