*-------------------------*
| Version 1.33b of PCMENU |
| Sat  10-06-1990         |
*-------------------------*


v 1.33b
=======
-A little bug in the configuration routine would cause trouble when the /c
 option was used on a monochrome machine.  This is the only change from
 version 1.33.


v 1.33
======
-This is a very minor revision.  There was one new bug, in that any invalid
 dot command in the file would show up as a menu selection item.  Invalid dot
 commands are now simply ignored.  There was something appealing about leaving
 the bug, as it would highlight erroneous dot commands - but the downside was
 that these bogus menu items had no commands associated with them and would
 therefore cause an immediate exit to DOS if selected.  The possible security
 problems outweighed the advantages...

-Since I was issuing a new cut anyway, this seemed a good time to finally
 change the default name of the startup batch file to 'MENU.BAT.'  I think at
 least 99% of the people using the program prefered that name, so might as
 well make it easy on them (and on me.)  The initial reason for PCMENU.BAT was
 that Novell users alread had a menu command defined - but now everyone can be
 kept happy (ha! - I'm sure someone will complain about this...)

-I've been asked by users to re-emphasise the fact that only pure ASCII files
 should be used.  One user used some editor called QED, and had trouble.  I'm
 not familiar with that editor, but the same user switched to QEdit and his
 problem was solved.


v 1.32
======
-Combined the various utility programs into one new utility called PCMSCFG.
 This is a command line driven program which uses different switches to tell
 it which function is desired.

-This PCMSCFG program also includes two new abilities.  First, it will allow
 you to change the name of the default startup batch file to anything you
 like.  It will write the new name directly into the PCMS.COM file while
 creating the batch file for you.  Second, it will optionally omit the batch
 file call based on the environment variable if you don't require this network
 support (making the batch file a bit smaller and faster.)

-Added ability to use '/' command embedded *within* other commands in a menu
 text file.  Previous versions required that it be the last item - or more
 precisely they ignored everything subsequent to the '/' command.

-Removed added error message about invalid dot commands.  This was helpful
 when first switching to v1.30, but the added size of the batch files was not
 in keeping with the 'small & fast' utilitarian approach.

-I've had a couple reports of odd behavior with menu files, but have not yet
 had a chance to examine the files in question.  In one case, however, simply
 suggesting the person examine the sample files and try using the QEdit editor
 solved the problem.  At this point, I'm not sure if there is a bug in the
 file parser or not.  I think that, if so, it's a pretty benign one.  Also,
 one of these reports was from an *old* version of PCMENU, so if it were
 really much of a problem I think I would have heard more about it by now...


v 1.30
======
-Added a new '+' option which allows the menu to appear with a selected item
 already highlighted automatically.  There are three places where this can be
 used: on the command line (PCMENU +6), after the '<' command (<utility.pcm
 +6), and after the '/' character (/+6).  See docs for more detailed
 explanation.  This option allows you to set up easy to use systems which
 anticipate the choices for the user.

-Employed the above '+' option to allow the '/' auto menu restart feature to
 'remember' the item which was previously selected and return to it after the
 item has been run.  This is the default behavior, but if you prefer the old
 system of always returning with the first item highlighted, just use '/+0'
 instead of '/' alone.

-Improved the mouse routines a bit.  The mouse cursor will initially be
 displayed on the first character of the item which is currently highlighted.
 If the highlight bar is moved via the keyboard, the mouse cursor will follow.
 Also, hitting a mouse button will now restore the screen when the screen
 protection routine is running.

-Took out the .a= administrator password option, as it was too insecure.
 Instead, added new encrypted administrator password option, which is
 installed directly into the PCMS.COM file with a special PCMSPASS program.

-Added error message if any invalid .dot commands are found in menu file. This
 was necessary to remind us to change all of those old .a= commands...

-Dropped the multi-tasking version, as no interest was displayed in this.