Hi folk,

Thanks for your replies. Much appreciated.

I tried Steven Marche's SoundDiver tips - cheers! Running in Win9X compatibility
mode definitely helps. I found that I was getting system exclusive error while
doing transfers, but without running in compatibility mode, there were no error
messages. The program would just do nothing for some time, and be unresponsive.
Running the MIDI loopback test showed no errors though.

I know many people who have chosen my brand of MIDI interface because of its
ability to handle sysem exclusive data reliably (not all interfaces will do
this) so I doubt there is an issue there.

I had tried converting some patches to .syx format, but had only partial success
loading these into SoundDiver. I may just have a few corrupted files though.
I'll try some more later.

Using MIDI Quest, I didn't get any of the system exclusive errors that were
occuring with SoundDiver. I suspect I have probably disabled some Windows
components that are needed by SoundDiver - perhaps some legacy libraries or
such, which I thought I could do without. As I am using a rather old computer I
have tried to streamline the OS a little, but maybe a little too far.

I think MIDI Quest 9.1 runs OK for me in WinXP SP3 with an Intel P4, though stil
not brilliantly. Version 10.x is a different story. Perhaps again, I've over
tweaked my system. I'll have to try all these with a basic installation.
Overall, I was still a little dissapointed with the program, given the price.

I'll also have a look for a MOTU Unisyn demo, and post back with results.

I've had the K5000R for more than 6 months now, and haven't yet given it the
attention required to get resuls from it. I hope to get a good editor
environment running soon.

Thanks a lot for all your help and input folks.

Oli