This problem no longer occurs with 1.2.0 using the same configuration
files as I used with 1.2b10.  Thanks for looking into it, though.

        --Jack;


Reply via email to