Thanks for the feedback, folks. One more quick question - have any of you had any contact from Areca about getting this issue resolved in 5.0? The drivers currently on their web site date back to October 21, 2011 and apparently the problem is ongoing. Thanks again for your response on this.
-Erik