Cat, as usual, has done an exceptional job explaining the way Build 12 works. <img src="http://www.piratesahoy.com/forum/style_emoticons/<#EMO_DIR#>/onya.gif" style="vertical-align:middle" emoid="

" border="0" alt="onya.gif" /> <img src="http://www.piratesahoy.com/forum/style_emoticons/<#EMO_DIR#>/par-ty.gif" style="vertical-align:middle" emoid="

" border="0" alt="par-ty.gif" /> I'll drill down a bit further to help you understand what's at play here.
The Build 12 executable is an installation engine only. It allows the user to select only the options they wish to install, and the location they wish to install the files to. Additionally, the user can choose to run only the update engine. I'll cover the function of the update engine a bit later.
Once the user has chosen the desired options and initiated the install, the Build engine connects to the server and begins the download and installation process.
The Build engine compares the files on the source code server with the files in the target location, and downloads only the files that are required. If the install is interrupted for any reason, the installer can be restarted, and the install process will automatically resume from the point it left off. Additionally, the source repository is optimized for 56k modem users for the most efficient possible transfers, regardless of connection speed.
Keep in mind that this is not a brute force, blind overwriting of files. Files are being compared, components are being downloaded and decompressed, old versions are being archived for uninstall support, etc.
The update engine functions in much the same way. Files in the update repository are compared against the user's installation, and only the required files are downloaded. The user is assured of getting only the latest updates without having to download a cumulative and `ever-growing` package.
This mechanism benefits the user in the following ways:
- The user is not forced to download the entire 78 megabyte package.
- If the download is interrupted, it can be resumed with no loss of progress.
- The Build can be downloaded to an empty folder and copied over an existing install of PotC if desired, either on the same machine or a different one.
- If the user wishes to download additional options at a later time, it is not necessary to download the full Build all over again.
Build 12 <b>is</b> a full upgrade to the stock version of PotC. Build 11 is not required <i>unless</i> the user is installing over a Euro version of PotC. This is a known problem and is being addressed as time permits.
I hope this clarifies matters for you. If you have any additional questions, please feel free to ask and I'll do what I can to assist.
<img src="http://www.piratesahoy.com/forum/style_emoticons/<#EMO_DIR#>/par-ty.gif" style="vertical-align:middle" emoid="

" border="0" alt="par-ty.gif" />