P.S. Here are the most significant fixes in this latest 1.0.9.6 release of MidiNotate Player:

1. The page setup saved in the .not file is now correctly restored when the file is reopened, even if the paper size or other page settings are not the defaults for your printer.

2. Conflicts between MidiNotate Player and other versions of MidiNotate in the area of MIDI device configuration have been resolved. Now, each version of MidiNotate-- that is, Player, Musician, Composer, and Composer Pro-- has its own copy of the MidiDev.cfg file in its own subdirectory of \Program Files\MidiNotate. For backward compatibility, the first time you run MidiNotate, it will copy the MidiDev.cfg file from the \Program Files\MidiNotate family directory to the local directory, such as \Program Files\MidiNotate\MNPlayer. This solution resolves the conflict, but comes at the cost that the various versions of MidiNotate now no longer share a common MIDI device configuration. For example, if you have Composer and Composer Pro, and make a change to the MIDI device configuration in one, you'll have to make the same change in the other.

3. MidiNotate's handling of the .mid file association is much more robust now. When you install one of the versions of MidiNotate, it will remember what MIDI application was previously associated with the .mid file extension. If you later uninstall MidiNotate, the previously associated MIDI application will be re-associated. This works the same way as (and in conjunction with) the Associate command in MidiNotate's Setup menu. This design has a flaw that the previously associated MIDI application that is restored might no longer exist of the user's system; but that case is much more rare than the common case where the user would like to restore the association to the old MIDI application that is still on his system.

Cheers
-- Mark