That would be fine. I've been using quite a bit of open source stuff lately
and haven't had an opportunity to give anything back yet. There's really
not much to the procedure though.
- I went to aolserver.com, to the download section, and got this:
http://aolserver.com/archive/server/binary-builds/aolserver-3.4-win32-instal
ler.exe
- It runs just like any other installer for window$. Take the defaults and
step all the way through it.
- Then you click Start/Programs/AOLserver/AOLserver. You see the console
pop up and go through its initialization. The console should stay open - if
it disappears you have a problem that caused AOLserver to terminate. Copy
the AOLserver shortcut and paste it into a DOS command prompt - then you can
see what happened without the window closing on you. Copy and paste that
text into the newsgroup for help.
- Point your browser to http://myipaddress:8000/ and check it out. You
should get an AOLserver introductory page with some links. Also the
telemetry page nstelemetry.adp (which is really nice btw) can run on the
default configuration. I also downloaded it from aolserver.com and placed
it in c:/apps/aolserver34/servers/server1/pages (my installation path was
c:/apps/aolserver34 - yours will probably be in c:/program files/aolserver).
- Note that you can't hit http://localhost:8000/ and expect it to work.
Apparently it doesn't listen on 127.0.0.1 by default.
- You can try this out while running IIS or PWS since AOLserver listens on
port 8000 by default, not the standard port 80. There will be no conflict.
- I was able to immediately make an .adp file in
c:/apps/aolserver34/servers/server1/pages and have it work. I then did a
{load c:/apps/tcl/lib/tclodbc2.2/tclodbc.dll Tclodbc} at the top of that
file, and used that package (nice!), which I already had installed, to
connect to M$ SQL Server and fetch some data into by browser. I'm sure this
is NOT the recommended method of loading a TCL package or library, but it's
the only way I presently know to do it from within AOLserver. (Any help with
that would be appreciated).
- I also used the socket command to connect to a back-end service i'd
written in TCL and fetch some data that way. It worked great except it
locked up AOLserver after a couple minutes of idle time. Probably at thread
cleanup time. ns_sockopen gave the same behavior except it locked up
immediately after the page, no delay. That would be an extremely valuable
thing for a lot of Win users who (like us) have SQL Server data that will
require use of a proxy daemon of some sort running on Win32.
- This was done on window$ NT 4 service pack 6. Should work on any other
win32 version (95 and up).
At this point I'd like to expound some more on issues that Win users would
be interested in, like virtual hosting (parsing Host headers and/or URLs).
But I'm new to AOLserver and still exploring that stuff. In fact if someone
could help me with that topic would be nice. The docs seem to skirt around
some issues that people are likely to be interested in, particularly in
environments like ours where IIS is already in use.
I hope some or all of this can be used. I also hope to run into you guys in
the AIM chat. Thursday 3PM Central Time right? Hope I can get it to work
(first time there).
--
Mark Hubbard: [EMAIL PROTECTED]
Microsoft Certified Professional
"Knowledge is Power."
-----Original Message-----
From: Dossy <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, August 22, 2001 1:23 PM
Subject: Re: installing AOL Server on WINDOWS!
>On 2001.08.22, Mark Hubbard <[EMAIL PROTECTED]> wrote:
>> I just did AOLserver last week, from the binaries, not the C source.
>
>Which binaries?
>
>> Listers: would you want to see this on the list, or should we keep it in
>> private email?
>
>The AOLserver walk-through ought to be sent to the list. If nothing
>else, a summary of the explanation that could possibly be turned
>into or used as a HOWTO. I'd then like to post it to the wiki if
>that's okay.
>
>-- Dossy
>
>--
>Dossy Shiobara mail: [EMAIL PROTECTED]
>Panoptic Computer Network web: http://www.panoptic.com/
