Skip to main content
M
Mat16-Pearl
16-Pearl
December 11, 2023
Solved

Custom folder for parametric.psf

  • December 11, 2023
  • 2 replies
  • 4102 views

Hi there,

 

in Creo's bin folder (e.g. C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin ) there is a "parametric.bat", which executes

 

@echo off
"C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.exe" "C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.psf" %*

 

 

Is it possible to place that batch file and the corresponding "parametric.psf" anywhere else?

 

e.g.

C:\temp\%username%\custom-parametric.bat with

 

@echo off
"C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.exe" "C:\temp\%username%\custom-parametric.psf" %*

 

 

I tried it, but it did not worked so far.

Best answer by Mat

I think I have it.

Instead of altering parametric.psf every time, I remove every "feature" in parametric.psf once and alter those settings via the "set" command by my start script.

 

set PRO_LANG=frensh
set CREOPMA_FEATURE_NAME=PROE_DesignEss (10119 10113)
set PTC_D_LICENSE_FILE=7788@my_license-server.com
<loadpoint>\Parametric\bin\parametric.bat

 

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
December 11, 2023
@Mat wrote:

Hi there,

 

in Creo's bin folder (e.g. C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin ) there is a "parametric.bat", which executes

 

@echo off
"C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.exe" "C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.psf" %*

 

 

Is it possible to place that batch file and the corresponding "parametric.psf" anywhere else?

 

e.g.

C:\temp\%username%\custom-parametric.bat with

 

@echo off
"C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.exe" "C:\temp\%username%\custom-parametric.psf" %*

 

 

I tried it, but it did not worked so far.

Hi,

my suggestion ... do not play with OOTB location of psf files. I am almost sure PTC does not support different location of these files.

Maybe you can explain what do you need to achieve and why.

    M
    Mat16-PearlAuthor
    16-Pearl
    December 12, 2023

    Hi Martin,

    the parametric.psf contains e.g. language settings, license type and server, special configurations like CEF_DEBUG_PORT and so on.

     

    I wrote a small Dialog, where Users can choose their desired license. They also can define settings like language in their own "user-config.psf".

    Mandatory settings like the license server address are stored in a company configuration file.

    When the user clicks on "START CREO", all important config files get combined to "C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\parametric.psf".

     

    But unfortunately this requires write access to that folder "C:\Program Files\PTC\Creo 10.0.2.0\Parametric\bin\", which is not always granted.

    M
    Mat16-PearlAuthorAnswer
    16-Pearl
    December 12, 2023

    I think I have it.

    Instead of altering parametric.psf every time, I remove every "feature" in parametric.psf once and alter those settings via the "set" command by my start script.

     

    set PRO_LANG=frensh
set CREOPMA_FEATURE_NAME=PROE_DesignEss (10119 10113)
set PTC_D_LICENSE_FILE=7788@my_license-server.com
<loadpoint>\Parametric\bin\parametric.bat

     

      Terms & ConditionsAccessibility statement