> > At our place, we have our own printf-style functions (along with lots of other
> > bits of libc), so that we can control that stuff directly.
> Yeah, we do the same thing. Also allows cleanly locking out printf on
> final/release builds. Lots of devs don't - if you have a T10k, boot up Jak and
> Daxter on it, and watch the TTY literally dump pages and pages of detailed debug
> info as you play (seen it myself on the US NTSC release, the PAL version might
> be cleaner). Or more (in)famously, SCEE's Porsche Challenge on PS1 prints out
> something like "USER IS A BLOODY GIT" if you don't finish the race.
Ha! I thought T10k couldn't play commercial games though?
Actually though maybe there are some boot flags you can set to make it act like a real PS2... can't recall
So TTY output isn't even a Sony TRC violation anyway (not that I ever left TTY output in in the first place, %!$£!)?
...or Jak and Daxter wouldn't have shipped?
You learn something old everyday...