
--55--

Even with the amazingly extensive MCI codes.  Are things like:
> Uploads:     5 @   23443 bytes
> Downloads:  12 @ 1902922 bytes
possible?  Left/right justifying?  No columns of #s can be correctly
displayed without it.

Or any kind of bordered display:
-----------------------
|                     |
|  4 D/Ls             |
|  239483 Bytes       |
|                     |
-----------------------

> Uploads:   /Vf /Vh        (no formatting)
> Downloads: /Ve /Vg

> Uploads:   /-2Vf /-7Vh        (standard C formatting)
> Downloads: /-2Ve /-7Vg        (right justify)

> Uploads:   /+2Vf /+7Vh        (standard C formatting)
> Downloads: /+2Ve /+7Vg        (left justify)

Luckily no MCI codes start with a number, so it would be an ideal
place to put formatting values.  (Between the "/" and the "MCI code")

--56--

Can a string be displayed if a user hits ABORT during a non-abortable
text file display?

<<CTRL-C IS IGNORED>>

I can imagine some users not familiar with Cnet, trying to hit a
variety of abort keys in frustration before the realize they can't
abort at all.

SysOps not wanting this string could remove it from BBSTEXT.

--57--

Is there a way to make the MORE prompt smarter?
If a user can't answer NO anyway (due to /A1 usage) why keep asking
him "More? YES/NO/=?" over and over again?
I see callers answering NO several times before the realize they can't.

BBSTEXT would need 2 strings:
1) More? YES/NO/=
2) More? YES
(#2 could be changed to just "HIT RETURN FOR MORE" too.)

--58--

When a user's charges run out he's automatically locked out of the
system forever?  Any plans for 2 new values to BBSCHARGES?

4     <-- When user's $ runs <0,      he's dropped to this level (-1=no log-in)
1     <-- When user's $ runs <MINBAL, he's dropped to this level (-1=no log-in)
-500  <-- MINBAL  Minimum allowed balance    (cents)
1     <-- DAILY   Assessed 1st call in any day  (cents)
2     <-- MONTHLY Assessed 1st call in any month   (cents)
100   <-- CONNECT Per minute of connect time      (hundredths)

Or some kind of "gradual lowering" then "lock-out"?

--59--

>3) ANSI support : No
>5) Screen width : 80
>7) ANSI tabs    : No
>2) Graphics set : ASCII
>6) Screen height: 24
>8) ANSI color   : No
Exactly which settings need to be on/off before the visual editor can
be used?

>(The visual editor is for) 80 column ANSI terminals only.
It seems to be more than just "3) ANSI support" and "80 columns"
that is needed.  I need to tell users EXACTLY what they need on/off/set.

--60--

Are there subboard MCI codes for quick displaying of:
>Uploading here will get you 200% additional time online.
>Uploading here will effect your file ratio at 100:1
>Uploading here will effect your file ratio at 1:1
>Each upload here will credit your account $5.00
>Each upload here will credit your account $0.05
>Each byte uploaded here will credit your account $0.10
>Each byte uploaded here will credit your account $0.01
>Uploads here count for 250% over the normal credits.
>Each file downloaded here counts as 300% more than usual.
>Each byte downloaded here counts as 200% more than usual.

Excellent ways to encourage U/Ls.

--61--

Arexx's "getuser structure 5-digit offset" command may very well be
the most powerful one in the whole package.

Is an MCI equivilent available?

--62--

> Custom appended signature files:
>
>  0.  Default (other files override)
>  1.  Mail and Feedback
> *2.  UUCP messages
> *3.  FIDO messages/handles
>  4.  FIDO messages/real names
>  5.  Other messages/handles
> *6.  Other messages/real names
>  7.  Upload descriptions/handles
> *8.  Upload descriptions/real names
>(*Already in use.)

Are these strings in BBSTEXT?  I'd like to automatically tell users
which they have/haven't already edited.  (Instead of making them
load/check/save them to find out.)
> %d.  %s\n
>*%d.  %s\n

-Bill Allen Beogelein, Amiga ShareWare HQ, 313-473-2020, 1:120/207
