Indigo Rose Software

Professional Software Development Tools

 
+ Reply to Thread
Results 1 to 6 of 6
  1. #1
    Join Date
    Mar 2007
    Posts
    26

    Thumbs down Problems with installing TTF fonts

    We have an installer create with version 8.1.1008.0 of Seutp Factory and all installers work great, except those that have a .TTF font file. We have ticked the Register As TrueType Font checkbox, and the autoname is Number Plate (TrueType).

    However first installation on a machine is fine. But subsequent installations cannot overwrite the "Number Plate.ttf" font in the C:\Windows\Fonts directory even though this font is not even being used as the application is closed.

    How can we force an installation of a font please without errors occuring such as Cannot Write File etc. giving users an annoying Retry, Abort or Cancel option for the font during installation.

    Any help much appreciated.

  2. #2
    Join Date
    Feb 2001
    Location
    Indigo Rose Software
    Posts
    2,728
    For direct support from IR you can submit a ticket from the customer portal.

    I'm not sure why the font you installed can't be overwritten. Was the original setup running with administrative privileges? Are the newer setups as well? Are you sure no other applications are using the font? Can you overwrite it "manually" in Windows? etc.
    --[[ Indigo Rose Software Developer ]]

  3. #3
    Join Date
    Mar 2007
    Posts
    26

    Thumbs down

    Quote Originally Posted by Lorne View Post
    For direct support from IR you can submit a ticket from the customer portal.

    I'm not sure why the font you installed can't be overwritten. Was the original setup running with administrative privileges? Are the newer setups as well? Are you sure no other applications are using the font? Can you overwrite it "manually" in Windows? etc.
    Hi

    We have submitted a ticket, but thought we'd also see what the community think as an urgent problem :(

    Our installers do have require administrator, the problem occurs when we launch the installer from our application if it detects an update is available. Our application does not need or have administrator priveleges but the installer is set to use admin privs.

    So when an update is required we force close our application after first launching the installer.

    Then it gets to installing the font, and says it cannot overwrite and gives IGNORE, RETRY or CANCEL options

  4. #4
    Join Date
    Jul 2001
    Location
    Harrisburg, PA , USA
    Posts
    114
    Quote Originally Posted by tmancey View Post
    Hi

    We have submitted a ticket, but thought we'd also see what the community think as an urgent problem :(
    Originally Posted by Lorne
    For direct support from IR you can submit a ticket from the customer portal.

    I'm not sure why the font you installed can't be overwritten. Was the original setup running with administrative privileges? Are the newer setups as well? Are you sure no other applications are using the font? Can you overwrite it "manually" in Windows? etc.
    I say I must agree with tmancey on this one. I recently submitted a ticket to IR and only got one IR staffer looking at my project while in the forums several people can share their knoledge.

    Anyway I still love IR but the problem I submitted still isn't resolved I just wrote a band aid for the script.

  5. #5
    Join Date
    Jul 2001
    Location
    Indigo Rose Software
    Posts
    1,834
    You mentioned that you are runnning the installer from your application after the font has initially been installed. Does it also occur if you run the setup outside of your application at that point? I'm just wondering if it is related to how you are running the setup, for example in Setup Factory terms, Shell.Execute versus File.Run, but in your case the corresponding API calls such as ShellExecute versus CreateProcess. Just want to eliminate that from the equation.
    Darryl
    Indigo Rose Corporation

    Product Guides: AMS80 | SUF9 | TU30 | VP30 |MSIFACT |DeltaMAX

  6. #6
    Join Date
    Mar 2007
    Posts
    26
    Quote Originally Posted by Darryl View Post
    You mentioned that you are runnning the installer from your application after the font has initially been installed. Does it also occur if you run the setup outside of your application at that point? I'm just wondering if it is related to how you are running the setup, for example in Setup Factory terms, Shell.Execute versus File.Run, but in your case the corresponding API calls such as ShellExecute versus CreateProcess. Just want to eliminate that from the equation.
    It works fine from outside of our application. We use ShellExecute from within our application and once we call this we then close our application automatically.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts