It's not just the firewall protecting them here. Both group policy prevents that in the first place, plus the script won't connect successfully with the firewall in the way. That's tested against both 64 and 32 bit Windows 7 installs done from the RTM build, by the way.

Having actually tried this on three windows 7 machines now, it doesn't seem to work on every machine. (Actually, it's yet to work on any here, although I hear tell that it does work on some). There's something more to this than just "that data crashes it every time".

There's no such thing as "properly scaling" between 720 and 766/768 (I think the hardware resolution's 766 not 768 if I remember right; either way, 2 pixels don't matter - the video mode on the PC is certainly 768 though). They're far too close together to scale without beat frequency issues. Not accepting the native resolution I'd agree is a definite failing of the product, but I honestly can't criticize the scaler - it does as good a job as can reasonably be expected i.e. bloody awful. At the end of the day, to scale between these resolutions means inserting 48 extra lines into the display *somewhere*. It doesn't matter how nicely you do this, or how intelligent the algorithm, it's still going to mess up display of text or any fine-detailed horizontal pattern.

The inability to set the native resolution I suspect may be part of some misguided effort to avoid confusing anything connected to it - at least it's safe to tell games consoles etc. that it does 720p and 1080p; I assume they'd ignore an extra 768 resolution, but I wouldn't be too amazed if that messed something up on some product somewhere.