
Thursday 17-Feb-94 16:33:47

--1500--

IF> 1101744, and muffle all is getuser 1101745.  Just dig through the file
IF> CNet.h in the programming directory...

Or File Requ "GETUSERS" from 1:2410/207 and get:
> a list of 600+ Arexx 'getUser' values for CNet v2.63-v3.0+ as of Feb94

by "by PMK & Dotoran".

I sure wish they'd mention real-names, phone #s, addresses, Fidonet addresses,
etc in that file too.  Take credit for the enormous amount of work that went
into it.  People ask me about it and I don't know if I'm allowed to say
anything more than "It's from PMK & Dotoran".  Period.

--1501--

On Wed 16-Feb-1994  4:55a, The Wizard said to Bill Allen:
TW> I think that the release updates like 3.05c should have the"bbslicense"
TW> file removed for the registered users, cuz copying this over the other
TW> one makes it a 7-day demo! Just an idea for future releases!

On Wed 16-Feb-1994 12:15p, Bill Allen wrote:
BA> The installer (if it doesn't already) would ask the user "overwrite your
BA> current license file?".

On Thu 17-Feb-1994  1:59a, Jim Selleck said to Bill Allen:
JS>   The installer script CHECKS to see if there is already a bbslicense file
JS> installed and DOES NOT overwrite if so.

I guess "TW" isn't using the installer.

Also, Jim, I asked Ken about making the v3.05c the demo.  Here's his reply...

KP> Yes, the policy will be ANY version is a demo version (with the
KP> DEMO license file) unless otherwise specified.

So unless it was "otherwise specified", please move v3.05c OUT of the
sysops-only subs and into the "for everyone" subs.

It might be best to create an acct here called "DEMO" with a password of
"DEMO".  First time callers looking for the demo could:
1) Skip the lengthy new-user registration.
2) Access raise, validation wait period.
3) Access to subs, ratios, etc.

Instant DEMO D/L on your 1st call!!!

--1502--

D> I ran SnoopDos yesterday and it showed no problem accessing the file.
D> Could someone upload an example of a working term link text file so I can
D> check and see if I did something wrong.

Everything seems to work for me with v3.05c and:

ATDT-255-2466       14400  8  1-2   0-31  1  Future World, CNet HQ
ATDT-421-3254        2400  8  1-2   0-31  1  Fido 1:120/230
ATDT-422-3113       14400  8  1-2   0-31  1  Local Ami-Express BBS
ATDT-427-0223        2400  8  1-2   0-31  1  Fido 1:120/193
ATDT-427-6673        2400  8  1-2   0-31  1  Fido 1:120/277
ATDT-476-1719        2400  8  1-2   0-31  1  Fido 1:120/263
ATDT-478-5214       14400  8  1-2   0-31  1  Fido 1:2410/243 42000files,5lines

I have that view'able as a gfile too, if you ever need to take a look at any 1
of a long, long list of CNet config files, just dial 810-473-2020 and log-in
under the "DEMO" "DEMO" acct.  View or D/L.  Help your self.

Sure wish 100 other BBSes (including FW) had a gfile menu like that.
When someong asks to see a working sample of a config file, Ken/Jim could just
say, "look in our gfile menu for the latest one we are using here".

--1503--

TB> o  Can we PLEASE get the "C" icon turned into an AppIcon, with a definable
TB>    image/position?  This window just does not fit with the times..

As long as the current method is also allowed.

I never use WB.  I never use AppIcons.  I save the ram, and I never even load
WB.  Won't AppIcon force me to load WB?  If so, I'm against it.  Why waste
50,000 bytes?

TB> o  The license window is rather obnoxious.. it's about 4 times as wide as
TB>    it needs to be (why does it open at all?)  It also activates it's
TB>    window upon opening which is kind of annoying.

There should be a CNet rule enforced 100%...
"If you can't type anything into it, why have it open up as activated?"
It just prevents me from working in the other window that I was in.
The Amiga MultiTasks, don't pull the rug out from under me while I type in my
other window, to open an ACTIVATED window that I can't type into anyway.

I see that happen with MANY prgs.  Terminus is VERY annoying in that regard.

TB> o  Whether or not RIP gets put in any time soon or not, lets please trash
TB>    SkyPix.  I doubt it's hogging up a LOT of code, but t's still a waste.

It would depend on the code estimates.  (That only Ken can make.)

In the meantime...
>"SkyPix is costing x bytes of code."
>"Remove SkyPix if is it costing more than y bytes of code."
What would you say are a fair #s for x and y?

I have no idea on x.  But my suggestion for y is 40K.

--1504--

S> If you're NEW this is your first call, how could any msgs be NEW since
S> your last call if this is your first? -- I like the way its setup, do you
S> propose that all unread msgs would be marked as NEW to newusers and
S> bombard them with about 50,000 or more messages on their first call? :)

No need for 1 extreme (show 0 msgs) or the other (show 50,000 msgs) extreme.

CNet needs (but doesn't have) a config setting...
You set it to x days, and CNet sets a new-user's last-scan-date to "today-x".

A first-time caller would see the last x days worth of msgs and files.

A setting of "5 days" (or so) would be about right for my BBS.


Mention this proposal to Ken.  Maybe he'll add it to a future version of CNet.

--1505--
DE> MS@? Boy that's intuitive... not! I agree C-Net has features... it's the
DE> user interface (or lack thereof) that I find most objectionable.

With CNet you can change cmds into anything that you like:
Send NetMail
SN
NS
Letter
Send
Send Letter
SL
LS
Mail
Net
Netmail
NM
Fido
Fidonet
FN
Fido Send
Fidonet Send
Net Send
Send Fido
SF
FS
(You can even have *ALL* of those possibilities at once.)
Add the French, German, Italian, Spanish, words for all those cmds too.

Heck, you could produce a BBS by which darn near ANY cmd that user
types, (even if it is just REMOTELY related to "sending-netmail") will
do the correct thing.  If the user has never called a BBS in his life,
and just FALLS on the keyboard and happens to hit ANY of the above,
the correct sending-netmail cmd is executed.

Some people are just use to a limited BBS-software package.  One that
allows limited (or 0) alternative cmd choices.  I used to be also.
(It's nothing to be a shamed of.)  I had no idea that CNet had that
kind of power.

Just wondering, how many different cmd aliases does DLG support for each cmd?
(I hope I'm allowed to ask such a question.)

--1506--
RS> 17) Edit network aliases
RS> Enter the # of the item to change, or press ENTER to continue.
RS> : 17

RS> Sorry, you may not create a network alias file.
RS> Any ideas?

Type "EA1-999" and edit the "limits" for "Network aliases" for those accts.
0 allows 0.
50 allows 50.

CNet v3.05c is now a NON-beta, full release.

--1507--

On Mon 14-Feb-1994  1:27a, Dave Anderson said to George Veeder:
DA> It is FREQ'able as "CNETMANUAL" from any of the addresses listed below.

The "CNETMANUAL" magicname is VERY misleading.  "CnetIndex" would be better.

DA> All I've ever written was a "index" "text" file.  If someone wants it in
DA> Amiga guide format, i'll convert it, but a index to me seems to be
DA> hardcopied in the manual.

I vote NO for an Amiga-Guide version of the index.  Print it out and
stick in in the binder, instead.

Or create a CLI alias like:
CLI> Alias index       Search ram:Cnet3Index []

Any time you type "index macros" you see all the page #s for "macros"
instantly.  (Yes, even the ones that aren't listed under "M" which
you'd probably have trouble finding otherwise.)

--1508--

Will somebody verify this....

I set-up a sub with the "PRIVATE MSGS" flag set to "FORCED".

Users are still allowed to post private msgs (and U/Ls) address to no one.

Bug?  Or do I have another flag set wrong some place?

--1509--

To: Brad Majors
Subj: NewWHO11.lha

Any plans on doing a version of WHO that lists users that are join-
linked in from other systems?

--1510--

GS>      Your UUCP ID is different than your User Account #.  I am not sure
GS> why this makes a difference, but it does.  I have several users who have
GS> changed their UUCP IDs to something other than the default (Account #) and
GS> they have problems with many programs that look for information in their
GS> Mail directory.

Without any programmer docs, authors have had to guess at things like that.

'getuser' 39,40,41 are NOT the same things.

In Arexx #39 is the user's home directory name.

If you find a door or tool that doesn't work due to that problem,
contact the author and tell him:
1) In arexx use 39.
2) In C use "UserData->UUCP".
to obtain the user's HOME directory name.

GS> CNet will not let you change the UUCP ID back to a number.

It will if you are a SysOp are use "EA".

--1511--

DW> Depending on how long the file has been around, it is true that this date
DW> could be QUITE old. I was under the impression that CNet used the CURRENT
DW> Date and Time for the ADOPTION date.

With v3.xx the SysOp can chose:
1) Use file's date/time stamp.
2) Use the current system-clock date/time.

Either works only for "by-hand AO", NOT "amaint AO".

--1512--
DW> Main> ms david weeks@1:260/121
DW> Main> ms areafix@1:260/10

DW> The above examples work, because you use complete node address
DW> specifications following the @ symbol. I do NOT use spaces BEFORE or AFTER
DW> the @ symbol.

It *IS* OK to use a space before the "@" symbol.

DW> I've never had a problem using this method. If you do NOT
DW> specify a NAME BEFORE the @ symbol, you're going to have problems. For
DW> instance:
DW> Main> ms @1:260/111
DW> Will NOT work, and will give you an error message similar to the one you
DW> stated above.

On my system that does NOT give any error msg at all.
It prompts the user for the name (as it should).

--1513--

MM> BB> MM>  * Origin: The Daily Planet BBS [5 HS lines 2gigs- Amiga]
MM> 905-436-6509
MM> BB> MM> (1:229/436.0) (1:229/436)
MM> BB>      ^^^^^^^^^^^   ^^^^^^^^^
MM> BB>           1            2
MM> BB> CONFIG/FIDONET/ORIGIN will tack on your node # for you.

MM> Weird...Couple things. I responded to this message and then relised that I
MM> had forgot to change the Origon line before saving it. (Oh yeah...Thanks
MM> Bill, have had it this way for a couple weeks...first person to let me
MM> know it was screwy...Thanks again).

You are very welcome.  When I mention things like that I sometimes
hear responses like "why are you criticizing me" or "you aren't the
moderator here" or "I'm not an idiot".  I'm glad you saw it as simply
a friendly, helpful comment.

MM> Anyways...I deleted the message and
MM> then responded again after the change. Curious about the proceedure of
MM> killing a Fido message I took a look in the MAIL:Outbound to see how Cnet
MM> handled it. Well it didn't handle it at all! The original responce is in
MM> the Cnet.packet ready to be tossed.

As of CNet "v2.90 30-Jul-93" you can't edit (or kill) network msgs.

Once you post them (even though they haven't been sent out) you can't
change them.  (It doesn't matter if you do/don't have edit/kill
powers, or do/don't have SysOp powers.)

That's an unfortunate side-effect of the CNet tosser.

It would be great if that could be changed.
Only a couple of people (including myself) have mentioned this to Ken.
I wonder what would happen if 200+ SysOps emailed Ken and said,
"Killing and editing network msgs is EXTREMELY important to us, please
re-allow it".

--1514--

RA> running a registered Trapdoor) I am sorry but I will NOT run a shareware
RA> program that does not allow for a DECENT trial period.  30 days is not
RA> enough with ANY SOFTWARE to see if it will pass the test of time.  One
RA> should expect at least 2-3 months as a trial on a program as important as
RA> a networking front door.

With TrapDoor's constant demo requesters, it doesn't really matter.

10 days, 30 days, 6 months, or 6 years, the TD demo doesn't really
allow you to demo it fully in a real-world situation anyway.

Please keep us posted if you decide to write your own front-door.

With thousands of CNet, E!, DLG, and other BBSes needing 1, users
should have a wider selection of front-door choices.

A "reasonable price" is a must.

If you can sell even just 500 copies and $40 each, $20,000.00 is
nothing to sneeze at these days.

--1515--

BB> BBSCOMMAND "CNet:BBS TRAP NOLACE NOSCREEN PORT 1 DEPTH 2 BAUD %B LOCK %b"
                         ^^^^

On Fri 18-Feb-1994  1:40a, Dave Anderson said to Mark Bull:
DA> MB> I haven't figured out why people keep adding the word TRAP in here,
DA> it's

DA> It forces a log entry that says "front end connect" in your LC log.
DA> Dave

It does A LOT more than just write a log entry.

It tells CNet that it is being run from TrapDoor and that CNet should
shut down after every caller.  (As it should.)

"TRAP" is is VERY important keyword.  It can NOT be added or left-off
just for laughs or for "log purposes".

--1516--

BB> Type "RR" from the ROOT (*ROOT*!) directory of your msg or file subs.

FW> Hello Bill, about 'RR', i can use it when i use the run command, but no
FW> action of this command when i launch it in a base. I type 'RR' and the
FW> system does not run or seems to run anything. Is it something to do to
FW> allow the use of 'RR'

You are running CNet v3.04 (or v3.05c) aren't you?

"RR" was added into BBSmenu by Ken himself, so it should be available to you.

You are logged in under a SysOp-acct?

You do have a "pfiles:Maintenance/repair_sub" file?

What does SnoopDos (or DosTrace) report when you type "RR"?

--1517--


On Sat 19-Feb-1994 10:51p, Daniel Crispin said to Bill Allen:
DC>  > You can currently use any old release of CNet to send RIP codes.
DC>  > (You just can't view them on Cnet's local screens, nor use
DC>  > interactive-RIP codes.)

DC> Well, that of no use.  I want an interactive RIP board.

What is your definition of "interactive RIP"?

Perhaps I should clarify my statement.

As of CNet v1.0 (and every release afterwards) you can NOT:
1) View RIP codes in the local screens.
2) Use RIP-codes that ask the caller a question and expect an answer.

You *CAN*:
3) Send RIP-codes and have your callers view them.
4) Have full graphics, icons, 3D-gadgets that users can point and click on.

Just set-up a gadget marked "[FILE AREA]" and instruct it to send the "UDBASE"
string when the user clicks on it.  (RIP handles all that, regardless of
whether or not CNet does.)

Set-up as many point&click gadgets as you like.
Just make sure *THEY* return the correct strings when the caller clicks on
them.  It actually has very little to do with CNet.  So I can't imagine why
Ken doesn't and a "RIP" choice to "ET;2".  That 1 simple text change is all
that would be needed to allowed massive RIP powers.

--1518--


I'm not sure who "anonymous" is, but I'll throw in my 2 cents.

I call 100s of BBSes.

DC> 1) You call 26 BBSs at all (10 before, this one, 15 after) (that's a lot
DC> man!)
DC>    and you want to be able to select ANSI ON or OFF for anyone of those
DC> right?

DC>         - Why not turn ANSI OFF on the BBS you don't want to see ANSI on?

On my first call, how am I suppose to know BEFORE I CALL whether the next BBS
is or isn't going to force ANSI characters down my throat?  Psychic?

DC>         - Why not use a Term program that allows you to select your
DC> graphic
DC>           display for each BBS in your phonebook?  I mean, most of them
DC>           have that option (NComm 2.0/3.0, Terminus, Term, etc).

Why make me change to a term prg that I don't want to run?
Why make me config 100s of settings?

CNet covers it fine.  If I want ANSI, I select it ON in my acct.  If I don't
want ANSI, I select it OFF.  Why ignore *MY* choice and force it on my
anyway???  Why not force tons of RIP codes down all your caller's throats
also?  Regardless of whether they want them or not.

DC> 2) If you are saying that for Ken to improve the Term program of the BBS,
DC>    on that I would approve.  I understand that it cannot compete with the
DC>    big leagues term programs but this little term is too bare to use.
DC>    I mean... there is not even a PhoneBook in it!  Anyways, probably in
DC>    Version 3.0 (Hope so).

CNet is a BBS, not a term.  I think NOTHING should be added to the term which
would make CNet (the BBS) code swell.

If you want to dial-out, you can set-up a CLI DOS-script called "CALL".  That
*1* cmd will close a CNet port, and run your term, after you are done, close
your term, and re-run you port.

Is typing "CALL" too much extra work?  You can have dialers, and colors, and
protocols, and features by the 1000s.  And all of it will increase CNet's
size by *0 BYTES*.

--1519--

PB> replaced by a completely new Network server that will allow you full
PB> access (limited by sysop) to another system.  not just the conferences,
PB> but also their udbases, message bases, e-mail, etc.

Pete, that's great news.  That's exactly what I want.

Every time I hear "new Network server" I keep thinking Ken is going to do
something that is going to require a Ethernet hook-up.  (Which won't do 95% of
the sysops a bit of good.)  I'm glad to hear otherwise.

My other BIG regret is that 40 beta-testers are NOT going to be allowed to
kick around ideas BEFORE HAND.  It'll be yet another case of:
1) Ken adds/removes/writes the code.
2) *THEN* we tell him what we wanted.

What a big waste of time and effort for Ken and everyone.

40 heads are better than 1.

--1520--

MM> Well, I allready knew about this, but I guess you didn't catch the part in
MM> the post that said I would like to completely DOWN the port when it's not
MM> in use.  That's easy to do in itself (Closeport event, simple) but it's
MM> bringing it back ONLINE (As in reloading the port) that has me stumped.
MM> Somebody out there must know how..

Re-load it the same way you loaded that port originally.

Have CNet run a DOS-CMD event like "Run CNet:bbs >nil: <nil: 2".
(Or whatever you use.)

DOS-CMD events will run even if you don't specify a config/event port #.

(You, of course, DO need to tell CNet:bbs which port to load.)

--1521--

On Tue 15-Feb-1994  7:58a, Flash wrote:
F> What's the best Spell checker for the Amiga and hwere can I get
F> it?  I need one something terrible.

On Sat 19-Feb-1994  1:36p, The Wizard said to Flash:
TW> Bill allen had a larger Spell Checker available on CNet Future World, but
TW> I do not know if it is still there

It is also file-requ'able as "CNetDict" from 1:2410/207.
(120K at 14400bps)

It replaces CNet's 37,000 word dictionary with a 59,000 word one.
(The extra *22,000* words just might contain the one you are looking to spell.)

--1522--

Hmmmm.   I wish I could track this one down more.

On three separate occasions, the full-screen editor started acting
flaking during heavy editing near the bottom of the screen.

1 or 2 lines started to appear twice or disappear.

(The 3 occurances were days (and reboots) apart.)

Anyone else?

--1523--

PB> 1>  make it possible to UM a specific account (even if they are not
PB> online!)

I mentioned adding this feature back in Jan 1993.  No comment from Ken.
(I'm NOT saying it shouldn't be mentioned again.)

PB> Main> UM 81
PB> That user is not currently online. Monitor anyway? [N,y]

That wouldn't work.  CNet would need a way to distinguish between PORT #81 and
ID #81.

Maybe "UM x" means PORT x.
and "UM #x" means ID #x.

Actually, the term "USER" monitor isn't even correct at all.
Currently, CNet can only monitor ports, not users at all.

Maybe "PM" can mean port-monitor.
and "UM" can be a true, (new) user-monitor.

(Then no port# or id# conflict would ever occur.)

Maybe a new "EP" "User Watch" setting could be added also.
You could store "1,3,6,84,145,234,333,487" id#s and they would automatically
be watched for as soon as you logged in.
(I don't want to have to remember all those ID#s on 20 different BBSes, or
have to key them all in by hand at the start of every 1 of my calls.)

--1524--
FW> Hello Bill, about 'RR', i can use it when i use the run command, but no
FW> action of this command when i launch it in a base. I type 'RR' and the
FW> system does not run or seems to run anything. Is it something to do to
FW> allow the use of 'RR'

DW> I was having this exact same problem for MONTHS, until I overread
DW> (overheard) a comment by Ken himself. He said the "Repair_Sub" file had to
DW> be in the ROOT "pfiles:maintenance/" directory in order for it to work
DW> from INSIDE of CNet.

I bet that's exactly what's happening to "DW".

Wouldn't it be great if CNet displayed:
> Can't find pfiles:maintenance/Repair_Sub
instead of
> [display nothing at all]

This whole week-long question & answer thread would never even need occur.

CNet itself would instantly tell you the problem.

--1525--

FW> Hello Bill, about 'RR', i can use it when i use the run command, but no
FW> action of this command when i launch it in a base. I type 'RR' and the
FW> system does not run or seems to run anything. Is it something to do to
FW> allow the use of 'RR'

DW> I was having this exact same problem for MONTHS, until I overread
DW> (overheard) a comment by Ken himself. He said the "Repair_Sub" file had to
DW> be in the ROOT "pfiles:maintenance/" directory in order for it to work
DW> from INSIDE of CNet.

I bet that's exactly what's happening to "FW".

Wouldn't it be great if CNet displayed:
> Can't find pfiles:maintenance/Repair_Sub
instead of
> [display nothing at all]

This whole week-long question & answer thread would never even need occur.

CNet itself would instantly tell you the problem.

--1526--

Ken, there's some discussion going on in the CNet Echo regarding
"MS name@x:y/z" use.  Confusion about whether or not a space is
permitted, mandatory, or optional before or after the "@".

You can help eliminate it all by allowing all 4 to work:
1) MS name@x:y/z
2) MS name @ x:y/z
3) MS name @x:y/z
4) MS name@ x:y/z

(Even I can't always remember which of those currently work or don't
work.)

Thanks for listening.

--1527--

KA>    I just protected my BBS.License by taking the D (Delete) flag off.
KA> This will keep it from being written over.

What about the WRITE flag?

> Protect CNet:BBSlicense R
That'll turn off writing, executing, deleting problems.

(Note: It's "BBSlicense", not "BBS.License")
                                  ^

--1528--

DW> RESIDENT PURE CNET:BBSWAKE ADD
DW> Any ideas on this?

How do you know that BBSwake is pure?
Many executables are NOT.

1) I can't find any mention in Ken's ReadMe of it being so.
2) I can't find any occurance of it where Ken as set the "P" pure flag.

It can be dangerous to use the forced-pure option for the resident cmd.
(Here, or on ANY executable that doesn't have its "P" flag set.  That's why
CBM invented that flag.  Use it, don't just ignore it, and override it.)

Ken, please do #1 and/or #2.  (#2 is preferred.)

Both LHA and DMS can preserve a file's flag settings.

Thanks

--1529--

We would have to be careful.  Once dropped (or default-dropped), all those
subs would not appear in the list, users might not even know they were there,
and might have difficulty JOINing them.

I'd be in favor of new, ADDITIONAL list-joined and list-dropped cmds, but I
think that basic, LIST cmd should remain as-is.  (List them all.)

As for making it sysop-config'able, I wouldn't want to call 50 different CNets
and have to wonder if "list" means list-all or list-joined on each of them.

It is also getting to a point where we will need:
> List 'xyz'
OR
> List xyz*
searching.  (It would only list sub-names containing that string.)
(Nested searches and non-nested.)

You might have 5000+ subs just in usenet alone.
(I can't even imagine Fidonet, CLINK, AmigaNet, and all the other networks
too.)

The day of the 10000-20000 sub BBS is coming.  Better be ready for it.

--1530--

Is anyone going to write a "RexxCNet.library" arexx support library?
What functions would you like it to have?

--1531--

Thursday 24-Feb-94 22:56:27, FW was experience memory problems.

4 users were online, (maybe more "hidding.)

When attempting a reply, I got:
> Not enough memory to enter the editor.

When attemping to enter a sub, I got:
> That subboard is temporarily locked.  Try again later.

I hung-up and called back in 15mins.  1/2 the lines were ringing but
not answering.  I got through at got "Timeout error loading external
program." at log-in.

At least we know the low-memory-warnings are working.

I hope that helps figure out what was happening.

--1532--
Here's an odd one that I haven't seen before...

My acct #s 1-182 can log-in using their real-name, handle, or acct #s.
Acct #s 183->up can only log-in using their handle, or acct #s.
(If they try and log-in with their real-name the system can't find it.)

Something's wacky with acct #s 182-183.

#182 is a caller from Spain with their "odd" very long or very short
addresses/city/state/zip/phone #s.

#183 is a doesn't seem to have anything out of the ordinary going on with
his acct.

I ran 'pointers' several times.
I ran 'amaint'.
The problem continues.

I guess I could kill those 1-2 accts, but I'd like to track this down
before I do.

Ken, do you need any more info?

--1533--

I'm finding the CNet v3.0 manual to be very accurate and thorough.
(But there are a few minor things.)

If you find any additions, typos, missing examples, errors, or things
that need better explaining, please post them here.  (Give the page
numbers, too.)

Maybe Ken/Jim (or someone) will toss together some "errata-pages" that
we can put into the manual binder.

Pages 273-274 are missing from my copy.

I couldn't find mention of the options that CNet:BBS uses:
Port/trap/depth/baud/lock/screen/noscreen/nolace/lace/halflace/etc.
That must be in there some place.  No?  I can't find it.

Page 262 states that AMAINT repacks subboard data files for killed items.
I thought that was done only by RR.

Page 211 states that new newsfiles are automatically displayed at log-on.  I
believe that is it only *ROOT DIR* new newsfiles.  (As it should be.)

Page 71, the joinlink example "ATDT#pass" needs a space in it.
Most likely the fault of the proportional typeset used in the manual.
Maybe printing "ATDT#   pass" would make it appear clearer.

Page 99, FINGER is not listed as a global-cmd.

Page 171, an actual example date would be great for the SINCE/UNTIL options.
"Use DATE-MONTH-YEAR as 31-12-94..."

Page 227, Getuser 39 should be mentioned as the physical HOME directory for a
user's acct.  (I see arexx scripts incorrectly trying to use 40 or 41
instead.)

A few more minor things....

p.16 Two occurances of "0-23" should read "0-31".

p.248, 5th paragraph.  The word "once" at the start of a sentence
needs to start with a capital letter.

p.227, GetUser #57 really displays date AND time, not just time.

p.248, bottom of page.  "Mail:Toss.log" should read "SysData:log/Toss.log".

p.226, GetUser #18.  The word "onlie" should read "online".

p.253, 3rd paragraph.  "2100" should be at least "5200".

p.71, 5th paragraph.  "Immediate--system idle or not" should be in
bold-type like its counterparts.

p.100-101.  "NF" and "NM".  Two occurances of "since your last call" should
read "since the last time NF or NM was executed".

p.119-120.  Two occurances of "(yes, no, sub)" should read
"(yes, no, sub, force)".

p.3 "Baud Rate" and "BPS" are NOT the same things.

p.226, GetUser #11.  The word "amd" should read "and".

A handful more...

p.118, 5th paragraph. "Join and OLM" should read "CC, Join, and OLM".

p.275, last paragraph.  "...only of they have..." should read
"...only if they have...".       ^^
         ^^

p.119, 6th paragraph.  For "Kill/edit own files", there is also a "SUB"
option that isn't mentioned at all.

p.44, 4th paragraph.  The line "The bottom line of the control panel..."
should read "The bottom line of the status window..."
                                    ^^^^^^^^^^^^^

p.112, 2nd paragraph.  The line "...using the "mail ken" command..."
should read "...using the "mail ken@" command...".
                                   ^

p.146, 2nd paragraph.  The cmd "ME!" needs to be mentioned or no members-list
can ever be created at all.       ^

p.182, 2nd paragraph.  The word "forgotton" should read "forgotten".
                                        ^                       ^

Hmmmmm, maybe there are more of these than I first thought...

p.181, 4th paragraph.  "...with a asterisk..." should
read "...with an asterisk..."   ^
               ^

p.259, 3rd paragraph.  The word "interpretted" should be "interpreted"
instead.                                 ^^                       ^

p.181, 5th paragraph.  "By default, this line contains the cmd "NS"..."
should read "NSAL" instead of "NS".

p.261, 3rd paragraph.  The sentence "Users may post, response, leave
mail..."  should read "respond" instead of "response".

p94.  Four references to "SysText:avalid" should read "SysText:sys.avalid".

Bottom of p.242 and top of p.243.  Two occurances (in charts) where
"Itr" and "Int" appear in an order reverse of the actual config/event
screen.  (Also, "Itr" and "Int" are very poor abbreviations for 2
different words that BOTH contain the letters I-T-R and I-N-T.)

p.203, 3rd paragraph from the bottom.  CNet is spelled "CNet" in 100s
of places in the manual, except here it is spelled "C [dash] Net".

(Jot all those down in your manuals.  Anybody have any others?)

--1534--

GS> While on the subject of Kill/Edit, I would love to see CNet have
GS> seperate access settings.  I like to give my users the ability to edit
GS> their posts/replies after it has been saved, but don't want them killing
GS> them.

There needs to be 3 separate settings.
(Not just 2.  And certainly not its current "lumped into 1" method.)

1) Kill your items (and all attached responses by other people)
2) Kill your responses
3) Edit your items and responses.

And everything edited should be marked in the header:
#13/13 From: Bill Beogelein  (SysOp)
       Orgz: CNet-BBS V3.05c Beta-Tester
       To  : Geoffrey Setser
       Date: Fri 25-Feb-1994  4:03a (Edited Sat 26-Feb-1994  2:11a)
                                     ^^^^^^

Or at least just the word "(Edited)".

--1535--

BC> I would like to see ANSI/MCI stripped automatically from NETMAIL or
BC> have an option to have it stripped.  That way, people can have ANSI/MCI in

What do you think of the idea of allowing netmail to go into a sub
called NETMAIL or MATRIX?  (We currently can't.)  Then you can set
that sub to no-MCI and 50 other sub config variables, too.  For
sorting, record-keeping, auto-purging, searching, signatures, carbon-
copies, threading purposes, the works.

Of course, sysops wouldn't HAVE TO create that NETMAIL sub if they
didn't want to.  (Netmail would then just behave like it does now.)

--1536--

When I type "SCAN" in a msg sub, I'd like to see:

>  # Posted Rsp          Subject              Author
> == ====== === ============================= ======
>  1 23-Feb   0 Control.dat files             John Doe
>  2 23-Feb   0 'C' Programming               Jim Loccer
>  3 21-Feb   0 Trapdoor Alternatives?        Bob White
>  5 21-Feb*  1 Cross-Posting /w Cnet Toss    Jack Doe
>  6 21-Feb*  2 Street Surgeons!              John Smyth
> 10 20-Feb*  3 Rylween...Cnet game?          Phil McCaverty
> 12 19-Feb*  2 Invite/Unvite                 Mike Hunt
> 13 19-Feb*  2 C-Net v3.05c : TERMLINK       Pat E. Cake

Line #423 of BBStext controls the scan displays.
How do I make it also display the author's name?

--1537--

M> problem?  I put the file in the sysdata directory, as the docs explained,
M> and made sure the filename was "TermLink".  The file is below:
M> ATB1DT6867495  19200  8  1-2  23-31  0  Arkham Asylum

HH> should be         192   instead of 19200

The manual states "19200" not "192".
The example in the manual shows "19200" not "192".
I've always used "19200", not "192" and it worked fine.
Ken's readme shows "2400", not "24".

Mug (or anyone), which 1 is working for you?  Both?  Neither?

--1538--
RJ> I want it to run once every 5 minutes on all ports
RJ> I have set it up in events as an Arexx pfile time = 0
RJ>                                             valid = 2400
RJ>                                          Interval = 5
RJ>                                          Interate = 144

AD> Change the valid value to 1, and it should work just fine.

That'll only make it run every 5 mins from midnight until noon.
(Every 5 mins x 144 times = 12 hours, not 24.)

If you want it to run every 5 mins 'round the clock, you need:
0
1
5
288

Event times can be very confusing things.  It still confuses me and
I've set-up and removed 100s of events over the last 9 months of beta-
testing.  Print this out and stick it into your manual near page 72...

Run once every  5 mins:  0 1    5 288
Run once every 30 mins:  0 1   30  48
Run once every 60 mins:  0 1  100  24  (Note: that's "100" not "60")
Run once every  4 hrs :  0 1  400   6
Run once every  6 hrs :  0 1  600   4
Run once every 12 hrs :  0 1 1200   2
Run once every 24 hrs :  0 1    0   1

(I hope I got all those correct.)

The manual needs more EXAMPLES EXAMPLES EXAMPLES!!!

MS> God, that's weird. Why does an hour flip to 100 instead of 60?

They are all really in "HR:MN" format.  1 hour, 00 minutes.

I tried to get Ken it add a "HR:MN" string right into the event window
display, as a reminder.  I don't know if he didn't think it was
important, or just couldn't squeeze it in.  I need all the reminders I
can get.  And from the look of all the questions on this subject, it
looks like it would have been handy.

--1539--

Manual> CNet will always send netmail in "reply" to AreaFix messages,
Manual> giving a list of which areas are accessible...

How do I get a copy of that?

FW feeds me a few echos.  I tried netmailing its areafix requesting
additional non-existing echos be added to my list.  I tried requesting
an echo that I'm already receiving.  I tried a subject line of
"PASSWORD -L".

FW sends no "reply" or "report" of any kind.

--1540--

With v3.xx the SysOp can chose:
1) Use file's date/time stamp.
2) Use the current system-clock date/time.
That works only for "by-hand AO", NOT "amaint AO".

Edit CNet:BBStext, change line #1 into line #2:
1> Adopt file-dates from DOS [Yes]? \?1
2> Adopt file-dates from DOS [No]? \?0

(Or however that line reads in the origin, unmodified release.)

"Amaint AO" *ALWAYS* uses the date-stamp of the file.

I guess you could set-up an event to run "c:SetDate FileName" to set
the file's datestamp to today (or whatever).  (That would have to be
done BEFORE amaint does its AO.)

--1541--

S> does anyone have (or is there even) a version of hslink for the amiga that
S> can be installed in cnet?

I have NOT seen one.

Type "FIND HSLINK" for more info about the IBM release.

CNet could really use a 2-way protocol of some sort.

U/L 500K while simultaneously D/Ling 500K, instead of doing 1, waiting until
it is done, and then doing the other.

It would put an instant end to folks that claim "it costs too much in phone
calls to U/L".  They could U/L w-h-i-l-e they are D/Ling.

--1542--

Do I start the printer-capture before, or during, the "E"?
Do I end the printer-capture during, or after the "E"?
Is it on a certain file compression type only?
Does "E" work 100% on that file as long as you don't use the printer-menu?

I tried a bunch of different combos, but they all worked 100% for me.

Please give me the exact order, and exact cmds, to produce a GURU.

--1543--

> Dial 1-800-xxx-xxxx for a toll-free BBS with encyclopedias, files, messages
> conferences, everything...

You should have mentioned that this "toll-free BBS" is just the GEnie
registration line.  You can NOT access encyclopedias, files, messages
conferences, etc, until AFTER you give your VISA credit-card number
and sign-up for the hourly fees.

I'm sure this post is wasting a lot of people's time and effort just
"to check".

(As well as wasting GEnie's money.  They have to pay for every 1-800
call they get.)

--1544--

T> does anybody Remember one of the first AmigA term programs call'd Diga??
T> it had a protocol called "DoubleTalk" I used to transfer files with
T> friends

ParaBIT (Amiga)
DoubleTalk (Amiga)
Proteus (Amiga)
Hydra (IBM)
Sadie (Amiga, $1 overall license-fee)
HS-Link (IBM)
Bi-Modem (IBM)
Chat&D/L by J.Robinson (Amiga)
VBBS (Amiga)
Dmodem (Amiga) (See Dream-Term in xprdmodem.library by Pasi Ristioja
        Fido-2:229/888 Usenet-pasi.ristioja@mpoli.fi)

The problem isn't FINDING a 2-way protocol.  There are 10-15 of those.
The problem is getting an Amiga BBS author (and an Amiga term author)
to USE ONE OF THEM.

I would vote for the protocol with the most features, newest update, fastest
transfers, and freely usable code.  I believe that is HS-Link or Hydra, used
by millions of IBMers around the world.

NOT something from the 1980's, long since forgotten, and used by <1% of
the Amiga users.

Whatever term you are running right now, hit the "ABOUT" menu, and jot
the author's name down on the front of a postcard.  On the back write:

                  >>> WE WANT A 2-WAY PROTOCOL!!!! <<<

Maybe 10,000 postcards might make a term author take note.

It'll be the best 15 cents you've ever spent.

D> I recall seeing Bi-Modem somewhere...it was porported to be a 2-way
D> protocal....when I used a hex editor to examine it, the "bi" part turned
D> out to stand for "Binary"..unless there's another program called
D> "Bi-modem".

It was my understanding that there was both.  (I've used neither.)

15-Apr-93 xprbi101.LHA  58K XPR Bi-modem library on BIX and Fred Fish
                            Disk
01-May-92 BiModem.LHA   20K Bi-modem protocol by David Betz, BYTE
                            Magazine (IBM)
01-Dec-89 QBIM300.LZH   17K Add Bi-Modem 2way transfers to IBM BBS
                            18Nov89

A phony bi-modem for Amiga users that was NOT 2-way even though some folks
called it such.

A true 2-way bi-modem protocol for IBM and other non-Amiga machines.
Bimodem Pro v3.1 for the IBM is available for File-Request at 1:377/49.
The file name is "BIMPRO31.ZIP".

And a new comer...
dterm13.lha               197413 ----rwed 07-Mar-94 01:16:23
: DreamTerm v1.3 by P.Ristioja includes an external xprdmoem.lib
: 2-way protocol

It *IS* a true 2-way protocol.  It *IS* for the Amiga.  It *IS* in external
xpr format.  Now, if I can just get it working with my favorite term and
favorite BBS.  File-requ "Dterm" from 1:2410/207 @ 14.4k, if you need it.
Let me know which other terms and BBSes it can be used under.

--1545--

RB> Also, in the same area, when CNET informs a users that someone tried to
RB> log-on to there account, I think CNET should PULL the attempted password
RB> from the log and include that in the mail to show the user what
RB> password(s) were attempted so he know if it is a password from another
RB> bbs, or just crap that someone typed.  I think this would be helpful to
RB> all parties (Sysops & Users).

That sounds like a great idea at first, but it isn't.

What if "Bill A Len" got mail that said:

> "Bill Allen" tried to log-in with the
> password of ELEPANT, ELEPHA{T, ELEPH.ANT?

It would be pretty obvious what Bill Allen's password is.
He was just getting line noise and had a name similar to yours.
Or maybe he tried to log-in with an acct number like 893 instead of
his 839 acct.

One user now knows the other user's password.

BB> That sounds like a great idea at first, but it isn't.
BB> What if "Bill A Len" got mail that said:
BB> > "Bill Allen" tried to log-in with the
BB> > password of ELEPANT, ELEPHA{T, ELEPH.ANT?

RB> That is a GOOD point, but CNET wouldn't have to give so much info.  It
RB> could just say...

RB> At 6:04pm on 3/5/94 someone tried to access your account with the password

I guess it could leave off the user's name, but I thought the whole
point was to find out WHO was doing this guessing.  No?

Even if you didn't know the name, you now know the other user's
password.  Just try and bunch of accts.  You'll hit it right one.
(It'll only take, at most, 1 guess per acct.)

RB> Besides, in your example above ^^^  The system would know WHO was trying
RB> the password yet because the weren't logged on yet.

The system could just assume the NAME and PASSWORD that the user entered.
(Regardless of whether he was logged-in or not.)

Even if I saw this, I would HIGHLY suggestion you change your password
i-m-m-e-d-i-a-t-e-l-y...

> At an unknown time, on an unknown date, an unknown user tried to
> access your acct with an unknown password 23 times.

Of course the SysOp could see:
> 15-Mar-94 03:34 John Doe failed password of ELEPHNT caller-ID 810-555-1212

Now *THAT* would be handy.  Now if we could just get Ken to do it.

--1546--

CR> I tried adopting my CD-ROM files during AMAINT and it didn't adopt the
CR> descriptions in each CD-ROM directory's FILES.BBS  at all, so I had to go
CR> back and AO! by hand.

On all of your CDs, they do call the file "FILES.BBS"?
And your CNet:BBSTEXT line is instructed to use the "FILES.BBS" name?

That's about the only conflict I can think of, at the moment.

Does SnoopDOS show a "FILES.BBS" trying/failing to be found (or opened) successfully?

--1547--

S> I can't get party-mail to work...

BA> You do have a route-file set-up, don't you?
BA> You won't get party-mail to work without one.

S> I don't remember this being required before... but it did turn
S> out to be the problem.  :|

"Not required" in which version?  I don't know how CNet would know where to
send all the party-mail replies, if it didn't have a list of the users.
No matter.  Glad you got it working.

(I wish Ken would have called it a "party mailing-list" (or something) instead
of a "route-file", just to keep it separate from the Fidonet routing stuff.
They are NOT related.)

--1548--

D> r mess since 5-Mar-1994
D> r mess before 1-Mar-1994

D> These were tested within this base:
D> r mess since 1-Mar
D> r mess before 5-Mar

Did all those work???

I've NEVER seen 1-Mar or 5-Mar-1994 as valid dates for SINCE or BEFORE.
Only 31-12-93 or 31-12.  (I hate that style.)

And I've NEVER seen a "BEFORE" option at all.  (It's "UNTIL".)

Since we can't add additional option aliases, it would be great if CNet
supporting things like:
SINCE AFTER UNTIL BEFORE PAST TILL BEYOND and any other synonyms we can think
of.

Also, it would be VERY easy for CNet to recognize more than *1* date format.
31-12-93
Dec. 31, 93
31-12-1993
December 31, '93
31-Dec-93
31Dec93
31-Dec
31.12.93

Just by using some pseudo artificial-intelligence rules:
1) Any letters (found anywhere) must mean the user is saying "MONTH".
   (You would only need to look at the 1st 1-3 chars.)
2) Any numbers 1-31 (found anywhere) are assumed to mean "DAY".
3) Any numbers 32-2100 (found anywhere) are assumed to mean "YEAR".
4) Ignore all punctuation.

Heck, even stuff like this would be interpreted correctly by CNet...
12-31-93          (You are calling from Europe.)
1993 20 Jan       (You are calling from another planet.)
Januarry 20 1993  (Even if you can't spell.)
Janu{.,y 20 1993  (Even through line-noise.)
Jan 20th 1993     (Xst Xnd Xrd etc.)
Dec31 93          (Decemeber is the only month starting with "DEC")
Ap31 93           (April is the only month starting with "AP")
S30 93            (September is the only month starting with "S")

It wouldn't catch EVERYTHING correctly, but it would sure be a lot more than
*1* forced date format.

--1549--

D> Sho nuff Was the problem.   But...you'd think that if DATE was in RAM:,
D> that would make it faster loading/executing instead of not being able to
D> run.

Was the "ram:Date" file a real copy of "c:Date"?
Or some other data-file just called "ram:DATE"?

It is extremely poor programming to write a pfile that creates files with
names EXACTLY like those of common DOS cmds.

If your pfile is called "FOO", make data files called FOO_DATE FOO_NAME
FOO_WHATEVER.  0 conflicts.

--EOF--

Monday 07-Mar-94 01:27:27

-Bill "Mr. BBS" Beogelein, 810-473-2020, 2-line HST 14.4k USR-DS, 1:2410/207

