Orion/AdeptXbbs

*****************************************************************************

DisClaimer:

******************************************************************************
4.2w
1> Fixed an inconsistency in the SRIF path processing.
2> Renamed the executable to Orion.Exe since there is another team at work
   on another version of AdeptXbbs derived from the Vac builds of 111yb or
   thereabouts.
3> This will be the last build for quite some time as I have become busy with
   real life these days. This build should be quite bug free and stable, there
   is one known problem at time of this release, the change fonts for the
   bbs windows does not save properly, the font size changes for that session
   but next login does not have the saved font (oh well).

4.2a
1> Fixed a nasty memory overwrite in a heavily used portion of adeptx, this
   was likely resposnible for a lot of the erratic, random traps adept would
   sometimes experinece.
2> Reenabled the change font menu on bbs screens
3> Telnet server now works properly.
4> startup sequence still sometimes has probs, (Looking further into this)
   if u get nodes stuck in a starting or initializing state, shut it down from upper
   left menu close option and restart, chances are it'll come up fine. Seems to be
   related to heavy disk usage, but who knows...
5> Shutdown now works properly. (unless it never got all the way up, then it still
   has probs, just close it if that happens, or let os2 end it from ctrl esc
   button)
6> menuitems with blank dataoption strings no longer cause problems.
7> smtp import now works properly, note area can be squish if u want it to be.

4.11x
1> Fixed Unuke.exe, it now works as advertised.
2> Did some more work on the new cserver.exe.
3> Fixed the startup/shutdown sequence when starting lots of nodes on a busy
   system, Adept now hits the cpu *HARD* on startup. If it's too much for
   your system, then use the /DONTSLAM switch to start er up..
4> I have to ask myself, is there any point in continuing this ? I have received
   absolutly no questions/interests/registrations for this product as of yet.
   So I'm seriously considering just letting it die... what say you?
   Comments to mariod@ican.net


4.1w
1> This build should be a drop in replacemnt for adept111 and down
   by following these simple steps,
   1> Delete all *_Configuration files in \adept
   2> Delete All *.Bin files in \adept\menus
   3> Fire it up in /setup mode, configure to your liking,
      shut it down, and bring it online normally.
2> Note: the users file should be safe but back it up just in case

4.1u
1> Adept now supports 6144 nodes PER COPY *BUT* you can run as many copies
   as u have machine or network to support, they will all quite happily share
   all config files cept for the linex configuration and log files. These are specific
   to the Case (instance) of adept running, but msg/files/user/bbs/menus/text
   etc configs are the same for all copies, giving u virtually unlimited nodes
   outta the box. To start a second copy of adept just type Adept /Nodes x /StartAt 2
   where x is number of nodes for this copy up to 6144 and 2 is instance 2 of adept.
   just replace the 2 with a 3 for a third instance and so forth.
   Note that when running multiple instances of adept there is only 1 outbound manager
   it lives on the first instance only. However mailer nodes are active on all
   instances unless u check the no mailer option for a particular node that is.
   Note: That OS/2 only supports 4k threads and each node of adept is a thread,
   so......<g>



4.1t
1> After much fuqing around with watcom v11.0a and repeated calls to tech support
   we have come to the conclusion that it is broken as far as compiling a large
   complex project like adept, they have kindly given me a copy of 10.6a which
   seems to be compiling/linking adept just dandy.
   Recompiled all code that i have access to with the new compiler.
2> More miscellaneous cleanup and general speed improvements, started 384
   nodes here on my machine with 48 megs o ram and a 48 meg swap file before
   I ran out of threads, can prolly start 512 on my configuration, anyway
   this build supports 2048 nodes outta the box, would love to see the machine
   with the memory to run this beast, note startup and shutdown are kind slow
   since it takes time to close/open all the various logfiles for each node,
   shutdown can be hurried up by clicking close in the upper left pulldown stead of
   the usual shutdown on/off hook selection.
3> Line configs and events files are no longer saved on a shutdown *UNLESS*
   you started Adept with the /SETUP option, same for colors and fonts and window
   positions.
4> Added a new command line switch /BEEPS will enable an audible tone on a
   successfull connect to adept on any online node ala SIO's telnet connection
   tone (rememeber that?). If u prefer quiet operation, this switch is not for you.
5> Fixed a memory alloc problem in ansi display routines, was a possible trap
   condition on large files.
6> Increased the total process wide stack space available, this should cure
   some of the spurious traps executing large complex AdeptRexx routines,
   specially those which call adeptmenutype or adeptmenu functions, as the code
   recurses a lot during this execution.
7> Reworked the line configs storage allocation yet again.
8> This build requires u delete all *_CONFIGURATION files in \adept dir
   and all *.bin files in \adept\menus dir and do a /setup to recreate
   them.
9> Set the default line creation configs to telnet ports as most people
   will likely only have a handfull of real modems and its easier to
   edit the few nodes for real modems than 50 telnet nodes, the telnet
   nodes come setup ready to use, just enable the telnet server in internet
   options under config pulldown to start using them.

