
Scanning Beta (6) Conference 

Date: 05-04-93 (14:18)              Number: 61977 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: v15.0 Wide Area Beta     
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

                              
                                       
                          
                                     
                                 
                                  
                 

                                           
                                 
                          
                                    
                                   
                                       
(47 min left), (H)elp, More? NS                       
                                             


ANNOUNCING THE START OF THE PCBOARD V15.0 WIDE AREA BETA CYCLE
==============================================================

Some very short rules to get us started here:

1) All BETA reports must include the DATE and TIME of the software being
   tested.  Please do NOT say "I have the latest" as this is often wrong and,
   at least, generally does not agree with our own internal testing release.
   So please take the time to look at the date on the .EXE file and include
   that information in your report.

2) All BETA reports must be submitted directly on Salt Air in *this*
   conference.  Sometimes we will ask you to call us in order to work with you
   on duplicating a BETA report.  However, we ask that you first submit the
   report here so that all reports will have a written 'trail' to follow so
   that we can track the progress of the testing.

3) A picture truly IS worth a thousand words.  If you can provide a screen
   capture, a callers log entry, etc, this will often save a lot of messaging
   back and forth that might otherwise be necessary to clarify your report.

   Help us out by telling us the SYMPTOMS of the problem, let us diagnose it.
   That is, instead of saying "it locked up" (which is your diagnosis), tell
   us what you did and what you saw (on the screen, on the modem, etc) and
   let us diagnose the symptoms.

4) We ask that you read the HISTORY file to keep yourself up to date with the
   changes being made to PCBoard.  Sometimes the information in the HISTORY
   file is critically important to keeping your system up and running.  Other
   times it's merely good-to-know information.  Please keep abreast of the
   changes being made.  The BETA door will give you a cut-down version of the
   HISTORY showing you only what is NEW SINCE your last download.  Or, you
   can type HISTORY at the command prompt to view the latest history
   information.

The above rules can be re-displayed by typing RULES at the command prompt.

So let's begin!  You'll find the next message, following this one, will give
you details on what you need to do to start out.

Thanks for your support!

Date: 05-04-93 (14:00)              Number: 61978 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: Getting Started          
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

1) If you missed the rules for beta testing, please type RULES to read them.

2) Use the BETA door to download all new executables.  Once you have downloaded
   the complete set, you can get updates from then on by typing "BETA NEW" and
   the BETA door will package up for you only those files that have changed.

3) READ CAREFULLY:  The README.1ST and the WHATSNEW files that come in your
   beta.zip download.  These will help you get up and running right away.

4) Most importantly:  Have fun!  We think you'll enjoy the new software.  At
   least, we certainly have!

Gentleman, start your engines...

Date: 05-04-93 (14:00)              Number: 61979 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: Wide Area Beta Schedule  
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

The plan here is for a very quick Wide Area Beta cycle.  Our goal is to have
PCBoard v15.0 ready for release in approximately 6 weeks.

An important item to note is that the Wide Area Beta code has a 30-day period
in which it operates normally.  After 30 days it will begin warning you that
you are running OLD CODE and that you need to upgrade.  This is NOT an
'expiration date'.  Your software will STILL operate.  The warning is meant to
be annoying.  It should be obvious that running beta code for 30 days is not
really 'testing' the beta code.

Anyone who has participated in our beta cycles before will probably already be
aware of this, but we generally have a fairly fast paced beta cycle.  We tend
to post updates on a DAILY basis in order to get the fastest possible turn
around on bug fixes and re-tests.

To aid in the quick turn arounds, please post your beta reports as quickly as
possible.  More importantly, please RESEARCH your beta report before you submit
it to us.

The best beta reports often include:

    - Date/Time of the code being tested
    - Screen captures, caller log snippets, etc
    - Step by step instructions on what to do to duplicate the problem
    - Configuration information

By including the above information right in your very first report of the
problem you can avoid the turn-around delays that would occur when we have to
ask you for the additional information.

All in all, this should be a fun beta cycle for all those involved.  And we
want to thank you, in advance, for your participation.

Date: 05-04-93 (14:01)              Number: 61980 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: Announcing the PCBoard Programming Language (PPL)
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

PCBoard v15.0 offers a new capability that will allow sysops to customize
their systems in ways never before possible.  This is done using the new
PCBoard Programming Language (or PPL).

The PCBoard Programming Language is quite similar to BASIC making it much
easier to implement new features on a system than would the alternative of
writing DOOR applications using C, PASCAL or even BASIC.

The PCBoard Programming Language gives you direct access to the user.  To the
user's record, to the displays that the user sees, to the inputs that the
user must answer.

The PCBoard Programming Language can be used to create intelligent Script
Questionnaires; providing logic and formatting control and creating many new
possibilities for script processing.

The PCBoard Programming Language can also be used to create NEW commands,
similar to the way DOOR 'names' can be used as commands.  It can also be used
to enhance existing commands or even replace them!

The PCBoard Programming Language is implemented directly in PCBoard.  This
means that ALL v15.0 customers can make use of the features it offers.

However, the PPL Compiler and Documentation will be sold as a separate item.
This is being done to keep the price of PCBoard down while recovering the
software, documentation and support expenses that are and will be associated
with the compiler.

The RETAIL PRICE of the PPL Compiler and Documentation will be $80 + S&H.

To encourage you, our BETA testers, to work with the compiler, we are offering
it to you for a pre-release price of $50 + S&H.

The printed documentation will not be immediately available, but as soon as it
is we will ship it to you with your pre-paid purchase of the compiler.

This $50 price will remain in effect until the end of the Wide Area Beta cycle.
After that point in time the price will be increased.

Product Support for the PCBoard Programming Language and Compiler will be
handled in conference #39 on this system.  Help in running PPL programs,
however, will be available in this conference (#6) during the beta cycle.

Both source and compiled PPL files are welcomed to be uploaded to this system.
Everyone can use the compiled PPL files.  However, only those who have
purchased the PPL Compiler and Documentation will be able to write and compile
their own source PPL source code.

The new PCBoard Programming Language, combined with the menus, commands and the
many other new features that PCBoard v15.0 has to offer, as well as our time
honored tradition of compatibility with prior releases of PCBoard and third
party offerings, makes this release of PCBoard by far the most flexible package
available today.  One might easily conclude:

If you can't do it with PCBoard v15.0, it probably can't be done.

Date: 05-04-93 (14:02)              Number: 61981 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: Where to find v15.0 files
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

PCBoard v15.0 and related files can be found the following locations:

1) The BETA files can be obtained by using the BETA door.

2) Any other utilities we may provide will be found in directory #2 of this
   conference.

3) Any third party files, that are specific to v15.0, such as PPL files, will
   be posted in the brand new Upload Directory in this conference.

If you want to automate the procedure for obtaining new v15.0 files you could
put the following in your scripts:

    BETA NEW        <-- grab the latest beta code (flag BETA.ZIP)
    N 2 S D NS      <-- view directory #2 for new files, flag for download
    N U S D NS      <-- view upload directory for new files, flag for download
    D Z BYE         <-- download command, using Zmodem, auto goodbye
    Y               <-- answer Y to 'download flagged files'

Date: 05-04-93 (16:35)              Number: 61986 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: FIXTEXT.ZIP              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Many people are missing the FIXTEXT.ZIP file when downloading the v15.0 files.

Due to the difficulty in calling back to pick up the files you need, and the
importance of this file, I have modified the BETA door so that (for now at
least) it is forcing EVERYONE to download that file.

My apologies to those that don't need it.

You're welcome to those that do.
                                         David W. Terry 

Date: 05-04-93 (16:35)              Number: 61987 of 63094 (Refer# NONE)
  To: THOMAS PAINE
From: DAVID TERRY
Subj: ordering the PPL compiler
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

For those interested in ordering the PPL Compiler, call 800-356-1686 (voice).

                                         David W. Terry 

Date: 05-04-93 (21:18)              Number: 61997 of 63094 (Refer# 61994)
  To: JOHN KERR
From: DAVID TERRY
Subj: OTHER:  COMMDRV 05-04-93 
Read: 05-05-93 (15:45)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Is there any new "mods", or enhancements in COMM-DRV that we should capture
-> as well for BETA testing??

Nope.  The originals work fine with v15.0.

                                          David W. Terry 

Date: 05-05-93 (02:56)              Number: 62011 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ROBERT MILLER
Subj: BETA report              
Read: 05-05-93 (09:50)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        


  I figured out my problem with the Aliases.  Turns out that I had
failed to enable the feature in the PWRD file for each appropriate
security level.  This was mentioned but didn't register fully when I was
making the changes.

  Sorry.  <grin>

Date: 05-05-93 (03:08)              Number: 62013 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ROBERT MILLER
Subj: BETA report              
Read: 05-05-93 (09:54)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        


  Problem: User account data getting corrupted at logon.

  Symptom: User starts to logon and the user record suddenly fills up
with what appears to be random line noise.  This occurs after the name
is entered but before the password is.  This results in logon failures.

  Details: This may be limited to a special type of user but this is a
very, very nasty potential problem.  I have a Macintosh user call my
system.  He is using Zterm and a USR DS to call my node #1's HST.  When
he enters his name and hits enter the user record fills up with random
appearing garbage.  It is not random since the same data appears again
after I edit the account.  The phone numbers, the address, the password
and the comments all get zinged.  I had the user call and use a test
account I have setup.  The same thing happend to this account.  If this
user types in the name of ANY valid user he will knock out their
account.  Running PCBSM analysis on the system does not find any
particular problem.  Node #2 is operating correctly but have not had a
chance to hook up my Mac to see if I can duplicate problem in house.

  Here is a capture of the node's log file:

**************************************************************
      Event #2 - MAILRUN ran at 05-05-93 04:33:18 Node 1
**************************************************************
05-05-93 (04:33) (1) DAN RING Off Abnormally
      Minutes Used: 5
      Time Limit Exceeded.
      Sysop CHAT ended at 04:33
      Sysop CHAT active at 04:29
05-05-93 (04:28) (1) RAD WARRIOR (9600E) (A) Ns(.84zn00
**************************************************************

  I will work on duplicating problem later today when I get a chance.

  Thanks and 'bug' you later.

  Hey, at least it's a REAL bug this time.

Date: 05-05-93 (05:38)              Number: 62016 of 63094 (Refer# 62015)
  To: RONALDO AMORIM
From: DAVID TERRY
Subj: ordering the PPL compiler
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> In order to buy the PPL Compiler, please leave me the number to call from
-> overseas.

Everybody:   You can reach us voice by dialing 801-261-1686 or 800-356-1686.

These are the same numbers we've always had...  if you're interested in
ordering the PPL Compiler please call voice at one of the above numbers.

                                          David W. Terry 

Date: 05-05-93 (05:45)              Number: 62018 of 63094 (Refer# 62010)
  To: ROBERT MILLER
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (10:21)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Updated "online help files" are not yet available.  Someday soon...  I hope.

                                          David W. Terry 

Date: 05-05-93 (05:47)              Number: 62019 of 63094 (Refer# 62009)
  To: FRANK JACOBBERGER
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (06:29)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Wondering about the STATS I SEE on SALT AIR, is that one of the BULLETINS
-> you created after installing the PCBSTATS in PSA allocation within PCBSM?

What stats are you seeing here?

If you are refering to bulletin #6, which shows a graph of System Availability,
then no, that has nothing to do with the Caller Statistics PSA.

For a copy of the program that creates bulletin #6, download SHOWFR10.ZIP.

If I misunderstood your question, please elaborate.

                                          David W. Terry 

Date: 05-05-93 (09:46)              Number: 62031 of 63094 (Refer# 61999)
  To: ADALBERTO FERMIN
From: DAVID TERRY
Subj: beta report              
Read: 05-06-93 (17:58)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> The CALLER? files are improved.  I see more information that i wasnt able to
-> see due to the additions of the "%c:\pcb\texts". I see most of the
-> information now, but I see that record 430 and record 326 is not
-> translating.  Couldn't find others that behave the same yet.
->
->     %c:\pcb\txt\dirscan.430
->     %c:\pcb\txt\nofound.326
->     Minutes Used: 25

I wonder if there is some confusion here....

PCBoard makes NO ATTEMPT to translate your %FILESPEC lines when writing to the
callers log.  What you showed up above is what you should *expect* to see.

There are only two aspects, about v15.0, that I can think of that might lead
erroneously lead you to the conclusions you have drawn.  They are:

1) PCBoard now uses the "PCBTEXT." file (no extension) whenever writing
   information out to the callers log.

   In other words, it no longer matters what language your callers have chosen,
   PCBoard will continue to write out the same text to the callers log.

2) MANY of the prompts in the PCBTEXT file were changed when you upgraded to
   v15.0.  This was done by REPLACING many of your existing pcbtext records.

My thoughts on these two changes, in relation to your report, are that possibly
the reason you think the caller logs have improved is that either:

- You are running a multiingual setup and the main "PCBTEXT." file is cleaner
  than the rest of your pcbtext files, or

- You had heavily customized your pcbtext and lost some of those changes in
  the upgrade.

Check out the above two theories and I think you'll find the true nature of the
situation you have described.

-> When i added PSA "ALIAS SUPPORT", i entered an alias for myself.  I then
-> tried to print the user list.  And discovered that in the printout every
-> user had my "Alias" in the "print-out".

I was unable to duplicate this one.  Please tell me more specifically, what
software are you using (PCBoard, PCBSM), what commands are you using (what are
you typing) and, if possible, please submit a capture file to show me what you
have seen.

Considering the contents of the capture you will probably want to upload it
privately or make your reply to this message private.

                                         David W. Terry 
P.S.
I realize yesterday was the first release and that the *only* code being tested
is yesterday, but please get in the habit of providing the date/time of the
software being tested in every report.

Date: 05-05-93 (09:50)              Number: 62032 of 63094 (Refer# 62007)
  To: JIM HOLLOWAY
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (20:34)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Do you have a short list of PCboard 15.0 features we can post as a bulleting
-> so the callers on my BBS can see what to expect with Ver. 15.0 The WHATSNEW
-> file that comes with the beta is over 100k, maybe something around 5 to 10k
-> in size with some highlights would be nice... Jim

There is a file in directory #2 called USERS15.ZIP.   It's still 8K unzipped,
and certainly not complete, but it covers most of the kinds of things that
callers will want to be aware of.
                                         David W. Terry 

Date: 05-05-93 (09:54)              Number: 62033 of 63094 (Refer# 62013)
  To: ROBERT MILLER
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (10:38)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Problem: User account data getting corrupted at logon.
->
-> Symptom: User starts to logon and the user record suddenly fills up with
-> what appears to be random line noise.  This occurs after the name is entered
-> but before the password is.  This results in logon failures.
->
-> Hey, at least it's a REAL bug this time.

I have to question that last line...  you mentioned "what appears to be random
line noise".  How have you concluded that it is NOT just that ... line noise?

What you have described certainly sounds serious (if it *is* PCBoard that is
doing it) but I haven't seen anything similar so I'm stumped at this point.

-> I will work on duplicating problem later today when I get a chance.

Thanks.  If you are successful, please give me a voice call ASAP at
801-261-1686.  Let whoever answers the phone know that I am expecting your
call.
                                         David W. Terry 

Date: 05-05-93 (09:59)              Number: 62036 of 63094 (Refer# 62021)
  To: FRANK JACOBBERGER
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (16:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Go to your main menu, and type STATS.
->
-> This is the little thing I was trying to mention in previous message. Gives
-> you PERSONAL, MESSAGE etc.
->
-> So, is this a program created with PPL?

Yes.  Look for STATS.ZIP in directory #2 of this conference.

                                         David W. Terry 

Date: 05-05-93 (10:05)              Number: 62037 of 63094 (Refer# 62023)
  To: AQUILA BBS
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (22:14)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> 1) Sharing violations on pcbstats.dat

Using what software?  (i.e. what software is accessing that file?)

PCBoard never accesses that file except in SHARED mode so there will never be a
sharing violation on it coming from PCBoard.

The *only* exception is if you are running TWO SEPARATE VERSIONS of PCBoard.
One with a greater node capacity than the other.  What happens is this:  if
PCBoard finds that the pcbstats.dat is formatted incorrectly it will have to
recreate the file.  During that period of time the file will not be shareable.

Therefore, if you run two different versions of the file you will get sharing
violations as the two programs fight over which format the file should use.

If you are *not* using two separate versions, then please investigate further
to determine what other software may be accessing that file.

-> 2) To many open files error,

Increase your FILES= setting.

Do this on the WORKSTATION and then do it *again* on your SERVER (for servers
that are based on DOS such as LANtastic).

PCBoard v15.0 definitely requires more file handles than did v14.5a, especially
on large systems where CNAMES and PCBTEXT cannot be pre-loaded into memory.

-> We are using Novell and are multitasking with Desqview

There is a setting in Netware that governs how many file handles can be opened.
I don't remember the setting but you'll want to check it out.  It is done on a
workstation basis.
                                         David W. Terry 

Date: 05-05-93 (10:13)              Number: 62039 of 63094 (Refer# 62026)
  To: FRANK JACOBBERGER
From: DAVID TERRY
Subj: OTHER:  MKPCBTXT 04-29-93 05:55:00
Read: 05-05-93 (16:34)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Wondered if the custom created file option for message text still exists?
-> ie. in PCBTEXT I have the following %C:\PCB\GEN\MESSPTT, a @ coded file
-> displaying the options after entering a message. Is this option no longer
-> available?

It definitely ought to work.  But what might have happened is that your
customization was lost when you upgraded to v15.0.  Many entries in the PCBTEXT
file were changed in the upgrade.

Please run MKPCBTXT.EXE on your PCBTEXT file.  RE-customize the prompt and then
report back to me on the status of your report.

                                         David W. Terry 

Date: 05-05-93 (10:15)              Number: 62040 of 63094 (Refer# 62028)
  To: MARK LANGE
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (01:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Darrell Dillingham and I have both had problems with getting the event to
-> run. We have both followed the instructions to the letter and yet the event
-> will not run.

All I can recommend at this point is this:  Re-read and follow explicitly the
instructions contained in EVENT.DOC.

If you have any further problems please describe the problem in as much detail
as possible.  (don't just say "the event didn't run")

Address your reports on events to Louis Zirkel.

                                         David W. Terry 

Date: 05-05-93 (10:30)              Number: 62041 of 63094 (Refer# 62037)
  To: DAVID TERRY
From: PHIL GORDEMER
Subj: BETA report              
Read: 05-05-93 (10:44)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> There is a setting in Netware that governs how many file handles can be
-> opened. I don't remember the setting but you'll want to check it out.  It is
-> done on a workstation basis.

        Thiss can be done in NET.CFG or SHELL.CFG in the same directory as the
IPX/NETX or ODI/NETX drivers.  Add the following line:

        FILE HANDLES=XXX

Where XXX is the number of files to open on the server.  The total of open
files locally(config.sys) and network(Net.cfg) must not exceeed 253.  I suggest
FILE HANDLES=120.

     -----> Phil <-----

Date: 05-05-93 (10:38)              Number: 62042 of 63094 (Refer# 62033)
  To: DAVID TERRY
From: ROBERT MILLER
Subj: BETA report              
Read: 05-05-93 (11:01)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


  Okay, okay, your right about my last line <grin>.

  I've got some further information for you about my problem.  The
problem is isolated to my #1 node and occurs when ANYONE logs in or even
if I run PCBSM and edit the user file locally (on that node).
Everything seems to work fine on nodes #2 and #3.

  The symptom is if I run PCBSM from node #1 and edit the user file as
soon as I arrive at record 1 much of the first screen data get's
trashed.  The result looks like line noise.  SL, download stats and the
other screens are not affected.

  You need hardware info now I suspect.

  Node #1 is a NEC Powermate 386sx (16mhz) with 2mb of RAM and a 40mb
hd.  I'm running DOS 6.0 on a Novell Netware 3.11 system with two file
servers.  The NIC is a NE1000 and I'm using the latest NETX but my
IPX.COM is out of date and I'm working on updating it or changing to
ODIs.  And it is using a USR HST 14.4 internal.

  Node #2 is a DELL 386sx with 4mb of RAM, 200mb hd, NE1000 and the SAME
versions NETX and IPX drivers.  It has two Sony CDU-535 CDs which the
other nodes access via map-assist. This node is using a PPI 14.4 FXSA
internal modem.  It too is running DOS 6.0

  Node #3 is a AST 386/C with 16mb of RAM, SCSI Tape drive, 300mb ESDI
hd, SB Pro with CD ROM.  This is my 'personal' node and is used for
backups and maintenance.

  Nodes #2 and #3 are running fine and are not corrupting the user file.

  I stripped out EVERYTHING from the config.sys file and everything but
IPX and NETX from the autoexec.bat and the problem persists.  I am
moving a copy of PCB to the local drive to see if the problem occurs
without the netware shell loaded.  I'm also updating the IPX to see if
that will help or change anything.  Though considering my two public
nodes are similiar and the one giving me the problem has the least
amount of hardware in it I'm not sure the problem will be the netware
shells.

Here for your reference are my config.sys and autoexec.bat though as
stated I removed everything possible to help isolate the problem.

[CONFIG.SYS]

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS NOMOVEXBDA
buffers=20,0
files=20
dos=UMB
LASTDRIVE=E
FCBS=4,0
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
DEVICEHIGH /L:1,9072 =C:\DOS\ANSI.SYS
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p
dos=HIGH

[AUTOEXEC.BAT]
@echo off
prompt=$p$g
PATH C:\DOS;c:\;c:\cdapps;f:\util;f:\pcb\bin
turbo +
LH /L:1,13984 share
LH /L:1,29504 ipx
LH /L:1,69376 netx
f:
login bubba\nec
cd \pcb
castoff
maclient d:=dell /r
maclient e:=dell /r
rem board

  One difference is that this node can load NETX high since it has so
little hardware installed.  However, loading it low along with IPX did
not effect the system.

  I will try to get you a screen capture of the user file after it get's
hit but I have to dig up a capture util first.  Printing it didn't
result in anything useful.

  Thanks.....

Date: 05-05-93 (10:51)              Number: 62043 of 63094 (Refer# 62037)
  To: AQUILA BBS
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (12:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Further on your File Handle problems...

Some of the problems related to file handles under Netware can be fixed based
on the following information which was provided to us by Howard Belasco:

- Re-install your SERVER.EXE file.  If it becomes corrupt it can malfunction
  by not letting any more than 40 files be opened at once on a workstation.

- If you are using ODI drivers, then edit your NET.CFG file to increase the
  number of file handles.  (FILE HANDLES = XXX)

- If you are using IPX.COM then edit SHELL.CFG to increase the number of file
  handles.  (FILE HANDLES = XXX)

- If you are getting a message about NCP Packets then on your server type:
  SET MAXIMUM OUTSTANDING NCP SEARCHES = 1000

NOTE:  The total number of file handles allocated, when combining the FILES=
setting in your config.sys file with the FILE HANDLES= setting in your .CFG
file must not exceed 253.

Hope this helps.
                                         David W. Terry 

Date: 05-05-93 (11:01)              Number: 62046 of 63094 (Refer# 62042)
  To: ROBERT MILLER
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-06-93 (07:43)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Okay, okay, your right about my last line <grin>.

One thing that comes to mind as a long shot; make *SURE* you are using the same
EXE files (PCBOARD.EXE PCBSM.EXE etc etc) on all nodes.  You probably are, and
this probably won't be that simple, but do it anyway.  As I've heard (seen)
David say (type), no fair guessing.  You gotta go look and see.  Thanks.

   Scott Robison

Date: 05-05-93 (11:15)              Number: 62050 of 63094 (Refer# 62048)
  To: CHRIS KENWARD
From: DANIEL CHLARSON
Subj: PPL Compiler             
Read: 05-05-93 (13:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I would like to purchase the PPL compiler but cannot dial you on your
-> 800 number as I am out of the country in South Africa.
->
-> Please post me as to how to do this - I want to purchase it from you
-> and not from the local agent if this is possible.

Try 801 261 1686 for international orders.

Daniel
Salt Air Sysop

Date: 05-05-93 (13:07)              Number: 62055 of 63094 (Refer# 62037)
  To: DAVID TERRY
From: AQUILA BBS
Subj: BETA report              
Read: 05-05-93 (13:08)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Using what software?  (i.e. what software is accessing that file?)
As far as we can tell it's Pcboard that is accessing the file, we were
running one Pcboard.exe which was the beta version.  It was a complete
system overhaul, and there were no straggling nodes left behind running
a different version.  We'll check on the file handles and see if that
has any effect.

Steve

Date: 05-05-93 (13:37)              Number: 62060 of 63094 (Refer# 62057)
  To: BILL ROBERTS
From: DANIEL CHLARSON
Subj: PPL compiler             
Read: 05-05-93 (13:38)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Hmm, I was charged 15.00 american for shipping.  Is there a diff?

You're not in the continental US, maybe?  <g>

Daniel
Salt Air Sysop

P.S.  Checked your record and you are in CANADA.  People want more money
to take our little boxes to the tundra!  <g>

Date: 05-05-93 (13:38)              Number: 62062 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: BILL ROBERTS
Subj: Missing Message?         
Read: 05-05-93 (13:57)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Try entering in a conference that is marked for NO echo and marked as
forced private this:
H.A.U. [Help All Users]
or any color formatted text like that.  On version pcboard.exe
452576  5-04-93  1:25p
I think you will find that whatever follows the color format will NOT be
there when re-reading the message in normal reading mode!  Weird to say
the least!  Actually, it has happened to ALL messages in the message
base, even messages entered prior to the beta code!  Let me know if you
are able to duplicate this?

---Bill---

Date: 05-05-93 (13:57)              Number: 62066 of 63094 (Refer# 62062)
  To: BILL ROBERTS
From: DAVID TERRY
Subj: Missing Message?         
Read: 05-06-93 (01:21)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Let me know if you are able to duplicate this?

Heck, I don't even understand what you mean yet....  :-)

Your message was colored (and hard to read) so the @X codes you used are
definitely working here.

Could you give me DETAILED step-by-step instructions as to what to do in order
to duplicate your report?

Also, a screen capture showing me what you see would be WONDERFUL and would
help immensely in understanding what it is you are trying to report.

A screen capture showing what you did, from step 1 all the way down to where
the display is not correct would be that much better.

A picture truly is worth a thousand words...

                                         David W. Terry 

Date: 05-05-93 (14:00)              Number: 62067 of 63094 (Refer# 62065)
  To: SWL INC
From: DAVID TERRY
Subj: BETA report              
Read: 05-05-93 (14:08)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I ran the beta door in the Developer's Conference, and it created a BETA.ZIP
-> for me.  I went to the Beta Conference, and reentered the Beta door, but did
-> not (supposedly) create a new BETA.ZIP.
->
-> When I downloaded my flagged files (four preceded the BETA.ZIP) it ended
-> without sending the BETA.ZIP.

The beta door automatically deletes any "prior" versions whenever you enter it
in order to avoid mixing files together (you don't want JOHN DOE's copy of
PCBoard, you want your own).

So when you use the BETA door *don't* use it again (during that session) until
you have downloaded the file that created (unless you don't want to download
that file).
                                         David W. Terry 

Date: 05-05-93 (17:41)              Number: 62077 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: So far so good...        
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Amazing...  this has to be one of the best (if not *the* best) "1st day" of
wide area beta testing we have ever had.

So far there have been no real "show stopper" problems and most of the problems
reported thus far have been solved with configuration changes.

I figure there are two possible explanations:  1) Our excellent alpha and
developer beta testers did a wonderful job of getting v15.0 ready for the
masses, or 2) You guys just can't get back online (thru the busy signals) to
report anything.

I hope it's more of #1 than #2.  :-)

Anyway, if you have already downloaded v15.0 and you are calling back looking
for the "next release" of the beta code, I just thought I'd let you know that
there won't be an update today.

So you can save your long distance pennies and try back again tomorrow or the
next day.
                                         David W. Terry 

P.S.
Check out directories 2 and 23 of this conference if you haven't already.
You'll find lots of "fun stuff" to try out with your new v15.0 software.

Date: 05-05-93 (19:56)              Number: 62079 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: SCOTT BOERKE
Subj: BETA report              
Read: 05-06-93 (09:34)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSETUP.EXE - 05-04-93 00:55:00                       


I am having trouble using the editor to edit the news files or any of
the graphic files.  My setup looks like this:

Name/Loc of User's Menu     : C:\PCB\GEN\BRDM
Name/Loc of Sysop's Menu    : C:\PCB\GEN\BRDS
Name/Loc of News File       : C:\PCB\MAIN\NEWS

I Highlight the News file location, Press F2 or F3 and the editor comes
up and says file not found.  I have the editor configured in PCBSM and I
am using THEDRAW.  I tried the Users Menu, Sysop Menu, Dir, and the news
file and none are found.  They come up fine on the board itself, so the
paths are correct.  I also ran the editor from the DOS prompt and it
loaded fine.

                                        Scott

Date: 05-05-93 (21:42)              Number: 62085 of 63094 (Refer# 62083)
  To: DONALD MEHRTENS
From: TERRY RALEY
Subj: BETA report              
Read: 05-06-93 (05:50)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

go into pcbsm and then to modem setup or somewhere in there look for a
switch that says verify CD turn it to on... that should solve the
problem.. ( same thing happened to me).

Date: 05-05-93 (22:12)              Number: 62090 of 63094 (Refer# 62080)
  To: ROBERT RATHKE
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (18:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When the user joins, they select the "G" and then the channel, but each of
-> them is in thier own world. niether can see any type but thier own.

Go to each of your nodes.  Run PCBSetup in each node's subdirectory.  Check the
name/location of CHAT.DAT.  It must be the same "physical" location for every
node or they won't see each other.

-> Also, what are the commands in the chat section? No Help files
-> available!

I believe the file you want is called CHATMENU.ZIP.  Check out the files in
directory #2... you may have missed other files that are good to have.  :-)

-> Other than this the code looks GREAT! I'm very impressed! The EAS*IEST
-> upgrade I've ever done! Keep up the GREAT work!

Thanks, I am really glad that things are going well.

                                          David W. Terry 

Date: 05-05-93 (22:15)              Number: 62091 of 63094 (Refer# 62081)
  To: JIM HOLLOWAY
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (19:43)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When I logon here I see the message "Testing your System capability" just
-> before the "Do you want Graphics" message, what needs to be set for the
-> message to appear is it done in PCbsetup or as a PCB set statement???

Actually, this is just an example of the flexibility of PCBoard v15.0 and the
new PCBoard Programming Language.

What you are seeing is nothing more than a PPL program that has been hooked
into the "Do you want graphics?" prompt.

You're welcome to install the PPL program on your own system and try it out.  I
believe the name of the file is ANSI-D.ZIP.  It's in directory #2 of this
conference.

-> and what is it doing at that time, setting the baud rate connect speed???

It is doing a RIPscrip and ANSI "auto detect".  It will default the caller to
ANSI Graphics or RIPscrip Graphics if the caller's terminal emulation software
responds to either query.
                                          David W. Terry 

Date: 05-05-93 (22:17)              Number: 62092 of 63094 (Refer# 62084)
  To: RUSSELL JACKSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David,  I looked to see if this had been reported already, but I haven't
-> noticed it. If I join a conference that allows an alias and then abandon
-> that conference, PCBoard isn't changing the alias back to my name. The main
-> board should not allow alias' but I had one there when I abandoned an alias
-> conference.

Go into the PWRD file editor and set the "Allow Alias" setting appropriately so
that the only people that can use aliases are the ones where you answer 'Y' in
the Alias column.

I believe that will take care of the problem.  But let me know, after making
that change, if you run into anything else.

                                          David W. Terry 

Date: 05-05-93 (22:19)              Number: 62093 of 63094 (Refer# 62086)
  To: TERRY RALEY
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (21:14)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> forgot to ask when i called.. arrg.. is there a new ovlsize file??

Actually, the "old ovlsize.exe" will work just fine.

I believe you'll find it in directory #2 ... called OVLSIZE.ZIP.  :-)

-> i cant remember how to set it in the beta door... thanks..

To set the default in the door, DE-select the main executable, then RE-select
it.  The BETA door will then ask you what you want the default to be.

                                          David W. Terry 

Date: 05-05-93 (23:28)              Number: 62096 of 63094 (Refer# 62077)
  To: DAVID TERRY
From: JOHN LUNDELL
Subj: So far so good...        
Read: 05-06-93 (09:54)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I figure there are two possible explanations:  1) Our excellent alpha and
-> developer beta testers did a wonderful job of getting v15.0 ready for the
-> masses, or 2) You guys just can't get back online (thru the busy signals) to
-> report anything.

can't get online is right! <G>  WOW.. never had this problem before.. having to
wait hours to get online kinda messes one up - BUT - it does force one to
really take a second.. a third.. a fourth etc. look at the problem and possibly
find out more info or work around it etc..  it stinks not to be able to connect
but might be a bit helpful in some ways.

Date: 05-06-93 (09:57)              Number: 62097 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ERNEST LAU
Subj: BETA report              
Read: 05-06-93 (09:57)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSM.EXE - 05-04-93 12:39:00                          


PCBSM    EXE    175280 05-04-93  12:39a


Problem:
       When I tried to pack users files, selected (c) or (d) after that when I
       exit, the computer would want to print, the screen below is the capture
       screen.  This is just a minor bug..

Ernest Lau


                           PCBoard System Manager
           Copyright (C) 1987-1991 Clark Development Company, Inc

    ķ
                          Users File Maintenance                        
    ĺ
                                                                        
                   A  Edit  Users File                                  
                   B  Sort  Users File                                  
                   C  Pack  Users File                                  
                   D  Pack  Users File while Online                     
                   E  Print Users File                                  
                   F  Make  Users File Index                            
                   G  Adjust Security Levels                            
                   H  Insert Group Conference                           
                   I  Remove Group Conference                           
                   J  Move Users BETWEEN Conferences                    
                   K  Adjust Expiration Dates                           
                   L  Standardize Phone Formats                         
                   M  Undo (restore backup file)                        
                                                                        
                                                                        
       Use arrow keys to move bar, press ENTER to select, ESC to exit   
 08:52:39  05-05-93  F1  help  caps: OFF  num: ON   ins: OFF 



                           PCBoard System Manager
                               Pack Users File


  Criteria for User Record Removal
  
  Remove Users that are Deleted or `LOCKED OUT'     : Y
  Remove Users who have not been on for XXXX days   : 9999
  Ŀ
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
   Scanning Users File                                                   
   Replacing Deleted Records                                             
   Purifying USERS.INF File                                              
   Processing    63 of    81                                             
  

                 Press PGDN to begin, or press ESC to abort

 08:53:02  05-05-93  F1  help  caps: OFF  num: ON   ins: OFF 


                           PCBoard System Manager
                               Pack Users File


  Criteria for User Record Removal
  
  Remove Users that are Deleted or `LOCKED OUT'     : Y
  Remove Users who have not been on for XXXX days   : 9999
  Remove Users who have not been on since           : 01-01-80
  Remove Users whose Reg. Exp. Date is older than   : 00-00-00


  Criteria for Keeping User Record
  
  Keep Users with security greater than or equal to : 100
  Keep Users that are `LOCKED OUT'                  : Y


  Print Deleted User Records on the Printer         : N


                 Press PGDN to begin, or press ESC to abort

 08:54:15  05-05-93  F1  help  caps: OFF  num: ON   ins: OFF 


          Ŀ
                                                                 
                  (29:2) Error Writing File - Write fault        
                                                                 
                                   LPT1                          
                                                                 
           Automatic retry in  3 seconds.  Press ESC to cancel.  
                                                                 
          

   08:53:46     05-05-93                       caps: OFF  num: ON   ins: OFF

Date: 05-06-93 (01:36)              Number: 62105 of 63094 (Refer# 62037)
  To: DAVID TERRY
From: JOHN HOFFMAN
Subj: Novell File handles setting
Read: 05-06-93 (10:05)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

The Novell File handels are set in either the SHELL.CFG or NET.CFG.
The line is:
 FILE HANDLES = 60

Novell defaults to 40 file handles if that statement is not in the .cfg
file on each work station.
Note 60 is jsut an example.
  JOhn

Date: 05-06-93 (01:40)              Number: 62106 of 63094 (Refer# 62040)
  To: DAVID TERRY
From: MARK LANGE
Subj: BETA report              
Read: 05-06-93 (10:06)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> All I can recommend at this point is this:  Re-read and follow
-> explicitly the instructions contained in EVENT.DOC.

No need, figured out what the problem was already. Wrong path.

Mark

Date: 05-06-93 (05:50)              Number: 62111 of 63094 (Refer# 62085)
  To: TERRY RALEY
From: DONALD MEHRTENS
Subj: Carrier loss             
Read: 05-07-93 (10:41)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> go into pcbsm and then to modem setup or somewhere in there look for
-> a switch that says verify CD turn it to on... that should solve the
-> problem.. ( same thing happened to me).

I could have sworn I did that already, but I'll check.  Thanks.

                Donald

Date: 05-06-93 (06:10)              Number: 62114 of 63094 (Refer# 62098)
  To: ZEIN DAWOOD
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (15:45)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I installed the pcb v15 as per the instructions given. When I deleted the
-> *.XXX file in pcb\main I kept getting a *.XXX corrupt file. Then I installed
-> it again and kept the *.XXX file.

I don't think PCBoard emits a "*.XXX corrupt" message.  Is that a message you
saw on your screen?  What is the *exact* wording of the message?

-> board didn't load, I had a blank screen. Ic ould type and it would accept
-> the enter key, but the board didn't actually load.

I had one other user report this yesterday.

Check your PCBML.DAT file.  Make sure that at least ONE entry in your PCBML.DAT
file is a "no extension" entry.  (the extension column is blank)

This tells PCBoard which of your languages will be the "system language".  It
also means that you will probably have a "PCBoard Defaults" language that your
callers can use for standard prompts to automate their scripts.

-> IS there a way I can just download the pcboard.exe file for pcb v15 and try
-> running that with the rest of the set-up?

Sure.  Go into the BETA door and use the (F)LAG command to flag just a single
file for download.
                                          David W. Terry 

Date: 05-06-93 (06:03)              Number: 62120 of 63094 (Refer# NONE)
  To: ALL
From: GARY WOOD
Subj: PCB15                    
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Is Gary Smith's Autoscribe and Robert Briggs Weekly_limits programs
compatible with PCB15?  I have been running both and do not want to
upgrade if these programs will not work with the new format.  Thank you.

Gary Wood

Date: 05-06-93 (10:08)              Number: 62121 of 63094 (Refer# 62119)
  To: MIKE DEMSKI
From: DAVID TERRY
Subj: COMMENT (7)              
Read: 05-06-93 (23:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I run three nodes with PCBoard 15.0 beta.  Should I have a separate Location
-> of Temporary Work Files for each node?  Right now all three nodes are set at
-> c:\pcb\files\flagged.  Thanks for the info.

Yes, although must have separate (unique) work directory locations. Otherwise
you run the risk of having the working files of each node collide with each
other.

Example:  Two people try to use the QWK D command at the same time.  They would
basically end up with crossed-QWK-packets seeing parts of each others mail or
indexes, etc.

So keep them separate.
                                          David W. Terry 

Date: 05-06-93 (06:24)              Number: 62122 of 63094 (Refer# 62118)
  To: JOE SIEGLER
From: DAVID TERRY
Subj: Address PSA              
Read: 05-07-93 (04:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Saw several mentions of the address PSA thing floating around, but I can't
-> find it.  Is this something that needs to be purchased, or is it something
-> I've just missed?   If it's a case of RTFM, just tell me; I'll understand!

Just go into PCBSM, User Info File Maintenance, Add PCBoard Supported
Allocations and then select the Full Address PSA off the menu.

Nothing to purchase, just install it via PCBSM.  :-)

                                          David W. Terry 

Date: 05-06-93 (06:32)              Number: 62123 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: GORDON ANSON
Subj: BETA report              
Read: 05-07-93 (13:53)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 04-30-93 -15:30:00                       


David
    My events suddenly stopped executing after installation of the code
on 4/30/93.   My event only one executes at 00:30 each evening and was
working fine until I put the 4/30 code on board.  now the event does not
execute any longer.  The date in the event file says it executed on 5/1
at 00:30 but it did not and this is the third and it still has not run.
Any Ideas.  I did not see anything in the messages about a correction.

abit more info

I have two events one main and one called month.. Both events
are exactly the same except one has some additional end of month
processing that includes chopping the callers logs etc.  The events are
set to run at exactly the same time ie 00:30 the main event runs at
00:30 each night s thru s etc .  the monthly event runs only on the 1st
day of each month.  the Daily event ran fine without any problems at all
until the 1st of the month.  When the Montly event ran the log shows it
ran on time on 05/01/93.  since that has occurred, the daily event has
not ran again.  I will repeat again.  both events are set for the same
time only the event main is a daily event where even month is a one time
a month event.  Since the monthly event ran on 5/1, the daily event has
failed to run every day.  It could be the code itself has nothing to do
with this but I need to know what has happened.
   Thanks
    Gordon

I am uploading my event.dat file to you so you can see how it is set up
under the filename ov wizard.dat as a private upload
 Well I guess I wont either since uploads are disaabled ast this time.

Date: 05-06-93 (06:33)              Number: 62124 of 63094 (Refer# 62103)
  To: BILL ROBERTS
From: DAVID TERRY
Subj: Missing Message?         
Read: 05-06-93 (12:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Ok!!!  I duplicated it on your system!!  READ message number 62102 with the
-> settings that I am at now.

Actually, your settings weren't what mattered...

Your message had a couple of @X codes and then an @Xff code (FF in uppercase).

You are probably aware that @Xff is used to RESTORE colors.  What you probably
didn't realize was that @Xff restores the SAVED COLOR.  The color that is saved
when you issue an @x00.

Your message did NOT contain an @x00 in it.

Therefore, the @xFF was restoring WHATEVER was in memory.  So a random
selection was being made.  I was seeing your message in all RED and you were
seeing it in all BLACK.  Others might have seen it in green, blue, whatever.

Before you use @xFF be sure to first issue @x00 to save the color.

By the way, this is nothing new to v15.0.  The same requirement was in v14.5
and v14.5a.  If it "appeared to be working" before, it was just plain luck for
the reasons mentioned up above.  The color that happened to be in memory must
have been a visible color.

Mystery solved.
                                          David W. Terry 

Date: 05-06-93 (09:46)              Number: 62144 of 63094 (Refer# 62142)
  To: ROBERT MILLER
From: STEVE CATMULL
Subj: File Attachments in Messages
Read: 05-06-93 (09:47)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> How does one attach a file to a message.  I see in the whatsnew file some
-> basic info but either missed or didn't understand the specifics of using
-> that feature.

Instead of using S to save a message, use SA (Save w/Attached) instead.

Date: 05-06-93 (09:54)              Number: 62148 of 63094 (Refer# 62094)
  To: CHRIS SLOYAN
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (14:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When a user reads a short messgae, the header with the address and subject
-> info stays very low on the screen instead of moving to the top.

Tell the user to use the (W)rite User Info command and to answer YES when asked
if (s)he wants the system to "Clear screen in betwen messages".

Answering YES to that question will place the header at the top of the screen.

Further, answer NO to the question after that, which asks if the caller wants
to "scroll" the message headers will, in effect, "lock" the message headers at
the top of the screen.

In other words, what you have just described is normal for those that want
PCBoard to operate that way.  But they *do* have a choice and can configure it
to operate differently.

The following is the appropriate information from the WHATSNEW file:

         - The message headers can now remain 'fixed' at the top of the
           screen while reading a long message.  This is done by using the
           (W)rite User Info command and setting "Clear screen between each
           message" to YES and setting "Scroll messages" to NO.


-> The return receipt prompt only show up for me, the sysop.

Two possibilities exist here:

1) You have assumed incorrectly.  The return receipt prompt only shows up if
   you enter a PRIVATE message.  Perhaps you only noticed the prompt for you
   because you were entering PRIVATE messages and the users were entering
   PUBLIC messages.

2) Or, you assumed correctly.  In which case, go into PCBSetup and adjust your
   settings (in each conference desired) for the "Level to Request Return
   Receipt".

   Go into the conference screen, press PGDN to get to the switch settings,
   then look on the right hand side of the screen.

The following related information is found in the WHATSNEW file:

         - A Return Receipt message can be requested when writing a private
           message in a conference where Return Receipts are enabled.

         PCBSetup allows you to determine which users, by security, can request
         return receipts on a conference-by-conference basis.

-> the name and Subject prompts have the brackets unusually wide. Was this
-> planned??

You bet.  From the WHATSNEW file:

 added   The message base has new capabilities including:

         - Longer TO, FROM and SUBJECT fields.  The longer TO and FROM fields
           are only available if enabled on a per conference basis.  They are
           primarily used for Internet addressing.  The limit of the TO and
           FROM fields is 120 characters.  If more characters are used than
           will fit on a single line then PCBoard will wrap down to the next
           line.

-> Ok, here are a few things I noticed, but maybe the DOCS will clear up in
-> time.

Give the WHATSNEW file a thorough reading...  there's a LOT of stuff in there
but it's fairly complete as to what changes have been made.  For now, WHATSNEW
is the best "docs" available for v15.0.

More to come later...
                                         David W. Terry 

Date: 05-06-93 (10:05)              Number: 62151 of 63094 (Refer# 62104)
  To: JOHN LUNDELL
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (16:28)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I have Alias enabled in my games conference.. (and in password, as well as
-> allowing the viewing of the alias when typing WHO) ... when I join the
-> conference and issue a WHO, I can only see "Logging into system" on the node
-> I am on instead of my handle.. then when abandoning to a conference with no
-> alias support the BBS will say "changing back to SYSOP" etc. then I type WHO
-> again and still it says "Logging into system" on the node I am on..

That's what you are supposed to see.   From the WHATSNEW file:

         If PCBSetup : Node Configuration : Show Alias Name in WHO Display is
         set to YES then, as a caller moves into an Alias-Allowed Conference,
         the USERNET file will be updated to show the caller's alias, and when
         the caller moves out of an Alias-Allowed Conference it will revert
         back to the caller's real name.  NOTE:  PCBoard delays this update
         with a blank "Logging into system" status to hide the identity
         change.  After approximately 1 minute, the WHO display will then
         reflect the change in the caller's name (or alias).

The point is...  if someone quickly goes in and out of an ALIAS conference then
other users on the system could repeatedly type WHO and watch the name changing
back and forth and figure what alias belongs to what user.

So by blanking out the name during the transition, and using the "Logging into
system" display instead, which should be a COMMON sight on the BBS as people
log in all the time, it hides the fact that a user is going in and out of the
ALIAS conference making it more difficult to guess alias names.

-> also, my account (Sysops account) gets the message read pointers reset to 0

Did you edit the PWRD file and answer 'Y' in the column "Multiple Logins"?  If
so, that's what it is supposed to be doing and, therefore, that is not an
appropriate setting for your account.

If you did NOT do this (please investigate first to be sure) then check it out
further and let me know what other information you can find out.  Try
duplicating the problem and let me know what steps are required to duplicate
it.

Anyway, from the WHATSNEW file here is the appropriate information:

 added   The PWRD file now has a setting that controls, on a security level
         basis, whether or not an account can be used by multiple callers
         simultaneiously on a multi-node system.

         Answering YES to "Multiple Logins" means that more than one caller
         can be online using the same user-id without getting the "Name
         already in use on another node" message.

         ....  see WHATSNEW for more info in the middle

         2) The Last Message Read pointers as well as Conference Selections
            will automatically be reset whenever a user logs in.  This avoids
            having previous callers read mail and set the pointer to the end
            of the message base causing subsequent callers to not see the
            mail.

Investigate it further and let me know what you find.

                                         David W. Terry 

Date: 05-06-93 (10:08)              Number: 62152 of 63094 (Refer# NONE)
  To: SCOTT ROBISON
From: SWL INC
Subj: PPLC suggestion          
Read: 05-06-93 (10:57)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

I have not received my copy of the PPLC yet, but from reading the PPLDOC.ZIP, I
was wondering if there was any functions to access the number of files and
bytes that a user has flagged for download.

What I am envisioning is writing a PPE for the Flag/Download command that will
watch the day and time and limit the user based on the file count and byte
total.  Files from business-related conferences would be unlimited, but the
PD/Shareware files would have limits during the business day, forr example; one
large file being more acceptable that 15 small ones that total to the same
size.

The details haven't been firmly worked out yet, but I wanted to check that the
PPL had the functions I would need to implement something like this.

Date: 05-06-93 (10:10)              Number: 62153 of 63094 (Refer# 62123)
  To: GORDON ANSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (08:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Go through EVENT.DOC with a fine tooth comb and examine your EVENT setup based
on the EVENT.DOC information.

Look for any descrepencies you might find.  One user found that the problem was
a simple as the "wrong path" having been used for the event files.

If you still cannot spot your event problem, then give Louis a call here in the
office at 801-261-1686.  NOTE:  He was out sick yesterday and will probably be
out sick most (if not all) of today.  So you might want to call tomorrow.

                                         David W. Terry 

Date: 05-06-93 (10:16)              Number: 62156 of 63094 (Refer# 62147)
  To: REGINALD HIRSCH
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (20:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> 1) The utilization of a work directory for qwk packets, am I to create
-> seperatte work dirs for each node.

Yes.

This can be as simple as calling the work directory "WORK" and nothing more.
No drive letter.  No path.  Absolutely no backslashes.  Just "WORK".

Now create a WORK "subdirectory" in each of the directories where your nodes
are run.  Example:  Node 1 might be in \PCB\NODE1 so you would create a
\PCB\NODE1\WORK directory.  Node 2 might be in \PCB\NODE2 so you would create a
\PCB\NODE2\WORK directory.

-> Also the reference to each sub off a main is somewhat confusing.

What "reference" would that be?  Can you point me to what I should be
reading/fixing?  Exact wording and/or line numbers and filenames will be of
tremendous help.

-> For instance my pcboard executables are in d:\pcb and d:\pcb2 and d:\pcb3
-> for each node 1-3.I assume a d:\work1 for node 1 and d:\work2 for node 2 etc
-> or is it d:\pcb\work1 and d:\pcb2\work2.I assume a common d:\work is
-> incorrect as two users creating qwk packets (QWK D) at same time in same
-> work directory would not work.

Your assumption is correct.  See if the above explanation will get you going.

-> Cnames rwcnf looks for the old cname(no extension) I substituted cnames.old
-> and all a-ok.

You can point RWCNF back to the regular CNAMES file.  There is nothing
"different" about it so RWCNF will continue to read it fine.

-> But if I add or change something in cnames will the new old cnames.old be
-> also changed

CNAMES.OLD won't be.  But if you answer 'Y' to SAVE when exiting PCBSetup it
will update the CNAMES file.
                                         David W. Terry 

Date: 05-06-93 (10:23)              Number: 62159 of 63094 (Refer# 62154)
  To: MICHAEL WALTER
From: STEVE CATMULL
Subj: New screens              
Read: 05-09-93 (18:41)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am very impressed with the set of new screens here on salt air. Are these
-> (some of these) available for download?

We have a few of them available for download as MENU.ZIP.  If you screen that
caught your eye is not in that file, just let us know which one interests you
and we'll make it available for download.

Date: 05-06-93 (10:28)              Number: 62161 of 63094 (Refer# 62160)
  To: MIKE DIPIETRO
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (10:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I am running a 10 node board using Lantastic AI, 10mps ethernet cards
-> dedicated 486/33 with 5 386/33's running 2 nodes each under dv.
->
->       When group chat is running and there are type overs
-> IE: two or more people typing and entering at the same time, I am getting
-> system timeouts, beeps, or retry's whatever you want to call it and people
-> are losing carrier.  It appears that the chat is not being buffered.

We also run LANtastic here...

I would recommend checking the SERVER STARTUP settings.  There is a setting in
there for something to do with "lock timeout" or something like that.  Down
near the bottom of the startup settings.

Try DECREASING that value.

That way the server won't slow PCBoard down.  I think it will help you out.
Give it a try and report back.
                                         David W. Terry 

Date: 05-06-93 (10:57)              Number: 62164 of 63094 (Refer# 62152)
  To: SWL INC
From: SCOTT ROBISON
Subj: PPLC suggestion          
Read: 05-07-93 (13:07)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I have not received my copy of the PPLC yet, but from reading the
-> PPLDOC.ZIP, I was wondering if there was any functions to access the number
-> of files and bytes that a user has flagged for download.

First, you do realize that we will not be shipping out disks or docs until
after the wide area beta is finished, right?  Main reason:  I'm still writing
the DOCs.  :)  That being said . . .

There isn't a function to do what you describe.  However, PCB 15.0 does have a
much nicer ratio system in place now that should take care of all your needs.
Maybe I didn't understand what you wanted or why you wanted it.  Care to take
another stab at it?

   Scott Robison

Date: 05-06-93 (11:10)              Number: 62166 of 63094 (Refer# 62165)
  To: PEAK PERF
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (09:32)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When desqview starts the computer beeps when each node loads and all 5
-> windows open but it takes about 60 seconds to load all 5 nodes (usually 10
-> secs). Once they're up if you call node 1 it asks if you want graphics, then
-> you answer Y it won't load the welcome screen, or log on commands.

Are you getting any error messages in your caller logs?  Any on screen?

-> It seems to be a problem with desqview opening the nodes too fast, like each
-> node is reading a file that another node needs. We can run all the nodes if
-> we manually start them from desqview.

Hmmm...  are you sharing one .EXE file amongst all of the nodes?

If so, make sure you have used ATTRIB +R PCBOARDM.EXE in order to make the file
read-only.

If that doesn't cure it, then try making copies of the executable and put one
in each node's subdirectory (just as an experiment to see what happens) and let
me know the results of your testing.
                                         David W. Terry 

Date: 05-06-93 (11:30)              Number: 62168 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: SCOTT BOERKE
Subj: BETA report              
Read: 05-06-93 (12:09)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBSETUP.EXE - 05-04-93 00:55:00                       


I have tried some other editors with the problem that I was having using
the F2 or F3 key to edit the NEWS file or any other ones.  The problem
seems to be with the way THEDRAW loads files.  If you do not specify
an extension it defaults to ANS for ansi or ASC or ASCII.  The only way
to force the load without the extension is to put a period after the
file name and leave the extension blank.  Of course this cannot be done
within PCBSETUP.  I have tried the other editors and they seem to work
fine.  The problem is only with the THEDRAW program.

                                        Scott

PS:  I have switched editors to PCBEDIT.

Date: 05-06-93 (11:55)              Number: 62172 of 63094 (Refer# 62168)
  To: SCOTT BOERKE
From: STEVE CATMULL
Subj: BETA report              
Read: 05-06-93 (18:32)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> If you do not specify an extension it defaults to ANS for ansi or ASC or
-> ASCII.  The only way to force the load without the extension is to put a
-> period after the file name and leave the extension blank.  Of course this
-> cannot be done within PCBSETUP.

What you could do is create a batch file that would load THEDRAW for you.  It
may look like this:

     THEDRAW %1.   <--- Notice the period on the end.  This would enable you
                        to edit any file that did not have an extension,
                        because it would force the period on the end of the
                        filename (%1).

-> PS:  I have switched editors to PCBEDIT.

That'll work too.  :-)

Date: 05-06-93 (12:41)              Number: 62177 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: SHOWFR11.ZIP Posted      
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

With the dramatically changed "availability" of our system - due to the many
phone calls of people dialing in to download the v15.0 beta - it was discovered
that the reports shown in bulletin #6 on our system were not quite accurate.

What they failed to take into account was that with the frequency of calls,
there are times when there are merely seconds between each call and yet the
clock will show the logon and logoff times as being 1 minute appart.

SHOWFREE v1.0 was counting that 1 minute as a full 1 minute of availability
which was distorting the true availability of the system.

Further, as busy as it is, we're finding that many of you leave your systems on
re-dial and then walk away without using a login script.  What happens is that
you get connected and then sit for a couple of minutes at the "Do you want
graphics?" prompt and then the system logs you off.

SHOWFREE v1.0 did not (and could not) take that period of time into account.

But with v15.0 that time can also be tracked by monitoring missed connections.
So, with the above discoveries in mind, and a fresh v15.0 beta out there for
everyone to access, the SHOWFREE program has been updated to v1.1 in order to
provide a little more accuracy in showing system availability.

If you're wondering why the system is so hard to get into lately, check out
bulletin #6 while you're online here.
                                         David W. Terry 

-------------------------------------------------------------------------------
NOTE:  This software is NOT supported.

Feel free to download and use SHOWFR11.ZIP on your system.  If it works for
you, great, if you have problems with it... sorry, but as busy as we are, we
really must concentrate all of our tech support on PCBoard.  So SHOWFR11.ZIP
can be freely used, but it comes with no support.
-------------------------------------------------------------------------------

Date: 05-06-93 (12:43)              Number: 62178 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: HARVEY PIERCE
Subj: BETA report              
Read: 05-06-93 (13:42)              Status: PUBLIC MESSAGE / FILE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBOARD.EXE - 05-03-93 19:53:00                        


David I am having a problem with the logoff script.  It has been working
OK up to this release but getting the following message:

(3:8:3:3) Error opening File !M:\PCB\PPE\GET-ADRS.PPE (Path not found)

I will attach the SCRIPT0.PPS file for your looking if it helps, but it
has been running flawlessly for about 3 weks now.

Date: 05-06-93 (12:47)              Number: 62179 of 63094 (Refer# 62174)
  To: BILL ROBERTS
From: DAVID TERRY
Subj: Missing Message? / Thanks /Y-Gmodem
Read: 05-07-93 (06:23)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Anyway, have you had any problem with the internal Y/Gmodem?

No other reports so far...

-> It would seem that sometimes, not very often, it will work, than most time
-> it will just sit there when the user tries to d/l with it.

I've not experienced this at all...  can you duplicate it in a controlled
environment?

If so, the questions that need answers are these:

- What COMM software is being used by the caller?
- What PROTOCOL was selected?  (accuracy counts here, Procomm Plus, for
  instance, has Ymodem/G and Ymodem/G BATCH ... the BATCH version is the one
  that *must* be used because their "Ymodem/G" is really "1K-Xmodem/G").

-> Other times Y-modem G will start, than it will stop and drop the caller.

If the caller lost carrier then I would attribute it to Line Noise.

PCBoard does not just "hang up the call".  Watch your DTR signal.  The *ONLY*
way that PCBoard can cause the connection to be dropped is by turning DTR off.
This does NOT occur except when the caller logs off.  No exceptions.

However, the MODEM is permitted to drop the connection ANY TIME it wants.  If
line noise is sufficient or if protocol-level errors occur the modem will
decide ON ITS OWN that the connection should be terminated.

This will obviously occur much more frequently in a high-date-rate transfer
such as Ymodem/G than when you are just sitting at a command prompt or entering
a message.  So you're much more likely to see the carrier loss during a file
transfer.  But that does not implicate the file transfer itself as being
responsible.

So try to duplicate it.  Find out what software is being used.  And watch the
CD and DTR lights on your modem.  I think the information should all come
together once you gather it up.

If you find there is indeed a problem that is not logically explained in the
above then let me know the results of your investigation.

-> Heh, should I stick around for a reply ;)

I'm quick...  but not all the time.  :-)
                                         David W. Terry 

Date: 05-06-93 (13:54)              Number: 62183 of 63094 (Refer# NONE)
  To: HARVEY PIERCE
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-06-93 (14:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> David I am having a problem with the logoff script.  It has been working OK
-> up to this release but getting the following message:
->
-> (3:8:3:3) Error opening File !M:\PCB\PPE\GET-ADRS.PPE (Path not found)

Found and (hopefully) fixed.  Thanks for the bug report!

   Scott Robison

Date: 05-06-93 (14:02)              Number: 62185 of 63094 (Refer# 62148)
  To: DAVID TERRY
From: CHRIS SLOYAN
Subj: BETA report              
Read: 05-06-93 (14:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Give the WHATSNEW file a thorough reading...  there's a LOT of stuff
-> in there but it's fairly complete as to what changes have been made.
-> For now, WHATSNEW is the best "docs" available for v15.0.

Hi David,
        I will not quote your message back for space considerations, but
wanted to thank you for answering all of my questions plus the ones I
was just calling with. You psychic!! Thanks again. Will check in soon!
Chris

Date: 05-06-93 (14:17)              Number: 62187 of 63094 (Refer# 62184)
  To: RICKY LACY
From: DAVID TERRY
Subj: So far so good...        
Read: 05-06-93 (14:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I suspect it's been this busy due to the onslaught of people calling in to
-> download the new toys....

It is, of course, "extra heavy" because of all of the "1st time downloaders"
coming in and downloading the entire package.

-> Any chance of maybe setting up one or two nodes that *only* let you leave
-> bug reports?

Things should slow down after people grab the first copy.  Since it costs money
set up new lines... and since the "mad rush" is expected to die down leaving
the new lines empty... we'll probably just wait it out for a little while.

We'll keep monitoring things though and make changes if absolutely necessary.

                                         David W. Terry 

Date: 05-06-93 (14:21)              Number: 62188 of 63094 (Refer# 62186)
  To: CHRIS SLOYAN
From: DAVID TERRY
Subj: My event                 
Read: 05-06-93 (14:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is this part of my event still valid?

-> echo ADJUSTING SYSTEM USER FILES
-> gwbasic bytes_up.bas /s:400                    <-- don't know what this is
-> pcbsm /adjust;uploads
-> pcbpack /users /days:180 /killbak /level:100   <-- invalid
-> pcbsm /sort;security;prireverse

You should be using PCBSM to pack your users file.  See the v14.5 manual for
appropriate command line parameters (similar to what you already have but
different because PCBSM is the one doing the packing).

-> Also, usually my PCB log has the results of the message base packing and
-> that did not show up at all.

You didn't include any calls to PCBPACK in the above - to pack messages anyway
- so I can't tell you what needs to be modified.

Run PCBPACK without any command line parameters and see if the help screen it
gives you helps you solve the problem.
                                         David W. Terry 

Date: 05-06-93 (14:22)              Number: 62189 of 63094 (Refer# 62183)
  To: HARVEY PIERCE
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-06-93 (14:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David I am having a problem with the logoff script.  It has been working OK
-> up to this release but getting the following message:
->
-> (3:8:3:3) Error opening File !M:\PCB\PPE\GET-ADRS.PPE (Path not found)

Oh, BTW, for what you are doing there, you should take a look at the CALL
statement instead of the DISPSTR statement.  Just thought you'd like to know.

   Scott Robison

Date: 05-06-93 (14:33)              Number: 62193 of 63094 (Refer# 62190)
  To: RICKY LACY
From: DAVID TERRY
Subj: couple of questions      
Read: 05-06-93 (14:37)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Where can I get some info about RIP?

You can download the following files which are found in the UPLOAD directory in
this conference:

RIPTM151.EXE   486186  04-23-93  RIPTerm v1.51 -- Terminal program necessary
                                 to access RIPscrip from a BBS.  RIPscript is
                                 a graphical script language that can enhance
                                 the look and feel of your bulletin board
                                 system.

RIPDMO15.EXE   536989  04-26-93  RIPaint v1.5 *DEMO* -- Demonstration version
                                 of paint program you can use to create RIP
                                 screens.  Gives you the ability to test every
                                 function except saving the actual file.
                                 Includes a lot of nifty looking RIP files
                                 that you may use on your BBS.

RIPSCRIP.ZIP    42754  04-26-93  Technical specification for RIPscrip.
                                 Details each of the "commands" that can be
                                 issued using the RIP specification.  Kind of
                                 painful to do by hand but certainly possible.


-> And is the PCBoard implementation compatible with the stuff "the other guys"
-> are working on?

I have two responses to this question:

1) I have no idea how the "other guys" have implemented it.  I've never dialed
   into the software, I've never even looked at the other software.

2) However, RIPscrip is like ANSI.  So although the other guys might go about
   setting things up differently, ultimately, the only "compatibility question"
   here is whether or not we're going to SEND THE SAME CODES as they are.

   The answer to that question has to be yes.  Otherwise RIPscrip simply would
   not work, just like ANSI would not work if we decided to implement ANSI
   differently.

So the choice of how to set up files is very likely to be different between the
two packages.  But what is IN those files will very likely be the same.

-> What exactly is PCBoard looking for in terms of result codes for the
-> Caller-ID information?

"Exactly" nothing in particular.  :-)

Seriously.  All PCBoard does is capture the information that is sent IN BETWEEN
the words "RING" (the first time) and "RING" (the second time).

PCBoard just stores that information in memory and, if you told it to log
connect strings to disk, it will write the information out to the callers log
in the EXACT format in which it was received.

You can further use a PPL program to process the Caller-ID information.
Because a PPL can be used, your usage of Caller-ID can be very different from
the way someone else uses it.  You might use it simply to record where callers
are calling from, while someone else might use it to screen calls, and another
might use it for a dialback setup.

-> Also, which modems do you know of that already support Caller-ID and CONNECT
-> FAX in the way you're looking for it?

That I personally am aware of...  Zyxel.  But I know there are others out
there.  I just do not have the information available because I haven't tried to
remember it.

-> And this one just breaks my heart.  I grabbed the PPLDOC and gave it a quick
-> glance and the one feature I really had my little heart set on is missing.
-> I've got some nifty ideas for making maintenance a breeze if I can just
-> check the amount of diskspace that is free on a given partition.  On first
-> glance I didn't see anything in PPL that might let me do that.  Ideas?

Sure... there's a function that will let you call a DOS interrupt.  You could
do that to call DOS to find out how much disk space is free.

Enjoy!
                                         David W. Terry 

Date: 05-06-93 (15:42)              Number: 62203 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: Overlay Size             
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

I believe the BETA door is defaulting to an overlay size of 14.

I just noticed that PPL programs run *very slowly* at that size.

If you are running PPL programs on your system you might want to
deselect-reselect the main code option in the BETA door and, in the process of
doing so, select a different overlay size.

Alternatively, download OVLSIZE.EXE and you can play around with and set your
own overlay sizes.
                                         David W. Terry 

Date: 05-06-93 (17:03)              Number: 62214 of 63094 (Refer# 62202)
  To: ED HOPPER
From: DAVID TERRY
Subj: Mixed Case & TO: Field   
Read: 05-07-93 (04:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I have noticed some inconsistency in the way PC board handles lower case in
-> messages posted with Long To: names.

I will modify it so that in conferences that are set for Internet TO: names it
will not force uppercase on ANY names (regardless of the length of the name).
Then it is up to the user to be consistent and appropriate.

                                         David W. Terry 

Date: 05-06-93 (18:28)              Number: 62218 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: new code posted          
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

05/06/93 18:24  PCBOARD.EXE
---------------------------
- The Multi-Port version, when using with COMM-DRV (and at no other time),
  would experience long delays while attempting to verify carrier loss due
  to a timer error.  Fixed.

- A system that was configured for multi-lingual operation which had a
  PCBML.DAT that did NOT have an entry with a blank extension in it would
  appear to "lock up" on code load.  Fixed by providing an error message
  indicating that a no-extension entry is needed and then exiting to DOS.

- With some of the problems that have been experienced (due to other software
  writing the MSGS files improperly and messing up message numbers) I have
  modified the Y-scan command so that it will fix up the Last Message Read
  pointers whenever the LMR is found to be out of range for the MSGS file.
  This should help get everyone back "in sync" after the MSGS file is fixed.

- When a conference is set to allow Long TO: Names (for Internet) it also
  allows the caller to type the name in lowercase letters because some
  systems are case-sensitive.  However, this was only working if the name
  entered was greater than 25 characters in length.  Fixed.

  PPL-related
  -----------
- Just because a filename was specified when checking for file existence
  (either by a PPL program or with the PPL execution module within
  PCBoard) didn't mean it would be used.  Squashed.  :)

- The DISPSTR function has the ability to launch a PPE if the string to
  display is prefixed with an exclamation mark and is followed by a
  valid filename.  Unfortunately, I was checking for the existence of
  "!D:\DIR\FILE.EXT" instead of "D:\DIR\FILE.EXT".  In other words, I
  forgot to strip the ! before checking for the file.  Squashed.

- The RDUSYS command would reset last message read pointers for users
  with a security level that allowed multiple logins.  Fixed.

- NOTE:  Neither of these changes require a new PPLC.EXE.  It will
  continue to work as expected.  The only changes necessary are in
  PCBoard.

Date: 05-06-93 (18:38)              Number: 62219 of 63094 (Refer# 62217)
  To: DONALD MEHRTENS
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (17:41)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Someone suggested I set "Verify CD loss" on and that seems to overcome my
-> first hurdle.  Though I'm curious about that switch - according to the help
-> setting it on is supposed to make it less sensitive to momentary carrier
-> interruptions due to retrain.  On my system setting it off makes all three
-> nodes hypersensitive to I-don't-know-what.  PCB immediately thinks carrier
-> is lost in all cases though I doubt there is much retraining going on
-> calling from one Desqview node to another.

Regardless of what you "doubt" ... the _ONLY_ thing that PCBoard is reacting to
is the CD signal going off.

PCBoard is interrupt driven.

As soon as the CD signal goes off PCBoard is interrupted and told that carrier
has been lost.  The "Verify CD Loss" has but *one* effect:  it forces PCBoard
to sit there and wait a moment to see if the CD signal comes back on.  If it
does, everything returns to normal.  If the CD signal does not come back on
after a period of time then PCBoard calls it a "verified carrier loss" and then
it recycles.

There are some MODEMS that will never drop CD except when the caller is gone.
Others will use the CD signal when retraining.  Still others will use it during
flow control.

Much as you might want to think that "all modems are created equal" they're
not.  And that is why it is up to "experienced software developers" to learn
the tricks of the trade ... to understand on a much larger scale what the
modem's behavior is likely to be in differing scenarios.  That is the biggest
edge that we have over the startup BBS authors...  they don't have the
experience under their belt that we do.  :-)

-> One modem was 2400 and I don't think it even can retrain.

Sure can.  I had an old CTS Datacomm 2400 (circa 1988) and it used to drive me
nuts with its retraining.  On this modem it was very noticeable because
whenever it retrained CD would go out for a moment and then it would suddenly
say "CONNECT 2400" right in the middle of what I was doing.  Drove me batty.

So yes, this "retrain" capability has been around for years.

                                         David W. Terry 

Date: 05-06-93 (18:44)              Number: 62222 of 63094 (Refer# 62219)
  To: ALL
From: DAVID TERRY
Subj: BETA report              
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Someone suggested I set "Verify CD loss" on and that seems to overcome my
-> first hurdle.

A clarification for everyone's benefit:

Do _NOT_ turn "Verify CD Loss" off.  Leave it set to YES unless you have a
specific reason for changing it to NO.
                                         David W. Terry 

Date: 05-06-93 (18:54)              Number: 62223 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: MIKE BORZUMATE
Subj: BETA report              
Read: 05-06-93 (18:57)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBSETUP.EXE - 05-04-93 12:55:00                       


I have one genuine bug, and 3 PCBSetup HELP typos.  :)

First the bug.

I was in PCBSetup, in "Modem Info" "Setup" "Comm Port".  The num lock
was ON.  I pressed F1 for help.  Then I toggled the num lock key.  The
status line at the bottom indicated that the num lock was now off.  I
pressed ESCape to get back to the setup program.  When the help window
disappeared, the num lock indicator switched back on.  I toggled num
lock again.  The indicator didn't change.  I toggled it again.  This
time the indicator changed properly, and it worked fine while I was
outside help.  In other words, the toggle of the num lock inside help
wasn't displayed after leaving help.

Here are the typos:

In the help screen for the location of ALLFILES.LST there is a line that
reads: "Press the F2 key to edit the ALLFLES.LST file." -- the filename
is spelled incorrectly.

In the help screen for Modem Switches, Answer on True Ring Detect there
is a line that reads: "A setting of 'N' should only be selected when
using modems which do not return a verbose 'RING' status to PCBoard when
the phone is ringing."  I believe this should read "A setting of 'Y'..."

In the help screen for Message Options, Prompt to Read Mail When Mail
Waiting, the end of the last line reads "...of this setting is enabled."
instead of "...if this setting is enabled."

So, there you go.  I don't know if you really care about minor bugs and
typos, but I had to offer anyway.  :)

Date: 05-06-93 (18:57)              Number: 62225 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: don't use event managers 
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

The following has been added to the APPS list.  I know everyone reads this
file, right?  Well, here it is in the message base just in case you miss it:

Applications which should NOT be used with PCBoard v15.0
--------------------------------------------------------

External Event Managers are no longer needed and shouldn't be used.

More to the point:  There is at least one, an OLD copy of PCBEvent (v2.x),
which would copy only the v14.5a lines of the pcboard.dat file whenever it
ran.  You would therefore LOSE any of the v15.0-specific items of your
configuration.  Items such as "Verify CD Loss" and "Color Selections" would
be some of the mostly notable items "missing" from your configuration after
having used it.
                                         David W. Terry 

Date: 05-06-93 (18:57)              Number: 62226 of 63094 (Refer# 62223)
  To: MIKE BORZUMATE
From: DAVID TERRY
Subj: BETA report              
Read: 05-06-93 (18:58)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> So, there you go.  I don't know if you really care about minor bugs and
-> typos, but I had to offer anyway.  :)

Yes, very much so!  Thanks for the help.
                                         David W. Terry 

Date: 05-06-93 (20:02)              Number: 62229 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: JEFF OLESEN
Subj: BETA report              
Read: 05-06-93 (20:07)              Status: PUBLIC MESSAGE / FILE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        


I have run into a problem with PCB 15.0 My call waiting screen is full
of high ascii heiroglyphics instead of the proper titling in thier
respective fields. The screen layout is ok, but any information that is
non-numerical and not retrieved from the PCBoard.dat file is corrupted.
I am attaching a file that is captured using DesqView (not a very good
representation, but it shows the problem). I am running on a 386-33 with
4 meg of ram, Dos 5, 4DOS ver 4.02 and Lantastic 4.01 AE using Lava
Arcnet cards. For the heck of it, I obtained a copy of my Co-Sysop's (he
is the SYSOP of Lion's Den ) code and it exhibited the same symptoms,
but only on my system. His system is running just fine.

Another problem I noticed, if a user logs in, they get to enter their
name and password. Then they have to type another CR or two to
continue. If they execute R A S the board will come up with 'Scanning
Conference (1)' and freeze until they hit carriage return. Then it will
tell them no messages and print the Scanning Conference (2) whereupon it
freezes again until they hit carriage return. If they drop carrier while
it is in this 'freeze' the system never recycles.


My server is running a USR DS on COM2 with a 16550 chip. The workstation
is running a Ventel-2400 on COM1 (16450), a USR DS on COM2 (16550) and a
Hayes V9600 on COM4 (16450). All four nodes exhibit the same problems. I
have tried bringin ther server up with no network installed and the
problem(s) persist. The server is also running with a Mitsumi CDROM,
a Hitachi CDROM, and a Trantor T128F SCSI card with 7 SCSI hardrives
from 312Mb to 639Mb on it. The CD's are proprietary interfaces.

I will try to have a better (more organized) description of my system to
accompany future bug reports. I just called to get the new code and
decided to leave this message.

Thanks,
 Jeff Olesen, PCB#17155

Date: 05-07-93 (10:43)              Number: 62230 of 63094 (Refer# 62229)
  To: JEFF OLESEN
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> My call waiting screen is full of high ascii heiroglyphics instead of the
-> proper titling in thier respective fields.

The information that should appear on your screen comes out of your PCBTEXT
file.

Do this:  Check your PCBML.DAT file and verify whether or not you have a
"default" entry in there ...  one that has NO EXTENSION (it's blank in the
extension field).

If not, you should add one.  (see the HISTORY notes from today's release for
more details)

Also, check your PCBTEXT file.  The one without an extension.  Save a copy of
it, create a brand new one (with MKPCBTXT), and then bring the board back up.

What happens then?

-> Another problem I noticed, if a user logs in, they get to enter their name
-> and password. Then they have to type another CR or two to continue. If they
-> execute R A S the board will come up with 'Scanning Conference (1)' and
-> freeze until they hit carriage return. Then it will tell them no messages
-> and print the Scanning Conference (2) whereupon it freezes again until they
-> hit carriage return. If they drop carrier while it is in this 'freeze' the
-> system never recycles.

Hmmm...  totally stumped me there.  Call me voice at 801-261-1686 if you can
DUPLICATE this *at will*.  I'll want to be able to dial in and see this for
myself so you'll need to be at your computer when you call.

                                         David W. Terry 

Date: 05-06-93 (23:03)              Number: 62234 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: RAY GARDNER
Subj: Bug Report: PCBPACK?     
Read: 05-11-93 (09:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

David,

        I have experienced lockups using the on-line PCBPACK sysop
commands. When choosing the option to renumber, the system hangs that
particular node and even after rebooting it (ctl-alt-del) the other
nodes appear to become unstable due to various locks not being released.
Please check into it as it was not specific to my machine, I checked
with 3 other local sysops and had them duplicate it with the same
results...

Re's,
        (and if that's the only REAL(grin) bug, i'm sold!!!)

Date: 05-07-93 (01:18)              Number: 62237 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: FRED MCCLAREN
Subj: BETA report              
Read: 05-11-93 (09:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBPACK.EXE - 05-04-93 01:08:00                        



     When I tried to repack a message base and resetting the starting message
number to 1, it ran but it didn't reset the starting message number.  When I
tried to run it the second time it reset the message numbers to something like
373774449-594388976.  I had to delete the message files and re-generate them.

Fred

Date: 05-06-93 (23:56)              Number: 62238 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: PETER VEECK
Subj: PCB - LANtastic Conflict 
Read: 05-07-93 (10:50)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

David,

Not a BUG.  Not PCBoard.  LANtastic's problem; but, affects PCBoard.

LANtastic 5.0 has a built in "Comtrol Server" function similar to
The Network Eye.  The PCBoard 15 call waiting screen does not recognize
any input made in this mode.  The same was true with 14.5.

For information only.  Not a complaint.  No response necessary.

Pete

 * DeLuxe2 1.26b #89sa * Remember Ranch Apocalypse -- Is your BBS next?

Date: 05-07-93 (06:09)              Number: 62245 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: PWRDWARN.ZIP             
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

The message below was previously posted in the Developer Conference.  It is
being moved out to the Beta Conference:

I have posted a file, in directory #2, called PWRDWARN.ZIP which can be used by
anyone (with or without the PPL Compiler, however, source code *is* included).

It is a rather simple program with only two actual lines of source code.

This program will warn a caller if his or her password is about to expire.  It
does so first by issuing the message on the screen and second by writing a
message to the caller.

Since many callers dial into BBS's in an automated fashion to pick up their
mail, they may never see the password warning.  The next thing they know,
PCBoard is no longer allowing them onto the system because their automated
scripts do not take into account the need to change the password.

To help avoid this problem, PCBoard displays PCBTEXT record #711 to the caller
to notify the caller of the impending need to change the password.

By replacing record #711 with a .PPE file, we can now do the same thing (notify
the caller online), plus we can write a message to the caller.  That way, if
the caller is downloading new mail, it is hoped that the caller will pick up
the notification message in the mail packet.

Installation of the PPE file is simple and takes advantage of a change in
MKPCBTXT.  All you do is execute MKPCBTXT like this:

      MKPCBTXT C:\PCB\GEN\PCBTEXT /I:711 !C:\PPE\PWRDWARN.PPE

Then copy the PWRDWARN.MSG file into the same directory where the PWRDWARN.PPE
file is stored and you're all set!

Oh, one more thing, you will need TODAY's release of PCBoard in order for this
program to work.  New code will be posted shortly.

Enjoy!
                                         David W. Terry 

Date: 05-07-93 (06:28)              Number: 62251 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: DAN VEANER
Subj: BETA report              
Read: 05-11-93 (09:39)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-05-93 01:25:00                        


May 5 Code / 386/25  2 node system running on Desqview X

Problem:       With 2 events set up, only one of them is running

What happens:  When the second event should run nothing happens.  The
               first event runs just fine.

Setup:         I have 2 different pcboard.dat files, but they point to
               a lot of the same files.  They share the same event.dat
               file, and both point to \pcb\main for the event files.

Act  Mod  Batch    Begin   End    SMTWTFS   Date      Last
===  ===  =====    =====   =====  =======   ========  ========
Y    E    MAINEVT  07:00   O7:30  YYYYYYY             05-07-93
Y    E    RIMEEVT  03:25   03:45  YYYYYYY             00-00-00

I checked the Last dates in both pcboard.dat files, and they are identical.

In \pcb\main are the following files:

mainevt.001     Node 1 does all the work
mainevt.002     Node 2 waits
rimeevt.002     Node 2 does the mail run.

MAINEVT is the one that works perfectly.  RIMEEVT does nothing.  The date
isn't changed in either event.dat.  It's as if the event weren't set up
at all.

What I did:    I let it run on May 5, and when it didn't work I checked
               the event.doc and carefully went over each step.  I decided
               to leave it alone to see what it did on May 6.  Nothing.
               This morning (May 7) I changed the order of the events in
               both versions of my file (putting RIMEEVT on the top of the
               list).  I did this before 7am, and watched as MAINEVT ran
               flawlessly.  Changing the order is a shot in the dark, but
               I'll watch it tonight to see if there is any change.

Date: 05-07-93 (11:30)              Number: 62253 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: JIM TORGERSON
Subj: BETA report              
Read: 05-11-93 (09:39)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        



    My daily EVEVT does not run.   I have followed the EVENT.DOC
    notes.   I copied my EVENT.SYS  to  MAINEVNT in the \pcb\main
    and in PCBSETUP when i go into EVENT  and hit F2 for
    NAME/LOCATION of EVENT.DAT it comes back with this error:
      (2:3)  Error opening file  - file not founf
                c:\pcb\main\usernet.xxx

thanks,
   Jim Torgerson

Date: 05-07-93 (07:47)              Number: 62255 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: JEFF BINKLEY
Subj: BETA report              
Read: 05-07-93 (11:30)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        


Problem:  MarkMail users are getting messages and message headers which
do not match the message in the PCBoard message base.  Sometimes the
header will contain useful information, other times just garbage.
Generally, on these messages the tagline of the sender gets duplicated
many times over.  The problem appears to not have a pattern (i.e. some
packets are fine, then the next MarkMail download will have messages
messed up).  A packet may/and probably will have both good and bad
messages.  I am running both InterNet and non-InterNet networks.  I have
the extended TO: line enabled on the InterNet confernces but not on the
non-InterNet conferences.  Just a question; can MarkMail handle long TO:
lines ?  I am running MarkMail 2.00B31.  Here is an example of a
message.  I do not have the ability to capture the header right now.  If
you need it I will figure out how.

************************************************************************

share them!

 > One, don't fuck with me or my mama. She's got some strong
 > juju and she will
 > unleash it on your ass :)
Ju Ju? hehe Thats ALL she gots is a little Ju Ju? That aint notin'
MY mom's got Kick YOUR ass ARMY boots! (FLAMES INCLUDED!)


 > Two, you don't have to quote EVERY FUCKING LINE! Just quote
 > enough to keep
 > the thread current. Quoting everything is overkill.
     like quoting EVERYTHING You got a problem with it? :-) ASS HOLE!

 > Colossus



AND what kind of name is Colossus and what the FUCK does it meabn
anyhow??

 > ... Even my mouse has big balls
AND your MOUSE has BIG BALLS and I suppose you have NO balls to
compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!


    MAd Dog

--- FMail 0.94
 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k
(181:192/112)
   alls to compensate!!

 * Origin: The Night Light ** (315)437-8427  ** 1200-14.4k  (181:192/112)

Date: 05-07-93 (08:05)              Number: 62258 of 63094 (Refer# 62255)
  To: JEFF BINKLEY
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (06:14)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Problem:  MarkMail users are getting messages and message headers which do
-> not match the message in the PCBoard message base.  Sometimes the

Did you use the /OLDINDEX setting?  If not, you NEED TO use it.

In your BOARD.BAT file:

        SET PCB=/OLDINDEX (plus whatever other parameters you had there)

In your EVENT when you are packing with PCBPACK:

        PCBPACK /AREA:ALL /OLDINDEX (plus whatever other parameters you have)

Please research the setup and ensure that ALL NODES are configured properly.
When you are done, immediately run PCBPACK *one time* using the following
command:

        PCBPACK /AREA:ALL /INDEX /OLDINDEX

The above will recreate the index files for all message bases.

Let me know a status report after you have performed the above.

                                          David W. Terry 

Date: 05-07-93 (08:09)              Number: 62260 of 63094 (Refer# 62248)
  To: PIERRE DOUCET
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (07:56)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When I install this new PCBOARD.EXE code, I found that the users can't use
-> the function R A S and so on,  in the mail reading try .

Why NOT?  I mean...  what happens when they try?  What do you SEE?

Please submit a capture file showing me what you see.

                                          David W. Terry 

Date: 05-07-93 (10:29)              Number: 62269 of 63094 (Refer# 62267)
  To: CHERYL BAEZ
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (10:36)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> after a caller logs into the board I have a problem exiting to Dos.  The
-> error:
->
-> SYSOP -> c:\pcb\user.sys cannot be opened or found
->
-> appears whenever I use the F1, F10 to the DOS selections from the waiting
-> menu.

The big question is...  what SOFTWARE produced the above message?

PCBoard does not create a message like that.  Please investigate your system
setup to determine what software is producing the message and why it is doing
it.

PCBoard, itself, has no need of a USERS.SYS file when 'exiting to DOS' so I do
not have the answer for you.

-> The other problem I am experiencing is with the new QWK D feature.
->
-> Total Messages Captured for Download -> 265
-> Creating QWK Packet, please wait...
-> Error compressing file.
-> Capture Aborted.  Read Pointers Restored ...

You need to create the PCBQWK.BAT file per instructions in the WHATSNEW file.
Here they are in case you missed them:

         To enable the QWK capability, you must create a batch file, either in
         your PCB directory or somewhere in your path, called PCBQWK.BAT.  A
         sample of what this would look like is as follows:

  ---->    if %1==COMPRESS pkzip -ex -m %2 %3MESSAGES.DAT %3CONTROL.DAT %3*.NDX
  ---->    if %1==EXTRACT  pkunzip -o %2 %3

         The %3 value, when executed, will be your "Work Directory".  You must
         ensure that this directory is a valid directory and that it is NOT
         your current directory.  Example:

              PCBSetup : File Locations : System Files and Directories

              Location of Temporary Work Files  : WORK\


I put "--->" on the two lines up above that need to go into your PCBQWK.BAT
file.  Also, ensure that the commands are VALID FOR YOUR SYSTEM that are in
that batch file.  (i.e. if you have renamed pkzip.exe to just zip.exe then your
batch file should reflect that change)

-> I will set up an account using

Your message to me was public.  I suggest removing the account you created to
avoid having others call in under that account.

Please do not create accounts for us.  Whenever we need to call your system we
will ask that you call us voice so that we can be speaking to you while we dial
in.  We will *almost never* call into a system without you there to watch.
This way we can be sure to see exactly what you are seeing.  And you can be
sure that we are properly helping you.

                                         David W. Terry 

Date: 05-07-93 (10:36)              Number: 62270 of 63094 (Refer# 62269)
  To: DAVID TERRY
From: CHERYL BAEZ
Subj: BETA report              
Read: 05-07-93 (11:36)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> SYSOP -> c:\pcb\user.sys cannot be opened or found
->
-> appears whenever I use the F1, F10 to the DOS selections from the
-> waiting
-> menu.
->
-> The big question is...  what SOFTWARE produced the above message?

I have the CAM-Mail and RoseMail doors on my system.  Both are used by
various users and both has caused the same error to happen.  I don't
know if this is any help or not.

-> Here they are in case you missed them:

Thanks.  I did miss that.  I'll modify the file and then let you know if
I have any more problems.

-> Your message to me was public.  I suggest removing the account you
-> created to avoid having others call in under that account.

No problem.  Account will be removed immediately.

Thanks again.

Cheryl

Date: 05-07-93 (11:50)              Number: 62277 of 63094 (Refer# 62234)
  To: RAY GARDNER
From: SCOTT CARPENTER
Subj: Bug Report: PCBPACK?     
Read: 05-09-93 (11:37)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I have experienced lockups using the on-line PCBPACK sysop commands.

*Please*, in the future, supply the executable file date and time stamp.  It
helps immensly when tracing down things like this.  I know we're in the first
phases, so chances are you're running the original release code, but help us
help you by supplying all the information we need.

And now back to your regularly schedule beta test..... <G>


       ͻ
          Scott Carpenter  
         CDC Support Staff 
       ͼ

Date: 05-07-93 (10:48)              Number: 62278 of 63094 (Refer# 62236)
  To: FRED MCCLAREN
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (02:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I can't get the alias feature to work.  Would you post a message going thru
-> the exact steps to enable this feature?

1) Install the Password PSA via PCBSM

2) Edit the PWRD file and put a 'Y' in the Alias column for those users that
   you will be allowing to use aliases

3) Edit your conferences, answering 'Y' to the Allow Aliases question, for each
   conference where you will be allowing alises to be used.

All that is left is for your callers to pick their aliases...  the (W)rite User
Info command will allow them to do that.
                                         David W. Terry 

Date: 05-07-93 (11:50)              Number: 62281 of 63094 (Refer# 62242)
  To: JIM WENZEL
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (00:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> All of a sudden my drop to dos (via doorway) has quit working... Not sure if
-> it is something we have done here locally or if it is with PCB.

There isn't much (to PCBoard) as far as dropping to DOS is concerned.

If your REMOTE.SYS file exists, and if PCBoard has "rights" on your system to
rename it to REMOTE.BAT then the, then that is the end of PCBoard's
responsibility.

At that point, it becomes the responsibility of BOARD.BAT to detect and execute
REMOTE.BAT.  That, then, is the end of BOARD.BAT's responsibility.

Now it is up to REMOTE.BAT to proper run DOORWAY.

Here are sample board.bat and remote.sys files:

   BOARD.BAT
   ---------
   @echo off
   c:
   cd\pcb
   set dszlog=pcbdsz.log
   if exist remote.bat rename remote.bat remote.sys
   if exist door.bat del door.bat
   if exist endpcb del endpcb
   pcboard
   if exist remote.bat remote    <--- board.bat runs it here
   if exist door.bat door
   if exist event.bat event
   if exist endpcb goto end
   board
   :end

   REMOTE.SYS
   ----------
   set box=no
   doorway com1 /v:d^O /m:600 /g:on /o: /k:v0 /c:dos   <--- check comm port
   set box=
   c:
   cd \pcb
   board

Make sure DOORWAY exists and that you have specified the proper comm port.
Everything should run fine if board.bat and remote.sys are set up properly.

                                         David W. Terry 

Date: 05-07-93 (11:17)              Number: 62283 of 63094 (Refer# 62243)
  To: DEAN LAVIOLETTE
From: DAVID TERRY
Subj: BEta                     
Read: 05-07-93 (21:51)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> You need MORE phone lines over there guy.

We are very much aware of the current conditions.  I realize you are
frustrated. Right now, all I can do is ask that you please be patient and work
with us.  We are *VERY* swamped and more phone lines will really only help us
to become more swamped.

Hang in there, things *will* get better.

-> Don't know why I get this error when I save from PCBSETUP.  Pressing ESC or
-> RETURN 4 or 5 times gets me out.  Don't know which file it is not finding.
->
-> Here is a screen capture...
->
-> Checking directories while saving files...
->
->                Ŀ
->                                                            
->                 (2:3) Error Opening File - File not found  
->                                                            
->                                                            
->                                                            
->                         press any key to continue          
->                                                            
->                

The above didn't help me any...   about all I can recommend is that you go
through your setup and look for a BLANK FIELD in there.

I would imagine that is why it does not give a filename in the above... because
it IS giving the filename, but since it is blank you don't see it.

If you would like me to research it for you then you'll need to upload your
PCBOARD.DAT, CNAMES.@@@ and CNAMES.ADD files.

-> PCBTEXT record #178 and record #179 are identical.  This may be by design.

It is.  One is for expert mode, the other is for novice mode.  That way you can
customize one for novices while keeping the other shorter for experts.

-> Many of the third party application software developers have specified
-> USERS.SYS be set to "O" in DOORS.LST.  However, in the PCBoard help file,
-> there is no mention of "O".  Only "Y" or "N".

I'll take care of that.  Thanks!

-> I have a couple of early bird Users bitching about the message base
-> self-indexing feature.
->
-> How do I turn this OFF.  I too also find it annoying.

You are mistaken in thinking that it is desirable to disable it.  You _WANT_ it
to be turned on because you *need* it to be turned on.  You cannot turn it off.

Instead, what you CAN do is make it so it won't be REQUIRED.

The reason it is happening, at all, is that you are running a NON-v15.0
compliant application which is putting messages into the message base without
updating the v15.0 index files.  Those index files NEED to be updated or you
will NEVER see your mail.

There are three possible solutions then:

1) Switch to a v15.0 compliant package

2) After your non-compliant software inserts messages, have PCBPACK recreate
   the indexes with the following command:

        PCBPACK /AREA:ALL /INDEX /OLDINDEX

3) Alternatively, have PCBPACK simply update the NEW indexes, which can be
   done more quickly, by using this command:

        PCBPACK /AREA:ALL /UPDATE

Hope this helps.  And let me know what you find on the PCBSetup problem.

                                         David W. Terry 

Date: 05-07-93 (11:19)              Number: 62286 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: PCBPACK /UPDATE          
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Having just mentioned the PCBPACK /UPDATE command in the previous message...
This is a old message re-posted from the Developer's Conference:

Just to let everyone know what we're doing here...  QMAIL4 will execute a batch
file called UPLOAD2.BAT right after a caller uploads a .REP packet.

PCBoard will update the MSGS.IDX as soon as someone tries to join a conference
that received one of these replies, or if a caller was already in that
conference then the update will occur when the caller tries to read messages.

In any case, there may be a slight pause while PCBoard updates the .IDX file
before the caller can continue.  The length of the delay depends on how many
messages were inserted from the .REP packet.

In an effort to get the MSGS.IDX files updated before someone joins one of
these conferences, we modified the UPLOAD2.BAT file as follows:

        PCBPACK /AREA:ALL /UPDATE

This tells PCBPack to scan all conferences and update any .IDX files that need
to be updated.  This is a fairly fast process - at least on OUR system with
only 60 conferences - and will only delay the caller for couple of moments.

Of course, if you have 4000 message bases this might not be a good idea.  :-)

I hear Sparky is working on .IDX routines so this technique won't be needed at
all at some point in the future.  And, of course, PCBoard gets along just fine
without doing this and simply updates the .IDX file whenever someone accesses
the MSGS file.  But I wanted to let everyone know how we were using the /UPDATE
parameter to PCBPack in case it might help others.

                                         David W. Terry 

Date: 05-07-93 (11:26)              Number: 62288 of 63094 (Refer# 62284)
  To: RALPH LOBIANCO
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (11:29)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I have had the Alias PSA installed since the first Developers Beta release
-> and have never had a problem up untill the first Wide Beta release. I have
-> two conferences set to use Alias's and I have the Flag set to yes that
-> allows users to change there alias. When a user now goes into a Alais
-> conference it dosn't use there alias and the diplay "You are now protected
-> by a Alias" never displays, even useing the ALIAS toggle dosn't do the
-> trick..

Yes, you ran into a "bug" which was fixed during the Developer Beta.  The bug
allowed you to _NOT_ configure your system properly.  The "fix" now REQUIRES
that you set it up properly.

Here is the portion of the HISTORY that you missed.

04/28/93 17:41  PCBOARD.EXE
---------------------------
- I caught a bug that nobody else spotted.  :-)  The PWRD file has a setting
  for "Allow Alias" and, if set to NO, it should NOT allow a caller of that
  security level to select an alias nor use the alias if one has already been
  selected.

  Well, after looking through the source code I found that, after reading the
  PWRD file in, that parameter was stored and *never again* used.  So it was
  not honoring this restriction.  This is now fixed.

  That means...  if you have been using the alias feature, you might want to
  check your PWRD file and make sure that your callers are set to "YES" on
  that setting, otherwise they might suddenly no longer be able to use their
  alias.

That last paragraph is the important one.

                                         David W. Terry 

Date: 05-07-93 (11:30)              Number: 62290 of 63094 (Refer# 62253)
  To: JIM TORGERSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (13:49)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When trying to use the QWK in reading messages - i.e. R A QWK  it states I
-> have 4 messages captured for download then states:
->
->       ERROR COMPRESSING FILE
->       CAPTURE ABORTED READ POINTERS RESTORED

You missed the requirement for PCBQWK.BAT in the WHATSNEW file.   Here it is:

         To enable the QWK capability, you must create a batch file, either in
         your PCB directory or somewhere in your path, called PCBQWK.BAT.  A
         sample of what this would look like is as follows:

           if %1==COMPRESS pkzip -ex -m %2 %3MESSAGES.DAT %3CONTROL.DAT %3*.NDX
           if %1==EXTRACT  pkunzip -o %2 %3

         The %3 value, when executed, will be your "Work Directory".  You must
         ensure that this directory is a valid directory and that it is NOT
         your current directory.  Example:

              PCBSetup : File Locations : System Files and Directories

              Location of Temporary Work Files  : WORK\

By the way, there is a PCBQWK.BAT file posted in directory #2 if you want to
just download it.  Of course, you need to verify that the commands it contains
are VALID FOR YOUR SYSTEM.  That is, if you have renamed PKZIP.EXE to ZIP.EXE
then your batch file will need to reflect that change.

                                         David W. Terry 

Date: 05-07-93 (11:36)              Number: 62292 of 63094 (Refer# 62270)
  To: CHERYL BAEZ
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> SYSOP -> c:\pcb\user.sys cannot be opened or found
->
-> appears whenever I use the F1, F10 to the DOS selections from the waiting
-> menu.
->
-> I have the CAM-Mail and RoseMail doors on my system.  Both are used by
-> various users and both has caused the same error to happen.  I don't know if
-> this is any help or not.

Does the problem ONLY HAPPEN if a caller has gone thru those doors prior to
your use of the F1/F10 function keys from PCBoard's Call Waiting screen?

I thought you were indicating that it happened "whenever" F1/F10 was pressed.

Please investigate further to find out what conditions are necessary to
creating the problem.

And... if you have one...  use some kind of "text search" program to scan your
.EXE files to find out what software is issuing that "cannot be opened or
found" message.  If you scan for just those words (assuming the above is an
exact quote of the message you are seeing) you should be able to locate what
software is producing the message.
                                         David W. Terry 

Date: 05-07-93 (12:05)              Number: 62297 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: TIM NEFF
Subj: BETA report              
Read: 05-11-93 (09:42)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBOARD.EXE - 05-04-93                                 


If I am understanding correctly, I only need 1 .dat file for my event
and this .dat file will take care of all nodes. Or do I need a seperate
.dat file for each node and only 1 event file for all nodes...
Any way I have been trying with only 1 .dat file and 1 event file and
naming the event file for node 2 as event.002. My problem is node 2 does
not go down...
My pcbsetup for both nodes are pointing to 1 event.dat file..

Tim

Date: 05-07-93 (12:13)              Number: 62298 of 63094 (Refer# NONE)
  To: (Carbon List)
From: SCOTT ROBISON
Subj: Known problems with ATI Graphics Ultra Pro+ Local Bus
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Thomas,

I called ATI today (05-07-93) in an attempt to find out what I could do to make
PCBEdit more reliable when used with the Local Bus adapter you are using.  The
tech support representative I spoke with told me that their engineers are aware
that there are problems with many text (not graphics) mode applications when
used with their card and that they are busily working on resolving those
problems.  So, *I* am happy to report that this doesn't appear to be a problem
with PCBEdit but rather with their card not providing a 100% compatible VGA
text mode 'interface' that will recognize direct screen writes (as I am
doing).  /SNOW should provide an acceptable work around in the meantime as it
utilizes BIOS routines instead of direct memory writes.  That being said . . .

I will also be attempting to contact the developers/engineers at ATI to see
what sort of work around is available that I might be able to add directly to
PCBEdit so that you don't have to work with the /SNOW switch.  But I don't know
how long that might take; watch for future releases!  :)

Thanks for the support and information that allowed me to track this problem
down.  You may want to call ATI yourselves and try to light a fire under them
to get them moving faster.  ;)

   Scott Robison
   CDC Development Staff

cc: BILL FINK                 05-09-93 13:33
cc: EARL BOONE                

Date: 05-07-93 (12:35)              Number: 62299 of 63094 (Refer# 62297)
  To: TIM NEFF
From: LOUIS ZIRKEL
Subj: BETA report              
Read: 05-07-93 (21:51)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Put a /DEBUG:1 in your PCB environment variable for a few hours or so
and then upload me a copy of the callers log for that portion of the day on
node 2.  That'll help me find what I'm looking for hopefully.  Also, include a
copy of the EVENT.DAT file if you would please so I can look at it as well.

        -= Louis Zirkel III =-

Date: 05-07-93 (12:37)              Number: 62301 of 63094 (Refer# 62123)
  To: GORDON ANSON
From: LOUIS ZIRKEL
Subj: BETA report              
Read: 05-08-93 (10:24)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I am uploading my event.dat file to you so you can see how it is set up
-> under the filename ov wizard.dat as a private upload
-> Well I guess I wont either since uploads are disaabled ast this time.
        If you could please try to upload that file as a file attachment to me
I'd appreciate it.  I'd like to take a look at the EVENT.DAT file so I might be
able to track down what the problem is.

        -= Louis Zirkel III =-

Date: 05-07-93 (12:41)              Number: 62303 of 63094 (Refer# 62237)
  To: FRED MCCLAREN
From: LOUIS ZIRKEL
Subj: BETA report              
Read: 05-08-93 (02:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Hmm, those are some big numbers <g>...  Let me look and see what might
be happening...  I'll let you know what I come up with.

        -= Louis Zirkel III =-

Date: 05-07-93 (13:30)              Number: 62308 of 63094 (Refer# 62307)
  To: SWL INC
From: SCOTT ROBISON
Subj: PCBEDIT.ZIP has wrong file date in DIR file
Read: 05-10-93 (15:07)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The new PCBEdit Beta 10 release should be dated 5/5/93 or later, but it is
-> coming up as April, 1993 in the DIR file.

Thanks, fixed.

   Scott Robison

Date: 05-07-93 (13:35)              Number: 62309 of 63094 (Refer# 62305)
  To: SWL INC
From: SCOTT ROBISON
Subj: Known problems with ATI Graphics Ultra Pro+ Local
Read: 05-10-93 (15:07)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I appreciate the effort you're putting into PCBEdit, but I'm afraid I'm not
-> an owner of an ATI Graphics Ultra card.

Well, as listed at the bottom, I only sent it *SPECIFICALLY* to two people who
I know to have those video adapters and have reported problems using PCBEdit
with them.  However, since there may be others out there, I decided to leave
the message public for others to learn from.  Hence, your name was not listed
in the message header, but your first name (or rather the first 'word' in your
user name) appeared because I used the @FIRST@ macro.  Does that make
sense?

   Scott Robison

Date: 05-07-93 (13:48)              Number: 62311 of 63094 (Refer# 62157)
  To: SWL INC
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (15:07)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

You said:

-> I'm not sure that this is truly a software problem, or simply the hardware
-> involved.
->
-> A user can call into my Node 1 with Telix and a script, and it will
-> faithfully log him into the system everytime.
->
-> The same user calling into Node 2 will get blown off, because the script
-> apparently is feeding only carriage returns to the password prompt, which
-> causes an automatic logoff after four attempts.  No dots represented entered
-> characters are shown.

I said:

-> My guess would be that you have added in one of the PPL's (such as ANSI-D)
-> during the login process and that the PPL is producing text during the login
-> that does not quite match what the caller's LOGIN SCRIPT is expecting to
-> see.

You replied:

-> You're right, I did add ANSI-D, but on all nodes, so that should rule that
-> out.

I feel you are too hasty in your judgement.  Please investigate more thoroughly
to discover what is happening there.

I have provided you with the "clue" that I think you needed.  I do not have the
answer for you... but I'll wager money that I was on the right track.

Please take the time to follow up on the investigation based on this new
information.
                                         David W. Terry 

Date: 05-07-93 (13:52)              Number: 62312 of 63094 (Refer# 62120)
  To: GARY WOOD
From: LOUIS ZIRKEL
Subj: PCB15                    
Read: 05-09-93 (14:41)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        I know that AutoScribe has worked like a champ for me...  No real
problems that weren't configuration errors on my part.  As for the WeeklyLimits
program, I have no idea though...  Sorry.

        -= Louis Zirkel III =-

Date: 05-07-93 (13:55)              Number: 62313 of 63094 (Refer# 62310)
  To: JOHN HERITAGE
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I have noticed PCBoard 15.0 does not allow people with a security level of
-> over 110 to engage the 'W' command.  Could you please help with this?.

You have "noticed" incorrectly.

My guess is that you have edited the PWRD file and answered 'Y' in the column
for Multiple Logins.  Per the WHATSNEW file:

         3) Users of such accounts will be unable to use the (W)rite User
            Info command.  This avoids the possibility that someone might,
            either accidently or maliciously, change the password on the
            account thus stopping anyone else from using the multiple user
            account.  It also prevents the user from changing the city/state
            information which might, again either accidently or maliciously,
            be changed to something that is not desired by the sysop for that
            account.

->       The CHAT Command sometimes sends random garbage when say, the local
-> chat buffer is full, and is receiving information from another node.

Please work on DUPLICATING this.  I need to know under *exactly* what
conditions the above is true.  Step by step.  What does it take to reproduce
your report?

-> Also, will you be increasing this type ahead buffer?..  I could type MANY
-> more lines ahead than one line.

No, definitely not.  At least, definitely not in v15.0.

The one-line type ahead is restricted to 1 line due to the problems of keeping
the two cursors straight (the one belonging to the person who has the focus,
and yours).

-> PCBSETUP -- Something Minor.  Character misalignment Between the DATE field,
-> and the word "Date" and the line underneath of it -- when editing the
-> EVENT.DAT file.

Got it.  Thanks.

-> Something I was aware of in PCBoard 14.5a , but unknown if 15.0 still has
-> this problem.  As a joke to a friend of mine, he was viewing a PCBDOOR.TXT,
-> and I entered chat..  and hit f10-esc-f10-esc-f10-esc repeatedly VERY fast
-> multiple time repeatedly...  and sometimes it outputs random ascii garbage
-> and random colors to the screen.. sometimes resulting in a node lockup..

I have no idea if this is still a problem (having never witnessed it as a
problem myself).  Could you, based on what you know of the problem, try to
duplicate it on your system and report back on your findings?  Thanks.

                                         David W. Terry 

Date: 05-07-93 (14:25)              Number: 62316 of 63094 (Refer# 62315)
  To: BARRY DEVINE
From: DAVID TERRY
Subj: COMMENT (1)              
Read: 05-07-93 (21:11)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I can't seem to figure out how to allow file attaches in a conference. When
-> I try, I get a message saying that file attaches not allowed in this
-> conference. Any ideas?

Each conference can be individually configured to allow or disallow file
attachments.

Go into PCBSetup.  Go to the conference in question.  Press the PGDN key once.
This takes you to the conference switches.  Answer 'Y' to the question "Allow
File Attachments".
                                         David W. Terry 

Date: 05-07-93 (15:36)              Number: 62320 of 63094 (Refer# 62319)
  To: JACK GORMAN
From: DAVID TERRY
Subj: Who & Alias              
Read: 05-08-93 (01:30)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> There seems to be a slight problem with the "WHO" command. I originally
-> though that it had to do with him being in an alias conference, but I went
-> back and found that it just does it randomly.
->
->  (#)   Status                  User
->  ---   ---------------------   -----------------------------
->    1   No Caller this Node
->    2   No Caller this Node
->    3   Available for CHAT      JABEN CARGMAN (SEDONA, AZ)
->
->  (#)   Status                  User
->  ---   ---------------------   -----------------------------
->    1   No Caller this Node
->    2   No Caller this Node
->    3   Logging into System

It's working CORRECTLY.  And your original assumption was correct.

Per the WHATSNEW file:

         If PCBSetup : Node Configuration : Show Alias Name in WHO Display is
         set to YES then, as a caller moves into an Alias-Allowed Conference,
         the USERNET file will be updated to show the caller's alias, and when
         the caller moves out of an Alias-Allowed Conference it will revert
         back to the caller's real name.  NOTE:  PCBoard delays this update
         with a blank "Logging into system" status to hide the identity
         change.  After approximately 1 minute, the WHO display will then
         reflect the change in the caller's name (or alias).

Keep an eye on that WHATSNEW file... there's a lot of good information in
there.
                                         David W. Terry 

Date: 05-07-93 (16:04)              Number: 62324 of 63094 (Refer# 62322)
  To: IVAN WINDON
From: DAVID TERRY
Subj: COMMENT (3)              
Read: 05-09-93 (03:10)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The files PCBalias, and pcbaddress, are there files for this, I noticed
-> there were setups for it, but it says the file isn't there.  I havn't found
-> them yet, I don't think.  Othewise everything is working great so far.

There aren't any "files" to use....  nothing to "set up".

All you do is go into "PCBSM : User Info File Maintenance : Add PCBoard
Supported Allocations" and then you select which PSA you want to add.  Press
ENTER.  Answer 'Y' to tell it to add it.  And away it goes...

There's nothing more to do add, no files, no nothing.

                                         David W. Terry 

Date: 05-07-93 (16:06)              Number: 62326 of 63094 (Refer# 62323)
  To: MSI-MICRO SYSTEMS
From: DAVID TERRY
Subj: Possible problem??       
Read: 05-08-93 (15:06)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Has anyone had any trouble with the Attach File to Message function?  I
-> think (but probably don't) I have it set up properly.  I have enabled Attach
-> in each conference and main board, and have made C:\PCB\attach as a
-> directory.  Do I need to include it in the path?  The file nnever gets
-> there.  If I copy the file to it, everything is fine.

What do you SEE when you try?  Tell me *exactly* what you TYPE and *exactly*
what you see after doing it.  (a capture file would be helpful)

Also, if you have a callers log entry that you can show me that could help to.

                                         David W. Terry 

P.S.
If just "copying the file" works, then something is wrong.  Because the file
should not be stored as a normal file.  In other words, if you attach a file
called TESTME.ZIP to a message you will _NOT_ find a file called TESTME.ZIP in
your attachment directory.  More likely it will be called TESTME.000.

Date: 05-07-93 (16:22)              Number: 62327 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: File Attachment Testing  
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

This is *not* new in the current code (it's been in there since at least the
alpha testing stage) but somehow it didn't get documented in the WHATSNEW file.

So the following information is being added to WHATSNEW:

|        NOTE:  After successfully uploading a File Attachment, PCBoard will
|        execute your PCBTEST.BAT file to verify the upload.  You can modify
|        your PCBTEST.BAT processing to jump around certain functions (or
|        even just drop out completely) of PCBTEST.BAT processing by testing
|        the %2 parameter for a value of ATTACH.  Example:
|
|             if '%2 == 'ATTACH goto end

Date: 05-07-93 (16:25)              Number: 62328 of 63094 (Refer# NONE)
  To: ALL
From: STEVE CATMULL
Subj: Auto ANSI/RIP detection  
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Okay folks,

I have released a new version of ANSI-D.PPE for those of you who want auto ansi
detection.

With this release, the name is changing to GRAF-D because of the added RIP
support.  The ANSI just no longer properly described it.

This version is basically a total rewrite.  The two command line options that I
added in the last release are no longer valid, but there are two more you can
play around with.

Have at it and have fun.  If you have questions or problems, leave me a
message.  I am out of here...

Date: 05-07-93 (17:18)              Number: 62330 of 63094 (Refer# 62329)
  To: ART EMERY
From: DAVID TERRY
Subj: Attached file - mail     
Read: 05-08-93 (05:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is it possible to attach a file that already is on the board to a message?

Yes, but it's not really necessary.

The caller can, at the "End of Message Command" prompt, type "FLAG" and then
the name of the file to flag (e.g. FLAG MYFILE.ZIP).

Or, you could download the file (if you are remote) and then use the SA command
(save with attachment) and upload the file.

If you are local it is easier, use the SA command and then select an internal
protocol and PCBoard will ask you where to find the file you are uploading.
You could type C:\DL1\ and it would attach the specified file by copying it out
of C:\DL1\ and into your file attachment location.

And there's the rub...   as a "file attachment" the file takes up space.  If
the file is ALREADY on your board, then it is taking up "extra" space that
wouldn't be needed if you just told the user to type "FLAG FILENAME" instead of
using the "FLAG" command (no parameters) to flag the attached file.

So, yes, it can be done.  But I would discourage it except on an occasional
basis.
                                         David W. Terry 

Date: 05-07-93 (17:23)              Number: 62331 of 63094 (Refer# 62261)
  To: PEKKA NIEMINEN
From: DAVID TERRY
Subj: several internationalization bugs/lacks
Read: 05-08-93 (02:12)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Anyway, thanks for making PCBoard the best BBS software supporting
-> international character sets!  Just a little more to do yet ... :-)

Thank you for the kind words.  This internationalization bit was a pet project
of mine and, as important as *I* think it is, there hasn't been much feedback
on it.

You managed, in one report, to find almost as many bugs as have been found for
the entire alpha/dev/beta cycle.  :-)     (okay, I exagerate a little)

I've fixed up all of the ones you found and will be posting them in the next
release of the code.  Hit me again if you find any more.  Thanks again!

                                         David W. Terry 

Date: 05-07-93 (17:51)              Number: 62335 of 63094 (Refer# 62334)
  To: DONALD MEHRTENS
From: DAVID TERRY
Subj: PCBoard 15.0 file formats
Read: 05-08-93 (11:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Are the file formats for the 15.0 files available?

Not yet...   though they should be sometime soon.

-> Is this me, you, or are Utah phone lines just bad?

MaBell blames the very wet conditions we have had this winter for the line
noise...  so "Utah Phone Lines" would probably be about as accurate as you can
get.
                                         David W. Terry 

Date: 05-07-93 (18:15)              Number: 62336 of 63094 (Refer# 62266)
  To: DAVID TERRY
From: REGINALD HIRSCH
Subj: BETA report              
Read: 05-07-93 (18:28)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

 David can I make a request for anyone running zyxel modems to post
there errorlevel bats for detecting and processing fax
transmittals?.Thanks

Date: 05-07-93 (18:35)              Number: 62340 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: JULIO DAVILA
Subj: event in pcboard 15.0    
Read: 05-11-93 (09:44)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

        I am using the pcb 15.0 code as of 5/04/93 ... I can not seems
to make the event work..  I am only using 1 node and the event>dat is in
a path (in c:\PCB ...  I create the event with a sample of
                                                  c:
                                                  cd\
                                                  dir /p
this was only for me to test.
when the event runs it reads the event.dat and then goes back to the
board.. It seems like is not reading the daily.001 that I made as a
batch..
                   Thank you
                                  Julio

Date: 05-07-93 (18:28)              Number: 62341 of 63094 (Refer# 62336)
  To: REGINALD HIRSCH
From: DAVID TERRY
Subj: BETA report              
Read: 05-07-93 (18:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> David can I make a request for anyone running zyxel modems to post there
-> errorlevel bats for detecting and processing fax
-> transmittals?.Thanks

I looks like you just did.  I unprotected your message.

                                         David W. Terry 

Date: 05-07-93 (18:33)              Number: 62345 of 63094 (Refer# 62104)
  To: JOHN LUNDELL
From: MARC MEDOW
Subj: BETA REPORT              
Read: 05-08-93 (01:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> also, my account (Sysops account) gets the message read pointers
-> reset to 0 .. I can't seem to duplicate this problem as sometimes it
-> does, sometimes it

I had this problem with a PPL program called CHATBOX23. It may be a bug
in the PPL setup. Then again, just guessing.

---
  RM 1.0 B0053  Confuse People: Quote From The Wrong Message

Date: 05-07-93 (18:33)              Number: 62346 of 63094 (Refer# 62188)
  To: LOUIS ZIRKEL
From: MARC MEDOW
Subj: My event                 
Read: 05-11-93 (09:45)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Run PCBPACK without any command line parameters and see if the help
-> screen it gives you helps you solve the problem.

What is the difference between the /fast and /quiet switches?

---
  RM 1.0 B0053  Confussion will be my epitaph


Date: 05-07-93 (18:37)              Number: 62350 of 63094 (Refer# 62343)
  To: MARC MEDOW
From: DAVID TERRY
Subj: Beta Bug                 
Read: 05-08-93 (16:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> A user uploaded 2 unannounced files to conference 3.
->
-> the files were put into the main board instead of conference 3.

Please try to duplicate this report on your system and let me know exactly what
steps are required to duplicate it.
                                         David W. Terry 

Date: 05-07-93 (18:53)              Number: 62352 of 63094 (Refer# 62345)
  To: MARC MEDOW
From: SCOTT ROBISON
Subj: BETA REPORT              
Read: 05-08-93 (16:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I had this problem with a PPL program called CHATBOX23. It may be a bug in
-> the PPL setup. Then again, just guessing.

First, that was a problem in PPL that has since been fixed.  Second, you
probably don't want to be using the multiple logins feature with SysOp level
users.  It was meant as a feature to allow a SysOp to set up a demo account
that could have multiple users using the same name (like TEST USER, password
GUEST) at the same time.  The multiple logins flag will always reset your LMRs
to 0 everytime you logon . . . the CHATBOX/PPL interface wasn't being
differentiated from a logon.

Anyway, to sum up, PPL is fixed, and you are using multiple logins wrong.

Make sense? :)

   Scott Robison

Date: 05-07-93 (18:54)              Number: 62353 of 63094 (Refer# 62347)
  To: MARC MEDOW
From: SCOTT ROBISON
Subj: PCBEDIT VERSION 1.00 WIDE
Read: 05-08-93 (16:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Any explanation what these @ codes mean? I tried them all and the only thing
-> I got that didn't come out as 0 was the CARRIER.

Try them in PCBoard to see what they are defined to be, or check out the PCB 15
docs for further information.

   Scott Robison

Date: 05-07-93 (18:12)              Number: 62354 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: new code posted          
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

05/07/93 18:08  PCBOARD.EXE
---------------------------
- The 5/3/93 Developer Beta had a change which fixed a problem that occured
  with Carbon List messages:  If you wrote a private Carbon List message you
  would be unable to read your own message after saving it unless your name
  was on the Carbon List.

  The "fix", however, allowed everyone to read the message instead of only
  letting those on the list read the message.  Fixed.

- Unless your WELCOME file had @poff@ at the bottom of it, PCBoard was not
  issuing a "press enter to continue" prompt after a novice-mode-caller issued
  the (I)nitial Welcome Screen command from the main command prompt.  Fixed.

- If the PCBML.DAT file had ESC codes in it, PCBoard could misinterpret the
  file causing PCBTEXT display problems.

  Although ESC codes were not appropriate there, this has been fixed anyway.

- The following areas did not used to allow high ascii characters even though
  the high ascii filter was disabled.  (they now did)

    - main command prompt
    - message read command prompt
    - The TO and FROM and USER prompts used for search for messages to or from
      a user (i.e. the commands R USER, R TO and R FROM)
    - the "text to scan for" prompt for the USERS command

- The "Received on" date of a Return Receipt was not being set to the proper
  internationalization format.  Fixed.

- When using the (E)dit Header command and then changing the Packout Date, it
  was improperly converting the date for internationalization.  Fixed.


05/07/93 17:35  PCBSETUP.EXE
----------------------------
- Ever since way back when...  PCBSetup has added a trailing period on
  filenames when using the F2/F3 function keys to edit display files.  It has
  been so long since I used THEDRAW that I completely forgot that *it* was
  the reason why a trailing period was needed in the first place (otherwise
  THEDRAW adds ".ANS" on the end) and so I removed the trailing period.

  Now that I have been brought back to my senses...  the trailing period is
  back in there again.

  BTW, everyone should check out PCBEDIT.  It's a great little utility for
  creating display files using PCBoard's @-codes.

- The PWRD editor was giving defaults of 9999999 in the File and Byte Limit
  fields whenever ALT-I was pressed.  Fixed.

- The Help Screens, after pressing ESC to exit, were not restoring the time
  and keyboard status at the bottom of the screen.  (actually, they were
  restoring the saved information, not the current updated information)

  This fix will be applied to all of the utilities.

- Added a WARNING display in Configuration Options : System Control for the
  "Encrypt Users File" setting.  This setting should not be used lightly.  See
  the help screen for details.

- If you had a subdirectory (off the CURRENT directory) that was the same name
  as your QWK PACKET name (specified in Configuration Options : Messages) then
  PCBSetup would give an erroneous error message indicating that the name of
  your packet file conflicted with the subdirectory that was found.  Fixed.

- Modified the Conference Name field to allow high ascii characters.


05/07/93 17:33  PCBSM.EXE
-------------------------
- The USERS File Editor was not properly converted high ascii characters to
  uppercase letters (for internationalization).  Fixed.

- The Online Pack (/PURGE) option was printing headers to the printer (or
  output file) whether you requested it to or not.  Fixed.

- The screen was not being restored after an ALT-R command to repeat the
  last search in the USERS File Editor.  Fixed.

Date: 05-07-93 (19:34)              Number: 62356 of 63094 (Refer# 62355)
  To: TONY WADDELL
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> A user logged on who didn't have ANSI capability.  They wanted to leave me a
-> message and the board asked "Use Full Screen Editor?"  They answered, "Y",
-> which was the default answer, and the board told them that "Full Screen
-> Editor requires ANSI capability."
->
-> If PCBoard knows whether or not the user has ANSI capability, wouldn't it be
-> better if the question was bypassed and not even offer the FSE?

Nope.  Because NOT ALL comm programs respond to the query that lets PCBoard
know whether or not the caller has ANSI on his end.

Why punish them just because they have a "older" terminal emulation package?

But... in the same vein, we don't want to punish them by suddenly dumping them
into a Full Screen Editor full of codes that they can't ready.  So it gives
them a second chance - to verify that they *really* want to use the FSE.

-> Cosmetic, for sure, but you guys do such a good job with everything and I
-> wondered how this one was missed!

In fact, it wasn't missed.  :-)

It was put there by design, way back when v14.5 was first coming out, after we
discovered that not everyone is going to have a comm program that will let
PCBoard know whether or not ANSI is available.

                                         David W. Terry 

Date: 05-07-93 (21:03)              Number: 62360 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ROY REYER
Subj: BETA report              
Read: 05-11-93 (09:45)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-06-93                                 


I'm also having a problem getting my event(s) to run and getting the
message unable to open usernet.xxx when hitting F2 to edit the event...

Date: 05-08-93 (01:28)              Number: 62371 of 63094 (Refer# 62168)
  To: SCOTT BOERKE
From: DON REID
Subj: BETA report              
Read: 05-08-93 (22:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

SB>The problem is only with the THEDRAW program.

When I was using THEDRAW, I could never get it to come up in PCBsetup. I
had to use it outside.

SB>PS:  I have switched editors to PCBEDIT.

I think you'll be glad you did. ;-)

 * SLMR 2.1a #1128 * CLAN DONNACHAIDH (ROBERTSON CLAN) U.S.A. BBS 510-937-6570


Date: 05-08-93 (02:04)              Number: 62377 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: TIM ELSON
Subj: BETA report              
Read: 05-11-93 (09:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-03-93                                 


David, I've had trouble with te code running the event.
I've named the event "daily" in the setup. I've created daily.XXX files
for my six nodes.
Problem...the batch files don't run. The event is reported as ru  i the
caller's log as expected, but the actual event doesn't go.
Am I doing something wrong or is this a bug?.
I can't give you a screen cap cause, nothing happens, just a blank
screen warning of event timer and poof...back to BBS. <:-)..just testing
right...I like it, but you need more lines when you do this.
I've tried all hours literally with three HST modems going and finally
got lucky today!.
If this is unique, please call. 705-737-9365<data>... I'll accept the
charges...

Nice Stuff!

Tim..

Date: 05-08-93 (02:39)              Number: 62380 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: GORDON MALONE
Subj: BETA report              
Read: 05-08-93 (12:15)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-06-93 18:24:00                        


Hi David! Neat!

Is this the PPL that did this? I like it!

Anyway, a few minor things

1) The origin entry option in setup only allows UPPERCASE.
Should be able to use both UPPER and lowercase in the originlines.

2) You forgot to update the FSEC editing portion to allow for FSEC file
over 256 lines. I'm still getting error when I attempt to edit via
PCBsetup and have to pop out and use an external editor.

Gord

Date: 05-08-93 (05:29)              Number: 62388 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ART EMERY
Subj: EVENT.DAT file           
Read: 05-11-93 (09:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

I had a problem (no brain in head) and made the end time earlier then
the Start time so the event did not run, however, that bit of dumbness
is not my question what I did find was that the EVENT.DAT file created
is 66,772 bytes for a single node single event. The file contains one
line of required info and is then padded with garbage. Is this the way
it is supposed to be or do I have a problem?

Thanks for the answer about the attached file.

Art

Date: 05-08-93 (08:47)              Number: 62401 of 63094 (Refer# 62358)
  To: JIM HOLLOWAY
From: DAVID TERRY
Subj: new help files??         
Read: 05-09-93 (14:24)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Are there new .hlp files for PCboard 15.0 beta???  Jim

Still no.  We will announce it here when they are ready.

                                          David W. Terry 

Date: 05-08-93 (09:31)              Number: 62403 of 63094 (Refer# 62327)
  To: DAVID TERRY
From: STACY SMITH
Subj: File Attachment Testing  
Read: 05-08-93 (12:29)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

DT NOTE:  After successfully uploading a File Attachment, PCBoard will
   execute your PCBTEST.BAT file to verify the upload.  You can modify
   your PCBTEST.BAT processing to jump around certain functions (or
   even just drop out completely) of PCBTEST.BAT processing by testing
   the %2 parameter for a value of ATTACH.  Example:
  
       if '%2 == 'ATTACH goto end

FYI, ULP has been modified to properly test and handle file attachments,
and will be released in the near future as 0.99.

BTW, I think your batch line example above is wrong...it should be:

    if '%2' == 'ATTACH' goto end

or

    if %2 == ATTACH goto end
---
  QMPro 1.02 41-6664  Ok, I pulled the pin. Now what? Where are you going?

Date: 05-08-93 (08:54)              Number: 62405 of 63094 (Refer# 62366)
  To: RICK DILORENZO
From: DAVID TERRY
Subj: vroom version            
Read: 05-10-93 (23:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> All versions of the code are now overlay versions.

-> Won't that mean PCBoard will be slower or something?  I don't have memory
-> problems at all so wouldn't mind using the regular NON-overlay version.
-> Want speed most of all.

In order to 'cram' all of the new features into PCBoard, the memory
requirements for PCBoard had to go way up.

The only way to "keep up the speed" was to "reduce the memory requirements"
because in a low memory environment it will actually slow down.

So by going to an overlay version for everyone we kept the memory requirements
down and the speed up.

You can adjust your overlay size by using the OVLSIZE.EXE program.  Right now I
would recommend a setting of 16 if you are running PPL programs.  You can
experiment with higher and lower sizes to see what works best for you.

                                          David W. Terry 

Date: 05-08-93 (08:55)              Number: 62406 of 63094 (Refer# 62367)
  To: MIKE DEMSKI
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (10:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I keep running into these errors on both my nodes
-> when someone uploads a SOUL.REP (not Qmail, but via QWK)
->
-> MSG2.$$$ NOT FOUND!     <----- Happened only once

Don't worry about them.  They are not harming anything.  I will try to remove
them later on.  The message is inconsequential.

                                          David W. Terry 

Date: 05-08-93 (08:57)              Number: 62407 of 63094 (Refer# 62368)
  To: NANCY H. MILLER
From: DAVID TERRY
Subj: BETA REPORT              
Read: 05-09-93 (16:20)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I converted two PCBTEXT files using FIXTEXT.EXE.  Since I only had two, I
-> did them "by hand" and redirected the results to a log file.  I unzipped
-> FIXTEXT.ZIP into C:\BBS\GEN, the subdirectory containing my PCBTEXT files,
-> and ran it within the directory.  In both cases the following showed up:
->
-> Record #29 (from/to)
-> CAUTION: Insure all other nodes are at the DOS prompt!
-> !|*|Y01000400|c0A|@0005RIPscrip |Y01000200|c0B|@3W0Fmode on|g0006

And, in both cases, it was correct.  :-)

Record #29 is similar to another record that says "Graphics mode on" except in
this case it is saying "RIPscrip mode on" only, as you can see, with a little
more to it than that.

Try calling into your system with RIPterm and use the M;RIP command and you'll
see it in action.
                                          David W. Terry 

Date: 05-08-93 (08:59)              Number: 62408 of 63094 (Refer# 62370)
  To: DON REID
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (01:50)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I'm wondering if these WORK direcpories can be in a RAM drive, and what else
-> in PCB 15 could be directed to a RAM drive? Thanks!

Yes, the WORK directory can be used as a RAM drive.  The latter part of your
question pertains to all versions of PCBoard and is not really specific to
PCBoard v15.0.  Therefore the same answer still applies.

If you need an answer, please post the question in conference #1.

                                          David W. Terry 

Date: 05-08-93 (09:09)              Number: 62409 of 63094 (Refer# 62375)
  To: DON REID
From: DAVID TERRY
Subj: Setup problem         1/2
Read: 05-10-93 (01:55)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> C:\PCB\MAIN\USERNET.XXX: format error
-> Exiting to DOS!

You missed one of the steps in the README.1ST file.  It said to DELETE that
file.  Do so, and PCBoard will create a new one.

Also, make sure that you do NOT run "mixed software".  Either all nodes should
be running v14.5a, or all nodes should be running v15.0.  Do NOT attempt to run
some nodes on one version and some nodes on another.

-> 2/ Here's another little problem I ran into while logged onto Node 1:
-> (194 min. left) Main Board Command? chat
->
-> Node CHAT: (G)roup, (U)navailable, (H)elp, (Enter)=none? (g)
->
-> (C:\PCB\GEN\GCTOPIC) is missing! <--????????

Download CHATMENU.ZIP from directory #2 of this conference.  You might want to
examine that directory as well as the upload directory for other files that may
be of interest/value to you.

-> 3/ A caller tried using the QWK feature and it didn't work, resulting in the
-> message:
->
-> "Error Compressing File. Capture Aborted. Read Pointers Restored"
-> Sounds like it couldn't find PKZIP?

Download PCBQWK.BAT from directory #2.  See the WHATSNEW file for details.

-> 4/ In running an analysis of the setup into DIAG0507.TXT, the
-> following messages appeared:
->
-> (2:3) Error Opening File - File not found
->
->         C:\PCB\MAIN\pcbndx.G

Sounds like you need to re-index your users file.  Go into PCBSM, select Users
File Maintenance, then select Create User Index Files.

-> 5/ added   A Logon Script Questionnaire is now available which can be
-> run after the caller has answered the login questions
->
-> Where *is* this Script Questionnaire?

We don't SUPPLY you with one.  We added the CAPABILITY for running one.  You
will need to create the questionnaire yourself _IF_ you are wanting to run a
logon questionnaire.

See PCBSetup : File : Scripts for more information.

-> 6/ added   Conference INTRO Files.
->
-> Where do I find these INTRO files?

We don't SUPPLY these to you.  We added the CAPABILITY for displaying them.
You will need to create them yourself.  Just like on Salt Air, you can have an
introduction for each conference.  Try joining a conference here and you'll see
an example of what it *CAN* look like (though what you create can be VERY
different from what we have done here).

-> 7/ I have always wanted to have my entire screen with a blue background and
-> a yellow foreground, while reading or entering messages, and have never
-> learned how to do it. Maybe you would be willing to explain it to me?

Go into PCBSetup : Configuration Options : Colors.

Try a setting such as 1F as the default color.

-> 8/ While watching a caller try various features this evening, when she tried
-> to OP 1 (the QMail4 door), the board would lock up each time and the
-> following appeared every time:
->
-> File allocation table bad, drive C Select:   Abort

This is a DOS error message and indicates you have problems with your hard
drive.  If you do not understand this message then I recommend you get an
expert to come over to your BBS and work on it.  We cannot supply you with the
Technical Support necessary to deal with File Allocation Table problems.

-> C:\WP51\MAC\ALTA.WPM
-> Is cross linked on allocation unit 5389

Yup, those are all indications of a File Allocation Table problem.

You'll want to rememedy this ASAP.  Good luck to you.

                                          David W. Terry 

Date: 05-08-93 (09:15)              Number: 62411 of 63094 (Refer# 62379)
  To: JOE SIEGLER
From: DAVID TERRY
Subj: Overlay Size             
Read: 05-10-93 (05:04)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I already tried 16.   Seems to speed it up a little bit.   However, my
-> original question still stands.  Can you tell me what this overlay number
-> thing DOES?   I'm a bit unfamiliar with what overlays do, and even more so
-> what this number thing is.

You'll notice that PCBoard's executable is now over 400K in size.

Rather than holding this entire 400K .EXE file in memory, and using up 400K
*just* for the CODE portion (not even counting the DATA requirements of the
program) it is instead using overlays.

This means that only a portion of the 400K .EXE file is in memory at any given
time.  How MUCH of the executable can be held in memory depends on two factors:
1) How much of it is "resident" (not in the overlay) and 2) How big the overlay
bufffer is.

A setting of 16 sets up a 64K overlay buffer.  That means that PCBoard can swap
pieces of the .EXE file in and out of memory keeping up to 64K of it in the
overlay buffer.

A higher value allows more of the .EXE file to be held in memory.  The highest
possible value, of course, would simply load the ENTIRE .EXE file into memory
at "load time" and would never again access the hard disk.

But that would be wasteful of memory.  So a smaller value, such as 16, is used.
This lets PCBoard pull in the code that is running, when it is needed, and
leave the rest of the code on disk until it is needed.

Lower values may hurt performance by causing PCBoard to continually swap code
in from disk - creating more disk activity than would otherwise be necessary.

So allowing you to pick the buffer size allows you to "tune" your system to
meet your memory AND performance needs.  If you need more memory, go for a
lower overlay buffer size.  If you need more performance, go for a higher
buffer size.

Hope this helps.
                                          David W. Terry 

Date: 05-08-93 (09:17)              Number: 62412 of 63094 (Refer# 62382)
  To: LEN HULT
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (01:36)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> The WHATSNEW file states that additional settings are available on a
-> per-conference basis, such as Force echo mail, security level to enter a
-> message, etc.  I am unable to locate these settings.  They do not appear in
-> PCBSETUP under conference maintenance.  What am I overlooking?

Press the PGDN key and you'll find them...  :-)

                                          David W. Terry 

(I suppose that, since PGDN is used, this implies the settings were "under"
what you were looking at...  does this mean you really *were* OVER-looking the
settings?)  <g>

Date: 05-08-93 (09:19)              Number: 62413 of 63094 (Refer# 62390)
  To: MIKE ADAMSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (05:53)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> How does one create RIPscrip graphics?  Is there a set of menus available
-> that we can install or a program that will create these graphics?

Check out RIPaint in the upload directory...  NOTE:  this is just a DEMO
version.  It works, but it does not "save" the screen after you create it.
Contact the authors for further information.

                                          David W. Terry 

Date: 05-08-93 (09:27)              Number: 62414 of 63094 (Refer# 62397)
  To: LEN HULT
From: DAVID TERRY
Subj: pcb 15.0 - got it!       
Read: 05-11-93 (01:36)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> My DV windows don't scroll like they did with 14.5a.  They're not as pretty!
-> I'm being petty, I know.  But 14.5a would reset itself to the top of the
-> window, and 15 doesn't seem to do this.  Am I making any sense at all? Maybe
-> you just have to be here!

It was changed on purpose.

Version 14.5a showed "useless information" (the top left corner of the menu) in
every DESQview window opened.

Version 14.5a/M (multiport) and all models of v15.0 put the Call Waiting
Statistics on the screen instead.  This allows you to quickly glance at each of
the windows and see who was last on and how many calls each node has taken,
etc.  In other words, "useful" rather than "useless" information.

I will definitely AGREE...  it's "uglier" than it was before...  but it is also
definitely more useful.  You no longer have to switch to each node just to find
out what kind of activity it has experienced.

One more change in behavior:  As soon as you press a key, v15.0 will "re-focus"
the window up to the menu so that you can see what you are doing.  So it shows
useful information when you're not doing anything, or it shows the menu when
you are.
                                          David W. Terry 

Date: 05-08-93 (09:29)              Number: 62415 of 63094 (Refer# 62398)
  To: DENNIS HUMPHREY
From: DAVID TERRY
Subj: OTHER:  PPL 05-06-93     
Read: 05-09-93 (23:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I called in and ordered the ppl lanquage on 05-06-93 and was told by the
-> telephone operator that I should not try and download it for at least 4
-> hours.  I have not yet been able to download this file as of 05-08-93. Was
-> wondering if there is some problem or are you folks just swamped.

Oops...  swamped is certainly accurate, but it looks like someone forgot to
upgrade you.  I've taken care of it for you just now.  Sorry for the trouble.

                                          David W. Terry 

Date: 05-08-93 (09:30)              Number: 62416 of 63094 (Refer# 62399)
  To: RAY CRAMER
From: DAVID TERRY
Subj: Suggestion               
Read: 05-09-93 (00:19)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Show in the Beta conference NEWS what the latest date/time was on the most
-> recent BETA 15.0.

Type "HISTORY" at the command prompt.

This command also lets you view the ENTIRE history - as opposed to what you get
when you download a new BETA.ZIP which merely includes the most recent history
based on your last download date.

-> Just a suggestion to keep folks from going in and out of BETA DOOR everytime
-> they call.

Good point.

Of course, you can also type "BETA NEW" and this will very quickly take you
into the door, and bring you right back out if there is nothing new.

                                          David W. Terry 

Date: 05-08-93 (09:35)              Number: 62417 of 63094 (Refer# 62403)
  To: STACY SMITH
From: DAVID TERRY
Subj: File Attachment Testing  
Read: 05-09-93 (07:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> BTW, I think your batch line example above is wrong...it should be:
->
->   if '%2' == 'ATTACH' goto end
->
-> or
->
->   if %2 == ATTACH goto end

Either one (and even MY example) will work.

The only reason I put an apostrophe in there is, NOT for semantics, but to keep
DOS from getting an error if %2 happened to be blank for some reason.  It
should never be blank in this instance so it isn't necessary.

In other words, the following are all perfectly valid:

        if HITHERE%2 == HIGHTHEREATTACH goto end
        if $%2 == $ATTACH goto end
        if "%2" == "ATTACH" goto end
        if %2 == ATTACH goto end

As you can see, all that DOS *really* does is replace %2 with the second
command line parameter and then compare the two.

However, that last example will experience an ERROR if you do *not* pass a
second command line parameter.  Try it and you'll see.

And that is the *single* reason for including anythinkg (apostrophes, quotes,
any other text) next to the %2.  There is no other reason.  Quotes are *not*
needed by DOS's batch file language and, in fact, have no effect whatsoever
except as a placeholder just like other characters in the above examples.

                                          David W. Terry 

Date: 05-08-93 (09:39)              Number: 62418 of 63094 (Refer# 62410)
  To: DON SHRIVER
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (22:05)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Instructions call for running FIXTEXT on PCBTEXT files. Could not file
-> FIXTEXT file. Ran MKPCBTEXT instead.

FIXTEXT.ZIP is available in directory #2.

I would recommend going back to your v14.5a PCBTEXT files and then running
FIXTEXT on them.  MKPCBTXT *will* work.  But FIXTEXT tries to keep more of
*your* customizations intact.  Of course, if you have not heavily customized
your PCBTEXT file then either method will work.

-> =====Per instructions, deleted USERNET.XXX file. PCBoard did NOT create it.

PCBoard will only create it if you are set up for multi-node operation.

-> =====Can't get new EVENT system to work. Followed instructions but events do
-> NOT run, and no warning is given.

Read through EVENT.DOC.  Most event problems are configuration errors.  If you
still have a problem, please report AS MUCH DETAIL AS POSSIBLE on what you are
doing and what you are seeing to Louis Zirkel.

-> =====Also, receiving DOS Sharing Violations when users close doors. System
-> freezes. Tried all options and removed other accessory files from door batch
-> files, but share violations continue.

I'm sorry, I have no idea there.

What software is producing the DOS Sharing Violations?  (i.e. what software is
RUNNING when the share violation occurs?)

Also, have you tried going back into PCBSetup and answer 'Y' for the multinode
setup?  Perhaps that will have an effect.

Please report on the results of your investigation into this.

                                          David W. Terry 

Date: 05-08-93 (11:28)              Number: 62429 of 63094 (Refer# 62424)
  To: JOEY MARQUEZ
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (01:43)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When in CHAT and you type MENU, the chat menu gets displayed twice.

I'll investigate this...  I've never seen it happen.  Do you have any more
input that you can provide?

-> Cosmetic  problem when  reading  messages, there  is no
-> space between the message TAG-LINE and the READ COMMAND
-> PROMPT; EXAMPLE:
->
->  * The New York Running Board*718-5191791/HST*654-1349/DS*
->  * PostLink(tm) v1.05  RUNNINGB (#3) : RelayNet(tm)           <---
-> (118 min left) -> (H)elp, (#) (+/-) (RE)ply, (EDIT), command? <---

This is CORRECT behavior.  It is *not* a cosmetic problem.

-> Note that this does not happen all the time, only in certain instances.

That is correct.  And to be more precise:  It ONLY HAPPENS when an "extra blank
line" would have caused a "more?" prompt to occur.

  Here is the OLD way of doing things           Here is the NEW way
  ===================================           ===================
   Message Header                               Message Header
   Full Page of Message                         Full Page of Message
   Blank Line                                   End of Message Prompt
   More prompt
   End of Message Command prompt

It is even more noticeable if you clear the screen after a full page (locking
the header) because then you get nothing but a Header and an End of Message
prompt on the screen.

I hope you'll agree that the NEW way is *much* better.

                                         David W. Terry 

Date: 05-08-93 (11:32)              Number: 62430 of 63094 (Refer# 62423)
  To: DAVID BORAK
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I have not been able to free up memory segments that stop Qemm from giving
-> me a Exception #13 errors. It happens all the time now no matter what swaps.

If you can reliably duplicate this then please give me a voice call at
801-261-1686 ASAP!  If it is something that PCBoard is doing (and not the
software that you are running inside the shell) then we'll get it fixed right
away.

-> Another strange happening, every so often the main menu BRDM path changes.
-> Example: I logged on yesterday morning and when it came to the main menu
-> instead a error on path G:\pcb\gen\brdm not found. I have pcboard located on
-> J: drive, and the pcboard.dat file says: J:\pcb\gen\brdm.

I hate to say this but...  I *seriously* doubt that the software is doing this
on its own.  Please investigate further.  I think you'll find a more logical
answer somewhere on your system or the way you are doing things.

-> Doors do not work on 15.0 /M using Comm-drv. Instead it sends a constant "*"
-> to the user. But the user can see the door. At least it enters the door.

We have plenty of /M customers where the doors DO work.  Please investigate
further.  Perhaps something else changed in the process.  There is a logical
explanation in there somewhere because PCBoard code does not affect the
behavior of the doors that run under it.

Let me know the results of your investigation into these matters.   And *do*
call voice if you can reliably duplicate the exception errors.

                                         David W. Terry 

Date: 05-08-93 (09:40)              Number: 62431 of 63094 (Refer# NONE)
  To: ALL
From: VIC KASS
Subj: RoseMail/PCBoard 15.0    
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


   This morning we have posted new exectuables for RoseMail (top
of Files Area 30) on Rose Media BBS in the !RM210-1.ZIP and
!RM210-2.ZIP files. This upgrade makes RoseMail fully compliant
with PCBoard 15.0 for those Sysops running the current wide beta
of PCBoard including the /M version. We will be uploading these two
files to the Salt Air Beta Conference Upload Area later today.

   You will find a new Flag (#19) in the RoseMail Manager, (RM.EXE),
Conference Data section, which will permit you to force RoseMail to
utilize the OLDINDEX methodology for your message bases. This is
particularly useful for those of you running older mail doors, most of
which do not support the new message indexing of PCB 15.0. For example,
if you carry RIME, you should set Flag 19 in RM for all your RIME
Conferences. If all these Conferences are in one block, you can set
the Flag with one command sequence using the Ctrl-S option.

   If you are running only RoseMail, you will be able to take advantage
of the new indexing in 15.0 which has an approximate 20% speed increase
in processing. If you have only RoseMail and Postlink, you would leave
Flag 19 'unset' for all your Conferences except RIME. If any of your
Conferences are accessible by other older mail doors which do not
support the new indexing, all these Conferences should have 19 set.
If you are using only the RoseMail door, do not use the 15.0
envirnment setting for OLDINDEX as this forces PCB to use the old 14.5
indexing. RoseMail is intelligent enough to figure which indexing
scheme is required and whether you are still using 14.5 PCB.

   For those of you that missed our post from yesterday, check the
RoseMail Conference for details on our third party developer information
on RoseNet formats. Now third party software developers can access
the exploding RoseNet World.

                Regards .......... Vic.

 * !RRRRRRRrrrrrrrr - RRev up with RoseReader!
---
  RoseReader 2.10 P001001

Date: 05-08-93 (11:37)              Number: 62432 of 63094 (Refer# 62419)
  To: LLOYD OSTERYOUNG
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (20:00)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> But....  did you install the Password PSA before making this test?

-> What is the Password PSA?

I guess that answers the question!  <g>

To save me some typing (I typed it once already) let me just give you the
pieces of the WHATSNEW file that you missed:

         PCBoard Supported Allocations (PSAs).  These are similar to the
         Third Party Allocations (TPAs) which are data areas reserved inside
         the USERS.INF file for Third Party Applications to use.  The PSAs are
         directly supported by PCBoard in PCBSM.  More so than are TPAs which
         are simply allocations.  A PSA is different in that not only is the
         space allocated, but PCBoard and PCBSM actually use the space.  The
         allocations implemented in version 15.0 are the following:

              Alias Support
              Full Address Support
              Password Changing Support
              Verification Support
              Caller Statistics Support

         Installation of a PSA is similar to installing a TPA.  From the
         Users Info File Maintenance menu option of PCBSM, you select "Add
         PCBoard Supported Allocations" and then pick which one you want to
         install.  You can install any or all of them, or none of them.

         If a PSA is installed, then PCBSM will show it when editing the
         Users File.  To get to the PSA screen simply press the F2 function
         key to rotate views (Short Form, Long Form, Conference Form, then
         the PSA Forms, one for each PSA installed).

         ....

         Password-Changing Support in both PCBoard and PCBSM.  This is another
         PSA (see above) and requires that you first install it via PCBSM.

         Installation requires that you first run PCBSM, select "User Info File
         Maintenance", then select "Add PCBoard Supported Allocations", then
         select "Add Password-Changing Support".

         Once installed, PCBoard will keep track of when your callers change
         their password (the last date changed), the number of times they have
         changed it, and the last three passwords used.  It will prevent them
         from selecting any of the previously used passwords.  You can view
         this information from PCBSM's Users File Editor.

         An additional field in the Password Support is an expiration date.
         You can set this date to force a caller to change the password as of
         that date.

         In addition, a setting is provided in PCBSetup : Configuration
         Options : Limits for the number of days between FORCED password
         changes.  If this setting is non-zero then PCBoard will require the
         caller to change the password when logging in after the expiration
         date of the password.

         New callers to the system, after the PSA is installed, will have the
         Login Date in the "Last Change Date" field.  And if a "forced change"
         period is specified in PCBSetup then the expiration date will be that
         many days from the caller's first logon date.

         You can warn the caller of the up coming need to change the password
         by setting the number of warning days to some value larger than zero.
         PCBoard will then display a PCBTEXT record informing the caller of the
         need to change the password.  This PCBTEXT record, like most PCBTEXT
         records, could be modified to run a PPL program.  This PPL program
         could be written to verify if the caller is "live" or "automated" and,
         if making an automated mail run, the program could write the user a
         message that might then be included in the packet the caller is about
         to download.  (NOTE:  A sample PPL is posted as PWRDWARN.ZIP)

         Setting the callers expiration date to a date prior to the current
         date effectively forces the caller to choose a new password on the
         next call.  Setting the expiration date to a date far into the future
         effectively disables the expiration feature.

         NOTE:  Callers who call in using automated systems MAY NOT BE AWARE
         of this change and may waste several calls before noticing that the
         reason they cannot get their mail is because they need to update their
         password.  You may want to use this feature sparingly.  (set the
         Number of DAYS to Forced Password Change to either 0 or to a high
         number, and perhaps set the number of warning days high just to give
         the caller a chance to see the warning in a "live" call sometime
         prior to the password's expiration date).

-> Another possible bug popped up with the 5/6/93 Beta and it showed on my user
-> log as follows
->      (L:\PCB\TEMP\MSG.$$$) is missing
-> Can't find what caused this, any ideas?

Ignore this.  I'll remove the message later.  The error message is bogus.

                                         David W. Terry 

Date: 05-08-93 (11:57)              Number: 62435 of 63094 (Refer# 62357)
  To: JIM HOLLOWAY
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (14:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Next I wanted to associate a file to a message, like telling everyone to
-> download the newest version of PKZIP and I read through the docs and could
-> not find the procedures on how to do it

Looks like it was left out of the WHATSNEW file.  I'll add it in as follows:

         - File attachments (1 per message).

|          File attachments are added to a message by typing "SA" to Save with
|          Attachment instead of typing "S" to save.

The vertical bars highly the changes.
                                         David W. Terry 

Date: 05-08-93 (11:58)              Number: 62436 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: TYLER MYERS
Subj: BETA report              
Read: 05-08-93 (12:33)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        


Beta Copy Date:  05-04-1993 13:25

Problem:  The DOS - Busy from the call waiting screen's password is
           faulty and can be bypassed.

Notes:  First you must know that this appears only to happen on
         nodes with modems attached.  Local nodes are fine.

Configuration:

                           SysOps Name: Tyler
                        Local Password: ###
Require Local Password to Exit PCBoard: Y
                         Use Real Name: Y

Make It Happen:  1.  Press enter on DOS - Busy
                 2.  When it asks for password press enter
                 3.  Then press ESC right after you press enter,
                      and it should then put you at the DOS
                      prompt.

On an HST modem you must press ESC before the modem says OK for
the second time, or PCB will only ask you for the PW again.  I
don't know if this is isolated only to USR modems or not.

Let me know the outcome or if there is something i'm doing wrong
here.

Correction:  By doing the above on ANY of the call waiting options
              that require a password you can exit to DOS.  Even if
              the modem is not taken off hook.

Note:  If the modem is not taken off hook you must press ESC quicker.
        Also everything appears to work fine on local nodes, with no
        modems attached.

Hope this helps...

            Tyler Myers 
       SysOp, The Radio Wave BBS
RIME(tm) Routable ->RADIOWAVE and ->1478

Date: 05-08-93 (12:07)              Number: 62437 of 63094 (Refer# 62364)
  To: JIM THOMPSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> POSSIBLE BUG #1:
->
-> Trying to run system diagnostics produces the following results:

PCBDIAG has not yet been updated.  Please hold off on using/testing/reporting
on it until after we post it.  Thanks.

-> POSSIBLE BUG #2:
->
-> Trying to use the 'W'rite User Info Command.
->
-> the "W"rite User Info command doesn't work for me as SysOp

It sounds like you have gone into the PWRD editor and answered 'Y' in the
column for Multiple Logins.  This is NOT a setting for sysops - it is for
setting up Demo Accounts where you want multiple users to be able to access the
system under the same name.

From the WHATSNEW file:

         The PWRD file now has a setting that controls, on a security level
         basis, whether or not an account can be used by multiple callers
         simultaneiously on a multi-node system.

         Answering YES to "Multiple Logins" means that more than one caller
         can be online using the same user-id without getting the "Name
         already in use on another node" message.

         This setting allows you to establish one or more accounts that can be
         used as DEMO accounts.  That is, accounts where you can hand out the
         user-id and password and allow more than one user to be online at the
         same time utilizing that user-id.

         ....

         3) Users of such accounts will be unable to use the (W)rite User
            Info command.  This avoids the possibility that someone might,
            either accidently or maliciously, change the password on the
            account thus stopping anyone else from using the multiple user
            account.  It also prevents the user from changing the city/state
            information which might, again either accidently or maliciously,
            be changed to something that is not desired by the sysop for that
            account.

-> POSSIBLE BUG #3:
->
-> I have a user that can not upload using any protocol (internal or external)
-> on Node 1 (Hayes Accura 14.4 modem/fax).  Nothing has changed from what I
-> can tell, except in the Modem Configuration for PCB v15.0 beta, the old
-> "Hayes V Series Modem" is no longer listed.  Could that have an impact?

Nope.  That setting does not affect the ability to transfer files.

My only guess here is that either the modem needs to be RESET (run PCBModem) or
else his own modem is perhaps not set up correctly.

Most of these kinds of problems are flow control problems.  Hence the need to
ensure proper setup for the modem.

-> The user is using a Intel 14.4 modem.  On Node 2 (Intel 14.4) the same user
-> does 'not' have any problems uploading.

That tends to point more to it being your modem that needs to be reset then.
Run PCBModem and then report back on the status of this report.

                                         David W. Terry 

Date: 05-08-93 (12:11)              Number: 62438 of 63094 (Refer# 62369)
  To: JAMES JONES
From: DAVID TERRY
Subj: Beta Report              
Read: 05-10-93 (05:45)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Local file attachments don't copy the uploaded file to the specified
-> directory.  In fact, I can't see where it copies it anywhere. (I did a
-> Norton's FileFind on all drives

Of course....  when you used Norton's what FILENAME did you look for?  My guess
is you looked for the wrong filename.

File Attachments are _NOT_ stored under their original filenames.

If you upload MYFILE.ZIP it will be stored in the File Attachment directory as
MYFILE.000 (a subsequent upload of a similar named file might be stored in the
same location as MYFILE.001 and so on).

-> I manually copied USERS.ZIP into the D:\ATTACH subdirectory, and then tried
-> again, and it was able to find the file.  It did rename it to USERS.000,
-> though.

USERS.ZIP was wrong.  The file that you uploaded (as an attachment) is the
USERS.000 file that DID show up.

As you can see, it IS, in fact, working since the file USERS.000 showed up
right were it was supposed to be.

-> 2.  The printing of the users file is off in PCBSM.

I'll check into this.

-> 3.  A print instead of purge of the user file duplicates the same problem as
-> #2 above.  All users have their PSA information printed with the information
-> of the user #1.

And this too.
                                         David W. Terry 

Date: 05-08-93 (12:23)              Number: 62443 of 63094 (Refer# 62392)
  To: RAY SULICH
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (07:30)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> This one happens everytime and is very minor.  When a return reciept is
-> requests and generated the reciept looks like this (at least the part that
-> is messed up looks like)
->
-> Was Received/re05-08-93 00:26
->
-> I think to should read
->
-> Was Received/read 05-08-93 00:26

Please recreate your PCBTEXT file.  Delete (or rename) your existing PCBTEXT
and use MKPCBTXT.EXE to create a new one.

Then try your test again.  (entering a message with RR, saving it, reading it,
and later finding the return receipt)  Then report back on the status of the
above report.

-> Also the time is way out in left field.  It should have been 18:46 This
-> message was generated in the main conf.

See if this is also affect.  Also, remember that the date/time shown is the
date/time when the RECEIVER of the message received the message.

If you still have a problem, please present a complete capture file showing the
message that was received, together with the return receipt message.

                                         David W. Terry 

Date: 05-08-93 (12:25)              Number: 62444 of 63094 (Refer# 62442)
  To: BRUCE HAEFEMEYER
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (13:15)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> At this time I am unable to get the QWK function to work. I have created the
-> required PCBQWK.BAT file. The files 000.NDX, 002.NDX, MESSAGES.DAT and
-> CONTROL.DAT are being created in my defined 'temp work files directory'
-> (D:\PCB\PCBCAP) but board always returns an "Error Compressing File" message
-> and aborts restoring the read pointers.

Check the CONTENTS of your PCBQWK.BAT file.  The commands in there must be
valid for your system.

Example:  if you have renamed PKZIP.EXE to ZIP.EXE then you need to make the
appropriate change to the PCBQWK.BAT file.

Suggestion for further investigation on your end:

        - Put ECHO ON at the top of the batch file
        - Put PAUSE at the bottom of the batch file
        - Now sit at the local screen and watch it run

The above should provide enlightening.
                                         David W. Terry 

Date: 05-08-93 (12:29)              Number: 62445 of 63094 (Refer# 62433)
  To: BOB JACOBSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (15:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Neither of my existing mail doors, Markmail or Qmail are functioning
-> properly with the new code.  They are both refusing to honor the PCBoard
-> pointers and are skipping mail.

It sounds to me like you may not be set up correctly.

You _MUST_ tell PCBoard to maintain old indexes in order for these OLD pieces
of software to work.

From the README.1ST file:

 9) If you are using any kind of NETMAIL or offline mail reader - programs
    which access the message base - then you should edit your BOARD.BAT file
    and change the "SET PCB=" line.  Add to it the word /OLDINDEX.

    This change tells PCBoard to maintain both the old and the new index
    files.  If you are not using any kind of offline mail reader, if you have
    chosen to use only PCBoard v15.0's built-in QWK capability, if you are
    not using any netmail software, then you do NOT need to use /OLDINDEX and
    can save disk space by not using it.

Additionally, you need to modify your PCBPACK command adding the word /OLDINDEX
on the command line so that PCBPACK will keep the old index file up to date as
well.

-> I have user.sys set to 'o' for both doors, and I have the SET PCB =
-> /OLDINDEX in my board.bat for all my nodes.

Run PCBPACK /AREA:ALL /INDEX /OLDINDEX right now, before you do anything else.

With that taken care of, now RE-perform your tests with the mail doors.  I am
pretty positive that you will find that they will work CORRECTLY.

Reason?  Same input in - same input out.

By maintaining the old index files you have the same input.  The same programs,
when run on the same input, will generate the same output.

                                         David W. Terry 

Date: 05-08-93 (12:51)              Number: 62449 of 63094 (Refer# 62321)
  To: ROB KITTREDGE
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (16:03)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Found another small problem when using the /LOCALON switch when exiting and
-> returning from a door.  When I return from a door in the local mode, PCBoard
-> reduces my viewable screen from 24 lines to 23.  So I get "More?" prompts a
-> line earlier than should be.  Of course, I get the full 24 lines before I
-> load the door.

I cannot find any way to duplicate this one.  I do the following:

1) Run PCBOARD /LOCALON
2) Log in
3) View a file with more than 1 screen's worth of information
4) Note that the entire screen is filled before the "more?" prompt occurs
5) Note also that there is only 1 status line
6) Run QMAIL4
7) Quit back to PCBoard
8) View that same file
9) Screen still fills completely before the "more?" prompt appears
10) And there is still only 1 status line

I get the same "picture" on my screen viewing the file both before and after
the QMAIL door.

Please re-test on your end and, if you still have a problem, please provide
exact details as to the method of testing (similar to the way I have stepped
you through my testing up above).
                                         David W. Terry 

Date: 05-08-93 (12:59)              Number: 62450 of 63094 (Refer# 62343)
  To: MARC MEDOW
From: DAVID TERRY
Subj: Beta Bug                 
Read: 05-08-93 (16:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Found a bug today. A user uploaded 2 unannounced files to conference 3. Both
-> files had FILE_DIZ info so the system didn't ask for the description, which
-> is right. Only problem is, the files were put into the main board instead of
-> conference 3.

I could not duplicate this report.

Please... before sending a bug report, please try to duplicate it YOURSELF so
that you will be able to provide any/all pertinent details in order to help us
to quickly duplicate your reports.  (this is really a plea for help from
everyone that is providing reports)

My testing was as follows:

1) I joined conference 3 on this system.
2) I told PCBoard I was uploading DUMMY and gave it a dummy description
3) I really uploaded MYTEST.ZIP.
4) MYTEST.ZIP showed up in the Upload Directory for Conference #3.  Right
   where it was supposed to be.

Testing #2:

1) While still in conference 3 on this system.
2) I told PCBoard I was uploading DUMMY and gave it a dummy description
   this time with a backslash at the start of it.
3) I really uploaded MYTEST2.ZIP.
4) MYTEST2.ZIP showed up in the PRIVATE Upload Directory for conference #3

You might not have know about or expected what happened in scenario #2.  If the
FIRST DESCRIBED FILE is a private file, then all UNANNOUNCED uploads
(containing FILE_ID.DIZ files) will ALSO become private uploads.

In neither case, however, did the upload land in the Main Board directory.

Having it land there would be rather difficult anyway because it would mean
that PCBoard would have to go out and read the CNAMES file to pick up the
record for the main board.  And the upload processor just doesn't do that - it
never reads the cnames file - it just uses the "current settings" based on
where the user is currently located in the system.

Please investigate your report and provide feedback as to the status of your
report.  If you can duplicate it I will need to know exactly, step by step,
what is needed to reproduce your report.

                                         David W. Terry 

Date: 05-08-93 (14:37)              Number: 62452 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: BOB KEYSER
Subj: BETA report              
Read: 05-11-93 (09:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSETUP.EXE - 05-04-93                                


Dave: I uploaded a file called KEYSER.ZIP which contains a copy of my
PCBoard.dat and a copy of the Event.dat. If you load the event.dat
through

Date: 05-08-93 (15:06)              Number: 62454 of 63094 (Refer# 62326)
  To: DAVID TERRY
From: MSI-MICRO SYSTEMS
Subj: Possible problem??       
Read: 05-08-93 (15:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Has anyone had any trouble with the Attach File to Message function?
-> I
-> What do you SEE when you try?  Tell me *exactly* what you TYPE and
-> *exactly* what you see after doing it.  (a capture file would be
-> helpful)

Ok, I will see if I can get a capture file.  When I try to FLAG or View
the file, it says it can't find it in the attach directory.  When I
upload the file, it goes through ZIPLAB just like any other upload, but
I can't find it anywhere on my system ( even with a different
extension.)

I'll see if I can find the caller log entries, and turn the log on
during testing for you.

Thanks Dave

Date: 05-08-93 (15:25)              Number: 62457 of 63094 (Refer# 62453)
  To: BOB JACOBSON
From: DAVID TERRY
Subj: Missing/Corrupted Mail   
Read: 05-08-93 (22:24)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Take a look at the whopping difference in scans and
-> the fact that neither door is able to scan correctly.

Run PCBPACK /AREA:ALL /INDEX /OLDINDEX and the above should clear itself right
up.
                                         David W. Terry 

Date: 05-08-93 (15:26)              Number: 62458 of 63094 (Refer# 62455)
  To: BOB JACOBSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (22:37)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Are you sure this in the documentation anywhere, David?

To be honest, I'm not really sure...   anyway, give it a try and then report
back on your findings.
                                         David W. Terry 

Date: 05-08-93 (15:37)              Number: 62460 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: PCBPACK and /OLDINDEX    
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

I've looked...   and I couldn't find this information anywhere (except in old
messages) so here are the changes that I am adding to the WHATSNEW file:

|        - Changing the PCB= environment setting, adding /OLDINDEX to it,
|          will instruct PCBoard to maintain old MSGS.NDX files across ALL of
|          your conferences regardless of the individual conference settings.
|
|        - PCBPACK will maintain old indexes by typing /OLDINDEX on the
|          command line with the rest of your commands.  For example, you
|          might use the command:  PCBPACK /AREA:ALL /DAYS:30 /OLDINDEX
|
|        WARNING!  If you are using a Mail Door or any netmail software which
|        accesses your message bases using the old index files, then you MUST
|        configure your system to maintain the old index files.  It is
|        recommended that you use SET PCB=/OLDINDEX and that you add /OLDINDEX
|        on your PCBPACK command line in your event batch files.

Everyone check out your EVENT batch files and make sure you are set up properly
to run PCBPACK with /OLDINDEX if your system needs it (per above indications).

                                         David W. Terry 

Date: 05-08-93 (16:02)              Number: 62462 of 63094 (Refer# NONE)
  To: ALL
From: JOHN KERR
Subj: Usage Of Zip-Lab         
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

 Help..

 Till I upgraded to beta 15.x, I have been running ZIP-LAB to test &
clean all uploads to the system.  I now find that when used with 15, it
still tests the uploads, but it does not insert FILE_ID.DIZ descriptions
into the description of the DIR file but rather inserts a message of
"Contains FILE_ID.DIZ"

 Anyone have any ideas on why this might be happening??

Thanks..John

Date: 05-08-93 (16:05)              Number: 62463 of 63094 (Refer# 62351)
  To: DAVID BAUER
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (00:03)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I think I found a bug in the pcboard.exe In chat mode on a 10 node system I
-> had people calling and entering the chat and found that a user drop carrier
-> and the board will not reset it just kept saying NO CARRIER in a endless
-> loop I was not home at the time but when I rebooted the board it look like
-> it was that way for about 5 hours, I then called my other node and I drop
-> (hung up) in the chat mode and it did the same thing, give it a try I think
-> it will happen to you to...

I dialed into the system.  Went into group chat.  Wrote one line of text.  Then
pressed ALT-H.

The PCBoard node I was logged into immediately recycled.

Can you re-duplicate it on your system and get, for me, a step-by-step list of
instructions necessary to duplicate your report?  Thanks.

                                         David W. Terry 

Date: 05-08-93 (16:10)              Number: 62464 of 63094 (Refer# 62462)
  To: JOHN KERR
From: DAVID TERRY
Subj: Usage Of Zip-Lab         
Read: 05-09-93 (07:20)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> it does not insert FILE_ID.DIZ descriptions into the description of the DIR
-> file but rather inserts a message of "Contains FILE_ID.DIZ"

Just in the FYI category:

When PCBoard auto-detects a FILE_ID.DIZ file in an UNANNOUNCED upload, it
creates a "dummy description" for the file that says simply "Contains
FILE_ID.DIZ" and then passes this dummy description out to the Upload Tester.

This process is IDENTICAL to what would occur if the caller had announced the
file and typed "Contains FILE_ID.DIZ" in as the description.

So, then, the Upload Testing of the file should be identical too.

You might want to check for whatever settings are used to tell ZipLab to
process FILE_ID.DIZ files to see if something is set wrong there.  It seems
that if it is going to process FILE_ID.DIZ files it should process them
regardless of whether or not the uploaded file was "announced" and regardless
of what the "description" is that was passed to it.

You also might want to contact the author of ZipLab for help in this area.

                                         David W. Terry 

Date: 05-08-93 (16:18)              Number: 62466 of 63094 (Refer# 62386)
  To: ARTHUR MOL
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (01:07)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> History repeats itself. Remember that there was a bug in the devbeta PCboard
-> where the multilingual prompts were not restored correctly after using a
-> door? Well, it's back again!
->
-> In Dutch, the "Y" prompt is "J".. When a door has been used, PCBoard will
-> only accept "Y" for an answer and not "J" when the user has selected the
-> Dutch language..

Well...  I have gone in and out of several doors and I cannot duplicate your
report.

The one idea that I did come up with was this:

The information which PCBoard stores, in the pcboard.sys file, that lets it
determine what language was in use (upon reloading from the door) is kept in
the pcboard.sys file at offset 135.

If a DOOR program were to truncate the pcboard.sys file to just 128 bytes, or
create a new pcboard.sys file copying only the first 128 bytes, or somehow mess
with the byte at offset 135, then the DOOR could *cause* what you described.

A DOOR program which properly leaves the pcboard.sys file intact, however, will
not harm the language selection.

Could you investigate your report further on your system to determine:

1) If ALL doors are doing this.
2) If only SOME doors are doing this.  (which ones?)
3) If the problem is due to pcboard.sys manipulation (see above).
4) Or if there is any other cause that you might be able to detect.

Let me know the results of your investigation.

                                         David W. Terry 

Date: 05-08-93 (16:30)              Number: 62467 of 63094 (Refer# 62465)
  To: ROB KITTREDGE
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (16:53)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I load PCBoard with /LOCALON, view directory 2 (more than 1 screenfull), get
-> the more prompt in the right place.  Then I open QMail4, and quit to
-> PCBoard.  Pcboard comes up and I view dir 2 again. This time the more prompt
-> is on line 23 instead of 24 where it was before I loaded the door.
->
-> It's as simple as that

Well...  it turns out not to be "as simple as that" ...  but I managed to
discover a way to duplicate your report.  What I did was this:

1) run PCBOARD /LOCALON
2) open the QMAIL4 door
3) shell out and edit my board.bat file to remove the /LOCALON parameter
4) quit back to PCBoard
5) now it is showing only 23 lines instead of 24

The key here is that PCBoard was started with a /LOCALON switch and that the
/LOCALON switch was NOT used upon returning to PCBoard.

You probably do not manually edit your files the way I described up above the
whatever you do, the effect is probably the same, because as long as I kept the
/LOCALON switch there it worked fine for me.

Anyway, with that discovery I have fixed the problem.

As you can see...  guessing how people use our software is not easy.  :-)

                                         David W. Terry 

Date: 05-08-93 (16:35)              Number: 62469 of 63094 (Refer# 62468)
  To: KRIS STEINWENDER
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (16:36)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> It also when you have the SysOp page and END in the PCBSETUP, it ignores the
-> callwaiting screen page sysop on/off function.

The above does not make any sense to me.  Please rephrase.

-> My code doesn't want to run teh EVENT's.

Carefully read and re-read the EVENT.DOC information.  Nearly all event
problems are CONFIGURATION related.  Once set up correctly they work.

If you STILL have a problem, then you will need to supply a LOT more
information than just "they don't work".  Please upload your EVENT.DAT file and
as well as your event files and DESCRIBE IN DETAIL exactly what you see
happening on your system.

Details are extremely important in order for us to provide you any assistance.

                                         David W. Terry 

Date: 05-08-93 (16:39)              Number: 62471 of 63094 (Refer# 62470)
  To: BRUCE HAEFEMEYER
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (19:58)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

->     (D:\PCB\PCBCAP\NOTEBK13.ZIP) is missing!
->
-> The file that is alledgedly missing is the users upload.

Ignore this message, it is BOGUS and will be fixed in a later release.

-> Uploads are supposed to go to N:\PCB\UPP not the indicated path

That is okay.  Don't worry about the message - it is bogus.

-> After the upload PCBTEST didn't run at all, rather it returned to the
-> prompt.

Check your setup.  There are only three possible reasons for not running
PCBTEST.BAT:

1) PCBSetup has "Verify Uploaded Files" set to NO.
2) You have insufficient memory to shell out to PCBTEST.BAT.
3) PCBTEST.BAT does not exist.

No fair guessing.  I am requesting that you EXAMINE the above before you reply.

->     Insufficient Memory for Operation DESC BUFFER (0/32256)

By the way, I don't know whether or not this will be a 'key' to the PCBTEST
operation or not.  It *could* be.  Anyway, check your setting in PCBSetup for
the number of lines in an upload description.  It might be set to ZERO.  Make
sure it is greater than 0 or the above will occur.

                                         David W. Terry 

Date: 05-08-93 (17:40)              Number: 62476 of 63094 (Refer# 62373)
  To: DON REID
From: SCOTT ROBISON
Subj: PCBEdit Version 1.00 Wide
Read: 05-10-93 (01:57)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Scott, I know I'm rather thick on a lot of things. However, I still have a
-> concern with regard to the colors *after* the end of a sentence. I use the
-> ATCLREOL@ after EVERY sentence. Seems to me there has to be an easier way to
-> accomplish this. What am I overlooking? Thanks!

You can change color and do a @cls@, that's about the only other option, and
*THAT* will change the entire screen color.  Other than that you've picked the
most efficient way to do it possible.

   Scott Robison

Date: 05-08-93 (17:43)              Number: 62477 of 63094 (Refer# 62383)
  To: SILVERADO BBS
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-09-93 (05:20)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> First of all; let me congratulate you for a GREAT software, got the PPLC
-> today. Qouple of questions; Is it anyway to increase the buffersize for the
-> KBDSTUFF. I would like to stuff more into the buffer befor it start chopping
-> of the first charachter that is stuffed into the buffer.

Thanks for the compliment . . . Sorry, you can't change the size of the buffer
used with KBDSTUFF as it is built into PCBoard.  However, you can stuff the
contents of a file by giving the filename to stuff to the KBDFILE statement
(similar to the PCBSTUFF.KBD file when coming back from a DOOR).

-> 2. Is it anyway to do a shell run from a PPL program. Like 'SYSTEM' in C. I
-> want to make my own message base. but then I need to store the messages in a
-> xbase format or something like that. Any ideas????

Try the SHELL statement.  Documented in PPL.DOC.

   Scott Robison

Date: 05-08-93 (17:51)              Number: 62482 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: FRANK JACOBBERGER
Subj: BETA report              
Read: 05-10-93 (06:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93 06:08:00                        


David,

Just a one time happening. I was in a FULL screen DOS window under OS/2
2.1 and a caller logged in to PCBOARD. Upon entering my FIDO Genealogy
conference (1500 messages active), he was able to read selected messages,
BTW the messsage base for that echo was just packed and I had looked at every
message within PCBOARD /LOCALON mode (no problem). After the USER
read about 10 messages, OS/2 2.1 HALTED the application.

I couldn't make out the error. Everything was normal upon restarting
PCBOARD. I was viewing a large ZIP file with the command PKUNZIP -v,
at the time of the crash. That may have caused it to happen. I've
loaded about five PPLs', so I'll try changing the OVLSIZE to 16 as I
saw previously mentioned.

Just FYI.

Thanks,

Frank :)

Date: 05-08-93 (19:13)              Number: 62488 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: JEFF WOODS
Subj: BETA report              
Read: 05-10-93 (06:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-03-93                                 


David:

  PCboard currently issues the following sequence prior to an ASCII
download:

[CR][LF][ESC][0mASCII Text Starts here

The RIP specifications indicate that a RIP sequence can only begin in
the first column, and the way those specs are now (I asked Jeff Reeder
this yesterday), ANSI sequences WILL trash this -- the ESC[0m places the
"Rip cursor" off the first "column" and the first line of a RIP file
being ASCII downloaded is lost (or more specifically, displayed in the
clear.

You will get the same effect and avoid this problem if PCBoard were to
issue the sequence:

[ESC][0m[CR][LF]

The above will allow the first line of a RIP file to be interpretted by
an ANSI/RIP parser that is coded to specs.

Thanks!

Jeff

Date: 05-08-93 (20:01)              Number: 62490 of 63094 (Refer# 62471)
  To: DAVID TERRY
From: BRUCE HAEFEMEYER
Subj: BETA report              
Read: 05-10-93 (06:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 1) PCBSetup has "Verify Uploaded Files" set to NO.
-> 2) You have insufficient memory to shell out to PCBTEST.BAT.
-> 3) PCBTEST.BAT does not exist.

-> operation or not.  It *could* be.  Anyway, check your setting in
-> PCBSetup for the number of lines in an upload description.  It might
-> be set to ZERO.  Make

David,
  One, two and three are not the problem. For some reason I ended up
with 0,3,8 and 15 lines of text in the UL description depending on the
node I checked. Not sure how that happened but you suggestion was right
on.

Thanks much for the quick reply,
Bruce Haefemeyer

Date: 05-08-93 (20:27)              Number: 62493 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ED LUCAS
Subj: BETA report              
Read: 05-11-93 (10:03)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBPACK.EXE - 05-04-93 13:08:00                        


This isn't a bug report...correct me if wrong. PCBpack is creating
temporary files. If one tries to run PCBPack on message bases in the
same path from different nodes, then there will be a problem? A lot of
us are now dealing with 1,000s of conferences and it would be nice if we
could pack different ranges of confs from different nodes without a
conflict.

Cheers!

Date: 05-08-93 (20:49)              Number: 62495 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ANDY KEEVES
Subj: BETA report              
Read: 05-10-93 (06:28)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-06-93                                 



David,

        The problem I mentioned to Louis and that Mark Rapp reported, relating
to PCB Zmodem..   Well, I just found a node here in PCBoard stuck..  The fella
was downloading a file using "F" (internal).  It was sitting there with the bar
showing 100% completion and it has been there for well over an hour.  The
connection was live!   The reason I associated it with the ZModem problem is
because  I recall that ZModem transfers, when they have this problem, show a
100% completion BUT the total bytes transferred is LESS than the bytes in the
file.  This was the case with the stuck transfer as well - the bytes
transferred were some 5 or so kb less than the 300+ kb file size.

        Checking the caller log, there are a large number of lines showing
"FLOW TIMEOUT".  Well..  the way I figure it, no matter what the problem was,
the transfer should have been aborted LONG before I found it..  :)

        And no, I cannot make this happen when I want to, sorry..  :(

Date: 05-08-93 (22:20)              Number: 62503 of 63094 (Refer# 62473)
  To: FRED WEHNER
From: DAVID TERRY
Subj: BETA report              
Read: 05-09-93 (15:55)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Downloads are working just fine, but uploads show an error message:
-> " work\MSG2.$$$ is missing  "
->
-> Followed by a message that says successful insertion.  Why the error
-> message, and what does it mean?

Everyone.  Please....  ignore this message.  It is a bogus message.  I'll take
care of it in a future release.  For now, please, just ignore it.

-> How does one use the 'broadcast command'...whats the syntax?

BR # TEXT

Where # is the node number you want to broadcast.

                                          David W. Terry 

Date: 05-08-93 (22:23)              Number: 62504 of 63094 (Refer# 62483)
  To: BOB NEAL
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Anyway - with LONG message headers the READ: YES/NO is screwed up, actually
-> shows SUBJECT a second time but not lined up and in another contrasting
-> color. May have been fixed by now, will grab the latest beta to see. Thanks

Your PCBTEXT file is probably screwed up.

Try creating a brand new one.  Delete (or rename) your current PCBTEXT file and
use MKPCBTXT.EXE to create a new one.

Please report back on your findings after performing the above.

                                          David W. Terry 

Date: 05-08-93 (22:26)              Number: 62505 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: SCOTT BOERKE
Subj: BETA report              
Read: 05-10-93 (06:28)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93 18:08:00                        


Just a couple of minor problems I encountered at the call waiting
screen.  If you press F1 to exit to dos and you have local password to
Dos on and the screen is blank, it is asking for the password but you
cannot see it on the screen.  The screen blanker did not redisplay the
screen before it asked for the password. Very minor.

I also discovered that if you press F5 when it is asking for the local
password from any area of the call waiting screen and you have allow
local shell to DOS set to Y, the board will shell out to DOS.

Also when pressing the Escape key during the modem going offhook or when
the modem is recycling will exit out of the board bypassing the local
password question.  So if You select DOS-Busy and quickly press Escape
before it asks for the password it will drop or press enter for the
password and while the modem is recycling press escape it will drop to
DOS.

I have also seen a display problem when you select any option that will
ask for a local password and then press F4 or F7 for the caller alarm or
Page Bell a status line will appear at the bottom of the screen like a
caller is online.


                                                Scott

Date: 05-08-93 (22:28)              Number: 62507 of 63094 (Refer# 62487)
  To: JIM LOCKHART
From: DAVID TERRY
Subj: beta report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am running your beta code dated 5-7-93 18:08 and cannot get my node #2 (of
-> 2) to send data out to the user once it answers the phone. (Node 1 works
-> fine with the new code.)

What kind of modem (brand and model) is on node 2?

Have you re-run PCBModem to see if that has any effect?

What selection do you pick in PCBModem when you use it?

Does your modem return a "CONNECT 14400" type of message or a "CONNECT 38400"
type of message?  (the former being the DCE speed, the latter being the DTE
speed)

Let me know the answers to all of the above questions and I'll try to help you
out.
                                          David W. Terry 

Date: 05-08-93 (22:32)              Number: 62508 of 63094 (Refer# 62492)
  To: ANDY KEEVES
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (00:55)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->       Clear the screen between each message? (Y)
->       Scroll multi-screen messages? (N)
->       Use long headers when reading messages? (Y)
->       Full Screen Editor Default: (Y)es, (N)o, (A)sk? (Y)
->       Set editor workspace default to 79 columns? (Y)
->
-> While reading mail in the ANSI graphics mode, the screen is cleared before
-> each message and the header is placed at the top of the screen, followed by
-> the body of the message, as expected.
->
-> However, pressing ALT-F and typing a file name to capture the
-> displayed messages alters this sequence.  Once ALT-F has been enabled, the
-> screen clear and sending the cursor to the home position are lost. The
-> messages simply scroll.  Turning ALT-F off returns to normal display
-> operations.

This is all "proper behavior".  As long as you are "capturing", either to disk
or to a file, the display of the message is changed so that the CAPTURE itself
will be "readable".  Since the capture will not be able to include "clear
screens" in the middle, PCBoard has to change to a method that will be captured
properly.
                                          David W. Terry 

Date: 05-08-93 (22:34)              Number: 62509 of 63094 (Refer# 62494)
  To: ED LUCAS
From: DAVID TERRY
Subj: BETA report              
Read: 05-08-93 (23:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Attempting to upload using G from local console a file named QWHT13.ZIP.
-> Pcboard informs me that QWHT13.DIR already exists. Is it just parsing the
-> name?

Everybody asked for the ability to protect against uploads REGARDLES of the
extension.

More commonly, they asked that FILENAME.ARJ not be allowed to be uploaded if
FILENAME.ZIP already exists.

Well, that is *exactly* what you just tried to do...  upload a file by the same
"root name" but with a different "extension" on the file.

Having Sysop Level you can then choose to:  Delete the file that was found,
Continue with the upload without deleting the original, or abort the upload.

-> If so, my allfiles.lst is blank.

The ALLFILES.LST file has nothing to do with this behavior...

                                          David W. Terry 

Date: 05-08-93 (22:37)              Number: 62510 of 63094 (Refer# 62458)
  To: DAVID TERRY
From: BOB JACOBSON
Subj: BETA report              
Read: 05-10-93 (06:29)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Are you sure this in the documentation anywhere, David?
->
-> To be honest, I'm not really sure...   anyway, give it a try and then
-> report back on your findings.

OK!  YES!  Setting the PCBPACK /OLDINDEX switch absolutely solved the
corruption and pointer problem, David.  And I did a grep of all the
files that you have and there is no mention of this in any of them, so I
suspect that there are going to be more people with this problem.  :-)

There is a switch shown if one types "pcbpack" without any parameters,
but it is not explained in the history or whatsnew docs at all, nor is
there any pointer to the parameter list as shown by typing the file
name.

Also, another question.  I used to be able to pack the user base from
command line by using pcbpack /users (or user). That switch no longer
seems to be available. What is the command line way to pack the userbase
please?

............Bob

Date: 05-08-93 (22:39)              Number: 62512 of 63094 (Refer# 62405)
  To: RICK DILORENZO
From: SCOTT ROBISON
Subj: vroom version            
Read: 05-10-93 (23:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> All versions of the code are now overlay versions.

-> Won't that mean PCBoard will be slower or something?  I don't have memory
-> problems at all so wouldn't mind using the regular NON-overlay version.
-> Want speed most of all.

Just a brief addendum to David's message.  I run a single node on a single
computer and don't multitask, so the memory requirements for my board are
negligable (as long as the program runs under a DOS 640K window -
DOS/DEVICE/TSRs).  So I was, for a while, running with 32 buffers (128K RAM).
I'm now only running with 24 buffers (96K RAM) because that is all the BETA
door supports and I was tired of running OVLSIZE.EXE after every download of
new code.  Basically, if you are not concerned about RAM, go as high as
possible to minimize swapping.

   Scott Robison

Date: 05-08-93 (22:45)              Number: 62514 of 63094 (Refer# 62500)
  To: TIM ELSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (03:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I've called it various names with the .000 node specific extention.

Do NOT put the extension inside of your EVENT.DAT file.  NO extensions belong
in there.

No extensions are even necessary.  They CAN BE USED, if desired, but none are
ever required.

Example:  You set up an event called MAINEVNT.  That is the name you type
inside your EVENT.DAT file:  "MAINEVNT"  Nothing more.

Now you create a file called "MAINEVNT" (nothing more than that) in your
\EVENTS directory (wherever you put that directory, check your setup to be
sure).

All nodes will run the "MAINEVNT" unless you create a NODE-SPECIFIC version of
your event.  Example:

        MAINEVNT.003    <--- node 3 runs this event
        MAINEVNT.005    <--- node 5 runs this event
        MAINEVNT        <--- all of the rest of the nodes default to this one

All of the above events are run at the SAME time with the only difference being
that nodes 3 and 5 have node-specific event files.

See if the above information helps you out.  If not, leave a message to Louis
describing your complete setup (upload your event.bat file, etc) and tell him
exactly what you see happening on your system.

                                          David W. Terry 

Date: 05-08-93 (22:48)              Number: 62515 of 63094 (Refer# 62502)
  To: BILL ATHINEOS
From: DAVID TERRY
Subj: OTHER:  PCBOARDEXE 05-04-93
Read: 05-09-93 (19:00)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am having a problem with the feature QWK. When i try to download the mail
-> packet i get an error.
-> Error compressing file.
-> Capture aborted. Read pointers restored.
->
-> I did what it said in the doc but i can't seem to figure out why, any ideas?
-> I put the batch file in the pcb directory!

You but "the" batch file?  Do you mean PCBQWK.BAT?

If so, did you examine the contents of the PCBQWK.BAT file and verify that the
contents are VALID FOR YOUR SYSTEM?

In other words, PCBQWK.BAT calls a program called PKZIP.EXE in order to perform
compression.

If you have renamed PKZIP.EXE to ZIP.EXE then PCBQWK.BAT is going to FAIL and
you will get the message "error compressing file" just like you described.  In
which case, you need to edit PCBQWK.BAT and change it to say ZIP instead of
PKZIP.

So please take the time to look at the PCBQWK.BAT file and verify that its
contents are valid for your setup.
                                          David W. Terry 

Date: 05-08-93 (22:50)              Number: 62516 of 63094 (Refer# 62510)
  To: BOB JACOBSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Also, another question.  I used to be able to pack the user base from
-> command line by using pcbpack /users (or user). That switch no longer seems
-> to be available. What is the command line way to pack the userbase please?

Use PCBSM to pack your users file.  The command line switches are in your v14.5
manual.
                                          David W. Terry 

P.S.
Thanks for your follow-up report on the index problem.

Date: 05-08-93 (23:04)              Number: 62518 of 63094 (Refer# 62472)
  To: RAYMOND CLEMENTS
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-10-93 (06:32)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> If you get a chance would you or Scott check out the READLINE function in
-> PPL?  I have a PPE that stopped working as of the 05-06-93 version and still
-> doesn't work now.  I didn't do anything to it (at all, really).  I am using
-> a 16 instead of a 14 as my OVLSIZE setting, but I tried it again with the
-> size of 14 and it still didn't work.  Thanks for checking this out for me.

I'll check on things monday when I get in.  In the meantime, I've done some
things the past week that would affect that function if I didn't do them right,
and I know I fixed at least one bug last week.  Let me know if you still have
problems with code dated on or after 05-07-93.  Thanx . . .

   Scott Robison

Date: 05-08-93 (23:44)              Number: 62522 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: BARRY YOUNG
Subj: BETA report              
Read: 05-10-93 (06:33)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93 06:08:00                        


Just to let you know, that I'm NOT having a problem.
(Thought that you'd like to see these messages sometimes also!) <G>

I just set 15.0 this morning (started early at 4am) YAWN!!!

I'm having fun with it.

I 'did' note that when reading a bunch of messages in a conference, and
then I select (L)ast message to hit then end, and then (A)ll to continue
with the rest of the conferences, PCB starts over with the preceeding
conference. It doesn't come up with any messages tho, it was just
strange to see it start over from the preceeding conference. I'm sure
there's a reason that you guys are doing that.

It DOES seem slow switching from one conference to the next when R A is
going on. Possibly being beta code with debug stuff, or going thru both
indexes?

I found a NEWUSER type of ZIP file onboard this morning (here) in which
I've set up as a bulletin for the callers to see what is new for them
with this new code. I'm sure you guys are working on new help files also
(as time permits).

Keep up the great work!

Barry Young
System Support BBS

Date: 05-10-93 (06:35)              Number: 62529 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: CHARLES EVANS
Subj: BETA report              
Read: 05-11-93 (10:12)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBSETUP.EXE - 05-03-93                                


2)   I am unable to get any events to run.  When using PCBSETUP, I go to
the "EVENTS" section and get a message: "Error Opening File - File Not
Found   C:\PCB\MAIN\USERNET.XXX.  I have tried to run two events and get
nothing.  PCB doesn't seem to sense that any events are pending.  This
is manifested by the fact that on an "E" event, the board does no
suspension of activities preparatory to running the event -- whether a
caller is on-line of no caller is present.  Your guidance will be
appreciated.

Date: 05-09-93 (01:17)              Number: 62531 of 63094 (Refer# 62466)
  To: DAVID TERRY
From: ARTHUR MOL
Subj: BETA report              
Read: 05-10-93 (06:38)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 1) If ALL doors are doing this.
-> 2) If only SOME doors are doing this.  (which ones?)
-> 3) If the problem is due to pcboard.sys manipulation (see above). 4)
-> Or if there is any other cause that you might be able to detect.
-> Let me know the results of your investigation.

Well, first I must say that I didnt change or add any door. I don't have
a lot of doors running here.. Doors that are causing the problem are;

Qmail4 (03-01-93 release)

Rosemail (v2.00 / not the new 2.10 version installed yet)

Guts (ansi game)

Ehm.. even a door that I wrote myself which runs under doorway, is
causing it (while I don't even use the USERS.SYS file for that door).
Guts and the above door are shelled doors. With Qmail4 and Rosemail and
exit is performed. I will look into it further..

Arthur

Date: 05-09-93 (03:43)              Number: 62533 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: BOB KEYSER
Subj: BETA report              
Read: 05-11-93 (10:12)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSETUP.EXE - 05-04-93 00:55:00                       


Dave: I uploaded a file called KEYSER.ZIP which contains a copy of
my pcboard.dat and event.dat. Please look at the event.dat file and
see why it is saving my file dirs. If you load it into pcbsetup it
looks just fine - when you save it it is full of garbage from my file
dirs. You will have to use the list program to view whats in it.
Can't figure this one out --- Thanks

Date: 05-09-93 (04:29)              Number: 62536 of 63094 (Refer# 62501)
  To: TIM ELSON
From: JULIO DAVILA
Subj: event in pcboard 15.0    
Read: 05-10-93 (02:58)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Julio, if it's any consolation, I'm having the same problem. I feel
-> better seeing at least one other person having this problem<grin>.
-> Tim.

I found the answer...!!!
   you only delete the line that says if event.sys rename....etc..
   but you must leave the second one.....
                                                   julio

Date: 05-09-93 (05:55)              Number: 62539 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: KENN HYSLOP
Subj: BETA report              
Read: 05-10-93 (06:39)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-06-93 18:24:00                        


I'm having remarkably few problems with v15.0, considering the fact I'm
running 75 Doors at the moment. I haven't had a crash on the Board Doors
yet. I thought you might appreciate that news - I sure did!

I, too, am having problems getting the Event to work but since other
people have it working, I blame the documentation. It might be a bit
clearer.

The only problem I can report is The Verify Door - and it might be my
system. The first time I tried it with 15.0 in local mode, it locked up
my computer. I rebooted and it verified and put me at the Main Menu. The
second time, my system re-booted itself and I ended up verified, at the
Main menu. The third time, it worked fine - no problem.

Since that time, I've had a new person register via The Verify Door and
it worked OK.

Kenn

Date: 05-09-93 (06:10)              Number: 62541 of 63094 (Refer# 62523)
  To: DAVID BAUER
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (21:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Just drop Carrier in the chat mode  the board will not recycled!!!

Either you didn't understand me, or I don't understand you.  My understanding,
of what you are saying, tells me that I *already* tried that.

Here again is MY REPORT to you:

-> I dialed into the system.  Went into group chat.  Wrote one line of
-> text.  Then pressed ALT-H.
->
-> The PCBoard node I was logged into immediately recycled.

When I said that I pressed "ALT-H" I meant that I was at the callers end and I
"dropped carrier" (just like you said) by hitting ALT-H to hang up.

As I described in my report to you:  the board immediately recycled.

Now, in order for us to get anywhere on this, there obviously must be MORE TO
IT than what I have understood of your report thus far.  And in order for me to
help you out, or do anything about the way the code is behaving on your system,
I apparently need MORE INFORMATION to go on.

So I issued the following request:

-> Can you re-duplicate it on your system and get, for me, a
-> step-by-step list of instructions necessary to duplicate your report?
-> Thanks.

Please.  I am only trying to help.  And I am only trying to do the BEST JOB I
can.  If you would like me to look into your report any further then I need
MORE INFORMATION from you.

Telling me to "just drop carrier" when it appears that this is precisely what I
have done is, as you can see, futile.  It *worked* for me.

So help me discover why it does not work for you.  Provide me with the details
I have requested of you.  Do the testing that I have asked for and tell me what
you find.

The more information you can provide to me, step-by-step detailed information
(not "just drop carrier"), the better I can serve you.

Thank you for your time.
                                          David W. Terry 

Date: 05-09-93 (06:13)              Number: 62542 of 63094 (Refer# 62524)
  To: CHRIS VON MOTZ
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David , this is NOT a problem .I need to know if , when the /oldindex
-> parameter is set in the BOARD.BAT file , that only does apply for 3rd party
-> application products that are not up to compatibility with 15.0, and leaves
-> all the other functions intact , ot that all applications are running in the
-> old scheme. I.E . Postlink NEEDS that parameter , but my RoseMail Mail door
-> does NOT need it. If I set that parameter , does it only work for the
-> program that NEEDS it , or for ALL (Incl.RoseMail)??

There are two types of index files for your message base:

        MSGS.IDX        <-- new for v15.0 and _ALWAYS_ used by v15.0
        MSGS.NDX        <-- old, and only used if /OLDINDEX is used

Therefore, a setting of /OLDINDEX tells PCBoard to maintain BOTH index files.
Both the new one, which PCBoard needs, as well as the old one, which PCBoard
completely IGNORES except for the process of updating it whenever a new message
is posted.

In short:  Using /OLDINDEX will not "hurt" anything.  Use it if one (or more)
of your applications requires it.  Those that do not need it will not be harmed
by its usage.
                                          David W. Terry 

Date: 05-09-93 (06:19)              Number: 62545 of 63094 (Refer# 62528)
  To: CHARLES EVANS
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I ordered PPLC a couple of days ago, and that is exactly what I got -
-> PPLC.EXE inside a zip with little else.  I always liked intuitive programs,
-> but I suspect I will need more than the compiler in order to understand the
-> language.  Any suggestions, or are there other files that I should download?

You'll find the PPLDOC.ZIP (the documentation for PPLC) sitting in directory #2
right where we posted it the first day of the beta.  :-)

(for other's benefit:  You do NOT have to purchase the PPL Compiler just to see
the documentation, it is posted there in directory #2 for all to download)

Now, as a warning, the PPLDOC.ZIP file has a very cryptic style of
documentation.  The REAL documentation is still being worked on.  It will be
much more readable.  But for now, the only thing available is PPLDOC.ZIP.  As
soon as the printed manual is finished, however, we will ship it out to you.

-> I encountered a similar problem with MKPCBMNU.  The 3/4 page set of
-> "instructions" is not adequate for me to understand what to do and how to do
-> it.  Are there any example files anywhere?

Check out directory #2.  There are example PPL files, there is even an example
MNU setup for you to try.

Directory #2 and the upload directory of this conference contain a lot of files
that pertain to v15.0.  It sounds like you've been missing out on half of the
fun!  <grin>
                                          David W. Terry 

Date: 05-09-93 (06:23)              Number: 62547 of 63094 (Refer# 62534)
  To: IVAN WINDON
From: DAVID TERRY
Subj: OTHER:  ENCRYPTION 05-04-93
Read: 05-10-93 (01:58)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Just curious, might be my fault, but I don't know, the feature that lets you
-> encrypt your user file.  WEll when I was setting everything up i just
-> answered yes to that and let it do it's thing, but it seemed to kill the
-> user file I couldn't get it back to normal, it encrypted it alright, but how
-> do I make it return it to normal.

Please do NOT use that feature unless you know what you are doing.  You will
actually TRASH your users file if you make a mistake.

The steps to proper usage are:

1) Run the ENCRYPT.EXE program on your users file
2) Then make sure that EVERY NODE (every pcboard.dat) is configured to use
   encryption.  If you have EVEN ONE node improperly configured you risk
   trashing your users file.

Do not enable the encryption unless you have already run ENCRYPT.EXE.

From your description, it sounds like restoring a backup of your users file
will be the proper course of action at this point.

                                          David W. Terry 

Date: 05-09-93 (06:30)              Number: 62550 of 63094 (Refer# 62543)
  To: FRED MCCLAREN
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (01:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->    If the user enters his complete name and password at the first name
-> prompt, but enters his password incorrectly, the system sees it as a new
-> user name and asks if they want to Continue or Re-enter the name rather than
-> just prompt for the correct password as previous versions did.

Yes, this is a "change in behavior" from past versions ... but it was a
necessary change in order to accomodate the many "new collisions" on names that
will be occuring now that the ALIAS capability is built into the system.

                                          David W. Terry 

Date: 05-09-93 (06:06)              Number: 62553 of 63094 (Refer# 62114)
  To: DAVID TERRY
From: BLAINE BINKERD
Subj: BETA report              
Read: 05-10-93 (06:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

DT>I don't think PCBoard emits a "*.XXX corrupt" message.  Is that a message you
DT>saw on your screen?  What is the *exact* wording of the message?

I think actually saw this error.  The wording of the message was more
along the lines that 'USERNET.XXX is corrupt'.  I found that on one of
my other nodes, I'd changed everything but the call to PCB145 in
BOARD.BAT.  I replaced it with PCBOARD and things ran marvelously.
(The new USERNET.XXX had already been created by a node I'd
succesfully updated).
---
  DeLuxe/386 1.25 #669s  Innocent men should not be sent to congress

Date: 05-09-93 (07:38)              Number: 62554 of 63094 (Refer# 62551)
  To: MARK DURSTEWITZ
From: DAVID TERRY
Subj: USERNET.XXX Trouble      
Read: 05-09-93 (07:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->       I downloaded the May 7 version of the beta files, and this
-> morning one of my users was doing a normal logoff.  After typing "G", the
-> closing screen came up, logged him off, then the following message came up
-> instead of the call waiting screen.
->
->       "M:\PCB\MAIN\USERNET.XXX: Format Error
->       Exiting To DOS!"

Are you running any other utilities (such as USERNET.EXE or any mail doors,
etc) that might write out to the USERNET.XXX file?

Please investigate thoroughly.

Most likely you're bringing up an old (14.5a) copy of PCBoard or else hitting
the usernet.xxx file with some other "old" utility that is still writing to
that file in the old format.
                                          David W. Terry 

Date: 05-09-93 (07:56)              Number: 62556 of 63094 (Refer# 62260)
  To: DAVID TERRY
From: PIERRE DOUCET
Subj: BETA report              
Read: 05-10-93 (06:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When I install this new PCBOARD.EXE code, I found that the users
-> can't use
-> the function R A S and so on,  in the mail reading try .
->
-> Why NOT?  I mean...  what happens when they try?  What do you SEE?


I'm very confuse David, the probleme is not in PCBoard code,  but in the
new external .MNU file that I've download.

Sorry for the inconvenient .

Pierre Doucet

Date: 05-09-93 (09:21)              Number: 62559 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: WOLFGANG KRINGEL
Subj: BETA report              
Read: 05-11-93 (11:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-04-93 17:58:00                        


Hello Louise:
I hope you can answer a couple of questions
for OLD SANTA CLAUSE    Chris Kringel
From UP NORTH in the TUNDRA Country  < GRIN >

I don't know where the problem ( BUG ) is
which I am getting Now with the PCBoard Version 15.0/M
Beta  05/06/93  18:24

PROBLEM No. 1
=============
Before I switched over to Version 15.0
I was running 14.5 with the Utility program PCBEVENT
to run my nightly events, with out any problems.

When I was doing the upgrade to Versioo 15.0 I removed
All the information about PCBEvent.

I then installed the Event as specified in the EVENT.DOC
I have RE-read the DOC file many times and I can't see
where I went wrong, Since the Event program will not run.

Now here is a copy of my BOARD.BAT file

echo off
C:
CD\PCB
SET FOSSIL=F
SET NODE=1
SET DSZLOG=PCBDSZ.LOG
SET DOORPCH=PCB
if exist remote.bat rename remote.bat remote.sys
if exist door.bat del door.bat
if exist ENDPCB DEL ENDPCB
PCBoardm
if exist remote.bat remote
if exist door.bat door
if exist event.bat event
if errorlevel == 5 goto cycle
if exist endpcb goto end
:cycle
if exist c:\pcb\download\flagged.zip del c:\pcb\download\flagged.zip
CD\PCB
board
:end
cls

And here is a copy of my EVENT.DAT file

                 Batch     Begin  End                       Last
       Act  Mod  File      Time   Time   SMTWTFS  Date      Date
       ===  ===  ========  =====  =====  =======  ========  ========
   1)   Y    E   MAINEVNT  01:00  02:00  YYYYYYY  00-00-00  00-00-00
   2)   Y    E   SYSLOTTO  23:00  00:30  NNNYNNY  00-00-00  00-00-00
   3)   N                                NNNNNNN            00-00-00

Now I have the two BAT file in my C:\PCB directory, plus the BOARD.BAT
file is there also located.

PROBLEM No. 2
=============
In one of my Conference areas there where 5 message, I have killed
message 1, 2, 3 and 4 I then did a REPACK of the message base with
the RENUMBER:1 command.
Now if I use the R command to read messages in this area
I get the following command line.
(H)elp,  (4-4), Message Read Command ?
It used to tell me (1-1) with Version 14.5

Now in another conference area where all the messages have been
killed, I get the following message
(H)elp,  (1073741824-1073741824), Message Read Command ?

===============================================================
Now I hope you can locate the problem and tell me how to correct
them. I will call back in a few days when the system is not to
bussy, The last time I called ( Saturday Morning ) it took
over 150 tries and over one hour to get connected.

In closing I would like to say a
 BIG THANK YOU
to all the Staff at CDC
for creating and supporting
The BEST Bulletin Board System in the World

Yours truly
Wolfgang Kringel  ( Chris Kringel )
                      Sysop of
                The Foothills HAM BBS

Date: 05-09-93 (11:12)              Number: 62564 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ALLEN STONE
Subj: BETA report              
Read: 05-10-93 (11:43)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBOARD.EXE - 05-07-93 18:00:00                        


Hello David,
I am using the 5-7-93 18:00 version of PCBoard. The problem I have
encountered is as follows. I run 3 nodes of PCB under DV. I have 2
Pioneer 6 disc changers connected to the system. The cd-roms are idx'd
and the dir files are set in the dir.lst. With one node up and running
under desqview, you can flag a file from the cd-rom and it is copied and
downloaded locally without a hitch. The busy light on the cd rom drive
flashes at a quick pace and the file is copied in no time to speak of.
Once you open another node of PCBoard, the problems begin. It appears to
slow the system down to a crawl. A user logged on while I was on node 1
and I saw where he was connected on the waiting for call screen, but it
took PCBoard so long that he was eventually disconnected, the connect
screen appeared but only two lines and then a qemm exception 12. With 2
windows open I attempted to flag and download a file from the cd-rom.
When I went to d/l the file, the busy light on the cd rom drive flashed
every 20 seconds or so, after approximately 10 minutes of waiting for
PCoard to copy the file (104,299). You see the preparing file(s) for
download. Please Wait. This message remained on the screen for the
entire time. Then the following appeared 21:7:1:4 Error Reading File
r:\013a\deswin.zip (Drive not Ready), but the download screen appeared
with the options for the download. Once I pressed enter and inserted the
path, the d/ling box came up (ymodem-g) but it took approximately 5
minutes to d/l the file. The cps dropped to 328 from the 36228 average
cps that was obtained when only one node was opened. The file was said
to be sent, but it was not in the download directory when I looked for
it. These are the problems I have using the 6 disc changer with 15.0.
FYI, it works perfectly under dos and with only one dv window of pcb up.

Date: 05-09-93 (11:37)              Number: 62566 of 63094 (Refer# 62277)
  To: SCOTT CARPENTER
From: RAY GARDNER
Subj: Bug Report: PCBPACK?     
Read: 05-10-93 (09:01)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

It was with the original posting that I had the problem. I was not aware
that you had had multiple PCBPACK POSTINGS (The first Wide-Area version
I guess)

Date: 05-09-93 (12:05)              Number: 62574 of 63094 (Refer# 14)
  To: LOUIS ZIRKEL
From: ROBERT BLACHER
Subj: pcbpack 5-4-93           
Read: 05-11-93 (11:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

If my memory is wrong and someone else is doing PCBPACK, please
pass this along.

These comments apply to 5-4-93 PCBPACK but have probably been true
for weeks -- I've been using the 12/92 PCBPACK plus QPACK to update
the new index.  I tried your PCBPACK to do the whole thing for the
first time today.

(1) Nice display while it's packing.

(2) The /PURGE parameter refused to pack out a comment to me that
I had read.  In other words, it wasn't treating a received comment
as a received+private msg and packing it out as it should have.
It did pack out a non-comment, received+private msg.  (If you read
this paragraph six or seven times, it's bound to be clearer -- I
just don't know any other way to say it!).

BTW, PCBPACK /AREA:00 /PURGE was the command I used to test this bug (my
normal command is more complicated -- it failed to get the comment, too).

And, there was nothing wrong with the flag on that comment -- 12/92 PCBPACK
/PURGE got rid of it.

(3) PCBPACK isn't removing REFER # references to messages that have
been purged and no longer exist the way earlier PCBPACKs did.  If
this feature has been removed and I just missed the announcement
of that, so be it.  But, if you're supposed to be removing obsolete
REFER # references, you're not.

(4) Finally, I saw several msgs from David in DEVELOP describing the
/UPDATE parm and how it worked.  But, if that command is documented
anywhere, darned if I can find it.  PCBPACK /H (which should be
PCBPACK /? by the way) doesn't describe it and I can't find it
in WHATSNEW.



Date: 05-09-93 (12:15)              Number: 62575 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: MICHELE MAURO
Subj: OTHER:  PCBZMODEM 04-14-93 13:32:00
Read: 05-11-93 (11:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Hi... I'm having trouble with your PCBZmodem here... It's happened twice
and considered the difficulty getting on here lately <grin> I'm not
about to try and duplicate it! <grin>

Here's the problem. I did a QWK U with Z selected here and using the
internal Zmodem of RoseReader v2.0. It sends the file, my end says EOF
and then I'm dropped back to Salt Air, but I'm locked up here, it never
returns to the main board prompt. Alt-H is the only thing I can do.

RR has had trouble with TriBBS and WildCat! versions of Zmodem too, so
I'm assuming there's something non-standard with RR, Tri and WC!'s
implementations of Zmodem that don't jive well (along with yours too).
I'm switching to DSZ here until either you or RR figure out what's
wrong, but I thought I'd let you know.

Thanks, Michele

Date: 05-09-93 (12:55)              Number: 62577 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: RON GAGE
Subj: BETA report              
Read: 05-10-93 (07:39)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-06-93 06:24:00                        


Conditions:
    Just changed conference message file location dir.
        Changed location from I:\mail\drdebug\ to I:\mail\dr_debug\
    New msgs file did not exist at this time.
    Attempted to join into the conference using it's text name:
        J DR_DEBUG
Error reported
    Overlay loading error
        or something to this effect.
Subconditions:
    PCBoard exe file not read only attributed
    Could join the conf by number (J 89) and it worked fine
        creating the msgs file without problem.

Date: 05-09-93 (13:21)              Number: 62581 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: MICHAEL MORRILL
Subj: BETA report              
Read: 05-11-93 (12:11)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBPACK.EXE - 05-04-93 01:08:00                        


I have noticed there is a bug in PCBPACK, when I execute the following
command the only thing that executes on the line is index/oldindex, none
of the other commands on the line are executed.  Here is the line that I
use in my batch files:
   PCBPACK /AREA:ALL /DAYS:35 /KB /KD /index /oldindex
However, if I do the index or oldindex first then run another batch file
with all of the above commands except index/oldindex it runs as it
should.
Should I run the index commands everytime after an imput of all my mail,
because I belong to the FIDO net and poll every night for my mail and
want to know if this index command is necessary to keep the message
index files up to date.  ie..... I also have in each conference the old
index flag turned on and the appropriate set= in the board bat for old
index.  I hope I have explained it correctly Louis.  That's all for now.
Thanks for any help you can give.
                                                  Mike

Date: 05-09-93 (14:18)              Number: 62591 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: SAM GORSTEIN
Subj: BETA report              
Read: 05-10-93 (07:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93                                 


I have password protect exit to dos enabled on my system, and I have noticed
that if I press escape while PCBoard is recycling before it sends the init
string to the modem it will exit to dos without asking for a password.

-SG

Date: 05-09-93 (22:44)              Number: 62595 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: BILL MARTIN
Subj: BETA report              
Read: 05-11-93 (12:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Also, PCBPACK was printing the high number of message to keep while packing
for every message. I am sure you got that one, though.

Good Job!

Date: 05-09-93 (16:20)              Number: 62603 of 63094 (Refer# 16)
  To: LOUIS ZIRKEL
From: NANCY H. MILLER
Subj: USERNET.xxx??            
Read: 05-11-93 (13:00)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSETUP.EXE   05-07-93 17:35   


I am running a single node using the /2 version.  When I begin to edit
the Event Information by pressing F2 at Name/Location of EVENT.DAT, I
get the following error concerning USERNET.XXX.  I have never (to my
knowledge) *had* a USERNET.xxx file.  Is this a problem with my
configuration or is PCBSETUP simply not detecting the punyness of my
BBS?  :-)  By the way, I press the ANY key and it goes right along.


                              Event Information

  Is a Timed Event Active               : Y
  Name/Location of EVENT.DAT            : C:\BBS\GEN\EVENT.DAT
  Location of EVENT Files               : C:\BBS\GEN\

  For EXPEDITED Events:
  Minutes Prior to Suspend All Activity :  0
  Disallow Uploads Prior to Event       : N
  Minutes Prior to Disallow Uploads     : 15
                Ŀ
                                                            
                 (2:3) Error Opening File - File not found  
                                                            
                          C:\BBS\MAIN\USERNET.XXX           
                                                            
                         press any key to continue          
                                                            
                
 08:29:17  05-08-93  F1  help  caps: OFF  num: ON

If I delete the "Name/Loc of USERNET.XXX File" information in the System
Files part of PCBSETUP, then it still gives the above message, but with
a blank instead of the path\filename info.
---
  DeLuxe 1.12 #746s  InterNet Email: njh@seeker.mystic.com


Date: 05-09-93 (16:20)              Number: 62607 of 63094 (Refer# 3)
  To: DAVID TERRY
From: NANCY H. MILLER
Subj: KUDOS                    
Read: 05-10-93 (07:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

By the way, EVERYTHING which I wanted to be in this release is there,
and I am singing your (pl.) praises to whomever will listen.
---
  DeLuxe 1.12 #746s  InterNet Email: njh@seeker.mystic.com


Date: 05-09-93 (18:26)              Number: 62620 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ALLEN STONE
Subj: BETA report              
Read: 05-11-93 (13:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93 18:00:00                        


Hi Again David,
I have run into another problem with 15.0 beta. I am using 5-7-93, 18:00
beta code. I have set up 4 events to be run. The 1st at 06:30, the 2nd
at 17:55, the 3rd at 03:00 and the 4th at 00:15, all are expedited
events.I went into each node and ctrl-end each date on the 00:15 event.
I then rebooted the computer. When I logged on locally at 8:00 pm, the
board told me that the next scheduled event was at 06:30. The 00:15
event is there, but the board didn't see it for some reason and it went
to the 06:30 event and skipped the 00:15 event.

Date: 05-09-93 (19:13)              Number: 62623 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ERIC SCALES
Subj: BETA report              
Read: 05-10-93 (08:14)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-04-93                                 


   Hello Dave..  Noticed this when I attached a file to a message...  Whenever
I uploaded the file (Hit SA) and it got through testing, it said Saving Message
#982 then it just sat there..  I could move around through desqview, but that
node seemed to stall.  So I did a CTRL-ALT-DEL within desqview which just
closes out that window, then I restarted that node..  I looked in the callers
log and it said "Back from Dos at 18:47".  I didn't drop to dos, the board
seemed to stall when the message was being saved..  So I tried it on my dial-in
node and it did the same thing only it put another message in the callers log
that said "Bad File Number".  I rebooted the computer and tried it again and
everything worked great.  Really confused here..   Here is a capture of my
callers log for my dial-in node..

**************************************************************
05-09-93 (13:03) (1) ERIC SCALES Off Normally
      Minutes Used: 1
      Back from DOS at 13:03
      (6:7:1:8) Error Writing File  (Bad file number)
      Message Left: Main Board # 987
      File Attachment: EDSQT101.ZIP
      (U) EDSQT101.ZIP  Completed using G  T/E=0  CPS=7200
05-09-93 (13:02) (1) ERIC SCALES (Local) (G) E.D.S. DEVELOPMEN

Date: 05-09-93 (20:31)              Number: 62626 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: DEAN LAVIOLETTE
Subj: BETA report              
Read: 05-10-93 (08:15)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSETUP.EXE - 05-07-93                                


Dear David:

-> The above didn't help me any...   about all I can recommend is that you
-> go through your setup and look for a BLANK FIELD in there.
->
-> I would imagine that is why it does not give a filename in the above...
-> because it IS giving the filename, but since it is blank you don't see it.

I know I have many conferences that have no blts, doors, or dl paths.
They've been like that for some time though, and the diagnostic program
does flag them as missing.  I doubt this is the problem though.

-> If you would like me to research it for you then you'll need to upload
-> your PCBOARD.DAT, CNAMES.@@@ and CNAMES.ADD files.

Look for DATACOM.ZIP in your upload directory.  I looked everywhere and
couldn't see any important blank fields.

-> 3) Alternatively, have PCBPACK simply update the NEW indexes, which can be
->    done more quickly, by using this command:
->
->         PCBPACK /AREA:ALL /UPDATE
->
->
-> Hope this helps.  And let me know what you find on the PCBSetup problem.

That one helped tremedously David.  Also, there was an OLD PCBPACK.EXE in
each of my node directories.  It corrupted many of my indexes, but I had
no problems recovering them.  I believe having PCBPACK.EXE in each node
sub-directory "was" a requirement in the old days.  I was only replacing
the one in my \PCB directory.  Maybe you may want to caution all those
who have been having PCBPACK problems.

As a side note... I'm not sure if you guys wrote the GRAF.PPE file for
auto-ansi detection, but when I run here... the User only sees a '?'.
If you did not write it, don't worry about it.  I'm sure you have more
important things to do.

On that note... thanks David!

Regards,

Dean Laviolette

Date: 05-09-93 (22:23)              Number: 62636 of 63094 (Refer# 62629)
  To: SCOTT CARGILL
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> ******************
-> Event.dat
-> ******************
->
-> Y    E   DOWN      14:39         YYYYYYY   00-00-93  00-00-00
-> Y    E   EVENT     14:40         YYYYYYY   00-00-93  00-00-00
->
-> I did finally figure the whole thing out, and don't find a major problem
-> other than when I put in a begin time I MEAN BEGIN!, that really ticked me
-> off a bit....

It looks to me like you still didn't figure it out.

The BEGIN TIME really DOES mean "begin".  But apparently you are not filling
out BOTH fields.   Both a BEGIN and an END time are required.

If you did (what your illustration above shows) you probably started out with a
valid BEGIN time and a BLANK end time and that is why it failed.

Then you switched to a BLANK begin time and a valid end time and, by some
quirk, that happened to work.

Please fill in BOTH fields.  Both of them are required.

                                          David W. Terry 

P.S.
In case you have never beta tested before...   docs are one of the last things
that will be finished.  Sorry, but that's the way "beta testing" is...

Date: 05-09-93 (22:32)              Number: 62637 of 63094 (Refer# 62627)
  To: MIKE JACKSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am having the same problem with Alias support that DONALD MEHRTENS is
-> reporting (see your response in message 62582).  I have followed the
-> instructions in the What's new file, and in that message to the letter. I
-> can also create and alias with PCBSM, but cannot switch to that alias when
-> in a conference that is set to allow alias'.

The above indicates that you have not yet edited your PWRD file to place the
letter 'Y' in the column that says to allow that security level to use an
alias.

In other words, there are three pieces to this puzzle. They are:

1) Install the Alias PSA
2) Set the "Allow Aliases to be Used" switch on a specific conference
3) Set the "Allow Alias" switch on a specific security level (PWRD File)

Get all three taken care of and it *will* work.

-> I am unable to create new alias' with the "W" command.  It doesn't even ask
-> for one during a new user logon (although, it does ask for the extended
-> address information as I have that installed also).

I believe the above is related to your lack of the "Allow Alias" in your PWRD
profile.

-> In another recent message from DONALD MEHRTENS, he states that somewhere, he
-> say that he would have to edit his PWRD file to allow alias' for various
-> security levels.  This would make sense, and sounds like a good idea, But I
-> don't see anywhere in the PWRD file that allows one to select alias support:

Press the F2 function key.

                                          David W. Terry 

Date: 05-09-93 (22:28)              Number: 62638 of 63094 (Refer# 62621)
  To: AQUILA BBS
From: DAVID TERRY
Subj: Files                    
Read: 05-10-93 (17:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David, you said the new code requires more open files, could you give us an
-> idea of how many could be open per node so that we can reconfigure our
-> system.   When we put that first beta up we found out that we maxed out the
-> open files, and we'll have to take care of this problem first.

Look down at the bottom of your screen.  The STATUS bar.  The blue box on the
status bar.  In that blue is the "highest handle returned" by DOS for that
session.  It's not exactly the "total number of files open" but it should give
you a pretty good indication, on a per node basis, of how many files are being
opened.
                                          David W. Terry 

Date: 05-09-93 (22:33)              Number: 62639 of 63094 (Refer# 62618)
  To: DONALD MEHRTENS
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (04:30)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> His message said this was mentioned in the docs and he missed it - I still
-> can't find it.  Where ever it is, it should be listed as step "3)" under
-> "added   Alias Support on a per-conference basis..." in the WHATSNEW file.

Got it.  Will add the following to the WHATSNEW file:

|        3) Then you must select which security levels will be allowed to use
|           an alias by editing your PWRD file.  Press the F2 key, once inside
|           the PWRD file editor, and answer 'Y' in the Alias column for each
|           security level that should be allowed to use an alias.

Thanks.
                                          David W. Terry 

Date: 05-09-93 (22:37)              Number: 62640 of 63094 (Refer# 62411)
  To: DAVID TERRY
From: CHUCK KIRBY
Subj: Overlay Size             
Read: 05-10-93 (08:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

DT>A higher value allows more of the .EXE file to be held in memory.  The highe
  >possible value, of course, would simply load the ENTIRE .EXE file into memor
  >at "load time" and would never again access the hard disk.

DT>But that would be wasteful of memory.  So a smaller value, such as 16, is us
  >This lets PCBoard pull in the code that is running, when it is needed, and
  >leave the rest of the code on disk until it is needed.

Being a programmer and quite familiar with overlays and such I find it
fascinating and am grateful to you for doing it.  I run a 2 node system
in Desqview on a 386 33mhz with 2 v.32bis modems.  I found I could make
the overlays the maximum size and all worked well...I did downsize it a
bit just for fun to check performance, all seemed well so I downsized it
some more until I got to the 3rd from smallest value when disk activity
picked up considerably.  I ended up running it at 100k when a few times
my 3rd node (local for me only) totally rebooted the machine when I
exited Pcboard.  No problems since then.  I wish more commercial
programs had this capability of sizing overlays.

DT>So allowing you to pick the buffer size allows you to "tune" your system to
  >meet your memory AND performance needs.  If you need more memory, go for a
  >lower overlay buffer size.  If you need more performance, go for a higher
  >buffer size.

From someone who has spent an enormous amount of time over the years
"tuning" the system (although I do it with all my computers being a
hardware expert and a programmer makes it easy)  I appreciate this
feature among many others in this release.  I found MANY things in v15
that make me glad I run Pcboard.  Thanx for your efforts!  Pcboard has
become a rather complicated and yet very configurable system....just
can't wait till I get the PPL!!!  grin.  I don't mind the sophistication
at all!  In fact I enjoy it.

I have had a bit of a problem with pcbpack however and am working on the
details.

---
  QMPro 1.01 12-1234  He does the work of 3 Men...Moe, Larry & Curly


Date: 05-09-93 (22:37)              Number: 62641 of 63094 (Refer# 62615)
  To: MARK DURSTEWITZ
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (09:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

DT>So do NOT use the /INDEX command unless creating INDEXES was all you wanted
  >do.

-> Sure does.  If I add the /INDEX switch to all my other switches, it will
-> create the new indexes as well as keep the old ones.

NO.  That is incorrect.  Re-read what you quoted back to me and notice the
capitalized "NOT" at the beginning.

You do _NOT_ want to use the /INDEX command UNLESS THAT IS ALL you want - just
a set of index files and NOTHING FURTHER.

In other words, if you want to "pack" your message base, then /INDEX is *not* a
command that you want to use.  /INDEX means only one thing:  Do NOTHING BUT
create an index file.

Here is the rest of my message again (you quoted it to me so I'll quote it back
to you).  Please re-read it carefully:

DT>For clarification:

DT>The /INDEX command tells PCBPACK to do _NOTHING BUT_ create an index.
  >you use PCBPACK /AREA:ALL /INDEX /OLDINDEX then you are telling PCBPAC
  >create index files (of both types) for all conferences.

DT>So do NOT use the /INDEX command unless creating INDEXES was all you w
  >do.

DT>On the other hand, /OLDINDEX means something entirely different.  It t
  >PCBPack that it should maintain the old index files.  This applies to
  >other commands you are passing to PCBPack.

DT>So if you issue the command:  PCBPACK /AREA:ALL /DAYS:30 /OLDINDEX

DT>This will tell PCBPack to pack the message base and update the new ind
  >also update the old index.

                                          David W. Terry 

Date: 05-09-93 (22:39)              Number: 62642 of 63094 (Refer# 62613)
  To: MARK DURSTEWITZ
From: DAVID TERRY
Subj: OTHER:  PCBOARDEXE 05-04-
Read: 05-10-93 (09:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I tried this one today and had the same problem.  Yes, PKZIP is in my path.
-> I was watching the node while the call took place, and when PCBoard shelled
-> out to pkzip I got this error message,
->       "PKZIP: CAN'T CREATE : WORK/.QWK"

The above error message looks like it is missing the filename.

Go into PCBSetup : Configuration Options : Messages and make sure that you have
specified a name for your QWK packets.
                                          David W. Terry 

Date: 05-09-93 (22:40)              Number: 62643 of 63094 (Refer# 62611)
  To: PETER LAUR
From: DAVID TERRY
Subj: The old CNAMES           
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I wonder if you or someone else at CDC could make a conversion program from
-> the new CNAMES.@@@ to the old CNAMES file? This because WGM isn't still
-> compatible and who knows when there will be a new release of it.

No need.  When you exit PCBSetup, type 'Y' to save.  It will create the CNAMES
file on the way out.
                                          David W. Terry 

Date: 05-09-93 (22:44)              Number: 62644 of 63094 (Refer# 62595)
  To: BILL MARTIN
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (00:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->     (C:\MWORK2\MSG2.$$$) is missing! <<<<<< This line... QWK U was command

Don't worry about this message... it is bogus and will be removed later.

                                          David W. Terry 

Date: 05-09-93 (22:45)              Number: 62645 of 63094 (Refer# 62594)
  To: RANDY DAVILA
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (01:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When in a conference that allows Alias', using the WHO command the USERS is
-> blank.  After returning to a conference that restores your real name it is
-> still blank.

It is working properly.  Please read the WHATSNEW file for details on how
PCBoard "hides" the changing of the alias name.

-> When I left a message using the @user@ macro the callers where not giving
-> the mail waiting prompt.  I did use the upper case letters for user.

It's not supposed to.  It never has done that and it doesn't do it now either.

                                          David W. Terry 

Date: 05-09-93 (22:50)              Number: 62647 of 63094 (Refer# 62590)
  To: PETER BYRNE
From: DAVID TERRY
Subj: QWK Local Upload         
Read: 05-10-93 (13:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is it possible to locally upload a REP packet using the QWK U command. If
-> so, which directory should the REP packet be in and how do I tell PCBoard to
-> uploard it locally, rather than trying to receive it from the COM port?

Either select an internal protocol as your default, and then type QWK U, or
else type QWK U G (the letter "G" is for Ymodem/G, but any internal protocol
definition will do).

PCBoard will then prompt you for the path\name of the file you want to upload.

You could then type \READER\UPLOAD\SALTAIR.REP to upload the file...

You might want to set up a Shifted-Function key to do the above for you to save
keystrokes the next time you want to upload a REP packet.

                                          David W. Terry 

Date: 05-09-93 (22:51)              Number: 62648 of 63094 (Refer# 62589)
  To: PETER BYRNE
From: DAVID TERRY
Subj: INTERNAL ZMODEM?         
Read: 05-10-93 (13:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> It was rumoured that PCBoard 15.0 would have Internal support for ZModem. I
-> don't see any reference to this in the WHATSNEW file, so I was wondering
-> whether it was actually implemented and, if so, how I activate it (I am
-> cureently using DSZ for ZModem.

Nope, the rumor didn't come from us.

The only 'truth' to the rumor is that we _DO_ offer our own zmodem now.  We
started offering it back when PCBoard/M (multi-port) came out.  And we will
continue to offer it now with v15.0.  It's not internal.  But it is from us.

                                          David W. Terry 

Date: 05-10-93 (00:52)              Number: 62654 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: CAM DEBUCK
Subj: BETA report              
Read: 05-11-93 (13:13)              Status: PUBLIC MESSAGE / FILE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93 06:08:00                        


   My date on PCBOARD.EXE is as follows:
 Directory of H:\PCB

PCBOARD  EXE    452576 05-07-93   6:08p
        1 file(s)     452576 bytes
                   329007104 bytes free

  Having problems with Events.  Basically, I have one event.  It runs
on Monday, Thursday, and Saturday.  Well, it doesn't.  It runs every
day <arg>.  Other than that, no other problems <sigh>.  I'm including
an attached file with some screen captures from PCBSetup and my
EVENT.DAT, and my MAILRUN batch file (Which is called MAILRUN.001) and
a file called EVENT.TXT that shows what my setup options look like.
Hope this helps you find the problem.
   --Cam--

Date: 05-10-93 (01:55)              Number: 62663 of 63094 (Refer# 62409)
  To: DAVID TERRY
From: DON REID
Subj: Setup problem         1/2
Read: 05-10-93 (09:51)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Go into PCBSetup : Configuration Options : Colors.
->
-> Try a setting such as 1F as the default color.

Already have! Man, you can't believe the wild colors I have. ;-)

-> Yup, those are all indications of a File Allocation Table problem.
-> You'll want to rememedy this ASAP.  Good luck to you.

Already have! Thank goodness for Norton's DD.

Date: 05-10-93 (01:58)              Number: 62665 of 63094 (Refer# 62547)
  To: DAVID TERRY
From: IVAN WINDON
Subj: OTHER:  ENCRYPTION 05-04-93
Read: 05-10-93 (09:51)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Please do NOT use that feature unless you know what you are doing.
-> You will actually TRASH your users file if you make a mistake.
->
-> The steps to proper usage are:

Yup, that's about what it did.  I saw the note in the second beta copy
of pcbsetup.  I was just so happy to have 15.0 I was making every
feature turn on.  In fact I have installed every PPE I can find on it,
and have everything in PCBoard working (that I know of)... except the
ecryption part (I fear that one now :-).

Thanks for the G R E A T software, I'm having so much fun!!

Ivan Windon

Date: 05-10-93 (02:58)              Number: 62670 of 63094 (Refer# 62536)
  To: JULIO DAVILA
From: TIM ELSON
Subj: event in pcboard 15.0    
Read: 05-10-93 (11:04)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I found the answer...!!!
-> you only delete the line that says if event.sys rename....etc..
-> but you must leave the second one.....
What is the other line you must leave?.
ttyl Tim.

Date: 05-10-93 (02:59)              Number: 62671 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: FRED BUSTEED
Subj: BETA report              
Read: 05-11-93 (13:14)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBPACK.EXE - 05-04-93 13:08:42                        


/re:1 doesn't work at all under ANY circumstances.  I can't renumber any
messages AND (most important of all) when I do an on-line command 3 and tell it
"Y" to "renumber", the system will lock up.  Understand that I am running under
DV and merely have to close the window up and re-open it to remedy the lock-up,
however when I am away and it happens, it stays in that condition (with the
command line showing pcbpack .....please wait.....) indefinitely.

                                =  Buz  =

Date: 05-10-93 (04:23)              Number: 62679 of 63094 (Refer# 62647)
  To: DAVID TERRY
From: ULF SVANLUND
Subj: Fund problem             
Read: 05-10-93 (10:06)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

I found a little bug when you are about to quit PCBSETUP and checking
DLPATH in the conferences.

The problem is, if you have a path that is on a drive that you do not have
in your system, PCBSETUP will hang and the only way out is to reboot, and
PCBOARD.DAT will get corrupted
A$;---A$;  WinQwk 2.0 #0  Unregistered Evaluation CopyA$;

Date: 05-10-93 (04:33)              Number: 62680 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: DONALD MEHRTENS
Subj: BETA report              
Read: 05-11-93 (13:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-07-93 18:08:00                        


I seem to be having a small problem with events.  This is my EVENT.DAT
file for node 2.  This screen shot was taken on Monday 5/10 at 5:50 am:

                  Batch    Begin  End                         Last
       Act  Mod   File     Time   Time   SMTWTFS    Date      Date
                     
  1)    Y    E   EVENT2    02:00  03:00  NYYYYYN  00-00-00  05-06-93
  2)    Y    E   EVENT2    06:00  07:00  YNNNNNY  00-00-00  05-09-93

Notice that the event 1 has not run.  The node was brought up at 11p
yesterday, and I have not changed the EVENT.DAT since at least Saturday.
The same thing happened on node 3.

I'm sure I do have the event directory and batch files set up correctly,
and PCBoard must have agreed because it ran the same event both Saturday
and Sunday without a hitch.  I have an EVENT2 file under D:\PCB\EVENT
which is my "Location of EVENT Files" directory.  The only reason I can
see it would have skipped it last night was if the node was busy for
that hour, but according to the log no one had been on either node since
Sunday night.

Further, node 1 had an event scheduled for that same time, and it ran
fine (which is what called my attention to the problem - when I woke up
node 1 was still in the event waiting for nodes 2 & 3 to come down which
is what the missed event was to do).  Here is my node 1 EVENT.DAT:

                 Batch    Begin  End                         Last
      Act  Mod   File     Time   Time   SMTWTFS    Date      Date
                    
 1)    Y    S   2400ON    00:02  03:00  NYYYYYN  00-00-00  05-10-93
 2)    Y    E   NIGHT     02:00  04:00  NYYYYYN  00-00-00  05-10-93
 3)    Y    E   NIGHT     06:00  08:00  YNNNNNY  00-00-00  05-09-93
 4)    Y    S   2400OFF   08:00  10:00  NYYYYYN  00-00-00  05-07-93
 5)    Y    E   RIMERUN   15:30  18:00  NYYYYYN  00-00-00  00-00-00
 6)    Y    S   RIMERUN   15:30  22:00  YNNNNNY  00-00-00  05-09-93

The end times don't match, a small error on my part which I just
corrected. But that shouldn't have made a difference since all nodes
were inactive at 2:00am.

One other thing I noticed.  I cannot use any time between 23:59 and
00:01 inclusive as an event start time.  PCBSetup won't let me tab out
of the field if I do.  Any reason for that?

                                Donald

Date: 05-10-93 (04:59)              Number: 62683 of 63094 (Refer# 62668)
  To: DON REID
From: LEWIS SCHALLER
Subj: PCBoard.DAT - Node 2     
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Having trouble getting Node 2 up. First it was the USERNET.XXX that
-> was bad. Got that fixed. Now the PCBOARD.DAT is bad. I copied the one
-> from Node 1 in and now Node 1 loads when I try to load Node 2. HELP!
-> Thanks!


Could you have overlooked the node # in the setup for node 2 and left it
as node 1?

                           Lou

Date: 05-10-93 (05:13)              Number: 62684 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: HAL WOLD
Subj: BETA report              
Read: 05-11-93 (13:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBPACK.EXE - 05-04-93 13:08:00                        


Exception #13 at 2020:2024, Error code: 0000
AX=8529 BX=14EE CX=0000 DX=0000 SI=000B DI=8529 BP=FFF0
DS=0000 ES=2B71 SS=1CC0 SP=FFD8 FLAGS=7246
Instruction=  6D 65 20 62 75 74 20 68 61 76 65 20 6A 75 73

DOS version 5.00, QEMM version 6.03

I've repeated this error five times. PCBoard 14.5 ran for over a year
with out error with my current setup, Only changes made so far was
upgrading to PCB 15.0. Not sure what else you need from me, If you need
more info, let me know. It may take a while since it's almost impossible
to get on here

Date: 05-10-93 (05:14)              Number: 62685 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: DEREK NIGRINI
Subj: BETA report              
Read: 05-11-93 (13:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBSETUP.EXE - 05-08-93                                


Hi Dave

When i try to set up Pcboard 15/e10 as a single node system, the events
won't run.Pcbsetup is also complaining about the missing usernet.xxx
file when pressing F2 to configure the event file...

When i tell pcbsetup that i am going to run a multinode system
everything works fine - the events start as normal etc..

Regards
Derek

Date: 05-10-93 (05:45)              Number: 62687 of 63094 (Refer# 62258)
  To: DAVID TERRY
From: JAMES JONES
Subj: BETA report              
Read: 05-10-93 (10:22)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

PCBOARD  EXE    452464 05-07-93   6:08p
PCBPACK  EXE     79012 05-04-93   1:08p
PCBSM    EXE    175312 05-07-93   5:33p

1.  You wrote this to someone else, but it applies...

DT>Please research the setup and ensure that ALL NODES are configured properly.
DT>When you are done, immediately run PCBPACK *one time* using the following
DT>command:

DT>        PCBPACK /AREA:ALL /INDEX /OLDINDEX

I found that if I didn't put the /INDEX on all the time, that the
system would lock up.  I mean, even Desqview wouldn't respond.  This
happened three times before I figured out what it was.

I am using QMail 4.0, QNet 3.0, and PCRelay 4.11 to import messages
into the message base.

2.  The problem I was having with File Attachments doesn't seem to be
    there in the new code (I was using code from the 6th I think).  It
    might have been because the message had failed the first time, and
    so it didn't copy it, and then subsequent attempts didn't copy it
    based on that.

    Anyway, local file attachments and remote file attachments seem to
    be working.

3.  When is a local file attachment deleted?  I killed the messages
    that had the file attached, and then packed the message base so
    the messages were removed.  The files remain in the attachment
    subdirectory.

4.  When using the alias feature, all messages inserted via the QWK U
    command are inserted with the name in use at the time.  So, if I
    am in the main board, and called "sysop" there, all messages, even
    those in an alias conference are from "sysop".  If I am in a alias
    supported conference and do the QWK U command, all messages are
    from the alias, even those in the main board (where aliases are
    not supported).

5.  The PCBSM sometimes prints the entire user record and sometimes it
    doesn't.  I selected the Print Users File command, option B (full
    record).  Pressing Page Down gives the regular output from version
    14.5.  Tried this three times.  On a whim, I pressed PgUp, it
    printed the headers for the extra information (address, city,
    state, etc), but it put no information in there.  Tried it again
    with PgUp (just to make sure that's what did it) and it printed it
    without the extra user information.

6.  Is it possible to allow multiple logons AND change the user
    information?  I have a couple of co-sysops I would like to allow
    on more than one node at a time (we all have a couple of modems).

7.  Will multiple logons be prompted for the password change?  I don't
    remember seeing anything about that in the WHATSNEW file.  Or,
    should I just make sure that all people who have a security level
    which allows multiple logons have their date set to 00-00-00 for
    the next change?

8.  The last dates that an event has been run are becoming scrambled for
    the events.  I went ahead and re-zeroed out the dates.  Sorry, I meant
    to capture it and show it to you.

9.  Something is wrong here.  Not sure what.  The 23:31 caller is normal,
    The 1:10am callers is screwed up.  In fact, every caller after that is
    messed up.  There is 9 Meg free on that drive.  There is 97 Meg free on
    the drive that contains the bulletins.  From looking at the logs, the only
    thing that I can figure is that Node 2 ran it's "CALLERS" event at 00:30.

    05-08-93 (23:31) (1) JIM SMITH (9600E) (A) WHITE SPRINGS, FL
          Modem: CONNECT 9600/ARQ/HST/HST
          Caller Number: 22,351
          Caller Security: 72
          Opened Door (QMAIL4) at 23:31
          (D) TWOTHIRD.QWK Completed using Z via Qmail (11k)
          Minutes Used: 2
    05-08-93 (23:32) (1)  JIM SMITH Off Normally
    **************************************************************
    05-09-93 (01:10) (1) ERIC MARTIN (2400E) (A) DECATUR, IL
          Modem: CONNECT 2400/ARQ/MNP
          Caller Number: 22,354
          Caller Security: 10
          Bulletin Read: Main Board # 15
          Disk Full - System presently unavailable!
          (39:0:0:3) Error Writing File C:\PCB\MAIN\USERS.INF (Pos
          Disk Full - System presently unavailable!
          (39:0:0:3) Error Writing File C:\PCB\MAIN\USERS.INF (Pos
          Disk Full - System presently unavailable!
          (39:0:0:3) Error Writing File C:\PCB\MAIN\USERS.INF (Pos
          Disk Full - System presently unavailable!
          (39:0:0:3) Error Writing File C:\PCB\MAIN\USERS.INF (Pos
          Minutes Used: 4
    05-09-93 (01:14) (1) ERIC MARTIN Off Normally

    The 23:31 caller is normal, the 1:10am callers is screwed up.  In fact,

(Continued in the next message)
---
  DeLuxe 1.26b #1158s  sin 2a = 2 sin a cos a


Date: 05-10-93 (05:45)              Number: 62688 of 63094 (Refer# 62258)
  To: DAVID TERRY
From: JAMES JONES
Subj: BETA report (#2)         
Read: 05-10-93 (10:23)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

(Continued from the previous message)

    every caller after that is messed up.  There is 9 Meg free on that drive.
    There is 97 Meg free on the drive that contains the bulletins.  From
    looking at the logs, the only thing that I can figure is that Node 2 ran
    it's "CALLERS" event at 00:30.

    **************************************************************
          Event #6 - CALLERS ran at 05-09-93 00:30:58 Node 2
    **************************************************************
          Event finished at 05-09-93 00:31:01 Node 2
    **************************************************************

    Here is my CALLERS file.  It is supposed to make a copy of the caller log
    so that I can view yesterday's log from online, then archive the log so
    at most there is only one day's log when you do command 13.  Datestr is a
    pascal program I wrote which outputs:  SET DATESTR=yyyymmdd  and then I
    execute the batch file so the environment is set with that.  That part
    works.  The program did not zip the callers log into
    c:\pcb\util\callers.zip  like it was supposed to.

    @echo off
    pcbcopy c:\pcb\main\caller%pcbnode% d:\confs\blt
    c:\pcb\util\datestr 1 > setdate.bat
    call setdate.bat
    ren c:\pcb\main\caller%pcbnode% %datestr%.%pcbnode%
    pkzip -m c:\pcb\util\callers c:\pcb\main\%datestr%.%pcbnode%
    set datestr=
    del setdate.bat
    board

    I just noticed a wrong path in the file.  c:\pcb\util\datestr should be
    c:\util\datestr.  What that means, though, is that the event merely copied
    the file into d:\confs\blt and then restarted the board.

    That would explain why the zip file wasn't updated, but it wouldn't
    explain all the problems with the disk being full and the system being
    unavailable

10. (filename) already exists on the system.
    This shows up to the remote caller, but not on the local screen.

11. In regards to number 4 (Alias feature).  I just had an user upload a
    message into an alias conference from a non-alias conference using the
    internal QWK routines.  He then joined the conference, and could read and
    kill both messages (both showed up with his real name, even though he had
    specified different names when he saved them in his mail reader).  That
    is, he can read messages from his real name when using his alias.

    He then joined the alias conference and uploads the same two messages.
    This time they are both from his alias, but he can neither read nor kill
    them.  That is, he can NOT read messages from his alias while using his
    alias.

    I had him enter a message online with his alias.  He could not turn around
    and read that or kill it.

    I then entered a message for him with his alias in a non-alias conference.
    He was unable to read that using his real name.

    In other words ... He can read messages from his real name whether he is
    using the alias or not.  He can not read messages from his alias whether
    he is using the alias or not.
---
  DeLuxe 1.26b #1158s  sin (-x) = - sin x



Date: 05-10-93 (05:57)              Number: 62691 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: DAN VEANER
Subj: BETA report              
Read: 05-11-93 (13:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93                                 


David,

I know this sounds screwy, but this is what is happening with the event
problem I wrote you about last week.  I set up a test event that simply
had a DIR command in it, and I set it up identically to the rimeevt that
wasn't running, except that I set it to run at 7:25am.  It ran fine, but
rimeevt did NOT run all this time (since the beta began).

This morning I made a copy of rimeevt called mailevt, set it up
identically in PCBSETUP, except that I set the time for 7:25 so I could
watch it.  It ran perfectly.  So I'm going to change the time back to
3:25 and see if it runs tonight.   I've been over the event doc six
times, and my setup more than that.  I'll let you know how tonight's
event runs.

Meanwhile my 2 node mainevt and the test event continue to run
flawlessly each day.

Dan

Date: 05-10-93 (06:14)              Number: 62693 of 63094 (Refer# 62258)
  To: DAVID TERRY
From: JEFF BINKLEY
Subj: BETA report              
Read: 05-10-93 (10:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> In your EVENT when you are packing with PCBPACK:
->
->       PCBPACK /AREA:ALL /OLDINDEX (plus whatever other parameters you
-> have)
->
-> Please research the setup and ensure that ALL NODES are configured
-> properly. When you are done, immediately run PCBPACK *one time* using
-> the following command:
->
->       PCBPACK /AREA:ALL /INDEX /OLDINDEX
->
-> The above will recreate the index files for all message bases.
->
-> Let me know a status report after you have performed the above.
->                                         David W. Terry 

David,

   I did not have the /OLDINDEX in the PCBPACK command during my event.
From my vantage point the problem is cleared (i.e. I cannot reproduce
it).  However, many of my users (most who use SLMR) are complaining of
their .QWK mail packets being "hashed".  I have asked them to upload one
so I can see it.  I'm kind of lost at this point since it works fine for
me using WinQwk.

                                Jeff

Date: 05-10-93 (06:25)              Number: 62695 of 63094 (Refer# 62484)
  To: MIKE DEMSKI
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (11:23)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I just installed the password PSA with 120 days pswrd expiration, 14 days
-> warning.  What happens to the users who already were on the bbs with old
-> paswords?

The first time an existing user calls, the user inherits the "password
expiration time" specified.

In other words, in your case, an existing user will inherit a 120 day
expiration period the first time he/she calls after you install the Password
PSA into the system.

-> Does the countdown start from the day that I installed the PSWRD PSA?  Will
-> they have 120 days from the installation day?

No, 120 days from the first day they call after installation day.

                                         David W. Terry 

Date: 05-10-93 (06:27)              Number: 62696 of 63094 (Refer# 62489)
  To: DONALD MEHRTENS
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (18:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> If these are out of scope for 15.0, please put them on the wish list for
-> whatever follows it.

Wishlisted.
                                         David W. Terry 

Date: 05-10-93 (06:33)              Number: 62698 of 63094 (Refer# 62519)
  To: DAVID FULLER
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I installed the PSA for alias use as described in the "Whats New" file and
-> am having the following problem:
->
-> I installed the PSA from PCBSM, User Info File Maintenance, Add PCBoard
-> Supported Allocations, Add Alias Support.
->
-> Then I went to PCBSetup and set the Allow Aliases to be Used flag to Y in
-> each conference I allow aliases to be used.

There is one more step.  The following information has been added to the
WHATSNEW file to help you out (and others having the same problem):

         1) You must first run PCBSM, select "User Info File Maintenance", then
            select "Add PCBoard Supported Allocations", then select "Add Alias
            Support".

            This step adds a PSA (similar to a TPA) into the users.inf file.
            The only major difference is that the PSA is directly supported by
            both PCBoard and PCBSM.  That is, callers can use PCBoard to set
            their Alias when logging in for the first time or by using the
            (W)rite User Info command, or the sysop can use PCBSM to edit the
            alias (via the Users File Editor).

         2) Then you must inform PCBoard which conferences allow aliases to be
            used.  Do this by going into PCBSetup, then go to the Conference
            configuration screen, then press PGDN to go to the switches screen.
            Answer 'Y' where it asks "Allow aliases to be used".

|        3) Then you must select which security levels will be allowed to use
|           an alias by editing your PWRD file.  Press the F2 key, once inside
|           the PWRD file editor, and answer 'Y' in the Alias column for each
|           security level that should be allowed to use an alias.

Item #3 was not in the original WHATSNEW file.

                                         David W. Terry 

Date: 05-10-93 (06:38)              Number: 62701 of 63094 (Refer# 62529)
  To: CHARLES EVANS
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 1)   I cannot get the logon to default to "Y" when asked about Color
-> Graphics.  Try as I may, it still defaults to "N".

Perhaps there is some confusion here...

Your PCBTEXT PROMPT, the one that says "Do you want graphics" probably says
"(enter=no)" in it.

If you want it to say "(enter=yes)" then you must MANUALLY CHANGE it.

PCBoard makes no attempt to understand the language in which a prompt is
written in order to modify the prompt.  The above could have been written in
French or German or whatever.

So if you change your default to yes, via PCBSetup : Configuration Options :
Switches : Default to Graphics at Login, then you must ALSO edit your PCBTEXT
prompt to reflect that change.

The following lines have been added to the WHATSNEW file:

|        This is done by answering 'Y' to the "Default to Graphics at Login"
|        question in the PCBSetup : Configuration Options : Switches screen.
|
|        NOTE:  If you make this change, you must also edit your PCBTEXT file
|        to change record #149 so that it will properly reflect the default
|        you have selected.

                                         David W. Terry 

Date: 05-10-93 (07:20)              Number: 62703 of 63094 (Refer# 62702)
  To: HOWARD MICHALSKI
From: DAVID TERRY
Subj: BETA DOOR??              
Read: 05-10-93 (18:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When attempting to flag the /M version of PCB 15.0 I get the VROOM overlay
-> messages...  has /M been completed?

All versions of PCBoard are now overlaid, including the Multi-Port version.

                                         David W. Terry 

Date: 05-10-93 (07:24)              Number: 62704 of 63094 (Refer# 62558)
  To: MARIO POZZETTI
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (07:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Do I need to keep the IBKs created inside the msg base directory (I use both
-> IDX and NDX) I assume IBKs are only backups?

You assumed correctly, and no, you do not need to keep the backups.

You can use the /KILLBAK command line option for PCBPACK to automatically purge
the .IBK files, or you can manually delete them (or use a batch file).

-> 2. If I need to change the PCBOARD.EXE overlay size (and I have from 14 to
-> 18) because my system slows dramatically, and I have to set the attribute to
-> r/o, will it work? Sorry if this question is stupid :)

The OVLSIZE program cannot modify your executable unless you first remove the
read-only attribute.  So you could do the following:

        ATTRIB -R PCBOARD.EXE
        OVLSIZE PCBOARD.EXE 18
        ATTRIB +R PCBOARD.EXE

-> 3. I called voice friday and purchased PPL and I was told I could call in an
-> hour to pick up my copy in the Beta door but sofar niet, could you do
-> something?

Looks like the "mad rush" left you waiting... sorry about that, I'll take care
of it for you.
                                         David W. Terry 

Date: 05-10-93 (07:27)              Number: 62707 of 63094 (Refer# 30)
  To: LOUIS ZIRKEL
From: NANCY H. MILLER
Subj: EVENT WON'T RUN          
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93 18:08      



I'm afraid I've joined the list of people who can't get an event to run.

I have a single node system, running the /2 version.  (I get an error
when trying to edit EVENT.DAT because there is not USERNET.xxx on my
system.)  I have tried S and E events, no date entered or 00-00-00, all
YYYYYYY, all NNNNNNN, and having or not having extensions on the event
files (SSHIFT. vs SSHIFT.001).  Nothing seems to make it go.  I've read
and re-read EVENT.DOC and cannot find my problem.

Here are the event-specific screens:

                              Event Information

  Is a Timed Event Active               : Y
  Name/Location of EVENT.DAT            : C:\BBS\DAT\EVENT.DAT
  Location of EVENT Files               : C:\BBS\EVENT\

  For EXPEDITED Events:
  Minutes Prior to Suspend All Activity :  0
  Disallow Uploads Prior to Event       : N
  Minutes Prior to Disallow Uploads     : 15

                Ŀ
                 (2:3) Error Opening File - File not found  
                                                            
                         (no USERNET.xxx)                   
                         press any key to continue          
                


                              Event Information

                  Batch    Begin  End                         Last
       Act  Mod   File     Time   Time   SMTWTFS    Date      Date
                     
  1)    Y    E   MIDNIGHT  00:38  01:00  YYYYYYY
  2)    Y    E   MORNING   05:43  06:30  YYYYYYY
  3)    Y    E   WEEKLY    02:00  05:00  YNNNNNN
  4)    Y    S   SSHIFT    01:00  01:15  YYYYYYY
  5)    Y    S   SSHIFT    03:00  03:15  NYYYYYY
  6)    Y    S   SSHIFT    08:15  08:30  YYYYYYY
  7)    Y    E   SSHIFT    11:30  11:45  NNNNNNN  00-00-00
  8)    Y    S   SSHIFT    15:00  15:15  YYYYYYY  00-00-00
  9)    Y    E   SSHIFT    17:30  17:45  YYYYYYY  00-00-00
 10)    Y    S   SSHIFT    21:00  21:15  NNNNNNN  00-00-00
 11)    Y                                NNNNNNN
 12)    N                                NNNNNNN
 13)    N                                NNNNNNN
 14)    N                                NNNNNNN
 15)    N                                NNNNNNN

  Modes: E = Expedite (Non-sliding)  S = Sliding

========================================================================
:::
::: BOARD.BAT
:::
@ECHO OFF
C:
CD \BBS\PCB

::: PCB=/OLDINDEX maintains backward compatibility with V.14.5a doors
SET PCB= /OLDINDEX
SET DSZLOG=C:\BBS\PCB\NODE_1.LOG

::: The following commands prepare files needed by PCB, run the
::: executable PCB145, and handle remote calls, and doors
IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS
IF EXIST DOOR.BAT DEL DOOR.BAT
IF EXIST ENDPCB DEL ENDPCB

PCBoard

IF EXIST REMOTE.BAT REMOTE
IF EXIST DOOR.BAT DOOR
IF EXIST EVENT.BAT EVENT
IF EXIST ENDPCB GOTO END

::: if no special conditions, call BOARD.BAT
BOARD
:END
SET PCB=
SET DSZLOG=
EXIT
========================================================================
 Volume in drive C is CALPURNIA
 Volume Serial Number is 1771-6968
 Directory of C:\BBS\EVENT

.            <DIR>     05-08-93   9:21p
..           <DIR>     05-08-93   9:21p

(Continued in the next message)
---
  DeLuxe 1.12 #746s  InterNet Email: njh@seeker.mystic.com


Date: 05-10-93 (07:27)              Number: 62708 of 63094 (Refer# 6)
  To: LOUIS ZIRKEL
From: NANCY H. MILLER
Subj: EVENT WON'T RUN          
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

(Continued from the previous message)

WEEKLY            1194 05-09-93  10:17p
SSHIFT             870 05-09-93  10:40p
MORNING           4213 05-09-93  10:18p
MIDNIGHT           544 05-09-93  10:18p
        6 file(s)       6821 bytes
                    38445056 bytes free

NOTE:  All these events run fine if changed to .BAT files and run
"by hand".

NOTE:  I changed everything so that EVENT.DAT and the EVENTs were in
C:\BBS\PCB, and that didn't make any difference.
---
  DeLuxe 1.12 #746s  InterNet Email: njh@seeker.mystic.com


Date: 05-10-93 (07:39)              Number: 62713 of 63094 (Refer# 62576)
  To: GARY HEIMSTEAD
From: DAVID TERRY
Subj: Beta Report              
Read: 05-10-93 (14:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When uploading file attachments I'm getting the following message...
->
-> (WORK\USER_V15) is missing!   <-----  This is the one!
->
-> As you can see here, the file is found by ULP and processed.

Yup, the message is bogus.  Please ignore it until I have a chance to post new
code.
                                         David W. Terry 

Date: 05-10-93 (07:44)              Number: 62714 of 63094 (Refer# 62586)
  To: PETER BYRNE
From: DAVID TERRY
Subj: CNAMES file              
Read: 05-10-93 (13:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> changed PCBSetup handles the CNAMES and CNAMES.##@ files diferently now.
->        The down side is that you can no longer make changes with a text
->        editor and expect PCBSetup to read those changes back into memory
->        and copy them into CNAMES.##@.
->
-> This is a fairly majorr downside, as it is now not possible to perform
-> global changes on CNAMES.

Download CHANGE.ZIP and use it to perform global modifications on your setup.

It won't cover everything (cuz it can't) but it'll take care of a many of the
globabl modifications that have been done in the past.

                                         David W. Terry 

Date: 05-10-93 (07:46)              Number: 62715 of 63094 (Refer# 62588)
  To: PETER BYRNE
From: DAVID TERRY
Subj: Swapping PCBOARD.DATs    
Read: 05-10-93 (13:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> One of my nodes has several PCBOARD.DAT files with slightly different setups
-> which, until now, have been swapped in and out as required using the PREVENT
-> external event manager.
->
-> Is there any danger in doing the same thing with PCBOARD 15.0's internal
-> event manager?

PCBoard won't run the event that is SPECIFIED by your external event manager.

But if the "real question" here is...  Can you swap pcboard.dat files during
events, the answer is yes.
                                         David W. Terry 

Date: 05-10-93 (07:53)              Number: 62718 of 63094 (Refer# 62602)
  To: CHRISTINE BLOUNT
From: DAVID TERRY
Subj: pcbfiles.lst             
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Can you explain how to PROPERLY use the ALLFILES.LST.  I have checked the
-> whatsnew and, to be honest, I don't understand it.

Think of it this way:

        ALLFILES.LST is nothing more than a DLPATH.LST ... but it is COMMON to
        ALL areas of the BBS if it is specified.

In other words, usage of ALLFILES.LST is identical to DLPATH.LST.  You put the
same kinds of paths and/or index files in it.

The only difference is that, if ALLFILES.LST is specified, PCBoard will use IT
instead of the DLPATH.LST file when determining if a file (to be uploaded)
already exists on the system.

The SOLE PURPOSE of this new capability is this:

        To let you scan for prior existence of the file IN ALL CONFERENCES
        before allowing the caller to upload the file.

So use it the same way you have used DLPATH.LST in the past.  But include paths
(or index files) for ALL conferences.

NOTE:  If all of your conferences have the same DLPATH.LST file then there is
absolutely no reason to use ALLFILES.LST.

                                         David W. Terry 

Date: 05-10-93 (07:58)              Number: 62720 of 63094 (Refer# 62605)
  To: NANCY H. MILLER
From: DAVID TERRY
Subj: QWK BATCH FILE           
Read: 05-11-93 (06:33)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> A question about the documentation - WHATSNEW suggests the following as part
-> of PCBQWK.BAT:
->
-> if %1==COMPRESS pkzip -ex -m %2 %3messages.dat %3control.dat %3*.ndx
->
-> For PKZIP 2.0, shouldn't that be -m-, so as not to delete the work
-> subdirectory, or is that not a problem?

We're using PKZIP 2.0 here...  we are also using the SAME batch file that I
posted for everyone else to use.

My guess is that "-m-" is only required if you issue a "*.*" parameter as the
list of files to be moved into the ZIP file.  In this case, the files are
individually wildcarded so it appears not to require "-m-".

                                         David W. Terry 

Date: 05-10-93 (07:59)              Number: 62721 of 63094 (Refer# 62606)
  To: NANCY H. MILLER
From: DAVID TERRY
Subj: Question Re: FILE_ID.DIZ 
Read: 05-11-93 (06:33)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Other than by turning upload verification off, is there a way to select
-> whether or not you want to force FILE_ID.DIZ as the upload description?

There isn't.
                                         David W. Terry 

Date: 05-10-93 (08:02)              Number: 62722 of 63094 (Refer# 62609)
  To: JIM CONDON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Not really a bug but, a problem that I can find the answer to in the online
-> help in PCBSM, whatsnew, or apps.  At one point my file attachs was almost
-> working right.  It was renaming the file with a .000 extension and putting
-> it in \pcb\gen.  I tried to view it with PCBFV and it didn't view it (wring
-> extension I guess).  My question is how do I view it with pcbfv and now

Step 1:  Read the message that holds the file attachment
Step 2:  Type "V" at the end of message command prompt

PCBoard will then copy the file over to the work directory (with the
APPROPRIATE extension for the file) and then call up PCBTEST.BAT to view the
file.

In other words, do NOT use the "F V FILENAME.ZIP" command to view your file.

The "F" in the above command is telling it to go through the "file subsystem"
to view the file.  But the file is NOT a normal download... it is a file
attachment.  As such, you must go through the "message subsystem" to flag or
view it.

So the first step is to read the message that holds the attachment and then use
the commands available to flag or view the file.

                                         David W. Terry 

Date: 05-10-93 (08:02)              Number: 62725 of 63094 (Refer# 62610)
  To: KEN MILLER
From: DAVID TERRY
Subj: SubMenus                 
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Could you copy your reply to the RIME-Support conference so I can read it on
-> my BBS since it takes so long to get into SA.

NO.

All reports must be submitted directly in THIS conference.  All replies will
also be placed in this conference.

No exceptions.
                                         David W. Terry 

Date: 05-10-93 (08:04)              Number: 62727 of 63094 (Refer# NONE)
  To: ALL
From: GARDINER JONES
Subj: EVENT not running - possible fix
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

I saw several messages the last few days from people who said their
EVENTs wouldn't run after upgrading to PCB15.0 beta code.  I had the
same problem.  After pulling my hair out for a day I came across a fix.
The PCBSETUP program took my original defaults and tried to included
them properly into the new PCBOARD.DAT file (or is it PCBOARD.SYS?)
Anyway, the Event selection had stuffed my path "D:\PCB\GEN\" into the
LOCATION of my events files, and I had dutifully put my event files into
the PCB\MAIN subdirectory as suggested by the documentation.  I
corrected this entry to point to \PCB\MAIN and, voila, my events now
run!

Date: 05-10-93 (08:04)              Number: 62728 of 63094 (Refer# 62666)
  To: DON REID
From: DANIEL CHLARSON
Subj: QWK problems             
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Here are some messages I've received from callers concerning QWK and
-> also the QMail4 door...
->
-> "When I attempted to download messages there was a PCBoard error
-> message that said something like, "Inform your sysop to set the
-> read/write buffers lower."  It did not allow the download."
->
-> "...after attempting a QWK command upload which failed the
-> post-upload compression, the qmail4 door does not accept uploads
-> either."
->
-> "... No upload directories are available, Don.  Check your config..."
->
-> "...it still won't process my uploaded qwk file, and it won't finish
-> sending me my downloaded qwk file."

This DOES NOT qualify as a beta report.  Do some investigating on your
end, come up with SOME FACTS and then get back to us.

Daniel
Salt Air Sysop

Date: 05-10-93 (08:05)              Number: 62729 of 63094 (Refer# 62667)
  To: DON REID
From: DANIEL CHLARSON
Subj: USERNET.XXX              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> As I mentioned in an earlier message, when I try to load Node 2
-> (using directory \PCB2), I get the message:
->
-> C:\PCB\MAIN\USERNET.XXX: format error
-> Exiting to DOS!
->
-> If I delete USERNET.XXX and try to load Node 2, it loads just fine.
-> However, then when I try load Node 1, I get the identical error
-> message.
-> What am I doing wrong? Thanks!

Are you running the same version of code (same date even) on all
machines?

Daniel
Salt Air Sysop

Date: 05-10-93 (08:06)              Number: 62731 of 63094 (Refer# 62612)
  To: MIKE JOHNSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> did a [N]ew files search.   I noticed that I now seem to have 2 recent
-> upload directories.

One of them is a "fake" upload directory ... one that you MANUALLY installed.

The other is a "new feature" in v15.0.  Here is the relevant information from
the WHATSNEW file:

 changed The behavior of the "Make All Uploads Private" switch.  It continues
         to force uploads to go into the private upload directory.  But it no
         longer tells the caller the "All uploads are private" when the caller
         tries to view the public upload directory.

         If the Public Upload Directory is defined (non-blank) the caller can
         now view it!

         However, by making the Public Upload Directory blank, PCBoard will
         revert back to the message "all uploads are private" and not allow
         the caller to view uploads.

         This takes care of the problem where some systems have defined area
         #99 (or some other number) as the Upload Directory, thereby disabling
         the use of commands such as "F U", "N U S" or any other command that
         would access the (U)pload directory.  This was forced on sysops
         because of the "all uploads are private" status.  But no longer.  Now
         all uploads can be forced into the private directory while allowing
         the sysop to move the uploads into the public directory after they
         have been previewed or scanned.

         Further information for clarification of the above:

         OLD WAY OF DOING THINGS
         -----------------------
         - Force all uploads private
         - Sysop scans uploads before posting
         - Sysop moves those files deemed appropriate to directory #13 (or
           whatever directory you might have chosen)
         - Sysop tells callers to scan directory #13 to find new uploads AND
           has to explain to everyone why the F;U command does not work, also
           the N;U;S command, also the L;U command, also the Z;U command, etc.
           What a hassle!

         NEW WAY OF DOING THINGS
         -----------------------
         - Force all uploads private
         - Sysop scans uploads before posting
         - Sysop moves those files deemed appropriate to directory #13 (or
           whatever directory you might have chosen)
         - Now, because directory #13 is seen as the UPLOAD directory, the
           callers can now use the F;U, N;U;S, L;U and Z;U commands.

         What this change has done is allowed you to set up a directory which
         PCBoard can see as the "U" directory.  A directory that your callers
         can reliably use to find new files no matter what number the directory
         is because they can now type "U" instead of "13" (or whatever the
         directory number is on your system)

         You, the sysop, are now free to insert new directories ahead of the
         upload directory, perhaps making the upload directory #14 now, without
         causing a problem for your users because they can go right on typing
         N;U;S to get a list of new files in the upload directory.  PCBoard
         automatically knows which directory is the 'Upload Directory' now even
         though you are forcing all uploads to be private.

So if you don't want callers to view this "new" upload directory, REMOVE it.
Blank it out.

But in reality, the BEST SOLUTION (in my opinion) would be for you to get rid
of your "fake upload directory" and now allow callers to use the "U" command to
find it.

This is because the "U" command ALWAYS works.  You can add new directories,
remove old directories, and your upload directory number might change but the
"U" command will always be valid.
                                         David W. Terry 

Date: 05-10-93 (08:12)              Number: 62734 of 63094 (Refer# 62674)
  To: RICK WELSHANS
From: DANIEL CHLARSON
Subj: OTHER:  BETA DOOR 05-07-93 01:01:01
Read: 05-11-93 (00:47)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> BUT, when I came in today, it showed the latest (5/7) beta as having
-> been downloaded.  I also could not flag multiple, individual files
-> all at once to re-create the BETA.ZIP.  Bug?

Possibly, but not likely.  The reason that it showed the latest as being
downloaded was because it had created the zip for you.  To the beta
door, that means it's been downloaded.

As for the other........I don't know.  I'll get someone to look into it.

Daniel
Salt Air Sysop

Date: 05-10-93 (08:20)              Number: 62736 of 63094 (Refer# 62631)
  To: BILL SAMPSON SR
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (00:15)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David, I am getting swap failure code:2 registered in my callers logs.

This indicates that the SWAP routines were not able to copy the pcboard
environment (the executable and data in use) out to EMS memory prior to
shelling out to DOS.

You may need to increase the amount of available EMS memory you are giving to
the session.

If that doesn't help then you may need to try a different EMS memory manager.

-> Is this something I should be concerned with?

Yes and no.  If it cannot swap to EMS then it will just SHELL out instead.  But
this will not give your shelled-to-process as much memory so it could still be
a problem.

Another alternative would be to give the session ZERO amount of EMS memory to
work with.  This will force PCBoard to swap out to disk and it should work
*every* time.
                                         David W. Terry 

Date: 05-10-93 (08:22)              Number: 62737 of 63094 (Refer# 62633)
  To: CHRIS SLOYAN
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (09:54)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Ok, I am just repeating a message I saw someone else write for the sake of
-> letting you know it was not JUST HIM. I am also finding that PCB has created
-> another Uploads file area and in addition to that, it is my PRIVATE UPLOADS
-> area and has been available to all users if they want to go in there. Please
-> tell me I can get rid of this as it is very annoying.

The message I wrote to him, #62731, is public.  You can read it... or look it
up in your WHATSNEW file.  This "new upload directory" is documented fairly
well in the WHATSNEW file.

See message #62731 for further details.

-> Also, Will I be able to purchase JUST a copy of the 15.0 docs when they are
-> finished?

Manual only (without disks) possibly.  But no guarantees as this point.  Please
hold any further "purchasing questions" until we announce the answers.  The
information simply is not available (to you or to us) and won't be until we get
things closer to being finished.
                                         David W. Terry 

Date: 05-10-93 (08:24)              Number: 62738 of 63094 (Refer# 62635)
  To: RAY CRAMER
From: DAVID TERRY
Subj: Slow Downloads           
Read: 05-10-93 (13:12)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> This is directed towards Houston area Sysops.  Is anyone in the
-> Houston,Baytown, Pasadena, Laporte Texas area having trouble with choppy low
-> CPS downloads from Salt Air?  I have been thinking it was me alone having
-> downloads of 400-800CPS for several months until tonight.

It's definitely "not just you" ... we have had EXTREMELY WET WEATHER this year
and MaBell blames the wet ground conditions for the line noise being
experienced.

Wish there was something WE could do about it.  There isn't.

                                         David W. Terry 

Date: 05-10-93 (08:37)              Number: 62742 of 63094 (Refer# 62646)
  To: MIKE DEMSKI
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (11:25)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Now, with a 64k overlay buffer setup, does that mean that PCBoard's
-> executable will take 64k of ram, and then certain data files will take up
-> some ram for a total of about xxxk ram?

It means only one thing:  The overlay buffer size is 64K.

-> What approximate total ram are we looking at in this case?  (64k, 100k,
-> 350k, 400k, or more needed?)

This is a question that is best answered BY YOU on your OWN system.

The reason being, that under MANY different setups, PCBoard can require MANY
different amounts of memory.

Here is a very simple method for you to determine how much memory is in use by
PCBoard:

   Step 1)  Type "MEM" to get the amount of FREE MEMORY before loading PCBoard

   Step 2)  Load PCBoard and log into the system.  Look at the BOTTOM status
            line where you see a "K" figure.  Record that number.

   Step 3)  Multiply the value from step #2 by 1024 to turn the K-bytes value
            into a bytes value.

   Step 4)  Subtract the value in step #3 from the value in step #1.  And there
            you have it.  Now you know how much memory PCBoard is using.

Here is an example scenario:

-> Step #1
-> -------
-> MEM
->
->     654336 bytes total conventional memory
->     654336 bytes available to MS-DOS
->     561024 largest executable program size
->
-> Step #2
-> -------
-> 1(Local) DAVID TERRY - SALT AIR SUPPORT STAFF              ALT-H=Help   0 08
-> G (05-10-93)  Sec(0)=250  Times On=1725  Up:Dn=8:573          12 334K 412 08
->
-> Step #3
-> -------
-> 334K times 1024 equals 342016 bytes
->
-> Step #4
-> -------
-> 561024 bytes minus 342016 bytes equals 219008 bytes (or 213K bytes).


NOTE:  When you log into the system LOCALLY you also allocate a "scrollback
buffer" which is NOT available to callers online from remote.  So a local login
will actually require MORE memory than a remote login.  The above example is a
*real* example right here on my test system and was performed from a local
login - but one which had the scrollback buffer set to 0 (disabling it).

Anyway, the point is, PCBoard v15.0 still has a very low appetite for memory in
spite of all of the many new features.  :-)

-> I have enough ram dedicated to both nodes (535k each node) that I would like
-> to minimize swapping and maximize performance within PCBoard.

With 535K you'll have PLENTY of memory.  You could either reduce the window
size or you could increase the overlay buffer size.

                                         David W. Terry 

Date: 05-10-93 (08:37)              Number: 62743 of 63094 (Refer# NONE)
  To: ALL
From: JOE WHITE
Subj: Slow Drive Batch File    
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Has anyone got a batch file that will enter the comment in a zip file
from the slow drive batch file?

In pcbsetup I have gone under G: Configuration Options, File Tranfers,
Slow Drive BatchFile.  I placed a batch file in this location but it
seems to be overlooked.  I have the slow drive set for E which is my ROM
drive.  The files are being placed in drive D:\temp1 2 or 3 depending on
which node it is.  I guess I need someone to send me the contense of
what there batch file looks like and what was put in the the pcbsetup.
Thanks to anyone that may be of help.

                                    Joe White
                                    The Georgia Bulletin Board System
                                    (404) 962-5116

Date: 05-10-93 (08:43)              Number: 62744 of 63094 (Refer# 62649)
  To: MARK COMPTON
From: DAVID TERRY
Subj: stuff                    
Read: 05-11-93 (01:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I noticed that the 'Scan Message Base Since Last Read' has been removed when
-> one has personal mail waiting.  Is this by design?

You have noticed incorrectly (or not "completely" if you prefer).   :-)

If you have personal mail waiting then PCBoard will let you read the mail
BEFORE you get to the "scan message base since last read" prompt.
======

That doesn't mean the prompt is gone.  It is just trying to get you to read the
mail as early as possible.  Once you are done reading the mail, then you WILL
be asked to scan for new mail.

-> Also, how does one change the directory where files are copied from slow
-> drives (CD-ROMS)?

PCBSetup : File Locations : System Files & Directories :  Location of Temporary
Work Files.

You can go to that question on the screen and press F1 for further help on the
subject.

-> Other than that, everything's great!  This is my first beta cycle with PCB,
-> and I'm pleasantly surprised how easy everything has been.  Keep up the good
-> work!

I just wish *everyone* had an easy time of it.  <tired smile>

                                         David W. Terry 

Date: 05-10-93 (08:45)              Number: 62745 of 63094 (Refer# 62650)
  To: MARK COMPTON
From: DAVID TERRY
Subj: possible bug             
Read: 05-10-93 (20:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> In the last two days, I've run across something that may be a bug on your
-> system or maybe in the new code.  While attempting to download the new beta
-> messages with 'QWK D' using Ymodem-G, your system dropped carrier on me
-> while I was giving Telix the download path.

This is called LINE NOISE.  Pure and simple line noise.

The system does not "drop carrier".  To do so would require that DTR be
dropped.  DTR is *not* being dropped except in response to the (G)oodbye
command.

However, your ERROR CORRECTING modem is programmed to PURPOSELY hang up the
connection if there is an excessive amount of line noise.  This is "normal
behavior" for your modem and should be expected.

I wish we could fix the line noise, but we are powerless to do so.

                                         David W. Terry 

Date: 05-10-93 (08:45)              Number: 62746 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: DAVID ORCUTT
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-06-93  


PCBOARD.EXE  452464  05-06-93 6:24p

I'm having EVENT problems.. I have the batch files set ok, with
my node 7 doing  MAILRUN (file is named MAILRUN.007), and the
path to the file is correct.
I logged on to the node 10 minutes prior to the event, and I was
given the warning message that an event was pending and my time is
reduced for the event, so it's finding the node-specific batch file.
The event will not run. If I log on a few minutes after the event was
supposed to start there is no warning message, and my full time is
restored.
Rechecked everything in PCBSETUP, but could not find anything out of
place... Any ideas?
Dave Orcutt
PVCC User Group BBS


Date: 05-10-93 (08:47)              Number: 62747 of 63094 (Refer# 62651)
  To: BARLY REDSAR
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (09:38)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am having problem when I try downloading messages thru QWK D.  The message
-> error I received is "Error Compressing File".  Probably that something that
-> I setup incorrectly.  Can you give some direction or hints?

Download PCBQWK.BAT from this system and put it in each node's subdirectory.

Also, see the WHATSNEW file for further details on this subject:

         To enable the QWK capability, you must create a batch file, either in
         your PCB directory or somewhere in your path, called PCBQWK.BAT.  A
         sample of what this would look like is as follows:

           if %1==COMPRESS pkzip -ex -m %2 %3MESSAGES.DAT %3CONTROL.DAT %3*.NDX
           if %1==EXTRACT  pkunzip -o %2 %3

         The %3 value, when executed, will be your "Work Directory".  You must
         ensure that this directory is a valid directory and that it is NOT
         your current directory.  Example:

              PCBSetup : File Locations : System Files and Directories

              Location of Temporary Work Files  : WORK\

         This will require that you exit PCBSetup answering 'Y' to save the
         change AND create the new subdirectory.  The WORK\ directory will be a
         subdirectory off from the 'current directory', whatever that may be.
         You must therefore ensure that ALL NODES have the work directory
         created.  You can do this by running PCBSetup for each node, or by
         manually making the directories.

-> Also, I can not seem to make the chat work.  For example: if i would like to
-> chat somebody one node 2, I entered "CHAT 2" and PCBoard give me a selection
-> for group chat or enter node # or enter to quit.  I try to enter the number
-> 2 but the board just would not take the number.

Type "CHAT G" to go into Group Chat.  From there you can CALL another user into
chat.

The old method of issuing "CHAT #" is no longer valid and cannot be used.  The
new method is more appropriate to the "group" nature of the new chat.

-> Is it possible for you to answer to questions thru RIME or U'NI?

Nope, all messages will be posted in this conference only.

                                         David W. Terry 

Date: 05-10-93 (08:49)              Number: 62748 of 63094 (Refer# 62652)
  To: BARLY REDSAR
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (09:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Where can I find the Help file for v15.0?

What "help file" are you looking for?   (note that your question is singular)

There is a "single" help file for PCBSM / PCBSetup / PCBFiler which you can
download through the BETA door.  It is called PCBSM.HLP and you have probably
already downloaded it.

There are other "help files" (plural) that PCBoard has used.  These have NOT
YET been updated.  Please continue to use your v14.5a help files until new ones
are posted.  We will announce the new help files here in this conference once
they are available.
                                         David W. Terry 

Date: 05-10-93 (08:52)              Number: 62749 of 63094 (Refer# 62653)
  To: CHUCK GOSS
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I've noticed an occurance in that when I log on locally I get the prompt to
-> read my personal mail now.  I select yes, and read through my mail in the
-> different conferences.  Then I log off.  Later return and log on again and
-> am prompted to read the same mail.  Finally, after the third log on attempt,
-> I wasn't prompted.

If you answer 'Y' to the question, you will be shown your mail in READ ONLY
mode.

This is to avoid LOSING any other mail that is NOT addressed to you.

You will be RE-prompted everytime NEW MAIL is waiting for you.  But your LMR
pointers will not be updated until you read the mail in non-Read Only mode.

You will NOT be prompted if you have already read the mail.  Only if NEWLY
POSTED mail is waiting for you.

But you will CONTINUE TO SEE old mail until your LMR pointers are beyond those
messages.  A message is not really "old" until your LMR pointers are PAST the
point where they are found.
                                         David W. Terry 

Date: 05-10-93 (08:54)              Number: 62750 of 63094 (Refer# 62656)
  To: RANDY DAVILA
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (23:09)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am having problems with the reading of messages.  When I log on and read
-> the mail that I have waiting and exit the board and back on I get the same
-> mail.

Please read the message JUST PREVIOUS to this message (I just answered this
question).  (#62749)
                                         David W. Terry 

Date: 05-10-93 (08:55)              Number: 62751 of 63094 (Refer# 62657)
  To: FRED MCCLAREN
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (01:11)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->    Is there any program available that will force previous users to fill in
-> data for the new user fields? (address, mother's maiden name, etc.)

A PPL program can be used to do this.  Check directory #2 as well as the Upload
Directory in this conference.  I know at least one PPL (for this purpose) has
already been posted and there may be even more.

                                         David W. Terry 

Date: 05-10-93 (09:00)              Number: 62752 of 63094 (Refer# 62658)
  To: FRED MCCLAREN
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (01:14)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

->    Could you provide some more info on configuring the Attached file option?
-> I have it setup to put it in my public upload directory, but after uploading
-> (which appears to go fine) it isn't there or anywhere else on disk.

Do _NOT_ put it into your public upload directory.

A file attachment is NOT THE SAME as an uploaded file and CANNOT be downloaded
the same way.

The NAME of the file, on a file attachment, is CHANGED in order to allow
multiple messages to have indentically named attachments.  For example, in a
Tech Support environment you might expect many people to upload AUTOEXEC.BAT.
That would not work out very well if the "stored name" of the attachment was
AUTOEXEC.BAT because then only the FIRST ATTACHMENT would be successful.  Every
attempt to attach AUTOEXEC.BAT thereafter would have to fail.

PCBoard purposely AVOIDS that problem.

The attachment lands in a special attachment directory (NOT your upload
directory).  And it is RENAMED to avoid collisions with existing files.

The first upload of AUTOEXEC.BAT will be found in your attachment directory as
AUTOEXEC.000.  The second attachment of AUTOEXEC.BAT will be in the same
directory as AUTOEXEC.001.

The message itself contains the translation information necessary to receive
the proper attachment.

Therefore, the ONLY WAY to obtain the proper file attachment is to read the
message and type FLAG or V (to flag for download or view the file).

You will NOT be able to just get to a command prompt and type "D AUTOEXEC.BAT"
because AUTOEXEC.BAT does not exist.  That is why you must first read the
message and then use the file attachment commands (FLAG/V) to access the file.

                                         David W. Terry 

Date: 05-10-93 (09:06)              Number: 62753 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ANDY KEEVES
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBOARD.EXE - 05-07-93                                 



We missed the event on node 8 at midnight last night and on Saturday night.
These are the first 2 events we have missed since the great event battle of
1993 - no idea whatto tell you beyond this brief report......

Date: 05-10-93 (09:12)              Number: 62754 of 63094 (Refer# 62659)
  To: KEVIN COLLINS
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When I first installed the beta, my graphics-mode messages did exactly what
-> they do here - when proceeding to a 2nd page, the header remained in place,
-> with only the text below scrolling - a neat new feature.  BUt shortly after
-> installation, this no longer worked for some reason.. messages and headers
-> now scroll as in prior versions.  What might have changed/gone wrong?  Only
-> thing I could think of was that ANSI.SYS wasn't loaded, but that wasn't the
-> problem.. any clue?

ANSI.SYS has no effect on PCBoard... it hasn't had any effect on PCBoard since
the days of v14.2 (v14.5 came out with its own built-in ansi driver).

Anyway, to answer your question...  use the (W)rite User Info command and
answer the following questions this way:

        Clear screen between each message:      YES
        Scroll long messages:                   NO

Also, when you log into the system you must either select graphics (answer 'Y'
at the "do you want graphics?" prompt) or else PCBoard has to be able to
auto-detect ansi (if you answer 'N' instead).

If PCBoard doesn't know that you have ANSI (on your remote COMM program) then
it must avoid using ANSI commands.  And the ability to lock headers at the top
of the screen *requires* ANSI commands so that feature will be disabled.

NOTE:  Local logins are always assumed to have ANSI capability regardless of
whether you select graphics or not.  The only exception is if you use the
"M CTTY" command to disable ANSI.

                                         David W. Terry 

Date: 05-10-93 (10:43)              Number: 62755 of 63094 (Refer# 62515)
  To: BILL ATHINEOS
From: MARK DURSTEWITZ
Subj: OTHER:  PCBOARDEXE 05-04-
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

  >-> I am having a problem with the feature QWK. When i try to download the ma
  >-> packet i get an error.
  >-> Error compressing file.
  >-> Capture aborted. Read pointers restored.
  >->
  >-> I did what it said in the doc but i can't seem to figure out why, any ide
  >-> I put the batch file in the pcb directory!

Bill,
I had the same problem but fixed it this way.  Although the WHAT'SNEW
file doesn't mention this part, the READ1ST does.  Go into PCBSETUP
:COnfiguration Options: Messages : Name of capture File - - and put the
name you want for the QWK packet there.  That should solve your problem!

        It was a little confusing as you needed to read both documents
to get all the steps.

Mark

Date: 05-10-93 (08:59)              Number: 62756 of 63094 (Refer# NONE)
  To: ALL
From: LOUIS ZIRKEL
Subj: New PCBPACK.EXE Posted   
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

05/10/93 09:00 - PCBPACK.EXE
----------------------------
- Added the ability for PCBPack to search the PCB environment variable for
  the /OLDINDEX switch and use it if found.

05/07/93 12:00 - PCBPACK.EXE
----------------------------
- Added a "status bar" that shows the percentage of the current message base
  that PCBPack has compressed so far.
- If ESC was pressed during use of the /UPDATE parameter, it would be ignored
  and the process would run to completion.
- If a conference didn't have a name defined, but all other information was
  present then /UPDATE would still try to process those conferences.


Date: 05-10-93 (09:27)              Number: 62758 of 63094 (Refer# 62660)
  To: BART SABATELLI
From: DAVID TERRY
Subj: time stamping            
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 05-09-93 (07:49) (1) RONALD STEPP Off Normally
-> **************************************************************
->     NO CONNECT / NO CARRIER
-> **************************************************************
->     NO CONNECT / NO CARRIER
-> **************************************************************
->     Carrier Lost ...
-> **************************************************************
->     Carrier Lost ...
-> **************************************************************
-> 05-09-93 (17:28) (1) MICHAEL REEVES (14400E) (A) WAUSAU,WI.

The above extra messages appear when you tell PCBoard to "Monitor Missed
Connections".

The first two examples at the top indicate that a RING DETECT occcured but that
your modem responded "NO CARRIER" before a "CONNECT" message ever occured.

In other words, if the caller used a modem to dial into your system, the
handshaking process NEVER COMPLETED to the point of "connecting" the caller.

The second two messages indicate that a CONNECTION was established by the
caller (so a modem must have been used) but that the caller lost carrier
(decided to hang up, or there was too much line noise and the modem hung up)
prior to logging into the system.

-> 1) were 4 different calls lost

Lost?  No...  missed would be a little more accurate.  The phone rang 4 times,
yes, but in two cases a connection was never established and in two more cases
the caller never logged in before losing carrier.

-> 2) would the time spacing look like two-callers
-> 3) was it the next caller (Michael Reeves) that actually made it on his 5th
-> call?

You cannot make that assumption.

-> Everything else in the callers log is stamped well, this should be too.

You can do that if you want.  Just edit your PCBTEXT file and add @systime@ in
front of the "Lost Carrier" and "NO CONNECT" messages.

Here is a sample batch file you could use to perform the change:

   MKPCBTXT C:\PCB\GEN\PCBTEXT /I:34 "@systime@ NO CONNECT/@optext@"
   MKPCBTXT C:\PCB\GEN\PCBTEXT /I:215 "@systime@ Carrier Lost..."

NOTE:  the systime and optext variables must be in uppercase.  Also, C:\PCB\GEN
may not be the proper location for your pcbtext file.  Adjust the batch file as
necessary for your system.
                                         David W. Terry 

Date: 05-10-93 (09:32)              Number: 62759 of 63094 (Refer# 62166)
  To: DAVID TERRY
From: PEAK PERF
Subj: BETA report              
Read: 05-10-93 (10:44)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

I think the main problem was not enough files alocated in our config.sys
I increased them and it seems to be working OK now.

Thanks, Brad.

Date: 05-10-93 (09:39)              Number: 62760 of 63094 (Refer# 62661)
  To: BART SABATELLI
From: DAVID TERRY
Subj: PCB 15.0 - UPLOADING    
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When a user uploads a file - the board prompts him for a description BEFORE
-> the D/l...in reading the "WHATSNEW" I noted that 15.0 is supposed to test
-> the file first and see if there is a FILE_ID.DIZ present...

This is not quite accurate.

PCBoard detects FILE_ID.DIZ files in an UNANNOUNCED upload and avoids asking
for a description after the unannounced upload is received if the description
is *already* available.

If you ANNOUNCE the file, however, then you must also describe the file.

Note the words "after an upload" in the description that was in the WHATSNEW
file:

 added   Immediate detection, after an upload, of the existence of a
         FILE_ID.DIZ file within a .ZIP or .EXE file.  If a FILE_ID.DIZ file
         is found AND the sysop has configured the system to verify uploads,
         the user will *not* be asked for a description.

I'll add the following to the above for the next release of WHATSNEW:

|        NOTE:  This ability to skip asking for a description takes place only
|        AFTER an unannounced file is received.  Normally PCBoard would prompt
|        for a description AFTER RECEIVING an unannounced file.  But in the
|        case where a file description accompanied the unannounced file, this
|        step would be redudant so PCBoard skips asking the caller for a
|        description and immediately shells out to PCBTEST.BAT which then
|        extracts and incorporates the included (FILE_ID.DIZ) description.

                                         David W. Terry 

Date: 05-10-93 (09:41)              Number: 62762 of 63094 (Refer# 62661)
  To: BART SABATELLI
From: DAVID TERRY
Subj: PCB 15.0 - UPLOADING    
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> If you attempt an upload an there is any file in the path [DOS AND PCB] that
-> has the same name but a different extention, you get a dupe file
-> message...is there some way to instruct the prog what extentions to check?

Nope.  It is just replacing your "U FILENAME.ZIP" with a scan for "FILENAME.*"
and reporting any matches found.

-> Finally: I have discovered that in 15.0 you cannot use the quick logon
-> feature: [FNAME;LNAME;PWRD] UNLESS...you use the correct password...in 14.5
-> if you entered that line with the wrong password, you were prompted for the
-> correct password...now if you enter the wrong password you are treated as a
-> new user....yes?

This is correct.

Version 15.0 opens up a slew of possibilities for name collisions - due to the
new ALIAS capability - and so the ability to receive a bad password and know
that it was the SAME USER (and not a collision on an existing name) had to be
modified.
                                         David W. Terry 

Date: 05-10-93 (09:43)              Number: 62763 of 63094 (Refer# 62346)
  To: MARC MEDOW
From: LOUIS ZIRKEL
Subj: My event                 
Read: 05-11-93 (05:48)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Absolutely nothing.  Just synonyms for people who think one word makes
more sense.

        -= Louis Zirkel III =-

Date: 05-10-93 (09:47)              Number: 62765 of 63094 (Refer# 62493)
  To: ED LUCAS
From: LOUIS ZIRKEL
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> This isn't a bug report...correct me if wrong. PCBpack is creating temporary
-> files. If one tries to run PCBPack on message bases in the same path from
-> different nodes, then there will be a problem? A lot of us are now dealing
-> with 1,000s of conferences and it would be nice if we could pack different
-> ranges of confs from different nodes without a conflict.
        You're basically correct, but the temporary files that it creates
aren't "static" in that if the name that PCBPack wants to use exists then it'll
try a different name.  You shouldn't have a problem.  Are you experiencing some
sort of problem attempting to do this?

        -= Louis Zirkel III =-

Date: 05-10-93 (09:49)              Number: 62766 of 63094 (Refer# 62552)
  To: BLAINE BINKERD
From: LOUIS ZIRKEL
Subj: Event/PCBPack observation
Read: 05-10-93 (17:55)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> PCBPack date/time:  5-04-93 1:08pm
-> Symptoms:  PCBPack does not appear to pack the users base.
        PCBPack does NOT pack the users base any more.  This task has been
handed over to PCBSM as it reduces the amount of duplication of program code.
Trying to maintain the same code in two modules is fairly difficult and with
the ability to pack while users are online now, PCBSM is by far the better
choice for packing the USERS file.

        -= Louis Zirkel III =-

Date: 05-10-93 (09:51)              Number: 62767 of 63094 (Refer# 62662)
  To: BART SABATELLI
From: DAVID TERRY
Subj: beta conf                
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> How about this.  Let me have net status to Beta conf so the (over 100) pcb
-> sysops can communicate to u in an expedient manner from their boards, since
-> they call here every night anyway.

Everyone that is going to report to us should do so directly.

We do not want a "middle man" interfering with the ability to collect,
interpret, understand, reply to, and process beta reports.

The idea presented, while it sounds good to the many sysops out there, has
several flaws in it:

  - The messages would not be sent on a timely basis

  - The replies would not be received on a timely basis

  - There would be inherent delays INTERFERING with our ability to collect
    data on the beta reports (a beta report is often incomplete and requires
    follow-up information).  Such delays will only make it HARDER for us to
    support the sysops.  This is NOT a desirable situation for us nor for
    the sysops that are beta testing.

  - Making it "easier" to post beta reports would actually open the flood
    gates to an already over-flowing stream of messages.   Sysops would rather
    post THEIR OWN individual message and get THEIR OWN reply back than to
    get the messages that are already online here and waiting for them to read.
    In effect, they would ask and re-ask, and duplicate messages to the point
    of making it IMPOSSIBLE for us to do any REAL work around here.

If the caller will not be calling here on a regular basis (for beta testing
purposes) then we suggest avoiding the beta cycle and waiting for the "release"
version of PCBoard to become available.

-> I did this with MSI when WC3 came out, and it worked well as a private conf
-> only for beta test people.

I suspect they have a much smaller group of testers (due to their smaller
customer base).

I have looked in on MSI tech support conferences before (netmail systems that
carry their tech support conferences) and they simply do not have any where
near the kind of traffic that we get due to the larger number of people out
there who are using PCBoard.

-> If the answer is no, then I will forward all I can 'keep an eye on', so that
-> it does not end up in the echo conf.

I'd really prefer that if the sysop is going to participate in the beta, that
the sysop also call direct for support.

But thanks for the offer to help, it *is* appreciated (even though refused).

                                         David W. Terry 

Date: 05-10-93 (09:52)              Number: 62768 of 63094 (Refer# 62595)
  To: BILL MARTIN
From: LOUIS ZIRKEL
Subj: BETA report              
Read: 05-11-93 (00:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Sorry that was one for my debugging purposes that slipped through.

        -= Louis Zirkel III =-

Date: 05-10-93 (09:55)              Number: 62769 of 63094 (Refer# 62753)
  To: ANDY KEEVES
From: LOUIS ZIRKEL
Subj: BETA report              
Read: 05-10-93 (11:11)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Thanks.  I don't know where to look, but I've got some other work to do
that may affect your problem (for the better I'd hope ;-)

        -= Louis Zirkel III =-

Date: 05-10-93 (10:00)              Number: 62770 of 63094 (Refer# 62673)
  To: TIM ELSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> ECHO OFF
-> O:
-> CD \PCB6
-> SET DSZLOG=PCBDSZ.LOG
-> IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS
-> IF EXIST DOOR.BAT DEL DOOR.BAT
-> IF EXIST ENDPCB DEL ENDPCB
-> PCBOARD.EXE
-> IF EXIST REMOTE.BAT REMOTE     <----  where is your EVENT.BAT ???
-> IF EXIST DOOR.BAT DOOR         <----
-> IF EXIST ENDPCB GOTO END
-> net clock \\node9
-> NODE6

The above was your complete message.  There was no question inside of the
message to direct me to anything specific.

However, I noticed that your board.bat file IS MISSING the line that would
enable it to run your events.   Without it, your events will definitely not do
anything except recycle the board.

Here is a proper BOARD.BAT file:

  @echo off
  c:
  cd\pcb
  set pcb=
  set dszlog=pcbdsz.log
  if exist remote.bat rename remote.bat remote.sys
  if exist door.bat del door.bat
  if exist endpcb del endpcb
  pcboard
  if exist remote.bat remote
  if exist door.bat door
  if exist event.bat event     <---- note the test for, and execution of, the
  if exist endpcb goto end           event.bat file
  board
  :end

If this was not your purpose (in posting the above message) please let me know
what you wanted me to do with the message.

                                         David W. Terry 

Date: 05-10-93 (10:02)              Number: 62772 of 63094 (Refer# 62675)
  To: TIM ELSON
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David I uploaded my node6.bat file. Should I have left an If exist event.bat
-> event, in there?.

Ah, this explains your previous message.  Yes, you DO need to keep that line in
there.
                                         David W. Terry 

Date: 05-10-93 (10:03)              Number: 62774 of 63094 (Refer# 62676)
  To: IVAN WINDON
From: DAVID TERRY
Subj: OTHER:  EVENT 05-07-93 18:08:00
Read: 05-11-93 (02:33)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Node 2 will look like it's about to start the event, sit for a second, then
-> load the board back up without doing a thing.

Perhaps you did the same thing as in the previous message I just answered.

You need to KEEP the line in your board.bat file that executes EVENT.BAT.
Without it, your board will just "recycle" just like you described.

Please read backward from this message a couple of messages and you'll find a
sample board.bat file.
                                         David W. Terry 

Date: 05-10-93 (10:04)              Number: 62775 of 63094 (Refer# 62677)
  To: YAN WOLF
From: DAVID TERRY
Subj: Beta Report              
Read: 05-11-93 (01:23)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Does Pcboard erase the file attach after a successfull download by the user

No.  The file is kept there until the message is "packed out" of the message
base by PCBPACK.
                                         David W. Terry 

Date: 05-10-93 (10:06)              Number: 62778 of 63094 (Refer# 62678)
  To: JOHN SCUDDER
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Hello there my friend.  I am getting the following message when attempting
-> to log on to node 2:
->
-> Unable to open PCBPROT.DAT file
-> Exiting to DOS!

Two possibilities exist:

1) The PCBPROT.DAT file does not exist.  Run PCBSetup and create it.

2) Or you are out of file handles.  Edit CONFIG.SYS and increase the FILES=
   setting to allow PCBoard to open more files.

                                         David W. Terry 

Date: 05-10-93 (10:05)              Number: 62780 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: FEMA SLPS
Subj: FYI on events not running
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

I too had difficulty with getting events to run under 15.0.  What I
discovered was that I had to fill in the date field with 00-00-00.
Leaving it blank as was shown in the example would make it fail for me.
Filling it in with 00-00-00 caused it to work without fail.  This was
under /2 version 05-06-93.

Date: 05-10-93 (10:13)              Number: 62782 of 63094 (Refer# 62682)
  To: JOHN SCUDDER
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When the instructions said to delete the PCBOARD.XXX file, I accidentially
-> deleted the PCBOARD.dat file in my PCB2 and PCB3 directories.

The BEST solution here is to restore a backup of your pcboard.dat file.

The 2nd best solution is to copy PCBOARD.OLD (which is a backup of your v14.5a
pcboard.dat file) over top of PCBOARD.DAT and then run PCBSetup to "re-convert"
it to v15.0.

The 3rd best solution is to use Norton Utilities (or equivalent) to undelete
the file that you deleted (or the pcboard.old file).

The 4th best solution is to create the pcboard.dat file from scratch.  And I
don't know that the word "best" really fits in this scenario.  :-(

Examine your system to see if you have a backup or a pcboard.old copy that you
can use....  otherwise you're going to have to start over setting it up.

-> I get the following info in the d:\pcb\pcbsm.exe use:
-> None of the above allocations require upgrading at this time...
->
-> I get the following in the d:\pcb2\pcbsm.exe use:
-> WARNING:  One or more of the above allocations requires updating

Make sure that ALL NODES on your system are configured with the SAME NUMBER for
the conferences (PCBSetup : Configuration Options : Messages : Number of
Highest Conference Desired).

Load PCBSetup.  Set the number.  Exit and SAVE!  (whether you made any changes
or not, don't leave out the 'SAVE' step)

-> ALSO... ALL MY CONFERENCES HAVE DISAPPEARED!
->
-> Can you help?

Sure, I'll be over right away to help you start typing the conference setups
back in. :-)  Sorry...  your best bet is to restore those files.

                                         David W. Terry 

Date: 05-10-93 (10:22)              Number: 62786 of 63094 (Refer# 62687)
  To: JAMES JONES
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> When is a local file attachment deleted?  I killed the messages that had the
-> file attached, and then packed the message base so the messages were
-> removed.  The files remain in the attachment subdirectory.

Please re-check your findings.

File attachments are removed after you PACK OUT the killed message.  I wonder,
though, your message included the following:

->        PCBPACK /AREA:ALL /INDEX /OLDINDEX

The above command is NOT a command to "pack out" anything.  It will simply
recreate the index files and NOTHING MORE than that.

If you want to pack messages out of your system then you need to use a normal
PCBPACK command line (with the addition of /OLDINDEX if that is your
intention).

Here is an example from our own board:

        pcbpack /area:0-9;11-51 /days:30 /fast /keep /oldindex
        pcbpack /area:0-9;11-51 /days:60 /fast /oldindex

-> Is it possible to allow multiple logons AND change the user information?

No.

-> I have a couple of co-sysops I would like to allow on more than one node at
-> a time (we all have a couple of modems).

This would be IMPROPER use of that feature.  The Multiple Logins feature is
intended to allow you to set up DEMO ACCOUNTS on your system.

The thing that makes it IMPROPER for sysop accounts is that, set up that way,
your sysops would be forced to RE-read mail all the time.  Every time they log
in PCBoard will reset their Last Message Read pointers to 0.  This is good and
proper for a DEMO ACCOUNT but would be frustrating to your co-sysops.

Do NOT use the Multiple Logins feature except for demo accounts.

-> Will multiple logons be prompted for the password change?

This looks like it might be an oversight.  I will investigate.

-> Or, should I just make sure that all people who have a security level which
-> allows multiple logons have their date set to 00-00-00 for the next change?

That will work.  Set the expiration date to 00-00-00 and their passwords will
never expire.

-> (39:0:0:3) Error Writing File C:\PCB\MAIN\USERS.INF (Pos

Do you still have this problem?  Or has the problem gone away?

Look for possibilities such as a READ-ONLY attribute on the file, or a file
whose size is wrong.  There may be other possibilities...  but further
investigation would be necessary to draw any conclusions.

                                         David W. Terry 

Date: 05-10-93 (06:24)              Number: 62788 of 63094 (Refer# NONE)
  To: RICK WELSHANS
From: JIM WENZEL
Subj: OTHER:  BETA DOOR 05-07-9
Read: 05-11-93 (00:48)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Rick Welshans * I used Robocomm to grab the newest beta the other day,
                and hung at the "Download Flagged Files" prompt. Never
                got the beta. Keyboard timed out. That was expected.
                                = = =

  Try BETA;NEW;NOFLAG this will grab beta.zip for you but will NOT set
  the flagged flag.. (if you know what I mean)_

  Then when you return from the door you can Download Beta.zip

  We use it just about everyday.. (at least when we can get on <G>)

---
 * SM 1.06 A0059 * The firm basis of government is justice not pity.W.Wils

Date: 05-10-93 (10:25)              Number: 62789 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: FEMA SLPS
Subj: BETA report              
Read: 05-10-93 (10:58)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-06-93                                 


I had the feature set that required the password be given to exit the
call waiting screen.  I notice that if I was in local mode, exited from
PCBoard, then pressed the F10 key as PCBoard was logging me off, that
PCBoard would momentarily flash the call waiting screen but exit without
asking for the password.  If I were at the Call Waiting screen and
pressed F10, it would ask for the password.

Date: 05-10-93 (10:25)              Number: 62790 of 63094 (Refer# 62692)
  To: IAN GERADA
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (23:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> @ECHO OFF
-> D:
-> CD\PCB
-> SET PCB = /OLDINDEX
-> SHARE
-> SET DSZLOG=D:\PCB\PCBDSZ.LOG
-> IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS
-> IF EXIST DOOR.BAT DEL DOOR.BAT
-> IF EXIST ENDPCB DEL ENDPCB
-> PCBoard %1 %2 %3 %4 %5 %6 %7 %8
-> IF EXIST REMOTE.BAT REMOTE
-> IF EXIST DOOR.BAT DOOR                           <--- where is EVENT.BAT?
-> IF EXIST O:\FREE\RECIPT.ZIP DEL O:\RECIPT.ZIP
-> BEEP
-> IF EXIST ENDPCB GOTO END
-> :END

You, too, are missing the line in your BOARD.BAT that is supposed to execute
the event.  It should say:

        IF EXIST EVENT.BAT EVENT

Let us know if you need any further assistance.

                                         David W. Terry 

Date: 05-10-93 (10:36)              Number: 62793 of 63094 (Refer# 62735)
  To: JAY CAPLAN
From: DAVID TERRY
Subj: Capabilities of PCB v15  
Read: 05-10-93 (20:18)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> There is a precedent for this capability to start a download taking more
-> time than the user has left: TBBS allows it.

So does PCBoard v14.5 and v14.5a ...  make the file "NOTIME" in your FSEC file.

                                         David W. Terry 

Date: 05-10-93 (10:41)              Number: 62795 of 63094 (Refer# 62739)
  To: JULIAN CAUCEGLIA
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (15:33)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 1. On File Uploads, system prompts for discription prior to d/l should first
-> check for DIZ then prompt after d/l

Incorrect.  You have misinterpeted what was written in the WHATSNEW file ---+
                                                                            |
                                    +---------------------------------------+
                                    |
                              vvvvvvvvvvvvvvv
 added   Immediate detection, after an upload, of the existence of a
         FILE_ID.DIZ file within a .ZIP or .EXE file.  If a FILE_ID.DIZ file
         is found AND the sysop has configured the system to verify uploads,
         the user will *not* be asked for a description.

The following additional information has been added to the WHATSNEW file for
the next posting:

|        NOTE:  This ability to skip asking for a description takes place only
|        AFTER an unannounced file is received.  Normally PCBoard would prompt
|        for a description AFTER RECEIVING an unannounced file.  But in the
|        case where a file description accompanied the unannounced file, this
|        step would be redudant so PCBoard skips asking the caller for a
|        description and immediately shells out to PCBTEST.BAT which then
|        extracts and incorporates the included (FILE_ID.DIZ) description.

-> 2.On File Uploads, system will seem to accept the upload - then when the
-> upload is complete...will flash message "<FILENAME> is already on the
-> system" and not accept the upload I seem to have eliminated this problem by
-> re-writing my "ALLFILE.PTH" but shouldn't it first check prior to allowing
-> the upload to begin?

Make sure you don't include your PRIVATE UPLOAD directory in the ALLFILES.LST
file.

-> 3.Need new HELP files to accomidate the changes in commands.
-> Perhaps there is a way we can download you entire help file subdirectory?

You can, of course, do that...  but the HELP files have not yet been updated.

Sorry... beta testing and documentation are like that.  The information will be
posted as soon as it is available.  Right now it simply does NOT YET exist.

-> docs sent with BETA are good but quite incomplete.

They were not intended to be complete.  The "complete" docs are expected to be
several HUNDRED printed pages in length.

It's coming....  you can expect "complete docs" around the time that v15.0 gets
ready for "release".  Until then, please use what has been supplied together
with the *many* messages posted in this conference.

-> 5. Is there some way to update the idx on message bases after a mail run?

Yes.  Use the following command:

        PCBPACK /AREA:ALL /UPDATE

                                         David W. Terry 

Date: 05-10-93 (10:42)              Number: 62796 of 63094 (Refer# 62741)
  To: RAY NOVINO
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (11:38)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> When using the F-5 function to do a local shell to DOS it does not seem to
-> clear the "INPCB=Y" after typing exit and then doing a goodby.  The
-> "INPCB=Y" myst be changed manualy.

Are you somehow loading up yet another copy of the software?

Please call me voice on this one ASAP.  The number is 801-261-1686.

                                         David W. Terry 

Date: 05-10-93 (10:46)              Number: 62798 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: BRUCE VIGIL
Subj: BETA report              
Read: 05-10-93 (11:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-04-93 13:25:00                        


Ok, here are some of the problems I found with PCB 15.0
Beta version (05-05-93 13:25)

First: I logged on locally and and went to chat mode, entered
       channel one, typed call, and the node locked up after
       spewing control codes all over the place. I guess it does'nt
       like this. PCB 14.5 had no problem with that manuveur.

Second: When I take down a conference, for example #30 and delete
        all the entries, PCB 14.5 would bypass reading this conference
        when the commad to do a full check was given. PCB 15.0 checks
        everything, and returns (2:3) Error opening file. File not
        found.

        This confused me at first, and I had to check over 300 confs,
        looking for the problem. I found none and then releazed that
        PCB 15.0 was checking all previous activiated conferences that
        were now vacant.

        Hope this can be fixed!

Third: This is more of a wish list. Could you make the CALL command part
       off the command structure. My users and I had a heck of a problem
       trying to chat node to node. This is very confusing, and for a
       system that was easy to use under v14.5, 15.0 fails on this
point.


Thanks for listening, and I will continue pushing you program to the
outer limits looking for things that need to be fixed.

Oh btw, I loved the INTRO part to the Conferences, that was a great
idea!
I also loved the EVENT MANAGER. Saved me some money! Now when are you
going to incorporate the WET BAR feature! :)

TTYL,

Bruce Vigil
SYSOP
SKELETON CREW BBS

RoseNet
bruce vigil@skeleton crew

Date: 05-10-93 (10:54)              Number: 62801 of 63094 (Refer# 62781)
  To: MIKE FIELD
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (10:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I noticed when electing to do a quick logon after the language prompt and
-> choozing Ansi mode you are put into a non-graphics mode...
-> i.e  Y N Q

You're a bit confused....   "Y" means you want graphics
                            "N" means you do NOT want graphics
                            "Q" means to skip the welcome screen

Your "Y N Q" command will result in NO GRAPHICS because you *requested* it that
way.
                                         David W. Terry 

Date: 05-10-93 (10:57)              Number: 62802 of 63094 (Refer# 62783)
  To: BARLY REDSAR
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I have another problem with v15.  I am allowing for my callers to upload
-> only .ZIP and .GIF files.  Which was working on the 14.5.  Currently, my
-> board is accepting only .ZIP files only.  Although if I type the filename as
-> for example TEST.GIF, PCBoard convert the extension to .ZIP.

I do not understand your report.

If someone tries to upload TEST.GIF they should be ALLOWED to do so.  The only
thing "new or different" about v15.0 is that if TEST.ZIP already exists then
PCBoard will tell them that TEST.ZIP already exists and refuse to allow
TEST.GIF to be uploaded.

From the WHATSNEW file:

 - Uploading now scans for matching files regardless of extension prior to
   allowing a file to be uploaded.

If I have misunderstood your report (I said I didn't right up front) then
please correct my thinking by providing EXAMPLES of what you are talking about.
Screen captures would be TERRIFIC.

                                         David W. Terry 

Date: 05-10-93 (11:02)              Number: 62803 of 63094 (Refer# 62798)
  To: BRUCE VIGIL
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I logged on locally and and went to chat mode, entered channel one, typed
-> call, and the node locked up after spewing control codes all over the place.
-> I guess it does'nt like this. PCB 14.5 had no problem with that manuveur.

Huh?  (sorry, I am questioning your "conclusion" here ... v14.5 did not HAVE
a call command and the chat system was *totally* different)

Anyway, the important thing is this:

Please try to DUPLICATE your report and then submit a detailed list of steps
required to duplicate the report.

NOTE:  It apparently isn't as simple as just "going into chat and using the
CALL command" otherwise there would be big-time problems with CHAT.

So research it a bit further and let me know the results of your investigation.

-> This is more of a wish list. Could you make the CALL command part off the
-> command structure. My users and I had a heck of a problem trying to chat
-> node to node. This is very confusing, and for a system that was easy to use
-> under v14.5, 15.0 fails on this point.

Of course, any time you CHANGE things, people have to "learn" the new way of
doing things.

Get into chat and then use the CALL command.

The new chat system is not designed for a main-menu-command that would allow
for a CALL command to work.  You have to first be "in chat" before a call
command can be issued.
                                         David W. Terry 

Date: 05-10-93 (11:04)              Number: 62804 of 63094 (Refer# 62670)
  To: TIM ELSON
From: JULIO DAVILA
Subj: event in pcboard 15.0    
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> What is the other line you must leave?.
-> ttyl Tim.

Here is a sample board.bat....


@echo off
c:
cd\pcb\node1
set pcb=/oldindex
if exist remote.bat rename remote.bat remote.sys
if exist door.bat del door.bat
if exist endpcb del endpcb
pcboard
if exist remote.bat remote
if exist door.bat door
if exist event.bat event   <<<---- leave this one...
if exist endpcb goto end
board1
:end

Julio
Greenwood Enterprise BBS
718-456-5478

Date: 05-10-93 (11:10)              Number: 62805 of 63094 (Refer# NONE)
  To: ALL
From: JULIO DAVILA
Subj: Download Counter         
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Hello,
      I will like to know if anyone know how to reset the download
counter in pcboard...  PCB v15.x offers a very good file/ratio &
byte/ratio setup..  I run a subscription board and i had it set with
file ratio using tuam program..  I would like to be able to reset the
download counter monthly...
                                                 Julio

Date: 05-10-93 (11:11)              Number: 62806 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ANDY KEEVES
Subj: BETA report              
Read: 05-10-93 (11:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93                                 


Perhaps not intended to work this way but....

If you enter a message via a plain "E" command and save it (no file
attachement), then go back and EDIT it and use "SA" to save it WITH a file
attachement all will appear normal.  However, when you try to download or view
the attached file you will likely find that it does not exist.


I have no problem reproducing this on ExecNet at will - unless it is something
unique to my setup you got a bit of a bugger here..  :)

Incidentally, I used "F" as the upload protocol and was in LOCAL mode (with
/LOCALON) when I did this.

Date: 05-10-93 (11:28)              Number: 62808 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: new messages today       
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

There are, so far, 278 new messages in this conference TODAY.  And it's not
even noon yet....

I hope everyone is keeping up with the message flow.  There are a lot of
messages with good information in them that, if you read it before you ask your
question, might save "yet another message" from being posted.

                                         David W. Terry 

Date: 05-10-93 (11:43)              Number: 62811 of 63094 (Refer# 62538)
  To: FRED HAMBRECHT
From: SCOTT ROBISON
Subj: Menu description MNU     
Read: 05-11-93 (09:07)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am setting up new menus using the MNU files. It is great for new users
-> etc. The problem is that once set up, even expert mode requires you travel
-> the paths to get to what you want to do.

Ah, but this is *EXACTLY* what menus do and why we've been telling everyone for
so long that they didn't want MNUs.  :)  They idea behind a menu (to my way of
thinking, and since I implemented them it's how they work) is to select an
option from the first level menu, then select an option from the second level
menu, and so on and so on until you get to the menu and option you want.

Why can't your expert mode users access a mail door from the OPEN DOOR menu?
If you have your MNUs set up as BRDM/BRDS replacements, and if they are in
expert mode, just use the commands they already know!

Let me know if you have any further questions.

   Scott Robison

Date: 05-10-93 (11:43)              Number: 62812 of 63094 (Refer# 62564)
  To: ALLEN STONE
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (07:45)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> With one node up and running under desqview, you can flag a file from the
-> cd-rom and it is copied and downloaded locally without a hitch. The busy
-> light on the cd rom drive flashes at a quick pace and the file is copied in
-> no time to speak of.
->
-> Once you open another node of PCBoard, the problems begin. It appears to
-> slow the system down to a crawl.

What you have just described sounds identical to what happens whenever you
access a FLOPPY drive under DESQview (or even Windows).

The floppy disk access sets the "DOS BUSY" flag that tells the various
multitaskers that they can no longer multitask.  This is because DOS is
non-reentrant.  (unlike OS/2 where floppy disk access has virtually no effect
on other tasks running simultaneously)

I have only two suggestions here:

1) Try to obtain a CD-ROM driver that is more multi-tasker "friendly".

   I have no experience with CD-ROM drives and, therefore, no "recommendations"
   that I can offer.  But this doesn't seem to be a wide-spread problem so
   perhaps a solution exists...

   Try contacting the CD-ROM manufacturer to see if they have an update.  Or,
   you might check out one of those new CD ROM "caches" that have come out
   recently.  They are like disk caches except they work with CD ROMs.  Perhaps
   their code will be more multitasker friendly.

2) Alternatively, set up a network.  Then put the CD-ROMs on a server (which is
   NOT running DESQview).  Then your DESQview workstations can access the
   CD-ROM over the network without invoking the "DOS BUSY" flag and thus
   multitasking can still occur.

-> I attempted to flag and download a file from the cd-rom. When I went to d/l
-> the file, the busy light on the cd rom drive flashed every 20 seconds or so,
-> after approximately 10 minutes of waiting for PCoard to copy the file
-> (104,299). You see the preparing file(s) for download. Please Wait. This
-> message remained on the screen for the entire time. Then the following
-> appeared 21:7:1:4 Error Reading File r:\013a\deswin.zip (Drive not Ready)

That message came from DOS.  There's not much PCBoard can do except report the
error message...

Again, perhaps a change in the CD-ROM device driver could help.

                                         David W. Terry 

Date: 05-10-93 (11:44)              Number: 62815 of 63094 (Refer# 62809)
  To: DANIEL CHLARSON
From: WAYNE MAAS
Subj: bbs number?              
Read: 05-10-93 (11:47)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Daniel,

-> Can I please get a current BBS number for you?  I was trying to get
-> in touch with you, but I believe that the number that I have must not
-> be correct.

My board is currently down.  I am still running PCB at work for
program development.  I will give you the number when it goes back up.

Wayne

Date: 05-10-93 (11:46)              Number: 62816 of 63094 (Refer# 62565)
  To: DONALD MEHRTENS
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-10-93 (18:02)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> ---- And for brevity I cut it, but when I hit enter I get the original
-> Sysops main menu (the BIG one with all the options) followed by my own
-> custem menu.  Shouldn't I only get the sub menu until I quit back to the
-> main menu?

Please ZIP up and upload your MNU files for me to take a look at.  Based on
what you've described I don't understand the problem and will probably be
better able to find it when I'm actually looking at the MNU files.

   Scott Robison

Date: 05-10-93 (11:47)              Number: 62817 of 63094 (Refer# 62583)
  To: BILL FINK
From: SCOTT ROBISON
Subj: Thanks!                  
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The /SNOW DOES work and will live JUST fine and WILL put a "fire" underneath
-> ATI's tech support.

Glad to hear it.  That takes a load off my mind.  :)

   Scott Robison

Date: 05-10-93 (11:53)              Number: 62820 of 63094 (Refer# 62598)
  To: JOHN LUNDELL
From: SCOTT ROBISON
Subj: BETA report              
Read: 05-10-93 (18:40)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Last night when I got to the BBS the server was locked up - a user was in
-> the MORE menu and it said "Caution.. 3 Minutes left blablabla..." the prompt
-> was there and he had pressed 6 and got a missing file error (like
-> MNU00006.$$$ - let me again stress that I had the error written down but I
-> can't find it here anywhere... dang!)

OK, the filename is MNU#####.$$$, where ##### is the 0 padded node number, so
if you saw 00006, then it should have been your node 6 that was locked up.
I'll look into it and see what I can find.  If you come up with more info
please pass it on, I can't think of what would cause this.

   Scott Robison

Date: 05-10-93 (11:53)              Number: 62821 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: OVLSIZE.ZIP updated      
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

The OVLSIZE program has been updated so that it will now save the date/time of
the executable.
                                         David W. Terry 

Date: 05-10-93 (11:54)              Number: 62822 of 63094 (Refer# 62664)
  To: DON REID
From: SCOTT ROBISON
Subj: PCBEdit Version 1.00 Wide
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Of course, you're going to work on this to make it even more efficient,
-> aren't you? ;-)

How can I make it more efficient?  Serious question, @clreol@ isn't that bad,
and allows you *PRECISE* control over what you are doing.

   Scott Robison

Date: 05-10-93 (12:00)              Number: 62823 of 63094 (Refer# 62686)
  To: BLAINE BINKERD
From: SCOTT ROBISON
Subj: .MNU behavior            
Read: 05-10-93 (17:55)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I got SUBMENU.ZIP this morning and took a look at the thing.  This looks
-> like a pretty powerful system, but the example is a bit lacking.

I *REALLY* need to see about more examples.  <sigh>  The documentation will
(hopefully) be much better.  Knowing Steve, I'm sure it will.

-> The shortcoming in this example program is that when a user is on the
-> message menu, it's not a simple operation to read mail with a
-> R;S

Right, because MNUs expect you to select one option at a time.  Of course, you
*COULD* create a series of commonly used read commands (R;S R;Y;S R;Y;O;S etc)
and make them into individual options that the user will select as needed
without *KNOWING* that the computer is really doing a R;S for them.  :)  Does
that make sense?  If not, feel free to fire another volley back.  :)

   Scott Robison

Date: 05-10-93 (12:05)              Number: 62824 of 63094 (Refer# 62610)
  To: KEN MILLER
From: SCOTT ROBISON
Subj: SubMenus                 
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> If you set PCB up to use submenus, it doesn't allow you to stack commads
-> anymore.

Looking into it.

   Scott Robison

Date: 05-10-93 (12:09)              Number: 62825 of 63094 (Refer# 62567)
  To: STACY SMITH
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (19:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Anyway, attached is a message base with indexes for a conference on my
-> board. It's a Fido conference, and I use FidoPCB to toss the messages. For
-> some reason, the last few messages tossed in this base are not readable from
-> the board. When I do a "r -", it gives me message 115, where there are 118
-> according to the message header.

Okay, I'm running your MSGS file under the debugger right now and found the
following:

1) Messages 116-118 are not found in the MSGS.IDX file.
2) Running PCBPACK with /INDEX did not put them into the MSGS.IDX file.
3) Deleting the .IDX file and letting PCBoard create it (by joining the
   conference) also did not put them into the IDX file.

The reason, as it turns out, was due to an invalid message header.  The
following is what I found in the header for message #116:

Status                       ' ' 32 (0x20)
MsgNumber                    "\0\0j\x87"
RefNumber                    "\0\0\0\0"
NumBlocks                    '\x10' 16 (0x10)
Date                         "13-Sa-Ma"                      <--- bad
Time                         "93 12"                         <--- bad
ToField                      "BILL ANDRUS              "
ReplyDate                    "\0\0\0\0"
ReplyTime                    "     "
ReplyStatus                  ' ' 32 (0x20)
FromField                    "PETER CLAUSEN            "
SubjField                    "New Net Petition         "
Password                     "            "
ActiveFlag                   '\xE1' 225 (0xE1)
EchoFlag                     'E' 69 (0x45)
Reserved                     "\0\0\0\0"
ExtendedStatus               '\0' 0 (0x00)
Reserved2                    '\0' 0 (0x00)

Of the above...  only the DATE really matters as far as accepting (as valid) or
rejecting it.  That date is definitely invalid and could not be processed.

Looks like someone needs to fix the FIDO tosser.  Everything else, after just a
quick lookover, looked correct so hopefully it won't be tough to fix.

                                         David W. Terry 

Date: 05-10-93 (12:26)              Number: 62828 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: TOM MCNALLY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93 18:08:00                        


I'm having reliablility problems with the EVENT processor.
It seems to ALWAYS work on my nine-node 04:00 event, but
seems to almost always skip any events that occur in the "00"
(Midnight) hour.  I have observed it just breeze right by the
event time.  I have checked and rechecked my config, and it is fine.
(If it wasn't - none of the events would work)
At this point, I'm going to have to go to a stand alone timer,
as I've missed about 4 mail runs this past week, and the guys
that pull from me are getting upset ...

... tom

Date: 05-10-93 (12:42)              Number: 62831 of 63094 (Refer# 62827)
  To: DANIEL CHLARSON
From: SEAN AZHADI
Subj: Message display command  
Read: 05-10-93 (12:44)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> What is the command to display the number of messages in all
-> conferences just as you login to PCBoard & answer "Y" to scan for
-> messages in conferences?
->
-> PCBSETUP, Configuration options, Configuration switches:

I'm afraid I did not make myself clear.  I like to create a command via
command translation so the user can type "ALLNEW" or whatever, & the
system SCANS all the conferences for all new messages while the user is
ON-LINE.  Sorry about not explaining it completely.

Date: 05-10-93 (13:17)              Number: 62838 of 63094 (Refer# 62830)
  To: VINCE RIFICI
From: SCOTT ROBISON
Subj: MNU files                
Read: 05-11-93 (11:16)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Could you please tell me how to get .MNU files to act as if the caller was
-> not in Xpert mode, even if he actually is?  All my .MNU files only display a
-> command line when the user is in Xpert, and he has to enter "MENU" to see
-> the sub-menu.

Not enough information for me to go on as there are several ways you could
install MNU files.  How have you done it?  As a CMD.LST entry, as a BRDM/BRDS
replacement, etc, etc, or what?

-> It doesn't work that way on this board.  I am in Xpert mode, and when I
-> enter SEARCH, the small search sub-menu comes up immediately. This is much
-> nicer that the way mine is configured, but I can't seem to get it to act
-> like yours does... Thanks,

Search isn't a MNU, it is a PPL application that can do *ANYTHING* it wants!
Literally.  Give me more info and I'll try to help you out some more.  The
simple answer to your question is, if a user is in expert mode and is running
an MNU file, you *CAN'T* force the menu to be displayed to them.  It doesn't
work that way.  Experts do not want or need display menus (usually) and if they
do, the MENU command is available.  Non-experts do want and need display menus
and they are automatically displayed.

   Scott Robison

Date: 05-10-93 (13:17)              Number: 62839 of 63094 (Refer# 62835)
  To: SEAN AZHADI
From: DAVID TERRY
Subj: Problem with PCBoard     
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> While on your system this morning, I notices something strange. When I
-> flagged some files & issued a "D" command, the system asked me if I wanted
-> to download the FLAGGED files.  I answered "Y" & then the system asked me
-> for "filename #4, enter for none".  I accedentally hit "G" for goodbye after
-> transfer.  This was obviously in the wrong place & I should have waited for
-> the prompt, however, the system changed my transfer protocol "ZMODEM" or "Z"
-> to "Ymodem/G BATCH" or "G".

Sean, every version of PCBoard, since v14.2 at least (and possibly even
before), has allowed you to type in the PROTOCOL letter on a "Filename to
download" prompt to select the protocol you want to use.

It's supposed to work that way...  this is not a problem it is a purposely
placed "design feature" for those that want to set their protocol after getting
into the process of selecting files.

                                         David W. Terry 

Date: 05-10-93 (13:20)              Number: 62840 of 63094 (Refer# 62830)
  To: VINCE RIFICI
From: DAVID TERRY
Subj: MNU files                
Read: 05-11-93 (11:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am in Xpert mode, and when I enter SEARCH, the small search sub-menu comes
-> up immediately.

<grin>  Version 15.0 is very flexible, I can see how you could get confused.
There are literally dozens of different ways to actually implement any given
task in v15.0.

What you THOUGHT was a .MNU file was no such thing...

Edit your CMD.LST file and, inside of there, put the command "SEARCH" and
attach to it the name of the SEARCH.PPE file.

This is how you go about "adding new commands" to your system.  It does NOT
require that you use an MNU file.

For completeness:  An MNU file *does* allow you to define commands on THAT
menu.  Of course, as you noted, only those who are in novice mode will ever
see those commands or be able to use them.  The same is not true of CMD.LST and
its ability to define new commands.

                                         David W. Terry 

Date: 05-10-93 (13:24)              Number: 62841 of 63094 (Refer# 62597)
  To: MSI-MICRO SYSTEMS
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (21:49)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> You will also notice a small bug in the upload portion.  The system bypasses
-> the Default (T)ransfer protocol, and defaults to (N)one before allowing the
-> upload.

This is not a bug, but rather, a "design feature".

Why?  Because if it did not default to NONE then you would have NO WAY to
change the protocol.

In other words, if you just spent 15 minutes composing a beautiful message and
then type SA to save that message with an attachment, you're going to feel
quite frustrated if you can't attach a file because of the default protocol.

Forcing it to NONE also solved a "tech support" problem we had where initial
testers kept trying to use ASCII for the message uploads without actually
READING what was on the screen.

This was understandable, in that PCBoard previously only allowed ASCII uploads
into the message base, but it was a bit of a nightmare having to answer the
question even though the answer was already on the caller's screen.

So now it defaults to NONE and there is no way to force any other default.

(for others reading this message:  the above applies ONLY to message uploads)

                                         David W. Terry 

Date: 05-10-93 (13:29)              Number: 62843 of 63094 (Refer# 62842)
  To: DANIEL COULOMBE
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (13:56)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Question #1:
-> It looks like I have pointers problems!...

Looks like you lost carrier after the above line.

Before you go any further though...  have you set your system up to maintain
OLD INDEX files?

Specifically:

   1) IMMEDIATELY DO THIS:         Run PCBPACK /AREA:ALL /INDEX /OLDINDEX

   2) Then edit your BOARD.BAT file adding /OLDINDEX to your SET PCB= line.

   3) Then add /OLDINDEX to your PCBPACK line in your events

The above should take care of whatever "pointer problems" you think you have.

                                         David W. Terry 

Date: 05-10-93 (14:00)              Number: 62845 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: MARK ADKINS
Subj: BLANK LINES IN CHAT MODE 
Read: 05-10-93 (14:38)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

PCBOARD 5-7-93  452464 18:08

Two users were in chat on channel 1. User on node 1 was typing and
each sentence that was typed wrapped as it should and looked like
these three lines.

The receive on node 2 did not always receive the lines of text as
above but would receive some lines here





and then these blank lines and the rest of what the user was typing
would appear down here.

The same happened if user on node 1 was the receiver and user on
node 2 was typing.

I logged on and entered channel 1 from a local node and the same
thing happened to my screen while reading what was being typed and
the same blank lines were sent to both nodes while I was the person
typing. Sending bluechat.zip which contains chat.dat file.

Mark
---
-> MegaMail v2.1 #405:.  Oregon Is what America Was


Date: 05-10-93 (14:01)              Number: 62848 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: DAVID BORAK
Subj: BETA report              
Read: 05-10-93 (14:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-04-93 01:00:00                        


Mr. Terry if you recall my problems with qemm errors and memory.
Well I found a way to get less errors. I have loaded everything high and
leave DOS low. My desqview windows are at 510K a piece. I had to put a
new upload processor online that requires less memory. But it's working
so far. 2 days without a qemm error. I did this on the weekend. I have
been experimenting with the bbs when time permits and my only main
concern is memory. Other than that..it's running..seeya Mr.Borak

Date: 05-10-93 (14:22)              Number: 62849 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: TODD KAP
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBPACK.EXE - 05-10-93 10:11:00                        


I cannot seem to get this copy of PCBPack to work at all.  It seems to go
through the motions of working and then ends with a Divide Error and I'm
dropped back to DOS with no cursor.

It doesn't matter whether I run the program from DOS or from within
PCBoard...the results are the same.

I am trying to pack the message base and purge all the read messages.

Todd

Date: 05-10-93 (14:38)              Number: 62850 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: TONY OLIVER
Subj: OTHER:  EVENT 05-04-93   
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Well I am having a small problem wuth my event. I have set using the
event.doc that was included with my files. I can not get it to run my
event. I am running a single node and when ever I enter the event.dat to
edit it I get a messager that the usernet.XXX is not found. If you can
shed some light on what I am doing wrong it would be greatful.

 Tony Oliver
CCC BBS

Date: 05-10-93 (14:40)              Number: 62852 of 63094 (Refer# 62846)
  To: MARK ADKINS
From: DAVID TERRY
Subj: FILE ATTACHED            
Read: 05-10-93 (16:43)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I've read so many messages, whatsnew files, history files, soup can labels,
-> I just can't remember how to setup to be able to send files attached to a
-> message.
->
-> Do I create a special directory where these files are to be held until they
-> are picked up? If so, where do I tell PCBoard where this holding directory
-> is?

Go into PCBSetup then go to each individual Conference.  Each of them has a
"File Attachment" directory.  You can set them all to be "unique" locations or
you can have them all go into one location.  It doesn't matter.  The only
critical thing is that the File Attachment directory exist.

                                         David W. Terry 

Date: 05-10-93 (14:46)              Number: 62853 of 63094 (Refer# 62847)
  To: MARK ADKINS
From: DAVID TERRY
Subj: LAST READ POINTERS       
Read: 05-10-93 (16:44)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> A caller logged in, was told he had mail waiting and was asked if he wanted
-> to read it and answered yes.
->
-> After reading his mail, he entered the MarkMail door to download his .QWK
-> packet. His last read pointers had been reset. He couldn't download via
-> MarkMail, the messages that he had just read on-line by answering Yes to the
-> prompt do you want to read your mail now.

When you answer 'Y' to "Read your mail" the messages are read in READ-ONLY
mode.  That is, the Last Message Read pointers will NOT be changed.  They will
be identical both BEFORE and AFTER having read the mail.

When you answer 'A' to "Read your mail" you are instead telling PCBoard to read
all new mail in those conferences where personal mail was found.  In this case
the Last Message Read pointers WILL be changed.  But your message, up above,
did not seem to imply that he had selected 'A' (still, a possibility though).

-> If a sysop enters a @user@ message, is everyone told they have new mail
-> waiting and are they asked if they want to read it now or is this feature
-> ONLY for private mail addressed to the user?

The @user@ works the SAME WAY it has worked for the last several years.

No, it does NOT set their "mail waiting flags" because to do so would require
that PCBoard scan your users file for EVERY USER and hit the users and
users.inf record for each user.  This could take a *very* long time if it were
implimented, but it is not, so it doesn't.

-> How do you, or can you send a message to @user@ or @44-100@ and have PCBoard
-> tell the caller he has messages and have PCBoard ask him if he wants to read
-> them?

You don't.  And can't.  PCBoard just doesn't do that.

                                         David W. Terry 

Date: 05-10-93 (15:16)              Number: 62855 of 63094 (Refer# 62700)
  To: MIKE ATKINSON
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (22:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> If a user changes his alias, he can't change it back to what it was before
-> until after I do a pack on the users file.

This is a result of the alias being held in the index files.

I've done nothing to "change" this behavior because I'd really prefer to
discourage continual changing on the alias name.  Making it easy to change back
and forth would encourage something like this:

        change name to JOHN DOE
        write a message
        change name to JANE DOE
        reply to JOHN DOE
        change name back to JOHN DOE
        reply to JANE DOE
        etc...

The one big thing I don't like about the very "idea" of aliases is that it
promotes a "lie" ... letting you pretend to be someone you are not.  If all you
do is use an alias for anonymity then I have less of a problem with aliases,
then they are serving a useful purpose, but if someone is continually changing
back and forth between 2 or more names then they are out to hide something.

-> I set up a PPE in the global CMD.LST with command name SETTINGS.  When
-> entering SE at the main comand prompt I got the settings PPE instead of
-> SElect conferences.

That is correct.  That ability allows you to OVERRIDE and REPLACE the internal
commands.  That's a FEATURE.

Now, do you want to know how to work around it?  :-)

Put SELECT in the CMD.LST file up above SETTINGS.  Tell SELECT that it should
just stuff the keyboard with "SELECT^M" and you're done.

Now if a caller types "SE" he will use the SELECT command.  He will have to
type at least "SET" (or anything more than that) to get the SETTINGS command.

-> Is there anyway to tell PCBoard to use the alias instead of the full name
-> when writing out the DOOR.SYS file?  I realize door.sys already contains the
-> handle

Because the DOOR.SYS file already contains that information, it is up to the
DOOR authors to use (or not use) the alias information that has been provided.

                                         David W. Terry 

Date: 05-10-93 (15:21)              Number: 62856 of 63094 (Refer# 62850)
  To: TONY OLIVER
From: NICK HARTZ
Subj: OTHER:  EVENT 05-04-93   
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Well I am having a small problem wuth my event. I have set using the
-> event.doc that was included with my files. I can not get it to run my
-> event. I am running a single node and when ever I enter the event.dat
-> to edit it I get a messager that the usernet.XXX is not found. If you
-> can shed some light on what I am doing wrong it would be greatful.

I have the exact same problem and cannot get my event to run.

If you answer "Y" to running under a network or multi-tasking
environment, exit PCBSETUP, re-enter, and then try editing your
EVENT.DAT, you will no longer get the error and the last-date field is
now filled with 00-00-00.

However, my event still does not work either. I am waiting for an answer
to a previous message (#62257) almost identical to yours.

If I hear something before I get a reply here, I will let you know.


                                        Nick

Date: 05-10-93 (15:23)              Number: 62857 of 63094 (Refer# 62474)
  To: DONALD MEHRTENS
From: DAVID TERRY
Subj: BETA report              
Read: 05-10-93 (18:03)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I witnessed this minor problem a caller had on my board while trying to
-> delete a message he had left.  I'll let him explain:
->
-> The software accepts kill, del, delete, erase, and any number of other
-> nulti-character commands with no complaints.  However..., only 'k', by
-> itself, actually kills a message.  I forgot the command & didn't find it
-> while looking through the help stuff, hence the message to you.

PCBoard has NEVER accepted KILL, DEL, DELETE, ERASE or any of those commands.
This is nothing new...

And as for "looking through the help stuff", he either didn't look very hard,
or your system is missing information that has been in there for ages.

The HLPENDR file (found in your \PCB\HELP directory) is the help that is shown
at the End of Message Command prompt.  This is the prompt at which you enter
the (K)ill a Message command.

(K)ill has been in that file for a very long time.  Check it out.

-> A question:  If I have both a daily K byte limit AND a byte ratio specified
-> for a given user level, which takes precedence?  IOW, is the user limited by
-> the most or least restrictive of the two?

The MOST restrictive of the two.

-> I had set one security level to a 400K byte limit and a 2:1 file ratio. My
-> intent was to allow these users to download at least 400K, and increase
-> their limit by uploading.  What happened was PCBoard would not let any of
-> these users download because they had execeeded their ratio.

Looks like you already knew the answer to the question then...  :-)

-> I know I can give an initial credit, but such users would still eventually
-> get cut off once they burned up their credit, even if they hadn't used up
-> their 400K daily limit and that isn't what I was after. I wanted all users
-> at that level to be able to download 400K per day no matter how bad their
-> ratio.

I don't know how to fit these two conditions together:

        a) You MUST maintain a ratio, but
        b) It's okay to NOT maintain the ratio on a per-day basis

This just isn't going to be do-able.  I'll put it in the wishlist for you, but
it just isn't something that will be implemented in v15.0.  You are either
using ratios or you aren't.

-> An even more powerful option occurs to me - having TWO sets of daily limits
-> for each security level, one specifiying the minimum limit (which the user
-> will always have no matter what his ratio) and another specifying the max
-> (which the user cannot exceed no matter what his ratio).  I guess that can
-> go on the 16.0 wish list...

Ugh...  do you want to do the Tech Support here?  <grin>

Seriously, with all of these new "combinations and permutations of features" in
v15.0 we're really going to have our hands full - even without adding a feature
like that one which would be a nightmare to document and explain.

                                         David W. Terry 

Date: 05-10-93 (16:15)              Number: 62866 of 63094 (Refer# 62535)
  To: STEVE OSMAN
From: DAVID TERRY
Subj: Preliminarly List of problems/Wishes.
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 1) If someone pages me and I don't respond (i.e. the page indicator is
-> flashing), when the user opens the door, it "forgets" the page indicator.
-> So, in the door, and when he returns to PCBoard, there's no more page
-> indicator.

That's the way it has worked for the last several years.  I'll put it in the
wishlist for you but it won't be changing in v15.0.

-> 2) I tried SET PCB=/OLDINDEX, and the first thing it did when I logged on
-> was update the indexes... to the NEW version.  QMAIL 4 REFUSED to work with
-> it.  I had to restore the backups (thank god for backups!), and then
-> MANUALLY go into every conference setup and tell it to use the old index
-> format.

I suspect you had not yet completed the process.  QMAIL4 works *fine* with
v15.0.

When you download new code you'll find that the README.1ST file has been
updated to include some steps commonly missed by others.  See if it will help
you out.

Specifically, use PCBPACK to create your indexes (see the README.1ST file for
complete details, I'm just helping you to narrow down what you need to look
at).

-> 3) I have a *SEVERE* problem with USERNET.XXX.  I delete it, when it
-> recreates it, everything seems fine.  *HOWEVER*, every time the PCBOARD.EXE
-> is loaded (either from another node, or if the batch file recycles after
-> someone logs off or someone opens a door), it tells me invalid USERNET.XXX
-> format, or something like that.

Two possibilities:

1) You are reloading an OLD version of PCBoard - thus recreating the OLD
   format.

2) Or else you are running an OLD utility - thus creating the OLD format.

PCBoard v15.0, on its own, definitely does NOT create the old format.  So focus
your attention elsewhere to find the true cause of the problem.

The most common problem is where someone brings up v14.5a for a moment, or when
someone executes the old USERNET.EXE file that we distributed for v14.5a.
There is a new USERNET program (posted as USERNET.ZIP in directory #2) that you
should use instead (if that is what you are doing).

Investigate it further, you'll find that the explanation is logically once you
uncover the true cause of the problem.

-> Some notorious teenager created something called "LEECH ZMODEM" a few years
-> ago, which would abort the transfer right after the file has been
-> successfully transferred, hence the user doesn't lose any download credits.
-> I'd appreciate it if you could include a field in the PCBSTATS PSA to
-> include "aborted transfers".

There are three problems with this request:

1) No new features will be implemented in v15.0.  Wishlist requests are for
   the next release.

   BUT THAT'S OKAY, read on.

2) All of OUR protocols, the internal PCBoard protocols as well as our external
   Zmodem, have "leech" detections built right in.

   That is, if someone tries to download a file and they receive the entire
   file successfully but ABORT THE VERY LAST BLOCK then the file will be
   counted as successfully downloaded in spite of the aborted status.

   In other words, it doesn't matter if someone tries to use a "leech" program
   they file will be counted as SUCCESSFULLY DOWNLOADED no matter what - if
   you are using *our* protocols.

   But what about external protocols not of our making?  Well, you can use the
   "slugbait" option in DSZ (I think it is -s) and you'll accomplish the same
   thing.  Abortions on the last block will be counted as good.

   So there is really little reason to worry about "leeches" as they will get
   their downloads counted anyway.

3) What about external protocols that don't have this capability?  Here's the
   clincher reason for not implementing it:

   If an external protocol aborts the last block it is counted as ABORTED for
   the entire file and the protocol has NO WAY to tell PCBoard how far the
   transfer went before it was aborted.

   In other words, PCBoard cannot detect whether or not a "leech" was attempted
   on an external protocol.  The information is simply not available.

-> I was reading mail in a certain conference on one node, and while I was
-> doing that, someone FidoNeted my system, adding many more messages to the
-> bases.  As I was reading messages, it was saying (for instance) 876 of 889,
-> next would be 877 of 889, next 878 of 889, and so on.  However, WHILE I WAS
-> READING, more messages were added to the conference, but the high message
-> pointer (889) was NOT updated, until I either
->      a) Do something (like change direction of read, reply, etc), or
->      b) REACH message 890
-> at which point the high message pointer is updated to reflect the TRUE
-> number of messages.

This is all NORMAL behavior.

In order for PCBoard to find out what the "current high message number" is, it
has to run to the TOP of the file and read the message header block.

To avoid the extra "hit" on your performance (it would not only SLOW YOU down,
but it would increase network traffic for EVERYONE on the system, especially if
you are attempting to read your mail RAPIDLY) PCBoard simply does not do that.

As you noted:  it will read the header if you change direction, or if you get
to the "current end" of the messages, then it reads the header to find out how
much MORE there might be there.

It has operated like this for years and there is really no reason to change it
but plenty of reasons to keep it working the way it is.

-> One of the most important (IMHO of course) ratios out there is the post-call
-> ratio.  Could you please add a field in the FSEC file for PCR?  Make it so
-> that people who aren't within their PCR range cannot download.  This is a
-> REALLY IMPORTANT feature for me.

Not in v15.0.  So I'll put it in the wishlist.

But you COULD write your OWN post-call ratio.  PCBoard v15.0 is *that*
flexible.  All you would have to do is write a PPL program and attach it to the
(D)ownload command.  Then if someone's ratio is not where it should be your PPL
program would inform them of that fact and refuse to process the download
request.

Have fun!

-> After an upload there's a message asking wether the user wants to remain
-> online while the file's being tested, or wether he'd like to hang up.  Let's
-> say the user went to the bathroom or fell asleep during the transfer (hey,
-> who knows, work can be VERY boring some times!), could you put a delay on
-> that prompt, so that if no response is recieved within say, one minute,
-> it'll default to one of the two options?

Have you tried it?  If not, you should do so and watch what happens.  We *know*
what we're doing around here...  certainly we would not have left the caller
"hanging" for 15 minutes.

Actually, it waits about 10 SECONDS.  If no response is received in that period
of time then it proceeds with the testing without hanging up the connection.

-> That way, if the user WAS, say, in the bathroom, by the time he returns, the
-> testing is already in progress, or DONE!

Yup, already implemented.

-> One of my users just used HS/Link to transfer some files at 9600.  She
-> downloaded for about one hour, and uploaded an 800k file at the same time.
-> The upload took only 12 minutes of the total transfer time.  Now, after the
-> end of the transfer, since I give two minutes for ever minute spent
-> uploading, she recieved TWO HOURS credit!

Two conclusions can be drawn here:

1) Your HS/Link is not set up correctly.
2) There is more to this equation than you have related (or may have even
   known about)

PCBoard bases its CREDIT on the amount of time spent for the UPLOAD portion.
It derives this information by getting the CPS calcuation (from the DSZLOG file
which HS/LINK creates) and divides it into the FILE SIZE of the file that was
received.

In other words, if you uploaded a 100K file at 1700 cps then PCBoard would
calculate it out to approximately 60 seconds REGARDLESS OF HOW LONG you spent
inside the file transfer.

The only exception is if you don't have a DSZLOG file - in which case the CPS
rate is not available to be determined.

Please investigate more thoroughly and you will either find a more logical
explanation or a problem with your setup somewhere.

-> If you think this is a long message, you ain't seen nothing yet!  Wait till
-> I *REALLY* get into it.  This is only a day's worth.

You should see _MY_ day's worth of mail.  You didn't even come close.  Of
course, you certainly CAUSED a healthy portion of it.  <GRIN>

                                         David W. Terry 

Date: 05-10-93 (16:58)              Number: 62872 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: MARK ADKINS
Subj: OTHER:  PCBOARD 05-07-93 18:03:00
Read: NO                            Status: PUBLIC MESSAGE / FILE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

I guess I'll stand in line with everyone else that is having problems
with the event.

I run a 3 node system. I set all nodes to read the event.dat file from
node 1's drive l:\pb\gen.

I created a file and named it test.003. In the event system, I answered

Y E TEST 15:11 15:13 YYYYYY 00-00-00

then I saved the info. The 15:11 time arrived, pcboard was taken off
line waiting for the event, then it ran the event but nothing happened.
I the test.003 file was the commnad

W:
CD\PB3\GEN
DIR

I then setup node 3 to have it's own location. w:\pb3\gen\event.dat
W:\PB3\GEN  and put the test file in there.

I have is a Timed Event Active set to Yes.

I changed the time of the begin and end time, I did a ctl-end on the
last date.

Pcboard again went off line waiting for an event, then it went out to
run the event and again nothing happened. I see in my last date that the
event ran and it is also in my log that it ran.

I changed the command inside of test.003 ( when I put it onto node 3's
drives drive W:  I tried this with the name of test and test.003, same
results)

The command I went to were
W:
cd\pb3\gen
standby.exe 400  (I tried standby 400 too)

Again pcboard went off line waiting for an event, then looked like it
was going to do something at event time but just cycled back to on line
call wait screen.

I changed back to drive L were the other two events are listed and used
that system, still no luck.

I run D'Bridge so all I want the event to do for nodes 1 and 2 is make
sure the caller is not on line around event time so it reduces their on
line time, which it does but on node 3, I want that node down for 2400
seconds so node 1 and 2 can run their events, then node 3 to return on
line after 2400 seconds.

I'll send you what ever files you request.

Also attached to this message is the bluechat.zip file that I should
have uploaded on my last call showing the chat log and the blank lines
that I reported in a previous message.

Date: 05-10-93 (17:02)              Number: 62873 of 63094 (Refer# NONE)
  To: ALL
From: LOUIS ZIRKEL
Subj: New PCBPACK.EXE Posted   
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

05/10/93 17:02 - PCBPACK.EXE
----------------------------
- Found a problem checking for duplicates in a message base with no messages
  where PCBPack would issue an out of memory error.  Fixed
- Found that PCBPack had the ability to renumber, but I had forgot to include
  it in any of the compiles.  It is now fix and available.  Let me know if
  you experience any problems when renumber message bases and...
    *** BE FOREWARNED ***
  we highly recommend that you renumber your message bases ONLY in case of
  dire necessity.  Renumbering messages has NO effect on any users last
  message read pointers so they may not receive new mail if messages have
  been renumbered.


Date: 05-10-93 (17:07)              Number: 62874 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: new code posted          
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

05/10/93 17:00  PCBOARD.EXE
---------------------------
- NOTE:  Posted a new WHATSNEW file.  Everyone please look over the "changes"
  which are highlighted by vertical bars down the left side of the document.
  These changes were made to help answer some of the *many* questions being
  asked on Salt Air.

- Fixed a bug in the @byteratio@ macro which would show up if the K-Byte Ratio
  Credits was high enough to cause a short integer overflow.  Fixed.

- Modified the @bytesleft@ macro so that it will now show the maximum number
  of bytes left based on the following criteria:

      Daily K-Byte Limit minus Bytes Downloaded Today
      Total K-Byte Limit minus Total Bytes Downloaded (including Today's)
      Byte Ratio Limit based on Total Bytes Uploaded & Downloaded (incl Today)

  The smaller of the above three values will be considered the maximum number
  of bytes left and will be shown when using the @bytesleft@ macro.

- If you used /LOCALON to start PCBoard, then went into a DOOR, then returned
  to PCBoard without the /LOCALON switch, the number of display lines would
  be reduced by 1 even though there was still only 1 status line.  Fixed.

- If the system was set up to require the local password in order to exit out
  to DOS it would require the password EXCEPT when pressing ESC while
  resetting the modem.  This has been fixed by disabling the ESC during
  modem reset.  This is ONLY disabled if a password is required to exit to DOS.

- Additionally, if the screen had already blanked out (due to 3-minute timer)
  or was forced off (via F9 function key) then when pressing ESC/F1/F10 to
  exit PCBoard was asking for the password to exit without having first
  restored the screen (i.e. you could not see that it was asking for the
  password because the screen was still blank).  Fixed.

- If you pressed F4 or F7 to change Alarm or Page status while sitting at the
  Local Password prompt, the caller status lines would appear at the bottom
  of the screen.  Fixed.

- If the system language (specified as a blank extension in PCBML.DAT) was
  other than language #1 in the PCBML.DAT file, then the first line displayed,
  indicating "Operational languages available", would be displayed from the
  wrong language file.  Fixed.

- Found some problems with File Attachments which were caused by a recent
  change in the beta code.  Fixed.

- In sysop function 7 (user file maintenance) the (A)dd User and (F)ind User
  commands would not allow high ascii characters in the user names.  Fixed.

- Editing a message header ("E" command at End of Message Command prompt)
  would not allow high ascii characters in the FROM/SUBJ fields.  Fixed.

- Fixed the DATE formats (for internationalization purposes) in the following
  areas:

  - When entering a new message and specifying the Packout Date
  - At the top of the Call Waiting screen
  - At the top of the "login" process (right after CONNECT)
  - The "Last Date On" field in the user record display (sysop function 7)
  - The "Last Date On" field when use the USERS command
  - The "Last Date On" field when using sysop function 2 V or 2 P
  - The "Expiration Date" on the status line (press ALT-H twice)
  - The capture date in a R C/D/Z command
  - The current date in a script answer file
  - The user's "Expiratin Date" in a script answer file

- Got rid of the bogus FILENAME.$$$ is missing message on message uploads and
  file attachments.

- When using the QWK U command to post messages, if you were in an Alias
  conference all of your replies, where in the alias conference or not, would
  have your alias name in the FROM field.  Similarly, if you were not in an
  alias conference, then all uploads would have your regular name, even those
  messages which were posted in an alias conference.  Fixed.

- If you entered a PRIVATE message in an ALIAS conference you would be unable
  to read the message you had just rewritten.  Fixed.

- The ASCII download protocol "startup sequence" has been modified to be
  compatible with RIPscrip which was losing the first line of RIPscrip codes.


05/10/93 14:52  PCBSETUP.EXE
----------------------------
- Increased the FSEC File Editor limit from 256 entries to 1024 entries.

- Changed the ORIGIN input to allow mixed case entry.

- Modified the event editor so it won't try to read USERNET.XXX if "Running
  on a Network" is set to NO.

Date: 05-10-93 (17:14)              Number: 62876 of 63094 (Refer# 62872)
  To: MARK ADKINS
From: DAVID TERRY
Subj: OTHER:  PCBOARD 05-07-93 18:03:00
Read: 05-10-93 (23:55)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> Pcboard again went off line waiting for an event, then it went out to run
-> the event and again nothing happened. I see in my last date that the event
-> ran and it is also in my log that it ran.

Most people with those exact descriptions have REMOVED the line from their
board.bat files that runs the event.

You MUST have in your board.bat a line that looks like this:

        IF EXIST EVENT.BAT EVENT

That is the line that *runs* the event.   Check it out and see if you have done
the same thing.
                                         David W. Terry 

Date: 05-10-93 (17:21)              Number: 62878 of 63094 (Refer# NONE)
  To: ALL
From: DAVID TERRY
Subj: additional fixes         
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

The following additional fixes ARE included in today's release but were not
mentioned in the HISTORY file for the first few people that downloaded today's
release:  (note:  these are from Scott Robison, but it was my fault for not
including them in the original history for today)

  MNU Support
  -----------
- I'm tired of answering questions to the effect of "Why can't I stack
  menu options?"  The answer has been that a menu is designed so that
  you don't have to stack.  Due to my overwhelming desire to stop
  answering the question, however, I've implemented the ability to stack
  to the MNU interface.  If you didn't want it, complain to those that
  wanted it as they have been a vocal group of people.  :)

  PPL Support
  -----------
- A bug was introduced last week that broke the READLINE() function.  I
  was incorrectly identifying that the file exists as an error.
  Obviously, if the file exists, I *CAN* read from it; what I needed to
  do was flag an internal error and return an empty string if the file
  didn't exist.  Fixed.

Date: 05-10-93 (17:47)              Number: 62881 of 63094 (Refer# 62873)
  To: LOUIS ZIRKEL
From: RAYMOND CLEMENTS
Subj: New PCBPACK.EXE Posted   
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Louis,
    Did you realized that MemCheck is still turned on in the PCBPack I
d/led earlier today?

             Raymond Clements - SysOp of The Pegasus BBS
              RIME PostLink routable ->PEGASUS  or ->36
             (502)684-9871 or (502)684-9896 USR DS 16.8K

Date: 05-10-93 (18:40)              Number: 62885 of 63094 (Refer# 62820)
  To: SCOTT ROBISON
From: JOHN LUNDELL
Subj: BETA report              
Read: 05-10-93 (19:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> OK, the filename is MNU#####.$$$, where ##### is the 0 padded node number,
-> so if you saw 00006, then it should have been your node 6 that was locked
-> up. I'll look into it and see what I can find.  If you come up with more
-> info please pass it on, I can't think of what would cause this.

why would it have been in the caller3 log?  Strange... I'll keep my eye on it.

Date: 05-10-93 (19:17)              Number: 62888 of 63094 (Refer# 62885)
  To: JOHN LUNDELL
From: SCOTT ROBISON
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> why would it have been in the caller3 log?  Strange... I'll keep my eye on
-> it.

I can't dup what you've described.  Let me know if you find an exact way to
duplicate it.  Thanx for the feedback . . .

   Scott Robison

Date: 05-10-93 (19:18)              Number: 62889 of 63094 (Refer# 62886)
  To: SCOTT YAGODA
From: SCOTT ROBISON
Subj: brdm.mnu                 
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> is it possible in the new menu setup to set a mnu to a user level as in the
-> old code you could have brdm and brdm25? If so please tell me how?

Well, you can't have a BRDM25.MNU if that's what you are asking.  What you
*CAN* do is have security specific display files.  Check out the first screen
of MKPCBMNU.  The second and third fields are filenames.  Whatever base name
you put in there can have security/graphics/language specific variations.  Make
sense?  :)

   Scott Robison

Date: 05-10-93 (19:36)              Number: 62895 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: DONALD MEHRTENS
Subj: BETA report              
Read: 05-11-93 (10:41)              Status: PUBLIC MESSAGE / FILE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93                                 


-> Please ZIP up and upload your MNU files for me to take a look at.

Enclosed with this message.

-> PCBoard has NEVER accepted KILL, DEL, DELETE, ERASE or any of those
-> commands. This is nothing new...

No argument on that from me, and I don't think you'd get any on it from
the user either.  I think the main point of his message was not that it
didn't accept these commands, but that it didn't give any feedback.
"Unknown command" or something along those lines would be a fair
expectation in that situation.

-> I don't know how to fit these two conditions together:
->
->         a) You MUST maintain a ratio, but
->         b) It's okay to NOT maintain the ratio on a per-day basis

I plead guilty to only half thinking this through, and after being
forced to clarify I realize I wasn't quite asking for the right thing.
It took me a while to figure out exactly what I was asking for, and
trust me, it does make sense.  But you're right, it isn't easy to
explain, and I don't need it that bad, and I wouldn't see it 15.0, if
at all, and you've got more important mail at the moment.  Another time.

                        Donald

Date: 05-10-93 (19:57)              Number: 62897 of 63094 (Refer# NONE)
  To: ALL
From: ERIC SCALES
Subj: EDSQuote Fully Operatiional
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)



  Just wanted to let everyone know that today's 05-10-93 17:00 release has
corrected the problem of not displaying a quote with EDSQuote..


    Thanks!
    ES

Date: 05-10-93 (20:55)              Number: 62909 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ERIC LUNDBERG
Subj: BETA report              
Read: 05-11-93 (11:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-07-93 18:08:00                        


Hi David,

        This is more of sujestion than a bug but just before
        you download a file there is a new prompt for list,protocol
        edit etc.
        When you chose protocol it defaults to NONE no matter what
        the default and I think it should use the default protocol.
        Since it does not and you hit enter you have to go through
        the motions of download again..........

        Thanks.......  Sorry I know you have more important things
        to deal with but just thought I would mention it.

        I have to say though I am VERY impressed with PCBoard 15.0

                                        Eric Lundberg

Date: 05-10-93 (21:06)              Number: 62910 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ERIC LUNDBERG
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBPACK.EXE - 05-04-93 13:08:00                        


        I have just read the history for PCBPACK and this was not
        mentioned so here it is.

        I pack my message online and when I chose the date 1/1/93
        weather I chose to remove PRIVATE+RECIEVED or not it locks
        my computer up.   I am doing it localy with QEMM 6.03 and
        not in any multitasker. I am also chosing renumber with
        starting at 1 and I see in the new history that this subject
        has been brought up but since it is a pain to logon here
        ( 550 redials ) I thought I would tell you now.

                                                Eric Lundberg

Date: 05-10-93 (22:14)              Number: 62914 of 63094 (Refer# 62037)
  To: DAVID TERRY
From: GREGG GRAUBINS
Subj: BETA report              
Read: 05-11-93 (11:35)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> 1) Sharing violations on pcbstats.dat
->
-> Using what software?  (i.e. what software is accessing that file?)

I found that using Instareg (Which has not been updated by the author to work
with v15.0 of PCBoard) has not been working. It reports a "Sharing
Violation"... But doesn't tell you which file.

                         į Gregg Graubins 

Date: 05-10-93 (22:15)              Number: 62915 of 63094 (Refer# 62905)
  To: JEFF SUMBERG
From: DAVID TERRY
Subj: Overlaid?                
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is there an "overlaid" version of the code for version 15, or has mempry
-> requirements been somehow lowered as to not need it anymore? I run the
-> overlaid version here - always have. The extra memory is needed.

All versions are now overlaid.  There is no longer a NON-overlay version.

                                          David W. Terry 

Date: 05-10-93 (22:16)              Number: 62916 of 63094 (Refer# 62908)
  To: JAMES DEAL
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am running on a Lantastic 5.0 network and I had a weird problem with the
-> file attachments.  When I would save a message with a file
-> attachment in the main section of the program, would upload the message
-> check it and then saying SAVING MESSAGE ##### and then she locked.

There were fixes in today's release for file attachments.  Give it a try and
then report back on the 5/10 release and let me know the status of your report.

                                          David W. Terry 

Date: 05-10-93 (23:55)              Number: 62920 of 63094 (Refer# 62876)
  To: DAVID TERRY
From: RICK DILORENZO
Subj: OTHER:  PCBOARD 05-07-93 18:03:00
Read: 05-11-93 (11:39)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Most people with those exact descriptions have REMOVED the line from
-> their board.bat files that runs the event.
->
-> You MUST have in your board.bat a line that looks like this:
->
->       IF EXIST EVENT.BAT EVENT
->
-> That is the line that *runs* the event.   Check it out and see if you
-> have done the same thing.

 Guilty as charged!  I read in a readme doc / upgrade text somewhere
that I was supposed to remove a line in my BOARD.BAT that had to do with
Event.  There were two of them, I removed both.  Guess only one of them
needed removing?

  Rick

Date: 05-11-93 (00:48)              Number: 62924 of 63094 (Refer# 62788)
  To: JIM WENZEL
From: RICK WELSHANS
Subj: OTHER:  BETA DOOR 05-07-9
Read: 05-11-93 (00:54)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Try BETA;NEW;NOFLAG this will grab beta.zip for you but will NOT set
-> the flagged flag.. (if you know what I mean)_

Ah.  Great - thanks, Jim!

Date: 05-11-93 (00:55)              Number: 62925 of 63094 (Refer# 62283)
  To: DEAN LAVIOLETTE
From: BILL MARTIN
Subj: BEta fix.....            
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Don't know why I get this error when I save from PCBSETUP.  Pressing ESC or
-> RETURN 4 or 5 times gets me out.  Don't know which file it is not finding.
->                Ŀ
->                                                            
->                 (2:3) Error Opening File - File not found  
->                                                            
->                                                            
->                                                            
->                         press any key to continue          
->                                                            
->                

The above is caused by having blank conferences, and not assigning them a
MSGS file. I have blank conferences to hold places for adding/removing
net conferences. With the new code, you will have to call them something,
and assign them a MSGS file. I make them private and call them X and
specify c:\pcb\x\msgs as the file. The callers never see them. I also
specified a security level of 254 so I dont have to look at them in
Qmail. Let me know if you need any more help on this.

Bill Martin, PCB14.5a/10 #018155 Lurking
---
  DeLuxe 1.26b #1343s  Lightning System III, Stateline, Nv. Node 3


Date: 05-11-93 (01:01)              Number: 62927 of 63094 (Refer# NONE)
  To: ALL
From: LARRY STEELE
Subj: (W)rite info command     
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

I have seen a couple of messages about the 'W' command not working for
some sysops.  If you take a look at your PWRD file and press F2 to
toggle the display you will seen at the end 'ALLOW MULTI-LOGONS' if this
field has a 'Y' in it then you will not be able to use this command no
matter what security level you are at.  I'm sure that this is a security
reason.  If I'm mistaken please let me know.

Larry Steele

Date: 05-11-93 (01:03)              Number: 62928 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: DAVID BONDS
Subj: BETA report              
Read: 05-11-93 (11:42)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Ŀ
 PCBOARD.EXE - 05-07-93 18:08:00                        


This may of been fixed in the 5-10 beta which I am about to upload, but
am just going to share a short story of my beta woes to date.  ;-)

Installed the 5-7 18:08beta on 5-8, everything ran fairly smoothly for
several hours, with myself, my cosysop, and another local sysop throwing
everything we had at it.  Then it reduced our users file from 500+ users
to 92.  Backed up from a old backup (one right before the beta was a
"quickie backup" (read, zipped /pcb, /pcb/main, /pcb/gen onto another
drive) and the backup got crosslinked) and started finding things I'd
never seen, like :

**************************************************************
05-09-93 (06:53) (1) LARRY BIBICH Off Normally
      Minutes Used: 6
      Back from DOS at 06:53
      Opened Door (QMAIL4) at 06:53
      Back from DOS at 06:53
      Opened Door (QMAIL4) at 06:53
      Expert mode is now on, Larry ...
      Comment Left: Main Board # 2665
      Back from DOS at 06:49
      Opened Door (QMAIL4) at 06:49
      Back from DOS at 06:48
      Opened Door (QMAIL4) at 06:47
      Back from DOS at 06:47
      Opened Door (QMAIL4) at 06:47
05-09-93 (06:47) (1) LARRY BIBICH (14400E) (G) HOUSTON, TX
      User Record Number Bad!
**************************************************************

(The User Record Number Bad! error)

and even one I'd never expected to see! :

**************************************************************
05-09-93 (12:47) (1) ADAM BLOOM Off Abnormally
      Minutes Used: 77
      Time Limit Exceeded.
      Back from DOS at 12:47
      Caller Exited to DOS at 12:29
      Directory Scan for (050993)
      Message Left: Main Board # 2672
      Directory Scan for (050993)
      Message Left: Main Board # 2671
      (E:\MSG1.$$$) is missing!
      Message Left: Main Board # 2670
      Back from DOS at 12:12
      Caller Exited to DOS at 11:48
      Back from DOS at 11:48
      (D) C-EDGE.QWK  Completed using  , Size: 9656
      Scan: 0 Files, 0 Personal, 3 Total
      Opened Door (KINGMAIL) at 11:42
      Back from DOS at 11:42
      Caller Exited to DOS at 11:40
      Back from DOS at 11:40
      (D) C-EDGE.QWK Completed using Z via Qmail (133k)
      Opened Door (QMAIL4) at 11:34
      Message Killed: Main Board # 2666
      Message Left: Main Board # 2669
      Message Killed: Main Board # 2665
      Message Left: Main Board # 2668
      Message Killed: Main Board # 2664
      Message Left: Main Board # 2667
05-09-93 (11:30) (1) DAVID BONDS (14400E) (G) HOUSTON, TEXAS
**************************************************************

The last shell to DOS I did a "user file pack while online" - apparently it
confused me with someone else!

The USERS.INF file has been trashed twice, and all TPAs mysteriously
disappreared once (just gone, as never installed).

I know none if this can really be duplicated, but thought in beta test, you'd
like to know everything that happens that is related to the software!  ;-)

Date: 05-11-93 (11:46)              Number: 62937 of 63094 (Refer# 62714)
  To: DAVID TERRY
From: PETER BYRNE
Subj: CNAMES file              
Read: 05-11-93 (11:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

DT>Download CHANGE.ZIP and use it to perform global modifications on your setup

As far as I can tell from the documentation, CHANGE will not make the
changes that I need to make to CNAMES.

I need to take the information that is in the NEWS file field in each
conference (e.g. C:\EMAIL\A000#049\CONF004) and move it into the INTRO
field. Then I need to put new information into the NEWS field. I need
to do this for every conference on my board.

I could probably use CHANGE to modify the contents of the NEWS field,
but I can't see any way of moving the existing contents of the NEWS
field into the INTRO field - there is nothing currently in the INTRO
field to do a search and replace on, for example.

The other immediate need is to set the "Disable Private Messages" flag
to Y in all but a couple of conferences. While this flag currently
*does* have a value to search on it is only N and I can't see any way
using CHANGE to pick out the particular N that I want to change.
---
  DeLuxe 1.25 #307s  peterb@mclprism.co.uk

Date: 05-11-93 (02:10)              Number: 62939 of 63094 (Refer# 62715)
  To: DAVID TERRY
From: PETER BYRNE
Subj: Swapping PCBOARD.DATs    
Read: 05-11-93 (11:46)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

DT>But if the "real question" here is...  Can you swap pcboard.dat files during
DT>events, the answer is yes.

Sorry, yes that was the real question. However, having discovered
CHANGE, I no longer need to swap PCBOARD.DAT files anyway. While
CHANGE may not solve my problems with CNAMES, it works great for
changing things in PCBOARD.DAT (like enabling and disabling the COM
port, which is my primary requirement).
---
  DeLuxe 1.25 #307s  peterb@mclprism.co.uk


Date: 05-11-93 (05:02)              Number: 62958 of 63094 (Refer# 62727)
  To: GARDINER JONES
From: LEWIS SCHALLER
Subj: EVENT not running - possible fix
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I saw several messages the last few days from people who said their
-> EVENTs wouldn't run after upgrading to PCB15.0 beta code.  I had the
-> same problem.  After pulling my hair out for a day I came across a
-> fix. The PCBSETUP program took my original defaults and tried to
-> included them properly into the new PCBOARD.DAT file (or is it
-> PCBOARD.SYS?) Anyway, the Event selection had stuffed my path
-> "D:\PCB\GEN\" into the LOCATION of my events files, and I had
-> dutifully put my event files into the PCB\MAIN subdirectory as
-> suggested by the documentation.  I corrected this entry to point to
-> \PCB\MAIN and, voila, my events now run!

Mine did the same thing, I though I fixed it though, but now 2 out of my
3 events are running, 1 of them on node 1 won't run.?????

Date: 05-11-93 (05:46)              Number: 62959 of 63094 (Refer# 62918)
  To: GORDON MALONE
From: DAVID TERRY
Subj: FIDO PCBoard Echo        
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Imagine your quite the busy one these days :)
->
-> Was just wondering if we will be able to contact you via the new Fido
-> PCBoard support echo?
->
-> Is it operational yet?

What "new Fido PCBoard support echo" would that be?

If it is echoing into our PCBoard Support Conference (#37) then yes.  However,
in case you missed rule #2 for beta testing here ...  ALL v15.0 reports belong
right here in THIS conference.

Please do NOT use any netmail system for beta reports or v15.0 questions.

Thanks.
                                          David W. Terry 

Date: 05-11-93 (05:48)              Number: 62960 of 63094 (Refer# 62921)
  To: ZEIN DAWOOD
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The new version is still giving me problems with the usernet.xxx file. I
-> have a door set-up for new users and a deposit door. Everytime a user exits
-> from the door, it gives me an error message about the usernet.xxx file. It
-> says the file is in the wrong format. To correct this problem, I have added
-> a line in my board.bat file to delete the usernet.xxx file before running
-> pcboard. It has fixed the problem. Is there any other way I can fix this
-> problem?

Yeah...  contact the DOOR author and ask that the software be upgraded to
support the v15.0 usernet.xxx file.

Alternatively, you might make a special pcboard.dat file that ONLY that door
sees ... and in it, set the usernet.xxx file to some other filename and/or
directory on your system.  That way it can't hit the "live" copy of the file.

                                          David W. Terry 

Date: 05-11-93 (05:52)              Number: 62962 of 63094 (Refer# 62922)
  To: PETER WADSWORTH
From: DAVID TERRY
Subj: Buglet report            
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> (996 min. left) Main Board Command? w
-> (W) Menu Selection is not available, Peter.
->
-> The security level for the (W)rite command is 20.  I'm way higher than that!
-> Can you imagine why this didn't work?  I've set up the Alias PCA and allowed
-> file attachments.

Not a bug.  You have mis-used a feature without reading up on the effects of
the feature.  Here's the relevant information out of the WHATSNEW file:

         Answering YES to "Multiple Logins" means that more than one caller
         can be online using the same user-id without getting the "Name
         already in use on another node" message.

         This setting allows you to establish one or more accounts that can be
         used as DEMO accounts.  That is, accounts where you can hand out the
         user-id and password and allow more than one user to be online at the
         same time utilizing that user-id.

         ...

         3) Users of such accounts will be unable to use the (W)rite User
            Info command.  This avoids the possibility that someone might,
            either accidently or maliciously, change the password on the
            account thus stopping anyone else from using the multiple user
            account.  It also prevents the user from changing the city/state
            information which might, again either accidently or maliciously,
            be changed to something that is not desired by the sysop for that
            account.

                                          David W. Terry 

Date: 05-11-93 (05:57)              Number: 62963 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: GARY WOOD
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93 06:08:00                        



I have yet to run run an event successfully on all of my nodes.  Am
sure it *MUST* be operator error but need assistance just the same!

In PCBSETUP the event screen reads as follows on ALL nodes:

                                 Y
                                 C:\PCB\MAIN\CHAT\EVENT.DAT
                                 C:\PCB\MAIN\CHAT\

                                  5
                                 Y
                                 20

When pressing F2 on NAME/LOCATION OF EVENT.DAT field here is the
setup:

Y   E   EVENT   5:00   5:15   YYYYYYY    00-00-00

I have the following files in the C:\PCB\MAIN\CHAT\ directory

EVENT.DAT, EVENT, EVENT.002, EVENT.003, EVENT.004, EVENT.005, EVENT.006,
EVENT.007, EVENT.008, EVENT.009, and EVENT.010.

Only nodes 1 and 4 will run the event.  All EVENT.* files are different
as all nodes run a different function, most of which, pause and wait.

When I run PCBSETUP and view the EVENT.DAT file from nodes 1 or 4 I
see the current run date in the last field.  Running PCBSETUP from the
other nodes, the last field is 00-00-00.  ALL nodes are pointing to the
same EVENT.DAT in the SAME directory on disk.  All BOARD.BAT files have
" if exist event.bat event " in them and I have *removed* " if exist
event.bat rename event.bat event.sys ".

Any help would be appreciated.  Other than the above problem, all is
running well.  Thank you.

Gary Wood
Passport System

Date: 05-11-93 (05:57)              Number: 62968 of 63094 (Refer# 62929)
  To: FRED MCCLAREN
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> What directory would they go in?  Do they need a special directory dedicated
-> to attachments and should this be in the FSEC listings?

Just about any directory will do.  You can put File Attachments in separate,
unique, directories for each conference.  Or you could group them all together
(all conference area file attachments) into a single directory.

There are no restrictions as to where you can put it.

And there is no need to use the FSEC file unless you WANT to use the FSEC file.
Perhaps to make the file attachments "FREE" or "NOTIME" or to put a security
level restriction on them, etc.

The only restriction that I mentioned (that caused your reply) was that you
should not put the file attachments in your upload directory (or any other
directory from which you can directly download files) because file attachments
are not regular download files.  Their names have been changed.  In addition,
the file subsystem is incapable of enforcing "access" to file attachments.

So if you'll just keep them in a directory that is not part of the download
path you'll be okay.
                                          David W. Terry 

Date: 05-11-93 (06:00)              Number: 62969 of 63094 (Refer# 62930)
  To: CHRIS GIFFORD
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am also having problems with the event running.  I am running a two node
-> system with one event on each node.  What the system does is when the two
-> minute suspension, the code drops to DOS with a cursor in the upper left
-> corner, it then drops down about three lines then the system recycles.

Most people who have described something similar, where it DOES drop out to the
event, but then recycles, have accidentally REMOVED the line from the board.bat
file that is supposed to RUN the event.

Go back into your board.bat file and make sure that, underneath the call to
pcboard.exe, you have a line that says:

        IF EXIST EVENT.BAT EVENT

That is the line that runs the event.

The README.1ST file made mention of removing the line UP ABOVE that stated
IF EXIST EVENT.BAT REN EVENT.BAT and people have gone off and removed BOTH
lines instead of just the one line that was mentioned.

Check your board.bat file out and see if you have done the same thing.

                                          David W. Terry 

Date: 05-11-93 (06:04)              Number: 62970 of 63094 (Refer# 62931)
  To: MARK COMPTON
From: DAVID TERRY
Subj: stuff                    
Read: 05-11-93 (12:59)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Maybe I'm missing something here, but I'm NOT getting the "scan message
-> base..." after the "new mail" read prompt.

Go into PCBSetup : Configuration Options : Messages and then look about half
way down the screen.  What is the answer to "Disable Message Scan Prompt"?

I'm guessing it is set to 'Y'.  If it is not, please give me a voice call at
801-261-1686 right away and we'll look into this further.

-> Also, another question.  I never ran across this in 14.5a, (but may have
-> never tried it either).  When one opens a capture file with Alt-F, captures
-> the desired text, then logs off without closing the capture file with Alt-F
-> again, the file is not saved.  Is this correct?  Should it not close and
-> save regardless?

That is the way all of the v14.5, v14.5a and v15.0 have worked.  If you forget
to close the capture file PCBoard "cleans up after itself" and removes the file
so that it isn't left dangling.

Just remember to always hit ALT-F to close the file when done.

                                          David W. Terry 

Date: 05-11-93 (06:16)              Number: 62973 of 63094 (Refer# 62941)
  To: IVAN WINDON
From: DAVID TERRY
Subj: OTHER:  EVENT 05-07-93 18:08:00
Read: 05-11-93 (07:27)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The board keeps telling everyone that USERS is not available.  How do I make
-> it available?  It won't let you type it, it will just give an error message.
-> This is from the same version and time as the one I told about the event.

This information is in the WHATSNEW file for aliases.  Here it is:

         While inside a conference where aliases are allowed, the security
         level requirement for the USERS command is changed to become equal to
         that which is required to use Sysop Function 7.  This allows the sysop
         to continue to use the USERS command while making it impossible for
         callers to use it.  This is to avoid the possibility of having a user
         compare logon dates/times or name ordering in the USERS list seen
         outside of the conference with a USERS list that might be seen inside.

                                          David W. Terry 

Date: 05-11-93 (06:28)              Number: 62980 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: DAN VEANER
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93                                 


May 7 - 18:08  Code / 386/25  2 node system running on Desqview X

Problem:       Rime mail run event not running

What happens:  When the mail event should run nothing happens.  The
               other events run just fine.  By "nothing happens" I
               mean that the call waiting screen stays in place,
               if a user is on node 2 he is not warned about an
               impending event, the date is not changed in the
               event setup chart, and the mailevt file does not run.

Setup:         I have 2 different pcboard.dat files, but they point to
               a lot of the same files.  They share the same event.dat
               file, and both point to \pcb\main for the event files.

Act  Mod  Batch    Begin   End    SMTWTFS   Date      Last
===  ===  =====    =====   =====  =======   ========  ========
N    E    RIMEEVT  03:25   04:20  YYYYYYY             00-00-00
Y    E    MAINEVT  07:00   O7:30  YYYYYYY             05-10-93
Y    E    TESTEVT  06:40   07:00  YYYYYYY             05-11-93
Y    E    MAILEVT  03:25   03:55  YYYYYYY             05-11-93

I  am reporting this at 6:59am.  Both nodes just went down to run MAINEVT.
(MAINEVT is running as I type this)

In \pcb\main are the following files:

mainevt.001     Node 1 does all the work
mainevt.002     Node 2 waits
rimeevt.002     Node 2 does the mail run.
testevt.002     Node 2 does DOS DIR command for testing
mailevt.002     An exact copy of rimeevt.002

What I did:    I let it run on May 5, and when it didn't work I checked
               the event.doc and carefully went over each step.  I decided
               to leave it alone to see what it did on May 6.  Nothing.
               Added TESTEVT - it runs just fine every day I tried it.
               May 7 I changed the order of the events (putting RIMEEVT
               on the top of the list).  Same results May 8 and 9 (MAINEVT
               runs, RIMEEVT does not run.

               May 10:  Made an exact copy of RIMEEVT called MAILEVT and
               set it up to run at 7:30 am.  It ran!  I changed the time
               to 3:25.  I made RIMEEVT inactive.  I quit PCBOARD and
               reloaded it.   <======= This is important =====

               May 11:  Got up at 3:20am to watch the event.  I am set up
               to go down 2 minutes before an event starts - at 3:23
               nothing happened.  At 3:26 I ran pcbsetup from the call
               waiting screen to make sure I had set the time correctly.
               I had.  Due to a mistake in my setup node 2 was dropping to
               DOS when returning from pcbsetup.  I typed "board" and
               immediately upon loading MAILEVT ran!!!

Just before typing this report I went over my node 2 setup with a fine
tooth comb to make it match the node 1 setup (now pcboard loads when I
return from pcbsetup).  I have tried to make this report as complete as
possible.

Questions:

1- In Desqview X should my nodes be set up with 1 text page?  (In checking
   my setup I noticed node 1 was set for 1 and node 2 was set for 4.  I
   made node 2 match node 1 (with 1 txt page).

2- I also noticed my main event is hanging at a point where it uses the
   CALL command to call a batch file that also uses a CALL command.  This
   did _not_ happen with pcb 14.5.  I have rearranged it so MAINEVT only
   calls the second batch file (it calls autoscan for virus checking) and
   will watch it tomorrow morning.

Dan

Date: 05-11-93 (06:29)              Number: 62981 of 63094 (Refer# 62961)
  To: STEW FRANCIS
From: DAVID TERRY
Subj: reposting of PPL files, etc
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is it permissable to repost the various PPL/PPE files found on this bbs? I'd
-> like to set up a separate file area for PCBoard 15 specific files including
-> the PPEs, but thought I'd best check with you first.

Yes, this is fine.

All we ask is that you not post any of the commercial files (the PCBoard code
and utilities that we provide).

So if you find it in the upload directory of this conference then it can
probably be posted publicly elsewhere.  But if you find it in directory #2 then
it should probably not be posted.  (our files are in directory #2)

                                          David W. Terry 

Date: 05-11-93 (06:34)              Number: 62984 of 63094 (Refer# 62983)
  To: DAN VEANER
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> What happens:  I called my board and typed QWK D
->              When I tried to read the packet using Sparky's Deluxe2
->              reader it was a total mess:  the message headers were
->              confused with each other, and when I tried to read
->              a message it hung the computer.
->              I rebooted and called the board again, uploaded my pointers
->              and used qmail4 to download the same messages.  Worked fine.

Try running PCBPACK /AREA:# /INDEX /OLDINDEX (where '#' is the number of the
conference that you tried to read).

Then re-try your QWK D test and report back on the status of this problem.

If you can duplicate the problem, please call ASAP.  You can reach me voice at
801-261-1686.
                                          David W. Terry 

Date: 05-11-93 (07:45)              Number: 62988 of 63094 (Refer# 62812)
  To: DAVID TERRY
From: ALLEN STONE
Subj: BETA report              
Read: 05-11-93 (12:31)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Hi David,
I am using corel scsi for my driver not the one that came with the
changers. The cd rom driver is cuni_asp.sys from corel scsi, so I am
using a different driver. Can you think of anything else.

Date: 05-11-93 (07:50)              Number: 62990 of 63094 (Refer# 62988)
  To: ALLEN STONE
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (07:52)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I am using corel scsi for my driver not the one that came with the changers.
-> The cd rom driver is cuni_asp.sys from corel scsi, so I am using a different
-> driver. Can you think of anything else.

My suggestion was that you try a DIFFERENT driver (something besides what you
are currently using).  Give it a try and see what happens.

                                          David W. Terry 

Date: 05-11-93 (07:54)              Number: 62995 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: BRYAN DEVANEY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-07-93                                 



I have been unable to get a second event to run while one node is down.
I have been using the DVWAIT program to drop one node down for over a
year.  It doesn't seem to want to work now.  I have it named WAIT.002
(node #2 is the node I want to drop).  I try to run MAINEVNT.001 on node
#1 one minute after WAIT.002 kicks in, but it will not run until
WAIT.002 is either interrupted, or completed.

Date: 05-11-93 (07:55)              Number: 62996 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: ALLEN STONE
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE / FILE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

Here is the caller's log.

It is relly a problem to do with the event capabilities and the event not
catching a 00:02 event. Allen.

Date: 05-11-93 (07:59)              Number: 62997 of 63094 (Refer# 62891)
  To: TOM SOUTHARD
From: DANIEL CHLARSON
Subj: file attachment          
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Where do I tell PCBoard the directory where my attached files are
-> kept, they default now to the PCB root directory (UUGGHH!) . Other
-> than that,It works fine. one other thing, if durring PCB Pack, the
-> message is deleted or of the Message is killed, will the attached
-> file also be deleted?

It's on each conference setup screen.  "Location of attachments".  And,
yes, PCBPack will delete the attached files.

Daniel
Salt Air Sysop

Date: 05-11-93 (08:00)              Number: 62998 of 63094 (Refer# 62893)
  To: TOM SOUTHARD
From: DANIEL CHLARSON
Subj: Dbase                    
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Are there any Conversion programs to convertuser info to a Dbase
-> file? I currently force new users into a door to duplicate their
-> Address info, so I can save in Dbase form to use for Mailings address
-> lables etc.. Would be a handy tool for sysops..

You'll need to do a Z scan in conference 1 for DBASE or DATABASE.

Daniel
Salt Air Sysop

Date: 05-10-93 (20:32)              Number: 62999 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: JAMES DEAL
Subj: OTHER:  CHANGE 04-15-93  
Read: 05-11-93 (12:32)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

When used the change program used the following line to change the
DIR.LST file:

CHANGE PCBOARD.DAT /DIRS /FROM:Z: /TO:D:

This proceded to create a DIR.LST file which was 47.9 megabyte in size
thus filling the hard dirve's empty space.  There were only 44 entries
in this file.

                                                Jim

Date: 05-11-93 (08:47)              Number: 63009 of 63094 (Refer# 62919)
  To: AL SANDE
From: LOUIS ZIRKEL
Subj: PCB15 EVENT              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Change it so it doesn't cross midnight.  Crossing midnight in an event
is usually a bad idea.  Make the start time something like 00:05 and the end
something later.  I'm working on a fix, but want to make sure I get it right
<grin>...

        -= Louis Zirkel III =-

Date: 05-11-93 (08:48)              Number: 63010 of 63094 (Refer# 62881)
  To: RAYMOND CLEMENTS
From: LOUIS ZIRKEL
Subj: New PCBPACK.EXE Posted   
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Yes, and it's there for a reason...  Are you having problems with it?

        -= Louis Zirkel III =-

Date: 05-11-93 (09:16)              Number: 63016 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: WILLIAM P. STEWART
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES


Ŀ
 PCBPACK.EXE - 05-04-93 01:08:00                        


Well even though I just picked up the new one, I thought I'd ask this
anyway:

While packing, what does "Packout date found" mean?

Also, why if I have 600K of free memory (613792bytes), do I then have
only 516000 bytes when running PCBpack? And because of that, I get this
message: "Not enough memory to check for duplicates"?

See ya later.

William P. Stewart
Computers & Dreams BBS

Date: 05-11-93 (09:17)              Number: 63017 of 63094 (Refer# 63016)
  To: WILLIAM P. STEWART
From: LOUIS ZIRKEL
Subj: BETA report              
Read: 05-11-93 (14:00)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

        The PACKOUT date is basically a date that you can set on a message by
typing a D at the security prompt and entering a date.  This tells PCBPack NOT
to pack that message out UNTIL that date.

        -= Louis Zirkel III =-

Date: 05-11-93 (09:41)              Number: 63019 of 63094 (Refer# 63015)
  To: JEFF BINKLEY
From: DAVID TERRY
Subj: PCBoard 15.0 Question    
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I am not sure if this is a bug or just a design feature of PCBoard. Today I
-> movedmy Main Board conference area from the drive that contains the PCB
-> files to another drive.  My reason was due to disk space and the numner of
-> uploads I have been getting. Anyway my question is now when I do uploads
-> into the Main board the amount of disk space available shows for the old
-> upload area (i.e. the same disk as PCBoard is on) and not the new drive
-> where the upload area is really at.  Is this normal ??

Well...  it's normal in that it means you didn't change what you thought you
were changing.  <grin>

The upload disk space shown is that amount of free space available on the drive
holding the PRIVATE UPLOAD directory.

This is because *all* uploads initially go to the private upload directory and,
from there, they are moved out to the public upload directory only if they
'pass' the testing requirements.

The best bet is to always keep the private and public directories on the same
drive.  This not only prevents a problem of filling one or the other up, but it
also makes the process of moving the newly uploaded file from private to public
that much quicker because a rename instead of a copy/delete operation is
performed.

So check your private upload directory.  Apparently you didn't move it.  :-)

                                         David W. Terry 

Date: 05-11-93 (09:43)              Number: 63021 of 63094 (Refer# 62875)
  To: DAVID TERRY
From: BOB NEDDO
Subj: BETA report              
Read: 05-11-93 (12:41)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I can't seem to get the new "Read your personal mail now" prompts nor
-> the "force" users to read waiting mail to work.

-> If the "pop-up" message "You have mail waiting" appears on the
-> screen, so will the "read it now?" prompt.  There is only one
-> exception:  if the caller does not have sufficient security to read
-> the messages then he won't be asked if he wants to read them.  (kinda
-> dumb, but it had to be coded in there)
-> There is only one other possibility I can think of...   are you sure
-> you are running v15.0 on that node?  <grin>

You forgot one other possibility -- that the "configuring sysop" (that's
me) didn't set it up properly.  I checked 3 nodes and they were set up
correctly, but my local only node wasn't.  <embarrassed grin>.

Of course, once I turned on the option in PCBSetup it works correctly.
Thanks for your quick response.

Date: 05-11-93 (09:43)              Number: 63022 of 63094 (Refer# 63012)
  To: JEFF BINKLEY
From: DAVID TERRY
Subj: Error Levels             
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Are there any new errorlevels (besides the fax detection) which were added
-> with PCBoard 15.0  ?

All of the errorlevels that v15.0 supports are listed at the bottom of the
WHATSNEW file.  They are:

 info    The following are the current ERRORLEVELS supported and returned by
         PCBoard:

               0 = normal exit at sysop request
               1 = exit to dos for the event
               2 = exit to dos for a door
               3 = exit to dos for remote dos operation
               4 = exit to dos to run pcbpack
               5 = exit to dos caused by caller saying goodbye
               6 = exit to dos to recycle through board.bat
               7 = exit to dos to handle incoming FAX
              99 = an error occured which dropped it to dos, board.bat will
                   recycle the system

                                         David W. Terry 

Date: 05-11-93 (09:44)              Number: 63023 of 63094 (Refer# 63011)
  To: JEFF BINKLEY
From: DAVID TERRY
Subj: pcbfiles.lst             
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> What about downloads ?  I assume ALLFILES.LST is not searched on downloads
-> since this may make files available in conferences where you don't want them
-> available from.  Am I correct ?

You are correct.
                                         David W. Terry 

Date: 05-11-93 (09:50)              Number: 63025 of 63094 (Refer# 63002)
  To: MARIO POZZETTI
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (11:29)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> I assume that the switch "Validate TO: Name in Messages" is valid only for
-> Main Board messages, the contrary would mean that I should have a userfile
-> as large as the echo network community :)

You are correct ... mostly.

Part of the validation procedure is also to let PCBoard find the user and set
the mail waiting flag for the user based on what was found.

So you want to leave validation turned on all the time.

Then...  in an echoed conference PCBoard will automatically avoid warning the
caller about a user-not-found on the assumption that the user might be accessed
via netmail.

-> In this case how is it possible for a user to write a messages to me
-> misspelled and the system accept it? This has happened yesterday, one user
-> wrote a msg (not a comment) to Mario Pozzeti (mind the spelling - just one
-> "t") and PCB did accept it.

In a non-echoed conference, where PCBoard warns if the user name was not found,
the caller has the choice of letting PCBoard search for a SOUNDEX "sound alike"
name, or accepting the spelling "as is".

In other words, PCBoard isn't going to REFUSE to accept MARIO POZZETI.  But it
*will* warn the caller and give the caller a chance to decide what to do.

And, of course, if the caller uploads a message via a mail door then PCBoard is
completely out of the loop and the caller can spell the name however he wants
with no warnings whatsoever.
                                         David W. Terry 

Date: 05-11-93 (09:53)              Number: 63027 of 63094 (Refer# 62388)
  To: ART EMERY
From: LOUIS ZIRKEL
Subj: EVENT.DAT file           
Read: 05-11-93 (13:26)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        This was a problem, but it should be fixed now.  Let me know if it
happens again.  BTW, you'll want to remove your EVENT.DAT and recreate it with
the new PCBSetup.

        -= Louis Zirkel III =-

Date: 05-11-93 (09:55)              Number: 63028 of 63094 (Refer# 63000)
  To: MARIO POZZETTI
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (11:34)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> David, I set up my system so that it would NOT write local calls to the
-> callwaiting screen but this only wroks on node1, on nodes 2,3 & 4 I still
-> see my name as th Last Caller. The switch is (I guess "exclude local logins
-> from stats) and I have set it to Y on all 4 nodes.

Please perform the following steps:

1) Take all nodes down.
2) Change to the directory for node 1.
3) Run PCBSetup to set the switch for local logins.
4) Exit and save.
5) Repeat steps 2 thru 4 explicitly (no "cheating", no "skipping") do them.

Now continue:

6) Log into node 1 locally.
7) Logoff and then look at the call waiting screen.
8) Repeat steps 6 & 7 on each node.

I believe you will discover that you were mistaken.

-> Another possible bug is that on node four I get "randomly" access debied
-> user in use on another node. This only happens on node 4 and the solution is
-> erasing USERNET.XXX  and let PCB recreate it, but I have NOT been able to
-> duplicate the situation.

Well, I can assure you that it isn't "at random" ... virtually nothing about
computers, which are deterministic machines, is at random.  Therefore, there is
a completely logically explanation for the symptoms once you uncover the cause.

My guess would be that sometimes you "reboot" or "close a window" without
actually logging out of the system.  Thus it has the username already in the
usernet.xxx file.

Properly exiting the system will cure this problem.

                                         David W. Terry 

Date: 05-11-93 (10:03)              Number: 63031 of 63094 (Refer# 63029)
  To: TIM NEFF
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> i have set up the psbsm for the ability to write a HANDLE to the users files
-> but have not been able to do so with the (W)rite command.. I do not see
-> where it asks for a handle (ALIAS). I have the alias flag set to yes in
-> pcbsetup..

New users will be prompted for an alias as they log in ... IF ... their
security level allows them to use an alias (see PWRD file).

Existing users will be prompted for an alias when using the (W)rite User Info
command ... IF ... they don't already have an alias ... OR IF ... you answer
'Y' to the Allow Alias Change question in PCBSetup.

I found a slight mis-wording of the above in the WHATSNEW file and below are
the changes to the text that have been made:

|        If PCBSetup :  Configuration Options :  System Control :  Allow Alias
|        Change is set to NO then once the Alias has been chosen it cannot
|        be changed except by leaving a comment to the sysop and asking the
|        sysop to change the alias.

See if this information will help.
                                         David W. Terry 

Date: 05-11-93 (10:07)              Number: 63032 of 63094 (Refer# 62880)
  To: JON ORTEN
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Can you tell me the format off the cmd.lst file.

For now, please use PCBSetup to edit that file.

-> can it be used to translate commands to suit our language?

Yes.

-> Are there some new HLP files for pcboard 15.0 to explain the new commands.

No.  We'll announce and post them when they are ready.  Right now they do not
even exist so continue using the v14.5a help files.

                                         David W. Terry 

Date: 05-11-93 (10:22)              Number: 63037 of 63094 (Refer# 62892)
  To: TOM SOUTHARD
From: SCOTT ROBISON
Subj: Re: sub menu             
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->    Now that is a fast reply, to be on line read your messages, join
->    another conference and have a reply as your leaving the sys? and at
->    6:00pm on a Saturday? Boy Do you ever sleep?

I was actually on my way out the door (wife was calling) and trying to at least
reply to *MY* mail that was waiting.  Even having responded to my mail, I had
about 175 or so messages waiting for me monday morning in this conference
alone.  Whew!  Can't afford to sleep or I'll get so far behind that I'd have to
quit and start from scratch somewhere else.  :)

   Scott Robison

Date: 05-11-93 (10:33)              Number: 63038 of 63094 (Refer# 62889)
  To: SCOTT YAGODA
From: DAVID TERRY
Subj: brdm.mnu                 
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

-> is it possible in the new menu setup to set a mnu to a user level as in the
-> old code you could have brdm and brdm25? If so please tell me how?

-> Well, you can't have a BRDM25.MNU if that's what you are asking.  What you
-> *CAN* do is have security specific display files.

-------------------------------------------------------------------------------
NOTE:  I wrote the message below thinking that v15.0 was *already* working this
way and then, to my dismay, discovered that it was not.  Okay, fine I said, the
NEXT release of v15.0 will allow you to do what I have described below.  So if
you use current code and it doesn't work, now you know why, grab the next
release (when it gets posted, perhaps later today) and then you can it.
-------------------------------------------------------------------------------

You can ALSO create a BRDM25 file and inside of it put the following line:

        $C:\PCB\GEN\BRDM25.MNU

So...  while PCBoard doesn't look for a BRDM25.MNU file, it DOES look for a
BRDM25 file and you can then force PCBoard to load an MNU file (of any name you
choose - I only picked BRDM25.MNU because that is what you picked).

The same thing would work for language-specific files or even RIPscrip specific
files.  Here are two more examples:

    Inside of the file BRDMR, which is for RIPscrip, place:

        $C:\PCB\GEN\BRDMR.MNU

    Inside of the file BRDM.FRE, which is a French version of BRDM, place:

        $C:\PCB\GEN\BRDMFRE.MNU

Again, the actual names of the MNU files are not important.  What IS important
is the name of the display file, which works the same as it always has, and the
contents of the display file which, new for v15.0, lets you put a dollar sign
followed by a valid filename to run a MNU file.

(this is also possible in PCBTEXT prompts, a $FILESPEC will load an MNU file)

So, yes, you CAN create menus that are specific to users having certain levels,
or for users that use specific languages, or even for those using RIPscrip.

And, of course, MNU files themselves allow you to set "display files" within
them so you could actually just create a single common menu for all types and
let PCBoard figure out which 'display file' should be shown.  And this is a
round-about right back to what Scott said to you in the first place.

The one caution I would mention is this:  PCBoard is going to try to display
your BRDM file, this is going to launch your BRDM25.MNU file, which is then
going to display ANOTHER file.  My suggestion would be to ensure that you don't
go recursive ... ensure that the last display file shown does not launch yet
another MNU file.  Make sense?

The flexibiilty of v15.0 is enough to boggle the minds of many a sysop.  <grin>

                                         David W. Terry 

Date: 05-11-93 (10:33)              Number: 63039 of 63094 (Refer# 62894)
  To: TOM SOUTHARD
From: SCOTT ROBISON
Subj: >menu files              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Scott is there sa file around that lists what each field represents in .mnu
-> files?
-> wondering, so as I can edit them properly..

You may want to download the following files from file area 2 in this
conference:

-> MENUDOC.ZIP    1647  05-03-93* Some information on MNU (Menu) file layout.
->                                Forward any questions to Scott Robison.
->
-> MKPCBMNU.ZIP  26545  04-08-93  A utility to create and edit PCBoard MNU
->                                files for v15.0

   Scott Robison

Date: 05-11-93 (10:34)              Number: 63040 of 63094 (Refer# 63034)
  To: RAY SULICH
From: DAVID TERRY
Subj: OTHER:  FIXTEXT 04-09-93 
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The problem I reported "The return recept line cut off" was caused by
-> Fixtext.exe.  It truncated lines 636, 637, 667, 687, 698, and 705 along with
-> the return recept line in my PCBTEXT file. I returned the lines to their
-> defaults and it works fine now.

Do you still have a copy of your v14.5a PCBTEXT file?  If so, could you upload
it to me so I can run FIXTEXT on it and see if there is anything that can be
done about it?

Thanks.
                                         David W. Terry 

Date: 05-11-93 (10:34)              Number: 63041 of 63094 (Refer# 62996)
  To: ALLEN STONE
From: LOUIS ZIRKEL
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Allen, are you still running FrontDoor on your system?  If so, is it
set up to run any of your events?

        -= Louis Zirkel III =-

Date: 05-11-93 (10:36)              Number: 63042 of 63094 (Refer# 63036)
  To: REGINALD HIRSCH
From: DAVID TERRY
Subj: BETA report              
Read: 05-11-93 (12:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> David I must have deleted my gctopic and hlpmenu files for Group Chat as
-> these files are reported missing can I get them also help is missing is it
-> possible that pcbtext is also involved or just file config.

Download CHATMENU.ZIP from directory #2.
                                         David W. Terry 

Date: 05-11-93 (10:38)              Number: 63043 of 63094 (Refer# 62913)
  To: DAVID BAUER
From: SCOTT ROBISON
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> This must be another bug in the PPLC dated 05-03-93.

Not a bug, see conference 39 (PPL conference) for discussion of this topic.

   Scott Robison

Date: 05-11-93 (10:43)              Number: 63045 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: DYNATECH COMMUNICATIONS
Subj: RRRCMD.LST               
Read: 05-11-93 (13:09)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

PCBoard.EXE   452464  May-04 1993 1:25p

When I set up for Menu (sub menu) operation;

It seems the CMD translation feature does not work.  I used the new PPE
SEARCH,  this command works great before I went and did the sub menu
setup. After i did it I set up SEARCH,30,7,SEARCH.  I did not work,  I
did a run PPE file with the Search command in my MNU file and it did go
into the search menu but it sent the command with no spaces.  oh well
if I set it up with just the BRDM.  menu all works great.

Also I would like to join the several people who are getting QEMM
errors.  I have been running fine for about a year now.  But since I
upgraded I get QEMM detected memory......  Please advise what you need
from me to report these type problem.

Bill Rogers
DYNATECH COMMUNICATIONS

---
  QMPro 1.02 41-9022  CCITT- Can't Conceive Intelligent Thoughts Today

Date: 05-11-93 (10:49)              Number: 63048 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: STEVE CATMULL
Subj: BETA report              
Read: 05-11-93 (13:13)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBOARD.EXE - 05-10-93                                 


If the DLPATH.LST for a particular conference is blank and you attempt to
download a file, you will get the following:

    Checking Transfer Request. Please wait...


    PPL (39) Conference Command?

If you add an entry into the DLPATH.LST file then it will properly print "File
not found on disk" after the "Checking..." message.

At one time wouldn't it say that downloads were disabled if the DLPATH.LST file
was blank?

Date: 05-11-93 (11:02)              Number: 63053 of 63094 (Refer# 62559)
  To: WOLFGANG KRINGEL
From: LOUIS ZIRKEL
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        For now make the first event so that it DOESN'T cross midnight.  I'm
working on a fix for this, but for now the times being on different days
confuses the event manager.

        -= Louis Zirkel III =-

Date: 05-11-93 (11:05)              Number: 63055 of 63094 (Refer# 62898)
  To: JIM JUSKO
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> What about adding a security level for the QWK command?  I limit my "QWK"
-> door to subscribers only.

Since QWK is the same thing as reading a message it inherits the security level
for reading messages.

In fact, QWK is even more closely related to the R;Z command.  The only
difference being that the information is put into a QWK packet instead of just
a text file.

I would encourage your users to make use of QWK ... it'll mean less time spent
on your system by an individual user and more time available to other callers
that want to get online.

Of course, you could always put QWK into your CMD.LST file and then place a
security level requirement on it!  In other words, if it's not built right into
v15.0, there is very likely a way to make v15.0 do what you want!  <grin>

This is an example of what I mean:

          Command     Security  PPE/MNU File -or- Keystroke Replacement
          
   1) QWK                30     QWK^M

Now if a user with a security level LESS THAN 30 tries to use the QWK command
PCBoard will inform the user that he does not have sufficient security.

On the other hand, everyone else will then be prompted:

        QWK Commands: (D)ownload, (U)pload?

Notice that the above has disabled the ability to simply type QWK D and QWK U.
But there are at least two different ways that we can work around this:

          Command     Security  PPE/MNU File -or- Keystroke Replacement
          
   1) QWK                30     QWK^M
   2) QWKD               30     QWK D^M
   3) QWKU               30     QWK U^M

Now tell your callers to use QWK to be prompted for the command, or to use QWKD
for a download or QWKU for an upload.

You could even make it QWK for a download and REP for an upload.  The way you
define things in v15.0 is largely up to you.

And here is the second way that you could do it:

          Command     Security  PPE/MNU File -or- Keystroke Replacement
          
   1) QWK                30     QWK.PPE

Notice that this time we're going to launce a PPE file.  That is, a simple
program written using the PPL language, that will reconstruct the caller's QWK
command (to include the D or U and even the protocol letters, etc).

Here is what the PPL would look like:

        kbdstuff "QWK;"+tokenstr()+chr(13)

All this PPL really does is stuff the keyboard with the QWK command, a
semi-colon separator, and then the tokens (IF ANY) that the caller may have
supplied when he first issued the QWK command, and finally, a chr(13) is simply
a carriage return.

Finally...  you could get even more complex here.  Inside your PPL program you
could even have conditional tests to let users use the QWK command only during
certain hours of the day, only if their file ratios are in check, only if their
name is on some kind of list.  When you can program, you can do ANYTHING you
want!

So now you've found a several of ways that YOU can add a security level
requirement, even if one is not built right into PCBoard.

-> What about modifying for attachment of files.  Like a security needed to do
-> so.

There is no security level for attaching a file.  But you could write a PPL
program and attach it to the PCBTEXT prompt that is used to ask the caller for
Editor Commands.  Your PPL program could then require certain security levels,
etc.

PCBoard v15.0's flexibility ... just about anything is possible.  Have fun!

                                         David W. Terry 

Date: 05-11-93 (11:17)              Number: 63056 of 63094 (Refer# 62900)
  To: JIM JUSKO
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Also, I cannot get the "W" command to work.  I have that level set to 20.
-> and Me as a SYSOP level 135.

Most likely you have misused the Multiple Logins feature.  Here is the relevant
portion of the WHATSNEW file:

         Answering YES to "Multiple Logins" means that more than one caller
         can be online using the same user-id without getting the "Name
         already in use on another node" message.

         This setting allows you to establish one or more accounts that can be
         used as DEMO accounts.  That is, accounts where you can hand out the
         user-id and password and allow more than one user to be online at the
         same time utilizing that user-id.

         ...


         3) Users of such accounts will be unable to use the (W)rite User
            Info command.  This avoids the possibility that someone might,
            either accidently or maliciously, change the password on the
            account thus stopping anyone else from using the multiple user
            account.  It also prevents the user from changing the city/state
            information which might, again either accidently or maliciously,
            be changed to something that is not desired by the sysop for that
            account.

Since your account is not a DEMO ACCOUNT you should leave the multiple logins
setting (in the PWRD file) set to N.
                                         David W. Terry 

Date: 05-11-93 (11:19)              Number: 63057 of 63094 (Refer# 62903)
  To: LLOYD OSTERYOUNG
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->     Just a thought after plating with the new version. This pertain to
-> the ansi side especially with it's great header in the message bases, the
-> problem I found is the only place that shows what conference you are in is
-> the number in the bottom info line. Could you possibly show the conference
-> name in the message header? Thanks

Switch to the LONG message headers and you'll see that information.

The following two entries from the WHATSNEW file should explain what I mean:

 added   New message base commands:

            LONG        view long message headers
            SHORT       view short message headers


 added   New message headers.  These headers include several modifications:

         - There are now two ways of viewing the message headers - either in
           LONG format, or SHORT format.  See the "R LONG" and "R SHORT"
           commands.  Also, (W)rite User Info can store your preference for
           long or short headers.

While you are reading a message, type "LONG" and press ENTER and you'll see
what I am talking about.
                                         David W. Terry 

Date: 05-11-93 (11:29)              Number: 63058 of 63094 (Refer# 63038)
  To: DAVID TERRY
From: SCOTT ROBISON
Subj: brdm.mnu                 
Read: 05-11-93 (13:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The flexibiilty of v15.0 is enough to boggle the minds of many a sysop.
-> <grin>

Heck, forget the SysOp, it's enough to boggle the minds of the developers of
the software!  :)

   Scott Robison

Date: 05-11-93 (11:29)              Number: 63060 of 63094 (Refer# 62904)
  To: JAY CAPLAN
From: DAVID TERRY
Subj: Capabilities of PCB v15  
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is there any way that I can allow a certain security level caller (or
-> perhaps any caller) to start downloading ANY file on my system, even if they
-> don't have enough time left to based on PCB's download time calculations?

You could write a PPL program and attach it to your D or DB commands.  Then
have it adjust the callers time upward or something like that...

-> I do NOT want to make EVERY file NOTIME, for obvious reasons. I just want to
-> be able to allow callers to start a download, even if they would overrun
-> their time limit. I DO want the time spent downloading a file to be counted.
-> But if a caller has 5 minutes left for today, and they want to download a 10
-> minute file, I want to allow for that. Since ANY file on my BBS may be
-> downloaded under these circumstances, I cannot use NOTIME on every filename.

Hmmm...  these are strange requirements and a little hard to meet, but...

On the one hand, you DO want to enforce the time limit, on the other hand, you
do NOT want to enforce it.  Communicating that to PCBoard isn't going to be
easy (conflicting goals never are).

At this point I can recommend that you look into the idea from a PPL
perspective but I cannot spend the time required to look into actually
"writing" the PPL for you or even telling you what would be required.  (sorry,
I have my own hands full, but if it can be done at all, I can tell you that it
will probably require the use of a PPL program)

                                         David W. Terry 

Date: 05-11-93 (11:32)              Number: 63061 of 63094 (Refer# 62906)
  To: JAMES DEAL
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> If you are using the alias function and have it set so that the user can
-> change his/her alias and the user wishes to use 2 or 3 different aliases,
-> will not let them change back to the orginial unless a generation of the
-> index files is performed.

That is correct.  I mentioned this yesterday in the message base.  Here is the
text of the message (so that I don't have to write it over again).  :-)

-------------------------------------------------------------------------------
-> If a user changes his alias, he can't change it back to what it was before
-> until after I do a pack on the users file.

This is a result of the alias being held in the index files.

I've done nothing to "change" this behavior because I'd really prefer to
discourage continual changing on the alias name.  Making it easy to change back
and forth would encourage something like this:

        change name to JOHN DOE
        write a message
        change name to JANE DOE
        reply to JOHN DOE
        change name back to JOHN DOE
        reply to JANE DOE
        etc...

The one big thing I don't like about the very "idea" of aliases is that it
promotes a "lie" ... letting you pretend to be someone you are not.  If all you
do is use an alias for anonymity then I have less of a problem with aliases,
then they are serving a useful purpose, but if someone is continually changing
back and forth between 2 or more names then they are out to hide something.
-------------------------------------------------------------------------------

Hope this helps.
                                         David W. Terry 

Date: 05-11-93 (11:34)              Number: 63062 of 63094 (Refer# 63028)
  To: DAVID TERRY
From: MARIO POZZETTI
Subj: BETA report              
Read: 05-11-93 (13:17)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Please perform the following steps:

I will and let you know the results, hope you're right.

-> Properly exiting the system will cure this problem.

I will give it a try, I really have NOT paid attention as how the
process is done when the error occurs.

Thanks again
Mario

Date: 05-11-93 (11:35)              Number: 63063 of 63094 (Refer# 63045)
  To: DYNATECH COMMUNICATIONS
From: SCOTT ROBISON
Subj: RRRCMD.LST               
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> It seems the CMD translation feature does not work.  I used the new PPE
-> SEARCH,  this command works great before I went and did the sub menu setup.
-> After i did it I set up SEARCH,30,7,SEARCH.  I did not work,  I did a run
-> PPE file with the Search command in my MNU file and it did go into the
-> search menu but it sent the command with no spaces.  oh well if I set it up
-> with just the BRDM.  menu all works great.

OK, I'm not sure what you are asking here as there are several different
concepts intermixed.  Let's see if we can straighten them out.

1) CMD.LST  -> If you add a line, define the command as SEARCH, security of
               whatever, and drive\path\filename of the SEARCH.PPE file, does
               it work then?

2) MNU file -> You add a line SEARCH,30,7,SEARCH to a MNU file.  This should
               stuff SEARCH into the keyboard buffer and execute it.  What does
               happen?  What is the name of your MNU and where do you have it
               defined?  Also, are you using MKPCBMNU to create/edit your MNU
               files?

Let me know what/how you are doing things and we'll get them (or you) :) fixed
up ASAP.

   Scott Robison

Date: 05-11-93 (11:52)              Number: 63066 of 63094 (Refer# 62574)
  To: ROBERT BLACHER
From: LOUIS ZIRKEL
Subj: pcbpack 5-4-93           
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> (1) Nice display while it's packing.
        Thanks, I thought so too...

-> (2) The /PURGE parameter refused to pack out a comment to me that I had
-> read.  In other words, it wasn't treating a received comment as a
-> received+private msg and packing it out as it should have. It did pack out a
-> non-comment, received+private msg.  (If you read this paragraph six or seven
-> times, it's bound to be clearer -- I just don't know any other way to say
-> it!).
->
-> BTW, PCBPACK /AREA:00 /PURGE was the command I used to test this bug (my
-> normal command is more complicated -- it failed to get the comment, too).
-> And, there was nothing wrong with the flag on that comment -- 12/92 PCBPACK
-> /PURGE got rid of it.
        Hmm, I had this fixed once.  I'll have to double check and see if I
changed something that ended up breaking this option.

-> (3) PCBPACK isn't removing REFER # references to messages that have been
-> purged and no longer exist the way earlier PCBPACKs did.  If this feature
-> has been removed and I just missed the announcement of that, so be it.  But,
-> if you're supposed to be removing obsolete REFER # references, you're not.
        In looking through the old code, I can't find anything that leads me to
believe that it worked this way.  I'm not saying you're wrong, but I haven't
found anything to lead me to believe it worked this way.  I'll go back and see
what I can find concerning this.

-> (4) Finally, I saw several msgs from David in DEVELOP describing the /UPDATE
-> parm and how it worked.  But, if that command is documented anywhere, darned
-> if I can find it.  PCBPACK /H (which should be PCBPACK /? by the way)
-> doesn't describe it and I can't find it
-> in WHATSNEW.
        No, I don't think the help screen has been updated with that command.
I'll get fixed as well.  Thanks for all the useful information and helpful
reports.

        -= Louis Zirkel III =-

Date: 05-11-93 (11:52)              Number: 63067 of 63094 (Refer# 62575)
  To: MICHELE MAURO
From: LOUIS ZIRKEL
Subj: OTHER:  PCBZMODEM 04-14-93 13:32:00
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Thanks for the information.  I'll talk to Vic and see if I can come up
with any reason for this happening.

        -= Louis Zirkel III =-

Date: 05-11-93 (11:54)              Number: 63068 of 63094 (Refer# 62951)
  To: MARK LANGE
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I have a problem when I log on locally and when callers log on. I have the
-> GRAF-D.PPE set up here on the system and it worked fine with the last beta
-> version. Now when I log on, it says "Testing Your Systems Capabilities" and
-> then right under it it says "There is presntly no room for your text,..."

Well...  the message you saw (about no room for text) is one that PCBoard
issues when you have filled the MSGS.NDX file.  With that thought in mind, I
pulled up the GRAF-D source code and went looking for something that might
attempt to write a message.  This is what I found:

; /* If the default to the "Do you want graphics prompt is "Yes", then
;    inform the sysop via a message that the system is configured improperly.

IF (default_yes) THEN
   temp_dir = READLINE(PCBDAT(),179)
   FCREATE 1,temp_dir+"ANSI-D.$$$",O_RW,S_DW
   FPUTLN 1,"The PPE shown in the subject, could not run properly because you"
   FPUTLN 1,"have your system configured to Default to Yes for the 'Do you
   want"
   FPUTLN 1,"graphics prompt'.  You need to change that setting in to 'N' in"
   FPUTLN 1,"PCBSetup | Configuration Options | Configuration Switches."
   FPUTLN 1,""
   FCLOSE 1
   MESSAGE 0,"SYSOP",PPEPATH()+PPENAME()+".PPE","Your
   Configuration","R",DATE()+2,FALSE,FALSE,temp_dir+"ANSI-D.$$$"
   PRINTLN
   PRINT "Do you want graphics (Enter)=no"
   END
ENDIF

Sure enough...  GRAF-D.PPS is trying to send you a warning message about your
configuration.  PCBoard is then trying to warn you that there was no room to
create the new message.

A three-step solution then is recommended:

1) Run PCBSetup and increase the number of Message Blocks for the main board.
2) Run PCBPACK /AREA:0 /INDEX /OLDINDEX
3) And also go into PCBSetup and change your "Default to Graphics" setting
   back to 'N' and then GRAF-D won't try to write you a message.

                                         David W. Terry 

Date: 05-11-93 (12:01)              Number: 63070 of 63094 (Refer# 62956)
  To: TERRY RALEY
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The problem that i seen was.. user as entering a message and went off to do
-> something.. the keyboard timer was beeping. my inactivity timer is set at 2
-> mins.. everything went ok except that it did not recycle the modem, was
-> still off hook, it recycled pcboard and was sitting at the callwaiting
-> screen. it never displayed carrier lost before.
->
->     KEYBOARD Time Expired!! 2 min time has elapsed.
->     Message Left: Hobbies (81) Conference # 8527
->     Carrier Lost ...
->     Minutes Used: 34
-> 05-10-93 (11:46) (3) SHARON SODERMAN Off Abnormally

This is completely normal.  The new capability for capturing a keyboard timeout
is run through the old code that captured carrier loss.  This allows PCBoard to
capture the message that has thus far been written and save it for the user,
then log the user off.

This was rather brief in the WHATSNEW file but this is where it was mentioned:

 added   The message editor has long been able to capture a "lost carrier" and
         SAVE the message before logging the caller off.  Now it will also
         detect keyboard timeout and SAVE the message before logging off.

So it's working properly.
                                         David W. Terry 

Date: 05-11-93 (12:23)              Number: 63073 of 63094 (Refer# 63072)
  To: BRUCE HAEFEMEYER
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Is there any way to allow file attachments but to put security on it so only
-> I (the SYSOP) can use it, or am I allowed to use it even with the "Allow
-> attachments" in the conferece setup set to "N".  Seems like it opens up the
-> 'flood gates' without some kind of security on it.

You could write a PPL program and attach it to your Editor Command prompt.

                                         David W. Terry 

Date: 05-11-93 (12:34)              Number: 63074 of 63094 (Refer# 63020)
  To: LOUIS ZIRKEL
From: NICK HARTZ
Subj: 2 problems               
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+) HAS REPLIES

->       This should be fixed in the release from yesterday (May 10).
-> Give this
-> a try and let me know if it fixes things for you.

I tried it today with the new code dated 5/10/93 and here are the
results:

I did not get the error anymore about the USERNET.XXX unless of course I
had answered Y to running on a network and the file was not there.

However, I was still unable to get the event to run automatically
UNLESS USERNET.XXX at least existed. This was the same as it was before
today's upgrade.

So, the bottom line is that USERNET.XXX has to exist for the event. to
run automatically at least in my case.

Hope this helps!


                                        Nick

Date: 05-11-93 (12:31)              Number: 63075 of 63094 (Refer# 62985)
  To: IAN SINGER
From: DAVID TERRY
Subj: Beta                     
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> The docs say that you can force a read of mail for a security level and
-> thats unders files, configure, password.  Where and how please?

1) Run PCBSetup
2) Select File Locations
3) Select Configuration files
4) With your cursor on the PWRD file press the F2 function key
5) Now press F2 *again* to see the rest of the display

-> My event would not run under desqview and DR Dos 6 because of environment
-> full, but it doesnt write that to log file, so I had to increase it from 300
-> bytes to a 400 (guessed).  Works fine now.

Hmmm... sounds like we may need to provide a general recommendation for higher
environment space requirements.

For others reading this message.  That means edit CONFIG.SYS and where it says
SHELL= have it say something like this:

        SHELL=C:\COMMAND.COM /E:512 /P

Where the /E:### parameter defines the size of the environment.

It looks like 400 was good enough for your system, others can probably use
about the same.  A setting of 512 is probably sufficient for most.  The only
general recommendation we have is to NOT make it any higher than 1024.

                                         David W. Terry 

Date: 05-11-93 (12:54)              Number: 63077 of 63094 (Refer# 63074)
  To: NICK HARTZ
From: LOUIS ZIRKEL
Subj: 2 problems               
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        The thing that doesn't make sense because the editor is the only thing
that really touches the USERNET.XXX file (except where the status is written to
the USERNET file and that works everywhere else).  If you'll set PCB=/DEBUG:1
and upload your caller from when you do that I'd appreciate it.  That will show
me a LOT of information that'll help me track this down.

        -= Louis Zirkel III =-

Date: 05-11-93 (13:22)              Number: 63082 of 63094 (Refer# NONE)
  To: DAVID TERRY
From: ARTHUR MOL
Subj: BETA report              
Read: 05-11-93 (13:28)              Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-10-93 17:00:00                        


David,

I found out something more about the problem where PCBoard won't accept
any other prompy than "Y" anymore after returning from a door.
We have our system here by default set at the Dutch language so a Dutch
prompt and PCBTEXT are the 1st lines in the PCBML.DAT file.

Whenever I swap the entries for the Dutch and English pcbtext file (and
the prompts) in PCBML.DAT, the problem won't occure... Probably this
helps you a bit more in locating the cause of this bug..


Arthur

Date: 05-11-93 (13:22)              Number: 63083 of 63094 (Refer# 62680)
  To: DONALD MEHRTENS
From: LOUIS ZIRKEL
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

        Everything looks in order to me, but I'm trying to track down some
problems, so hopefully I'll have this fixed real soon.  Many people have
said that by placing a "dummy" event at the bottom of the list of events
that it will help.  You may wish to try this out...

-> One other thing I noticed.  I cannot use any time between 23:59 and 00:01
-> inclusive as an event start time.  PCBSetup won't let me tab out of the
-> field if I do.  Any reason for that?
        Yeah.  We don't want to cause any problems with crossing midnight, or
trying to run an event right at midnight.  That's the reason!

        -= Louis Zirkel III =-

Date: 05-11-93 (13:34)              Number: 63085 of 63094 (Refer# NONE)
  To: ALL
From: SCOTT ROBISON
Subj: PCBEdit Version 1.00 Wide Area Beta 11
Read: (N/A)                         Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

PCBEdit Version 1.00 Wide Area Beta 11 is now available for download from the
Salt Air BBS, BETA conference (6), file directory 2.  The filename is
PCBEDIT.ZIP.  A history of changes follows:

 * Fixed an error in a warning message ("Insufficient memory to save line being
      editing" to "Insufficient memory to save line being edited")

 * Fixed a problem in changing attributes for the rest of the screen when a
      color code is inserted or deleted

Remember, this is still beta code; if you have any problems or suggestions,
please leave me a message IN THE BETA CONFERENCE!  We really need the feedback
you provide, and I can't guarantee I'll get the message if it comes from in
anywhere else!  Be sure to provide the release number and/or file date and time
of PCBEDIT.EXE when reporting problems so I'll know if they have been fixed or
not.  Thank you.

   Scott Robison
   CDC Development Staff

Date: 05-11-93 (13:50)              Number: 63087 of 63094 (Refer# 63084)
  To: ART EMERY
From: DAVID TERRY
Subj: ALL-FILES LIST           
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I have created an ALFILES.IDX for all of the files on the BBS. Can't I point
-> all conferences to this one file instead of creating an IDX file for each
-> one. Just the CDROM IDX file is over 124k and as it is now it uses a lot of
-> RAM disk space with 5 different IDX files.

Sure, you can do that.  It's nothing different from in v14.5a though.  Just put
your ALLFILES.IDX file into your DLPATH.LST and then people can download from
any conference.
                                         David W. Terry 

Date: 05-11-93 (13:53)              Number: 63088 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: TOM MCNALLY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-10-93 17:02:00                        



PCBpack is still locking up on conferences with no messages.
It locked up last night in an EVENT (having to use an external
clock timer, since PCBoard will not run an event in the midnight
hour) and again today in a manual pack.  It came up with a
QEMM exception 13 error and I had to re-boot the network.
Upon searching for the conference it died in, I found it
to be one with no messages.

Thought you might like to know ...

... tom

Date: 05-11-93 (13:59)              Number: 63090 of 63094 (Refer# NONE)
  To: TOM MCNALLY
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

Ŀ
 PCBOARD.EXE - 05-10-93 17:02:00                        


PCBpack is still locking up on conferences with no messages.

By the way, when you submit a report for PCBPACK you need to give the date/time
on PCBPACK.EXE *not* PCBOARD.EXE.

Otherwise we are left guessing what the PCBPACK.EXE date is.

                                         David W. Terry 

Date: 05-11-93 (14:00)              Number: 63091 of 63094 (Refer# 63017)
  To: LOUIS ZIRKEL
From: WILLIAM P. STEWART
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

->       The PACKOUT date is basically a date that you can set on a
-> message by
-> typing a D at the security prompt and entering a date.  This tells
-> PCBPack NOT to pack that message out UNTIL that date.

I never knew this. I just tried it, BTW, and it did not work. Also, what
the "carbon copy" feature, or what I mean is how does it work? I just
got one from Scott and it had little "cc:" at the bottom. How do you do
that one?

Also, how would there be a packout date if I never set one? I didn't
even know the feature existed.

See ya!

William P. Stewart
Computers & Dreams BBS

Date: 05-11-93 (14:03)              Number: 63092 of 63094 (Refer# NONE)
  To: LOUIS ZIRKEL
From: WILLIAM P. STEWART
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)


Ŀ
 PCBPACK.EXE - 05-10-93 17:02:00                        


OK. I haven't seen this one in a loooong time:

"Unallocated Ptr 0x726F4220 at d:\tc\dos\dosfclos.c(24)
Press any key to continue..."

See ya!

William P. Stewart
Computers & Dreams BBS

Date: 05-11-93 (14:09)              Number: 63096 of 63097 (Refer# 63093)
  To: DANIEL COULOMBE
From: DAVID TERRY
Subj: BETA report              
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> I know, I should use PCBPACK /AREA:ALL /INDEX /OLDINDEX

In ADDITION to doing that, you also need to tell PCBoard to MAINTAIN the old
indexes and you also must tell PCBPACK (in your event) that it should MAINTAIN
the old indexes.

Example for board.bat:      SET PCB=/OLDINDEX     (plus any other settings)

Example for your event:     PCBPACK /AREA:ALL /DAYS:30 /OLDINDEX

If *all* of the pieces of the puzzle are properly configured you will not have
any problems.
                                         David W. Terry 

Date: 05-11-93 (14:10)              Number: 63097 of 63097 (Refer# 63094)
  To: WILLIAM P. STEWART
From: DAVID TERRY
Subj: New pcboard code         
Read: NO                            Status: PUBLIC MESSAGE
Conf: BETA (6)                   Read Type: GENERAL (+)

-> Sorry to be a pain but I couldn't help but notice that your code is dated
-> 5/11/93 12:43 yet there is no new code in the beta door.
->
-> I realize you simply might not have released it but since in the past there
-> were times when you super-busy guys just forgot, I thought I'd mention it.

Thanks, but...   we always "pre-test" the code here.  We may go through several
revisions during the day (or before the next beta posting) in order to ensure
that when we DO post the code the changes that have been made will be stable.

I'd much rather catch a bug here on Salt Air than give it to you guys and
suffer the onslaught of messages reporting it!  <grinning broadly>

                                         David W. Terry 

