Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily.
X
Aha, we have a winner. It was the PSF files. We have two license configurations but instead of entering in the info to create the PSF files at install time on each machine, I keep a copy of the PSF & BAT files on the server and copy them into the bin folder after install, removing the default PSF & BAT. The PSF files contain the ship code:
SHIPCODE=M030
CREO_COMMON_FILES=Common Files\M030
The PSF files I have on disk were from F000, so they did not work with M030 on the laptop. On my machine, I had installed F000 and upgraded to M030 and the PSF files got revised when I upgraded. When I copied the F000 PSF files on disk into my Creo 1.0 M030 bin folder, I got the same result that I had on the laptop, Creo wouldn't launch. When I put the M030 files back, everything worked again.
So now I get to keep a set of PSF files for each new build. Yay.
Doug Schaefer
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
This is one of the reason why I have made my .psf files parametric and substitute the content with the correct build when copying to the local machine at startup. // PTC - PSF file: parametric // PRODUCT=Creo Parametric DESC=Creo 1 _CREOBUILD_ (default) SHIPCODE=_CREOBUILD_ CREO_COMMON_FILES=Common Files\_CREOBUILD_
Great, thanks Bjarne. Do you also have some scripting in the batch file to determine the latest installed build code in the Common Files folder and set the CREOBUILD variable automatically? Kind regards, Olaf Corten Olaf Corten CAD/PLM Manager Fico B.V. Ratio 6, Duiven Phone: +31 26 3196215 Mobile: +31 644548554 www.besi.com From: Bjarne Frandsen <-> To: "-" <-> Date: 17-04-2012 16:31 Subject: [proesys] - RE: Summary - Creo 1.0 M030 won't run This is one of the reason why I have made my .psf files parametric and substitute the content with the correct build when copying to the local machine at startup. // PTC - PSF file: parametric // PRODUCT=Creo Parametric DESC=Creo 1 _CREOBUILD_ (default) SHIPCODE=_CREOBUILD_ CREO_COMMON_FILES=Common Files\_CREOBUILD_ /Bjarne
Thanks that's part of what I wanted. But wouldn't it be nice if we could use the determined %CREOVERSION% in the .psf file? Than we can have one generic psf file for every Creo build. But unfortunately this does not work: DESC=Creo 1 %CREOVERSION% (default) SHIPCODE=%CREOVERSION% CREO_COMMON_FILES=Common Files\%CREOVERSION% And this neither ENV=DESC=Creo 1 %CREOVERSION% (default) ENV=SHIPCODE=%CREOVERSION% ENV=CREO_COMMON_FILES=Common Files\%CREOVERSION% Creo just won't start even though CREOVERSION has been correctly set. Kind regards, Olaf Corten Olaf Corten CAD/PLM Manager Fico B.V. Ratio 6, Duiven Phone: +31 26 3196215 Mobile: +31 644548554 www.besi.com From: "Haigh, David A." <-> To: Doug Schaefer <>, "-" <->, Olaf Corten <-> Date: 18-04-2012 17:18 Subject: [proesys] - RE: Summary - Creo 1.0 M030 won't run Here’s what I’m using right now: tskill creoagent del "%APPDATA%\PTC\Creo\Platform\2.6\ServerMgr\.srv_mgr_db.fldx" for /F "tokens=3 delims=\ usebackq" %%A IN (`findstr "%%cf%%" "C:\ptc\Creo 2.0\Parametric\bin\ptcstatus.bat"`)DO set CREOVERSION=%%A xcopy "%USERPROFILE%\pro\creo_2_home\Configs\loadpoint\*" "C:\ptc\Creo 2.0\Common Files\%CREOVERSION%\text" /y /r xcopy "%USERPROFILE%\pro\creo_2_home\Configs\user\*" "%USERPROFILE%\pro\creo_2_home" /y /r attrib +R "C:\ptc\Creo 2.0\Common Files\%CREOVERSION%\text\config.pro" attrib +R "C:\ptc\Creo 2.0\Common Files\%CREOVERSION%\text\config.sup" set PTC_WF_ROOT=%USERPROFILE%\pro\creo_2_home\PDMLink_Cache\PTC\ProENGINEER start "LLNL" "C:\ptc\Creo 2.0\Parametric\bin\parametric.exe" This assumes you have the config.pro & config.sup in a specific location David Haigh