> Or did it break again between 3.3.0 and 3.3.1? I believe so, somebody else asked about it recently and I didn't remember the original bug. -- Scott