> Stephen Boyd wrote:
>>
>>I wonder if this is a bug that should be reported to the developer list?
>

Ann W. Harrison wrote:

> Yes, I think so, thought given it's a 1.03 problem and people are very
> focused on 2.0 and Vulcan, it may not get the attention it deserves.

I did mention it on the devel list, and Vlad responded that they found
and fixed a bug in the 1.5 release that could cause the problem you're
seeing. So unless someone has a case that shows up on 1.5 (or later) I
think that's the answer. It is possible to create a custom build of
1.03 that includes the fix - pretty straight forward - but as this is
not a priority 1 bug, a full 1.0x update is unlikely.

Regards,


Ann