Windows XPe and Keyboard problem

[Guest]

Hi.

I'm building a Digital Pciture Frame out of an old Dell Inspiron 7500
laptop. I've built an image based on the "WinLogon Sample Macro" component.
I've allso added the "Generic USB Input Device Support" component to the
image.

The image builds with no errors, and the system boots up. Once XP is loaded
i try to logon, but the keyboard isn't working. I've tryed connecting it
using USB and PS/2 (it's a wireless Microsoft keyboard, so i can either
connect using USB, or use the PS/2 connection).

I know that the keyboard is working since i can hit "ESC" and enter bios
setup before XPe is loaded.

I've read some past post on this forum about people with the same problem,
but i havent found a solution.

-Jonas

 

[Slobodan Brcin \(eMVP\)]

Jonas,

If your USB drivers are working then try adding:
"HID Keyboard Device"

Regards,
Slobodan

 

[Guest]

Hi.

By adding the "Generic USB Input Device Support" component, the "HID
Keyboard Device" get's added as well.

The strange thing is that the keyboard isn't working as a PS/2 keyboard.
There is obvious a connection between the Keyboard and the RF reciver, since
i can access the BIOS setup. So, the strang thing is that it isn't working
once XPe is loaded.

The RF-reciver is allso drawing power from the computer, since if i hit the
"F-lock" button on the Microsoft keyboard, the F-lock led lights up on the
reciver.

 

[Slobodan Brcin \(eMVP\)]

Hi Jonas,

Try adding "MinLogon Sample Macro" to empty project and then resolve all
dependencies.

Try this image it should work. Also have you tried Win XPP?

Regards,
Slobodan

 

[KM]

Jonas,

Do you have "Class Installer - Keyboards" in the configuration?

KM

 

[Slobodan Brcin \(eMVP\)]

Konstantin,

Both "Standard 101/102-Key or Microsoft Natural PS/2 Keyboard" and "Class
Installer - Keyboards" have direct dependency to this component.

Regards,
Slobodan

 

[KM]

Slobodan,

Yup. The "Standard 101/102-Key or Microsoft Natural PS/2 Keyboard" does depend on the "Device: Keyboard" which depends on the
keyboards class installer. The same for "Generic USB Input Device Support"/"HID Keyboard Device".

But this is all there only if the Autoresolve depedencies option was turned on.

I guess we should ask for SetupApi.log.

Konstantin

 

[Guest]

I have the following keyboard related components in my configuration:

- Class Installers / Hardware Compatibility
- Generic USB Input Device Support
- HID Keyboard Device
- HID-compliant consumer control device
- HID-compliant mouse
- Microsoft Internet Keyboard Composite Device
- Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
- Standard PS/2 Port Mouse
- WinLogon Sample Macro
- USB Human Interface Device

If you're interested i could upload log files. This is the first time I'm
using Windows XPe, so you would have to tell me where to find those files.

 

[Guest]

My log file can be downloaded at http://jonas.greit.no/smartframe2.txt
Save it to disk to view it, unless the line breaking get all messed up.

Thanks.

 

[Guest]

Wee! It's finally working!

I think the "Class Installers / Hardware Compatibility" did the trick

 

[Slobodan Brcin \(eMVP\)]

Hi Jonas,

We usually never ask for project files logs, but nevertheless according to
components that you have used it must work, I'm still wondering why it did
not work.
It would be nice if you could figure out what component/registry entries
were added to make this work finally.

fba.log and setup api log can bee found in post FBA windows folders of XPe.
These tell you what PnP and FBA did and what errors they encountered from
these we can sometimes pinpoint various problems.
Log that you gave us usually only tell what components you have in project
so that we do not ask you stupid guess question that me and Konstantin did.
Like do you have this or that component and whether you have auto
dependencies on/off.

Also you can use public news server: news.microsoft.com from Outlook express
for easy access to this NG and for posting attachments (just zip them).

Regards,
Slobodan

 

[KM]

Jonas,

Definitely you were missing some of the class installers.
In case you still want to know that, the log file you wanted to send us is \Windows\Setupapi.log from your runtime (not the build
log).