1. You received an errormessage: "bZone did not get any response from the Axk"
Until now, every time this happened to me or someone else, the problem was a misconfiguration or setup fault. You really need to double check everything. Here's a list. These things might seem obvious, but please double check anyway.
If you doublechecked all this and it still doesn't work, try rebooting everything: your Axk, your MIDI interface (if it is an external one) and your PC. Don't start any programs, only bZone. If things still don't work, use the logging feature and send the output to me.
2. You received an errormessage: "bZone received corrupted data from the Axk"
Most likely, this is a problem with your MIDI interface or driver. First of all, you should check the MIDI interface compatibility list. If your MIDI interface is listed there as not working with bZone (marked with a red dot), then I'm afraid there's not much we can do. Someone already reported problems with your MIDI interface, we had a look into it and the problem was beyond my control and could not be solved. Sorry...
If your MIDI interface is not listed there, then let's have a deeper look. The explanation for the corrupted data usually is the following. When bZone tries to connect to your Axk, he'll first ask for an Object List. Basically, bZone will ask the Axk "give me a list of all objects you have in memory". Objects means: programs, samples, banks... This is always (in terms of MIDI) a lot of data and what the Axk does if he has to send a lot of data is split the data in blocks of 4096 bytes (4K). So, he'll send a block of 4096 bytes and then another of let's say 700 bytes (depending on how many samples you have loaded). What your MIDI interface and its driver should do is: accept the first block, store it in some buffer and accept the second block. At some time, the MIDI driver will pass the blocks on to bZone. Now, what might happen is that your MIDI interface does not have enough buffers. Then, when the second block comes in, the data in the buffer (the first block) might get overwritten with the data of the second. When bZone then receives this data from your MIDI interface driver, he'll notice it is corrupt. I hope this explanation is a bit clear.
To make sure this is indeed the problem you are having, you can use the Logging feature (further on this page) and send me the log file, then I can have a look.
What can be done about this? Usually, not too much. If your MIDI interface is not designed for handling large portions of data, then, well, you're out of luck. However, with some MIDI interfaces you can configure the size and/or number of buffers. If you could increase the number and/or size of the buffers, the problem might be solved. Where should you look to see if you can configure the buffers? Well, that depends on the MIDI interface. First of all, maybe, when you installed the driver for your MIDI interface, some configuration utility got installed too. Check if you find one. Secondly, locate your driver in the Windows Control Panel. In Windows 2000, you find it in Control-Panel, Sounds&Multimedia, Hardware. In other version of Windows, things are a bit different. If you located it, click Properties and see if you can configure the sysex buffers in the dialog that appears. Ask me if you need help.
In case of problems and the suggestions above didn't help, do the following: start bZone, choose Tools-Logging. A new window will appear. Leave it open and connect like always, choosing Ax000-Connect in the bZone main window. Go through the connection wizard. You'll see output appearing in the logging window. After connection failed, send the contents of the logging window to me. You can do this by hitting the WriteToFile button in the logging window. A file will be written in the bZone/log directory. Send that to me.