SamplerBox not reading my thumbdrive (or keyboard?)

Hi Ryan,
Thanks for your post, very good news.

First of all that you have a working solution before the deadline - be it some sort of bypass for some wishes you have. It works, phew....

I'm also glad that my "frowning" was caused by misunderstanding, where time pressure and limitations of e-communication may have done the rest of the job (and yes, I'm human too). Chat sessions can be facilitated by help desks, but not by individuals. I tried and found it suppresses all other activities. Free/open software requires DIY and/or patience - completely incompatible with deadlines.
Your post is crystal clear, so I'd say: let's continue without hard feelings.
In fact having proper feedback & questions help and inspire me, so my helping you is not one-way traffic.

Having said that, resume of open points:

• Reading the samples area on SD from Windows is solved in upcoming release by converting it to NTFS
  
• Documentation for this upcoming release has improvements (still working on that), so "it's in the docs" will be easier. I welcome feedback on improvements for docs - I understand that I consider things obvious, because I'm deeply involved.
  
• Instrument switching for M-Audio Oxygen requires some investigation. Reading the manual I noticed there seems no button equipped with the standard midi program change ("preset change" often refers to a proprietary feature). I propose to proceed this subject via PM's, preferably without ambition to solve this before your performance.
  My intention was/is/remains to give midi devices control over all SB's functions except for editing definitions or maps. If the limitation is on the midi device ("no buttons.."), this can be bypassed via buttons+screen on the box. The Oxygen looks well equipped, so I'm optimistic on that (as a side effect I hope to be able to produce some sort of howto for doing this).
  Bottom line: no PC's needed on stage. The webgui is a nice to have tablet/phone gadget with special bonus of editing definitions/maps becoming more and more available (programmer's challenge...).
  
• A working linux machine is not necessary for getting debug info if you can establish a network connection with the box. This can be either via just wiring it to your home network or adapting /boot/wifinetworks.txt with your home network info and the Commandline access and debugging is possible.
  

All above to be addressed in separate threads or PM's; this thread is closed in my opinion as the subject has been achieved.
Thanks & regards, Hans