M
mcgowanp
Guest
Hey folks, just wondering if anyon knows how to turn off the trail files on proe??
Eng-Tips is the largest forum for Engineering Professionals on the Internet.
Members share and learn making Eng-Tips Forums the best source of engineering information on the Internet!
-
Congratulations dmapguru on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
- Status
- Thread starter
- #2
L
looslib
Guest
Pro/E MUST have the trail files to allow you to regenerate the model. You can not eliminate them. The best you can do is set a config.pro option to put them in a known folder so they can be deleted periodically.
- Thread starter
- #3
D
Dell_Boy
Guest
To do the housework automatically, you could always put a batch file in your start up folder with a statement along the lines of
del c:\temp\trail\trail.txt.* /q
DB
del c:\temp\trail\trail.txt.* /q
DB
- Thread starter
- #4
M
mcgowanp
Guest
Well, ProE don't need these files to regen a file at all, they are just records of what operations, button clicks etc that were clicked, used for recovering from crashes or for training file purposes - hence the name "trail".
The batch file is a good idea, I was just doing that but then I noticed a config.pro setting of trail_delay, set this to 0 and you will have only one file created, usually when proe is started, it might mean though that everything will be appended to this file so it could become large. I have never, ever used a trial file to recover from an error in 12 years of using proe. I would imagine it should be easier to turn these off.
The batch file is a good idea, I was just doing that but then I noticed a config.pro setting of trail_delay, set this to 0 and you will have only one file created, usually when proe is started, it might mean though that everything will be appended to this file so it could become large. I have never, ever used a trial file to recover from an error in 12 years of using proe. I would imagine it should be easier to turn these off.
- Thread starter
- #5
S
saymo
Guest
always good to keep the last trail file to recover from a crash etc.
for me trail files are invaluable. esp if you want to batch process. right a batch file and then loop the trail file,
i used a trail file to load thousands of pro files into our PDM database....all done unmanned....
use a batch file to purge the startup directory....it can be started as an arguement or started manually whenever the user wants to purge the startup dir...
eg of a purge batch file below.
set path=c:\ptc\proewildfire2\bin;%path%
cd /d "%1"
start /B purge.bat
modify your 'path' to suit and it will work.
for me trail files are invaluable. esp if you want to batch process. right a batch file and then loop the trail file,
i used a trail file to load thousands of pro files into our PDM database....all done unmanned....
use a batch file to purge the startup directory....it can be started as an arguement or started manually whenever the user wants to purge the startup dir...
eg of a purge batch file below.
set path=c:\ptc\proewildfire2\bin;%path%
cd /d "%1"
start /B purge.bat
modify your 'path' to suit and it will work.
- Status
