Imagine a situation in which a user clicks on a link in WebBoard's topics list: only to find that a fully-featured web page opens up in a new window (or the messages frame, if you like).

By fully-featured,, I mean that this page can have both client-side and server-side scripting, even if ASP isn't available - as well as forms, frames, etc.

On this page there are "feedback" links which let the user see what other users think (by viewing a WebBoard discussion thread), or offer his or her own feedback (by posting a WebBoard message).

Each post in the discussion ("feedback") thread carries a red regarding link back to the original web page, so that users who run into the discussion thread "accidentally" can see what all the chatter concerns.

But that's not all: consider a scenario in which a user clicks on a link in WebBoard's topics list.

In the messages frame, a very short web page (not necessarily a WebBoard message) opens up, which emphasizes that a PowerPoint presentation, or an Adobe file, or an MS-WORD document has just loaded in a new window.

The short web page is the "mediator" between the primary content (the PowerPoint presentation, Adobe file, or whatever it may be), and the discussion (in which users may provide feedback).  As before, each post in the discussion thread provides a red regarding link back to the original "mediating" web page, so that users who run into the discussion thread "accidentally" can see what all the chatter concerns.  The whole set-up looks like this:

Now go all the way: imagine creating a full-featured web site with a WebBoard "no authorization" board.  In other words, a web site that's indistinguishable from any other site on the net.  Users don't have to log in, they don't see a "frameset", a "conferences menu" (i.e. a topics list), or any of the other WebBoard overhead: all they see are the pages that you've placed in the site.

Did we go too far in the direction of web sites?

Perhaps, so let's move back a little bit towards message boards: consider the possibility of having a web site with various articles, written by experts - each designed to promote your firm's products or services.  Each article has "feedback" links that allow the user to post responses, or read other users' responses.  But there's no frameset, "conferences menu" (i.e. topics list), or any of the other WebBoard overhead.

In effect what you have is a "one-thread miniature message board" associated with each web page.  And users don't have to log in or register!

(How many virtal boards do you need to create that structure?  Just one.)

And to create any or all of these points on the spectrum between web sites and message boards, you don't need IIS, you don't need ASP, and you don't even need to be able to access the server via FTP!  The fact that you don't need FTP means that those who create your structures don't need the higher level of "security clearance" often required for those with FTP access.  Indeed, many system administrators don't even allow direct FTP access to their servers.

For those of you who are doubters at this moment, you might want to take a look at the on-line help pages.  There are three (cross-linked) pages, starting with: this one.

(You may be interested to know that there are "context" links into these help pages, in order to assist your staff in using this system.)

Why use this system, if you already have a web server?  First of all, without this system, your web server and WebBoard exist in two separate application arenas: they only way you can let them come together is via passive links.

Moreover, as the saying goes: "A person with one watch might know what time it is, whereas someone who has two watches is never quite sure."  In other words, one server is either "up" or "down": whereas there are four possibilities with two servers.

This code is freeware.  You use it at your own risk.  No warrany of fitness for use or any other form of guarantee inheres.

Once you unpack the zip, you'll find that there are two folders: one is called fp: this contains the files that should be placed on the folder for your virtual board(s).  Note that there are some files in the help subfolder: these must be transferred to the help subfolder of the folder for your virtual board(s).

There are also some files in the images folder.  I'll tell you what to do with those in section 5.

If you've customized any of the WebBoard pages that are in my install, you'll have to either propagate your customizations to my pages, or propagate my alterations to your customized pages.

Here's a list of each file, along with the role it plays in the various operations:

The rest of this section explains how to make the help pages available.  Since these are linked-to in a "contextual" way, I strongly recommend that you follow these instructions.

The first set of bullet points is for WebBoard 4; the second is for WebBoard 6.

• WebBoard 4 - if you have direct access to the server (i.e. you can put files wherever you desire):

  Move the files in the images folder of the release zip to the c:\webboard\upload folder.  (Don't worry, you're not going to find any files by the same name that are already there!)

  Then move _fp_hlp1.html, _fp_hlp2.html, and _fp_hlp3.html to the c:\webboard\html\help folder.  You'll find these files in the fp\help folder, in the release zip.

• WebBoard 4 - if you don't have direct access to the server (i.e., you only have web access), and you only need the help files available for one board:

  Create a private conference.  Then post a "dummy" message, in which you upload all the files on the images folder of the release zip.

• WebBoard 4 - if you don't have direct access to the server (i.e., you only have web access), and you need the help files available for multiple boards:

  Create a private conference.  Then post a "dummy" message, in which you upload all the files on the images folder of the release zip.

  Now open up Windows Notepad.  Make sure that the Edit | Word Wrap option is off.

  Open up the file _fp_hlp1.html on the fp\help folder of the release zip.  Paste this file into a message post on your private conference, and post the message.

  When the post displays, scroll to the bottom and click on the "staff options for this post" link.

  Then scroll to the section entitled "Move Post to Main Help Folder", enter the file name of _fp_hlp1 in the box, and click on the COPY button.

  Repeat the procedure in the previous 3 paragraphs for _fp_hlp2.html and _fp_hlp3.html on the fp\help folder of the release zip (obviously, you'll be varying the file name that you put into the form that's in the "staff options for this post" page!).

• WebBoard 6 - if you have direct access to the server (i.e. you can put files wherever you desire):

  Move the files in the images folder of the release zip to the c:\webboard\upload folder.  (Don't worry, you're not going to find any files by the same name that are already there!)

  Create a private conference.

  Now open up Windows Notepad.  Make sure that the Edit | Word Wrap option is off.

  Open up the file _fp_hlp1.html on the fp\help folder of the release zip.  Paste this file into a message post on your private conference, and post the message.

  When the post displays, scroll to the bottom and click on the "staff options for this post" link.

  Then scroll to the section entitled "Move Post to Main Help Folder", enter the file name of _fp_hlp1 in the box, and click on the COPY button.

  Repeat the procedure in the previous 3 paragraphs for _fp_hlp2.html and _fp_hlp3.html on the fp\help folder of the release zip (obviously, you'll be varying the file name that you put into the form that's in the "staff options for this post" page!).

  Finally go to the "more options" menu, and select the option to "Maintain files on the local (board's) help folder".  Delete the files _fp_hlp1.html, _fp_hlp2.html and _fp_hlp3.html from the board's help folder.

• WebBoard 6 - if you don't have direct access to the server (i.e. you only have Web access):

  Create a private conference.  Then post a "dummy" message, in which you upload all the files on the images folder of the release zip.

  Now open up Windows Notepad.  Make sure that the Edit | Word Wrap option is off.

  Open up the file _fp_hlp1.html on the fp\help folder of the release zip.  Paste this file into a message post on your private conference, and post the message.

  When the post displays, scroll to the bottom and click on the "staff options for this post" link.

  Then scroll to the section entitled "Move Post to Main Help Folder", enter the file name of _fp_hlp1 in the box, and click on the COPY button.

  Repeat the procedure in the previous 3 paragraphs for _fp_hlp2.html and _fp_hlp3.html on the fp\help folder of the release zip (obviously, you'll be varying the file name that you put into the form that's in the "staff options for this post" page!).

  Finally go to the "more options" menu, and select the option to "Maintain files on the local (board's) help folder".  Delete the files _fp_hlp1.html, _fp_hlp2.html and _fp_hlp3.html from the board's help folder.

DEST should have the folder name of the board from which you wish to run the thread sequencing system.  If you wish to use multiple boards, please be sure to read (?install_mult)section (#?install_mult).

Note that double backslashes are required to separate folder names.

For more information about folder names, please see my DOS primer.

This doesn't show you how to rebuild or customize the "help" files.  Please contact me if you want more information on how to do this.

Please supply me with as much information as you can about your server, your version of WebBoard, any browser or Operating System that was involved, including the WebBoard Server's Operating System  (9x, NT, 2K, XP?).  Also, please provide any configuration files, or customized WebBoard files that you were using.  Keep in mind that I might actually have to have the opportunity to try what you were doing, in order to diagnose the problem.

BTW, I don't gaurantee to answer all e-mail or fix all bugs, etc.  Please remember that this is freeware, and that my time and resources are limited.

That said, I've put a lot of work into designing, coding, testing, and documenting this product, and I'm probably going to be fairly interested in any comments anyone has, fixing any bugs, and/or extending the scope to applications that strike me as being potentially valuable to a large number of users.

Naturally, if you're willing to hire me to make changes for your special-purpose application, I'm certainly willing to consider your offer.  My standard rate is $75/hr., but I may charge less if the work is to be done for a small business (less than 25 employees), or a nonprofit organization (in the latter case, I might even do it on a gratis basis  :-)  I may also consider charging you nothing if you're suggesting an improvement that I feel is of value to a large number of other users.

You can find out more about me, including references, and a list of clients/projects at: http://www.rs-freeware.org/rog.