Common Control Libraries

  • Thread starter Thread starter JoP
  • Start date Start date
J

JoP

Hi all!

I found that the component <Disk Drive> as a dependency upon the
component <Class Installer - Disk drives>. <Class Installer - Disk
drives> as a dependency upon <Class install library - storprop>. For
now it's okay. <Class install library - storprop> as a dependency upon
<Common File Dialogs>... why? <Commond File Dialogs> as dependency upon
the Common Control Libraries (v5,6...) components. So why there is a
link between the disk drive component and the common control
libraries???
Anybody as tried to run xpe in minlogon mode without the common control
libraries? Is it possible?

I want to reduce my footprint, I'm want to know if I can remove the
common control libraries or if I can keep only one of the version?

Jonathan
 
JoP said:
Hi all!

I found that the component <Disk Drive> as a dependency upon the
component <Class Installer - Disk drives>. <Class Installer - Disk
drives> as a dependency upon <Class install library - storprop>. For
now it's okay. <Class install library - storprop> as a dependency upon
<Common File Dialogs>... why? <Commond File Dialogs> as dependency upon
the Common Control Libraries (v5,6...) components. So why there is a
link between the disk drive component and the common control
libraries???
Anybody as tried to run xpe in minlogon mode without the common control
libraries? Is it possible?

I want to reduce my footprint, I'm want to know if I can remove the
common control libraries or if I can keep only one of the version?

Jonathan
Click to expand...
When it comes to minimising your image, when you get to the stage of not
resolving dependencies, the best advice is, I'm afraid 'try it and see'
- it may not break anything you need to do, but it probably does break
something *someone* would want to do.
 
Until now I obtained a 40meg image with resolving all the dependencies
with auto-resolve dependencies. Now I will adopt your strategy Adora.
Will disable auto-resolve depencies. And remove the components I think
they aren't needed. I just tested removing the common control libraries
and it's working. FBA loading, minlogon console loading!!!

I removed the following component without doing a dependencies check :
Common Control Libraries Policy
Common Control Libraries Version 5
Common Control Libraries Version 6 [1.0.0.0]
Common Control Libraries Version 6 [1.0.10.0]
Common File Dialogs
 
JoP said:
Until now I obtained a 40meg image with resolving all the dependencies
with auto-resolve dependencies. Now I will adopt your strategy Adora.
Will disable auto-resolve depencies. And remove the components I think
they aren't needed. I just tested removing the common control libraries
and it's working. FBA loading, minlogon console loading!!!

I removed the following component without doing a dependencies check :
Common Control Libraries Policy
Common Control Libraries Version 5
Common Control Libraries Version 6 [1.0.0.0]
Common Control Libraries Version 6 [1.0.10.0]
Common File Dialogs
Click to expand...
The real test is: Does it still do all the things you need it to do?
If it does, I like to copy the section of the build log that has the
component sizes and sort it, then take out a couple of big ones that
look like I might not need them.
 
I thought the little FBA progress windows needed the common control
libraries but that is not the case. Also the minlogon launch a basic
CMD.exe window in fullscreen and it seems cmd doesn't need the common
control libraries to appear on screen.
My XPE image will only execute basic console command at startup to
reinitialize a system, formating, partitionning, ghosting, copying...
the applications I use for these tasks dont have any GUI, all console
mode. This is why I thought the common control libraries aren't needed
in my image. I will have to validate that theses applications dont have
any dependencies with the common control libraries. My configuration
contains less than 200 components, do you want me to past the build log
here? I've already located the big components, common control libraries
was a part of them. Will continue my investigation :)
JoP said:
Until now I obtained a 40meg image with resolving all the dependencies
with auto-resolve dependencies. Now I will adopt your strategy Adora.
Will disable auto-resolve depencies. And remove the components I think
they aren't needed. I just tested removing the common control libraries
and it's working. FBA loading, minlogon console loading!!!

I removed the following component without doing a dependencies check :
Common Control Libraries Policy
Common Control Libraries Version 5
Common Control Libraries Version 6 [1.0.0.0]
Common Control Libraries Version 6 [1.0.10.0]
Common File Dialogs
Click to expand...
The real test is: Does it still do all the things you need it to do?
If it does, I like to copy the section of the build log that has the
component sizes and sort it, then take out a couple of big ones that
look like I might not need them.
Click to expand...
 
JoP said:
I thought the little FBA progress windows needed the common control
libraries but that is not the case. Also the minlogon launch a basic
CMD.exe window in fullscreen and it seems cmd doesn't need the common
control libraries to appear on screen.
My XPE image will only execute basic console command at startup to
reinitialize a system, formating, partitionning, ghosting, copying...
the applications I use for these tasks dont have any GUI, all console
mode. This is why I thought the common control libraries aren't needed
in my image. I will have to validate that theses applications dont have
any dependencies with the common control libraries. My configuration
contains less than 200 components, do you want me to past the build log
here? I've already located the big components, common control libraries
was a part of them. Will continue my investigation :)
Click to expand...
A .sld for a very small image suitable for setting up a system via PXE
boot would probably be very popular if it were uploaded to xpefiles.com.
 
Ok I found another point. I was asking myself If I can get smaller
footprint with the Standard PC instead of the ACPI Uniprocessor PC I'm
currently using. I tried it, started a new configuration with standard
PC. I get a xpe image of 20meg with 130 components fully working... I
can type the command 'dir' in console!! :)

Looking at this new configuration, I see that the common control
libraries aren't required.
I found that I made a mistake previously saying that <Class Installer -
Disk drives> as a dependency upon <Class Install Library - Storprop>.
It is not true. So in my old configuration common control libraries
aren't required if I remove the storprop component.

Here is the build log of the Standard PC Configuration :

Starting run-time build at: 6/28/2006 12:28:51 PM...
Building: "Base Component [Version 5.1.2600.1106, R1507]"...
Building: "Class Installer - Computer [Version 5.1.2600.1106,
R1507]"...
Building: "Class Installer - Disk drives [Version 5.1.2600.1106,
R1507]"...
Building: "Class Installer - IDE ATA/ATAPI controllers [Version
5.1.2600.1106, R1507]"...
Building: "Class Installer - Keyboards [Version 5.1.2600.1106,
R1507]"...
Building: "Class Installer - Monitors [Version 5.1.2600.1106,
R1507]"...
Building: "Class Installer - Processors [Version 5.1.2600.1106,
R1507]"...
Building: "Class Installer - SCSI and RAID controllers [Version
5.1.2600.1106, R1507]"...
Building: "Class Installer - Storage volumes [Version 5.1.2600.1106,
R1507]"...
Building: "Class Installer - Stream [Version 5.1.2600, R620]"...
Building: "Class Installer - System devices [Version 5.1.2600.1106,
R1507]"...
Building: "Client / Server Runtime (Console) [Version 5.1.2600.1106,
R1507]"...
Building: "CMD - Windows Command Processor [Version 5.1.2600, R620]"...
Building: "CodePage: 10000 (MAC - Roman) [Version 5.1.2600, R620]"...
Building: "CodePage: 1252 (ANSI - Latin I) [Version 5.1.2600,
R620]"...
Building: "CodePage: 437 (OEM - United States) [Version 5.1.2600,
R620]"...
Building: "CoDevice Installer - Disk drives [Version 5.1.2600.1106,
R1507]"...
Building: "CoDevice Installer - IDE ATA/ATAPI controllers [Version
5.1.2600.1106, R1507]"...
Building: "CoDevice Installer - Keyboards [Version 5.1.2600.1106,
R1507]"...
Building: "CoDevice Installer - SCSI and RAID controllers [Version
5.1.2600.1106, R1507]"...
Building: "CoDevice Installer - System devices [Version 5.1.2600.1106,
R1507]"...
Building: "Command shell [Version 5.1.2600.1106, R1507]"...
Building: "Direct memory access controller [Version 5.1.2600, R620]"...
Building: "Disk drive [Version 5.1.2600, R620]"...
Building: "Disk Management Basic Volume Runtime [Version 5.1.2600,
R620]"...
Building: "Embedded Trust [Version 5.1.2600.1106, R1507]"...
Building: "English Language Support [Version 5.1.2600.1106, R1507]"...
Building: "English MUI Resource [Version 5.1.2600, R620]"...
Building: "Extended IO Bus [Version 5.1.2600, R620]"...
Building: "FAT [Version 5.1.2600.1106, R1507]"...
Building: "File system recognizer [Version 5.1.2600.1106, R1507]"...
Building: "First Boot Agent (FBA) [Version 5.1.2600.1106, R1507]"...
Building: "Font: Marlett [Version 5.1.2600, R620]"...
Building: "Fonts: EGA [Version 5.1.2600, R620]"...
Building: "Fonts: Fonts Microsoft_San_Serif [Version 5.1.2600,
R620]"...
Building: "Fonts: Fonts Tahoma [Version 5.1.2600.1106, R1507]"...
Building: "Fonts: Fonts tahoma_bold [Version 5.1.2600.1106, R1507]"...
Building: "Fonts: Western Europe font substitute [Version 5.1.2600,
R620]"...
Building: "Fonts:vgaoem_fon [Version 5.1.2600, R620]"...
Building: "Generic Bus [Version 5.1.2600, R620]"...
Building: "Group Policy Core - Support Files [Version 5.1.2600,
R620]"...
Building: "HID Keyboard Device [Version 5.1.2600, R620]"...
Building: "I/O Error Log Messages [Version 5.1.2600, R620]"...
Building: "Intel Microcode Update Driver [Version 5.1.2600, R620]"...
Building: "Intel(R) 82801 PCI Bridge - 244E [Version 5.1.2600.2180,
R2]"...
Building: "Intel(R) 82801GB LPC Interface Controller - 27B8 [Version
7.0.0.1014, R2]"...
Building: "Intel(R) 82801GB PCI Express Root Port - 27D0 [Version
7.0.0.1014, R2]"...
Building: "Intel(R) 82801GB PCI Express Root Port - 27D2 [Version
7.0.0.1014, R2]"...
Building: "Intel(R) 82801GB Serial ATA Storage Controllers - 27C0
[Version 7.0.0.1014, R2]"...
Building: "Intel(R) 82801GB SMBus Controller - 27DA [Version
7.0.0.1014, R2]"...
Building: "Intel(r) 82802 Firmware Hub Device [Version 5.1.2600,
R620]"...
Building: "Intel(R) 945G/GZ/P/PL PCI Express Root Port - 2771 [Version
7.2.2.1002, R4]"...
Building: "Intel(R) 945G/GZ/P/PL Processor to I/O Controller - 2770
[Version 7.2.2.1002, R4]"...
Building: "Keyboard Class Driver [Version 5.1.2600.1106, R1507]"...
Building: "Keyboard: United States English [Version 5.1.2600, R620]"...
Building: "Language: English (United States) - 0409 [Version 5.1.2600,
R620]"...
Building: "Microcode Update Device [Version 5.1.2600, R620]"...
Building: "Microsoft ACPI-Compliant System [Version 5.1.2600, R620]"...
Building: "Microsoft System Management BIOS Driver [Version
5.1.2600.2180, R2]"...
Building: "Microsoft Visual C++ Run Time [Version 5.1.2600.1106,
R1507]"...
Building: "Minlogon [Version 5.1.2600.1106, R1507]"...
Building: "Motherboard resources [Version 5.1.2600, R620]"...
Building: "Mount Manager [Version 5.1.2600.1106, R1507]"...
Building: "NLS: Core Files [Version 5.1.2600.1106, R1507]"...
Building: "NLS: Locale Map IDs [Version 5.1.2600, R620]"...
Building: "NLS: Time Zones [Version 5.1.2600, R621]"...
Building: "NPFS [Version 5.1.2600.1106, R1507]"...
Building: "NT Hardware Detect [Version 5.1.2600.1106, R1507]"...
Building: "NT Loader [Version 5.1.2600.1106, R1507]"...
Building: "Numeric data processor [Version 5.1.2600, R620]"...
Building: "Partition Manager [Version 5.1.2600.1106, R1507]"...
Building: "PCI bus [Version 5.1.2600, R620]"...
Building: "PCI standard ISA bridge [Version 5.1.2600, R620]"...
Building: "Plug and Play Monitor [Version 5.1.2600, R620]"...
Building: "Plug and Play Software Device Enumerator [Version 5.1.2600,
R620]"...
Building: "PnP (Kernel-mode) [Version 5.1.2600.1106, R1507]"...
Building: "Primary IDE Channel [Version 5.1.2600, R620]"...
Building: "Primitive: Dxapi.sys [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Dxg [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Dxgthk [Version 5.1.2600, R620]"...
Building: "Primitive: Hidparse.sys [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Imm32 [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Kdcom [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Ks.sys [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Mscms [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Msimg32 [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Ntdll [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Ole32 [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Pidgen [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Setupapi [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: SxS [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Userenv [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Version [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Winspool [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Winsta [Version 5.1.2600.1106, R1507]"...
Building: "Primitive: Wmilib [Version 5.1.2600.1106, R1507]"...
Building: "Processor [Version 5.1.2600, R620]"...
Building: "Programmable interrupt controller [Version 5.1.2600,
R620]"...
Building: "Regional and Language Options [Version 5.1.2600.1106,
R1507]"...
Building: "RPC Local Support [Version 5.1.2600.1106, R1507]"...
Building: "SCSI Port Driver [Version 5.1.2600.1106, R1507]"...
Building: "SCSI/RAID Host Controller [Version 5.1.2600, R620]"...
Building: "Secondary IDE Channel [Version 5.1.2600, R620]"...
Building: "Session Manager (Windows subsystem) [Version 5.1.2600.1106,
R1507]"...
Building: "Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
[Version 5.1.2600, R620]"...
Building: "Standard Dual Channel PCI IDE Controller [Version 5.1.2600,
R620]"...
Building: "Standard PC [Version 5.1.2600.1106, R1507]"...
Building: "System CMOS/real time clock [Version 5.1.2600, R620]"...
Building: "System timer [Version 5.1.2600, R620]"...
Building: "User Locale: English - Australia [Version 5.1.2600,
R621]"...
Building: "User Locale: English - Belize [Version 5.1.2600, R621]"...
Building: "User Locale: English - Canada [Version 5.1.2600, R621]"...
Building: "User Locale: English - Carribbean [Version 5.1.2600,
R621]"...
Building: "User Locale: English - Ireland [Version 5.1.2600, R621]"...
Building: "User Locale: English - Jamaica [Version 5.1.2600, R621]"...
Building: "User Locale: English - New Zealand [Version 5.1.2600,
R621]"...
Building: "User Locale: English - Phillippines [Version 5.1.2600,
R621]"...
Building: "User Locale: English - South Africa [Version 5.1.2600,
R621]"...
Building: "User Locale: English - Trinidad [Version 5.1.2600, R621]"...
Building: "User Locale: English - United Kingdom [Version 5.1.2600,
R621]"...
Building: "User Locale: English - United States [Version 5.1.2600,
R621]"...
Building: "User Locale: English - Zimbabwe [Version 5.1.2600, R621]"...
Building: "VGA Boot Driver [Version 5.1.2600.1106, R1507]"...
Building: "VGA Save [Version 5.1.2600.1106, R1507]"...
Building: "Win32 API - Advanced [Version 5.1.2600.1106, R1507]"...
Building: "Win32 API - GDI [Version 5.1.2600.1106, R1507]"...
Building: "Win32 API - Kernel [Version 5.1.2600.1106, R1507]"...
Building: "Win32 API - User [Version 5.1.2600.1106, R1507]"...
Building: "Windows subsystem [Version 5.1.2600.1106, R1507]"...
Building: "Windows XP Service Pack 1 Resource DLL [Version
5.1.2600.1106, R1507]"...

Some of the Intel component aren't in the xpe database when shipped. I
componentized some of them.

Do you know if there is a way to access the <Base component>? So we
will be able to start degisning a configuration directly from it, just
to see the capabilities...

Regards,
Jonathan
 
Is it possible that dependencies are differents when we have Standard
PC configuration instead of ACPI Uniprocessor PC configuration?
Because lots of dependencies I establish when I had my ACPI
Uniprocessor PC configuration are no more valid with the Standard PC
Configuration.
If it is the case, the dependency I stated about storprop is probably
not wrong...

For example, in the ACPI Uniprocessor PC configuration, the Windows
subsystem component had a dependency upon COM Server Registration
component. See log bellow:

Starting dependency auto-resolve at: 6/28/2006 12:54:02 PM...
Info 106: Adding component: "COM Server Registration [Version
5.1.2600.1106, R1507]", origin: "Windows subsystem [Version
5.1.2600.1106, R1507]"
Info 101: Initializing new component: "COM Server Registration
[Version 5.1.2600.1106, R1507]"
Info 101: Estimated footprint: 8192 Bytes

But in the Standard PC Configuration, the Windows subsystem is present
and the auto-resolve dependency dont detech that COM Server
Registration is required.

I'm trying to understand... it looks strange..

Regards,
Jonathan
 
JoP said:
Is it possible that dependencies are differents when we have Standard
PC configuration instead of ACPI Uniprocessor PC configuration?
Because lots of dependencies I establish when I had my ACPI
Uniprocessor PC configuration are no more valid with the Standard PC
Configuration.
If it is the case, the dependency I stated about storprop is probably
not wrong...

For example, in the ACPI Uniprocessor PC configuration, the Windows
subsystem component had a dependency upon COM Server Registration
component. See log bellow:
Click to expand...
Entirely possible. Personally, I need to be able to get the machines to
turn off remotely, so I need ACPI.
 
Standard PC Configuration : 129 components (20meg)
ACPI Uniprocessor PC Configuration : 174 components (35meg)

1 supplementary component for the Standard PC configuration :
Standard PC

45 supplementary components for the ACPI Uniprocessor PC configuration
:
ACPI Fixed Feature Button
ACPI Power Button
ACPI Thermal Zone
ACPI Uniprocessor PC
Active Template Library (ATL)
COM Base
COM Server Registration
Lightweight Directory Access Protocol (LDAP)
Local Security Authority Subsystem (LSASS)
Ole Automation
Primitive: AuthZ
Primitive: Crypt32
Primitive: Cryptdll
Primitive: Dnsapi
Primitive: Esent
Primitive: Icmp
Primitive: Imagehlp
Primitive: Ksecdd
Primitive: Mpr
Primitive: Msasn1
Primitive: Msctf
Primitive: Ncobjapi
Primitive: NetApi
Primitive: Netapi32
Primitive: Netrap
Primitive: Oleaut32
Primitive: Pstorsvc
Primitive: Regsvr32
Primitive: Rundll32
Primitive: Secur32
Primitive: Security
Primitive: Shell32
Primitive: Shlwapi
Primitive: Umpnpmgr
Primitive: Wldap32
Primitive: Ws2_32
Primitive: Ws2Help
Primitive: Wsock32
RPC Server
Security Accounts Manager Client
Security Accounts Manager Server Library
Service Control Manager (SCM)
Urlmon Library
Windows NT MARTA Provider
Windows Security Configuration Editor Engine

Currently I only have keyboard and monitor functionnality.
Will try to add USB as I needed.
 
I think I need PnP (User-mode) component in order for my USB stick to
be detected when xpe running. But, I've found that when you add the
component PnP (User-mode) new dependencies are created between
components. If you start from scratch and you don't have this component
in your configuration, go in options and desactive auto-resolve
dependencies. Insert PnP (User-mode) component, start a dependencies
check, you will see that lots of new dependencies appear.

Why these dependencies appear when the PnP (User-mode) component is
inserted?
 
Back
Top