| www.delorie.com/archives/browse.cgi | search |
At 11:22 PM 12/9/2004, you wrote: >I guess I should have been more specific with my original posting... > >I was running pro_batch in command-line mode (pro_batch -text ...) and not >interactive mode, i.e. not using the GUI at all. I thought it was implied since >I was talking about running a shell script and a batch file. The shell script >actually constructs the command-line and input file automatically and then >kicks off the DOS batch file. The script is supposed to monitor to contents >of the file pro_batch.log.1 afterwards but it started to parse the file contents >even before the DOS batch file is completed. If I forced a long wait by adding >a "sleep 300" after the DOS batch file command, parsing was done properly. >However, I cannot set a fix wait time as it depends on the complexity of the >Pro/E assembly. > >You are correct in that the pro_batch interactive mode does work. Well, I guess I need a simple example then. So far, everything I've tried works fine. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |