06-07-2004, 10:23 AM -
Hah, no disrespect taken. I'm not a BestCrypt developer. 
BestCrypt does do some strange things, but I really don't think that in this case, BestCrypt is at fault. Rather, I think it has to do with the fact that TLB thinks a file system object is there, when it really is not, and doesn't handle it gracefully when it tries to perform an operation on it. This is just a guess, based on what I see, and experience. I could be wrong, of course.
Maybe the difference between how your virtual CD-ROMs behave and how my BestCrypt volumes behave has to do with the fact that fixed drives are handled differently (in general) than removable drives. I am not sure. I can say that I also have removable and virtual-removable drives, and I cannot reproduce the Explorer crash with them--even if I take the same steps I outlined above.
BestCrypt does do some strange things, but I really don't think that in this case, BestCrypt is at fault. Rather, I think it has to do with the fact that TLB thinks a file system object is there, when it really is not, and doesn't handle it gracefully when it tries to perform an operation on it. This is just a guess, based on what I see, and experience. I could be wrong, of course.
Maybe the difference between how your virtual CD-ROMs behave and how my BestCrypt volumes behave has to do with the fact that fixed drives are handled differently (in general) than removable drives. I am not sure. I can say that I also have removable and virtual-removable drives, and I cannot reproduce the Explorer crash with them--even if I take the same steps I outlined above.