That is correct. In all these 'countdown' videos they have a little gimmick where they set a kitchen timer at the beginning for 10 minutes. It runs a little fast. The show's over when the timer goes off, even if that's in mid-sentence.
I cannot recommend attending the pre-conference sessions. At PDC05 I attended PRE03 presented by Brandon Bray, Anson Tsao and others. Anson had some gems in his slide deck that I really wanted. There's a problem, though. Microsoft presenters believe that
the slides and everything will be available to attendees on the DVD afterword, so they don't bother printing them out. But that's wrong. Indeed, in the conference guide for PDC05 on page 39 it says "Pre-conference sessions, Hands-on labs, and keynote/general
sessions are not included".
Even after pestering the presenters with email after the DVD arrived, I never got Anson's slides.
Scott is probably more familiar with ETW than he himself realizes. In Hanselminutes podcast
#52 he talks in detail about end-to-end tracing. I can't be %100 sure, but I gotta believe that the framework ultimately calls EventWriteTransfer() from the ETW API to do its thing there.
I've been working with ETW a lot recently (in C code) (and XML for the manifests, of course). But I haven't seen that there is any facility for a "new feature" with "the ability to crawl the stacks" as Vance puts it, in ETW. I would greatly appreciate any pointers
to more info on that topic. I read Osterman's blog entry but that didn't clarify this point for me.
The current methodology may not be strictly correct but it is understood.
Oh, really? Do people really understand that when talking about bandwidth or processor speed the prefixes have decimal meanings?
Can you imagine the resulting mess from changing binary data metrics at this late stage?
I'm old enough that I don't need to imagine it. I lived in a world where kilo still had an unambiguous meaning. It was orderly, peaceful world of shiny happy people. "Late stage", huh? In physics, kilo has meant 1000 for hundreds of years. See the section 'Historical
context' at the NIST site:
Once upon a time, computer professionals noticed that 210 was very nearly equal to 1000 and started using the SI prefix "kilo" to mean 1024. That worked well enough for a decade or two because everybody who talked kilobytes knew that the term
implied 1024 bytes. But, almost overnight a much more numerous "everybody" bought computers, and the trade computer professionals needed to talk to
physicists and engineers and even to ordinary people, most of whom know that a kilometer is 1000 meters and a kilogram is 1000 grams.
Side note: Somebody please correct the link to Brian's blog to read "Brianbec's weblog" instead of "Brainbec's weblog".