通过

Suggestion Box

  • 项目

Recreating the suggestion box :)

Please note that I reserve the right to choose which suggestions I write on, and I'm not likely to write about things I don't know about.

Topics I feel comfortable writing about (in no specific order):

  • Microsoft History
  • Windows Audio (if I don't know the answer I can find it)
  • Microsoft Exchange, and email in general
  • The Win32 APIs, but not the Win32 GUI APIs (I'm not a UI programmer)
  • Software engineering
  • Debugging tricks and tips
  • Security - but NOT about specific exploits etc - there are legal issues involved that I'm not willing to push.
  • COM, DCOM, RPC, etc
  • The .Net framework (although there are others far better at that than I)
  • Localization/Internationalization issues

Topics I don't feel comfortable writing about:

  • Legal issues.
  • Internet Explorer (there are others better suited to write about that)
  • Windows GUI (ask Raymond, he knows that stuff, I don't)
  • Why doesn't my code work? (Unless the reason it doesn't work demonstrates a general principal)
  • Longhorn specifics (including multimedia in Longhorn)

Comments

  • Anonymous
    February 28, 2006
    Hi Larry,

    Since February's Vista CTP build is supposed to be feature-complete, are you going to drop the 'Longhorn specifics' from your list of uncomfortable topics?  We should be seeing all the new features by now :)
  • Anonymous
    March 01, 2006
    The comment has been removed
  • Anonymous
    April 05, 2006
    You should talk about the real Windows 95 architcture.

    The real Windows 95 architcture is really two parts. The first is the VMM and VxDs. The second part is the KRNL386.EXE, User.exe and gdi.exe, and all Win16 and Win32 DLLs and applications and everything else in the system VM. Think of that as it was a 16-bit DPMI application. At least it is that way when startup is completed. After the VMM init is completed, if the Winstart.bat file exists, the VMM executes command.com inside the system VM, which executes it. And after that, it executes KRNL386.EXE, which is a 16-bit DPMI application. What about win32? The Vwin32 VXD, together with Kernel32.dll handles that. At the time the KRNL386.EXE executes, it kicks in to load kernel32.dll into the System VM. How does kernel32.dll communicates with the VMM? it uses an undocumented function called CallVxD.
  • Anonymous
    April 14, 2006
    The comment has been removed
  • Anonymous
    April 26, 2006
    Have _beginthreadex() and _endthreadex() been deprecated?

    There is no documentation on it on the MSDN site - just a brief mention in the CreateThread() entry.

    For those of us who still use the standard C library, is there a better threadsafe alternative?
  • Anonymous
    April 26, 2006
    Ok, I feel foolish, there are no links to it from the CreateThread() page, but the pages do exist.

    Maybe you might like to comment why they make those pages so hard to find.

  • Anonymous
    May 06, 2006
    The 286 protected mode was very powerful for a PC. It could have brought lots of things from minicomputers into the PC.
    But was it be able to run many of the DOS applications?
    It could have been able to run it, if not for the direct hardware access and segment arichmetic etc. that most DOS applications use. It was one of the consequences for the fact that DOS and BIOS APIs were limited.

    But what if Microsoft, on 286 introduction, started development on Protected Mode DOS and finish it in time for the AT lanuch?
  • Anonymous
    May 16, 2006
    Would be nice if your blog pages had a "printer friendly" link
    that showed the page without the stuff in the left hand pane.
    Otherwise, printed versions of your blog pages have the
    calendar and stuff at the top and a huge left margin. :(