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

** ---------------------------------**
** IMPORTANT INFORMATION regarding **
** recent 3.2.1 release of CTCI-W32 **
** ---------------------------------**

The 3.2.1 version of CTCI-W32 unfortunately contains a fatal flaw in
its implemented workaround/"fix" of Microsoft's recent Visual Studio
2005 SP1 (Service Pack 1) snafu. Apparently their suggested
workaround[1] (building with _USE_RTM_VERSION) only works for
executables and non-regular DLLs (e.g. extension DLLs such as
FishLib). For some reason I completely missed that fact when I
[admittedly rather hastily] implemented and subsequently released by
3.2.1 workaround/"fix" release for the broken 3.2.0 version of
CTCI-W32.

The currently released versions of all of my products -- EXCEPT
CTCI-W32 -- *should* now work with *either* the original Microsoft
Visual C++ 2005 runtime DLL redistributables (available from their
web site[2]) -OR- with the newer "SP1" (Service Pack 1) version of
the same thing (available only from softdevlabs[3]).

Unfortunately the above is NOT true when it comes to the CTCI-W32
package (because CTCI-W32 consists of two regular DLLs -- FishPack
and TunTap32 -- which are not fixed by the _USE_RTM_VERSION
workaround).

Thus, in order for CTCI-W32 version 3.2.1 to work AT ALL on your
systems (should you decide to use it[4]), you will unfortunately have
to install the "SP1" version of the Microsoft VC++ redistributables
(which as explained are NOT available on any of Microsoft's web pages
(yet)). The "SP1" version of their runtime DLLs -- which again, are
REQUIRED for version 3.2.1 of CTCI-W32 (but not for any of my other
products (yet) -- can ONLY be downloaded from softdevlabs.com (or any
of the mirrors) at the URLs mentioned in footnote 3.

Also note that when you run the SP1 install program, unlike the
non-SP1 version from Microsoft's web site, you will *not* be
presented with any type of License Agreement dialog at all. Instead,
the program will simply perform the install and that's it. (You won't
even receive an "OK" dialog when it's done either! It'll just finish,
without any indication whatsoever that it has completed.[6])

Once it completes installing (should only take a few seconds) THEN
CTCI-W32 *should* work for you. The TT32Test program and Hercules
CTCI/LCS networking devices *should* start working just fine for you.

Again I apologize to my users for this f**kup but in my own defense
it wasn't completely my fault. Mostly it was Microsoft's for not
properly warning their users (developers) that this would happen as a
result of installing their service pack. The only thing that was
admittedly my fault was in rushing a tad bit too hastily in trying to
fix it (without researching the issue more deeply). For that I
apologize. (For Microsoft having caused this issue in the first place
I do NOT however. You'll have to talk to THEM about getting an
apology on THAT.)



(p.s. I am hard at work trying to create proper Windows Installation
(.msi) packages for all my products, but it's going slow. The
tools/technology/user-interface for the IDE/etc involved in helping
one do that are all new to me, so it's taking me longer than expected
to "come up to speed" on them all.)

- --
"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] http://msdn2.microsoft.com/en-us/library/aa983356(VS.80).aspx

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?F
eedbackID=247057

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1053779&SiteID=1

[2]
http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9
- -4C13-9C99-220B62A191EE&displaylang=en

[3] Note that the download link on my web page (which was originally
incorrect) for the SP1 redistributables has now been corrected.
Please refresh your browser's cache. The correct download URLs are:

(32-bit Windows):
http://www.softdevlabs.com/Hercules/vcredist_x86.exe
(64-bit Windows):
http://www.softdevlabs.com/Hercules/vcredist_x64.exe

[4] The previous 3.1 version of CTCI-W32 should continue to work just
fine with version 3.1 of WinPCap. It only fails when you try using
version 4.0 of WinPCap which version 3.1 of CTCI-W32 doesn't support.
(Only version 3.2 or greater of CTCI-W32 supports version 4.0 of
WinPCap.)

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

iQA/AwUBRe1POEj11/TE7j4qEQJX4QCgk3Hv7PDDdDUk1TlDQdJD0HVHrAkAmQHs
fa2V3UdTHuHwItVXpmFZyhw5
=mXwi
-----END PGP SIGNATURE-----