
------------------------------------------------------------ Commercials end -

           ________      ________      ______________      ________
         __\___    \_  __\       \_  __\_________    \_  __\       \_
        /     /_____/\/\  \_______\\/     /     /     /\/\  \_______\\
       /     __/\   \/  \__\___    /     /     /     / /  \__\___    \\
      /_    /\ \ \__/   /   __/   /_____/     /     / /   /     /_____/
      \ \__/  \_\/  \  /    \     \    /_____/_____/  \  /     __/__\
       \_\ \  /      \/_____/     /\___\     \     \  /\/_    /     /
          \_\/            \/_____/      \_____\_____\/    \________/sYz


                          p  r  e  v  i  e  w

                        p  i  c  t  u  r  e  s


------------------------------------------------------------------------------

Following files are origin files of the package 'FAMEPrev.lha'

FAMEPreview.txt                 14426 bytes.
FIM_FAMEChat.iff                 8946 bytes.
FIM_FAMEFulled.iff              22108 bytes.
MP_AwaitScreen.iff              12598 bytes.
MP_Intern_UserEd.iff            33002 bytes.
MP_Options.iff                  14770 bytes.
MP_PublicScreen.iff             25326 bytes.
MP_XPR_Download.iff             37432 bytes.
MUI_UserEditor.iff             103498 bytes.
SE_Conferences.iff              82058 bytes.
SE_Doors.iff                    79282 bytes.
SE_SystemEditor_Nodes.iff       65990 bytes.
SE_SystemEditor_Serial.iff      75812 bytes.
SE_XPR_Settings.iff             83648 bytes.
SV_Server.iff                   87162 bytes.

All of them are included in the directory 'FAMEPreview'.
You can delete all other files, they are only BBS-adds.

------------------------------------------------------------------------------




                                 Welcome!

                                ~~~~~~~~~~



The package 'FAMEPrev.lha' is for all those people who have already heard or
read about FAME and for all interested in new software developments.

Many of those people who have already heard about FAME BBS might have some
questions about FAME, because you may have read many good things about it
in documents from tools/doors coded by members of tRSi/X/F/T-iNNOVATiON,
like CD-Server, MUI-MegaView, NewFiles, dRE!REQUESt and many other.

This package consists of this text file which you are reading now and some
preview pictures of FAME.

The pictures are in Multiscan Productivity with 3 or 4 bitplanes means
8 and 16 colors in a size of 640x480.

Sorry about some little graphical errors in some pictures. They are surely
not normal, this is a result of converting the pictures from some overscan
sizes down to standard Multiscan Productivity 640x480 size.

Every picture name in this package begins with an index which indicates
one of the following categories:

SE  : FAME SystemEditor
SV  : FAME Server
MP  : FAME MainPart (Node)
FIM : Fame Interface Module (Door)
MUI : FAME tools using MUI
      MUI - MagicUserInterface (c) Copyright 1992-95 by Stefan Stuntz


Now let me tell you something about every single picture:

SE_Conferences.iff:

 - Shows the 'SystemEditor' and the 'Conferences-Editor-Window'.

SE_Doors.iff:

 - Shows the 'Door-Editor-Window' of the 'SystemEditor'.

SE_SystemEditor_Nodes.iff:

 - Shows the 'Nodes+MoreNodes-Editor-Window' of the 'SystemEditor'.
   Note that there is no node limit as it seems to be in this picture,
   because this picture is older and no longer up-to-date. There are no
   real limits given in FAME aparat from the ULONG/LONG size limit.
   There are no longer limitations in the current existing SystemEditor.

SE_SystemEditor_Serial.iff:

 - Shows the SystemEditor and the 'Serial-Modem-Screen-Editor-Window'.

SE_XPR_Settings.iff:

 - Shows the 'Transfer-Editor-Window' and the Server in the back.

SV_Server.iff:

 - Shows the Server alone.

MP_AwaitScreen.iff:

 - Shows the nodes 'Await-Screen'.

MP_Intern_UserEd.iff:

 - Shows the two screens of the nodes internal user-editor.

MP_Options.iff:

 - Shows the nodes first options screen.

MP_PublicScreen.iff:

 - Shows the nodes abilities as a public-screen.
   This is wonderful for door-coder. They can have editors, shells and
   everything else on the node-screen. There also exists a tool from
   Bloodrock/TRSI to switch between each open public-window and the
   node-screen-window to make it easy via hot-keys to activate the
   next window just like in an editor.

MP_XPR_Download.iff:

 - Shows the nodes xpr(z)modem.library based 'Transfer-Window'.
 - Hydra is also been showed in MP_PublicScreen.iff, but more in the
   background.

MUI_UserEditor.iff:

 - Shows the excellent external MUI based 'User-Editor' for FAME.

   This one is programmed by Siegel/TRSI and will be a part of the
   registered FAME-package and this in the full-version.

   Watch out for other great tools from Siegel/TRSI, FAME only or
   /X based. Until now Siegel/TRSI has written as FAME-only-tools the
   following doors and tools:

   - Lastcallers (Bulletin-tool like SamiLog, but faster)
   - Page-Master (SysOp pager door with many options and highscore)
   - MUI User-Editor
   - MultiTop (A very fast multi-bulletin creater with 12 different bulletins)
     This tool needs between 3-4 seconds to create all 12 bulletins!
     This results of speed optimized code and the easy handable logfiles
     of FAME.

   There are also many other doors written by Siegel/TRSI for /X which are
   all running perfectly under FAME. Some of them, like CD-Server are
   taking usage of the advantaged XIM-Port under FAME if they are
   running on FAME.

FIM_FAMEChat.iff:

 - Shows the FAMEChat for FAME which will also be a part of the
   registered FAME-package of FAME.

   This is a chat as no one has seen it before. You have two different
   chat modes, a 'FullChat' and a 'Line Chat' display.
   FAMEChat automaticly reacts on every changing.
   For example, if a user is using the FullChat and there are more and
   more users entering the chat session until there are suddenly no more
   lines available for displaying all of the users, the chat will jump
   automaticly into the LineChat mode, but that's not all! There is a big
   difference between console and terminal side. The user on the terminal
   side can be in LineChat mode while on console (node) the SysOp can see
   the same chat-node in the FullChat mode. FAMEChat will also have many
   nice features like multiple chat sessions, private sessions and many
   more.

   FAMEChat is programmed by Bloodrock/TRSI, a really great asm-coder
   and a high optimizer. He also is the programmer of the amazing
   FAME.library which is a fundamental part of FAME.
   This library also contains many nice functions not only for
   door-coder.

   Bloodrock is also the programmer of the FileId.library.

FIM_FAMEFulled.iff:

 - Shows the mighty 'Full Screen Editor' of FAME which will be a part
   of the registered FAME-package too.

   This editor is more as a "normal" fullscreen edior.
   It's origins are based on internet's emacs, but not every command
   is the same, they are a little bit changed for "normal" mailbox users.
   This editor is faster than light and gives you many nice tools to
   work with like yank-buffer and an integrated script language which
   is full compatible to the script language of FAME.
   This script language is similar to the installer language of the
   'Amiga Installer'.

   Beatnik/tRSi is the programmer of the amazing FAMEFulled.
   He also writes the script language for FAME and several other tools.

------------------------------------------------------------------------------


Now some simple words about FAME.


FAME is coded totaly system friendly and is very fast.

FAME is hardware depending what means that if you have more and better
hardware you can do more with FAME.
The only limit FAME has is your computer-equipment!

FAME uses everywhere dynamical lists, in some parts bi-directional and
more-dimensional. Because of this FAME uses no megabytes of memory and
is also very fast. This was one aspect i ever want to realize in FAME...
...speed! And yes, it's fast and this with no exaggerate memory usage.

For example the executable size of the MainPart (node) is now about
357024 bytes. The first node uses overall about 498 kb memory
(incl. codesize etc.), from the second node on each next node uses 458 kb.
The next nodes are using less memory, because they share datas over the
Server. The Server loads for example config datas once and reaches them
over message ports to the nodes. The conference datas for example will
be read into a list and a pointer will be given to each node.
But you can save more memory for each node, because you can start the
MainPart (node) resident. If you start the nodes resident each node uses
about 110 kb of memory, because the big code size now only exists once in
memory. Not that this values are relative. You should always have about
one megabyte of memory free if all your nodes are started, because not
only the nodes, doors too, are using sometimes temporary some larger
sizes of memory, for example: filelistings. This is a reason of speed.
The nodes are trying to load a filelist completely into memory if a user
views it, but if there is no more memory left for this the nodes will
view it directly from your harddisk.

The MainPart can be loaded resident into memory in spite of it the node
takes usage of the xpr<z>modem.libraries.
I have to thank Bloodrock for this, because we have solved together
in coorperation the A4 near data pointer problem. If everything went
well until the release of FAME, the pool functions of the FAME.library
are ready and will be consequently used in FAME. This reduces memory
fragmentations drastic, because the FAME internal lists will use them
and this also under AmigaOS 2.x .

If you are interested in the file sizes of the Server and SystemEditor,
here they are: Server: 61144 bytes and SystemEditor: 200180 bytes.
The MUI User Editor has a file size of 40592 bytes. The sizes may grow in
future. You now may ask yourselves why the hell the SystemEditor is about
200180 bytes long. This is because the SystemEditor does everything for you.
If you start the SystemEditor the first time it will generate everything
for you to run a single node BBS. You only have to do personal settings.
The SystemEditor is a mighty part of FAME and if you see the SystemEditor
someday by yourselve you will know why the file size is so high...
there are lots of windows and gadgets, because you can configure nearly all.

To show you the extend of FAME here are some more statistics:

FAME uses more than 15 own and some OS lists.
FAME exists of more than 40 different structures.
FAME knows about 1000 FIM door commands.
FAME User.Data currently has about 116 different options.


As you already know FAME will be configured via the full gadtools driven
SystemEditor, there is no boring ToolType inserting in more boring icons
and also no stupid configuration through ascii questions on a special screen.
You control everything of your BBS via the heart of FAME the Server,
where Server is a totaly wrong word for, it's more a Master.
SystemEditor and Server are commodities for easy usage.

Under FAME you can use 90% of the current existing /X Doors and Paragon
based Doors also.

The FAME own door system, called FIM, owns now about 1000 commands from
which a door coder can use more than a third, the rest is undocumented
and restricted, because those commands are to dangerous to use if you
not really know what they do. Theoreticly a door can take over a FAME node
on start and can take usage of every single procedure and structure of the
node. Some restricted commands are available for FAME developers.

There are curently existing 7 FAME Supporters in the FAME Supporter Team.
FAME has lots of informations and guidelines for door and tool coders.
The FAME Supporter Team has more informations about restrict commands
and structures of FAME than normal door and tool coders will have, but
a FAME Supporter Team coder also must strictly code with the guidelines.

There is many more to say about FAME. There are so many features to tell
that this will be here a never ending story. In FAME exists until now more
than 3 years of hard work, because of this fact this system must offer
many interesting stuff. I insure you it does! But i've decided not to
write down all those features, because FAME is still under development
and the competitors are everywhere.

I hope this text will give you an introduction about FAME, but you can see
it in the near future with your own eyes when i release the first demo
version. You will find it in the AmiNET then.

If everything went well, this demo version will be released at the end of
this year.

There is no really decision made about how and when FAME will be full
released.

The price is also not clear yet, but it won't be too expensive.
You will get quality and a thought-out mailbox engine for your money.

I decided to give you this preview package about FAME, because there
are lots of people which have heard about FAME, but the more important
reason is that i want to do my part for the Amiga. I've seen in the last
year too many people gone to the PC, also sysops which were no longer
statisfied with Amiga mailbox software.

Might ESCOM with Amiga Technologies will push through their competitors
and will bring the Amiga back to the top!

But if you can't wait until the release of FAME, give the following BBS
a call to see FAME now:


       pUNISHMENT iNC. (tRSi/X/F-iNNOVATiON) GERMAN HQ (SYSOP SieGeL)

            Node 1. +49-30-694 8470      Node 2. +49-30-694 8570

                   << FAME support and develop BBS >>



               You can reach me in this board under Strider.



                                I am:

                        David "Strider" Wettig

                  If you want to contact me via e-mail:

                       strider@deadline.snafu.de



             You can also reach the following FAME developers
                via e-mail or in the pUNISHMENT iNC. BBS:



       Oliver "BloodRock" Lange        Bloodrock@funboard.in-berlin.de
       Ulrich Arne "Beatnik" Jansen    beatnik@cs.tu-berlin.de
       Sascha "SieGeL" Pfalz           siegel@deadline.snafu.de

-------------------------------------------------------- Commercials restart -
