Mozart the Music Processor: music notation software for Microsoft Windows">
MOZART development
Unfortunately no. And with the release of Mozart 4.0, then the Windows 3.1 version (Mozart 1) will be effectively discontinued.
Printing problems
This was a problem with some printer drivers and Mozart 1-5. Mozart 6 has been rewritten to by-pass the problems in the printer drivers and it should no-longer happen at all.
If you are using an earlier version of Mozart and encounter this problem then it may be worth downloading the evaluation copy of Mozart 6 and checking to see if that is ok. If so, it may be worth your while upgrading.
Otherwise, for those using earlier versions of Mozart, here is how to fix it.
The Cause: This problem is a printer driver bug. Mozart is giving the correct instructions but the printer driver is not interpreting them correctly.
Mozart draws the stave lines first and then draws (monochrome) notes over the top of them. The note head is a small rectangle with the oval note drawn in black and a white surround. The "blitting mode" is chosen so that the white bit should ends up transparent on the printer, allowing the already drawn stave lines to show through. On a few printers (ie with some printer drivers) drawing large numbers of such items on a page sometimes seems to cause an occasional random ugly blob (even though, even with these printer drivers, it still works most of the time).
Solution 1: Printer manufacturers release new versions of the drivers at intervals when bugs are discovered. These are usually made available free of charge on their internet sites. It is therefore sometimes possible to find newer versions. (Be careful though: Windows 3.1, Windows 95, and Windows NT drivers are usually different and you mustn't mix these up.) Newer drivers will often fix the problem.
Solution 2: Many manufacturers make different printers with different drivers which are internally very similar. Mozart only uses a limited set of printer functions, and any one of a similar set of drivers will often do. Try installing a different printer in Windows and just print to that - even though your physically connected printer hasn't changed.
Hewlett Packard printers: HP make drivers available from http://www.hp.com - if you use an HP printer it is worth a visit to check that you have the most recent version. (I have just, at time of writing, downloaded the much improved August 1997 version of the NT4 drivers for the HP Deskjet 870Cxi. Hitherto the HP Deskjet 510 drivers worked better with Mozart on this printer.)
Epson stylus: one user reported a problem with D.S. symbol on this printer. I don't know if he had the latest version of the drivers but he reports that he has resolved the problem by installing the Epson LQ 860 printer drivers, and printing to that.
Other printers: If anyone manages to cure a problem with Mozart printing, by downloading updated drivers on other makes of printer, please e-mail support@mozart.co.uk and tell us the make of printer and the URL where the new drivers may be found. We should be happy to add a link here for the benefit of all users of Mozart.
Problems reading files
Later versions of Mozart will read files created by earlier versions - but not the other way round. Usually, when it finds a file created by a later version of Mozart, the program tells you so.
However if you try to read a Mozart 3 file with Mozart 1 or 2 it may tell you that this is not a legal Mozart file.
The reason for this last is utterly perverse. From the earliest days of Mozart (an unreleased first attempt on an Atari ST520) the first two bytes of all Mozart files were "MZ". Mozart 1 and 2 immediately reject any files which do not start with these two bytes. In one of those coincidences which have no right to happen, it turns out that all Windows .exe files start with the two bytes "MZ". I found this out when my e-mail software started telling me that all the Mozart files people e-mailed me were executables! Now it convenient for me (and everyone else using this e-mail software) to be able to open Mozart files automatically when people send them - especially as from Mozart 3 onwards it very easy to send them from MAPI compliant systems. It is also just possible that this coincidence might cause other problems - although I currently know of none. It is probably easier for me to change the first couple of bytes of a Mozart file than it is for Microsoft to do the same for executables. Therefore Mozart 3 writes files starting with a different flag. Mozart 3 can read earlier mz files, but Mozart 3 files (and later) totally bamboozle Mozart 1 or 2. Sorry.
Installation problems
Mozart is finding a version of BWCC.DLL other than the one installed in your Windows or Windows System directory by Mozart itself.
BWCC.DLL is a graphics library written by Borland and installed by most programs written with the Borland C++ compiler. (You can recognise these by the style of tick and cross on the ok/cancel buttons.)
Unfortunately Borland's advice to programmers was almost non-existent. What programs should do (as Mozart does) is install it in one of the Windows directories and only replace an existing one if it is an older version. What many programs do do is install BWCC in their own directory. This causes the following problem.
If any program is running using a DLL, then any newly launched program only sees the running version. If BWCC.DLL is in the current directory or on your DOS search path, then any program may pick up that version.
The solution is as follows: search for all copies of BWCC.DLL on your system. Make safe backups of them (labelling each carefully). (One Mozart user had 7 copies on his system!) Leave only the one which Mozart installed in your windows directory (or a newer one if there is one).
This will cure the problem. (Use a DOS box and go to the root directory and type dir /s bwcc.dll to find all the copies.) There's more on this in the readme.txt file which came with Mozart.
Note that this problem does not occur in Mozart 2 or later as these do not use BWCC.DLL.
Under Windows 95 or NT or later, the Mozart installation program installs Mozart's own DLL's (Dynamic Link Libraries) either in the Mozart directory or in a directory "system" within that directory. (By default the Mozart directory is usually C:\Program Files\Mozart.. but you may have chosen something else in the installation program.) In Mozart 2 onwards, the DLL's have names like mzw32?.dll where ? represents a single character. When Mozart runs, it knows to look in the appropriate directory (if necessary from information stored in the Windows registry). All this is standard practice as recommended by Microsoft.
However it does mean that problems may occur (a) if the registry is incorrectly set up or becomes corrupted or (b) if you want to run more than one version of Mozart (as in the latter case the registry only stores the location of one set of DLL's).
In either case, you can get round this just by moving all the files with names like mzw32?.dll into the Mozart directory (ie into the same directory as mozart32.exe) - as a program will find dll's in its own directory. For Mozart 2 and Mozart 3 the files in question are mzw320.dll mzw32f.dll mzw32s.dll
If you have installed more than one version of mozart32.exe in different directories this will be necessary for all but the most recently installed version. This should not be a problem running later versions together - eg Mozart 4 and Mozart 5.
If you have installed Mozart 3 in a separate directory from Mozart 2, you may find that Mozart 2 no longer runs, but complains about being unable to find a DLL. Sorry about that - we at mozart.co.uk can't duck the whole blame on this one - but the solution is at hand. MOZART is probably failing to find one of its DLL files (Dynamic Link Libraries.) See how to fix this in another FAQ.
MOZART 2 and later versions use the Microsoft Dynamic Link Library, mfc42.dll, which normally resides
in your Windows System Directory. MOZART 3 uses a more recent version of this than
MOZART 2, and MOZART 4 uses a still more recent version, etc. The installation
program checks the version numbers and installs the library upgrade on your system if
necessary. (They are upwardly compatible, and this is the normal procedure for all
installation programs.)
If
you get a message like the one in the title, then this installation has failed and MOZART
is finding an out-of-date version. The usual reason for failure is that a program was
running and using the existing mfc42.dll while you were installing MOZART.
The
cure: reboot Windows and make sure that no programs are running. (NB: the Microsoft Office
toolbar which many people launch on start up is a program and may be the source of the
problem: close this too while installing software.) Then reinstall MOZART.
(If
this doesn't work, use the Windows 95/NT explorer to move mfc42.dll out of your Windows
System directory to somewhere safe - for example a temporary directory or a back-up floppy
disk. Or just rename it mfc42.old. If Windows doesn't let you remove it from the Windows
System directory or rename it, then it is in use by a program. Once you have shut down
enough programs and successfully moved it, reinstalling MOZART will put the new version in
place.)
Note:
Many programs written with Microsoft Visual C++ use mfc42.dll but the operating system
itself doesn't. Programs written with VC++ 4.2 use the older version; programs written
with VC++5.0 use the newer version and programs written with VC++ 6 use a newer one still.
MOZART 4 installs mfc42.dll version 6.00.8267.0
First install MOZART 4 or later in a different directory from MOZART 3. (The installation program suggests a different name, and so you can accept the default.) Then you must move some of MOZART 3's files. In the directory where you installed MOZART 3 you'll find version 3 of mozart32.exe and various other files and a subdirectory called "system". In the system directory you'll find DLL files: mzw320.dll, mzw32f.dll, and mzw32s.dll. Move these up one level into the same directory as mozart32.exe. You will now be able to use either MOZART 3 or MOZART 4 on the same computer. NB do not confuse the directory trees for the two different versions.
Also please note that later MOZART versions will read files saved by earlier versions but not the other way round.
Download the zip file version of the installation program - see the download page.
Unzip the file using a standard unzipping program (eg pkzip or winzip which can be found on most shareware sites). Format two 1.44MB floppies and copy the unzipped files to the disks. Put setup.exe on one disk and setup.w02 on another and label them "Mozart installation disk 1", and "Mozart installation disk 2" respectively. Put the information files ReadMe.txt and file_id.diz on both for preference, but they must be put on the second disk. Running setup.exe from disk 1 will install MOZART, prompting you to insert disk 2 when required.
NB MOZART's Evaluation Copy is freely distributable. The Virtuoso Edition, which you get when you buy the program, is not - it is licensed to you only.
Music Editing
Yes! From MOZART 4 onwards.
Lyrics were a little slow to enter up to and including MOZART 5. In MOZART 6 onwards this topic is covered in detail in the help system.