This is a must feature for me being the geek I am. I will pitch in the efforts to get this working. It has too work and it will work and we will find it.
I noticed the eshell.exe text file referenced a version of DOT NET (v2.0 exactly). I also know Vista has a patch out there which fixed a virtual memory error that failed to CORRECTLY apply “software restriction policies” or the lack there of. There were some issues installing some drivers which this particular patch fixed in Vista (seeing that you are getting the same error in your thread above).
I’m going to match the dot net framework versions per Vista and see where that gets me. As for the patch, I say we keep that in the back of our minds. We’ll figure this out with world wide mass efforts.