This bug appears to have been introduced by the fix for #1045220. Dave -- John David Anglin dave.anglin@bell.net