Creo Leaves Command Prompt Window Open

[dgschaefer]

Creo 1.0 F000



Hello,



We use a series of batch files to launch Pro/E. We use the same files
for WF3, WF4, WF5 and now Creo 1. When a specific version is launched,
it's a specific batch file that sets a series of variables that define
the version being used then it calls the common batch files. Part of
that process is that the user is prompted to choose which client they
are working on so that the proper config files are loaded.



In WF3, WF4 and WF5 (as well as versions back to 2001), the command
prompt window comes up with the client choice prompt, but once the
choice is made and the files are processed the command prompt window
goes away before Pro/E comes up. With Creo 1, the window fails to close
but Creo launches fine. The user can close the command prompt without
apparent issue or it will close when Creo is closed.



The last line of our batch files simply calls the Pro/E or Creo
executable (preo.exe in WF5 and older, parametric.exe in Creo),
sometimes with a trail file to run. I tried adding 'exit' and 'exit /b'
to the end of our batch file but that didn't work. I suspect it may be
a change in the executable file itself.



It's not a huge deal, but it would be nice to have the command prompt
window close once the batch file is processed, like it did prior to
Creo. Any ideas?



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.

[DaveEngel]

Try this:

start "Creo 1.0 Parametric" "C:\<where you=" loaded=" it=">\Parametric\bin\parametric.exe"

-Dave

[joe.kidd]

Hi Doug,

I'm having the same issue. Did you ever figure it out or get any help?

Also, I've always loaded the config.sup file to the loadpoint text directory. They've changed that and the two text directories I did find don't recognize the config.sup file because the options don't show up in Creo.

Frustrated,

Joe

[DamianCastillo]

I believe Dave Engel provided the solution. I had to deal with this back when I first installed F000 of Creo 1.0

Works fine when you use the example Dave provided.

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[dgschaefer]

Here's the command I used, based on info from the exploder, probably
from Dave Engel.



start " "C:\Program Files\PTC\Creo 1.0\parametric\bin\parametric.exe "



Works great, even for other versions of Pro/E.



Doug Schaefer

[DarrinHiebert]

In Reply to Doug Schaefer:

We just installed Creo1 and ran into this same issue. Just so that I understand, you guys are NOT loading the PSF file that is in the bin directory then? What exactly does that file do, and why did they put it in there, if we don't really need it???

Darrin Hiebert

Here's the command I used, based on info from the exploder, probably
from Dave Engel.



start " "C:\Program Files\PTC\Creo 1.0\parametric\bin\parametric.exe "



Works great, even for other versions of Pro/E.