OKSU. EXE 
Utility OKsu.exe shows, how one realizes with the help of T2U, Self Self-Updates von Software 
can. First we explain the idea briefly, how it functions. The user starts those 
To software on his computer normally by click on the Icon on the Desktop 
or on the starting menu. In both cases it starts only a linkage with that 
appropriate Icon. Which hides itself behind the linkage, is not always the path too 
the started program. 
T2U offers a way to start the installation of the update of a program. The idea is, 
instead of the linkage, which bring along a software, another linkage to provide. 
This linkage is for users at first sight exactly like an original 
Linkage look. It is to have the same Icon and the text. In the command line 
however another program is to be started, e.g..   OKsu.exe. This other program 
it is to examine somehow whether a newer version of the program already in the net 
is available. If there is no newer version, is the local program directly 
are started. However if a newer version is available, the user is over it 
are informed and as required directly the Setup for the new version to start to be able. 
For the statement of the existence of a newer version OKsu.exe seizes on the server and gets 
the information from a INI file. One knows either a INI file per product 
use or several products can a INI file divide. Per product needs 
one a section. 
We explain the work of OKsu.exe and the format of the INI file by an example. 
We imagine that we have two versions of a product: Solitaer (sol.exe) and 
Spider Solitaer (Spider.exe). Both programs are present with Windows XP. Although 
both plays to be parallel used can, call we first (sol.exe) Solitaer 
Version 1.0 and the second (Spider.exe) as Solitaer version 2.0. 
The installation of Solitaer 1,0 can be a batch file about in such a way and look: 
:
IF NOT EXIST "%ProgramFiles%\solitair" md "%ProgramFiles%\solitair"
copy .\sol.exe "%ProgramFiles%\solitair\" >nul
:
and the installation of Solitaer 2.0: 
:
REM remove old version
IF EXIST "%ProgramFiles%\solitair\sol.exe" del /Q "%ProgramFiles%\solitair\sol.exe"
::
IF NOT EXIST "%ProgramFiles%\solitair" mkdir "%ProgramFiles%\solitair"
copy .\spider.exe "%ProgramFiles%\solitair\" >nul
:
To make possible around the user a simple start from Solitaer to and at the same time one 
To connect, we provide examination on existence of a newer version before the start 
a linkage for each Solitaer version. 
The linkage of Solitaer is to be replaced with the following line: 
"%ProgramFiles%\OK soft" e:"%ProgramFiles%\solitair\sol.exe" Solitair.en US 
1,0 \\BONN\T2U\Self-Update\solitair.ini 
and/or for version 2.0: 
"%ProgramFiles%\OK soft" "- e:%ProgramFiles%\solitair\spider.exe" Solitair.enus 
2,0 \\BONN\T2U\Self-Update\solitair.ini 
In both cases the call parameters are identical to the exception of the current 
Indication of version ("1,0" or "2,0"). 
As Icon is the old (originals) Icon (with the path too %ProgramFiles%\solitair\sol.exe 
and/or.   %ProgramFiles%\solitair\spider.exe) to be maintained. 
This linkage is to be copied by the appropriate Setup (Install.cmd) simply. 
With the start of such a linkage the section examines Solitair.en US from the INIDatei 
\\BONN\T2U\Self-Update\solitair.ini. 
Enclosed an example of the INI: 
; @name@ - placeholder for product name ('Name' entry)
; @version@ - placeholder for product version (from the command line of OKsu.exe)
; @lastversion@ - placeholder for aktual version ('LastVersion' entry)
[Solitair.en-us]
Name=Solitair
LastVersion=2.0
StartId=Install
Cat=\\BONN\T2U\Catalogs\Solitair_2.cat
PkgDir1=\\BONN\T2U\Packages\Solitair_2.0
;Cat=@CDROM@Catalogs\Solitair_2.cat
;PkgDir1=@CDROM@Packages\Solitair_2.0
;CDInsertMsg=Bitte, legen Sie CD/DVD mit dem Paket @name@ @lastversion@.
;CDInsertMsgTitle=Update von @name@ @version@
Advertisement=5.10.2005
AdvertisementMsg=Lieber Benutzer,\n\nab dem 5.10.2005 wird das Spielen von Solitair in
veralteten Version @version@ nicht mehr empfohlen.\nBitte installieren sie die neue Version
@lastversion@.\nSoll die neue Version jetzt installiert werden?
AdvertisementMsgTitle=Update von @name@ @version@
AdvertisementMsgType=NOYES
Mandatory=30.12.2005
MandatoryMsg=Ab Heute muss eine neue Version von dem Spiel Solitair installiert
werden.\nKlicken Sie auf OK um das neue Spiel zu installieren.
MandatoryMsgType=OK
MandatoryMsgTitle=Update von @name@ @version@
Expire=1.05.2008
ExpireMsg=Bitte installieren sie jetzt die neue Version von dem Spiel Solitair.
ExpireMsgTitle=Update von @name@ @version@
ExpireMsgType=OK
; AdvertisementMsgType, MandatoryMsgType, ExpireMsgType can have values:
; {OK, YESNO, NOYES}
; YESNO - "yes" default, NOYES - "no" default
As the first OKsu.exe examines whether the current version of the program from the command line 
("1,0" or "2,0") corresponds to the newest version (see load version entry). If both 
Equal versions are, the locally existing program one starts (see switch e of the 
OKsu.exe). If a newer version than the locally existing exists, the data become 
from Advertisement, Mandatory and Expire with the current date compared. That 
Mandatory date is to lie between Advertisement and the Expire. 
If the current date before the Advertisement lies, the local version of Solitaer becomes  
started. Thus one can prepare a follow-up version of a software and to 
Deadline offer. Such scenario is e.g. important with a tariff change starting from one 
determined date. Another frequent example, like during a classical software distribution 
many problems to arise know, are the update Client servers of an application. 
One must up-play a new version on a server, e.g. a data base, and 
at the same time update each Client. 
If the current date is later than the Advertisement however in former times than the Mandatory, 
becomes the user a message from the AdvertisementMsg with the title 
AdvertisementMsgTitle indicated. The AdvertisementMsgType is NOYES. That means, 
that the Message box two Buttons has "Yes" (and/or "") and "NO" (and/or "no"). That 
User is asked whether he wants to now update the software. With the answer "no" becomes 
the locally existing old version started.With "" the Setup of the new version becomes 
by means of T2U started.   All call parameters become by the entries Cat, StartId and 
PkgDir1 indicated. We notice still that with the Message box of the "Nein" Button as 
Standard Button is defined. If you want to change it, need only that 
To change AdvertisementMsgType of NOYES on YESNO. 
The Mandatory and Expire messages function exactly the same as the Advertisement 
Messages.   MandatoryMsgType and ExpireMsgType have however OK ONE. That means it that 
with these messages one leaves to the user no choice. After the user 
the OK switching surface clicks, becomes with Mandatory messages the installation of the new 
Version started. With the Expire messages becomes instead neither the Setup nor those 
locally existing old version started. The task of the old version ran off thereby 
simply. 
If one distributes the software updates by CD/DVD, are the entries Cat and PkgDir1 
begin in the INI file with the character sequence @CDROM @. This character sequence becomes through 
the name of the current master directory before the start of the update replaces. Before 
it is examined naturally whether itself in one of the CD and/or DVD drive assemblies the CD with that 
appropriate files finds. If no and/or wrong CD in the drive assembly lies, becomes 
of the user requires to insert the correct CD. Text and titles of the messages become 
by the entries CDInsertMsg and CDInsertMsgTitle steered.   An example of it finds 
one above in the comment lines.  

Go to Help Contents