mjones mjones

Niner since 2005


  • Donn Terry: PreFAST for Drivers

    Great seeing some of men behind a wonderful technology.  Keep up the great work.  Just wish it was more technical.  Loved your definition of real time code: Concurrent code that is timing critcal.  Just wish it was more...

  • Juggs Ravalia – Windows CE 6.0 Device Driver Model

    I enjoyed the video.
    (1) On all of the interviews on Channel 9, why not use the PC tablet instead of a white board.  Hard to see the white board.  Cool app time maybe for creating presentations.  Use it here then sell it.
    (2) Just a suggestion, synchronous and asynchronous sounded exactly the same Juggs on the Video.
    (3) After adjusting to the two above the presentation was Excellent.  You are clear and you convey understanding. Thank you. I for one liked when you showed how some of the supported Kernal apis are supported in both kernel and user mode.  Also the statement the Reflexor is the nucleus of the UMDF. 
    (4) Using UMDF in Windows CE stills teases me with respect to porting code from Windows to Windows CE.
  • Juggs Ravalia – Windows CE 6.0 Device Driver Model

    Will watch the video tonight.  Question:
    I asked a question to Peter Wieland on his Channel 9 video of UMDF about if the source code for a UMDF can be recompiled in the Windows CE 6.0 environment and the Driver will run.   He replied and left the question open.

    You can of course see the benifits of this just as WDM did for Windows 98 and Windows 2000.   You get of course "free" drivers shared between Windows and Windows CE.

    -William Michael Jones

  • Doron Holan - Kernel Mode Driver Framework

    (1) Excellent.
    (2) What about hot pluggable KMDF components. 
    (3) Loved seeing the State machines.  Wonderful way you did that too d.
    (4) Isolation in the KMDF with garbage collection, smart pointers, COM in the kernel, etc.  More Isolation and better detection will even allow maybe recovery from the KMDF BSOD. What about ring 1 and/or 2 for KMDF to achieve isolation and for debugging  a recreatable memory access.
    (5) Loved hearing about the serial KMDF sample. Excellent.
    Devil Thank you d.
  • Peter Wieland: User Mode Driver Framework

    Good.  Thought, how about UMDF and  CE.  Maybe the design of a UMDF component could port to CE with changes done in  CE to support this and a changing a  KMDF to work in CE but at least you can get the UMDF to port.  In other words how to leverage UMDF to CE.  Being layered in CE of course performance but if you get the driver for "free" and it works great.

    -William Michael Jones
  • Virtualizat​ion

    Excellent.  Will you support MultiMontor support where each VM is on a separate monitor?  Will you support Seamless VMs where its desktop is in a window on the host desktop?  Will you support Seamless apps from a VM where the app will display on the host desktop?  Good for legacy apps.  Definitely the host or displaying VM should use all the great display technology, for example 16 monitors with 3D effects. I see maybe an advantage here with debugging kernel code coverage with your restart feature. You said you have things to help kernel development, I find that interesting.  With Multi CPUs will the VMs run on separate CPUs?  Also since the Hypervisor will never crash, servers can always be inband and controlled remotely over say Ethernet. Also could the Hypervisor be scaled to the Workstation - 1 CPU to always allow inband connections for remotely controlly boxes that even BSOD. This is definately good technology - thank your time. Like to hear more.
  • Windows, NT Cache Manager - Molly Brown - Part II

    Excellent Molly.  I like this stuff just wish I was better. Indeed some of the tuff problems are because of their time to reproduce.  Just some thoughts: How about trying to do kernel code coverage with the following:
    (1) Sometimes it is the permutation of aquiring synchronization objects.  How about varying the kernel with virtualization technique that allows a restart in the kernel where we need to see the permutations of code taking with shared synchronization objects. Get the code, or threads all waiting to acquire the shared synchronization objects then, take a snap shot of the kernel, now allow one permutation to continue, etc. If ok go back to the snap shot of the kernel, get it running or looping for release, now allow a different permuation to continue, etc. Just some thoughts on this...
    (2) How do we analyze code coverage - well use a static analysis code to replace the acquiring of shared synchronization objects with a looping on the acquire such the all the permutations can be seen to run.  Ok.  Now we then have data as input - well maybe the boundary conditions on data can be feed into this  simulator as well.  Just some thoughts. 
    (3) Also you mentioned the intrusion principle that changes timing such the bug so away, effects the permutations... We how about some hardware that can be put into the memory accesses between the CPUs and physical memory - like a PCI bridge chip - but will add debugging info with flows of memory accesses and data and not change the timing.  I still believe hardware can help here alot in ways.
    Just one more comment - MORE of the neat free stuff please - also why are the e-classes on development so expensive.  I like them all.  Why not allow them with a MSDN subscription.  The more people use Microsoft languages the better for Microsoft.