DOWNLOAD: mymess.zip (6K)

COST:
Notta darn thing. Freeware.

DISTRIBUTION:
It may go here, there and everywhere without restriction.
Wanna put it on a CD? Go ahead.
Offer it on your freeware/shareware site? Knock yourself out.

REQUIREMENTS:
Windows95/98.
It's written in plain old C, so you don't need any fat-n-slow runtimes or nuthin like that.

INSTRUCTIONS:
Using My Personal MessageBox is very simple. Along with the program you'll find the file MYMESS.INI. This is where you'll define your messages. You can edit it with any text editor and your entries should be in the following format:

[myitem]
title=My Title
message=This is my message.

Unzip the contents of the zip file into a directory.
IMPORTANT... Make sure that the path to the directory has no spaces...

Something like C:\mymess\ or C:\Somestuff\mymess\ will work just fine. This is a reflection of my feeble coding skills. Until I figure out what I'm doing wrong, this will have to do. Keep the spaces out of the path and it works like a charm.

Create a shortcut to MYMESS.EXE. (Right click and choose "Create Shortcut"). Rename this shortcut to whatever you want. Right-click on the shortcut and choose "Properties". In the dialog box that pops up choose the tab marked "Shortcut". Where it asks for the "Target", add the section name after the path...

For example, from this -
C:\mymess\mymess.exe

To this -
C:\mymess\mymess.exe myitem

You can have a hundred (or more) different shortcuts each using different entries in MYMESS.INI. Each will display a different title & message.

If you write batch files, you can easily use it that way also.

The default title/message is: Message/Yes, we have no bananas. If you get this, then either you are running with no parameter in the shortcut (or command line), or you have placed the program in a directory that has a space in the path.

VERSION HISTORY:
v1.1
After uploading and announcing, I discovered that it doesn't work right if you place the program where there is a space in the path, such as C:\My Programs\mymess\... Rather than immediately try to determine my coding error, I just offered a simple workaround.