Slobodan,
I was wrong in my statement.
I just played with the component a little bit. It seems to be a macro
component with a custom CMI script.
It allows you to add particular device class support (check-boxes) to you
image. At the Dependency Check phase it just adds the
required Class Installers and etc.
But at the Build time it builds all the drivers for the selected device
class in the image.
Very nice component implementation. It does not blow up the SLX
(component are not in the Configuration) but all the required
drivers get built in the image.
--
Regards,
Konstantin
Hi Konstantin,
I was under impression after the chat we had with MS that is some
mysterious way this will bring all components that are related to
certain category.
If it is as simple as you say it is, I wonder why do they market is as
new option in SP2. We had generic components before so what
would be a difference?
Regards,
Slobodan
Slobodan,
"Generic Driver Support" component does not bring all the printer (or
specified device class) drivers. It just a simple
wrapper
to
bring class installer, etc.
It does help to have an easy way to have a support for any printer in
your image.
But, I guess, it does not help much if you want to support many [all
supported by XP Pro] printers and don't want end users to
mess
around installations (or do not provide a way to add printer
drivers).
--
Regards,
KM, BSquare Corp.
Hi,
SP2 Release should have support for generic driver components (I do
not remember exactly how they called these components) They
should encapsulate all other components from same category. This is
not very configurable but will do the job for you.
Regards,
Slobodan
Is it possible to add (auto?) all components of a category (like
Printers or
Modems) without to take each one (2650 components for
printers!!!!) ?
Maybe with Macro Component but depency is on a group or
components not on
category ...
Fred
