|
[Sponsors] |
August 24, 2003, 02:54 |
how can I generate new exe file in star-cd
|
#1 |
Guest
Posts: n/a
|
I use star-cd 3.15a, windows 2000 and absoft8.0.
I try to generate a new exe file in star-cd, but I can not. This is the first error: "Corrupt parm.inc file - exiting starlink." Who know how can I generate a new exe file in windows version? Is there any document about this topic? Thanks, |
|
August 25, 2003, 15:10 |
Re: how can I generate new exe file in star-cd
|
#2 |
Guest
Posts: n/a
|
Did you write the parm.inc with Prostar on that windows version? If not, thats the problem.
|
|
August 26, 2003, 01:08 |
Re: how can I generate new exe file in star-cd
|
#3 |
Guest
Posts: n/a
|
Yes, I write with pro-am on windows version. In other problem, I use udf too. I can not generate exe file.
|
|
August 27, 2003, 09:36 |
Re: how can I generate new exe file in star-cd
|
#4 |
Guest
Posts: n/a
|
hmm, I would guess that there is a problem with running grep or sed under the pdksh on your machine...if you look at the starlink script, there is a line:
MAXDMN=`grep -i MAXDMN parm.inc | sed -e 's/.*=\(.*\)).*/\1/' -e 's/ //g'` if you start up a command prompt, run the pdksh, then try executing grep -i MAXDMN parm.inc | sed -e 's/.*=\(.*\)).*/\1/' -e 's/ //g' see if it properly returns the value corresponding to MAXDMN in your parm.inc file. |
|
August 28, 2003, 00:51 |
Re: how can I generate new exe file in star-cd
|
#5 |
Guest
Posts: n/a
|
Dear Kevin,
It returns 1 In parm.inc file I have PARAMETER (MAXDMN= 1). What is MAXDMN? Does it have currect parameter? |
|
August 28, 2003, 02:34 |
Re: how can I generate new exe file in star-cd
|
#6 |
Guest
Posts: n/a
|
Dear Kevin,
Below line in starlink does not work properly. MAXDMN=`grep -i MAXDMN parm.inc | sed -e 's/.*=\(.*\)).*/\1/' -e 's/ //g'` I add MAXDMN=1 after that and everything is OK now. But it is not good solution. Why that line does not work properly? |
|
August 28, 2003, 06:11 |
Re: how can I generate new exe file in star-cd
|
#7 |
Guest
Posts: n/a
|
I had a problem that was about the same. I solved it by adding the option -o to the grep command in starlink. It has something to do with the difference between the pksh and a normal csh. The output from grep is formatted just a little bit different this pksh. By adding the -o option this can probably be corrected. The line in starlink now looks like
MAXDMN='grep -i -o MAXDMN patm.inc | ser -e 's/.*=\(.*\)).*/\1/'-e 's/ //g'' I hope this works for you also Michiel |
|
August 28, 2003, 08:33 |
Re: how can I generate new exe file in star-cd
|
#8 |
Guest
Posts: n/a
|
Dear Michiel,
I use windows version of star-cd and grep. There is not -o option for grep in windows version. What is -o option? Is there another option for it? |
|
August 28, 2003, 08:53 |
Re: how can I generate new exe file in star-cd
|
#9 |
Guest
Posts: n/a
|
The -o option comes from the MS-grep command. If you type 'grep ?' in dos command mode than you see what these options are.
grep ? tells you thatthat the -o options gives you the UNIX output format Michiel |
|
September 2, 2003, 06:39 |
Re: how can I generate new exe file in star-cd
|
#10 |
Guest
Posts: n/a
|
I think that maybe you have more than one copy of sed on your system. The sed to use is in $STARDIR/wingnu/bin and if you run pdksh and type sed you should see this: C:\>"c:\Program Files\STAR_520\wingnu\bin\sed.exe" Usage: c:/progra~1/star_520/wingnu/bin/sed.exe [OPTION]... {script-only-if-no-other-script} [input-file]...
-n, --quiet, --silent suppress automatic printing of pattern space -e script, --expression=script add the script to the commands to be executed -f script-file, --file=script-file add the contents of script-file to the commands to be executed -l N, --line-length=N specify the desired line-wrap length for the `l' command -u, --unbuffered --help display this help and exit -V, --version output version information and exit If no -e, --expression, -f, or --file option is given, then the first non-option argument is taken as the sed script to interpret. All remaining arguments are names of input files; if no input files are specified, then the standard input is read. E-mail bug reports to: bug-gnu-utils@gnu.org . Be sure to include the word ``sed'' somewhere in the ``Subject:'' field. If you see output other than this you have the wrong sed and you can fix this in one of three ways: 1) modify starlink so it runs $STARDIR/wingnu/bin/sed.exe 2) modify your path so $STARDIR/wingn/bin is found further up the list 3) copy sed.exe form $STARDIR/wingnu/bin to somewhere further up on your path such as C:\WINNT\system32 |
|
September 6, 2003, 01:18 |
Re: how can I generate new exe file in star-cd
|
#11 |
Guest
Posts: n/a
|
Dear philip,
I have only one sed.exe on my system. I saw other file in wingnu\bin folder too (nnsed.exe). I edited starlink and I replaced sed with nnsed. Now everything is OK. But I think it is better that I don't edit starlink. Also I have got other solution too, But it is not good solution. I added MAXDMN=1 after below line in starlink. So I know this line does not work properly. MAXDMN=`grep -i MAXDMN parm.inc | sed -e 's/.*=\(.*\)).*/\1/' -e 's/ //g'` Best Regards, |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Importing Star-CCM+´s .ccm file in Star-CD | Zolet | Siemens | 7 | November 26, 2008 14:57 |
Generate chemkin appropriate file for a reaction | ilati | FLUENT | 0 | March 3, 2007 04:22 |
how to generate postscript file? | leo | Siemens | 6 | May 28, 2003 00:38 |
Is it the bug to save file in star-cd 3.10a | raymond | Siemens | 3 | September 21, 2001 03:09 |
How to generate a postscript file or a tif file? | Ming-Jyh Chern | Siemens | 4 | June 5, 2001 14:07 |