[chronster]

This is really weird. I had this same issue, but setting it to 0 is what fixed it as it was already set to 1.

Perhaps there's something going on here where simply changing this fixes it, but it doesn't matter if you change it to 1 or to 0...

Odd...

Thank you for the info nevertheless.