Re: [CLSD] DP_HID_wnt5_x86-32_90204

Well it may end up being necessary to break driver signing, which of course would necessitate the end user enable the option to ignore driver signing.  It does not look as though there will be a perfect solution.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Since all of the Logitech PS/2 stuff seemed to be confined to two .inf files, I just removed those files and the associated .sys and .cat files.  This is mainly meant to be a temporary solution to allow installs to work until I can figure something else out.

Post #1 download link updated.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I have a probleme with this pack


i have keybord error at driverpack finisher ans it say tthat can' replacer newet file for my PS2 keyboard.....

Last edited by abdou (2008-10-29 10:59:49)

Re: [CLSD] DP_HID_wnt5_x86-32_90204

_____

     I have a probleme with this pack


     i have keybord error at driverpack finisher ans it say tthat can' replacer newet file for my PS2 keyboard.....

_____


I have the exact same problem here with my last installs.

Thanks for the very good work.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I've now used the latest version, 81027, on two Dell laptops, a Sony VAIO laptop, an HP desktop, an OptiPlex 755, and VMware - all with no problems.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Thank you for this pack, RougeSpear.
Unfortunately, it breaks keyboard and mouse support at OOBE.
Windows installation goes fine, but after it finishes and restarts the problem begins; At OOBE, after you press a key you can no
longer press other keys, nor move the mouse cursor. You can, however, move the mouse cursor unless you press any key.
Again, while in windows setup to problem does NOT occurs.
I have a USB keyboard and mouse, so I didn't try and use PS/2 ports to see if something is related to USB.
Moreover, I don't know if the problem only persists at OOBE. Maybe OOBE is not related, maybe it does.

Note: This was tested ONLY in a virtual machine (VirtualBox).

Edit: Hmm... strange. Unchanging your change log at the first post distracted me from seeing that there is a newer version.
I will try the latest version (81027) and post my results.

2nd Edit: Well, the newer version if just fine. Thank you very much.
You better change the change log. It can cause confusion to others, too.
Thanks again. smile

Last edited by Oron123 (2008-11-19 06:13:44)

An advice for life: Do not argue with people who have no knowledge.
They aren't aware of what they say/write and will drag you down to their level.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

RougeSpear, after few tests I found out that there is a problem for people with Logitech mouse, like G5.
After integrating this pack there is that old problem that Chad wrote on version 7.09.23.
By the way, check the "KHALMNPR.exe" file. It seems corrupt. Maybe this is the problem.

An advice for life: Do not argue with people who have no knowledge.
They aren't aware of what they say/write and will drag you down to their level.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Thx for reporting the issue Oron123, since RogueSpear is very busy and he might not have the hardware to reproduce your issue, so I suggest you download the last logitech driver and compare the md5 of "KHALMNPR.exe". Then you would know if it's corrupted or newer. Remember that no one of us get paid to do this and we always appreciate help.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Oron123 wrote:

By the way, check the "KHALMNPR.exe" file. It seems corrupt. Maybe this is the problem.

Thank you specifying the file and some details.  That should make what I have to do much easier.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

No problem, JakeLD.
I know none of you get paid, that's why I appreciate your doing so much.

RougeSpear, I was only trying to help. You don't have to be so cynical.
The file "KHALMNPR.exe" on the HID pack gives an error telling it's not a valid Win32 application.
I did compare the hashes of the two files; from the HID pack and from the Logitech installation file.
They were different and that is why I knew these two files were not the same.
The DriverPacked file's MD5 hash is: 1E9987B72F1522424C8001CC557834B0
The Logitech file's MD5 hash is: 19E0D28FE38F55CA4C63F77D3657959A
I also checked all other files from the "LS" directory from the HID pack to see if more files don't have the same hash.
I found that in addition to the mismatched hash of the file "KHALMNPR.exe", these files have mismatched hash too:

LBeepKE.sys, LHidFilt.sys, LMouFilt.sys, LUsbFilt.sys, WdfCoInstaller01005.dll

Edit: Forgot to write the "KHALMNPR.exe" hash.

Last edited by Oron123 (2008-12-02 07:17:28)

An advice for life: Do not argue with people who have no knowledge.
They aren't aware of what they say/write and will drag you down to their level.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Oron123 wrote:

RougeSpear, I was only trying to help. You don't have to be so cynical.

Sometimes the written word can get misunderstood on these forums.  I wasn't cynical at all.  I literally was thankful that you pointed out the specific file for me.  Most of the time I get stuff like "it doesn't work".  Like that's supposed to be helpful to me.  By pointing out the file you saved me the time, effort, and aggravation of having to pinpoint the problem myself.  Anyway, I've made the same mistake myself several times where I've taken what someone wrote entirely wrong.  When there's no tone of voice or body language to observe it can be tough to tell if someone is being considerate or being a jerk.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I'm happy to know that you were thankful.
Sorry for thinking the other way around. smile
If only you knew how much time you saved me. I really do appreciate your work.
It's a shame not all know how hard and frustrating this all stuff can get, and above all not getting any payment.
Maybe the feedback isn't given at all time, but I assure you many people, including me, thank you behind your back.

An advice for life: Do not argue with people who have no knowledge.
They aren't aware of what they say/write and will drag you down to their level.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Hi
today I noticed that the VMware mouse driver was installed in 'live metal' test in XP. (on a 'el cheapo' asus P5M2E low feature "server" mobo).

The asus mobo has no sound on board and no sound card.
And, windows XP installs standard sound stuff none the less.
Life is fun.
Anyway. HID like mice and keyb are important, and while the mouse works with the VM driver, it struck me as 'very" odd that XP had not used the M$ driver.

edit>
I tried look up what version DriverPack Chipset I used, but I find no names..
Well, this was done with a super short path method one DVD I saved as ISO around June 2008.
(was in a hurry to get that thing running and used an older build.)

----------
@ the team.
I will try put in time and will attempt to collect data from the current Third Party DriverPacks and released main DriverPacks (and the latest main DP nightlies) and can (I hope) do some worthwhile work in excel.

Nobody likes conflicts, and sound/modem/TV/Graphics with HDMI, have sound.
I saw that an excel sheet was left in Third Party DriverPack modem. (with the hilite formula in it.)
This gave me the idea to do more of this.

Last edited by Jaak (2008-12-02 13:55:45)

The answer was 42?
Kind regards, Jaak.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Logitech G5 Laser gets the yellow exclamation point in device manager with current HID pack. Noticed the driver provided is 4.60, setpoint for this mouse is now at v4.70. I'll try the new driver to see if that fixes.

=============
Input Devices
=============
HID\VID_045E&PID_00B4&MI_00\7&2E835FE5&0&0000               : HID Keyboard Device
HID\VID_045E&PID_00B4&MI_01&COL01\7&AAC2223&0&0000          : HID-compliant consumer control device
HID\VID_045E&PID_00B4&MI_01&COL02\7&AAC2223&0&0001          : HID-compliant device
HID\VID_046D&PID_C049&MI_00\7&1693DD53&0&0000               : Logitech HID-compliant G5 Laser Mouse
HID\VID_046D&PID_C049&MI_01&COL01\7&363C115&0&0000          : HID-compliant device
HID\VID_046D&PID_C049&MI_01&COL02\7&363C115&0&0001          : HID-compliant device
6 matching device(s) found.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Fragbert wrote:

Logitech G5 Laser gets the yellow exclamation point in device manager with current HID pack. Noticed the driver provided is 4.60, setpoint for this mouse is now at v4.70. I'll try the new driver to see if that fixes.

=============
Input Devices
=============
HID\VID_045E&PID_00B4&MI_00\7&2E835FE5&0&0000               : HID Keyboard Device
HID\VID_045E&PID_00B4&MI_01&COL01\7&AAC2223&0&0000          : HID-compliant consumer control device
HID\VID_045E&PID_00B4&MI_01&COL02\7&AAC2223&0&0001          : HID-compliant device
HID\VID_046D&PID_C049&MI_00\7&1693DD53&0&0000               : Logitech HID-compliant G5 Laser Mouse
HID\VID_046D&PID_C049&MI_01&COL01\7&363C115&0&0000          : HID-compliant device
HID\VID_046D&PID_C049&MI_01&COL02\7&363C115&0&0001          : HID-compliant device
6 matching device(s) found.

Update: v4.70 fixes issue for the G5 mouse, but dell branded logitech mice now go yellow. Logitech hardware seem very picky on drivers in this pack.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I rolled back to v3.6 (about a year ago or more?) due to problems with Dell branded logitech mice, which got over this issue, any newer driver got yellow exclam. [In fact in the end I used my own pack with the logitech part completely removed as the logitech driver made plugging mouse into a different usb port take ages to recognise.]

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I wonder if it's really worth it to have a HID pack that covers mice that otherwise can work fine with MS supplied generic HID drivers? The touchpad stuff is definitely useful, but what a pain dealing with yellow devices on simple mice...

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Well, certain mice, while working fine with the default MS provided driver, feature enhanced capabilities that go beyond the scope of RMB, LMB, MMB and scroll wheel.
For these, you may need to use a special driver.
For instance, mine has a DPI quick selection button that can increase or decerase the sensitinity on the fly.
It's pretty useful because usually, I like a high responsiveness so I can traverse desktops faster, however, when using an image manipulating app, I want absolute precision and not have it skip a pixel so I turn it down then.
Pretty convenient if you switch often.

Of course, you won't notice any difference with some ordinary €15 mouse, so you may want to cut out on this pack.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I alway thought that you needed vendor specific drivers for the reasons you state above - however my G9 uses the generic and all the default buttons work with generic, plus the dpi adjustment - and get this, with the latest mouseware (at least for the G9), the default install routine uses the generic MS driver! You have to manually select to insist on using the logitech driver.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Hm, now that you mention it...

I never really tried w/o the special driver on my Habu, as I included it in my personal DP.
When I got the mouse, I installed the software immediately, only to find it too bloated and fancy.
So I just grabbed the driver files and included them on my install disc.

Guess I'll have to try w/o them to find out, however, using just the drivers files and no useless GUI, I can see no negative side-effects.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

dpi stuff works on my mx518 with no additional drivers

47

Re: [CLSD] DP_HID_wnt5_x86-32_90204

Can support for the following be added.

IBM/Lenovo ThinkPad UltraNav and TrackPoint

http://www-307.ibm.com/pc/support/site. … MIGR-42487

http://www-307.ibm.com/pc/support/site. … MIGR-66893

http://www-307.ibm.com/pc/support/site. … MIGR-70478

http://www-307.ibm.com/pc/support/site. … MIGR-70010

http://www-307.ibm.com/pc/support/site. … MIGR-68000

http://www-307.ibm.com/pc/support/site. … MIGR-67226

http://www-307.ibm.com/pc/support/site. … MIGR-42489

http://www-307.ibm.com/pc/support/site. … IGR-4Z9QVD

Game controllers

PS3 SIXAXIS Controller
PS2 Controller via USB adapter
Wii Controllers

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I'll implement as much updates and fixes as I can this week.  Finally have a fleeting chance this week....

Re: [CLSD] DP_HID_wnt5_x86-32_90204

I downloaded all of these.  It's going to take a little while to go through them however.  Most seem like custom Synaptics packages.  I'm beginning to wonder if we should just start to break driver signing, where needed, in order to get the best distribution per workstation.  It would be a fair amount of work to keep track of all that I'm guessing.

Ra wrote:

PS3 SIXAXIS Controller
PS2 Controller via USB adapter
Wii Controllers

If you have links I'll take a look, but I'm probably not going to go and hunt these down.

Re: [CLSD] DP_HID_wnt5_x86-32_90204

20090122 - Updated

9.01.22 - RogueSpear

Added
- \F2 Fujitsu USB TouchPanel HID Driver V1.0.0.1 [20070301]
Changed
- \P changed to \F1
Updated
- \F1 Fujitsu PS2 Touchpad from V2.0.4.2002 [20031108] to V2.2.4.20006 [20060801]
- \LS Logitech Setpoint from V4.60.42 [20080229] to V4.70.165 [20080926]