Jump to content











Photo
- - - - -

Standard USB Keyboard and Mouse in VistaPE 12


  • Please log in to reply
38 replies to this topic

#1 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 13 January 2009 - 10:47 PM

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.

#2 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 13 January 2009 - 11:01 PM

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

#3 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 13 January 2009 - 11:27 PM

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.

#4 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 13 January 2009 - 11:42 PM

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

#5 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 14 January 2009 - 03:17 PM

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.

#6 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 14 January 2009 - 04:24 PM

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.

#7 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 14 January 2009 - 09:29 PM

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.

#8 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 15 January 2009 - 06:58 AM

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...

#9 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 15 January 2009 - 02:08 PM

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?

#10 Tim Pierce

Tim Pierce

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 16 January 2009 - 05:23 PM

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.

#11 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 17 January 2009 - 09:52 PM

Some notes Testing USB PNP

Explorer shell

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?

#12 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 18 January 2009 - 07:23 AM

could be and as i am rewriting the complete pnp process we will know sooner or later...

but i still think the key to the problem is here...someone who has this problem needs to do some tests..

http://www.boot-land...?...ost&p=55072

#13 nextgen-networks.de

nextgen-networks.de
  • Members
  • 5 posts
  •  
    Germany

Posted 18 January 2009 - 03:15 PM

Hi ctmag,

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!

Ralf

#14 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 18 January 2009 - 04:30 PM

OK, can you use the ct loader (posted here in the forum) and please mail me the zipped vpeldr.log which you can find in system32 after boot...i know it is trick without kbd/mouse...maybe you can do it with ultravnc as server, or some script that copiers it to hd some time after the system booted up...

#15 theGressier

theGressier
  • Members
  • 4 posts
  •  
    France

Posted 19 January 2009 - 08:41 AM

Hello,

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) .

Billy

#16 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 19 January 2009 - 10:10 AM

hmm, if i get you right, it is that adding the mentioned files solves this in any case (only USB cd drive problem are still there)

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...?

#17 theGressier

theGressier
  • Members
  • 4 posts
  •  
    France

Posted 19 January 2009 - 01:24 PM

Hi,

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 :
- infpub.dat
- infstor.dat
- infstrng.dat
- infcache.1
- drvindex.dat
- *.pnf
- 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
Billy

#18 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 19 January 2009 - 01:52 PM

i would bet on the fr-fr folder:-))

try restoring it...

#19 theGressier

theGressier
  • Members
  • 4 posts
  •  
    France

Posted 19 January 2009 - 03:00 PM

My last investigations :
- 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?

#20 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 19 January 2009 - 03:45 PM

does it mean driverstore and the dat files are needed but the other folders are not ? If so, this will help, of not, i really need to found out what the minimum set of files is that fixes the bug...as i do not have this bug, i depend on your help....

#21 theGressier

theGressier
  • Members
  • 4 posts
  •  
    France

Posted 20 January 2009 - 09:04 AM

I'm still searching which files are mandatory, I've rebuild a vistape 12 image with all in ram option and all integrated drivers. I'm know trying to add some files.

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?

#22 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 20 January 2009 - 09:41 AM

i do not know if the dat files can be built, maybe by peimg?

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.-))

#23 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 25 January 2009 - 01:21 PM

OK, i tried some things and this should work:

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

#24 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 25 January 2009 - 05:09 PM

Edited Never mind

END very end of script - Sorry this was my fault, builds fine

#25 Dave7

Dave7

    Frequent Member

  • Advanced user
  • 210 posts
  •  
    United States

Posted 26 January 2009 - 10:12 AM

Is "end of the script" the right place where to insert this? I added it at the end of the [AddDrivers] sections.

Dave




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users