Frank, presumably because Dossy is busy doing other higher priority
things? I'd say installing all of OpenACS and Project Open on
Windows,
just to check whether they actually work with the
latest AOLserver code is, uh, more a job for the OpenACS and Project
Open developers, and/or the auto-magic Windows Insaller maintainer,
than it is for the AOLserver maintainer.
More importantly, any "Windows Installer" is doomed to be
eternally out of date - and thus not particularly useful - until and
unless the AOLserver build process on Windows (the lack there of!) is
dramatically improved. Right now, building both the core and a bunch
of modules on Unix is fairly easy, but building on Windows has only
very limited support and is thus a major PITA. (Which is still a
lot better than it used to be, note. Dossy's Windows Tcl
build script for the AOLserver core is a very useful prototype.)
Creating a spiffy Windows installer using years-old binaries, but
having no useful way to update and recompile all that code, seems very
much putting the cart before the horse...
One of these days I may work on such a Windows build process, (likely
experimenting with "bras", the
Tcl-based make replacement),
but as I currently only use the AOLserver core plus nsopenssl on
Windows, I don't have any immediate plans to do so. And maybe Dossy
or someone else will beat me to it.
If all you want is recent Windows binaries for Tcl, the AOLserver
core, or nsopenssl, I can just send you those. I'm currently using
slightly out of date versions of everything (Tcl 8.4.7, AOLserver
4.0.8, and nsopenssl 3.0 beta 23), but I'll probably be upgrading to
the latest releases of everything in a few weeks.