[neil.young]

Hi,
is it OK, that the unsigned scriptshell doesn't install on N82 (3rd FP1)?

That wasn't the case with my N95 before.

Regards

[bogdan.galiceanu]

If it is completely unsigned (PythonScriptShell_1_4_4_3rdEd_unsigned_testrange.SIS) then it is normal for it not to install. You have to sign it at Symbian Signed first.

Also, go to Settings->Applications->App. manager and make sure "Software installation" is set to All.

[aaaaapo]

Originally Posted by neil.young

Hi,
is it OK, that the unsigned scriptshell doesn't install on N82 (3rd FP1)?

That wasn't the case with my N95 before.

Regards

Yep, you have to take PythonScriptShell_1_4_4_3rdEd_unsigned_testrange.SIS and go to Symbian signed/OpenSignedOnline and sign it.

Or you can take PythonScriptShell_1_4_4_3rdEd.SIS and sign it offline with your very own developer certificate, ensymble is great tool for that, this works for me:

ensymble signsis --execaps=ALL-TCB-DRM-AllFiles --verbose --cert=yourcert.cer --privkey=yourcert.key PythonScriptShell_1_4_4_3rdEd.SIS PythonScriptShell_1_4_4_3rdEd-yourcert-signed.sis

[neil.young]

Thanks. As I said: This wasn't the case with my N95 before. Meanwhile I could successfully online sign the shell and install it.

But now I was trying to self sign a good old py app of mine, coming from S60 2nd and run lastely on my N95.

Up to now I used MAKESIS together with a *.pkg file in order to produce the SIS. Afterwards I ran SIGNSIS in order to produce the devolper signed SISX.

The latter is no longer possible I've learned. Unfortunately the online signing doesn't work either, because SYMBIANSIGNED refuses my request with:

Your application (reminder.sis) signing has failed. This may be because it has been flagged as a potential virus by our scanning or because the format of your sis file is incorrect or corrupt. Please try re-building your .sis file and re-submitting.

Can anybody point me to a secure way to produce a SIS from a .py for s60 3rd?

Until now I've used makesis (does not work) or ensymble_python2.2-0.25.py (does not work either), but both tools don't work for me.

Regards

[neil.young]

Or you can take PythonScriptShell_1_4_4_3rdEd.SIS and sign it offline with you very own developer certificate, ensymble is great tool for that, this works for me:

Yes, this worked for me to, until now. But because my old developer certificate was made for another IMEI I just wanted to go through the DevCertReq process again. Unfortunately I cannot find a hint about how to get the good old DevCert-Program again... Seemed to be not supported any longer?!

[aaaaapo]

Originally Posted by neil.young

- - my old developer certificate was made for another IMEI I just wanted to go through the DevCertReq process again. Unfortunately I cannot find a hint about how to get the good old DevCert-Program again... Seemed to be not supported any longer?!

Probably not. You have to use opensigned or pay for devcert. I surrendered and paid $200 for Trustcenter. SymbianSigned is a pain in the ass, isn't it?

Anyway, now creating sis-packages is pretty easy, I can even sign a package for 1000 IMEIs with a single command.

[neil.young]

Originally Posted by aaaaapo

SymbianSigned is a pain in the ass, isn't it?

If I would be gay, I would LOVE to work with them each day and night

But because I'm not, I hate them

Meanwhile I got it. It's simply that you MUST not bother them with a sign request, if your app doesn't use any cap at all...

Found anywhere on page 783, upper left corner, italic, 6pt

BTW:

Anyway, now creating sis-packages is pretty easy, I can even sign a package for 1000 IMEIs with a single command.

How are you doing that?

Thanks for your patience.
Regards

[aaaaapo]

Originally Posted by neil.young

It's simply that you MUST not bother them with a sign request, if your app doesn't use any cap at all...

I think the easiest way to develop PyS60 applications is to make such a file and directory hierarchy, which is executable both as separate py-files and a sis-package and which is also runnable in emulator.

You can try this kind of quick start:

1. Download the latest PythonForS60_X_Y_Z_3rdEd.sis from
   Sourceforge and install it into your phones memory.
2. Download the latest PythonScriptShell_X_Y_Z_3rdEd.SIS from
   Sourceforge.
3. Sign the PythonScriptShell with all available capabilities for the IMEI of your current development phone in OpenSignedOnline. You have to do this only once (per PyS60 revision). Then install it into your phones memory.
4. Create directories like this: Python\lib\ on your computer (Windows-PC, Mac, Linux, all are ok).
5. Put your main program into Python\ directory, you can name it now whatever you want (with .py-suffix, e.g. yourapp.py).
6. If your program uses external modules (not included in PyS60), save those into Python\lib\ directory.
7. When you want test your code in phone: zip the Python-directory, transfer it into phone (e.g. via bluetooth), unzip it to the root of your memory card with ZipManager and then run your script from script shell's menu. Your script goes into E:\Python and modules into E:\Python\lib, which is in script shell's sys.path.
8. When you want create a sis-package, use ensymble. For single script files just: ensymble.py py2sis yourapp.py. For applications with main application and separate modules rename yourapp.py -> default.py and copy all lib\*.py files to the same directory with default.py and then ensymble.py py2sis yourapp_dir

(Correct me if I forgot something or if you don't agree something above.)

It will help very much if you can use S60 emulator to test your code. You can use above mentioned directory as a workspace where ever it is located, because it can be configured to be shown as E:-drive. Configuration is a bit tricky task, but it can be done. I can write up some instructions based on my memos if somebody is interested in?

Originally Posted by neil.young

How are you doing [sign a package for 1000 IMEIs with a single command]?

I bought Open Signed Offline (Publisher ID), $200, from TrustCenter...

[neil.young]

Thanks for your efforts. Bookmarked your tutorial for later use. I'm currently just an occasional PyS60 programmer and just wanted to ensure, that an older app runs on my latest phone, so debugging is currently not an issue.

Regards

[croozeus]

Hi a(5)po,

Good workon!

Its actually a good practice to unzip to the root of the memory card, this insures that the scripts in C:\Python are not replaced

Originally Posted by aaaaapo

Configuration is a bit tricky task, but it can be done. I can write up some instructions based on my memos if somebody is interested in?

Please... that should help some folks.

Best Regards,
Croozeusz

[aaaaapo]

Originally Posted by aaaaapo

It will help very much if you can use S60 emulator to test your code. You can use above mentioned directory as a workspace where ever it is located, because it can be configured to be shown as E:-drive. Configuration is a bit tricky task, but it can be done. I can write up some instructions based on my memos if somebody is interested in?

Here is a draft version, I'll put this to the wiki after comments.

* * *

How to use any directory as E:-drive in PyS60 emulator
At this point you should have S60 and PyS60 SDK installed in you MS Windows.

1. Create somewhere on your hard- or network-drive directories e\python\lib\ It shouldn't matter where it is located.
2. Let's assume you have now directory Z:\Documents\workspace\e\python\lib\
   Open command prompt (cmd.exe) and issue following command:
   SUBST e: z:\Documents
   Now you should have virtual drive letter E: which points to your Z:\Documents.
   If you want to make this setting permanent, put it into your private autoexec.bat or paste this into your command prompt:
   echo SUBST e: z:\Documents >> "C:\Documents and Settings\All Users\Start Menu\Programs\Startup\autoexec.bat"
   
3. Edit your epoc.ini, in FP1 SDK it is in C:\Symbian\9.2\S60_3rd_FP1\Epoc32\Data\epoc.ini
   Replace suitable line with this:
   _EPOC_DRIVE_E e:\workspace\e
   Note the letter's case: small 'e:'!
4. Create file e\python\foobar.py with content "print "hello memory card"
5. Start your emulator. IF you have correct Java version installed, you should be able to open Tools->Utilities from menu and there Use Virtual MMC.
6. After emulator restart you should see (after starting PyS60) Options -> Run script an option e:foobar.py

* * *
It is possible I forgot something. Please try and reply with comments!