You guys are welcome, I hope my reply did not sound too harsh... I was
rushing a little to look up valid links to explain the issue.
miniMUNCH, I think the idea was that any app that would be sharing a VXD should
be addressing the same instance of the driver; whether it is loaded from the VMM
or separately. This is a trade-off, more efficient management of the resource with
a slightly greater risk that the driver will poorly handle multiple requests.
That doesn't really answer the question, but as far as I know, the VMM32 file is
designed to react to the system as if it was the individual file.