Unpack Chinese standard package: SISWareV4.7 Chinese Version (with MBM )**************** conversion tool License: SWW100501-B01712607-FNT325470 all external controls integrated runtime Make sure that the system version themes service turned on. Make sure the subject of a non (!) windows version of the classic formal SISWare4.7. (SIS)Class capacity update: The multi-level nested open the third edition of the sis file to improve the operations for the third edition sis file sis files nested tree view mode added (nested in tree view of the SIS mode control device) the third edition of the nested sis file export functions sis file installation method: Direct install MBM conversion tools | MBMConverter in BITMAP originally based on the successful implementation of an increase of THUMBNAILTWIP
PS:**********Symbian|SISWarev4.7SISWare Symbian
PS: About unpack package ********** Symbian Tools | SISWarev4.7SISWare is the best application of the Symbian tools installation package packing. Symbian sis sisx Applies to any Symbian version of the sis and sisx file.
General features include:
Open SIS file or files from sis package script packages SIS file editor to extract files or build scripts and reconstruction package compiled sis file or script.
The establishment of sis file Batch extraction options you can set a signature or cancel sis file signature, signature certificate can create their own software directly open the script file and the sis file through the establishment of the window make it easy to create sis file to extract files from sis any document, and a batch file to create a certificate signed sis, re-signed to remove the signature (the signature information out) S60v3 do not need the sis file script SDK tools to avoid errors associated to open after double-click the. sis, . sisx,. pkg,. txt,. ssd file-to-use script editor to support drag-and-drop operation of the compiler package script to revoke or to repeat the guidance of environmental input or to stop the closure of SISWare automatically create a temporary file clean-up complete cessation of function of the creation of SIS files into multi-level updates SISWarev3.8: sis file without extracting the whole through the appropriate procedure to open the sis file inside the package; the equipment platform symbian9.x from previous when migrated to symbian9.x to add the default editor vendor name and the name of the only vendors; correct sis file creation time of the month; correct entries editor input; new applications and associated files icon.
Download SISWare V4.7 Chinese Version
Version History
December 2005
SIM1.0 unreleased for publication/development project for SISWare
- Fine user GUI(Windows GUI not used)
- Standard makesis function for S60 1st and 2nd
- Not support sis file extraction and viewver
January 2006
SIM1.2 unreleased for publication/development project for SISWare
- PKG file openable
- makesis function
- Ignored user GUI
April 2006
SISWare1.0 released
- PKG file collection from S60 sis file
- sis file extraction ability
- PKG script compiler
May 2006
SISWare1.4 released
- PKG script compiler buxs fixed
July 2006
SISWare2.5 released
- PKG script compiler buxs fixed
December 2006
SISWare2.7 released
- New input form
January 2007
SISWare3.0 released
- sisx(series60 3rd edition) support
February 2007
SISWare3.5 released
- full sisx compilation support
March 2007
SISWare3.6 released
- Protected location guidance in entry editor input form
- sign and unsign tools bugs fixed
March 2007
SISWare3.8 released
- Open files in SIS contents by appropiate application without whole SIS file extraction
- Add default entry of local vendor name and unique vendor name to the editor when change device platform form pre-Symbian9.x to Symbian9.x
- Correct the month on sis creation time
- Correct the Entry editor input form
- New application and associated file icon
March 2007
SISWare3.9 released
- PKG file opening improvement
- Supported capabilities information for 3rd SIS file
- Recent file opening
March 2007
SISWare4.0 released
- Fixed PKG compiler for 3rd sis file
- 2 Modes added: View and Edit mode
- Show signatures in 3rd sis file
- Support PKG file in ANSI, UTF-8 and Unicode format
March 2007
SISWare4.2 released
- If statements buxs fixed (ElseIf syntax) for 3rd sis file openning
- Drag and Drop file supports for entry add under Quick Menu panel
April 2007
SISWare4.5 released
- SIS file extraction bugs fixed for Symbian9.x
- New file type .spf (SISWare package file) presented
- Extract none extension file support
- Save and Save As bugs fixed
- Improve undo/redo speed and undo limit is up to 255 events
May 2007
SISWare4.6 released
- Improve file openning for multi-level embedded 3rd sis file
- New Embedded sis file treeview (see the embedded SISController as tree) for 3rd sis file
- Embedded SIS file export for 3rd sis file
June 2007
SISWare4.7 released
- New Product / Platform ID's added, UIQ 3.0, UIQ 3.1 and Series60 v3
- PKG compiler bugs fixed for UIQ v3.x platform and signature strings
- UIQ 3.x sis file gathering information bugs fixed
K. Suwatchai, Cequenze Technology Inc.
Introduction
Thank you for using SISWare4.7 SISWare is the best tools for Symbian Application Install package builder. SISWare providing as freeware and usage limitation of this software described on License item. SISWare4.7 supports sisx and sis file creation and extraction for Symbian9.x and pre-version.
Standard features including:
- Open SIS file or pkg script file.
- Extract files from sis package.
- Edit SIS file or pkg script and re-build.
- Compile sis file or pkg script.
- Build sis file with multiple options.
- Batch extraction of multiple sis files.
- Sign and UnSign sis file and create self-signed certificate file.
What's new in SISWare4.7:
SIS Product string index bugs fixed, Unhandle index occurs when open multi string of SIS Product/ Platform ID which the pointer that indices to string array is not valid and make SISWare running out of step and lost of data.
Product Serial Number:
SWW100501-B01712607-FNT325470
Copy this serial number and paste to the authorization input form.
This serial number only use to prevent the crash of running SISWare in different version at the same time.
This package released on June 23, 2007 17.13 PM.
Release Note
More bugs and improvements were done as we are continuing to support and development of SISWare.
Thanks for your support
K. Suwatchai
System requirements
- Windows Me, 2000 or Windows XP
- CPU Pentium 200 MHz or higher
- 20 MB Hard Disk space
- 128 MB of RAM
Feedback
Contact developers and send feedback to k_suwatchai@hotmail.com
Thanks
Thanks for using SISWare.
All advise and comments will be useful for software improvement.
Thanks people who use my software.
K. Suwatchai, Cequenze Technology Inc.
(C) 2007 Cequenze Technology Inc.
A butt book is a book stored on the ambition accessory afterwards a amalgamation has been installed. It capacity which files were installed and where, and is acclimated to accredit the basic to be uninstalled. However, if an appliance on the accessory was not installed application a SIS book and has no butt file, you can use Butt SIS advantage to actualize a butt book for it. This is an avant-garde affection and not about acclimated by developers. SISWare supports the conception of butt files for admittance in the ROM. This is appropriate so that back installing fresh apparatus a analysis can be fabricated to ensure that a ROM based basic is not replaced by an earlier RAM based component
TCapability
Description
An archive that defines the set of all accurate capabilities.
ECapabilityTCB Grants address admission to executables and aggregate read-only resources.
This is the best analytical adequacy as it grants admission to executables and accordingly to their capabilities. It additionally grants address admission to the /sys and /resource directories.
ECapabilityCommDD Grants absolute admission to all advice accessory drivers. This includes: the EComm, Ethernet, USB accessory drivers etc.
ECapabilityPowerMgmt Grants the right:
to annihilate any activity in the arrangement to ability off bare peripherals to about-face the apparatus into standby accompaniment to deathwatch the apparatus up to ability the apparatus bottomward completely.
Note that this does not ascendancy admission to annihilation and aggregate that ability cesspool array power.
ECapabilityMultimediaDD Grants absolute admission to all multimedia accessory drivers.
This includes the sound, camera, video accessory drivers etc.
ECapabilityReadDeviceData Grants apprehend admission to arrangement operator, buzz architect and accessory arcane settings or data.
For example, the pin lock code, the account of applications that are installed.
ECapabilityWriteDeviceData Grants address admission to settings that ascendancy the behaviour of the device.
For example, accessory lock settings, arrangement time, time zone, alarms, etc.
ECapabilityDRM Grants admission to adequate content.
DRM (Digital Rights Managment) agents use this adequacy to adjudge whether or not an appliance should accept admission to DRM content. Applications accepted DRM are trusted to account the rights associated with the content.
ECapabilityTrustedUI Grants the appropriate to actualize a trusted UI session, and accordingly to affectation dialogs in a defended UI environment.
Trusted UI dialogs are rare. They charge be acclimated alone back acquaintance and aegis are critical; for example, for countersign dialogs.
Normal admission to the user interafce and the awning does not crave this capability.
ECapabilityProtServ Grants the appropriate to a server to annals with a adequate name.
Currently, adequate names alpha with a "!" character. The atom prevents servers afterwards this adequacy from appliance such a name, and accordingly prevents adequate servers from actuality impersonated.
ECapabilityDiskAdmin Grants admission to deejay adminstration operations that affect added than one book or one agenda (or all-embracing filesystem integrity/behaviour, etc).
For examples, reformatting a deejay partition.
ECapabilityNetworkControl Grants the appropriate to adapt or admission arrangement agreement controls.
Typically back an activity can change the behaviour of all absolute and approaching connections, it should be adequate by this capability.
For example, banishment all absolute admission on a specific agreement to be dropped, or alteration the antecedence of a call.
ECapabilityAllFiles Grants apprehend admission to the absolute book system; grants address admission to the clandestine directories of added processes.
This adequacy is actual carefully controlled and should not often be granted.
ECapabilitySwEvent Grants the appropriate to accomplishcomputer appliance key & pen events, and to abduction any of them behindhand of the cachet of the application.
Note that afterwards accepting the focus, accustomed applications do not charge this adequacy to be accomplished key and pen events.
ECapabilityNetworkServices A user adequacy that grants admission to alien casework afterwards any brake on its concrete location.
Typically, such a area is alien to the buzz user, and such casework may acquire amount for the buzz user.
Voice calls, SMS, and internet casework are acceptable examples of such arrangement services. They are accurate by GSM, CDMA and all IP carriage protocols including Bluetooth profiles over IP.
ECapabilityLocalServices A user adequacy that grants admission to alien casework in the abutting around of the phone.
The area of the alien account is acclaimed to the buzz user, and in best cases, such casework will not acquire amount for the buzz user.
ECapabilityReadUserData A user adequacy that grants apprehend admission to abstracts that is arcane to the buzz user.
This adequacy supports the administration of the user's privacy.
Typically, contacts, letters and accessories are consistently apparent user arcane data.
ECapabilityWriteUserData A user adequacy that grants address admission to user data.
This adequacy supports the administration of the candor of user data.
Note that this adequacy is not symmetric with the ECapabilityReadUserData capability. For example, you may appetite to anticipate rogue applications from deleting music advance but you may not appetite to bind apprehend admission to them.
ECapabilityLocation A user adequacy that grants admission to the area of the device.
This adequacy supports the administration of the user's aloofness with attention to the buzz location.
ECapabilitySurroundingsDD Grants admission to analytic accessory drivers that accommodate ascribe advice about the ambience of the device.
Good examples of drivers that crave this adequacy would be GPS and bionetrics accessory drivers. For circuitous multimedia analytic accessory drivers that accommodate both ascribe and achievement functions, such as Complete accessory driver, the MultimediaDD adequacy should be acclimated if it is too difficult to abstracted the ascribe from the ouput calls at its API level.
ECapabilityUserEnvironment Grants admission to alive arcane advice about the user and his/her actual environment. This adequacy assure the user's privacy.
Examples are audio, account and video recording, biometrics (such as claret pressure) recording.
Please agenda that the area of the accessory is afar from this capability. The aegis of this is accomplished by appliance the committed adequacy Location
ECapability_None Special amount acclimated to specify 'do not care' or 'no capability'.
ECapability_Denied Special amount acclimated to announce a adequacy that is never granted.
SISWare is the best SIS Editor for Symbian Application Install package builder.SISWare4.7 supports sisx and sis file creation and extraction for Symbian9.x and pre-version.
Donwload here
Developers can localise a C++ application by simply changing the resource file text associated with each menu item, task bar or other control. Since changes to the text do not change the symbol information in the generated header file, it is not necessary to recompile the application to use the new file. Consequently, a resource file may be generated for each language supported, and the actual resource used is determined by the end-user at installation time.
The examples quoted in this page are taken from the code example Examples\ToolsAndUtilities\Localise, which provides the Hello World application, localised for English and German.
Localisable strings
Localisable strings should not be defined within a resource file, but in separate files with the extension .rls. An .rls file defines symbolic identifiers for strings, to which the resource file refers when it needs the associated string.
An example from an .rls file is shown below:
// Strings localised for UK
rls_string STRING_r_example_first_menu_name "Hello"
rls_string STRING_r_example_item0 "Item 0"
The keyword rls_string appears before each string definition, followed by a symbolic identifier, and then the string itself in quotes. To localise the file for German, the same identifiers would be used, but the strings would be translated, i.e.
// Strings localised for German
rls_string STRING_r_example_first_menu_name "Hallo"
rls_string STRING_r_example_item0 "Eintrag 0"
The resource file itself would be the same, whatever the locale, as it would only refer to strings through their symbolic names, e.g.
MENU_TITLE
{
menu_pane=r_example_first_menu;
txt=STRING_r_example_first_menu_name;
}
defines a menu title resource, with a title string defined by STRING_r_example_first_menu_name (i.e. "Hello" in UK, "Hallo" in German).
Building localised resource files
You can define in a project definition (.mmp) file the locales that the project supports. Given appropriate resource source and .rls files, the build process then builds a separate compiled resource file for each supported locale.
The process in detail can be broken into three steps:
determine on a symbolic identifier for every supported locale
specify in the project definition file the supported locales
#include the .rls files for the supported locales in the resource source file
These are discussed further below.
Locale identifiers
You should decide on a symbolic identifier for every supported language. The symbol should be of the form:LANGUAGE_language-code
where language-code should be two characters long, but otherwise can be anything you like, as long as each language in the resource file has a unique symbol.
You are recommended to use a standard two-digit number as defined by Symbian in an enumeration TLanguage in e32std.h, which gives numeric values to the languages. For example, the value ELangGerman (German) in TLanguage has the value 3, so you could use LANGUAGE_03 as the symbol for German.
Alternatively, you can use logical letters for each language: e.g. US English might have the symbol LANGUAGE_US, while French might have the symbol LANGUAGE_FR.
Project definition files
For projects with localised resources, you must use the lang statement in the .mmp file to set the languages codes used. So, for the above example, in which the language codes used are for German (03) and UK English (01), the lang statement should read:
lang 01 03
When the project is built, each resource file specified in the project file will be compiled multiple times, once for each language-code specified. The language codes are used to complete the extension of the built resource files: for our example, two files would be built: project-name.r01 and project-name.r03.
Resource source files
The symbols can then used, with conditional compilation statements, to specify which string definitions should be compiled for each language. In the example code fragment below, the file 01-strings.rls is assumed to have the strings localised for UK English, and the file 03-strings.rls the strings localised for German.// Conditional compile, depending on locale
#ifdef LANGUAGE_01 // if language code is for UK
#include "01-strings.rls"
#elif defined LANGUAGE_03 // if language code is for German
#include "03-strings.rls"
#endif
// end conditional compile
when built with the code 01, the UK English strings in 01-strings.rls are compiled into the resource file
when built with the code 03, the German strings in 03-strings.rls are compiled into the resource file
How programs load resource files
The Uikon application framework attempts to load the project's resource file when the application starts up. If the resource file has the extension .rsc, then this is loaded. Alternatively, the framework attempts to load the correct resource file by comparing the system locale setting with the available resource files: for example, in a German locale, the resource file with extension .r03 would be loaded. Resource files that are explicitly loaded by programs, rather than by the framework, can use the same stategy, by calling BalfUtils::NearestLanguageFile() to find a resource file with the correct language extension.
More typically than installing all the resource files for all the available locales, you would only want to select a single resource file for installation, based on the system locale or user preference. The Symbian OS Installation System enables this, as described in How to create an installation file for a multilingual application.
Resource building is performed by the epocrc tool. It is a three-stage process:
- pre-processing
- localised string merging
- compilation to binary format
Pre-processing
Resource files can use the familiar pre-processor directives. In particular, #include is used to include header files; #define is used to define macros such as numeric constants; and #if and related directives can be used to perform conditional compilation. Pre-processor arguments for include file paths and macro definitions can be passed to the pre-processor through epocrc.
The source file is pre-processed, using the cpp pre-processor, and an output file produced with an extension .rpp.
Merging localised strings
Strings that should be localised should not be defined in the resource file itself, but in separate files with an .rls extension. The .rpp files are processed by epocrc to merge in the localisable strings.
A flag can also be specified to epocrc that causes it to copy the .rpp files into a epoc32\localisation\ directory, from where they can form input into a localisation kit.
Compilation to binary format
The final stage is to convert the intermediary .rpp files into the final compiled format. This is done by the rcomp tool. The resource compiler also produces a header file that contains a symbolic identifier for each resource.
The names of the output files are specified as parameters to epocrc. Note though that:
resource files as built by the project build tools (abld) have the default extension .rsc. The additional naming conventions used when you need to supply multiple resource files, each for a different locale, are discussed in How to localise resources
by convention, the header file has an extension .rsg
The identifiers in the header file provide symbolic names for index positions in the resource file, so that your source code can be independent of the number and order of resources within the file. For a named resource such as:
RESOURCE TBUF r_eik_bafl_error_offset { buf="Wrong format resource file"; }
the generated header file will have a #define such as:
#define R_EIK_BAFL_ERROR_OFFSET 0xf3b045
where the number is a resource ID which encodes the resource index, and is suitable for passing to the C++ function RResourceFile::AllocReadLC().
In the course of project development, changes to the resource file may not always result in changes to the set of #define statements generated. If there is no change, the rsg file is not rebuilt, thereby avoiding unnecessary re-compilation and linking.
Much of the information that defines the appearance, behaviour and functionality of a Symbian OS application is stored externally to the main body of the program, in a resource file. This is unlike some other programming environments, in which a single executable contains all the code and information used by the application. Resource files can have the advantages that information is loaded only when needed, which can reduce RAM requirements, they can be compressed, and they can be localised without needing to recompile the main program.
Resource files are developed as text files written in a Symbian OS-specific resource language. These source files are then compiled into a binary file format that can be loaded and read by programs. The source files can be compiled on their own using the command-line resource builder tool (epocrc), or as part of the standard project building process either from the command-line or from within an IDE.
Purposes of resource files
Resource files are used for the following purposes:
to define the application user interface. The C++ application programming framework requires that some aspects of an application’s layout and behaviour, such as the menu bars and dialogs, are defined in a resource file
to define application properties that are used by the application launcher or system shell.
Until v9.0, (.aif) are used to define the application's icon and caption, and various properties, for instance whether the application is exposed to users or hidden, whether the application can be embedded, and the priority at which the application should be associated with MIME data types.
From v9.0, aif files are replaced by application registration information. The caption and icon are defined either in a special resource file called a localisable icon/caption definition file, or, if more convenient, in the application's UI resource file. The application's properties and some other information is defined in another type of resource file called a registration file.
Literal strings and other constant data: for example, dialog text and error messages. The resource tool chain provides support for localisation of these.
File types reference
The resource compilation process uses a number of file types:
rss
resource source file
rls
defines localisable strings, for inclusion in the resource source file
h
header file, for inclusion in C++ file
rh
resource header, for inclusion in the resource source file
hrh
common C++ or resource header, for inclusion in either type of source file
rsg
resource header file output from the resource compiler
rsc
compiled resource file from the resource compiler
Standard features including:
- Open SIS file or pkg script file.
- Extract files from sis package.
- Edit SIS file or pkg script and re-build.
- Compile sis file or pkg script.
- Build sis file with multiple options.
- Batch extraction of multiple sis files.
- Sign and UnSign sis file and create self-signed certificate file.
SISWare4.6 Beta1 New Released (built 1042007 released 21/05/07)
This new version of SISWare added the function to automatic sign for Symbian9.x sis file when build.
Which can sign with the predefined certificate or self-sign certificate.
The certificate declares in pkg will be signed unless the promt to create self-signed certificate will show after the sis file has built.
This make sure sis file that build with SISWare will be signed even self-signed.
Download SISWare v4.6 Beta 1
1. Select Menu Extras --> Configurations.
2. From configurations window, on application setting group, check the item 'Use defined offset when export session'.
3. Uncheck item 'Extract all files to the same folder' and click OK button.
4. Open the SIS file.
5. Extract SIS file.
6. At this step, edit the PKG session as required.
7. If SIS file that opened(Item4) is Symbian9.x SIS file and that SIS file has embedded sis file(s)
(otherwise go to Item8)which you will see the multiple of tabs, the first tab
is the main sis file and the another one(s) is the embedded sis file which
within main sis file. To re-build up main sis file you must
re-build that embedded sis file(s)again by select that embedded sis file tab and build.
After the embedded sis file(s) was built then you are ready to re-package or re-build main sis file by select the first tab on the screen.
Before you start to re-build, make sure you have alter the path of embedded sis file(s) to the embedded sis file which you re-built and save to that path.
Note:
Due to 3rd sis file has embedded its embedded sis file as the contents which indices with SISController then you extract 3rd sis file that contains embedded sis file inside, all of embeded sis file will be extracted as contents in that embedded sis package. This perfom one extraction for all contents in main 3rd sis package. This unlike the older sis file version which its embedded sis file will be stored in the main sis package as sis file.
8. If SIS file that opened(Item4) is Pre-Symbian9.x sis file you can re-built it now by go to menu Tools -----> Build SIS File of Press F3
Introduction
In S60 3rd Edition application development all .sis files must be signed before installing them to a device. When an application requires no capabilities or utilizes APIs which are open to all, you can use the Self Signed certificate. This can be used when testing an application inone’s own device or when shipping the application. Using the Self Signed certificate is recommended for freeware applications using unrestricted capabilities.
Self Signed Certificate
When an application requires no capabilities or utilizes APIs, which are open to all. This can be used when testing an application in one’s own device or when shipping the application.
Note: The application is regarded as Untrusted if signed with the Self Signed Certificate.
This process is recommended for freeware applications using unrestricted capabilities(User grantable capabilities)
Developer Certificate
When testing the application in developer’s own device(s). This certificate is received from Symbian.
The Symbian Developer Certificate can be used by developers to sign their applications in order to obtain the restricted capabilities for device testing. The certificate is restricted to a certain set of IMEIs and the set cannot be changed. There are a few requirements to get a Symbian Developer Certificate.
Symbian Signed
Mandatory if the application is using capabilities beyond the scope of APIs open to all and the application is shipped.
This is the sets of certificates respeected to APIs utilized.
60% of APIs (no restricted certificate)
User-Grantable Capabilities (need atleast self signed certificate)
ReadUserData
WriteUserData
NetworkServices
LocalServices
UserEnvironment
Symbian Signed Capabilities (need Symbian signed certificate)
User-Grantable Capabilities + sets of following
Location
ReadDeviceData
WriteDeviceData
PowerMgmt
SurroundingsDD
ProtServ
TrustedUI
SwEvent
Licensee/Platform Approval Capabilities (need Symbian signed certificate)
Symbian Signed capabilities + sets of following
Manufacturer
DRM
TCB
S60
DiskAdmin
AllFiles
CommDD
MultiMediaDD
NetworkControl
For more access capabilities details see also Enum TCapability
Sign SIS file
To self-sign the sis file with SISWare you must have the key file(.key) and certificate file(.cer).
The key file and certificate file may be given Symbian Signed Certificate from trusted Certificate Authority such as Verisign
and Symbian Signed or create your own self-sign certificate
To use the SISWare's sign tool, go to menu Tools ---> Digitally Sign Tools.
At Sign SIS File tab, follow these steps.
1. Specifile original SIS to be signed, this file will not effacted by signing process. The result of signing process is the target signed sis file.
2. Specify the target sis file which will create.
3. Specify key file
4. specify certificate file
5. Specify password(if that certificate file encrypted with password)
6. Specify algorithm. If you use symbian tool named makekeys.exe (even use in SISware) to produce key and certificate file, please choose DSA algorithm because that file created with that algorithm.
7. Click Sign button.
If no error occurs the signing will complete with some signature information that given by certificate file that seen from Signing Info box. Then this signed sis file will be able to install to Symbian9.x OS devices.
Create self-sign certificate file
You can create your own key and certificate file to use in signing process and your sis file will be regarded as Untrusted. To create key and certifiate file, go to Create Self-Signed Certificate tab in Digitally Sign Tools window
SISware developed using the Visual Basic language. Then it needs the VB virtual machine and it's libraries for running. This version uses the open source components as makesis, makekeys and signsis from Symbian and zlib library for file extraction.
About Serial Number
SISWare distributed as freeware and running and using one serial number for each version then do not affraid about this serial number. This serial number only used to software crash prevention from running SISWare in difference version at the same time. And the serial number was included in the readme.txt document in the setup package. Everytime you newly install SISWare, it will ask you the serial code even you already installed current version of SISware before.
System requirements
- Windows Me, 2000 or Windows XP
- CPU Pentium 200 MHz or higher
- 20 MB Hard Disk space
- 128 MB of RAM
The above requirements is recommended for general use. The speed of data rendering may differ with RAM and CPU speed
Thank you for using SISWare4.2 SISWare is the best SIS Editor for Symbian Application Install package builder. SISWare distributed as freeware and usage limitation of this software described in the Licenses. SISWare4.2 supports sisx and sis file creation and extraction for Symbian9.x and pre-version. All SISWare features included in this help documentation.
Standard features including:
What's new in SISWare4.2:
