
--103--

Is there a way to make the "AM" activity monitor cmd available to
everyone, instead of just SysOps?  Nice formatted info and tons of it.
There really isn't anything too 'private' about that data.

--104--

>Can't match that to a user on-line!
How does "UM" send a msg when a certain user logs-in if it
requires that user to already be online?  Can't we watch for ANY
user (currently online or not) if his name/# is specified?

--105--

Does anyone have a need to quote from 2 (or more) replies?
".Q 5" quote from reply #5.
".Q 8" quote from reply #8.
Great for those items where several different callers are stating
conflicting "facts":

Bill Beoglein says...
BB> 2+2=5

Ken says...
KS> 2+2=4

--106--

EEC [E]mbedded [E]scape [C]odes
TCS [T]ext [C]ontrol [S]equences
EVC [E]xpanded [V]ariable [C]odes
FCI [F]ormatted [C]ommand [I]nterpreter
While you're revamping the MCI codes you might want to change
its name also.
1)  To distinguish them from the current, soon-to-be "old" MCI codes.
2)  I'm always concerned when I see things like "We do/don't allow
    MCI codes to be posted in this base."  Not everyone (including the
    phone company) will know that these are a different kind of "MCI Codes".

--107--

What is the quickest way to read a certain response?
>READ 23.10
Read item #23, starting at response #10.

--108--

SysData:log.U+Dloads...
>G 24  230  1-Aug 11:59 Bill Allen          DOSPLUS0.ARC          14 SWHQ/
>Y 24  232  1-Aug 12:59 Bill Allen          DOSPLUS1.ARC          24 SWHQ/
>Z 24  239  1-Aug 13:59 Bill Allen          DOSPLUS2.ARC          34 SWHQ/
>U 24  236  1-Aug 14:59 Bill Allen          DOSPLUS3.ARC          44 SWHQ/
 ^
 |
I assume this means "unfinished" transfer.
This should be noted IN ADDITION to, (not instead of) the protocol used.
How do I know which protocol is failing repeatedly?

Maybe:
>ZU24  236  1-Aug 14:59 Bill Allen          DOSPLUS3.ARC          44 SWHQ/
or
>Z-24  236  1-Aug 14:59 Bill Allen          DOSPLUS3.ARC          44 SWHQ/
 ^^
  \\
   \It's unfinished.
    Zmodem was used.
(Also gains consistency with online format:  "-" means unfinished.)

--109--

Now that C-net can run DOS-pfiles directly online what are the
pros/cons of author's writing them instead of C-pfiles?
Pros:
   1)  Can be tested/debugged right from the CLI.
   2)  No need to deal with communication ports, get/return to BBS.
   3)  Portable to/from other BBSes.
I am assuming that DOS-pfiles can get/set all the variables
that C-piles can?

Can't DOS-pfiles replace C-net pfiles entirely?
If so, we should encourage their use exclusively.

Who has a list of things that C-net pfiles can do that DOS cmds
(used online) can't do?

--110--

>Quit, Scan, New, Old, [All]:
I wasn't even aware that I could enter Msg #s and ranges at this prompt.
>Quit, Scan, New, Old, [All] or Msg#:

--111--

Any plans on standardizing all single keystroke choices everywhere?
"If it's a prompt where only 1-letter choices are needed, then it's
always hot-keyed (no return needed)."

Users never need wonder (or wait for) (or accidentally) hit RETURN
when it is/isn't needed.
> Log-in scan for new files:              (hot-keyed)
> Sex [Male/Female]:  M                   (not hot-keyed)
> Scan messages now [Yes]? No             (hot-keyed)
> Logoff upon completion, Abort, [Begin]: (not hot-keyed)
> Kill all messages [No]? No              (hot-keyed)
But all only accept 1 stroke input anyway.

--112--

The [OR]der and the SysOp's [A]rrangement choices...

When 5x6x7=125 udbases and 5x10x12=500 bases need to be set, the quicker,
the better.  If we could pick a sort-type on per-dirs, instead of per-base,
we could quickly set a large # of bases with a single [OR] [A] cmd.

>Telecommunications> OR 4  (then pick sort-type from given menu)
(I just set the 6x7=42 bases within dir 4)

>Amiga> OR 2 (then pick sort-type from given menu)
(I just set 5x6x7=125 within dir 1)

(Personally, I think allowing 7 types of sorting choices for EACH
individual base and individual udbase is overkill.  Setting them per-
dir would be plenty.  Most BBSes don't even allow that.  Or even
allow 7 sorting types at all, for that matter.)
You can set sort-type for:
1) The whole system:
> Set sort-type for all bases:
> Set sort-type for all udbases:
> Set sort-type for all bases in current dir:
> Set sort-type for all each bases in current dir:

> Set sort-type for this dir:
instead of the current
> Set sort-type for this base:

--113--

If a DOS cmd gets a key-hit without needing a RETURN, should this work
in the same fashion when that cmd is placed online as a pfile?

Or I guess the real question is:  "How SHOULD a standard DOS cmd
be getting a hot-key response so it'll work as such from both the CLI
and as a c-net pfile?"

For Aztec users it's something like:
> set_raw();        /* turns raw on */
> c=getchar();
> set_con();        /* turns raw off */
Which works from the CLI fine.
As a pfile it still requires a RETURN too.

--114--

Did C-net at 1 time have a libs:cnet.library file?

--115--

Is there a way to make /MCI codes that run DOS/arexx/pfiles just
display EXACTLY what those cmds output?
They are instead currently displaying:
> /n
> The cmd's output.
> /n

This makes formatting difficult, if not impossible.  SysOps that
DO want the 2 extra L/Fs could still have them.  (They'd just
have to specify them in the text file.)

Things like:
> You currently have /#4c:MyOutput/ remaining.
would then work.

So would:
> You currently have /n /#4c:MyOutput/ /n remaining.
If you DO want C-net's current "I'll add the 2 LFs" for you method.

--116--

Have any SysOps experienced callers that stay online far, far longer
than they should be allowed due to C-net's "no cut-off while writing
a msg" feature?  I like the feature but within certain reasonable limits.

If you have 5 mins left, you can stay online 2 hours (or more), as long
you are writing 1 msg.

Perhaps a config value.
0    (When a caller's time runs out, they are disconnected.)
10   (When a caller's time runs out, they are warned and given 10 mins
     to finish up.)
999  (When a caller's time runs out, they can stay on for 999 mins.

--117--

Would anyone use a "pay kickbacks" flag, if available?
SysOps could mark certain files as "pay kickbacks".  These would still
cut into file/byte credits, as D/Ling does now.  But they would have
the additional effect of rewarding the U/Ler with credits (file and
byte) each time his U/L is D/Led by someone.

"Your last U/L has been D/Led 52 times, so far."
"You've gained x file credits and y byte credits due to this."

"You will gained B file credits and C byte credits each time your
 file is D/Led by others."

I think this would greatly encourage users to U/L better/popular files
that they know are going to be heavily D/Led/needed by everyone.

Perhaps, whatever file/byte credits it COST the D/Ler to D/L this
file, x% of them would be ADDED to the U/Ler's credits too.

--118--

>you entered the Vote section,
>you were taken from one new topic to the next as answered.

It depends.  Does this mean a caller will have to choose between
answering "ALL the questions" or "none"?
I'd like to see a way to allow the SysOp to 'group' questions together.
1-n would be a "set".  5-n, etc.  If a caller picked a 'group', then
it WOULD go through them all 1 by 1.  It could be done keeping the same
'sub'dir structure as bases/gfiles/pfiles/etc...

SysOps could "force" a group of questions ALL to be answered.

Additional, if a sysop did NOT "force" a group, the caller could
still ask for question #s by 1,5,10-20 ranging.

--119--

> (3)  I would like some other way of importing tic files.
>      SO that tic files are imported with info like original
>      node of origin. I will again upload a sample tic file.
>      And instead of listing me as the uploader, have it list
>      the area the file was hatched into.
How about both the ADS area and node # appearing as "Uploader"?
Uploaded by:  "ADS_SOUND 1:120/207"

--120--

> (5)  A better way to edit access groups (EG). Maybe sort them into
>      subgroups like they are for EA. Even EA could use some improvements.
Just a "copy group TO FROM" would do wonders.
A new SysOp would define GROUP #1, copy it to GROUP #2.
Tweek a few changes, copy it to #3.
Tweek a few changes, copy it to #4.
Tweek a few changes, copy it to #5.
Each 1 would be an increasing level of the previous one.

Where is a newly created group currently getting its defaults from?

It would also help a new-sysop set things up if C-net came out-of-the-box
with a few bases/udbases/groups all ready installed.

--121--

> (6)  From the 'countdown to logoff' you should be able to
>      Press SPACEBAR to Abort, or press H to Hangup now.
How about "O" to hang up to remain consistant with "OFF"?
Fewer new cmds to memorize.

--122--

> (13) Ability to open CNet Ports as windows on the workbench.
DEFINITELY!  You could re-size/position a 4-line system and keep an
eye on all 4 windows at once.  Zoom-gadget them full/partition open
with a simple, single mouse click.

Ask an 8-line SysOp what memory it costs to open 8 additional 4-color
screens instead of 0, (if the already open WB screen is used instead).

--123--

> (15) Some Pfile source code to come with CNet. At one time you
>      gave us source to Vote, The Online Store, and a few examples
>      of using various functions. Also better commented Function
>      calls. Myself I would like Amaint source, and Userlist.
>      More comments throughout. We cant read minds.
I thought for sure there was a fairly large C-net Programmer's
archive available last year.  Not finding it on the 2 disk BBS set
these days.  "We cannot code, what we do not know."

--124--

> (16) Could you devise a program or method of us attaining the proper
>      getuser values for Certain variables in CNet.h.  Right now you can
>      figure the first few easily. But after that its majorly confusing,
>      and is more of a guessing game.
Or maybe just list a bunch of the more common 5-codes.

--125--

>Upsmatic Noman writes...
>and make YA not yank from subboards you are not a member of.
I thought this is what it was doing now.  No?

> * 4. Make a USER-FRIENDLY way to see what Base/UDBase areas you are a member
>      of, and to join or drop them. Like:
>
>        UDBase status ('+' indicates you are a member of this subboard)
>        1.         + Uploads                  2.         + Graphics
>        3.         - Utilities                4. (dir)   - IBM
I'd love this.  I thought I heard somewhere that the current storage
method used, would make displaying of this info, too slow.  If so,
maybe release an arexx script or pfile that would do it.  Those
needing it could type "JL~JOIN LIST" and see all their join/drop list.
Those NOT needing it (or finding it too slow displaying) could use
the current [L]ist cmd instead.

I guess even the current L wouldn't be so confusing if the +/- was
ALWAYS shown or NEVER shown.
(Anything, but not its current "mixture of both".)

--126--

If you find that a certain item (and its responses) are of NO
interest to you, can you "FORGET" this item and NOT have to
read any of its future responses?
Later if you reconsidered, a "REMEMBER" cmd would once again
allow it to be read.

--127---

>Yes we need options for Amaint. I didnt see an ADOPT orphan
>in there, which I would like seperate.
-a Adopt orphans in msg bases
-A Adopt orphans in udbases

-Bill Allen Beogelein, SysOp 313-473-2020, 2-line HST 14.4k USR DS, 1:120/207

