D DavidHB Active Member Oct 4, 2010 #2 It's a known issue. Joel only discovered the error after 6.0.7 was released, and decided not to correct it. David
It's a known issue. Joel only discovered the error after 6.0.7 was released, and decided not to correct it. David