The Art of Dissolving Splash Screens

[Scott Kane]

From: "Tiemo Hollmann TB" <toolbook at kestner.de>

> Didn't thought about that technique injecting back and front scripts yet, 
> do you check automatically online for updates at this state, or where do 
> you
> get the repair scripts from?

Like all things Rev there are many ways of doing this.  I personally use the 
program to do it (the executable) and update that way.  However you could 
just as easily do it using a stack or any other type of file.  For example 
the one of current applications I'm working on checks the server inside the 
exe for updates.  This ties in with my licensing system and security as well 
as getting valid updates or bug fixes.  It simply reads a text file on the 
server.  If there's a new version it downloads it, runs the update and then 
reloads the program.  Because I am using partial key verification (PKV) for 
my license code I can disable a serial number or even an entire keygen in 
one hit (and without making any modifications to core code functionality or 
even the algo' for how the key is calculated).  So it's handy to do this in 
the executable.  However it can include fixes for any part of my code.  In 
addition once you've got a system of working going (each person has their 
own preferences) you can use it as a kind of conditional compiling tool 
which is not possible in Rev technically.  Thus I can inject code according 
to the version using the savingstandalone event in Rev.

Scott Kane
Moderator comp.software.shareware.*