Standard USB Keyboard and Mouse in VistaPE 12 External links Options

[e2p2]

I have seen this mentioned in a number of threads. Since I have run into this problem my self I thought I would see if anyone has made any progress on this issue. I am trying to run VistaPE 12 on a Dell Poweredge R300. This system does not have PS/2 ports. This limits me to using a standard USB keyboard and mouse. I have tried a number of solutions suggested in other threads but none have worked.

What I have tried:
Wired USB Keyboard and Mouse
Wired PS/2 Keyboard and Mouse through a PS/2 to USB adapter
Building with Vista SP0
Building with Vista SP1
Building with Windows Server 2008
Using C'T VPELDR
AutoStarting HWPNP

Nothing has worked so far. Given that I can not directly connect a PS/2 Keyboard or Mouse to this system any assistance would be greatly appreciated.

[PaPeuser]

Hello
I have had luck with a Logitech wireless USB mouse as in this post, i dont have a working USB Keyboard to test

Realtime USB Suport


VistaPE 12
Vista Ultimate SP0
Not CT's Loader

[e2p2]

Your referenced post mentions FBWF and Ramdisk set at a percentage. Are you using a specific plugin for that, I do not see it anywhere in my environment.

[PaPeuser]

Hi Again

In winbuilder window (before you build) in left Tree view under VistaPE 12 (RC1) you have folders

Base\Basic configuration you can set your FBWF cache size

Addons\ImDisk Ramdisk for VistaPE you can set ramdisk capacity

Most but not all scripts have options you can select or not
Most default setting are fine, some APP scripts ask to have at FBWF 128,

This has worked for me Good Luck

[e2p2]

Though I have been through most of the scripts I had missed the one with the FBWF cache. I will try setting it to 128. I am using the option to run all programs from RAM, so I had the Ramdisk disabled.

[PaPeuser]

Hi
There are lots of options and some work better with different setups. I never tried this with the Run from Ram option checked.

I wanted to let you know what work for me,

Let us know how you make out.

[e2p2]

Well I tried increasing the FBWF and the Ramdisk. Neither allow my wired USB keyboard and mouse to work. My plug and play is and has been working. One thing to note. I can bring this build up in VMWare and everything is fine, mouse and keyboard work. But when I bring it up on the Poweredge not only does the keyboard and mouse not work, but I do not have a mouse cursor on the screen.

[ctmag]

I am investigation this for a long time, and i believe it has to do woth the way the files are stored in the cd or inside the wim file.

Please try to only add basic tools (remove all apps) and see if it works

if still not, try using dircet from cd instead of "from ram" (the wim file) for booting

or put some large (200MB?) file in the custom folder so that it is added to the disc...

please report of anything helped...thanks...

[PaPeuser]

Hello
I just downloaded WB 6 to a clean folder and D|L Vista Beta from servers in WB
Most settings before build are default; I did set FBWF to 128 and Ram at 70%

Vista Ulit SP0 and WAIK 1.1 both are selected and available
Extended PNP is checked before build (default)
Explorer Shell is default
Test Machine has 1 gig Ram and USB is VIA

USB
Ext Hard Drive
Sony Handy Cam
Wireless USB mouse was detected and installed and listed as Human Interface Devices –USB Receiver
All where detected and installed correctly
Wireless mouse work at boot up and wile PEloader ran Extended PNP?

Can I add anything else?

[Tim Pierce]

I am also running into issues with USB keyboards. Any PS2 wired keyboard works fine, as do any Laptop integrated keyboards. Under VistaPE 12 RC1, I have aobut a 1 in 3 chance of getting a USB keyboard to work properly on boot, with the same disk on the same machine. VistaPE 11 worked fine, and the drivers and utilities I am running were approximatly the same.

I've noticed that under device manager when they keyboard does not detect properly, it shows up as a "Microsoft Intellitype keyboard" with an error, and under properties it claims to be missing a driver. I get the same result regardless of which USB keyboard I use, be it microsoft, Logitech, or even one old USB viewsonic keyboard we have laying around.

I have not tried adding intellitype drivers to my driver folder yet. That will be my next workaround attempt.

The issue seems to affect any Intel chipset based board. My few Nvidia chipset boards seem to recognize the keyboard without problems.

Any insight anyone can offer into how to fix this would be greatly appriciated.