use Minlogon

  • Thread starter Thread starter Andreas Drumbl
  • Start date Start date
A

Andreas Drumbl

Hi

I use minlogon in my image, but if I make the dependency
check it always install the windows logon (Standard)
component.

If I delete the windows logon (Standard) component and
repeat the dependency check it installs a
the component again.
I have a image with 180MB, is it impossible to use
minlogon if I have a size like this.

Or which components are depentend with windows logon
component?

I ignored the dependency check and deleted the component,
than I created the image and tried to boot. It seems
that there is no error. I didn't recognized a error in
the FBA.log as well.
Is there a risk that the image crashes during normal
operation?
 
Go to tools, options, dependency check and untick 'auto-resolve
dependencies'. This will mean that rather than just changing your build, it
will tell you what components want you to import what, it's up to you
whether you do or not.
My build has about 30 unresolved dependencies, and works just fine.
 
I have two minlogon builds.

One does not have any unresolved dependencies.
Other has one warning on component "Class Install Library - Netcfgx [..."
this components requires Core Networking. Resolving this add to image size
additional 8 MB.

Both my images are under 60 MB.

Disable Auto Resolve Dependencies.
And see what component requires WinLogon.
Then disable that component. And so on until you disable all component that
you don't require. (If you really don't need them).


Regards,
Slobodan
 
To add more to this.
If you want small image, don't use all components that are generated from
TAP result.
Use ONLY WHAT YOU NEED to support your project.

Adding even one extra component can result in many dependencies that you
probably don't need.

Slobodan Brcin said:
I have two minlogon builds.

One does not have any unresolved dependencies.
Other has one warning on component "Class Install Library - Netcfgx [..."
this components requires Core Networking. Resolving this add to image size
additional 8 MB.

Both my images are under 60 MB.

Disable Auto Resolve Dependencies.
And see what component requires WinLogon.
Then disable that component. And so on until you disable all component that
you don't require. (If you really don't need them).


Regards,
Slobodan

Andreas Drumbl said:
Hi

I use minlogon in my image, but if I make the dependency
check it always install the windows logon (Standard)
component.

If I delete the windows logon (Standard) component and
repeat the dependency check it installs a
the component again.
I have a image with 180MB, is it impossible to use
minlogon if I have a size like this.

Or which components are depentend with windows logon
component?

I ignored the dependency check and deleted the component,
than I created the image and tried to boot. It seems
that there is no error. I didn't recognized a error in
the FBA.log as well.
Is there a risk that the image crashes during normal
operation?
Click to expand...
Click to expand...
 
WinLogon will bring a lot of components into your image. You may need only
some of them.
Here is the short list of the components depended with WinLogon (first level
of the dependency check):

Component: WinLogon Sample Macro [Version 5.1.2600.1106, R1507]
Component.Dependencies(1): Programmable interrupt controller
Component.Dependencies(2): Processor
Component.Dependencies(3): PCI bus
Component.Dependencies(4): Numeric data processor
Component.Dependencies(5): Motherboard resources
Component.Dependencies(6): Direct memory access controller
Component.Dependencies(7): Min Kern Helper Mancro (NTFS) depends on NT
Loader
Component.Dependencies(8): Min Kern Helper Mancro (NTFS) depends on FAT
Component.Dependencies(9): New Component 1 depends on Primary IDE
Channel
Component.Dependencies(10): New Component 1 depends on Disk drive
Component.Dependencies(11): New Component 1 depends on Standard PC
Component.Dependencies(12): New Component 1 depends on Standard IDE/ESDI
Hard Disk Controller
Component.Dependencies(13): New Component 1 depends on PCI standard host
CPU bridge
Component.Dependencies(14): New Component 1 depends on PCI standard ISA
bridge
Component.Dependencies(15): New Component 1 depends on PCI standard
PCI-to-PCI bridge
Component.Dependencies(16): Min Kern Helper Macro (NTFS) depends on
Secondary IDE Channel
Component.Dependencies(17): MinLogon Helper Macro (FAT) depends on
English Language Support
Component.Dependencies(18): MinLogon Helper Macro (FAT) depends on
Session Manager (Windows subsystem)
Component.Dependencies(19): System timer
Component.Dependencies(20): System CMOS/real time clock
Component.Dependencies(21): System board
Component.Dependencies(22): Standard 101/102-Key or Microsoft Natural
PS/2 Keyboard
Component.Dependencies(23): WinLogon Helper Macro (NTFS) depends on
Windows Logon (Standard)
Component.Dependencies(24): WinLogon Helper Macro (NTFS) depends on
Explorer shell
Component.Dependencies(25): WinLogon Helper Macro (FAT) depends on FAT
Format
Component.Dependencies(26): WinLogon Helper Macro (NTFS) depends on
Standard PS/2 Port Mouse
Component.Dependencies(27): WinLogon Helper Macro depends on NTFS Format
Component.Dependencies(28): WinLogon Helper Macro depends on NTFS
Component.Resources: Empty collection

Dependency tree for: WinLogon Sample Macro [Version 5.1.2600.1106, R1507]
+-> Dependency: Programmable interrupt controller
| +-- Component: Programmable interrupt controller [Version 5.1.2600,
R620]
+-> Dependency: Processor
| +-- Component: Processor [Version 5.1.2600, R620]
+-> Dependency: PCI bus
| +-- Component: PCI bus [Version 5.1.2600, R620]
+-> Dependency: Numeric data processor
| +-- Component: Numeric data processor [Version 5.1.2600, R620]
+-> Dependency: Motherboard resources
| +-- Component: Motherboard resources [Version 5.1.2600, R620]
+-> Dependency: Direct memory access controller
| +-- Component: Direct memory access controller [Version 5.1.2600, R620]
+-> Dependency: Min Kern Helper Mancro (NTFS) depends on NT Loader
| +-- Component: NT Loader [Version 5.1.2600.1106, R1507]
+-> Dependency: Min Kern Helper Mancro (NTFS) depends on FAT
| +-- Component: FAT [Version 5.1.2600.1106, R1507]
+-> Dependency: New Component 1 depends on Primary IDE Channel
| +-- Component: Primary IDE Channel [Version 5.1.2600, R620]
+-> Dependency: New Component 1 depends on Disk drive
| +-- Missing dependency target: {1BC4A770-8284-4FCC-9DA1-BFEB589DABE2}
+-> Dependency: New Component 1 depends on Standard PC
| +-- Component: Standard PC [Version 5.1.2600.1106, R1507]
+-> Dependency: New Component 1 depends on Standard IDE/ESDI Hard Disk
Controller
| +-- Component: Standard IDE/ESDI Hard Disk Controller [Version 5.1.2600,
R620]
+-> Dependency: New Component 1 depends on PCI standard host CPU bridge
| +-- Component: PCI standard host CPU bridge [Version 5.1.2600, R620]
+-> Dependency: New Component 1 depends on PCI standard ISA bridge
| +-- Component: PCI standard ISA bridge [Version 5.1.2600, R620]
+-> Dependency: New Component 1 depends on PCI standard PCI-to-PCI bridge
| +-- Component: PCI standard PCI-to-PCI bridge [Version 5.1.2600, R620]
+-> Dependency: MinLogon Helper Macro (FAT) depends on English Language
Support
| +-- Component: English Language Support [Version 5.1.2600.1106, R1507]
+-> Dependency: MinLogon Helper Macro (FAT) depends on Session Manager
(Windows subsystem)
| +-- Component: Session Manager (Windows subsystem) [Version
5.1.2600.1106, R1507]
+-> Dependency: System timer
| +-- Component: System timer [Version 5.1.2600, R620]
+-> Dependency: System CMOS/real time clock
| +-- Component: System CMOS/real time clock [Version 5.1.2600, R620]
+-> Dependency: System board
| +-- Component: System board [Version 5.1.2600, R620]
+-> Dependency: Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| +-- Component: Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
[Version 5.1.2600, R620]
+-> Dependency: WinLogon Helper Macro (NTFS) depends on Windows Logon
(Standard)
| +-- Component: Windows Logon (Standard) [Version 5.1.2600.1106, R1507]
+-> Dependency: WinLogon Helper Macro (NTFS) depends on Explorer shell
| +-- Component: Explorer shell [Version 5.1.2600.1106, R1507]
+-> Dependency: WinLogon Helper Macro (FAT) depends on FAT Format
| +-- Component: FAT Format [Version 5.1.2600, R620]
+-> Dependency: WinLogon Helper Macro (NTFS) depends on Standard PS/2 Port
Mouse
| +-- Component: Standard PS/2 Port Mouse [Version 5.1.2600, R620]
+-> Dependency: WinLogon Helper Macro depends on NTFS Format
| +-- Component: NTFS Format [Version 5.1.2600, R620]
+-> Dependency: WinLogon Helper Macro depends on NTFS
| +-- Component: NTFS [Version 5.1.2600.1106, R1507]

I have a long list of the dependencies that includes the entire component
tree brought up by including the WinLogon. The file is a few megs, though.
If you need it, I can zip it and send you via email.

KM

AD> Hi

AD> I use minlogon in my image, but if I make the dependency check it
AD> always install the windows logon (Standard)
AD> component.

AD> If I delete the windows logon (Standard) component and repeat the
AD> dependency check it installs a the component again.
AD> I have a image with 180MB, is it impossible to use minlogon if I
AD> have a size like this.

AD> Or which components are depentend with windows logon component?

AD> I ignored the dependency check and deleted the component, than I
AD> created the image and tried to boot. It seems that there is no
AD> error. I didn't recognized a error in the FBA.log as well.
AD> Is there a risk that the image crashes during normal operation?

With best regards, KM. E-mail: (e-mail address removed)
 
You can also include windows logon and then disable all associated
files, resources and reg keys. This will fake the target designer and
the dependency check ends successfully.
 
Back
Top