Turns out there was unused code that dealt with strings
that may or may not have been initialized, and treated
them as multi-byte strings even though they were unicode
strings.
I don't actually understand why this would cause a failure
only on Windows Server 2012, but this change definitely fixed
the problem, and the code removed was unnecessary and wrong anyways.
While at it, improved error reporting in case we fail to
get the link to the bootstrap tarball, or download it.
Also fixed a bug that broke login/signup (due to passing a
char* instead of a wchar_t*)
Uses the https://packages.meteor.com/bootstrap-link
URL to generate a link to the windows bootstrap tarball.
With this change we no longer have to build a new installer
for every release.
Older installers, like the one on http://win.meteor.com
populated the same directory as our new installer, but with
different files. Specifically, meteor.exe which runs before
our meteor.bat. So we delete the contents of the installed
directory before starting the install.
* Always install the the user's local directory
(skip the dialog asking where to install)
* Skip login/register dialog (it doesn't work yet)
* Improve prose
