So some weeks ago I sent out a Creo 1.0 startup script that copied some config files into the load point. That script looked inside a file to determine what version of Creo Parametric was installed.
Well, wouldn't you know, the file I was looking at.... no longer exist in Creo 2.0. Damn!
So I had to rewrite my script to look at another file. This time around I decided to use a file I doubt PTC will eliminate. The ptcstatus.bat file.
This time I only needed one "for" statement. A few things to note in this version:
* I used delims=\ to use the backslash as a delimiter.
* I'm now looking for the third token.
* The string I'm looking for in the file had % signs in it. So I have to double the %'s to escape them in the script.
for /F "tokens=3 delims=\ usebackq" %%A IN (`findstr "%%cf%%" "C:\ptc\Creo 2.0\Parametric\bin\ptcstatus.bat"`)DO set CREOVERSION=%%A
Everything else about the script is the same as previously described. The complete script is below.
David Haigh Phone: 925-424-3931 Fax: 925-423-7496 Lawrence Livermore National Lab 7000 East Ave, L-362 Livermore, CA 94550
The complete script 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.