summaryrefslogtreecommitdiff
path: root/web/funnelweb/0stoppress/fw_README.mes
diff options
context:
space:
mode:
Diffstat (limited to 'web/funnelweb/0stoppress/fw_README.mes')
-rw-r--r--web/funnelweb/0stoppress/fw_README.mes92
1 files changed, 92 insertions, 0 deletions
diff --git a/web/funnelweb/0stoppress/fw_README.mes b/web/funnelweb/0stoppress/fw_README.mes
new file mode 100644
index 0000000000..186661abfa
--- /dev/null
+++ b/web/funnelweb/0stoppress/fw_README.mes
@@ -0,0 +1,92 @@
+--<Guru>--
+D=10-Nov-1992
+A=Ross Williams
+S=Overview of FunnelWeb archive.
+K=funnelweb archive messages status release notes update readme
+--<Guru>--
+OVERVIEW OF FUNNELWEB ARCHIVE
+=============================
+FunnelWeb is a simple, portable literate preprocessor. It was released
+in June 1992. The June 1992 release is the only release of FunnelWeb
+to date (mid November 1992). This archive contains files that provide
+additional information that may be of assistance to FunnelWeb users.
+
+ fw_README.mes - This message.
+ fw_abandon.mes - About why FunnelWeb was temporarily abandoned.
+ fw_advert.mes - The original FunnelWeb internet advertisment.
+ fw_make.mes - A FunnelWeb make file.
+ fw_mlist.mes - FunnelWeb mailing list.
+ fw_mlist_rules.mes - All about the FunnelWeb mailing list.
+ fw_p_apollo.mes - Notes on porting to Apollo.
+ fw_p_hp.mes - Notes on porting to HP.
+ fw_p_mpw.mes - Notes on porting to MPW.
+ fw_p_next.mes - Notes on porting to NeXT.
+ fw_p_next_patch.mes - NeXT machine patches.
+ fw_p_pc.exe - An MSDOS/386 FunnelWeb executable.
+ fw_p_pc.mes - Notes on porting to MSDOS.
+ fw_refs.mes - Literate programming references.
+ fw_sugg.mes - Current list of suggestions for improving FunnelWeb.
+ fw_tabs.mes - A note about FunnelWeb and tab characters.
+ fw_testim.mes - FunnelWeb customer testimonials!
+
+The original release kit of FunnelWeb is in
+
+Machine : sirius.itd.adelaide.edu.au [IP=129.127.40.3].
+File : ~pub/funnelweb/funnelweb.tar.Z
+ (=directory tree in ~pub/funnelweb/..... (less the tar file!))
+
+That's all the information released on FunnelWeb so far.
+
+Currently, I have stopped working on FunnelWeb in favour of other
+projects. However, I have decided to spend a small amount of my time
+acting in a coordinating role to make FunnelWeb more widely known and
+to organize its users so that they can assist each other.
+
+The most unfortunate aspect of my lack of time for FunnelWeb at the
+moment is that I do not have the time even to update the source code
+so that it will compile properly on the variety of machines that
+FunnelWeb users have ported it to. Instead, I have simply organized
+and archived the porting information provided by FunnelWeb users.
+Getting a new version out is at least one week's work and I just don't
+have a week at the moment. The worst case is FunnelWeb for the PC
+which doesn't quite compile (I took some shortcuts at release time).
+As this is such an important platform, I have included a PC .exe file
+in the archive. Note: There have been few reported problems with
+getting FunnelWeb to compile on the other three supported platforms:
+Suns, Macs, and Vaxen.
+
+The three support activities I intend to pursue are:
+
+ * Advertising FunnelWeb.
+ * Running the FunnelWeb mailing list.
+ * Maintainance of a FunnelWeb archive.
+
+The archive consists of a set of text files (what you are reading is
+one of the messages). Each message is headed with a "Guru" header
+record. "Guru" is my private text file database which I might release
+one day. Most of the content of the message files has been drawn from
+the email that I have received from FunnelWeb users. In organizing all
+this material, I have tended to omit people's names and email
+addresses for two reasons:
+
+ * It would take too long to obtain permission from each person
+ to quote them publicly. This has been a real headache.
+
+ * I don't want to punish people for emailing me about FunnelWeb
+ by listing them publicly as having performed particular ports
+ etc, so I have refrained from listing the names and email
+ addresses so that they won't be barraged by email.
+
+Thus, most of the information is paraphrased from the email. To avoid
+these problems in the future, I am making the rule that anything sent
+to the mailing list has public status.
+
+I hope that this archive will assist FunnelWeb users. If you have
+anything that you think might benefit other FunnelWeb users, email it
+to me, and I will place it in the archive.
+
+Ross Williams
+ross@spam.adelaide.edu.au
+Creator of FunnelWeb.
+
+--<End of document>--