>I (and others!) will be waiting for the next release of code and it is my
>hope that it will *not* be release until the cause of this error is
>thoroughly vetted and resolved.

I on the other hand wish to try and test any pre-release fixes, since there 
really are no working version for the Windows at the moment. We need to find 
*something* asap, even if it fixes just some of the problems.







Reply via email to