I really do think it has something to do with the drive timing. I never had this problem with 1.03. I have not gone back becuase the problem does not happen that often and also 2.0Bx is so much nicer! I also never had it act funny first like lofreq mentioned. . It either works (perfectly) or not at all.

Steve