![]() |
Does/Will the software run on the Mac?
Short answer: No.
Long answer: For a small company such as Algorithmic Arts, it comes down to a choice of whether to expand the market by supporting multiple platforms with the same product, or expanding the product by using limited resources on continuing development. We have chosen to expand the product. This simply does not leave room to develop for Mac, Linux, etc., much as we would like to.
Does it run on the Mac with Virtual PC?
While we do not support running our software on the Mac, we are told by users that it does run OK on the newer Intel based machines. Try the free download and see for yourself.
Do I need a MIDI Synth to Run ArtWonk or MusicWonk?
If you can play a MIDI file (any file that ends in ".mid") by double clicking on it, you can run our software.
Why do I get a Runtime Error?
Usually a Runtime Errors will come from one of three issues. The most common are from an external device i/o error, Runtime Error 57. This is most likely from your sound card being in use by another program.
Normally the software will trap the error, not initialize the sound card, and so indicate in the MIDI setup dialog box, but the program will run fine. However some MIDI drivers, especially older Windows 95/98 drivers, will not tolorate even being queried by the software if it is in use, so you get the error. Check for another program that might be keeping the MIDI interface busy.
The other Runtime Error, usually a larger number such as 50002, is caused by a conflict with the program components caused by another program using the same components and improperly installing them in its own program directory, so the newly installed program can "see" the component, but other programs can't. This rarely happens with commercial software, but it is very common with shareware and freeware. If our software had been working, but now stopped with this error, try uninstalling your more recent shareware/freeware programs, then reinstall our software.
The last Runtime Error we see happens when you first try to run the software, even before it initializes and displays anything. This is due to a conflict with some (now outdated) anti virus software. The solution is to get the latest update to your antivirus program - to the best of our knowledge all major antivirus programs have been updated to fix this, you only need to get the latest update.