How so I disable the welcome screen for Windows Logon (Standard)

[PeniWize]

Hello everyone,

I’m using Windows XP embedded with “Windows Logon (Standard)†instead of
minlogon. This is necessary due to some 3rd party software being used in the
image and I don’t have the option to not use “Windows Logon (Standard)â€, so
please don’t suggest this. I must use it or something else that logs me on
as Administrator. My problem is that using “Windows Logon (Standard)†shows
either the welcome screen or a logging on to windows dialog box. Is there
any way to disable this so that only a black screen (or something similar) is
shown? The welcome screen is inappropriate for an embedded device. I find
it difficult to believe that Windows XP _EMBEDDED_ does not have a way
quietly to boot up into the Administrator account. Am I wrong?

Thanks in advance.

 

[Sean Liming \(MVP\)]

Uncheck the two boxes in the Windows Logon (Standard) component's settings
tht enable the user friendly logon screens. This changes the logon to the
dialog box logon. Make sure automatic logon is setup.

Then set the following registry key to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system\DisableStatusMessage

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[PeniWize]

Thanks, Sean. That worked great, but now I have a blue background and a
mouse cursor that I need to change. What is the correct way to modify the
background color of the Administrator's profile and how do I hide the mouse
cursor by default?

Thanks!

 

[Sean Liming \(MVP\)]

For the back ground, change the wallpaper - make it anything you want. For
mouse, the old trick was to create a blank cursor ICON and set the mouse
pointer to the blank cursor. There might be other solutions if you do a
search.

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[PeniWize]

Hi Sean,

I tried setting HKCU\Control Panel\Colors\Background to “0 0 0†to change
the background color, but it doesn’t work. I assume this is because it’s
being changed in the same profile that FBA uses, which I assume is not the
one used by Administrator. What do I have to do to make my registry changes
affect the correct profile? Is there something I can do in an XPe component
or is there no way to know which sub-tree under HKEY_USERS is for
Administrator?

Thanks!

 

[Mike Warren]

I tried setting HKCU\Control Panel\Colors\Background to “0 0 0â€
to change the background color, but it doesn’t work. I assume this
is because it’s being changed in the same profile that FBA uses,
which I assume is not the one used by Administrator. What do I have
to do to make my registry changes affect the correct profile?

Try HKU\.DEFAULT\Control Panel\Colors

 

[PeniWize]

Hi Sean,

I tried changing both registry values for the background color and it didn't
work, but updating the mouse cursor did work so I investigated further and
discovered that the registry settings for the background color are not being
changed in registry of the final OS image, but the mouse cursor values are.

I have an XPe component that contains nothing but registry values for
"HKCU\Control Panel\Colors\Background" and "HKU\.DEFAULT\Control
Panel\Colors\Background" and each value has a build priority of 32767.
Wouldn't this cause FBA to set these values as late as possible in the
process? If so then wouldn't this also cause my settings to override the
blue background color, which I assume is set earlier on during FBA?

Thanks for the help.

 

[Sean Liming \(MVP\)]

Create a new component with the registry keys. Title the component with a
period (.) before the name. This will ensure that the registry keys are in
place.

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[Mike Warren]

Create a new component with the registry keys. Title the component
with a period (.) before the name. This will ensure that the registry
keys are in place.

Really? That explains why it works for me. All my custom components
are prefixed with #MW so the appear at the top of the list and I can
find them all easily.

 

[Sean Liming \(MVP\)]

It is an old trick. Components build in alphabetical order, unless build
order is setup. Being at the top, the component over rides any components
with similar registry settings.

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[PeniWize]

Hi Sean,

Renaming the component worked, but changing the build priority doesn't. It
may be because I'm using registry values instead of a custom FBA Command.

Thanks for the help!

 

[nickanuszczyk]

Sean,

When you refer to changing key to 1, what exactly do you mean?
I'm having the same problem, yet i cant figure it out.

nick