Standard USB Keyboard and Mouse in VistaPE 12
Posted 13 January 2009 - 10:47 PM
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
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.
Posted 13 January 2009 - 11:27 PM
Posted 13 January 2009 - 11:42 PM
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
Posted 14 January 2009 - 03:17 PM
Posted 14 January 2009 - 04:24 PM
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.
Posted 14 January 2009 - 09:29 PM
Posted 15 January 2009 - 06:58 AM
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...
Posted 15 January 2009 - 02:08 PM
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
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?
Posted 16 January 2009 - 05:23 PM
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.
Posted 17 January 2009 - 09:52 PM
When I watch PeLoader load during boot (easier in Vmware) and I see USB devices loading as one of the first events, then near the end it detects Human interface devices and adds usbport.inf.
My Wireless USB mouse installed during boot works fine. If I plug it in after boot it is detected as a USB receiver with a yellow exclamation point.
If some usb HD’s are pluged in at boot and unplugged after PE loads refreshing devices manager works and usb hard drive is no longer shown. If I plug it back in and rescanned in device manager it is listed correctly. (Same in my computer)
Could there be a problem with the order USB is loaded and detected?
Could it be USB Human Interface Devises not being detected or installed correctly?
Posted 18 January 2009 - 03:15 PM
I have the USB-HID detection problems on several systems and would like to test any beta to find a solution.
my affected systems:
DELL PowerEdge 2950 III Server with Intel 5000X Chipset (3 Servers all the same problem)
custom PC with ASUS P5K Premium - Intel P35 Chipset
Best regards and thank's for all your hard work!
Posted 18 January 2009 - 04:30 PM
Posted 19 January 2009 - 08:41 AM
I'm currently have the same problem on two system :
- dell 1950 with usb keyboard & mouse (from a kvm)
- ibm bladecenter with the integrated kvm
I'v done some research on this and I could give you these informations :
- With vistape 11, keyboard and mouse are working but the raid controllers aren't and I've to detect and install each drive and logical volume manually with takes a lot of time
- With waik 1.1, keyboard and mouse are working out of the box
- With vistape 12 build with waik 1.1 and ctloader, keyboard and mouse are not working. If I add the windows\inf and windows\system32\drivers and windows\system32\driverstore from waik boot.wim, keyboard and mouse work but there are still problems as my cdrom drive is connected in usb too (ibm bladecenter) .
- With vistape12 build with vista sp1 cd and ctloader, keyboard and mouse are not working (either with explorer, bsexplorer). If I add the windows\inf and windows\system32\drivers and windows\system32\driverstore from waik boot.wim, keyboard and mouse work but there are still problems as my cdrom drive is connected in usb too (ibm bladecenter) .
Posted 19 January 2009 - 10:10 AM
If so, i could try narrowing it down a bit...the cd drive problem may be adressed in a second step...
Could yo test if adding Windows\inf OR Windows\System32\drivers OR windows\swystem32\driverstore fixes this to...or are you sure all three are needed...?
Posted 19 January 2009 - 01:24 PM
I ran a new test : After adding the windows\inf and windows\system32\drivers and windows\system32\driverstore to have a working usb keyboard and mouse , I have deleted some files added in windows inf :
- BITS directory
- RemoteAccess directory
- fr_FR directory
and it is not working anymore...
I'm not sure that all three directory are needed, I will try to find which are required
Posted 19 January 2009 - 01:52 PM
try restoring it...
Posted 19 January 2009 - 03:00 PM
- driverstore directory is needed
- in windows\inf, .dat files are needed : infpub.dat, infstor.dat, infstrng.dat, drvindex.dat
I look to my old vistape 11 cd, and I found theses files were in the boot.wim
Is that enough to let you find the problem in vistape 12?
Posted 19 January 2009 - 03:45 PM
Posted 20 January 2009 - 09:04 AM
Could somebody tell me if I should copy the .dat files from vista disk or if these files can be built depending on the inf files you put inf the windows\inf directory.
Second question: does somebody know why the driverstore directory is no more present in vistape12?
Posted 20 January 2009 - 09:41 AM
Nightman removes a lot of file to slim down vistape...while doing this he sometimes removed too much...no we have to find out what to add.-))
Posted 25 January 2009 - 01:21 PM
add the following lines at the end of the [Process] section of 04-additional.script
DirCopy,"%BootSRC%\Windows\inf","%TargetDir%\Windows" DirCopy,"%BootSRC%\Windows\system32\drivers","%TargetDir%\Windows\system32" DirCopy,"%BootSRC%\Windows\system32\driverstore","%TargetDir%\Windows\system32" FileDelete,"%TargetDir%\Windows\inf\*.pnf" DirDelete,"%TargetDir%\Windows\inf\BITS" DirDelete,"%TargetDir%\Windows\inf\RemoteAccess"
it will need some more space on the disc and also in RAM, but it fixes the USB Mouse/Keyboard issue and it also fixes a bug where when you booted from an USB drive the USB drive was not visible (only the X drive was visisble..)
Please report if it works for you...thanks !
Edit: Added info to make clearer
Posted 25 January 2009 - 05:09 PM
END very end of script - Sorry this was my fault, builds fine
Posted 26 January 2009 - 10:12 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users