What's New?
What's new in Version 4.1.0.6 (released 2nd July 2007)
- When registering your licence file the read-only file attribute is now set.
- New service install flags which let you run the Web Update Wizard service
under any user account. See here.
- Web Update Wizard Project Manager can now use either WebUpdate() or WebUpdateWait()
for testing your scripts. See here.
What's new in Version 4.1.0.4 (released 25th June 2007)
- Updated version of wuwinstaller.exe which fixes reported clash with specific
Group Policy settings in some instances.
- Added new command line flags '-I' and '-U' to WebUpdateSvc4.exe,
which allow service to be installed and started ('-I') or stopped and uninstalled
('-U') from the Windows services database in a single call to WebUpdateSvc4.exe.
What's new in Version 4.1.0.2 (released 22nd June 2007)
- Added new ScrollingLink
feature, which adds a scrolling link to the bottom edge of Web Update Wizard
message boxes.
- Fixed pipe error on message box texts greater than 4096 characters.
- Corrected - some releases of the Web Update Wizard executables and dlls
were not digitally signed. This has been rectified in the current release.
What's new in Version 4.1.0.1 (released 21st May 2007)
- Added ability for Web Update Wizard message boxes, which are normally displayed
with a topmost and centered window style to be dragged around the desktop.
In case the user needs to see something under the message box before dismissing
it.
What's new in Version 4.1.0.0 (released 18th May 2007)
What's new in Version 4.0.0.13 (released 14th May 2007)
- Fixed crash where update script is completely empty.
What's new in Version 4.0.0.12 (released 27th April 2007)
- Fix on Campaign Manager script processing.
What's new in Version 4.0.0.11 (released 24th April 2007)
- Tweaked - reference to PowerProgrammer in Service name removed at customer
request.
What's new in Version 4.0.0.10 (released 10th April 2007)
- Fixed - Proxy server setting from Internet Explorer was being used even
if the checkbox on the Internet Explorer / Internet Settings dialog box was
unchecked (and the proxy server details were therefore greyed out). The proxy
server setting is only used now if the IE proxy server settings checkbox is
checked.
- Added - This version has been enhanced to allow use of the https: protocol
as well as http: in processing updates. An update script URL or Filename/Zipfile
keyword which starts with "https://" will now be transacted using
the https: protocol.
What's new in Version 4.0.0.9 (released 6th April 2007)
- Fixed - language files were not being read into
user interface component (WuWUI.exe).
What's new in Version 4.0.0.8 (released 4th April 2007)
- Added - proxy server details reported in SuperLogging mode.
- Corrected - proxy server details were not being used when running in Application
mode.
- Corrected - LastUpdate.xml was being
updated in LocalApplication data folder. It is now updated in the running
application's folder, as in previous versions of the Web Update Wizard.
What's new in Version 4.0.0.7 (released 30th March 2007)
- Several assorted fixes and improvements to situations where two or more
update requests are fired off from the calling application in immediate succession.
What's new in Version 4.0.0.5 (released 29th March 2007)
- Fixed Title and Subtitle custom fonts. The font is now set if specified
in the Title/Subtitle keyword lines.
- WebUpdateWait() function now waits until WuWUI.exe terminates before returning
control to the calling function.
- WuW3 scripts will now fully work in WuW4 - pipe character used for carriage
returns in WuW3 will automatically be replaced by "<p>" as
WuW4 interprets the update script. DialogTxt keyword which is removed from
WuW4 will not post a syntax error in WuW4.
- ShowSystemTray was briefly showning system tray icon / bubble when the update
script was being parsed, even if no update was available. This behaviour has
been corrected, and the system tray items are only displayed if an actual
update is taking place
What's new in Version 4.0.0.3 (released 28th March 2007)
What's new in Version 4.0.0.2 (released 26th March 2007)
-
Fixed silent uninstaller (wuwuninst.exe) failing in redistributable package
(wuwinstaller.exe).
- Fixed <CLIENTFOLDER> substitution error in ExecAfter/ExecBefore keywords.
- Small update to notes for V3 to V4 upgraders
help page.
What's new in Version 4.0.0.0 (released 19th March 2007)
What's new in Version 3.0.0.29 (released 6th October 2006)
- The CheckFileExists keyword now has an optional "<NOT>"
option, allowing an update to be processed only if the specified file is NOT
on the target computer.
What's new in Version 3.0.0.28 (released 4th October 2006)
- The SubmitForm option has been upgraded to now support
POST submissions, as well as GET submissions. To submit as a POST rather than
a GET, insert the optional text "<POST>" at the start of the URL, as in:
SubmitForm=<POST>http://mycompany.com/cgi-bin/formail.pl?Recipient=...
etc
What's new in Version 3.0.0.27 (released 18th July 2006)
- Fixed version checking logic when WebUpdateSvc.exe is called directly via
ShellExecute or equivalent, rather than through wuw.dll / wuwstub.exe.
What's new in Version 3.0.0.25 (released 17th July 2006)
- Fixed Campaign Manager dialog customisation to bring in line with update
dialogs. Improved LoginAs/Password error handling
What's new in Version 3.0.0.22 (released 2nd June 2006)
- Fixed problem where (rarely) the Web Update Wizard would restart 2 instances
of the application which has been updated.
What's new in Version 3.0.0.21b (released 1st June 2006)
- Fixed problem with wuw.dll where a folder was appended to the update script
URL to wuw.dll in a WebUpdate or WebUpdateWait function call. In other
words, the call 'WebUpdate("http://www.mycompany.com/update.txt|c:\somefolder");'
now works as described in this documentation, and looks
for the WebUpdateSvc.LIC file in the folder 'c:\somefolder' rather than the
folder of the application which made the call to wuw.dll.
What's new in Version 3.0.0.21 (released 20th April 2006)
- Added "<nowarn>" option to Reboot
keyword.
What's new in Version 3.0.0.20 (released 11th April 2006)
- When downloading a zip file of a certain size range the size of the file
being downloaded was not shown on the download progress dialog. This
error has been fixed.
- Added internationalisation for the progress window displayed whilst zip
files are being unzipped.
What's new in Version 3.0.0.17 (released 21st February 2006)
- Introduced small delay in KillProcess
for when WM_CLOSE fails to close the target application and the TerminateProcess
API is launched instead. In certain rare circumstances, the Web Update
Wizard message box saying that the application was still open and needs to
be closed manually would appear, even though KillProcess had successfully
(i.e. just) terminated the application.
- Small changes to a couple of the Web Update Wizard standard messages to
hopefully make them clearer / better presented.
What's new in Version 3.0.0.16 (released 31st January 2006)
- Fixed crash when using Zipfile
keyword and one of the target files on the user's computer is read-only /
hidden. The Web Update Wizard will now change the attribute and successfully
unzip the updated file.
- Fixed crash when using Filename
keyword and target file on the user's computer had the hidden file attribute
set. The Web Update Wizard will now change the attribute and successfully
update the target file.
What's new in Version 3.0.0.15 (released 13th January 2006)
- Enhanced Bitmap and
Icon keywords so that they can use image files located on remote (i.e.
internet) web servers.
What's new in Version 3.0.0.14 (released 12th January 2006)
- Added a progress bar to show progress while downloaded zip file is being
unzipped by the Web Update Wizard. Affects Zipfile= keyword only.
What's new in Version 3.0.0.13 (released 22 December 2005)
- Inserted a pesky space into the "x% of file downloaded" title bar text on
the download dialog.
What's new in Version 3.0.0.12 (released 30 November 2005)
- The LastUpdate.xml file is now written before the UsageCounter registry
value at "HKEY_LOCAL_MACHINE\SOFTWARE\\WUW" is incremented. This seems
a more correct order.
- Some documentation corrections and additions.
What's new in Version 3.0.0.11 (released 29 September 2005)
- The Web Update Wizard now uses the Internet Explorer proxy server settings
when running in Windows service mode, as well as in standard application mode.
(Previously in service mode it used the Local Service proxy server settings,
which may be different to the logged on user's settings.)
What's new in Version 3.0.0.10 (released 3 August 2005)
- Changed behaviour when the script file contains syntax errors. Now,
only one message box is posted for a script block containing multiple syntax
errors, which reports all the errors found in the script block. In addition,
the syntax errors are now written to the WebUpdateSvc.log log file.
What's new in Version 3.0.0.9 (released 1 July 2005)
- A small correction to the change introduced in 3.0.0.7, based on user feedback.
The Web Update
Wizard message boxes go back to being forced topmost as before 3.0.0.7, but
the download progress dialog can be demoted in the active window z-order.
Hopefully this
is the most sensible option, and we can stick with it!
What's new in Version 3.0.0.8 (released 22 June 2005)
- Fix to allow VERY long update script files.
What's new in Version 3.0.0.7 (released 22 June 2005)
- Removed the wndTopMost flag from the Z-order window placement properties
of Web Update Wizard dialogs and message boxes, so that they are brought to
the front on display, but other windows can be subsequently be brought in
front if required. This allows the user to continue computing whilst
the update is being made.
What's new in Version 3.0.0.6 (released 10 June 2005)
- This is an update to the LastUpdate.xml file which was added in
3.0.0.5 and addresses the concerns of some users. The creation of LastUpdate.xml is now optional, and you
can now choose what information is updated into it. Click the link for more information.
What's new in Version 3.0.0.5 (released 8 June 2005)
- The registry key "HKEY_LOCAL_MACHINE\SOFTWARE\WUW\UsageCounter"
used by the WebUpdateWait() function
is now created upon installation of the Web Update Wizard, rather than the
first time an update script is processed.
This makes it easier for users who want to directly interrogate this value
from their application as otherwise they would have to program around the
registry key not being created until AFTER the first run of the Web Update
Wizard on the target machine.
The key is now created by WebUpdateSvc.exe the first time it is executed,
including when WebUpdateSvc.exe is registered with Windows as a Windows service.
Even on Windows 9x, the wuwinstaller.exe will try to install the service and
silently fail on this task (because Windows 9x does not support service applications)
- which means that the registry key will be created by WebUpdateSvc.exe as
it tries (and fails) to install itself as a service.
Therefore, the only occasion when the key will not be automatically
created for you is now:
- When you are not using our wuwinstaller.exe client installer program...
- ... and the user's operating system is Windows 9x
- A new XML file, LastUpdate.xml, is created in your
application folder after each call to the Web Update Wizard, which lets your
application more easily evaluate whether the user was connected to the internet,
whether an update was made and whether the update completed successfully.
What's new in Version 3.0.0.4 (released 1 June 2005)
- Oops - 2 releases in 2 days - sorry!
Not good, but at least it proves we fix problems
quickly!
- Fix: font override in Title and
SubTitle keywords in 'empty'
script blocks (i.e. the block [99999] which tells the user they already have
the most up to date version) now works correctly.
- Fix: Integrated Windows Authentication now works properly when using LoginAs and Password keywords.
- Enhancement: Added the RunAlways keyword, which causes
a script block to be processed always, irrespective of the value of the counter
variable in the script. This makes it possible to have a single script
block and to process the updates based on a comparison between the file version
number on the user's computer and a specified (new) version number in the
script file, using the CheckFile
or FileVersion keyword options.
What's new in Version 3.0.0.3 (released 31 May 2005)
- All processes launched from the Web Update Wizard by KillProcess, WindowTitle, ExecBefore and ExecAfter are now launched with
the working folder of your running application (i.e. equivalent to the <CLIENTFOLDER>
folder substitution variable).
Previously the working folder of WebUpdateSvc.exe was used.
What's new in Version 3.0.0.2 (released 19 May 2005)
- Normally you must install the Web Update Wizard licence file, WebUpdateSvc.LIC,
into the same folder as your running application. However, some users
have asked for the ability to install it into a different folder.
This update optionally lets
you install your licence file (WebUpdateSvc.LIC) into different folder to
your running application. The URL you pass to WebUpdate() can now have
the local path of the licence file appended to the script URL.
- For example, say the licence file is stored in the folder 'c:\Program Files\MyApp\LicenceFolder':
WebUpdate("http://www.mycompany.com/updatescript.txt|c:\Program
Files\MyApp\LicenceFolder");
- The folder path is appended to the update script URL and separated with
a '|' character (ASCII character decimal 124 / hex 7C).
- However - please note that if you use this option the default update
folder (i.e. if you do not use a TargetFolder keyword) will
be the folder you specified for the licence file.
Also the <CLIENTFOLDER> folder substitution
variable will return the folder you specified for the licence file.
- Fixed problem with WebUpdateWait() function in wuw.dll. It was needlessly
trying to create the registry counter key when all it needed to do is open
it for reading. WebUpdateSvc.exe actually creates the key.
What's new in Version 3.0.0.0 (released 2nd May 2005)
- Improved, clearer and better structured documentation. Virtually totally
rewritten, with a view to making the product more accessible and easier to
learn. Please send
us feedback if you are unhappy with any of the documentation or have any
suggestions to make it clearer.
- The 'Web Update Wizard Named Pipe Test Utility'
has been renamed 'Web Update Wizard Project Manager' and can now be used as
a proper 'front end- tool for preparing update scripts / uploading them to
your server. It has been given significantly upgraded features, such as the
ability to start and stop the Web Update Wizard service, launch editing of
script files, ftp uploads of scripts / update files etc.. In prior versions
this utility communicated directly with the Web Update Wizard service through
a named pipe but from V3 forward it uses the recommended mechanism for communicating
with the Web Update Wizard - i.e. via a WebUpdate() call to the
wuw.dll Dynamic Link Library:
- Common binary implemented. WebUpdateSvc.exe can now be installed as
a Windows Service, or can operate as wuw.exe in earlier versions - i.e. as
a standard Windows executable, passing the URL of the server update script
as an argument in the command line in a ShellExecute() API or equivalent call.. (N.b. When
installed as a Windows Service, WebUpdateSvc.exe is able to operate in the
SYSTEM security context, allowing you to update files in folders such as Program
Files which the logged on user may not have rights to. When launched
with a ShellExecute() API or equivalent call and a script URL
WebUpdateSvc.exe operates exclusively in the logged on user's security context).
Wuw.exe is no more!
(When calling WebUpdateSvc.exe directly using ShellExecute(), we recommend
you use SW_HIDE as the display argument in order to suppress display of the
Web Update Wizard console window.
The Web Update Wizard interaction dialogs will still
dsiplay as normal).
- Full multi-language support added. All
interactions with user can now be customised via language files. If
a language file matching the Windows language setting is not available then
the Web Update Wizard looks for a default language file (which you can provide).
If no default language file is found then the Web Update Wizard reverts to
(PowerProgrammer) English.
- Added KillProcess keyword,
a more powerful and reliable way (than WindowTitle ) of closing specified
running applications prior to updating them and then restarting them once
the updated version has been written to disc.
- The Web Update Wizard in Windows Service mode now works properly through
corporate proxy servers, providing the logged on user already authenticates
with the proxy server via their Internet Explorer proxy server settings.
Previously http requests were launched in the SYSTEM security context, which
meant that they were unable to authenticate with corporate proxy servers.
- Added Web Update Wizard clipbook / syntax
definitions for popular Textpad (shareware) and PSPad (freeware) text editors. Tip:
PSPad uses IDE-type code completion / boilerplates more effectively for the
Web Update Wizard:
- Important change! The Web Update Wizard licence file, WebUpdateSvc.LIC,
must now be located in your application's folder in order for the Web Update
Wizard to find it. In other words the licence file must be in the same folder
as the application which calls the Web Update Wizard is running from.
In addition, Web Update Wizard licence files are now personalised to your
software company. Registered users are provided with a serial number which
converts their licence to a registered version.
- Web Update Wizard dialogs now use XP style buttons where applicable.
- Fix: previous versions of the Web Update Wizard issued 2 requests to the
target web server for each URL requested, although the actual file was only
downloaded once. The first request was to test that the file was reachable
/ existed, and the second request was issued to initiate the actual download.
This behaviour was causing 2 entries to appear in the web server log files
for each request, although the file was indeed only downloaded once.
This is fixed in V3.0.0.0 - there is one request only for each URL.
Apologies to any customers who previously reported this behaviour - it took
much research to pin down and eliminate!
- Added: You can change the font name and height of the fonts used for the
Web Update Wizard dialog title panels. See the keyword help for Title= and Subtitle=.
What's new in Version 2.8.0.0 - (released 1st March 2005)
- Wuw.dll can now, optionally, interoperate synchronously
with your application. In other words, it will only return control to
your program once the Web Update Wizard has finished its update check / update,
or after a specified timeout. This option is available by using the
new WebUpdateWait(URL, TimeOut) exported function. To work asynchronously
(as previously) just keep using the WebUpdate(URL) exported function.
What's new in Version 2.7.0.3 - (released 7th February 2005)
What's new in Version 2.7.0.2 - (released 3rd February 2005)
- Small bugfix on CheckFile / CheckVersion keywords. Only affects Windows
98 clients.
What's new in Version 2.7.0.1 - (released 31st January 2005)
- Fixed some dratted broken links in the help file! Why do somewysiwyg
web page editors insist on expanding urls to a full localpath? Must
upgrade to notepad for my web pages!
What's new in Version 2.7.0.0 - (released 27th January 2005)
- Added several new folder substitution constants. You can now substitute
the users's 'My Documents', Start Menu folder, Startup folder, Windows fonts
folder and desktop folder, as well as the existing Windows, temp, system andProgram
Files folders in the keywords TargetFolder=, ExecBefore=, ExecAfter=, Bitmap=, Icon= and CheckFile=.
What's new in Version 2.6.0.0 - (released 15th January 2005)
- Added LoginAs= and Password= keywords, which let you
specify authentication details where your update file resides in a password
protected web server folder. You can either 'hard code' the details
in your script or refer to a pair of specified registry keys on the user's
PC. See the keywordssection for more information.
What's new in Version 2.5.0.6 - (released 13th January 2005)
- Another cursed small bug fixed!
What's new in Version 2.5.0.4 - (released 31st December 2004)
- This is just a small maintenance release which fixes a bug reported bya
customer.
What's new in Version 2.5.0.3 - (released 10th December 2004)
- Added new keyword to update script options: ' CampaignManager= ', which
allows you to launch campaign manager scripts
directly from your update script.
- WuwStub.exe now returns 0 to calling process if URL successfully passedto
Web Update Wizard service application, else non-zero if the call failed(because
the service named pipe is busy or not running).
What's new in Version 2.5.0.2 - (released 1st November 2004)
- Addition of CheckFileExists keyword - allows you to specify that an update
script section should processed only if one or more specified files alreadyexist
on the user's computer.
What's new in version 2.5.0.1? - (released 5th October 2004)
- Sometimes someone makes a suggestion that is simple to implement, but which
adds potentially lots of benefit to the product, and this point release contains
one of these. We have added a newkeyword - ' IniSectionID= ', which lets
you determine the INI file section label used to
keep track on the user's PC of the updates processed. The result is that you
can use PHP/ASP to dynamically create the server update script files for the
Web Update Wizard on your server. You application can pass through PHP/ASP
URLs which contain parameters to the Web Update Wizard, which then submits
it to your server using http in the normal way. Your server can then generate
the script and return it to the Web Update Wizard for processing. The benefit
is that this lets your server receive and react to information about which
customers are updating etc.. Pleaseclick this
link for more information.
What's new in version 2.5.0.0? - (released 4th October 2004)
- Addition of Campaign Managermodule -
the ability to use the Web Update Wizard to manage a marketing campaign launched
from your application via the Web Update Wizard. This functionality is completely
separate from the software update functionality offered by the Web Update
Wizard, but works in a very similar way - i.e. you provide a server script
file, you launch the Web Update Wizard with its URL, the Web Update Wizard
parses the file, determines whether it is a software update or campaign manager
type script and proceeds accordingly.
- Removed the previous restriction that the update files had to be on the
same server as the Web Update Wizard server script. Updated thedocumentation
for ' Filename= ' and ' Zipfile= '.
- If no ' Subtitle= ' text is
provided then no subtitle will be shown on the Web Update Wizard dialogs.
Previously the text "© PowerProgrammer 2002-2004' would be shown.
- Service now has a proper 'Description' in the Windows servicecontrol snapin/applet.
(Well, every little helps!)
- Further revisions on help files - fixing a few broken internallinks.
What's new in Version 2.4.0.6? - (released 16 September 2004)
- Updated help files. Hopefully we have made them clearer! Specialfocus on
clarifying the architecturaloptions
- i.e. using the Windows Serviceimplementation
of the Web Update Wizard versus the standard Exe version.
- Removed the requirement to pass the 'http://' part of the serverscript URL
through to the Web Update Wizard components from yourapplication. Everything
now works either way - i.e.'http://www.mycompany.com/script.txt' and'www.mycompany.com/script.txt'
both work.
What's new in Version 2.4? - (released 24 March 2004)
- Added ability to skip processing of one or more subsequent update blocks
if user declines an optional update. See enhanceddocumentation of Importance=
keyword for more information and examples.
What's new in Version 2.3? - (released 13 February 2004)
- Enhanced the Named Pipe Test Utility (WebUpdateSCP.exe) to:
- Remember the last URL tested
- Open the WebUpdateSvc.ini file for viewing or editing
- Open the WebUpdateLog.log file for viewing or editing
- Added new keyword - CheckFile. This keyword lets you
specify a file, a file version number and / or a file date/time stamp. If
the file does not exist on the user's PC, or the file version on the user's
PC is older than the version specified, or the date/time stamp of the file
on the user's PC is older than that specified in the CheckFile line, then the script
block will be processed, otherwise it will be bypassed.
- Fixed bug on MoveFileEx=
keyword processing in line with Microsoft Knowledge Base Article - 202071
( http://support.microsoft.com/default.aspx?scid=kb;en-us;q202071
). Unfortunately Microsoft's documentation of the MoveFileEx API function
leaves one critical item out! (See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/movefileex.asp.)
- Fixed incorrect handling of version strings where the stringcontains spaces
between commas or full stops.
- Developer Installer installs the Web Update Wizard service app (WebUpdateSvc.exe)
and licence file (Web Update Service.LIC) into the Windows/System32 folder.
Previous versions installed these files into the Program Files folder for
the Web Update Wizard. This change brings the Developer Installer into line
with the Client Installer program, wuwNTClient.exe, supplied with the product,
and hopefully makes testingyour scripts easier.
Web Update Wizard - Version 2.2 What's New
- Enhanced ' WindowTitle= ' keyword to more
effectively deal with applications which do not respond to WM_CLOSE window
messages. If the application has not closed down within a default period
of 5 seconds in response to receiving its WM_CLOSE message the Web Update
Wizard will forcibly close it down. You can control the period between
WM_CLOSE and forcible closure using the "<Timeout=xxx>" option - see
the keyword reference section
for more information. (Prior versions just issued WM_CLOSE messages
without following up with a forced closure in the event of the target window
failing to respond to the message.)
- Enhanced the ' ExecBefore= ' and ' ExecAfter= ' keywords to allow
you to (optionally) specify / limit which operating systems the command should
be run on. Append the option "<MaxVer=x,x,x>" or "<MinVer=x,x,x>"
to the keyword line for this additional level of control.
- Added "<BlockDone>" option to the ' ExecAfter= ' keyword. This
ensures that the Web Update Wizard counter is incremented even if the ' ExecAfter=
' keyword uses the "<Wait=Yes>" option and the launched process triggers
a reboot. In this situation earlier versions of the Web Update Wizard
would not have incremented the counter. (See the keyword reference section for
more information.)
- Fixed bug on " MoveFileEx= " option for Windows
9x platforms. This option was previously failing under Windows 9x.
- Downloads greater than around 5.5Mb were failing on Windows 98. All
other operating systems and downloads less than 5.5Mbwere unaffected.
This bug appears to be related to a problem withmultiple uses of the Microsoft
realloc() C runtime libraryroutine. Version 2.2 works around this issue
by eliminatingrealloc() calls and therefore resolves this issue.
- Log file detail
increased.
Web Update Wizard - Version 2.0 What's New
- Replaced the ActiveX component in V1 with a simple 32-bit Windows dll which performs the same function.
The dll does not need registering in the Windows registry and exports just
one function - WebUpdate(URL of server update script
as a string).
- Dialogs totally changed and (hopefully) vastly more attractive tousers.
- Dialog colours, title text, icon andbitmap can now
be customised and 'branded' to your own product.
- Windows 9x and Windows NT or later version now uses 99% common code and
is compiled from the same code base. The Windows 9x versionhas been renamed
WuW.exe due to Windows 9x's restrictions
on replacing in-use files via the (antiquated) wininit.ini route.
- Suppressed display of download dialog when the service downloadsthe script
from the server.
- Added (optional) SubmitForm keyword to simulate
a web browser form post, including spoofing the referring page. Use to transparently
send message to software house from the Web Update Wizard that an update was
completed on a user's machine.
- Added user defined substitution variables for
SubmitForm, so that registry values (text strings) can be transmitted with
the SubmitForm syntax.
- Added (optional) FileDate and
FileVersion keywords, to save
downloading update files which are newer on the client PC. Update only
occurs if version for download is newer than version on user's machine.
- Fixed bugs on dropped connections where the ExecAfters ran anyway (they don't
now) and where the update was incorrectly logged as successful (it isn't now).
- Added Reboot keyword to reboot
computer as last item in process.
- Added MoveFileEx keyword,
which allows you to replace in-use files at next reboot.
- Added NoSuccessMessage keyword
which, if included, prevents the 'xxx was successfully downloaded..' message
box at the end of the download.
- Added <NOWARN> option which suppresses the "I'm going toclose xxx"
warning for the WindowTitle keyword - e.g. "WindowTitle=Your
Application<NOWARN>" will close 'Your Application' without popping up
a warning box.
- Added FinalMessage keyword
which lets you post your own success message instead of the Web Update Wizard
success message. Shows after everything else has finished but before (optional)
reboot.
- FinalMessage and Message keywords can now expand
carriage returns - use a '|' character in the message as a newline character.
- The NT Service has always received the folder
containing the exe which contains the ActiveX component of Web Update Wizard.
Windows 9x users now now get this information too - the Web Update Wizard
sees the current folder as the one which contains the wuw.exe component.
- Added <CLIENTFOLDER> as a constant to TargetFolder, ExecBefore, ExecAfter - it expands to the
folder hosting wuw.exe for Windows 9x and the folder hosting
the application which calls the Web Update Wizard dll ( wuw.dll
) for the NT Service version.
- Enhanced the wuw.dll DLL so that it knows whether
to call the Web Update Wizard Service if running on NT or later or the WuW.exe if on Win 9x. Therefore it
is now possible to create a 'one size fits all' installation program for the
Web Update Wizard functionality.
- Added <TEMPDIR> and <COMPUTERNAME> to list ofconstants that
ExecBefore / ExecAfter can expand.
- Added <PROGRAMFILES>, <WINDIR> and <SYSDIR> tolist of
constants that TargetFolder can expand.
- Enabled a user defined
message for situations when the client user already has the most up to
date versions of the software - simply append a block at the end of the server
script with a counter value larger than any used in the script (e.g. "[99999]")
and use the "Message=" keyword to have your user-defined message displayed.
- For Windows NT/2000/XP platforms, ExecBefore and ExecAfter processes launched within
SYSTEM security context unless "<AsUser>" is appended to their keyword
lines, where the launched process runs in the security context of the logged
on user. (In V1 all processes where launched in the SYSTEM security context.)