Creo 1.0 Custom startup script - cmd window not exiting

[davehaigh]

I copied my current startup script for ProE and made some changes to allow it to startup Creo 1.0.

The issue I'm having is the command window isn't going away once Creo starts.

My current script for WildFire 4, is almost identical and the command window does go away when ProE starts.

Any ideas? I don't want users to have to close the command window manually.

I have a Windows 7 machine, however I don't believe the OS is the problem.

Here's the script:
set PTC_WF_ROOT=%USERPROFILE%\pro\creo_1_home\PDMLink_Cache\PTC\ProENGINEER
del "%USERPROFILE%\pro\creo_1_home\*.log*"
del "%USERPROFILE%\pro\creo_1_home\*.xml*"
del "%USERPROFILE%\pro\creo_1_home\*.inf*"
del "%USERPROFILE%\pro\creo_1_home\*.m_p*"
del "%USERPROFILE%\pro\creo_1_home\*.out*"
del "%USERPROFILE%\pro\creo_1_home\*.crc*"
del "%USERPROFILE%\pro\creo_1_home\*.usr*"
del "%USERPROFILE%\pro\creo_1_home\*.bom*"
del "%USERPROFILE%\pro\creo_1_home\*.tst*"
del "%USERPROFILE%\pro\creo_1_home\*.ger*"
del "%USERPROFILE%\pro\creo_1_home\*.err*"
del "%USERPROFILE%\pro\creo_1_home\*.lst*"
del "%USERPROFILE%\pro\creo_1_home\*.idx*"
del "%USERPROFILE%\pro\creo_1_home\*.isl*"
del "%USERPROFILE%\pro\creo_1_home\*trail.*"
"C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric.exe"


David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550


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.

[DamianCastillo]

David,

I have the same issue. Have not looked into it much as of yet, but I can
tell you that the script is exactly the same, so it must be some kind of
bug. It's hard to think that Creo 1.0 could have an issue that leaves the
Command Window open, but I double checked the two scripts and they are the
same.

I am running Windows 7 Professional 64-bit.

I will look into it more soon.


Damián Castillo
CAD & Administration Manager
Engineering Department
Hensley Industries

[davehaigh]

So far I've had suggestions to add either call or start to the line of the script that actually starts Creo.

Neither works:
call "C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric.exe"
Does the same thing as not having call there. Creo starts but the window doesn't go away

call "C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric.exe"
exit
Same results as having just the call line.

Start "C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric.exe"
Creo doesn't start at all, and the cmd window doesn't go away. But the window repaints to a new prompt

Start /nowait "C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric.exe"
Creo doesn't start, but the command window does go away

Time to contact PTC.

David Haigh

[davehaigh]

Thanks to Tom McNaney Jr. at PTC for the answer. The following syntax works.

start "Creo 1.0 Parametric" "<creo_parametric_loadpoint>\bin\parametric.exe"

David Haigh

[DamianCastillo]

Thanks for the update David.

It must be a Creo 1.0 issue because I have the same exact script except
for Wildfire 5 and it works perfect. The only difference is the location
it points to for the exe.

I will open a ticket soon.


Damián Castillo
CAD & Administration Manager
Engineering Department
Hensley Industries

[DamianCastillo]

That worked, but the Golden Questions is.... Why?

Why would the batch script work on Wildfire 5 and not on Creo 1.0

How did you come up with the syntax? I don't even use the "Creo 1.0
Parametric" naming anywhere in my installation.

I want answers.....Give me the Info.

🙂


Damián Castillo
CAD & Administration Manager
Engineering Department
Hensley Industries