home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Pier Shareware 6
/
The_Pier_Shareware_Number_6_(The_Pier_Exchange)_(1995).iso
/
004
/
mmaker48.zip
/
MMAKER.HIS
< prev
next >
Wrap
Text File
|
1994-12-12
|
64KB
|
1,120 lines
12/12/94
[v4.8] When deleting a message the program returned an Error 52. Our
testing shows that the message being deleted was actually
deleted, and that the error occured when the program attempted
to read other messages that were present.
In the MMAINT program, when deleting all users associated with a
particular BBS (option 13), you will have to enter the BBS
name EXACTLY as it appears in the database. Prior versions
converted the BBS name to all uppercase thus causing ALL
matches on that BBS to be deleted.
Dramatically increased the USERS re-indexing speed in MMAINT
Dramatically increased the MESSAGE re-indexing speed in MMAINT
Dramatically increased the USERS re-indexing speed in MMEXCH
Improved the USERS import speed in MMEXCH
A NEW command line option has been added to MMEXCH. In addtion
to the ALL or NEW we have added ALLMINE. When used this option
will EXPORT ALL profiles/pictures and messages that were
generated on the current BBS. This should be useful to everyone
as it will allow the HUB to bring his/her database up to date
by (1) deleting all records for the individual BBS and
(2) requesting individual BBS' to send only their profiles.
MMAINT AUDIT function was not recording the Number of messages
There was a report that when exchanging files, and the alias
AND logon name were the same on 2 or more BBS' the incoming
user profile would overlay the wrong profile... I believe this
has been fixed.
The MMAKER message option was SUPPOSED to let the caller know
if there were duplicates of the Alias in the database, in which
case the caller would be able to make a choice based on BBS
name and location. Should now work as it was designed to...
If there were duplicate Alias' in the database (but from
different BBS'), MMAKER was showing any messages addressed to
that Alias, to both callers with the same Alias.
Prior versions bypassed any database records that matched the
caller's Alias when doing a MATCH. The program will now only
bypasss your Alias and not a like Alias from another BBS.
When a user record was being deleted (either an individual
deletion or one based on the BBS being deleted) the program
was NOT deleting any attached PICTURE files.
'Message Waiting' message was being displayed twice; once when
you first logged on (when Door welcomed you back) and then again
on the Main Menu. It will now only be displayed on the Main Menu.
The program was not clearing out the 3-line self description a
new user fills out. If the caller only used 2 of the 3 lines,
the 3rd line contained another callers database information. The
3 lines will be cleared before asking for information.
Added a new Match Criteria. You will now have the choice of
limiting your match to callers from the BBS you are accessing
or from All BBS'
Added a new feature for those that wish to present the
questionaires in differnt languages. If you wish the caller to
choose a language other than English, then you must create a
file called MMQLANG.DAT (see DOCS). If you will only have the
questionaires in English, then there is no need to create this
file. If the file is present the program will display it and ask
the caller to choose a language. Please note that this only
applies to the questionaires at the present time. See DOCS for
more information.
For HUBS that wish to reject certain BBSnames from being imported
when doing a Match Maker exchange, we have added a new file to be
used to record the BBS' name. This file will only be read by
MMEXCH and you must be a HUB. See DOCs for more information.
When purging users (MMAINT option # 4), the delete flag was not
being set for those being deleted. Without the flag being set,
the program would not know which ones were to be deleted.
In MMAINT, option 13, the program was only deleting users IF the
BBS names were ALL Uppercase.
MMEXCH will no longer Export OR Import any records where the
caller has not answered the questionaire or has taken the
questionaire defaults.
Under certain circumstances, when using MMEXCH, a duplicate entry
was being allowed into the user database.
You can now FORCE the use of the caller's BBS logon Alias in the
Door. See the DOC file (CFG file explanation... Door.SYS
sub-option)
Removed the restriction that would not allow unregistered
versions of the Door to access the MMAINT user re-index option.
If you tried to run the MMAINT Audit option and there were no
records in the database, the program would hang.
Added a new option ot the MMAINT program that will VALIDATE
the MatchMaker PICTURE files existance. When picture files can
not be verified, pertinent information will be written to a
report file called MMVERIFY.RPT. The Sysop will then be able to
take whatever action he/she desires.
MMAINT Duplicate check option, now MUCH faster!!!
Processing time decreased for some of the options in MMAINT
If you limited the number of times a caller could enter the
door on any given day (game limit entry in the CFG file), the
program, under certain circumstances, would only allow 1 less
entry than the number you defined in the CFG file.
When doing a match, option 4, the program displays the number
of records being searched as well as the total number of records
in the file. Somewhere along the way the number of records in
the file was not being picked up correctly and the program was
displaying a zero (ie: 55 of 0).
When using Option 4 (Make-A-Match) MMAKER will now *remember*
the LAST match criteria used during the LAST use of MMAKER. All
the caller will have to do is press enter to any of the
questions to use the LAST entry they made for that question.
**NOTE** YOU MUST RUN MMAINT (option 17) ONCE!!!
One of the match crtieria (in option #4, MMAKER) combined STATE
and COUNTRY as one. In this version STATE and COUNTRY will become
SEPARATE match criteria.
The default "Minimum Age", used when making a match (MMAKER
option #4), has been changed to 18.
Added a new option to the CFG file. This option, if set to Y,
will force validation of STATE abreviations.
MMAINT was not creating all the questionaire files when you
tried to use a language other than English.
11/08 The Welcome file, MMWELCOM is now multi-language capable. If you
are currently using a WELCOME file, you MUST rename it to
MMWELCOM.E... and read the DOCs for information on how to adapt
the MMWELCOM file to multiple languages.
The text file you can insert into a downloaded questionaire
file, MMDLTEXT, is now multi-language capable. If you
are currently using a text file, you MUST rename it to
MMDLTEXT.E... and read the DOCs for information on how to adapt
the MMDLTEXT file to multiple languages.
If you have set the CFG option that forces the use of the
Logonname or alias used on the BBS, the user will no longer
be required to respond Y or N to the "Is this correct.."
message.
All messages read by the caller will be marked as READ, along
with date read.
If you attempted to change the LogonName of an existing
caller's record, MMAINT would not allow it if the new name
duplicated an entry in the database. This would have been
correct if the new LogonName had been for the same BBS but it
was being rejected for ANY duplication regardless if from
another BBS.
If using the TRIBBS.SYS system file, the door always presented
the opening screen in black and white. Will now be presented
in color.
The Door knows that the caller is the Sysop, if the caller is
record #1 in the BBS' user database. The BBS software passes
that record number to the door via the system file. Some BBS
software does not pass the actual record number but passes a
relative number (ie: record #1 is passed as record #0). If the
number being passsed is 0, the Door will not know it is the
Sysop calling. We will now recognize the caller as the Sysop
if their record number is 0 or 1.
When caller responded to a message sent by another caller, the
response was never sent.
When importing and indexing LARGE numbers of messages the MMEXCH
program produced an OUT OF STRING SPACE error.
After reading a message addressed to you, and you do not wish to
delete it, MMAKER was not letting you know that you had messages
waiting (the ones you did not delete) on your subsequent calls.
Hopefully this version will fix this.. if not please let me know!
The MMexch log was not recording the PICTURE filenames being
exported. With this change all exported Picture files will be
recorded.
08/19/94
[v4.7] There have been a number of problems reported that some of your
users were not able to log into the Door. I have been able to
track the problem(s) back to a change we put into the program
to force the deletion of a record if it was deleted on one of
the BBS' in a network. What we found was that many of the user
records were being FLAGGED as deleted, erroneously. You did not
lose any records, they were just flagged as being deleted. If
you use the UNDELETE option on the MMAINT menu you will be able
to recover ALL of the 'deleted' records.
We will have to figure out a better way of ensuring that a user
deleted on one BBS, will be deleted on all other BBS' in the
network.
In addition, based on your feedback, we have also removed the
restriction that only the Sysop of the originating BBS would be
able to Delete or modify a user record.
****************************
MMAKER: Under certain circumstances, if a caller uses an Alias
that duplicates another Alias in the database, but is
not from the same BBS, the questions presented to the
new user appear to already have been answered. The
'problem' should now be fixed..
When a caller requested to review a particular user's
profile AND there was more than one user with that
particular Alias, MatchMaker would only show the caller
the first match it found in the database. The caller
will now be shown all those that match, one after
another. The caller may terminate the display of those
they do not wish to look at by replying "E" at the
Personal Info screen.
The heading, when displaying a caller's personal
information screen, showed as 'Change Personal
Information'. This should have displayed as 'Personal
Information' and I promised to change it a while ago.
Well, for my fellow perfectionists, it has finally
been accomplished.
The CFG entry that allows you to pull the caller's alias
from the DOOR.SYS, now has another sub-option. This
sub-option FORCES the use of the caller's logon name to
be used as the Alias.
MMAINT: Added an option to enable the Sysop to delete ALL users
from a particular BBS
Added an option to UNDELETE an individual database
entry or ALL Database entries
Added an AUDIT option to be used to determine the number
of users/messages by BBS, in the MMAKER databases
Added an option to allow the SYsop to change a users
logon name.
In order to add in more features we have had to make
room in the program by removing the BLACKOUT TIME
feature. You will have to remove the (5) lines of
XXXX/YYYY's from the CFG file.
When using option 4 to Make-A-Match, the program will
automatically keep track of the matches you have made
(up to 100). When you subsequently go to option 5 to
see the profiles of those you matched to, you will be
given a choice of entering an individual user's name to
view OR the program will show you the profiles of ALL
the matches you made. This will eliminate, to some
extent, the necessity to write down the names of those
you matched on to use in option 5.
05/06/94
[v4.6] MMAKER: Callers were unable to enter the Door. They were being
told that they already had an Alias. This was caused by
a corrupted MMAKER.EXE file.
Error 52 being generated. This was caused by a corrupted
MMAKER.TXT file.
We have recompiled MMAINT.EXE, MMAKER.EXE and MMEXCH.EXE
to make sure we catch any other strange problems BEFORE
they occur.
*** For some strange reason we experienced several
problems relating to corrupted files with the MMAKER
archive. At this time I have no idea why, but I
believe everyhting should be fine with this release.
My apologies to those that have been victimized by
these problems. The prior release can almost be
defined as the "Release from H*ll"
05/05/94
[v4.5] MMAKER: When doing a match, the bottom of the screen shows the
caller the record numbers being processed. At times
the record being processed was not the true number
(usually less than the actual number).
When doing a match the option to match on NEW callers
since last logon, was not working properly. I believe
we have this fixed (where have you heard that before?)
The documentation, on page 7, makes mention of a sample
file called MMDLTEXT being included in the archive.
Unfortunately it was not included in the last archive
and I am not sure how many of the recent Match Maker
archives this was missing from. The file in question is
used to give the caller instructions as to how to
respond to the questionaires offline and then upload
them. This text file is then affixed to the beginning of
then download questionare file(s). I would URGE you to
edit the file and then go into the Match Maker
Maintenance file and run option 7 to recreate the
questionare download files.
When trying to send a message to a person whose name
started with a numeric character, the program would
indicate that that person did not exist in the
database, when in fact it did.
04/20/94
[v4.4] MMAKER: If PROTOCOL.DAT is not found an error 52 was reported.
This is an erroneous error as it should have reported
Error 53. This has been corrected so that if that file
is missing it will not attempt to load the Protocols.
The display line for COUNTRY had a '/' instead of a ':'
The display line for Orientation did not show a ':'
When answering the questions user is reminded whether
they are responding to the SELF-DESCRIPTION questions
or the DESIRED MATCH questions by flashing DESIRED
MATCH and/or SELF DESCRIPTION. This has now been
changed to flash ONLY if you are using the dual
questionaire option.
If 1st character of ALIAS not an Alpha character and
there is more than one non-Alpha character Alias in the
database, the Door was not handling the Index correctly
and would return an error message indicating that the
caller already had an Alias when they attempted to
log into the door.
When answering the DESIRED MATCH questions, the user
will now have another option, + = "I DO NOT CARE",
which in essence says to flag all the answers so that
he/she will match whatever answer the program
encounters for others in the database.
When making a match, the caller will be asked another
criteria question: Whether they want to include the
entire database or only those in the database that have
been entered or changed since the caller's last logon.
When entering personal information for a new caller,
there was no indication on the screen as to how to quit
and start over. The command is "Q" and it will now show
on the CITY/STATE line of the personal info screen.
When using option #6 (Userlist) the caller will now be
asked if they wish to view the entire User List or just
those that have been added since the caller's last call.
Added another Match Criteria option. This option will
ask for a MUST MATCH question number. If the users in
the database do NOT match the caller on this question
then they will be bypassed even if other questions are
a match. If the caller enters 0 for this option then
the MUST MATCH option will be ignored. Will only accept
ONE question number!
The verbage for option 5 was incomplete, it was missing
the second line.
When reviewing someone's responses to the questionaire,
the heading read "SELF DESCRIPTION". It will now read
"User's Responses".
When doing a match the program was NOT bypassing DELETED
records. It will now!
If you placed a 0 in the CFG for number of times the Door
could be played per day, it would default to 1 per day.
This has now been changed to default to 99 games per day.
You can override the default value by placing the correct
number of games allowed in the CFG.
When displaying other participant's responses, their
names will be displayed at the top of the screen rather
than 'user's responses'.
MMAKER.TXT has been updated. Be sure to replace!
MMAINT: When doing a re-index, the record number being acted
on, if greater than 99, was overlaying the 'of' on the
screen display. This cosmetic 'problem' has been fixed.
Reindexing of the user's database was not working
correctly under certain circumstances.
It seems like we have allowed any Sysop to EDIT or DELETE
profiles of those who were not members of current BBS.
This only affects participants in an Exchange Network.
Options that require registration will now state so
instead of just returning to the menu
Added the ability to change a caller's ALIAS. You will
only be able to change the ALIAS for a user that
originated from YOUR BBS...
When the Sysop wanted to force a SINGLE user to reanswer
the questionaire he/she would choose the appropriate
sub-option from the Main Menu Option #6. Unfortunately
MMAINT would just return the Sysop to the Main Menu, not
doing anything. The SYsop did not realize that nothing
was done and assumed the request was honored.
When deleting a user record associated with your BBS,
MMAINT was marking it as deleted, but the re-indexing
routine was not recognizing that it was deleted, thereby
including it in the User Index. When a person logged on
to MMAKER and used the deleted alias they were told that
someone already had that alias and the person was denied
access. You should re-index the User Base.
Added another option that would allow the Sysop to
UNDELETE a previously deleted user record. This option
will only work on those users that originated on the
current BBS.
When doing the User Purge, the program was not
displaying the record number it was working on when it
was recreating the User Master file. The Sysop could
mistakenly think the computer was hung as it does take a
few seconds to do the recreation and the Hard Drive red
light would remain on and solid.
After deleting a User, the purge User option was not
deleting the deleted record.
I have had some feedback about the inability to EDIT a
caller's record, if they did NOT originate from the
current BBS. For the most part there has been general
acceptance of this concept. However, yes there is always
a however, I have been asked to allow any Sysop to modify
the PICTURE FILENAME portion of the record. I see no
problem with this other than it would normally cause the
record to be re-exported. In this case I will not allow
it to be re-exported since in theory the Picture Name is
being changed for local use only. I welcome feedback on
this, but do not want to overly complicate such a
simple change.
MMEXCH: If you are participating in an Exchange network then
whenever you delete a user from your Database it will be
deleted from all other participating databases.
When importing User's database, and a corrupted record is
encountered the program would create an 'Bad File Name'
error. We have added a bypass for the error (error # 52).
Added some more 'record processing ' information to the
screen display during import/export.
Reports of User Profiles/Pictures/Messages recycling
between HUB/Node/HUB even though there were no changes
made that would have caused it to export.
Additional changes to fix the recycling of files/messages
Reports of not being able to login to the Match Maker
Door, even though one had been on before. This would
occur after doing an IMPORT from another system in a
network. A way around the problem was to use the MMAINT
program to re-Index the User database.
Made some changes to the MMEXCH.LOG and the screen
display to HOPEFULLY clarify the actions being performed.
When Exporting a user record AND the Picture filename in
the user's record indicates that there is a Picture file
present AND the filename can not be located in the
Exporting systems' file area, the user's record will be
blanked out as will the exported record.
When doing an IMPORT for the first time, the USER base
imported fine but the MESSAGE base import would cause a
BAD RECORD error. The problem occured in the re-indexing
routine and thus also caused PICTURE files not to import
Every time we do an import we will force a re-index of
the User file.
12/25/93
[v4.3] MMAINT: If you attempted to put in Drive:\Path info into the
Picture name field of the user's record you would
generate a "Bad FileName error". All Drive:\Path\ info
MUST be placed in the CFG file ONLY. We will now trap
the error and give an "English" error message (ie: one
that you will understand <g>)
MMAINT: Under certain circumstances, using option 11 to strip
the Drive:\path info from a user's record, was not
stripping correctly. The result would be an incomplete
filename being inserted in the user's record
MMEXCH: The 2nd Message base re-indexing, used to ensure that
the Logonname of the Message To recipient is correct,
was not functioning correctly.. fixed!
MMEXCH: The 2nd Message Base re-indexing was pathetically slow.
It is now much faster.
MMAKER: MMAKER is designed to handle the use of duplicate Alias',
when you are involved in a network, provided they are
used on differnent BBS' (different BBS names). Under
certain cricumstances, when their was a duplicate Alias',
MMAKER would deny one of those Alias' access even though
they were logging on the correct BBS. This is a little
tricky to word properly, but suffice to say I believe we
have fixed the problem.
MMAINT: Added a check to ensure that the Drive:\Pathname to the
PICTURE files did not contain any blanks and a \ was the
last entry on the line (in the CFG).
MMAKER: Added a check to ensure that the Drive:\Pathname to the
PICTURE files did not contain any blanks and a \ was the
last entry on the line (in the CFG).
MMAKER: Under certain circumstances a new caller, choosing NOT to
answer questions but rather taking the defaults, will
choose option 2 to answer the questionaire online and
when each question is displayed they see answers from
another user. In most cases the answers would be those of
another user with the same Alias (imported from another
BBS). This has now been corrected.
MMAKER: Updated MMAKER.TXT
12/16/93
[v4.2] MMAINT: When re-indexing the Message base, the Logon Name of the
person sending the message was being inserted in the
Message index file instead of the Logon name of the
recipient. When the record was originally created in
MMAKER it was done correctly. This problem has no effect
on Match Maker, but does affect the MMBULL (Match Maker
Bulletin Generator) program in that the bulletin would
show that a caller had mail waiting when infact they did
not. With this change MMAINT will geenerate the Index
file correctly.
MMEXCH: The "can't open MMTEMP" error message reared it's ugly
head again. We thought we had it fixed in the prior
version, but as luck would have it, we only fixed part
of the problem. We believe we have it totally
erradicated this time. This will also fix other reports
of not being able to export/import the PXP picture files.
MMEXCH: The maximum length of the Match Maker Exchange filename
(line 29 in CFG line) is 6 characters. The MMAKER
program was checking for it, but the MMEXCH program was
not. If someone used a name longer than 6 characters the
program would error out with a 'bad filename' message.
MMAINT: Program was not allowing Sysop to edit field 13
(Originating BBS Name) in the User record.
MMAINT: If you selected option 1, chose / to review all records,
editied a record, chose "continue search..." you would
be returned to the menu without continuing the search.
MMEXCH: Added a routine to fix the Message Index to plug in the
correct LogonName of the TO portion of the message.
This only affected the MMBULL program.
MMAKER: As many of you found out, we only allowed 28 characters
for the Picture file name. With version, the file name
will be limited to a maximum of 12 characters AND
Drive:\Path information, for ALL Picture files, will be
placed in the MMAKER.CFG file. You must update your CFG
file AND then run option 11 in MMAINT.
MMEXCH: By moving the Picture File Drive:\Path info to the CFG
file, ALL exported Picture file names will NOT contain
any pathing info.
MMEXCH: Corrected problem whereby the Message Index was being
corrupted when importing messages. This gave the effect
that the message base was 'wiped out'. The messages were
not lost, rather the Message index was corrupted. To
correct the problem you would have had to re-index the
Message base via the MMAINT program; that action is
no longer required!
MMAINT: When re-indexing Messages, the program undeleted any
previously deleted messages
MMEXCH: To give the Sysop more control over the
archiving/unarchiving of the Picture files, we have now
externalized this function. By externalizing we mean
that you can create your own batch files any way you
want, using the archiver of your choice. We will pass 2
parameters to each batch file as follows(we will use
PKZIP and PKUNZIP as the examples):
PKZIP %1 %2
where %1 = ZIP file name and %2 = Files to be ZIPPED
PKUNZIP %1 %2
where %1 = ZIP file to be unzipped and %2 = pathname
from MMAKER.CFG into which you will UNZIP Pictures
The name of the Batch files must be placed in a file
called COMPRESS.DAT. There must be only 2 entries in
this file, the first is the name of the ARCHIVER batch
and the second the name of the UnARCHIVER.
A sample COMPRESS.DAT is included, using PKZIP/PKUNZIP
and the sample Batch files (ZIP.BAT and UNZIP.bat), can
be found in the MMBATCH.ZIP file in the MMAKER directory
12/01/93
[v4.1] If you indicated, in the CFG file, that you wanted to use the
Alias from the Door.SYS AND the Alias field of the DOOR.SYS
was blank or null the program would loop at the 'enter alias'
prompt. The program will now check the ALIAS field and if it
is invalid the program will require you to input the Alias.
When editing a users record, in MMAINT, and you choose to edit
the CITY, the prompt indicated STATE and COUNTRY. The prompt
has been changed. The correct field was being updated
regardless of what the prompt said.
The MM40EXP program that expands existing databases, did NOT
expand the Message database. You can tell if the message
database was expanded or not, by trying to read a message that
was created by a version of MMAKER prior to 4.0. You should see
garbage in the message header. This has now been corrected. IF
you want to expand just the message database, then run MM40EXP
as follows: MM40EXP MMAKER.CFG /MSG
NOTE NOTE!!!! If messages have already been entered in the new
version, this MUST NOT BE USED!!! Either restore
the original MMSG.DAT and MMSG.INX then run this
or delete the same files and let the users start
with a fresh Message Database. IF YOU HAVE NOT
ENCOUNTERED A PROBLEM WITH THE MESSAGE DATABASE
after doing the original MM40EXP, then this does
NOT APPLY
When exporting pictures with the MMEXCH program, the program
returned a "can't open MTEMP" error message.
If someone logged on to MMAKER, reviewed a user's record that
had not answered all the questions, the program would return
the caller to the main menu. However, 2 of the options on the
main menu would be disabled.
11/19/93
[v4.0] ****NOTE to PRIOR REGISTERED USERS****: This version of Match
Maker requires that you obtain a new registration number for
both the Match Maker and Match Maker Exchange programs. SEE
UPGRADE.TXT for more information!!!. The Door will revert to an
unregistered version, until a registration number is obtained.
*************************************************************
Due to a change in the user database you will be required to run
a conversion program... MM40EXP.EXE. Just run the program and
it will do the conversion. This program is to be run only ONCE!
The MMAINT (Match Maker maintenance) program will now allow
you to edit a number of fields in the User's record.
MMEXCH (Match Maker Exchange), when indexing the Message
Database, was marking ALL messages as being NOT deleted even
though some were previously marked as being Deleted.
MMEXCH (Match Maker Exchange) was allowing duplicate users
records to be imported. I believe we have that fixed.
If you do not allow Downloads then the caller will NOT be able
to take the default answers and must answer questions online.
Caller can use High ASCII characters as input when filling out
the 3-line free-form description about themselves (under
Personal Information). This is controlled by a CFG option,
since not every Sysop will want to allow this. I would
imagine our friends in countries outside the U.S. would use
this capability since their language makes use of the ASCII
numbers greater than 127.
On the Match Criteria screen we have now added defaults for
each questions asked. If caller wants the default, they just
have to hit the ENTER key. We also changed some of the colors
on that screen as well.
We removed all references to Birth Date since it was only used
in conjuction with the Birth sign, which was also removed.
We had to make some room in the program for other features and
chose to remove the all references to the Caller's Birth Sign.
We chose this to remove as it would be very easy for you to
add it to your questionaire as an additional question.
Added another criteria match option: State/Country. You can now
narrow your matches to a particular State or Country.
NEW FEATURE: You now have the option to present the caller
with 2 questionaires. The first questionaire would be used as
a self description questionaire. The questions would be
designed so that the answers described the caller. The second
questionaire would be designed for the caller to answer to
describe what they are looking for in a match. When doing the
match the program will match the caller's DESIRED responses
against everyones elses SELF responses.
Of course you do not have to use this new feature and stay with
the single questionaire that is used as both a self description
and desired match. You control this thru a NEW option in the
Configuration file.
Added a configuration file (CFG) option that will allow the
Sysop to permit new callers to take the Default answers to
the questionaire or force them to answer the questions.
NEW FEATURE: Allow the caller to download a PICTURE file.
In most cases this would be a picture of the person in the
Database. If a caller would like to have a picture available
for anyone to look at, they would first notify the Sysop.
He/She would have the caller upload the picture. If the Sysop
wishes to make the picture available for others to download,
they would run the MMAINT program and EDIT that caller's
record to reflect the name of picture file.
When starting the MMAINT program, you no longer will use the
/ in front of the CFG filename.
In prior versions of Match Maker the caller's BBS LOGON Name
AND Alias were being checked against the TRASHCAN file. There
was never any intention of checking the LogonName, so that
check has been REMOVED.
In MMAINT, when doing a Message purge, the program was not
able to cope with a record that may have a garbled date.
Made some color changes to MMAINT to make it easier to read
when doing the purges.
Updated DOC file to reflect the optional 2 questionaire
concept for each sex.
Added NEW entry to the MMAKER.CFG to control access to the
Picture Viewing option. A zero(0) entry means everyone can
view the pictures. Any other value will be used to match
against the caller's BBS security level. If the BBS security
level is equal to or greater than the CFG value the caller
will be shown the Picture.
Added a new entry to the CFG file to allow the Sysop to make
the viewing/downloading of a PICTURE, security level specific.
If a file named PICTURE.TXT is found in the MMAKER directory,
it will be displayed to the caller just prior to them being
given the option to download/view the picture for the caller
being reviewed. Sysop can can have ANY verbage displayed in
ASCII file.
Made a change to the meaning of line 9 of the CFG file. In
prior versions, this line referenced whether or not you wanted
to allow ALL callers to use the Message Base or not. In this
version we have changed it to allow the Sysop to define a
MINUMUM security level that can access the Message base. If
you wish everyone to have access you would use a zero (0).
Added an option to the CFG file to control the Import/Export of
the Picture files when particiapting in a Match Maker network.
Fixed display problem in MMAINT when using option 10.
Match Maker Exchange re-written to speed up processing.
In the sample CFG and the Docs, changed the values,
in line 9, from 1 to 0
Changed the extension of the Message file created during the
exchange process from .MXP to .MEX. The change was required
so as not to conflict with the same extension being used in
the Classified Exchange program.
Expanded the size of the Alias field from 10 to 25 characters
State/Country has now been split into 2 different fields in
the database. The State entry will be a maximum of 2
characters, since it refers to the United States. The country
will be 3 characters. This is being done to accommodate our
foreign customers and those whose Match Maker networks reach
into foreign countries.
Added a new option to the CFG file. This option will control
whether you wish to use the ALIAS the caller has on the BBS.
The way this will work is you must be using DOOR.SYS as the
'drop file'. When the caller logs on, and the CFG file says
to use the ALIAS in the DOOR.SYS, the program will place the
ALIAS it finds in the area of the screen the caller would
normally use to manually enter the ALIAS. The caller will be
asked if this is correct. If not correct the caller will be
asked to enter the ALIAS manually. NOTE: Callers already in
the Match Maker database, prior to this option going into
effect, MUST use the ALIAS they entered previously.
Minor verbage change to the MMAKER.TXT file
CFG option that controls the use of the DOOR.SYS
Alias/LogonName uses 3 possible numeric entries:
0 = Don't use the DOOR.SYS ALIAS option. Manual entry of ALIAS
1 = Use DOOR.SYS Alias for MMAKER Alias
2 = Use DOOR.SYS LogonName for MMAKER Alias
Use 1 if your BBS software puts the Alias in the Door.SYS
Alias field. Use 2 if your BBS puts then Alias in the
Caller's LogonName field of DOOR.SYS.
If a new caller takes the (D)efault answers to the questionaire,
they will NOT have access to options 4 and 5 on the Main Menu...
UNTIL they answer the questions online or upload their answers.
When using option 10 in MMAINT to format a question file, and
you had a BLANK after the M or S (for multiple or single
answer), MMAINT generated an error 'S or M missing'. We will
now trim the blanks before testing for an S or M.
MM Exchange log file has been revised to make it easier to read
New command line options added to MM Exchange if you are acting
as a HUB in a Match Maker network. Further explanation can be
found in the MMAKER.DOC file.
When reading a user's profile AND there is a Picture attached
that has a file name containing an invalid Drive letter or
directory name the program will just ignore the fact that a
picture is present. This will normally happen when you are
reviewing a user whose profile was imported from another board.
09/01/93
[v3.5] CLEXCH was not importing any files other than one with the
same name as the name defined in the CFG file.
You can now use 3 lines for each question.
NOTE: You MUST run MMAINT and choose option #10 !!!!!
There have been several reports about problems related to
deleting messages. The reports indicate that the message gets
deleted, but the system hangs. I believe I have found the
problem and fixed it. If you were one of those experiencing
the problem, please let me know if this release fixes it.
There have been several reports of MMEXCH not recognizing
a legitimate registration number. Finally tracked it down
and it should not be a problem any more.
For technical reasons, MMAKER no longer supports CHAIN.TXT
Several reports of receiving Error #70, even though SHARE
was loaded. I believe the problem is now resolved.
When a caller is in the Message Center reading a message and it
is a 15 line message the <R>eply <D>elete.... etc overlayed the
15th line of the message... fixed!
Updated MMAKER.TXT
07/14/93
[v3.4] Program was not accepting uploaded questionaire responses
Scenario: New caller enters MMAKER, fills out info, chooses
to take the Default answers to the questionaire. On next logon
they decide to upload the answers to the questionaire, however,
they were being forced to answer the questions manually before
they had an opportunity to upload the answers. We have changed
this to bypass the forcing of question answering if the caller
originally took the default answers.
When using option #1 in the MMAINT module, you were being
returned to the main menu if you deleted an entry. The program
will now continue to present all the users in the database.
This will allow you to delete/view as many callers as you wish
in one pass.
06/19/93
[v3.3] Added support for the PCBoard /M version
06/09/93
[v3.2] Fixed the ERROR 52 problem when uploading replies to
the questionaire.
After deleting a user record via the MMAINT program, the
alias was still being displayed when you chose the
'display all users' option in Match Maker Door.
Found a problem that seems to have been in the program for a
few versions now. If a caller viewed another callers answers
and then chose option 2 to change their answers, the changes
would be fine, but you would not be able to reference the
record of the person you had viewed using option 5. That
person's record was fine but the program overwrote the index
entry. The only way around it was to use the maintenance
program and re-index the users file.
The PROTOCOL.DAT file can now be made node-specific to
accommodate using special information that is required for
certain nodes and not for all nodes.
There were reports about questions being changed by the
caller and the changes not being reflected the next time
they called and used the door.
If you used option 1 of MMAINT to delete a user's alias, it
would do so from the Master record, but not from the index
file. When you went back to the Match Maker program it still
recognized the caller as having been on before.
When answering questions, the callers will not be asked if
the answer is correct, since they always have the option of
changing answers via the "Change Questions" option off the
Main Menu.
Added an option to the configuration file to ALLOW/DISALLOW
the changing of caller's questionaire answers.
Added an option to the configuration file to ALLOW/DISALLOW
Uploading/Downloading of files.
With this version, you will have to run the MMAKER maintenance
program (MMAINT), option 10, everytime you make a change to the
MMaker questionaire file (MMQUESTM.QUE and MMQUESTF.QUE). This
option will convert these ASCII files into a format that can be
used by MMAKER. The extension of each file will be .DAT after
the conversion is complete.
Added an option to the MMAKER maintenance program (MMAINT) to
allow the Sysop to clear the questionaire answers for an
individual caller. You might want to use this option if you are
not allowing the caller to change their answers.
Fixed a problem whereby the caller could enter a letter, as an
answer to a question, that was greater than the highest answer
letter displayed.
When multiple answers to a question were allowed, the caller was
getting confused as to how to enter the multiple answers..
an example is now shown at bottom of screen.
When reviewing another caller's answers, the caller will be
given a choice of displaying one question and all possible
choices, one per screen OR a continuous display showing the
question and only the answers.
If a caller does not answer the questions, but takes the
defaults, they will not be able to view any other caller's
information until they either answer the questions online or
upload the replies.
If more than one message was waiting to be read, the caller
would only be able to read one of them at a time, per call.
When they logged off and back on again they were presented
with the next message.
The main menu will now reflect the number of messages the
caller has waiting to be read. It will continue to display
until the caller has read/deleted the messages addresssed
to them.
When a caller chooses to change answers to the questionaire,
they will now be able to choose a SPECIFIC question number
rather than having to go thru all the questions to just
change one or two.
SYSOP can now send a message to ALL Match Maker users on
his/her board only (will not be exported if running in a
network). This is accomplished by entering ALL in the TO field
of the message. Be aware that this message will be flagged for
the user to read EVERY time a caller opens the door. You can
delete the message by reading it and taking the delete option.
The message can not be replied to, nor can it be deleted by
the user.
If a caller does not answer the questionaire (chooses defaults)
they will not be able to enter a message, reply to a message or
make a match. If they choose the "Change questions" option to
answer the questions they previously bypassed when they first
logged on, they must answer the questions or choose \ to leave
the door.
Prior versions would only allow the caller to use the door once
per day in the UNREGISTERED version. Only limitation will now
be the number of users and number of messages.
03/10/93
[v3.1] NOTE: You MUST run MM31CVT.EXE to convert/expand the Master
User File (MMAST.DAT). The program will also DELETE the
existing MESSAGE Database. Due to a requirement to incorporate
more information into each Message record we could not keep
any current messages. (ONLY RUN THIS ONCE AND BACKUP THE
DIRECTORY BEFORE YOU START!!!!)
The Configuration file has been expanded to include two(2)
new entries. These entries are required to accomodate the new
Match Maker Exchange program. See DOCs for explanation!
BRUN45.EXE is no longer required!
Added support for Comm Ports 0-15
Added support for Multi-port cards!
When at the "Enter Alias" prompt, caller will be required to
enter a "Q" to quit. Previously an "enter" key would have done
that, but if a caller pressed "Enter" too many times, when the
door started, they would be returned to the BBS prematurely.
State/Country information expanded to 3 characters to
accomodate foreign country definitions.
Maximum number of questions has been increased to 100 from 50
Added another option to the Sexual Orientation match criteria.
(A)ll will allow for the matching on ALL Sexual Orientations.
If the Sysop changes, adds or clears all questions the Match
Maker will force the caller to answer those questions. In this
version the caller will be taken DIRECTLY to the CHANGED/NEW
questions without having to see any of the others. Previous
version of the Door required the caller to have to step thru
ALL questions. We have included a new MMNEWQUE.TXT file to
reflect this change. If you have created your own then you may
want to change the wording to reflect this enhancement.
All KEYBOARD responses will now require that you press the
"Enter" key. The "hot key", although a good idea, seems to have
caused some frustration on the part of callers accustomed to
working with 'non-hotkey' systems.
Added a "Color ON/OFF' option to the Main Menu to allow callers
to turn the color ON/OFF by just selecting the option. Turning
color off will more than likely speed up the screen displays
for slower modem users. Whichever option the user chooses, that
option will carry from logon to logon, until changed again.
Added 2 new options to allow your callers to DOWNLOAD the
questionaire file, develope their answers and UPLOAD answers to
the door. You MUST run the maintenance program and select option
# 7 to CREATE a formatted questionaire file for download. You
should also check the new file: MMDLTEXT, to see if you wish to
change the wording that will be placed at the beginning of all
downloaded question files.
New callers will now be asked whether they want to answer your
questionaire while online or take the default answers, download
the questionaire and upload their answers on next call. The
default answers to ALL questions will be the "A" choice.
MMAINT was not deleting entries you marked for deletion using
option #1.
Changed 'Sexual Preference' wording to 'Sexual Orientation'
Added a file called PROTOCOL.DAT. This file will contain ALL
the protocols you allow to be used on your system along with
the name of the batch files that each protocol will use for
UPLOAD and DOWNLOAD. See Docs for more info.
With this version of Match Maker we are introducing a program
called MMEXCH.EXE. This program will allow you to exchange
Match Maker USER and MESSAGE databases with other BBS'. The
MMEXCH requires a separate Registration number and makes the
networking of Match Maker relatively easy to facilitate. Your
MMAKER config file MUST be updated with 2 additional entries,
whether you use the MMEXCH or not!
Reformatted the documentation and added a Table of Contents.
Just bear in mind that I hate writing documentation <grin>
We have expanded the use of the TRASHCAN file. It will now be
used to check against the contents of all messages entered. It
will only check the body of the message and will replace all
occurances of words found in the MMTCAN.DAT, with asteriks.
When doing matching, if the LAST user in the database does not
match on any questions/personal criteria, the program would
display the "No Matches Found...." message, even if there
were other matches displayed. This 'bug' has been in Match
Maker since version 1.0 as far as I can tell.
MMAKER.TXT updated.
11/08/92
[v3.0] WARNING: If you are upgrading from a prior version, you must
run MMDATCVT.EXE to convert the MMAST.DAT file to accomodate
the changes made in the way the program handles multiple
answers per question. Just run MMDATCVT.EXE! All entries in
the database will be marked as being (S)traight, so if you
activate the Sexual Orientation option, be sure to let your
callers know that they will have to update their Personal
Information if they have another preference!!!
Added support for TRIBBS software. We now access the
TRIBBS.SYS system file directly!
After a CHAT or DROP-TO-DOS the game screen will now be
restored to its original state.
The program was counting each use of the door twice in the
same call. In other words if you said you wanted to allow
