Hi Friedrich,

In pt. 3 in the "To create a WebUpdate installer:" section in "Using
WebUpdate in your Installation" you say:

...." We suggest you use the same Product GUID here." Hmm... Same as
_what_?<g> Do you mean that the PRoduct GUID should be the same as
for the install with the Webupdate Client?

Pt. 8:

"It's a good idea to add "Start Delayed File Install" ... around your
files"

Do you mean the "Install File" enries in the [ Install Files ] section
in the Script?

Pt. 16:

"Your application can now start wupdate.exe..."

Actually it can do that in pt. 8 in the previous section "To install
the WebUpdate Client" as at that point the wupdate.exe is included and
you need to be able to call it in order to use what comes next.

Now, I have put the main install into a download directory on my
server. I have also put it along with the config file into an
"update" directory on the server and intend to use it to download any
updates. The main download directory will be for the full install and
made available from my website, download sites etc. Does this sound
like a reasonable way to do this?

My plan is that the update installs will mainly contain updated exe,
help etc. where as the full install will of course include everything.


Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA
www.icetips.com