
--1--

I haven't yet been running C-net full-time.  But rather experimenting
with its many features in local-mode.  If any of the following
suggestions are already possible, please excuse it.

--2--

I assume that the particular node needs to be running before
its companion bbsEvent# file is put into effect.

Is there a bbsEvent file that would be valid ANYTIME the control panel
itself is running?  BbsEvent24 perhaps?  Effective regardless of which
nodes are on or off-line at any given time.

I hate to set-up and continuously running a 2nd non-Cnet housekeeping
program just to a handful of other non-Cnet related tasks I need done.

(Especially when C-net's is already running and it's full-featured.)

--3--

Is there a way to open/close a Cnet screen under software control?
Screen "OPEN" would work like a double-click on the control panel.
Screen "CLOSE" would work like a LeftAmiga-I on a Cnet screen.

(I need to automatically open/close screens when I'm likely/unlikely
to be at home/work/play.  But it could also be used to pop the screen
open/close only when a caller calls in, or certain low-baud users, or
during certain menu cmd execution.)  (via DOS/MCI codes.)

Also, is there a way to do a screen refresh when a screen is (re)opened?
The screen remains blank until the caller hits a key.

--4--

Are the individual log.port#s being automatically deleted AFTER every
call?  Wouldn't it be better to clear them BEFORE every call?  That
way we could still see what the last caller did.  As it is now, all the
valuable, detailed record of his visit is gone the instant he hangs up.

--5--

There are several commands that ask:
>\n1Port, handle, or *=ALL:
Is there a way to also allow "WHO" at this prompt also?
>\n1Port, handle, ?=who, or *=ALL:
(Callers can't know port/handle to needed chat, otherwise.)

--6--

It's great that I can shut off any/all "\?n" prompts in BBStext with
"\=n".  But what about the many "\In" "\Gn" calls?  Can defaults be
set and more importantly, removed entirely?

--7--
Is there an MCI code to display a user's access # (not access name)?

--8--

>Item: 1
>Subj: test
>From: Sysop  (Bill Beogelein)
>On  : Tue 21-Jul-1992  3:40a
I'm still getting inverse chars in the 1st 5 chars of each line
of all msg headers.  I've got no ANSI tabs, no ANSI colors, no ANSI
no ANSI support set.  Anything to do inverse filtering also?
(Short of removing it from BBSTEXT entirely and from everyone.)

--9--

Is there a way to D/L a file, based on the filename only?
(And regardless of which file area you are in.)

So I can tell users "D/L FOOFII.LHA".
Not "Join area 4, subarea 2, subsubarea 6, and D/L file #435,
that is, if it's still called #435."

Two things:
1)  D/L by name.   (Regardless of item renumbering, etc.)
2)  D/L globally.  (No need to do a search to find the file,
(it only gives you the subsub area name/# anyway.  Not the full
path to it.)  move to that area, D/L by # only.)

--10--

If a "MODEM x" bbsEvent has "CLOSED DEVICE" shouldn't the control
panel being displaying this very important fact?

Also, any plans on adding this "No I/O" feature to the control panel
or node's pull-down menus?  Great, quick way to free-up a modem w/o
closing/re-running that node.

--11--

>Z and ZG...
Is there a way to distinguish between "search titles only" from
the current "search every response to every item"?

(The latter can be quite time-consuming with 5 areas, 5 sub areas,
each with 50 msgs, each with 20 responses.  (25,000 searches instead
of 1,250.)

--12--

If you know a file/msg is in "Area 5: Graphics", how do you move to
it as quickly as possible?  If a system has 6 areas, each with 6
subareas, each 6 subsubareas, that's 216 places for it.  36 different
"Area 5"s.

"Area 2.4.5:  Graphics"  would do it.
(It would be interesting to see how many SysOps would use this feature
if there was an MCI code that expanded in the full area # path "2.4.5".)

--13--

If I don't want a user to have ANY MCI ability how does he still
post c-code/etc with common "\n\t\r" chars in it?

I can't justify giving him access to bells, colors, cursor positioning/
dancing, backspacing, label jumping, kolorific, printing up/down/
backwards, inverse, underline text, just to allow source code to also
be posted.  (But I certainly don't want to restrict the source-code posts
because of it.)

--14--

Are there any plans to add MCI cmds for:
"Item #"
"Title"
"Size"
"U/Ler name"
"U/L date"
"File Description", etc
So that custom msg/file headers can be displayed?

This is by far the least configuratible part of any otherwise
VERY flexible package.

--15--

Is there a way for someone (with the right access) to edit the
actual post and response msg text?

--16--

The control panel's CLEAR LINE menu is identical to a port's HANG UP
menu?  I always wonder about things like this.
(Different wording for the same things.)

--17--

Is a CLOSE SCREEN available from the control panel (in addition to the
1 on each port).  It would work the same, but you wouldn't have to shuffle
through 5-10 screens to find the 1 you want to close.

--18--

Any plans on removing the "You have to JOIN an area just to DROP its
subareas".  DROP ALL should DROP ALL.  JOIN ALL should JOIN ALL.
(Maybe prompt the user to verify that he is about to also drop (list
the areas) these subareas within.)

Anything to help quickly set-up my scan-list on those 100-200 area
BBSes.  Anything would be better than:

Join Unix, then join each of 10 subareas, just to be able to drop them all.
Join Atari, then join each of 10 subareas, just to be able to drop them all.
Join Mac, then join each of 10 subareas, just to be able to drop them all.
Join IBM, then join each of 10 subareas, just to be able to drop them all.
Anything to avoid this time consuming task.

In addition (not as a substitute), has anyone seen a door that would
list ALL areas and prompt JOIN/DROP for each.  Great for setting things
up on your 1st call.   (As well as SEEING everything that is available.)

--19--

Any plans on adding a LOAD CONFIG pull-down menu to the control panel?
(Load new bbscontrol, bbstext, bbsconfig, bbsmenu, bbscolors, bbsevents,
bbskeys, etc.)

Am I correct in assuming a 5-10 line system has to wait (or boot) off
all callers just to enact some small (or big) change made to the
config files?  (I plan on editing these frequently and still want
my system online as close in 100% of the time as possible.)

--20--

It's real easy to fill-up 10 functions keys.  Especially when they are
5+5 print/stream.  I'd love to see 20-30 (norm/shift/ctrl).  As well
as NO print/stream FIXED 5+5 setting.

1)  Any lines that start with a "\" are print only.
2)  Any lines that don't, are input-stream.
Set them up as needed.

--21--

Can the dial-out TERM be restricted with a sys.dialout file?  I'd be
more likely to give users access to it if I could limit them to
calling across town instead of Europe.

sys.dialOut would contain phone #s in the same format as sys.avalid.
TERM-ACCESS would not be a bit, but rather a value 0-9999.
The caller could legally call-out to any phone #s matching the first
x lines of sys.dialOut.  Local #s would be placed near the top of
the list, and gradually more expensive ones near the end.

(More info is in my MASTER.LHA file.)

--22--

Is Zmodem supported for msg U/Ling instead of just xmodem and ASCII?

I have 1000s of other ideas.
Bill Allen Beogelein
313-473-2020 2-line, USR-HST 14.4k DS

