-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

BCC: direct to a few people


(somewhat LONGISH)


Okay, I've just uploaded new versions of all my products[1] that
allows them to run on systems that don't have the SP1 version of
Microsoft's VC Runtime distributable installed. Additionally, I've
also uploaded and made available for download, the new "SP1" versions
of the Microsoft C/C++ Runtime DLLs required by my programs. Thus you
now have a choice of either:


a. Download the new SP1 version of Microsoft's C/C++ Runtime DLLs
to allow the previous version of my products to run.


b. Download the new version of my product that now works with
previous (non-SP1) versions of Microsoft's C/C++ Runtime DLLs.


c. All of the above. :)


The problem with my original release made last week (for those not
familiar) was the fact that it had been built with the new "SP1"
(Service Pack 1) version of Microsoft's Visual Studio product,
thereby causing (unbeknownst to me and many other developers around
the world bit by the same issue) all programs BUILT with that [SP1]
version [of Visual Studio] to thus require the corresponding "SP1"
version of their runtime dlls (msvcr80.dll, etc) as well.

Now normally such a dependency requirement is not a huge problem
since *normally* products are shipped with installer programs (.msi)
that automatically install all prerequisite (dependent) components,
but my products don't come with installation programs (yet). They
require the user to manually install the necessary (dependent)
components themselves (which up until now wasn't really that big of a
deal either).

The only problem is, Microsoft, in their infinite
lazin^H^H^H^H^H<cough>"wisdom"<cough> decided to NOT provide the new
SP1 versions for download from their web site! [2] (grumble)

Soo... Up until today (when I released the new SP1 versions of their
runtime myself) users would download the [unbeknownst to them] OLD
runtime redistributable components (vcredist) and discover much to
their dismay that, after installing it, their programs (my products)
STILL wouldn't work! :(

This new release addresses (resolves) this issue.

This new release is essentially the same as the last release except
that it was built with a new compile switch called
"_USE_RTM_VERSION". This new switch (first appearing with SP1) allows
programs thus built to continue working with the OLD (non-SP1)
versions of their (Microsoft's) C/C++ Runtime DLLs.

ADDITIONALLY, I've also released along with new versions of all my
products, the new SP1 version of the Microsoft C/C++ Runtime DLLs
themselves. The link is on the main HercGUI web page.

So the choice is now your: you can download the new runtime dlls so
you can continue using the versions of my programs you already
downloaded last week, or you can download the new versions of all my
products so you can continue using your existing non-SP1 version of
Microsoft's runtime DLLs, or you can, of course, do both if you so
desire.

I apologize to everyone for this minor snafu but it was as much a
surprise to me as it was to all of you. I really wasn't expecting
such a thing at all (nor were many others either from the looks of
it).

As a result of this snafu however I shall make a renewed effort to
try and set things up so that my products come with installation
programs (.msi) so that HOPEFULLY this won't happen again. Don't know
how long it'll take me though. At first glance creating a "deployment
project" as they're called appears to be a simple thing to do. Once
you start digging deeper however you soon discover that looks can be
deceiving.


Anyway, that's it. Have fun with the new versions. :)


Oh yeah:

****************************************************
* And PLEASE MAKE A DONATION if you haven't yet! *
****************************************************

It's March 1st and rent is due and while we currently have enough to
pay it THIS month, next month isn't looking very good at all.

Thanks.

- --
"Fish" (David B. Trout) - fish(at)infidels.org
Fight Spam! Join CAUCE! <http://www.cauce.org/>
(Any HTML email received will be deleted unread)
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52

[1] But at the moment only to SOFTDEVLABS.COM and CBTTAPE.ORG. For
some odd reason I can't seem to get through to Volker's site. I think
his maybe his server must be down or something (hopefully only
temporarily though). Pedro's mirror doesn't yet have the new versions
either but should within 24-48 hours or so. I'll get them uploaded to
Volker's mirror too just as soon as I find out what's going on.
(Might be an end-of-month thing maybe seeing how it's the 1st of the
month. <shrug> (just a wild, uneducated guess))

[2] WHY they decided not to (why they're still dragging their feet
about it) is anyone's guess. <shrug>

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRebUR0j11/TE7j4qEQLwmACfeSR62cY/vm5swO/UO1Q1l0bQVUUAnjWL
6sy0AeFIfleH7Wmb/2mvu02G
=8aMo
-----END PGP SIGNATURE-----