<< Thanks a lot for your effort on this. I figured this out after I
installed the official driver and it worked fine. Unfortunately, I did not
find this information before. >>
I've corrected this for the next build, however I don't think this was the
same issue that you were seeing unless it somehow managed to manifest itself
in an entirely different fashion than my VS2005. Irregardless, I'm glad
that the problem is solved and you're back up and running. My apologies for
all of the problems.