Category : Communication (modem) tools and utilities
Archive   : ANS36E.ZIP
Filename : BETABUGS.LST

 
Output of file : BETABUGS.LST contained in archive : ANS36E.ZIP
The following is a discussion of the bugs found and repaired in v36a.

[Scott Woynarski] Bugs that I have found with ANSWER V3.6a

ANSWERING MACHINE
-----------------
1. In first time access
- For directory outgoing, I cursored to the end of the default that
was there and added "\REC" to the path. Then I changed my mind and
back spaced over it. I was returned to the P,I,O,T,B menu. I chose
outgoing again. The path was the default "D:\MODEM", but it also had
three spaces on the end and a "\", so it looked lik "D:\MODEM\ \".

* Added a check to ensure the edited entry is a valid DOS directory name.

2. When I use the cursor keys to move the menu bar, it appears that some other
messages are being printed underneath first, then the proper one on top.

* Disabled HELP for Main Menu command when a Pull Down window is active.

3. Voice "AT" commands often extend past the brown box in the middle of the
screen and overwrite the shareware notice.

* Limited the length of messages displayed in the box to 32 characters.

4. I went into Incomming Call Log, and it showed me a call in the upper left
hand corner (there was only one call made). I pressed ESC to get out of
there and then pressed ENTER to go back in again. I got a "memory alloc
error!". I the pressed ESC to get out again and it re-booted my machine.
(I hate when pointers go wild!)

* This only occured if the log file was less than 25 lines long. Added
* extra checks to ignore page-down and down keys if less than 25 lines.
* My system didn't lock up either way, so I'm not sure this fixed the
* problem, but there was a problem and I fixed it.

5. Calls are displayed on the screen blanker, but I do believe that these are
total calls made to the system. I think it would be much more usefull if
it would display only those calls since you last played the incomming calls.

* This is intended to be the number of incoming messages in the incoming
* directory. I could change it to say "Messages:".

6. One of the 1st times I ran the anwsering machine, I did not have an active
message. The system, when it answered a call, just beeped and the caller
doesn't know what is going on. This was my own mistake, but I thought it
might be a good idea that upon activation of answering machine, it would
check to make sure that at lease 1 OGM message has active status.

* Changed the OGM record function to automatically activate the OGM
* directly after it is recorded IF there are no other active OGMs.

7. The editing of message hours seems to be very cumbersome. You have to
cursor through the days of week twice to get to hours. This is a very
good idea though. It's nice to be able to have different messages at
different times.

* I changed the logic there a bit. It's better but still cumbersome.
* I'll see if I can come up with a better editing scheme.


INFO SERVER
-----------
1. The treetest.cfg is the one that I un-zipped, and it seems to look fine to
me. When I activate the info server, the display
prints "File I/O Error
tree.cfg
Press A Key"
Then you are stuck in this mode, whereby you have to keep pressing a key
and are never let out, even if you press ESC. You have to re-boot.

* Added a check for error code returning from reading the tree.cfg file.
* The call session will be terminated if the file was not found.

I then renamed treetest.cfg to tree.cfg, but am having some problems.
It seems when I edit the tree.cfg menu, I choose edit branch and then a
name. The new branch menu shows up, but when I press ESC to go back, the
main menu is all INVALID.BIN again. Am I doing something wrong, or has
the menu name change caused this?

* It's not something you're doing wrong - the internal tree editor has
* problems. I will try to fix it, but for now, it's better to edit the
* text file yourself.

2. I found that when playing around inside the edit menu function, I often
got garbage on the screen and had to re-boot. I'll try to find out what
sequence of events is causing this & let you know.

* See the previous comment.

======== Other changes ========

After recording or playing a message, the system clock is advanced by the
time length of the file times 4. This has been corrected.

Repaired the NUMS.BIN, DAYS.BIN, and MONTHS.BIN files.

04/06/92

Added "Copy msgs to temp dir before playing" option. This is useful when
you have a ram disk which can be used as a temporary disk from which to play
messages. This will reduce the "gaps" heard in messages when they are played.

03/10/92

Due to the hardware configuration, you will be unable to use a phone which
is plugged into the back of the CompuCom modem. Instead, you will have to
have two wires which come from the wall - one going to the modem, and the
other to the phone.

07/22/91

DELETE YOUR OPTIONS.DAT FILE!

I will be periodically adding additional configuration options and when
I do, your OPTIONS.DAT file will change. You will have to delete it and
reconfigure the program each time I do that. I will try to keep the number
of times I do this to a minimum and I have allowed some spare room for
expansion in between times when I have to add more room.

I have added the function which dials a number during message playback
and record. If the phone is previously offhook, ANSWER.EXE will dial
a single digit and then ask the operator to pick up the phone. It will
then continue to play or record and dial another digit after 15 seconds.

On the other hand, If you supply a phone number under "CONTROL/DIAL OPTIONS",
then it will dial that phone number each time it goes to record or play
a message and will not dial digits during playing or recording.

If the phone is previously offhook before going into play or record mode,
ANSWER.EXE will dial no numbers at all.



  3 Responses to “Category : Communication (modem) tools and utilities
Archive   : ANS36E.ZIP
Filename : BETABUGS.LST

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/