/build/static/layout/Breadcrumb_cap_w.png

Packaging Fiery Command Workstation 5.2

 

I was trying to package Fiery Command WorkStation 5.2 and i can see 2 shortcuts under 2 differnt folders and only one of them launches and the other gives a error message - 'AdobeFnt11.|st' can not be opened because either its damaged or not correctly decoded. And my system has Adobe installed on it, so can any one tell how to solve this issue?


0 Comments   [ + ] Show comments

Answers (3)

Posted by: dunnpy 12 years ago
Red Belt
2

Does it work correctly with a manual installation?

Try a 'gap capture' using your favourite lightweight snapshot tool (Picture Taker, InControl, InstallRite et al) by installing your MSI and then the vendor setup over the top.

That should identifiy anything missing in your MSI that you can then incorporate into your package.

Hope that helps,

Dunnpy


Comments:
  • I am having this issue with the manual install of the .exe itself. - shamu99 12 years ago
  • get the correct source... The package is as good as the source. - piyushnasa 12 years ago
Posted by: anonymous_9363 12 years ago
Red Belt
0

>I am having this issue with the manual install of the .exe itself.

Then it's the vendor's issue, not yours!

Posted by: shamu99 12 years ago
Fifth Degree Brown Belt
0

Thanks all. Has anyone got a chance to package it. I tried to capture, but the msi install gives a missing dll. And I dont get a silent switch when i do the exe /?

Please guide.

Thanks


Comments:
  • First find the extracted folders in the temp directory:"Common Utilities","EFI Command Workstation","Fiery User Software Install".

    Create a answer file with the command:
    EFI Command Workstation\setup.exe" -r
    and find the answer file in c:\windows folder.

    After the installation you need to extract the driver certificate with certmgr.msc
    The certificate "x-rite incorporated" expires in 2010 but works fine..

    Create a package that includeds all the extracted installations folders and the certificate.

    [1] Create a custom action to install the certificate in the right folder: *run before the setup.
    -------------------------
    Set WshShell = CreateObject("WScript.Shell")
    WshShell.Run "cmd /c c:\PROGRA~2\Fiery\CA_INS~1\CERTIF~1\CertMgr.exe -add c:\PROGRA~2\Fiery\CA_INS~1\CERTIF~1\i1_driver.cer -s -r localMachine TrustedPublisher",0,True
    -------------------------
    [2]Create a custom action for the silent install:
    -------------------------
    Set WshShell = CreateObject("WScript.Shell")
    WshShell.Run "cmd /c c:\PROGRA~2\Fiery\CA_INS~1\EFICOM~1\setup.exe /s /f1c:\PROGRA~2\Fiery\CA_INS~1\EFICOM~1\CA_Install.iss",0,True
    -------------------------

    ***UNINSTALL Custom Action***
    cmd /c c:\PROGRA~2\Fiery\APPLIC~1\CA_INS~1\EFICOM~1\setup.exe remove /removeonly /s /f1c:\PROGRA~2\Fiery\APPLIC~1\CA_INS~1\EFICOM~1\CA_Uninstall.iss - YabsRecords 11 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ