Universal VESA/VBE Video Display Driver

From what I gathered, I doubt it would be of any use, as it is for Win 9x.

What would be the point of including a single 9x driver on an NT CD?
The primary use of the DriverPacks is to slipstream them into a source, not to provide a universal driver resource database.

As for the NT version of said driver (I am posting replies to both because I can't make out which one you were referring to. Please ignore the answer that does not apply ), it certainly does sound nice.
The question is just how compatible is it?
Since it replaces a Windows system file, we need 100% compatibility and it has to be transparent for the user.

The size is pretty small, so that's certainly not deterring.

I think it would require some extensive testing on our part just to make sure there aren't any issues (although I do believe the team working on this did they very best in any case).
Also, the replacement of the file is not a default action by the BASE so we'd need a specific update just for that (shouldn't be too hard to implement but I don't code it...).
If it was to be replaced by the Finisher we'd probably have to get around SFC - which in turn requires an altered system file to make it work (I think we discussed this before).

That again raises the question whether it is really worth it.
The amount of PCs still running such an old card while at the same time providing the hardware to meet requirements on Win 2k and above is probably very small.
Even if no 3D support was required, most folks would utilize a motherboard with on-board graphics for the task rather than digging up a totally outdated PCI (or rather ISA) GFX card for display output, I figure.
At least that would be more efficient power-wise (not using a discreet GFX card as well as using a mobo that doesn't use much power, which usually come in the on.board GFX shape).

OTOH, even if there was a mere .1 per cent of the user base employing a specific HW we'd still add the drivers if it fit one of the DP categories and was available as a mass product, I gather.

I do think, though, that because of the nature of this driver, being a replacement for a file delivered with the RTM version of Windows, it would be better to make it into an addon that you could slipstream to your source using nLite or RVM's integrator.
This is how I do it with other system file replacements, and it works great.

Also, this file does not need to have any exceptions applied to it, as it won't be used unless you have a GFX card that needs it, if I'm not mistaken.
So, if you wanted it, you can replace and still have a Universal Windows Disc that can be installed on any system.

What do you think about that approach?

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!