PKG File: executing an exe with command line arguments

[vaibhavjain]

Hi,

Is possible to specify the command line arguments that are passed to the installed executable marked with FR flag for running then during installations. And it is possible then can we bind that argument to an option list. Lets say i display an option list.
!(("Register via GPRS"), ("Register via SMS"))

;Copy the registration stub and pass it reg arguments
"register.exe"-"C:\private\10000005\import\register.exe" option1 option2, FR

SDK: S60 3rd Edition FP1
IDE: Carbide Express 1.2

Regards,
Vaibhav

[symbianyucca]

Nope but you can make two executables from which one is selected according to the users choice.

yucca

[vaibhavjain]

oh... it was really disappointing to hear that. If can run an executable during installation then we shall also be able to give it some command line params.

Anyways it seems that i only have two options left.

1. Branch the execution based on the presence/content of a text file. The registration stub will check for the presence or content of a file and then will proceed appropriatly.

2. Dynamically generate the name of the installed file. like
!(("Register via GPRS"), ("Register via SMS"))
IF ( option1==1)
"register.exe"-"C:\private\10000005\import\registersms.exe", FR
ELSE
"register.exe"-"C:\private\10000005\import\registergprs.exe", FR
ENDIF
since the executable name will always be available to the exe via arg[0] i think i will be able to pass parameters to the same registration stub.

both options seem messy to me. Can you please any suggest any other solution.

Thanks,

[wizard_hu_]

Since you are starting an executable, you can consider asking the user in your code.

[vaibhavjain]

ya that would have been the most sensible approach but i wanted to keep the registration stubs clean of any UI. They are executed only one time and then removed by the main application when it first boots up.

[wizard_hu_]

They are executed only one time and then removed by the main application when it first boots up.

Since you are using 3rd edition, I would have some doubts about the probability of this removal.

[vaibhavjain]

Since you are using 3rd edition, I would have some doubts about the probability of this removal.

prefect point.(how could i miss the data caging issue).... however as far as my understanding of data caging is concerned the application has access to its own directories ( readonly for /resouce and readwrite for /private/<sid>/) and if that exe resides in the same directory (/private/<sid>) then i can easily get it deleted . Please correct me if i am wrong.

[wizard_hu_]

Remember that on 3rd edition any file containing binary executable code resides in \sys\bin. The directory you cannot even read in a general situation. And this is the only place where the OS looks for binaries.
Ok, there are tricks (for JIT compilers, there is RChunk::CreateLocalCode, and you can put there anything you want), but their use is not typical in "everyday code".

[vaibhavjain]

Thanks for that insight in to data caging . I wasnt aware of the /sys/bin issue. Now i can really see how datacaging provides real security.

Anyways i am only left with two working options one that i add some gui to my registration stub or second that i use option 2 mentioned in my previous post. I think that former option will be much better in terms of simplicity and future extensibiliy.

Thanks for the help.
:-)