SIS file - Python 1.4.1 - Symbian S60 3rd Ed

[Chiara81000]

Hi all,
I'm working on 3rd edition mobile with Python version 1.4.1. I need to do a SIS file for an application, but it doesn't work. I have read and followed the procedure written here:

http://www.nbl.fi/~nbl928/ensymble.html

and I have also read the Ensymble documentation for py2sis (http://www.nbl.fi/~nbl928/README-0.26.txt). I managed to do the SIS file with this command line:

ensymble.py py2sis 
--appname=application 
--version=1.0.0 
--caption="application" 
--cert=cert.cer 
--privkey=key.key 
--passphrase=password 
--caps=
LocalServices+Location+NetworkServices+PowerMgmt+ProtServ+ReadDeviceData+ReadUserData+SurroundingsDD+SwEvent+TrustedUI+UserEnvironment+WriteDeviceData+WriteUserData 
application.py

and also the installation is successfull but when I try to open it, but it doesn't start (it seems that it is opening for half a second). I try to put some try/except somewhere but it does the same.

Does anyone have any idea?
Chiara

[dehlerm]

Are the python runtime and your application istalled on the same drive? (both in phone memory _or_ both on memory card)

[Chiara81000]

Are the python runtime and your application istalled on the same drive? (both in phone memory _or_ both on memory card)

Yes! It was this the problem! Thank you very much dehlerm!
Maybe you can help me again... I want to make an unsigned version of the application. I have two sis files. I would like to merge them with esymble(mergesis). The question is this. If I sign the final sis file, Am I going to sign both the sis files included in it?
Thank you very much again,
Chiara

[bogdan.galiceanu]

Yes! It was this the problem! Thank you very much dehlerm!
Maybe you can help me again... I want to make an unsigned version of the application. I have two sis files. I would like to merge them with esymble(mergesis). The question is this. If I sign the final sis file, Am I going to sign both the sis files included in it?
Thank you very much again,
Chiara

If you are talking about signing it with ensymble during the merge process, then yes, they are both signed when the final .sis file is created.