E. Crane Computing Support Forum

Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.

You are not logged in.

#1 2007-02-22 04:53:04

Mike
Guest

Re: PowerGen EXE generation using CLI

Hi

We've just migrated our PB from v9 to v10.5.1.  Our overnight build uses PowerGen scripts/cli and seems to work fine except that the .exe files that are generated are smaller than they should be and then nothing happens if you try to execute them.  Example is ssm.exe that should be 57k but is now only 25k.  If however, I manually open the gen file in PowerGen and select Create EXE, it produces the .exe file correctly.

We're using PowerGen 6.5.0.12 for PB10.5. 

I have an old test build that works and the only difference I can see is that it was using PB10.5.0.  I'm sure I've had it working ok using PB10.5.1 but I can't be 100%.

Any ideas please?

Cheers
Mike

#2 2007-02-22 11:54:43

Phil
Guest

Re: PowerGen EXE generation using CLI

Hi Mike,

What is the command line you're using?  If the configurations for the GUI and CLI builds are the same the resulting EXE should be the same.  So it must be something in the configuration.  Also send the output log if you can.

Regards,

Phil

#3 2007-02-23 05:51:41

Mike
Guest

Re: PowerGen EXE generation using CLI

Hi Phil

We have a batch file that sets Registry settings before the build begins ...
Start /w Pwrgn105.exe /Q /H /L_SREO=Y /L_SSDO=Y /I_RALIP=Y /I_RDIO=N /I_F=R /E_S=pgerror_session.err /B_BEL=N /I_DONS=Y

...and the CLI used to create the EXE is
Start /w Pwrgn105.exe /Q /E="c:\pb\genfiles\ssm.gen"

I kept getting errors when trying to upload file(s) for attachment, so I've tried adding a section of the log file as a code attachment.
If it doesn't work, I could just email you anything you need.

Cheers
Mike

#4 2007-02-27 08:20:49

Mike
Guest

Re: PowerGen EXE generation using CLI

Hi Phil

I think we've stumbled upon the problem!

It seems our build was using an older version of VECli to change the EXE properties.  This caused the problem.  Changing the build to use the latest PowerGen 6.5 version of VECli, seems to have sorted things out.

Cheers
Mike

Board footer