Thank you for expressing your opinion. I agree 100% with you and I'm going to focus on (W)LAN drivers first because they are critically important and not very difficult to integrate too (and most manufacturers still officially support Win2k even in the newest releases of their drivers). Mass Storage drivers are also critical but there's one very important issue - if the system detects the controller wrongly and applies an improper driver then the system won't boot. This seems to apply to the AMD SATA drivers which are available in many different versions. Once I tried to integrate two of them in the same Win2k source and the system applied them wrongly so there was a BSOD on boot. Still integrating at least some of the Mass Storage drivers is a "must" so I'm going to integrate them but I'll be very careful when doing it.
Some drivers can be integrated without any changes but I've checked some others, ex. the drivers for Matrox G* cards and there were many useless files there together with the proper system files. I'm going to remove all of such files because they are not required to make the drivers work and only take space in the driver.cab. What I mean is that I don't think anyone needs explanatory *.PDF or *.TXT files to be installed with the drivers, right?
Such files are normally installed when you add Matrox drivers to the system.
Adding VM drivers sounds very interesting. Have you got any specific drivers in mind? I use VirtualBox myself so I can try to add the ones for it but I've got no clue about the drivers for other VMs.