Sign in or 
Share this
MakeSIS & Unmakesis For OS9.x kvt,unsis,winsis 3rd Edition Worked
If are wondering if it is possible to
create .sis / .sisx and decompiler .sis / .sisx 3rd editions OS9.x...
the answer is YES
KVT Symbian Installer 2.0.368 Beta5 !!!
KVT Symbian Installer 2.0 (Beta 5)
Feature :
- Open and Import now support SymbianOS 9 (New)
- Support UIQ 3 (New)
- Extract SIS support SymbianOS 9 (New)
- Generate Seft-Signed Certificate Tools (New)
- Get SIS version and UID information from a sis file (Currently not support SymbianOS 9)
- Multiple popup texts
- Faster than old version (v1.4)
- Add LOG tab
- Support multiple language dependent files
- Support AddOn Option
- Support Embedded SIS
- Support multiple platform (s60, s80, UIQ ...)
- Support Khmer and English Interfaces
- Fixed some bugs
3 Step for Download and Register:
1. dowload Kvt v2.0 (Build 368) Beta5
Kvt v2.0 (Build 368) Beta5
2. download ActivePerl
ActivePerl-5.8.8.819-MSWin32-x64-267479
3. Register
Get register serial here
UnMakesis OS9.x whit uNsIs 2.2
-------------[About uNsIs v2.2]-----------------------
Based on SISInfo issued by NewLC on Aug. 24 by Jari.
A public issued unpack tool, please support us greatly!
Keep on supporting 3G365! We can do it better!
-------------[uNsIs Note]----------------------------
1)Unpack and run "uNsIs v2.2.msi".
2)There are 3 folds as bin、 pkg and temp in this directory.
Directory “bin” contains system files and do not touch anything!!!
3)Installation path information of sis package is stored in directory“pkg” ,
and it can be showed in the application as well; files unpacked from
sisarchive are placed in the directory “temp”.
4)Make sure to clean “temp” everytimeafter unpack process for fear affecting
the next unpack operation!!!
v2.2(2006-10-14):
support Theme unpack!
1. dowload Kvt v2.0 (Build 368) Beta5
Kvt v2.0 (Build 368) Beta5
2. download ActivePerl
ActivePerl-5.8.8.819-MSWin32-x64-267479
3. Register
Get register serial here
UnMakesis OS9.x whit uNsIs 2.2
-------------[About uNsIs v2.2]-----------------------
Based on SISInfo issued by NewLC on Aug. 24 by Jari.
A public issued unpack tool, please support us greatly!
Keep on supporting 3G365! We can do it better!
-------------[uNsIs Note]----------------------------
1)Unpack and run "uNsIs v2.2.msi".
2)There are 3 folds as bin、 pkg and temp in this directory.
Directory “bin” contains system files and do not touch anything!!!
3)Installation path information of sis package is stored in directory“pkg” ,
and it can be showed in the application as well; files unpacked from
sisarchive are placed in the directory “temp”.
4)Make sure to clean “temp” everytimeafter unpack process for fear affecting
the next unpack operation!!!
v2.2(2006-10-14):
support Theme unpack!
Download :
uNsIs_2.2
-------------[WinSiS Pro Note]---------------------------------------------------------
1)Run the main application by unpacking WinsisPro.rar archive,
starting installation of WinSiSPro_EN.msi and running WinSiSPro_EN.msi
in the installation directory.Referring to the figure bellow for
the UI view of main application, with hintson major menu buttons!
2)Fill the acquired UID and version number into relevant blank frames
respectively; Name the target SiS file to be generated by packing
in the display frame "SiS eXtrafile name". It supports picking-up
UID from original sis files.
Specific format is as follows,
UID: 8-digithex number (e.g. a00007a6);
Version No.:should be xx,xx,xx (e.g. 00,50,00),not supporting Chinese punctuation;
SiS eXtra Filename: can be anything preferred including alphabets, Arabic numbers
and Chinese characters (try not using special characters).
3)7 display frames on theUI are used to show files to be packed, with one “□” selector
and three “○” selectorson each display frame. To activate the display frame please
tick the “□” selector, not-activated framesmeans not to install into this directory.
Installation path is indicated afterthe “□” selector,and please tick “○” selector
to define installation path; Left click the display frame by mouse, and a menu pops up,
please select files to be installedinto this path (e.g. example.exe is to be installed
to \sys\bin directory inthe smart phone, please activate this display frame firstly by a
left click,select example.exe, and there will be relevant display inside the frame.)
Display frame 5# is to show setup option of the embedded sis file.
Display frame 6# is to show messages during the sisx file installation,
just similarly activate it and input desired text messages.
Display frame 7# is for extended path, all those paths not included in the above 6
installation paths can be set here (e.g. C:\sys\help).
4)Upon completion of the above jobs it is time to click “Save PKG” button to make the PKG file,
and a winsis.pkg file will be generated in this directory.
5)There is a certificate file cert.cer and key file key.key attached with the application.
It can begenerated by yourself when clicking “Creat credentials” button.
Be sure to delete or rename the cert.cer and key.key file in advance.
6)Click “MakeSiS” button and generate the SiS eXtra installation application.
It takes about 10s for the pack process.
--------------------------------------------------------------------------------------
Download :
WinSis Pro v1.31
Premising that the author of the soft naturally I am not me... but is it so difficult?
If you have created themi you should not have any difficulty to create certified etc...
I have posted only the soft the rest you can do it you...
You can manually Create also the certificates :
Create a private key and self signed certificate
makekeys -cert [-v] [-len key-length ] [-password password ] -dname distinguished-name-string private-key-file public-key-cert
For example:
makekeys -cert -dname “CN=Symbian OU=Development OR=SymbianLtd CO=GB” mykey.key mycert.cer
Create a certificate request given a self-signed certificate
makekeys – req [-v][-password password] -dname distinguished-name-string private-key-file public-key-cert cert-request-file
For example:
makekeys req -dname “CN=Symbian OU=Development OR=SymbianLtd CO=GB” mykey.key mycert.cer myreq.p10
It is then up to the developer to send the certificate request to be signed by a trusted third party, i.e. a Certificate Authority. The CA uses various means to establish that the originator of the certificate request is who they claim to be. The developer’s public key is signed by the CA, using the CA’s private key, creating a certificate, which is then sent back to the applicant. The CA may return a single certificate, or a file containing a chain of certificates.
It is important that certificates returned by CA’s are in the base64 encoded ASCII format. The Certification Generator generates base 64 encoded certificate files and expects certificates which come back from a CA to be in the same format.
The CA may return a file containing a certificate chain. These are supported, and are needed if intermediate certificates are required between the CA’s root certificate on the Symbian OS device and the developer certificate.
View certificate details
makekeys – view public-key-cert
Displays details of a certificate or certificate chain file. The -view command should be used with an existing certificate file (which should be in base 64 encoded format).
For example:
makekeys – view mycert.cer
Arguments
-cert
Create the private key (private-key-file) and self signed certificate (public-key-cert). If the private key file already exists it will be used to create the self signed certificate.
-req
Create a certificate request.
-view
View certificate details.
-v
Verbose mode — displays additional diagnostic information.
-dname distinguished-name-string
The distinguished-name-string specifies the distinguished name parameters required for the self-signed public key certificate file. This command line option should be constructed of a string of white space separated key/value pairs as follows:
CN=common name
OU=organisational unit
OR=organisation
LO=locality
ST=state
CO=country
EM=e-mail address
-password password
Password (optional). After creation, the password must be supplied to subsequently use the private key.
-len key-length
The key-length. The minimum is 512, maximum is 4096. The key length defaults to 1024.
-private-key-file
The file containing the private key. The private key should kept secret by the developer, whereas the public key is usually made generally available. Has a .key extension.
-public-key-cert
A self-signed certificate containing the public key. Has a .cer extension.
-cert-request-file
A self-contained file which is sent to the CA. The Certification Generator will create this file given a private and public key. It is then up to the developer to send the file to the CA and arrange for the application for the certificate. Has a .p10 extension.
uNsIs_2.2
MakeSis OS9.x whit WinSis Pro v1.31
-------------[WinSiS Pro Note]---------------------------------------------------------
1)Run the main application by unpacking WinsisPro.rar archive,
starting installation of WinSiSPro_EN.msi and running WinSiSPro_EN.msi
in the installation directory.Referring to the figure bellow for
the UI view of main application, with hintson major menu buttons!
2)Fill the acquired UID and version number into relevant blank frames
respectively; Name the target SiS file to be generated by packing
in the display frame "SiS eXtrafile name". It supports picking-up
UID from original sis files.
Specific format is as follows,
UID: 8-digithex number (e.g. a00007a6);
Version No.:should be xx,xx,xx (e.g. 00,50,00),not supporting Chinese punctuation;
SiS eXtra Filename: can be anything preferred including alphabets, Arabic numbers
and Chinese characters (try not using special characters).
3)7 display frames on theUI are used to show files to be packed, with one “□” selector
and three “○” selectorson each display frame. To activate the display frame please
tick the “□” selector, not-activated framesmeans not to install into this directory.
Installation path is indicated afterthe “□” selector,and please tick “○” selector
to define installation path; Left click the display frame by mouse, and a menu pops up,
please select files to be installedinto this path (e.g. example.exe is to be installed
to \sys\bin directory inthe smart phone, please activate this display frame firstly by a
left click,select example.exe, and there will be relevant display inside the frame.)
Display frame 5# is to show setup option of the embedded sis file.
Display frame 6# is to show messages during the sisx file installation,
just similarly activate it and input desired text messages.
Display frame 7# is for extended path, all those paths not included in the above 6
installation paths can be set here (e.g. C:\sys\help).
4)Upon completion of the above jobs it is time to click “Save PKG” button to make the PKG file,
and a winsis.pkg file will be generated in this directory.
5)There is a certificate file cert.cer and key file key.key attached with the application.
It can begenerated by yourself when clicking “Creat credentials” button.
Be sure to delete or rename the cert.cer and key.key file in advance.
6)Click “MakeSiS” button and generate the SiS eXtra installation application.
It takes about 10s for the pack process.
--------------------------------------------------------------------------------------
Download :
WinSis Pro v1.31
Premising that the author of the soft naturally I am not me... but is it so difficult?
If you have created themi you should not have any difficulty to create certified etc...
I have posted only the soft the rest you can do it you...
You can manually Create also the certificates :
Create a private key and self signed certificate
makekeys -cert [-v] [-len key-length ] [-password password ] -dname distinguished-name-string private-key-file public-key-cert
For example:
makekeys -cert -dname “CN=Symbian OU=Development OR=SymbianLtd CO=GB” mykey.key mycert.cer
Create a certificate request given a self-signed certificate
makekeys – req [-v][-password password] -dname distinguished-name-string private-key-file public-key-cert cert-request-file
For example:
makekeys req -dname “CN=Symbian OU=Development OR=SymbianLtd CO=GB” mykey.key mycert.cer myreq.p10
It is then up to the developer to send the certificate request to be signed by a trusted third party, i.e. a Certificate Authority. The CA uses various means to establish that the originator of the certificate request is who they claim to be. The developer’s public key is signed by the CA, using the CA’s private key, creating a certificate, which is then sent back to the applicant. The CA may return a single certificate, or a file containing a chain of certificates.
It is important that certificates returned by CA’s are in the base64 encoded ASCII format. The Certification Generator generates base 64 encoded certificate files and expects certificates which come back from a CA to be in the same format.
The CA may return a file containing a certificate chain. These are supported, and are needed if intermediate certificates are required between the CA’s root certificate on the Symbian OS device and the developer certificate.
View certificate details
makekeys – view public-key-cert
Displays details of a certificate or certificate chain file. The -view command should be used with an existing certificate file (which should be in base 64 encoded format).
For example:
makekeys – view mycert.cer
Arguments
-cert
Create the private key (private-key-file) and self signed certificate (public-key-cert). If the private key file already exists it will be used to create the self signed certificate.
-req
Create a certificate request.
-view
View certificate details.
-v
Verbose mode — displays additional diagnostic information.
-dname distinguished-name-string
The distinguished-name-string specifies the distinguished name parameters required for the self-signed public key certificate file. This command line option should be constructed of a string of white space separated key/value pairs as follows:
CN=common name
OU=organisational unit
OR=organisation
LO=locality
ST=state
CO=country
EM=e-mail address
-password password
Password (optional). After creation, the password must be supplied to subsequently use the private key.
-len key-length
The key-length. The minimum is 512, maximum is 4096. The key length defaults to 1024.
-private-key-file
The file containing the private key. The private key should kept secret by the developer, whereas the public key is usually made generally available. Has a .key extension.
-public-key-cert
A self-signed certificate containing the public key. Has a .cer extension.
-cert-request-file
A self-contained file which is sent to the CA. The Certification Generator will create this file given a private and public key. It is then up to the developer to send the file to the CA and arrange for the application for the certificate. Has a .p10 extension.
Once created the certificates composed by the two files ( xxxxx.key xxxxx.cer ) you use them with the soft kvt ... where xxxxx is the name that you will have given to your certificate..
Regards
Regards
ragax |
Latest page update: made by ragax
, Apr 13 2007, 2:17 AM EDT
(about this update
About This Update
Edited by ragax
1227 words added 3 images added view changes - complete history) |
|
Keyword tags:
None
More Info: links to this page
|
There are no threads for this page.
Be the first to start a new thread.
