DriverPacks.net Forum - [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2008-06-07T17:53:10Z

Jake/Jaak, do you have any interest in updating this driverpack? If so, would you consider adding the Wacom TabletPC driver for XP?

Thanks in advance!

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-10-28T02:08:52Z

hi,
it looks like this one was considered stable?
The sticky was not updated yet, and you are at.
(MD5 Hash: 3522d465acf3559dd527a2d3e5557dd6 DP_Input_wnt5_x86-32_070923.7z)

(I'll prepare a txt for twig123, so he can update that sticky.)

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-28T20:33:11Z

Just an update... I tried using this on a Dell Inspiron 1100 laptop that has a Synaptics Touchpad, but it got detected as "Microsoft PS/2 Port Mouse (IntelliPoint)".

It's HWID is:

ACPI\PNP0F13\4&2A083901&0

Sadly, it was the sole reason I tried the DP. Go figure.

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-23T10:59:23Z

I have taken the liberty of rolling back the non-working setpoint V4 driver to previous v3.10, now on server

-update-
Now everything works again

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-22T04:57:21Z

I believe the reason you are having this issue has to do with how mouse drivers in Windows work. If you are unaware, there can only be one mouse driver loaded at a time.

I used to try to directly integrate Synaptics drivers into my Sysprep'ed Ghost image for the school district I work at because of the laptops we have, but I found it tried to load the Synaptics drivers for everything, including desktop machines using Microsoft, Logitech, etc mice. So I started digging through the INFs and found that the way Synaptics drivers work, they are assuming it is going to be a touchpad on a laptop in which case there is a strong possibility of someone adding another pointer device (i.e. mouse) to the computer via USB. So how do you make it work if only one driver can be loaded at a time? Make your driver include a catch-all. The Synaptics drivers install for everything and has generic support for all USB mice added as well.

So people that are using this DP are getting Synaptics drivers loaded for their non-Synaptics touchpads and mice causing problems. Although it provides generic support, it apparently only works on additional devices added, not on the primary.

So what was my solution for my school district? I'm sort of embarassed to admit this, but to get the drivers to work the best without having to manually load the drivers on every machine, I just made a copy of the image file and included the Synaptics drivers to this image and called it my "laptop" image. So I have about 1.5gb taken up on my server because of touchpad drivers. Yeah, I'm sure I could just set up Ghost to install the drivers by copying the installer and running it with a switch to make it silent... and I probably should. *sigh* But it wasn't the first thing to come to mind.

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-17T14:25:06Z

V4 driver dont work.....this is the exact same mouse on each pc(Dell rebranded Logitech)

GX745 V3.1.0.0 - works fine
USB\VID_046D&PID_C016\5&18E0A94F&0&2 [corded optical wheel mouse, under HID devices]
USB\VID_413C&PID_2101&MI_00\6&5E51BFE&0&0000 [USB human interface device, under HID devices]
HID\VID_046D&PID_C016\6&1A600EB3&0&0000 [ HID-compliant optical wheeel mouse, under mice and other poitning devices]

GX150 V4 - not work
USB\VID_046D&PID_C016\5&35B73D88&0&2

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-16T01:27:14Z

does going back to DP_Input_wnt5_x86-32_070113.7z fix this issue?

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-14T17:45:39Z

eethball: its an issue with Dell USB corded optical mouse (rebadged Logitech) - I seem to recall having the issue last week with an older pack (that had the file) and it just said the device couldn't start and so didn't work. I got it working in the end by forcing it to be a regular HID device and using the MS driver.

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-14T14:27:32Z

Chud, what input driver does your mouse or touchpad use? Because if it's not the Logitech SetPoint driver than the issue is much bigger than just missing files...Windows can't select which driver to load because of the overlapping hwids.

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-14T13:41:46Z

JakeLD, maybe it's possible to make fix via ini-file for common hwids? To detect device we are may to use a subsys hwids.

Edit:
I meant to detect device by *&SUBSYS_*xxxx of any device in laptop, where an xxxx is vendor ID of vendor of laptop. But it will be difficult to define what models of laptops uses those or others touchpads.

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-14T12:18:55Z

Pack V7.09.08 - Getting error with missing file "WdfCoInstaller01005.dll" from

d\3\in\l\s

why has this file been removed, its referenced in the SourceDisksFiles entries ??

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-14T03:52:38Z

If you take the out the common hwids from these drivers won't Windows just load the generic PS/2 driver or whatever, which would defeat the whole purpose of having Touchpad drivers in the driverpack?

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-12T18:12:10Z

Yes, i'm pretty sure it's the issue. The thing is almost all drivers use that specific HWID so many INF needs to be edited. Plus I think windows drivers can handle ACPI\PNP0303 & ACPI\PNP0F13 without added drivers. Work in porgress.....

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-12T17:45:58Z

JakeLD, many of touchpad drivers have a same hwid - ACPI\PNP0303... Therefore Windows installs a random driver... Can be it is necessary to delete common hwid in driver's infs?

Re: [REL] [x86, 32 bit] DP_Input_wnt5_x86-32_070905

2007-09-12T16:02:29Z

It also broke my laptops keyboard. I plugged in a USB keyboard and mouse just so I could function, but I loaded the Synaptics driver off of Gateway's site, and then had to manually set the unknown device under keyboards to the Standard 101/102-Key or Microsoft Natural PS/2 Keyboard before that would function again. When doing that I received a warning saying that the keyboard driver was also connected to the Mouse or something, but I continued anyways and then both were working. I tried running the save_hwids.exe on my laptop and my desktop and it only showed the PCI Devices and the USB Devices. So I went to device manger and found the following ids.

Keyboard

ACPI\PNP0303\4&1D6F7EAE&0 : Standard 101/102-Key or Microsoft Natural Keyboard

Touchpad
ACPI\PNP0F13\4&1D6F7EAE&0 : Synaptics PS/2 Pointing Device

Hope this helps in troubleshooting.