AThis help file consists of extracts from the Symbian EPOC SDK. All copyright is acknowledged.
This file has been provided with Neuon
s nSISUtil
a utility for the EPOC machine based creation of .PKG and .SIS files. nSISUtil is available from the Neuon site at www.neuon.com.
AA .pkg file is a text file which contains installation information for applications or files. It consists of the following sections, some of which may be omitted:
the languages supported
the installation header, including the name of the application or file which is being installed and its version information
the files to install a list of files of which only one will be installed, depending on the language chosen
dependencies
component
.sis file comments
CThe installation header must be included before all other items, except the language section, if one is specified. Its format is:
#{"Component Name for language1",..., "Component Name for language n"},(ComponentUID),Major,Minor,Variant
Note: The component name is language dependent. It is used in the dialogs displayed by EPOC Install during the installation process. It is also used to identify the application in the list of installed programs in the control panel's Add\remove program.
Note: The number of component names must equal the number of languages specified in the languages line.
Note: The variant number identifies the EPOC32 machine type on which the application can be installed. It will be used to ensure that an attempt to install an application on the wrong machine type will fail, but it is not currently used by the install programs.
AOne or more .sis component files may be included as part of the installation.
They are specified in the following way:
@"ComponentFile.sis",(UID)
For example:
@"ikmin.sis",(0x01000502)
The component filename must have a .sis extension. If more than one .sis file is specified, they are installed in the order in which they are listed. The UID may be found in the installation header in the .sis file's .pkg file.
Table1
title
synonym
Table1
ColA1
ColB1
ColA2
ColB2
ColA3
ColB3
ColA4
ColB4
Index1
ColA3
ZNThe files which will be installed regardless of the language variant selected by the end user, are specified as follows:
The source is the path and filename for the source file on the PC. The destination is the target path and filename on the EPOC32 machine. You must specify a filename in the destination unless the file is a text file.
Text files (indicated by an "FT" argument) are not installed, so their destination is irrelevant and may consist of empty quotes. If the appname directory does not exist, it will be created. Note that applications must be built to \system\apps\appname\appname.app.
Other component files which form part of the application, for example resource files and application information files should reside in the same directory as the application. If the file should be installed on a specific drive (c: for RAM, d: etc. for removable media), the drive letter should be specified, otherwise "!:" may be used to indicate that the drive can be specified by the user at installation time.
An optional comma separated list of arguments following the destination file may be specified, to describe the type of file and how it will affect the installation or removal process.
Use one of the following arguments to describe the type of file to install:
FF Standard file (the default)
FT Text file whose contents will be displayed in a dialog box during the installation. The dialog will contain either a "Continue" button (the default) or "Yes" and "No" buttons, depending on other arguments specified. Text files are not installed on the target machine.
FN A file which does not yet exist, so is not included in the .sis file. It is created by the running application and will be deleted when the application is removed. If this argument is specified, the name assigned to the source file is unimportant. Note that such files will not be deleted when upgrading to a later version. This ensures that such files as .ini files (which store application preferences) are not lost in an upgrade.
FR A file which will be run during installation and/or removal, depending on other arguments specified. This file will normally be an executable, a document or an application.It will be installed on the target machine.
Use one of the following arguments for a text file (i.e. after FT has been specified) to determine how the text file dialog should be cancelled, and how cancellation should affect the installation:
TC Use a "Continue" button in the text file dialog (the default). When the user presses this button the dialog is cancelled and the installation continues.
TS Use "Yes" and "No" buttons in the text file dialog. If "Yes" is pressed, the dialog is cancelled and the installation continues. If "No" is pressed, the dialog is cancelled, and the installation will continue, but the next file specified in the .pkg file will not be installed.
TA Use "Yes" and "No" buttons in the text file dialog. If "Yes" is pressed, the dialog is cancelled and the installation continues. If "No" is pressed, the installation is aborted.
One of the following arguments may be specified for a file which will be run during the installation or removal process (i.e. after "FR" has been specified). If the file is a document, the appropriate application will be launched. For example, on installation, you may want to open a WORD document providing information about the newly-installed application.
RI Run the file during installation only (the default).
RR Run the file during removal only.
RB Run the file during both installation and removal.
DThis format, rather than the one described in the previous section, is used to specify a list of files, of which only one will be installed, depending on the language selected by the user during installation:
Note: The opening brace denotes the start of the block of language-dependent files.
The order of the files should be the same as the order in which the languages were specified in the languages line. The number of files specified must be the same as the number of languages supported.
The arguments are the same as for the previous section.
This format will commonly be used to specify lists of resource files. Like applications, resource files must be built to \system\apps\appname\appname.rsc. If the appname directory does not exist, it will be created.
Here, three compiled resource files are specified, but only one will be installed on the target machine. Whichever language is chosen, the resource file will be installed as ikmin.rsc.
/CThe language line specifies which languages are supported. Languages are identified by a two character code. The line may be omitted; if so, UK English is assumed by default. The language line must be specified before any languages section (see "Files in different languages" below). Its format is as follows:
&Language, Language, Language
For example:
&EN,FR,IT
The following languages are supported:
EN UK English
FR French
GE German
SP Spanish
IT Italian
SW Swedish
DA Danish
NO Norwegian
FI Finnish
AM US English
SF Swiss French
SG Swiss German
PO Portuguese
TU Turkish
IC Icelandic
RU Russian
HU Hungarian
DU Dutch
BL Belgian Flemish
AU Australian English
BF Belgian French
GA German (Austria)
ED English (Newsealand)
IF International French
CZ Czech
SK Slovak
PL Polish
SN Slovakian
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
ContentsR
EPOC PKG & SIS Files!
IntroductionR
EPOC PKG & SIS Files!
LanguagesR
EPOC PKG & SIS Files!
Installation headerR
EPOC PKG & SIS Files!
Files to be installedR
EPOC PKG & SIS Files!
Files in different languagesR
EPOC PKG & SIS Files!
DependenciesR
A required file can be specified in the following way:
Would you like to install an EPOC help format file ("PKGSyntax.hlp" - 13k)
which contains details of the commands which can be used in a .PKG file?
If installed, it will be available from the menu item:
"Tools|Help on PKG Syntax..."7
0D:\Opl\Special\nSISUtil\Include\nSISUtil_Machine
MACHINE%
ER5.aifK
nSISUtil.aifK
ER5.mbmK
nSISUtil.mbmK
ER3.aifK
nSISUtil.aifK
ER3.mbmK
nSISUtil.mbmK
ER3.aifK
nSISUtil.aifK
ER3.mbmK
nSISUtil.mbmK
ER5.aifK
ER5.mbmK
ER3.aifK
ER3.mbmK
INSTALL%E
MACHINE%
<UPUUU
LPUUU
|dUDEETU
wwVEc
g6EEV$4#B
Z23##2
VefevgV4D
YCE4B22B3#3
wfe4#A
HUffTDESeU3C#
{STDU
l1TwVew
yvfgg
fvgfgU
wffeC
ivhwgwwvwgfw
Vfewwu
ISTTUeuUgt
ggfwgU
ZDffwg
vfVvgfv
i"DDTVU
Ydwwxf
hgwwfw
yUDDUV
yVUUTDd
$Cefw
"nSISUtil"nSISUtil
`fffff
`ffffff
`fffffff
`ffffff
`fffff
`ffff
03333
`ff033333
`ff03333
`f0333
`f033
`ffff
fffff0
`ff03
PUUU "
PUUU "
PUUU "
PUUU "
PUUU "
PUU "
UUUU"
UUUUU
|dUDEETU
wwVEc
g6EEV$4#B
Z23##2
VefevgV4D
YCE4B22B3#3
wfe4#A
HUffTDESeU3C#
{STDU
l1TwVew
yvfgg
fvgfgU
wffeC
ivhwgwwvwgfw
Vfewwu
ISTTUeuUgt
ggfwgU
ZDffwg
vfVvgfv
i"DDTVU
Ydwwxf
hgwwfw
yUDDUV
yVUUTDd
$Cefw
,f63,
ffb63
oollo
,f63,
ffb63
"nSISUtil"nSISUtil>application/pkg
D:\Opl\Special\nSISUtil\nSISUtilF
XSCREEN%
YSCREEN%
MACHINE%
TBARLINK
mbmKW
mbmKW8
rscKW
rscKW8
Machine.opoK
Z:\System\OPL\Toolbar.opo
+ LinknEDITO
Z:\System\OPL\Toolbar.opo
NEDITLINK
\System\Opm\+ nEdit.opm
\System\Opm\nEdit.opmW8
MainO
BACK_GND%
LOAD%
PKGALLOC&
PKGFILE$
SISFILE$
MBMFILE$
DEFPKGFOLDER$
DEFSISFOLDER$
DEFEXTFOLDER$
EVENT&
HELP_THREAD&
OPTIMISE%
SKIPSYNTAX%
REVERSE%
MAXFILES&
OPTIONS%
EXTRACTMODE%
CHANGED%
PKGFONT&
PKGSTYLE%
NEDITLANG
SPLASH%
INIT%
SISCREATOR%
OPENPKG%
EDITPKG%
NEWPKG%
MENU%
TBAROFFER%
KEYS%
KILL_HELP%
TBWINID%
TIM:O
O.hD[
PKGMenuO
PKGKeysO
.pkgW
.pkgK
PKGMenuO
PKGKeysO
'{A`[
O {IO
Oe{A[
KEYS%
LOAD%
hlpKW
PKGSyntax.hlpKW
+"C:\System\Apps\InstApp\InstApp.iniW
ABOUT%
HELP%
PREF%
INSTAPPPREF%
CREATESIS%
OPENPKG%
EDITPKG%
NEWPKG%
SIS_ANALYSER%
PKGFILE$
LOAD%
OA{A[
OH{A[
nSISUtilO
OP{A[
+ PKGSyntaxO
Ok{A[
OK{A[
Oc{A[E
PKGMenuO
PKGKeysO
Oe{A[
On{A[.
PKGMenuO
PKGKeysO
Oo{A[2
PKGMenuO
PKGKeysO
Oq{A[
Or{A[
KEYS%
KEYS%
KEYS%
MACHINE%
TBWIDTH%
TBBTH%
OcWX {O
OcWX {O
OcWX {O
EVENT&
KEYS%
KEYS%
OPTIMISE%
SKIPSYNTAX%
REVERSE%
MAXFILES&
DEFPKGFOLDER$
DEFSISFOLDER$
EXTRACTMODE%
DEFEXTFOLDER$
nMPDDCB
nMPDDCB
nMPDDCB
nMPDDCBO
PnMPDCCB+
nMPDPCCB
LANGUAGE%
DELSIS%
READINI%
WRITEINI%
nMPDDCB
nMPDDCBO
nMPDCCB+
nMPDPCCB
LANGUAGE%
DELSIS%
+"C:\System\Apps\InstApp\InstApp.iniW
+"C:\System\Apps\InstApp\InstApp.ini
+"C:\System\Apps\InstApp\InstApp.ini(
LANGUAGE%
DELSIS%
+"C:\System\Apps\InstApp\InstApp.ini(
NDIRNAVFILE$
SISCREATOR%
PKGFILE$
DEFPKGFOLDER$
h{A[q
SIZE&
MULTI&
TYPE&
LANGUAGE%
SRCFILE&
DESFILE&
TOTAL_FILES%
TOTAL_LANG%
CAPTIONS$
CAPTIONS%
HEADER&
GUESSMAXFILES&
READPKG%
BARCLOSE%
ERROR_LOG%
FREEALLOC%
MAXFILES&
GETFILENAME$
NEWBAR&
WRITE_SIS_FILE%
BARCLOSE%
SISFILE$
DEFSISFOLDER$
PKGFILE$
.sisK
GETFILENAME$
BARUPDATE%
WRITE_FILES%
TOTAL_LANG%
CAPTIONS$
TOTAL_FILES%
MULTI&
DESFILE&
OPTIMISE%
SRCFILE&
HEADER&
SISFILE$
LANGUAGE%
REVERSE%
TYPE&
SIZE&
P{IWC)
P{IWC(
LP{IW
P{IWCW
P{IWCW
P{IWCW
P{IWC_
P{IWC)
P{IWC_
P{IO O
P{IO O
P{IWC)
P{IWCW
P{IWCW
P{IWCW
P{IO O
P{IO O
P{IWC_
P{IWC
{QI L
P{IWC
P{IWC
P{IWC_
P{IWC_
P{I L
P{IWCW
P{IWC_
P{IO O
P{IWC
{QIWCI
P{IWC_
P{IO O
P{IWCI
P{IWC)
P{IWC
P{IO O
P{IWC
P{IO O
P{IWC)
P{IWCW
P{IWCW
P{IWCO
P{IWCW
P{IWC)
P{IWC
TOTAL_FILES%
REVERSE%
MULTI&
TOTAL_LANG%
SRCFILE&
TYPE&
P{IWC_
P{IWC
P{IWC_
P{IWC_
P{IWCW
GETFILENAME$
FF -)d
FT -)e
FN -)f
FR -)g
TC -)h
TS -)i
TA -)j
RI -)k
RR -)l
RB -)m
TOTAL_FILES%
SRCFILE&
DESFILE&
MULTI&
SIZE&
TYPE&
P{IWC
P{IWC
P{IWC_
P{IWC
NEWBAR&
SYNTAXCHECK%
BARUPDATE%
COMMENT%
GETSTRING$
COMPACT%
PARAMETER%
SISUID%
GETFILENAME$
CHECKUID&
PKGFILE$
SKIPSYNTAX%
TOTAL_LANG%
LANGUAGE%
CAPTIONS%
CAPTIONS$
HEADER&
SISFILE$
TOTAL_FILES%
SRCFILE&
DESFILE&
MULTI&
TYPE&
O$h@[.
_ E\[
Unknown language:
APPK)
)KO"W
_ E\[V
P{IWC
P{IWCW
P{IWC
_,A[X
P{IWCO
P{IWC(
P{IWC(
LP{IW
P{IWC(
LP{IW
)KO"W
P{IWC(
LP{IW
P{IWC(
P{IWC(
LP{IW
P{IWC
_,A[X
P{IWCO
)KO"W
_ E\[T
P{IWC
P{IWCO
P{IWC
P{IWCW
P{IWCW
)KO"W
P{IWCW
WC_(E
WC_0E
WC_)E
WC_)E
WC_;A
COMMENT%
WC_"E
WC_"E
WC_"E[
WC_,E\
WC_,E\
WC_,A[P
GETFILENAME$
NEDITREFRESH
PKGALLOC&
XSCREEN%
YSCREEN%
PKGFONT&
PKGSTYLE%
CHANGED%
WCE[^
(0x 0
(0x 0
(0x 0
GETFILENAME$
ERROR%
Edit+
Auto+
ErrorCCB
SENDEVENT%
ERROR%
TOTAL_FILES%
MULTI&
TOTAL_LANG%
SRCFILE&
TYPE&
P{IWC_
P{IWC(
LP{IW
P{IWC(
LP{IW
P{IWC_
P{IWC_
P{IWCW
P{IWCW
NEWBAR&
FINDFILE$
GETFILENAME$
BARUPDATE%
ERRORCCB%
BARCLOSE%
TOTAL_FILES%
MULTI&
TOTAL_LANG%
SRCFILE&
TYPE&
P{IWC_
P{IWC(
P{IWC_
P{IWC_
P{IWC
FINDFILE$
GETFILENAME$
NDIRNAVFILE$
SENDEVENT%
TOTAL_FILES%
MULTI&
TOTAL_LANG%
SRCFILE&
TYPE&
ERROR%
P{IWC_
P{IWC(
LP{IW
P{IWC(
P{IWC_
P{IWC_
P{IWCW
P{IWC
Os@[i
Ob@['
NDIRNAVFILE$
SISANALYSER%
SISFILE$
DEFSISFOLDER$
SISUID&
TOTAL_FILES%
TOTAL_LANG%
REQUISITES%
LANGUAGE%
INSTALLED_LANG%
INSTALLED_FILES%
INSTALLED_DRIVE%
CAPTIONS$
VERSION%
MULTI&
TYPE&
FILEDATA&
SIZE&
SRCFILE&
DESFILE&
PKGRECONSTRUCTOR%
SIS_EXPLORER%
FREEALLOC%
P{IWC
P{IWC
P{IWC
P{IWC
P{IWC_
P{IWCO
P{IWCO
P{IWC_
P{IWC)
P{IWCW
P{IWC
P{IWC
P{IWCO
P{IWC
P{IWCW
P{IWC
P{IWCO
P{IWCW
P{IWCW
P{IWC
P{IWCO
P{IWCW
P{IWC_
P{IWC
P{IWC)
P{IWC
CLOSEPKG%
STRING$
PARAMETER$
EDITPKG%
NEDITREFRESH
LOAD%
PKGALLOC&
CHANGED%
PKGFILE$
TOTAL_LANG%
LANGUAGE%
CAPTIONS$
SISUID&
VERSION%
TOTAL_FILES%
REVERSE%
MULTI&
TYPE&
SRCFILE&
DESFILE&
XSCREEN%
YSCREEN%
PKGFONT&
PKGSTYLE%
,(0x ^
P{IWC_
P{IWC_
P{IWCW
P{IWCW
}-O"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
}-O"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
},(0x n
P{IWCW
P{IWC_
P{IWCW
P{IWCW
}-O"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
}-O"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWC_
P{IWCW
-KO"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
-KO"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
,(0xK n
P{IWCW
P{IWC_
P{IWCW
-KO"W
P{IWCW
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
-KO"W
P{IWCW
P{IWCxO
P{IWCO
(0x f
P{IWCW
),K h
P{IWC}O
L{1[=
P{IWC
P{IWC
ReconstMenuO
ReconstKeysO
RECONSTKEYS&
CHANGED%
RECONSTSAVE%
RECONSTCLOSE%
CHANGED%
Os{A[$
Oe{A[
GETFILENAME$
TXTFILTER%
SAVE_FILE%
PKGFILE$
DEFPKGFOLDER$
SISFILE$
PKGALLOC&
CHANGED%
.pkgK
RECONSTSAVE%
CHANGED%
MODE%
GETFILENAME$
TOTAL_FILES%
SISFILE$
INSTALLED_FILES%
MACHINE%
XSCREEN%
ListBoxArray+
Info+
Extract+
W2|)G
W2|)H
W2|)~
O2|Jy
W2|)G
W2|)~
O2|Jy
LBCCB
GETFILENAME$
PARAMETER$
MODE%
TOTAL_FILES%
MULTI&
TYPE&
DESFILE&
TOTAL_LANG%
SIZE&
LANGUAGE%
SRCFILE&
P{IWC_
P{IWC_
P{IWCW
P{IWCW
P{IWC
{MWC}O
P{IWC
{MWC}O
)KO W
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
P{IWC
{MWC}O
P{IWC
{MWC}O
)KO W
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
P{IWC
{MWC}O
P{IWC
{MWC}O
)KO W
UID: &K D
P{IWCW
P{IWC_
P{IWCW
P{IWCW
P{IWC
{MWC}O
P{IWC
{MWC}O
)KO W
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
P{IWC
{MWC}O
P{IWC
{MWC}O
)KO W
P{IWCxO
P{IWCO
P{IWC_
P{IWC_
P{IWCW
P{IWCW
P{IWC}O
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWC}O
P{IWCxO
P{IWCO
P{IWCW
P{IWC}O
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWC}O
UID: &K D
P{IWCW
P{IWCW
P{IWC}O
UID: &K D
P{IWCW
P{IWC_
P{IWCW
P{IWCW
P{IWC}O
P{IWCxO
P{IWCO
P{IWC_
P{IWCW
P{IWCW
P{IWC}O
P{IWCxO
P{IWCO
P{IWCW
P{IWCW
UID: &K 8
P{IWCW
P{IWC_
+ Callback W
LISTBOXARRAY%
EXTRACTFILE%
GETFILENAME$
GETDRIVES$
READ_FILE%
SAVE_FILE%
EXTRACTMODE%
TYPE&
DEFEXTFOLDER$
SRCFILE&
DESFILE&
MULTI&
TOTAL_LANG%
LANGUAGE%
FILEDATA&
SIZE&
SISFILE$
P{IWC_
P{IWC_
P{IWCW
P{IWCW
P{IWC_
P{IWC_
P{IWCW
P{IWCW
P{IWC_
P{IWC_
C:\ X
P{IWCW
C:\ Z
P{IWCW
!:\C[
P{IWC_
P{IWC)
P{IWC_
,...K
P{IWC_
P{IWC)
P{IWC_
,...K
P{IWC_
P{IWC
P{IWC
P{IWC_
P{IWC
P{IWC
P{IWC_
P{IWC)
INFOTEXT%
TYPE&
MULTI&
SRCFILE&
TOTAL_LANG%
LANGUAGE%
SIZE&
INSTALLED_FILES%
DESFILE&
P{IWC_
P{IWC)
P{IWC_
P{IWCW
):K /
P{IWC
{MWC}O
bytesK
P{IWC_
P{IWCW
P{IWC}O
bytesK
P{IWC_
P{IWC)
P{IWC_
P{IWCW
):K /
P{IWC
{MWC}O
bytesK
P{IWCW
P{IWC}O
bytesK
P{IWC_
P{IWCW
):K /
P{IWC
{MWC}O
bytesK
P{IWC_
P{IWCW
P{IWC}O
bytesK
P{IWC)
):K 5
P{IWC
UID: &K '
P{IWCW
READ_FILE%
TXTFILTER%
MULTI&
TOTAL_LANG%
LANGUAGE%
SIZE&
FILEDATA&
SISFILE$
MACHINE%
P{IWC_
,...K
P{IWC
P{IWC
{MWCO
P{IWC_
P{IWC
P{IWCO
nMPDCCB+
nMPDPCCB
PKGALLOC&
NDIRNAVFILE$
READ_FILE%
TXTFILTER%
PKGFILE$
DEFPKGFOLDER$
LOAD%
PKGALLOC&
CHANGED%
h{A[N
SAVEPKG%
CHANGED%
STRING$
LOAD%
PKGALLOC&
CHANGED%
TXTFILTER%
SAVE_FILE%
SAVEPKGAS%
LOAD%
PKGFILE$
PKGALLOC&
CHANGED%
GETPKGNAME$
TXTFILTER%
SAVE_FILE%
PKGFILE$
DEFPKGFOLDER$
PKGALLOC&
.pkgK
PKGALLOC&
O@{1\[:
NEDITOFFER%
NEDIT_LINES%
NEDITMULTI
GOTOLINE%
NEDITCURSOR
NEDITOFFER%
NEDITOFF
XSCREEN%
YSCREEN%
PKGALLOC&
PKGFONT&
NEDITCHANGED%
CHANGED%
LOAD%
'{A`[
{A\`[
OM{IO
{A\`[
Om{IO
O {IO
PKGKEYS&
CHANGED%
NEDITSEL%
+"C:\System\Apps\InstApp\InstApp.iniW
Oqh)~
OCh)t
Iix)\
CLOSEPKG%
NEWPKG%
NEDITREFRESH
GOTOLINE%
OPENPKG%
SAVEPKG%
SAVEPKGAS%
PARAMETERHLP%
KEYS%
NEDITCMD
PKGFILE$
XSCREEN%
YSCREEN%
PKGFONT&
PKGSTYLE%
CHANGED%
hlpKW
PKGSyntax.hlpKW
Oe{A[
On{A[H
Oo{A[F
Os{A[4
OS{A[
OH{A[
IxWX
OP{IO
OH{IO
Ol{A[
Ox{A[
Oc{A[
Ov{A[
Oa{A[
OC{A[
Om{A[R
OM{A[R
TXTFILTER%
SAVE_FILE%
NEWBAR&
SYNTAXCHECK%
BARCLOSE%
NEDITREFRESH
GOTOLINE%
PKGALLOC&
XSCREEN%
YSCREEN%
PKGFONT&
PKGSTYLE%
C:\System\Temp\
C:\System\Temp\
COMMENT%
ALERT%
BARUPDATE%
GETSTRING$
WTDO%
PARAMETER%
SISUID%
CHECKUID&
O$h@[+
#KO"W
#KO"W
{KO"W
{KO"W
_"A[#
}KO"W
}KO"W
P{E[O
,KO"W
,KO"W
_,A`[
(KO"W
(KO"W
)KO"W
)KO"W
_ E\[
-KO"W
-KO"W
_"A`[
@KO"W
@KO"W
_{A`[
}KO"W
}KO"W
,KO"W
,KO"W
(KO"W
(KO"W
)KO"W
)KO"W
( or )KO"W
( or )KO"W
}KO"W
}KO"W
-KO"W
-KO"W
0KO"W
0KO"W
XKO"W
XKO"W
)KO"W
)KO"W
_ E\[
KO"W
KO"W
,KO"W
,KO"W
{KO"W
{KO"W
,KO"W
,KO"W
}KO"W
}KO"W
,KO"W
,KO"W
(KO"W
(KO"W
)KO"W
)KO"W
( or )KO"W
( or )KO"W
FINDFILE$
GETFILENAME$
NDIRNAVFILE$
PKGALLOC&
CHANGED%
Ob@[w
TEMP$
DNCCB+ DNCloseCB
GETFILENAME$
TEMP$
+ Callback W
+ Callback W
EXTRACTMODE%
GETFILENAME$
:\C[E
O0{=
O9{5\
Oa{=
Of{5\`
OA{=
OF{5\`[
O0{=
O9{5\[
GETDRIVES$
SENDEVENT%
{M1[2
,...K
O!hDW
MBMFILE$
LOFLO
100%W2O
{IWC}
VOd|RO
OUOUOU
O \[A
OUOUOU
O \[a
OUOUOU
OUOUOU
OUOUOU
XSCREEN%
MBMFILE$
YSCREEN%
nSISUtil+
1.30K
HO0HO
O0O0O
02.08.2000
Email: jens@neuon.com
URL: http://www.neuon.com
1998-2000 Jens Kaminski & Neuon
BACK_GND%
XSCREEN%
YSCREEN%
MBMFILE$
Z:\System\Data\Eikon.mbmO
W.W/O
nSISUtil
EPOC installation file utility
+'Generates SIS files on your EPOC device
MBMFILE$
LO0LO
O0O0O
LW/O?LO
1.30K
W2LO0LO
1998-2000 Jens Kaminski & Neuon
jens@neuon.com
www.neuon.com
HELP_THREAD&
.hlpK
HELP_THREAD&
PKGFILE$
SISFILE$
DEFPKGFOLDER$
DEFSISFOLDER$
DEFEXTFOLDER$
OPTIMISE%
SKIPSYNTAX%
REVERSE%
EXTRACTMODE%
PKGSTYLE%
PKGFONT&
MAXFILES&
C:\System\Apps\nSISUtil\
+$C:\System\Apps\nSISUtil\nSISUtil.ini
TBARINIT
TBARINITC
BGRND%
TBARBUTT
TBARSHOW
MACHINE%
XSCREEN%
YSCREEN%
MBMFILE$
nSISUtilO
nSISUtilO
nSISUtilO
LINKTBAR5
LINKNEDIT
MAINU
MENU%>
KEYS%
CMDN%
CMDO%
CMDC%
CMDX%1
CMDQ%U
CMDK%w
PREF%
INSTAPPPREF%
READINI%
WRITEINI%
CREATESIS%\
SISCREATOR%Y
SIS%a
WRITE_SIS_FILE%@
WRITE_FILES%D&
COMPACT%
PARAMETERHLP%d)
FREEALLOC%l*
READPKG%@+
GUESSMAXFILES&fD
UID&CE
COMMENT%jF
GETSTRING$
PARAMETER%
CHECKUID&
SISUID%
ERROR_LOG%
ERRORCCB%
AUTO%DR
EDIT%>T
SIS_ANALYSER%
SISANALYSER%
PKGRECONSTRUCTOR%
RECONSTMENU&]m
RECONSTKEYS&
RECONSTSAVE%Jn
RECONSTCLOSE%go
SIS_EXPLORER%5p
LISTBOXARRAY%
LBOXCALLBACKMANAGER%E~
LBCCB%
EXTRACT%
EXTRACTFILE%3
INFO%
INFOTEXT%
STRING$
PARAMETER$I
LNG$x
TXTFILTER%
OPENPKG%
CLOSEPKG%
NEWPKG%
SAVEPKG%
SAVEPKGAS%
GETPKGNAME$
GOTOLINE%
EDITPKG%
PKGMENU&x
PKGKEYS&7
ESC%>
SYNTAXCHECK%
WTDO%
NDIRNAVFILE$
DNCLOSECB%
DNCCB%
DNAVCALLBACKMANAGER%
NMPDCALLBACKMANAGER%
PNMPDCCB%R
NMPDCCB%
NMPDPCCB%
NMPDDCB%
FINDFILE$
GETDRIVES$
GETFILENAME$
READ_FILE%
SAVE_FILE%
SENDEVENT%I
ALERT%
NEWBAR&
BARUPDATE%
BARCLOSE%
ABOUT%T
BGRND%
SPLASH%
HELP%]
KILL_HELP%
INI%
INIT%
SYSTEM\
NMPD@M
NDISKTOOLS~e
NDIRNAV>M
NLISTBOX=M
NEUON<M
*#{*}*
application/pkg
EUSER[100000c1].DLL
APMIME[100012c3].DLL
EFSRV[100000bd].DLL
000D0T0`0l0x0
1,2024282x2
3 3,383D3P3\3h3t3
3H4L4P4T4X4d4h4
"DATA.APP)@
AYou can learn more about our dynamic company, and expanding EPOC software portfolio, from Neuon's web site at http://www.neuon.com
If you are a visionary C++, Java or OPL32 developer, motivated by doing something different, excited by challenges, relish the prospect of working with kindred spirits, and recognise the value of a dedicated support team, Neuon would like to hear from you.
Neuon - where innovation and quality are principles, not an afterthought
DnSISUtil enables .PKG/.SIS file creation and editing on an EPOC device. The main purpose for nSISUtil is to allow EPOC developers to create .SIS files on an EPOC platform without having to use a PC. This then enables developers to update applications on the net using only an EPOC device, for example.
This help file assumes that the developer has an understanding of the principle concepts of using .PKG and .SIS files. It is not the purpose of nSISUtil to be a tutorial for the creation of .PKG and .SIS files. However, for ease of reference, extracts from the Symbian EPOC SDK on PKG syntax have been included in the file PKGSyntax (in EPOC help file format). This is an option during installation and is installed to the \System\nSISUtil\ folder.
If you intend creating a .SIS file which embeds another .SIS file, you should read the topic .SIS and the Shared Module Problem.
After starting nSISUtil, use:
PKG | New Ctrl+N to create a new .PKG file
PKG | Open Ctrl+O to open an existing .PKG file.
PKG | Recreate Ctrl+R to recreate a .PKG file from a .SIS file.
SIS | Create Ctrl+C to create a .SIS file.
SIS | Explore Ctrl+Q to explore a .SIS file and extract and/or read any included files.
AA .PKG file must first exist before a .SIS file can be created. nSISUtil provides the option to create a new .PKG file, or edit an existing one.
To Create a new .PKG file, use the menu item PKG | Open (Ctrl+N).
To open an existing .PKG file, use the menu item PKG | Open (Ctrl+O)
For assistance with the syntax used in .PKG files, read the optional help file PKGSyntax in the \System\nSISUtil\ folder
BnSISUtil offers the option to recreate a .PKG file from the information contained in a SIS.file. The .SIS file may either be a complete .SIS which has yet to be installed, or the .SIS stub file which remains in a \System\Install\ folder after installation.
To recreate a .PKG file, use the menu item PKG | Recreate (Ctrl+R)
In the folder navigator, select the .SIS file from which you want to reconstruct the .PKG data.
Tip: In the navigator, you can change drives using the Tab key
The reconstructed .PKG file will be displayed.
Important: Before saving the data to a new .PKG file, you should check the reconstructed data as multi-language filenames cannot be reconstructed completely
Use Save to PKG (Ctrl+S) to save the reconstructed data to a .PKG file.
]ATo create a .SIS file:
A .PKG file must first have been created (see the topic Open/Create .PKG).
Use the menu item SIS |Create Ctrl+C and select a .PKG file in the folder navigator.
Tip: In the navigator, you can change drives using the Tab key
Enter a filename for .SIS file.
A message will appear if the .SIS file has been successfully created.
AThis software has been extensively tested and no problems have been found.
However, neither the Author nor Neuon warrant that this software is error free. In no event shall the author or Neuon be liable for any consequential, special, incidental or indirect damages of any kind arising out of the delivery, performance or use of the software, even if the Author or Neuon have been advised of the possibility of such damages.
Use of this software is entirely at the Users risk.
Table1
title
synonym
Table1
ColA1
ColB1
ColA2
ColB2
ColA3
ColB3
ColA4
ColB4
Index1
ColA4
LIf you are creating a .SIS which embeds another .SIS file (e.g. your .PKG file contains an entry like @
Another.sis
,(0x00000000), you should be aware of the following. In this explanation, module.sis applies to any embedded .SIS inside a parent .SIS.
1. The embedded method of .SIS incorporation has limitations, which are of note for shared modules (typically a shared.opx) which are packaged in their own separate shared module.SIS file.
2. After an installation, a residual .SIS stub is created in \system\install\ for the dependant parent .SIS and for each of its embedded shared module.SIS. These stubs contain important information for use by EPOC Install and the Control panel option 'Add/Remove'.
3. To ensure that
1) any shared module is only removed when no other dependant application requires it, and...
2) the user is warned that removing the shared module directly may break other applications,
requires every .SIS stub for a dependant parent .SIS to be in C:\system\install\.
It does not matter on which drive the .SIS stub for any embedded shared module.SIS is located, nor does it matter on which drive the dependant applications or shared module(s) are located. The key requirement is that the .SIS stub for the dependant parent is in C:\system\install\.
4. Unfortunately, this cannot be guaranteed for two reasons:
1) Unlike installations on the machine itself, which always use C:\system\install\, the PC based EPOC Install program places .SIS stubs in the \system\install\ folder dependent on the options originally used in the parent.sis .PKG file. If all files can be installed on an optional drive selected by the user, this same drive is used for the .SIS stubs. If this is D, then the .SIS stubs are placed in D:\system\install\. The same is true if the .PKG file mandates that all files must be on drive D.
2) Users may move .SIS stubs from C:\system\install\ to D:\system\install\, partly prompted by what EPOC Install may have done.
When the last dependant parent.SIS stub in C:\system\install\ is removed, or there are no dependant parent .SIS stub in C:\system\install\, removing a parent app.SIS will mean that shared modules will be deleted, or no warning given, even if a dependant app remains on the machine.
So, what does this mean?
When your app depends on a shared module, in order to ensure that the removal of your application does not break someone else's which also uses the same shared module, this three point plan is recommended:
1. You exploit the EPOC Install behaviour which forces the parent .SIS stub to be placed in C:\system\install\, even if the drive location for all other files was drive D, by choice or by design. This is done by including one option in the parent .PKG file which has a hard-coded drive of C. Some possibilities are:
a. To include a real file which is installed on drive C
"some real file"-"C:\some folder\some real file",FF
b. To specify a deletion requirement, when the app is removed, for a real or bogus file on drive C
""-"C:\system\apps\myapp\myapp.ini",FN
""-"C:\bogus stub fix",FN
2. You embed the shared module.SIS in the parent .SIS file
shared.sis
,(0x00000000)
3. Users are advised not to move any parent .SIS stub.
pBThe menu item Tools | Preferences provides options to customise nSISUtil
s operation. These options are provided for advanced users only.
Optimise removes the source file path. This will make the .SIS file a bit smaller.
Skip syntax check prevents nSISUtil performing a syntax check while analysing a .PKG file.
Reverse files makes nSISUtil process the files which were defined in the .PKG in the reverse order.
Max files sets the maximum number of files which can be defined in a .PKG (the default = 128). Changing this number will affect the memory used by nSISUtil. More memory is used the greater the maximum limit.
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Swiss
Arial
Arial
Arial
Arial
Arial
Arial
Arial
AThe Author would like to express his thanks to the following people, without whom nSISUtil would never have been the application it is today:
Beta testing:
Ralph Sprenger
Henry Hirst
Ben Vaisvil
Phil Spencer
Support:
Special thanks to Henry Hirst, Alex Wilbur & Richard Betts for the five OPX's used, the first four of which are publicly available from the Neuon web site www.neuon.com
nListbox.OPX
nDirNav.OPX
nMPD.OPX
nDiskTools.OPX
Neuon.OPX
About NeuonR
NSISUtil!
Welcome to nSISUtilR
NSISUtil!
PreferencesR
NSISUtil!
Open/Create .PKGR
NSISUtil!
Recreate .PKGR
NSISUtil!
Create .SISR
NSISUtil!
Explore .SISR
To explore a .SIS file, use the menu item SIS | Explore (Ctrl+Q). After selecting the required .SIS file in the folder navigator, the contents of the .SIS file will be displayed.
Tip: In the navigator, you can change drives using the Tab key
NSISUtil!
Licence and DistributionR
{nSISUtil is copyright (c) Jens Kaminski and Neuon 1998-2000. nSISUtil is provided as freeware, subject to the Disclaimer.
NSISUtil!
DisclaimerR
NSISUtil!
Contacting the AuthorR
If you wish to contact the author, Jens Kaminski, for more information concerning nSISUtil, to report any bugs, or just for a chat:
Email - jens@neuon.com
ICQ - 4681731
NSISUtil!
CreditsR
NSISUtil!
".SIS and the shared module problemR
NSISUtil!
Installer preferences5
This option can be accessed in Tools | Installer preferences on the menu.
This allows you to change the settings of the Installer, such as:
Delete .SIS installation file?
Prefered language
NSISUtil!
"DATA.APP)@
Table1
ColA1
ColB1
ColA2
ColB2
ColA3
ColB3
ColA4
ColB4
Index1
ColA4
Table1
title
synonym
ADies erm
glicht Ihnen die Einstellungen der Systemsteuerung "Hinzu./Entf." zu
ndern, wie z.B.:
Automatisches l
schen der .SIS-Installationsdatei nach der Installation (spart Speicherplatz).
Standard Sprache, die bei der Installation benutzt werden soll.
ASie k
nnen mehr
ber unsere dynamische Firma und unser EPOC Softwareangebot lernen, wenn Sie unsere Homepage besuchen, unter http://www.neuon.com.
Wenn Sie ein vision
rer C++, Java oder OPL32 Entwickler sind, der motiviert ist etwas v
llig anderes zu tun, der nach Herausforderungen sucht und der den Wert von Teamarbeit sch
tzt, der sollte sich bei Neuon melden.
Neuon - wo Innovation und Qualit
t Prinzipien sind und keine leere Idee
ZADie Basis zur .SIS Erstellung bildet die .PKG Datei.
Um eine neue .PKG-Datei zu erstellen, w
hlen Sie im Menu PKG | Erstellen (Ctrl+N).
Um eine existierende .PKG-Datei zu editieren, w
hlen Sie im Menu PKG |
ffnen (Ctrl+O)
Wenn Sie Hilfe zur Syntax der .PKG-Dateien ben
tigen, lesen Sie die optionale Hilfe PKGSyntax im Ordner \System\nSISUtil\.
DnSISUtil erm
glicht es Ihnen .PKG/.SIS Dateien auf Ihrem EPOC Ger
t zu erstellen und zu editieren. nSISUtil wurde geschrieben um EPOC Entwicklern die M
glchkeit zu geben .SIS Dateien direkt auf einem Psion zu erstellen, ohne die Hilfe eines PCs.
Diese Hilfedatei geht davon aus, dass der Benutzer ein grobes Verst
ndnis mit dem Umgang von .PKG und .SIS Dateien hat. nSISUtil ist nicht daf
r gedacht, eine Anleitung f
r die Erstellung von .PKG und .SIS Dateien zu sein. Um aber den Umgang mit nSISUtil zu erleichtern, wurde ein Ausschnitt aus dem Symbian EPOC SDK
ber die PKG Syntax in der Datei PKGSyntax (im EPOC Hilfe-Dateiformat) optional mitinstalliert.
Wenn Sie beabsichtigen eine .SIS Datei zu erstellen, die eine andere .SIS Datei beinhaltet, sollten Sie das Kapitel .SIS and the shared module problem lesen.
Nach dem Starten von nSISUtil, Umgang:
PKG | Neu Ctrl+N erstellen einer neuen .PKG Datei.
PKG |
ffnen Ctrl+O
ffnen einer vorhandenen .PKG Datei.
PKG | Wiederherstellen Ctrl+R wiederherstellen einer .PKG Datei aus den Informationen der .SIS Datei.
SIS | Erstellen Ctrl+C erstellen einer .SIS Datei.
SIS | Explore Ctrl+Q untersuchen eine .SIS Datei, mit extrahieren und lesen der enthaltenen Dateien.
tigen, lesen Sie die optionale Hilfe PKGSyntax im Ordner \System\nSISUtil\.
dieser Software erfolgt auf eigene Verantwortung.
LIf you are creating a .SIS which embeds another .SIS file (e.g. your .PKG file contains an entry like @
Another.sis
,(0x00000000), you should be aware of the following. In this explanation, module.sis applies to any embedded .SIS inside a parent .SIS.
1. The embedded method of .SIS incorporation has limitations, which are of note for shared modules (typically a shared.opx) which are packaged in their own separate shared module.SIS file.
2. After an installation, a residual .SIS stub is created in \system\install\ for the dependant parent .SIS and for each of its embedded shared module.SIS. These stubs contain important information for use by EPOC Install and the Control panel option 'Add/Remove'.
3. To ensure that
1) any shared module is only removed when no other dependant application requires it, and...
2) the user is warned that removing the shared module directly may break other applications,
requires every .SIS stub for a dependant parent .SIS to be in C:\system\install\.
It does not matter on which drive the .SIS stub for any embedded shared module.SIS is located, nor does it matter on which drive the dependant applications or shared module(s) are located. The key requirement is that the .SIS stub for the dependant parent is in C:\system\install\.
4. Unfortunately, this cannot be guaranteed for two reasons:
1) Unlike installations on the machine itself, which always use C:\system\install\, the PC based EPOC Install program places .SIS stubs in the \system\install\ folder dependent on the options originally used in the parent.sis .PKG file. If all files can be installed on an optional drive selected by the user, this same drive is used for the .SIS stubs. If this is D, then the .SIS stubs are placed in D:\system\install\. The same is true if the .PKG file mandates that all files must be on drive D.
2) Users may move .SIS stubs from C:\system\install\ to D:\system\install\, partly prompted by what EPOC Install may have done.
When the last dependant parent.SIS stub in C:\system\install\ is removed, or there are no dependant parent .SIS stub in C:\system\install\, removing a parent app.SIS will mean that shared modules will be deleted, or no warning given, even if a dependant app remains on the machine.
So, what does this mean?
When your app depends on a shared module, in order to ensure that the removal of your application does not break someone else's which also uses the same shared module, this three point plan is recommended:
1. You exploit the EPOC Install behaviour which forces the parent .SIS stub to be placed in C:\system\install\, even if the drive location for all other files was drive D, by choice or by design. This is done by including one option in the parent .PKG file which has a hard-coded drive of C. Some possibilities are:
a. To include a real file which is installed on drive C
"some real file"-"C:\some folder\some real file",FF
b. To specify a deletion requirement, when the app is removed, for a real or bogus file on drive C
""-"C:\system\apps\myapp\myapp.ini",FN
""-"C:\bogus stub fix",FN
2. You embed the shared module.SIS in the parent .SIS file
shared.sis
,(0x00000000)
3. Users are advised not to move any parent .SIS stub.
BUnter Tools | Einstellungen k
nnen spezielle Funktionsweisen von nSISUtil eingestellt werden. Diese Optionen sollten nur von erfahrenen Benutzern ver
ndert werden.
Optimiere .SIS-Datei entfernt die Quellpfade in der .SIS Datei und reduziert dadurch etwas die Dateigr
berspringe Syntaxs
berpr
fung h
lt nSISUtil davon ab, die Syntax der .PKG Datei zu
berpr
Dateien r
rts verarbeiten veranlasst nSISUtil die Dateien in umgekehrter Reihenfolge in die .SIS zu schreiben.
Maximale Dateien legt fest, wieviele Dateien in einer .PKG Datei definiert werden k
nnen (default = 128). Dies ver
ndert den Speicherbedarf von nSISUtil. Je h
her die Zahl desto gr
er der Speicherbedarf.
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
TCnSISUtil bietet ihnen die M
glichkeit, eine .PKG-Datei, auf Basis einer .SIS Datei zu rekonstruieren. Die .SIS-Datei kann dabei sowohl eine vollst
ndige .SIS-Datei sein, oder ein Installations-Log, welches Sie im Ordner \System\Install\ finden.
Um eine .PKG-Datei zu rekonstruieren, w
hlen Sie im Menu PKG | Wiederherstellen (Ctrl+R)
In dem darauf folgenden Dialog w
hlen Sie die .SIS-Datei, aus der Sie die .PKG-Datei wiederherstellen m
chten.
Tip: In diesem Dialog k
nnen Sie die Laufwerke
ber die Tab Taste
ndern.
Die wiederhergestellte .PKG-Datei wird im Anschlu
angezeigt.
Wichtig: Bevor Sie die .PKG-Datei speichern, sollten Sie deren Inhalt
berpr
fen, da mehrsprachige Dateinamen nicht komplett wiederhergestellt werden k
nnen.
Um die wiederhergestellten Informationen in einer .PKG-Datei zu speichern, w
hlen Sie .PKG Speichern (Ctrl+S).
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
Arial
ADiese Software wurde ausgiebig getestet und es wurden keine Fehler festgestellt.
Weder der Author noch Neuon k
nnen garantieren, da
diese Software fehlerfrei ist. Bei Datenverlusst oder Besch
digung kann in keinem Fall weder der Author noch Neuon Haftung
bernehmen, selbst wenn der Author oder Neuon
ber die M
glichkeiten solcher Auswirkungen informiert worden sind.
Die Benutzung dieser Software erfolgt auf eigene Verantwortung.
ADer Author m
chte sich bei allen bedanken, die bei der Entwicklung von nSISUtil behilflich waren:
Beta Test:
Ralph Sprenger
Henry Hirst
Ben Vaisvil
Phil Spencer
Support:
Speziellen Dank an Henry Hirst, Alex Wilbur & Richard Betts f
r die f
nf OPX's, die ich benutze, vier davon sind frei zug
nglich
ber die Neuon Webseite www.neuon.com.
nListbox.OPX
nDirNav.OPX
nMPD.OPX
nDiskTools.OPX
Neuon.OPX
AEine .SIS-Datei erstellen:
Als allererstes m
ssen Sie eine .PKG-Datei erstellen (siehe
ffnen/erstellen von .PKG-Dateien).
hlen Sie im Menu SIS |Erstellen Ctrl+C und w
hlen Sie in dem Dialog eine .PKG-Datei aus.
Tip: In diesem Dialog k
nnen Sie die Laufwerke
ber die Tab Taste
ndern.
Geben Sie nun einen Namen f
r die .SIS-Datei an.
Ein Folgedialog best
tigt den erfolgreichen Abschlu
der Operation.
Arial
ber NeuonR
NSISUtil!
Willkommen zu nSISUtilR
NSISUtil!
EinstellungenR
NSISUtil!
ffnen/Erstellen von .PKG-DateienR
NSISUtil!
!Wiederherstellen einer .PKG-DateiR
NSISUtil!
Erstellen einer .SIS-DateiR
NSISUtil!
Untersuchen einer .SIS-DateiR
Um eine .SIS-Datei zu untersuchen, w
hlen Sie im Menu SIS | Explore (Ctrl+Q). Nachdem Sie eine .SIS-Datei ausgew
hlt haben, wird Ihnen der Inhalt gezeigt.
Tip: In diesem Dialog k
nnen Sie die Laufwerke
ber die Tab Taste
ndern.
NSISUtil!
Lizenz und DistributionR
Das Copyright (c) von nSISUtil liegt bei Jens Kaminski und Neuon 1998-2000. nSISUtil ist Freeware unter Ber
cksichtigung der Haftungsbedingungen.
NSISUtil!
HaftungsbedingungenR
NSISUtil!
KontaktR
Wenn Sie mehr Informationen
ber nSISUtil ben
tigen oder einen Programmfehler gefunden haben sollten, so kontaktieren Sie den A9
uthor Jens Kaminski
Email - jens@neuon.com
ICQ - 4681731
NSISUtil!
DankR
NSISUtil!
".SIS and the shared module problemR
NSISUtil!
Install App Einstellungen5
Swiss
Arial
Arial
Arial
Arial
FWait
ErrorDiskFile,Folder,DiskFile is in use by another application.Close the other Application and retry.CancelledContinueDoneSaveSave as
BrowseCancelOKFileClosePKGNew
Recreate
SISCreate
Explorer
ToolsPreferencesInstaller preferencesQuick help on parametersHelp on nSISUtil
Help on PKG syntax
About nSISUtil
Optimise .SIS fileSkip syntax checkReverse filesMax filesAutomatically deleting the .SIS installation file after installation saves on disk spaceThe preferred language is used for all program installations if available.Last installed .SIS-InstallationfileCreating SISsuccessfully created.Select PKG fileSelect SIS fileAnalysing PKGNot a PKG fileNot a SIS fileWrong parameter Missing Missing file/description at line: Missing file at line: at line: Open .PKGErrors detectedEditAuto findSearching file(s)Find fileFile found:File not found:RetryNo language defined Wrong UID assigned Search;This file was created with nSISUtil
Jens Kaminski & Neuon
&Save to PKGSave to TXTFile savedFile has not changedSIS ExplorerSIS Explorer - ExtractPathInfoExtractDelete .SIS installation file?TextComponentNormalVersion: RequisitesMultilanguagePreferred languageThis file will be create by the Application.It does not exists currently.This file is required by the Application.This item cannot be extracted.File infoNameSizeReadLanguageReading
Save current PKG ?HelpMenuClose PKGNo source path will be saved in SIS.WarningOnly advanced users should activate this feature.Overwrite fileOverwrite Install (default)Text fileRemove file during uninstallRun fileText with "Continue" buttonText with "Yes/No" button (install continues)Text with "Yes/No" button (install cancels)Run file during installation onlyRun file during uninstallaton onlyRun file during both un- & installationNewOpenExploreCreatePrefer-
encesCloseVerifySyntax check successfully completedWrong UID assigned to: Assigned UID:Correct UID:nSISUtil will assign the correct UID.Not a .SIS compnent: compressedExecuteRemoveDismissDefault PKG folderDefault SIS folderDefault extract folderSIS extract modeExtract to default folder,Extract to original folder,IndividualOptionsDefaultCopiedMax characters reachedCutCopyPasteNothing to cutNothing to copyNothing to pasteSelect allInsert special chararacter
schen der .SIS-Installationsdatei nach der Installation spart SpeicherplatzDie ausgew
hlte Sprache wird soweit vorhanden f
r alle Programminstallationen genutzt.Zuletzt installierte .SIS-InstallationsdateiErstelle SISerfolgreich erstellt.PKG-Datei
ffnenSIS-Datei
ffnenAnalysiere PKGKeine PKG-DateiKeine SIS-DateiFalscher Parameter Fehlt Datei/Beschreibung in Zeile: Datei fehlt in Zeile: in Zeile: .PKG
ffnenFehler festgestelltBearbeitenAutomatisches findenSuche Datei(en)Datei findenDatei gefunden:Datei nicht gefunden:WiederholenKeine Sprachen definiert Falsche UID zugewiesen Suchen;Diese Datei wurde mit nSISUtil erstellt
Jens Kaminski & Neuon
&PKG speichernTXT speichernDatei gespeichertDatei hat sich nicht ge
ndertSIS ExplorerSIS Explorer - ExtrahierenPfadInfoExtrahieren.SIS-Installationsdatei l
schen?TextKomponenteNormalVersion: Ben
tigtMehrsprachigSpracheDiese Datei wird von der jeweiligen Applikation erstellt.Sie existiert derzeit nicht.Datei wird von der Applikation ben
tigt.Eintrag kann nicht extrahiert werden.Datei InformationNameGr
eLesenSprache w
hlenLese
PKG-Datei speichern ?HilfeMenuPKG schlie
enKein Quellpfade werden in der SIS gespeichert.WarnungNur erfahrene Benutzer sollten diese Option aktivieren.Datei
berschreiben
berschreiben Installieren (standard)TextdateiDatei bei Deinstallation l
schenDatei ausf
hrenText mit "Weiter"Text mit "Ja/Nein" (Installation wird fortgesetzt)Text mit "Ja/Nein" (Installation wird abgebrochen)Datei bei der Installation ausf
hrenDatei bei der Deinstallation ausf
hrenDatei bei der De- & Installation ausf
hrenNeu
ffnenExploreEr-
stellenEinstel-
lungenBe-
enden
berpr
fenSyntax
berpr
fung erfolgreich beendetFalsche UID zugewiesen: Zugewiesene UID:Korrekte UID:nSISUtil wird die richtige UID zuweisen.Keine .SIS Komponente: komprimiertAusf
(.txt)