Hi Frank, I am indeed maintaining a Windows version of AOLserver, though at the moment I only have HEAD built (4.1), and not 4.0.8.  I did try native Win32 PostgreSQL back when it was still PostgreSQL 7.5 beta.  It seemed to be running smoothly, but I did see the same 7.4 -> 7.5 problems in OpenACS that you see and that Jeff has committed patches for.  (I haven't tried an install with Jeff's patches.)

I put a zip of recent AOLserver binaries up at http://www.jamierasmussen.com/download/

AOLserver 4.1 is still Alpha, when 4.1 final is released I'm hoping to rebuild the installer and host it on SourceForge.  The installer by Vlassis uses PostgreSQL on Cygwin and some fairly recent binaries from me.  The native PostgreSQL installer is quite nice.  My personal preference would be to have separate (but simple, GUI-based) installers for the database, web server, and OpenACS / dotLRN, since I think maintaining a combined installer will be more difficult.  Vlassis' installer does have some nice features, but requires downloading a whole Java distribution, etc.

To build AOLserver, I use Microsoft Visual Studio .NET 2003, there are project files (like Makefiles) for Visual C++ 6.0 in the SourceForge repository, as well as a Tcl script Dossy wrote that can be used with Microsoft's free (to download) version of the .NET 2003 compiler.  Dossy's Tcl script currently only builds the core modules though, I have project files for all of the modules you see in the binary zip.  They haven't been checked in because Dossy and I think enhancing the Tcl-based make is a better long-term solution.

The AOLserver installer I built used some custome Perl wrappers to PerlMSI, which is part of ActiveState's Perl Dev Kit.  MSI installers have some nice features, but I may switch to Inno Setup for the next installer, since Inno Setup is free to download and rather easy to use, which would make it easier for other people to contribute to the installer code.  It will depend on how much free time I have before 4.1 goes final.  I think PostgreSQL uses WiX to build an MSI installer from an XML source file - I haven't used that tool myself so I'm not certain how hard it would be to do what you suggest.

Installing AOLserver from a zip file is only slightly harder than using an installer.  The main difficulty in building AOLserver on Windows is that there are a lot of modules, some of which need to be tweaked to compile, and many of which have dependencies that you also have to track down and build.

Frank, AOLserver 4.0 beta 10 ?? Why are you running such an old version? 4.0.8 is current, and Dossy should be releasing 4.0.9 sometime soon with some additional bugfixes. Are you running Jamie's old binary distribution of AOLserver on Windows? It's just that, old. There have been lots of little bug fixes since then.

Unfortunately the current build situation for AOLserver on Windows is a little confused, and definitely incomplete. Dossy's Tcl script does build the core just fine for Windows. I also hacked it up in order to build nsopenssl on Windows, but last I heard no one else has built any of the other modules that way. Dossy also was undecided whether to stick with a Tcl-based make script or just write nmake files for Windows.

If I ever find the time and motivation, I would like to try using one of the several Tcl-based make replacements for building AOLserve and all its modules on Windows - and maybe on Unix too. So far, having used none of them, I'm leaning towards bras, as it seems the most powerful and complete. (It even mentions "Recursive Make Considered Harmful" on its homepage, which is a good sign.)

Hi Andrew,

thank a lot for the hint with "mv" and "find" in TCL. This probably saves me _a_lot_ of time.

> Jamie's old binary distribution

Yes in dead. I don't have all the M$ stuff running on my machine (http://panoptic.com/wiki/aolserver/1332) and my last M$ programming experiences is >8 years ago (Borland Pascal 7.0...), so it would probably take me _a_lot_ of time getting started again.

What's funny is that Vlassis also used Jamie's binary distribution. It seem that Vlassis with his "graphical installer" hasn't managed to compile all these modules necessary neither, because he's also using Jamie's stuff...

So you've got everything running at home? Would it be possible to post a ZIP of your binaries somewhere?

Bests, and thanks a lot for your replies,
Frank

Hi Frank, sorry for the slow response.  I don't know what is causing your broken gif problem.  If using a newer version doesn't fix it, you may want to check out that the proper headers are coming through via Mozilla's livehttpheaders or Ethereal or similar.  Does this happen only to some gif files or all, and does it happen all the time?

Vlassis is using a binary distribution from me, but he isn't using 4.0b10, he's using a nightly build of 4.1a from a couple of months ago.  I've put another nightly build of 4.1a up at
http://jamierasmussen.com/download/ if you want to try that.  There's no online bugtracker for my build.  I'm afraid that this is an untested build from HEAD with some Win32 and other patches (and I haven't looked at the recent changes by Jim that it includes).  But it does include all of the modules that OpenACS uses and many that OpenACS doesn't.

When I last checked, Dossy's script didn't build any non-core modules.

Oh, Vlassis may have ended up using the 4.0b10 stuff after all, I remember now that he had some problems with getting 4.1 to shutdown cleanly.  I unfortunately never had time to look at his installer closely.

There should be tDOM 0.8.0 binaries in the zip you downloaded from me.  If you copied the files from my zip over an older installation of AOLserver you may be mixing files from two different version of tDOM?  I'm not sure why you're getting the multithreading message.  My zip just includes the pre-built win32 dlls from tdom.org - I think that download used to be a multithreaded build...

I'm afraid that's the only thing that comes to mind, if you don't figure it out, you might ask on the AOLserver mailing list and Zoran or someone else could know what's happening.

Is the nsxml compatibility layer still working?

Hi Jamie,

thanks for sending me the threaded tdom-0.8.0. I've installed it and AOLServer 4.1.0a loads correctly. Also, the load time for OpenACS has gone down remarkebly. Is there some whichcraft going on???

However, I'm now getting problems with some Project/Open transactions. For example I'm getting a timeout when I try to create a new company. The log file doesn't say anything in this case, it's as if I would never have selected the page. It does work fine with AOLServer 4.0.beta10, I've renamed the directory and it works fine now again.

So I think I'll have to do the same as Vlassis and revert to 4.0.beta10 again because I'm running out of time. However, I can provide you with my test setu-up here if you want. It consists of Vlassis' install results, replacing his C:\OpenACS\nsd4 by your 4.1.0a distro and by adding some P/O packages. I can send you the P/O packages as a ZIP if you want.

Cheers,
Frank