EditLogin by Spike Dethman

Arexx mod for C-net 3.05c, allows each user to edit a customized version of
their login sequence, by adding a new command "ELO".

To install:

Copy EditLogin.rexx, sys.EditLogin.rexx, EditLogin.welcome to your Pfiles:


Create a new file called Systext:sys.welcome.default, containing the MCI lines
that run "optional" login mods (usually from the end of your current ttx.welcome
files.)  This will be your "default" options, seen during login by users that
have not yet used the ELO command.  (You can also create tt1.welcome.default,
tt2.welcome.default, etc. for your individual terminal types.)  I've included
examples of the sys.welcome and sys.welcome.default files to give you an idea...

The "optional" lines are the mods that you wish your users to have the ability to
disable.  Do NOT include lines for mods which MUST be run during login, or
mods that should only be run ONCE EACH CALL, such as Last10Callers.


Edit your ttx.welcome files to remove those "optional" lines, and add this one:

{#0 Pfiles:sys.EditLogin.rexx}
^-(ctrl-Q, of course...)


Edit the Pfiles:EditLogin.welcome file to show all the login options you wish
to be available.  The file's format is THREE lines for every option.  The FIRST
line is the option prompt, that will be shown on the editor's main screen.  This
should be 28 characters or less.  The SECOND line for the entry is a description
of what the option can do for the user.  This may be as long as you want, but
must be all on one line.  The THIRD line is the actual MCI command to run the
option.  I suppose you could use MCI in the first or second line, but then the
ELO command would look less like the EP command.  Be sure that any lines that
are also in sys.welcome.default match the corresponding MCI line in this file
EXACTLY- a match-up is done to find which options a user currently has turned on.

You can have as many options in this file as you wish, and I suggest you include
many P-files as choices.  Again, be sure NOT to include things like Last10Callers
and other modules that must be run during login, or only once per call.

BTW... I suggest that you have more options listed in your EditLogin.welcome
than are listed in your ttx.welcome.default files, keeping the default files
just a minimal "basic" login.


Finally, edit bbsmenu and add this line at the end of 2; Available everywhere:
        ELO, EDit LOgin | {#0 Pfiles:EditLogin.rexx}
                          ^-(that durned ctrl-Q again!)

(Don't forget to RELOAD TEXT/MENU, too!)


Copy the file ELO to Systext:Help/, so your users can HELP ELO.  You may also
want to add the command and a description to your Systext:Menu/main file,
so your users know it's there when they "?" at the Main> prompt.


You're all done!


When a user types "ELO", they will be presented with a menu to customize their
individual login sequence, based on the options and commands you listed in the
EditLogin.welcome file.  The editor looks and behaves very much like the EP (Edit
Prefs) command in C-net. The mod will take their choices and put them into a file
in their userdir called sys.welcome.  During login, sys.EditLogin.rexx looks for
this file, and will execute it if found.  If there is no sys.welcome file in the
user's dir, it will instead execute Systext:ttx.welcome.default to complete this
login sequence.

If you should happen to delete or move any of your P-files, be sure to update
the MCI commands in the EditLogin.welcome file and ttx.welcome.default.  Users
with customized logins may see "Can't find: Pfiles:xxxxx" messages for the mods
you moved.  To correct this, the user simply needs to enter the ELO command...
the option that you moved will be shown as disabled, and they may re-enable
it, if they wish-- it will then use your new MCI command.  Simply entering
and exiting the ELO command is enough to remove any outdated MCI lines from
their sys.welcome, though. (If, for example, you have removed a particular Pfile
completely...)

Enjoy the mod... it's Free as usual.

EditLogin was written and tested on my trusty 3M A500, with C-net 3.05c, and
it works great here.  Your machine might catch fire and collapse in a heap,
causing massive damage to your house and all your belongings.  If this happens,
I take no responsibility for any damage to your machine, data, hard drive, modem,
house, or clothes... not even the ones you've stuffed under your bed.  (Of
course, if it works, why not call me at The Codex BBS and fawn me with
compliments about my programming expertise?  E-mail "Spike" at (404) 473-6173
[This will be (770) 473 - 6173 after December 1995])

I've read too many of these Amiga disclaimers, huh?

This is FreeWare.  I give permission to distribute it through any normal
public-domain means, especially CD collections, as long as outrageous fees are
not charged.