CMD does not close automatically after calling the parametric.bat file of Creo 2.0

Forum|Forum|12 years ago
January 27, 2014
10 replies
5095 views

Hello All,

I have created a batch file which sets everything for an user like configuration files, start in directory and finally calls the parametric.bat file. Everything works except the cmd window does not close automatially.

I can change the parametric.bat file to parametric.exe which works as expected. However, i would like to know why it does not work with Creo 2.0 whereas it was working with Pro/ENGINEER Wildfire 5.0.

call "D:\Creo2\Creo2\Creo2\Parametric\bin\parametric.bat"

exit

Thank you!

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.

General

C

chuck1989

1-Visitor

Hello there,

we have creo 2.0 m030 and it works fine for us.

1. we setup the shortcut started up and execute the parametric.bat This is a short cut on desktop or any program group. It is also where you set the working directory for creo parametric as well.

2. in the parametric.bat, we have all kind of environments for permissions and so on, the last line should be like so, exactly like the out of the box that parametric.bat has:

"C:\Program Files\PTC\Creo 2.0\Parametric\bin\parametric.exe" "C:\Program Files\PTC\Creo 2.0\Parametric\bin\parametric.psf" %*

*notes: you call parametric.bat from another DOS shell. that is why it is still open and not exit.

N

NiharPal

Author

1-Visitor

Thank you.

We have Creo 2.0 M060. I can get it to work if i call the exe file and psf file.

The method of calling batch file (proe1.bat) was working in Wildfire 5.0. I expect it should work in Creo 2.0.

C

chuck1989

1-Visitor

disregard how you do in wildfire, it works for me as is. It should work for you if you just execute directly from parametric.bat or create a shortcut for it.

you can just put all your environments setup in that file before execute the parametric.exe

S

SergDubrovskiy

1-Visitor

@echo off

start "Creo 2.0 Windchill" "E:\PTC\Creo 2.0\Parametric\bin\parametric.exe" "E:\PTC\Creo 2.0\Parametric\bin\parametric_wnc.psf" %*

N

NiharPal

Author

1-Visitor

Thanks Sergey.

I have it that way and it's working for me withouts issues. I was interested to know if there is any change in environment of Creo which is not allowing the CMD to close automatically.

A

akrenzer

1-Visitor

Add empty quotes before the path ""

start "" "D:\Creo2\Creo2\Creo2\Parametric\bin\parametric.bat"