Is this with v2.0b3, or an earlier version of the software? I ask because there was a version of v1.0x that had a problem suspiciously similar to this.


-- roger