Search options (Page 1 of 155)

Well, doing some research into WMIC I found the following tidbit works to identify notebooks.

WMIC SystemEnclosure GET ChassisTypes /value

On a notebook the output would be "ChassisTypes={10}" but on anything else the value would be blank.  Once the target machine is identified as a notebook, further filtering can be applied.

Ref: http://technet.microsoft.com/en-us/libr … 80825.aspx

Hmm, I wonder if we could do something similar by polling WMIC on the target system.

<goes off to play in the sandbox...>

I haven't even SEEN a Pentium 1 in over 10 years!  Get some new(er) hardware!

Yup, source is suspect if DriverPacks BASE is already detecting a prior (broken) method-2 integration.

We don't support Windows XP x64
http://forum.driverpacks.net/viewtopic.php?id=2651

Thanks cdob!  I had forgotten about that.

Change your "for %%i" line to read as follows and it WILL work:

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF /I EXIST %%i:\sources\install.wim SET "CDROM=%%i:"

The main difference is the inclusion of "IF /I", the /I makes the query case-insensitive meaning that "BlAh" is the same as "blah".  Also get in the habit of enclosing your SET variables in quotes to eliminate stray spaces.
I know this works because I use the exact same line in my .cmd.

I always use IF /I EXIST unless I'm looking for a very specific case-spelling.

Well, adding the text file to the DriverPacks and adding code to support that function was just a proof of concept.  It still needs further testing before we re-release new DriverPacks with the "known-problems*" file (not all DriverPacks will need it).
This current version of SAD will work fine if those files are not present (IF EXIST...).
I'm glad it worked for you!  Whew!

If you don't want to wait for my HID testpack uploads, you can make your own by creating a text file inside the \D\ folder (NT5) or in the root of the .7z archive (NT6) using the following format:

Known-problems-{name_of_dps}.txt

; The following drivers are known to cause problems during automatic integration.
; If your device is not installed during automatic installation, you can try these folders manually.
x64\All\3\Touchpad_Mouse\Alps\2\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Alps\3\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Alps\4\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Alps\5\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Elantech\1\ETD.inf
x64\All\3\Touchpad_Mouse\Elantech\2\ETD.inf
x64\All\3\Touchpad_Mouse\Elantech\3\ETD.inf
x64\All\3\Touchpad_Mouse\Cypress\1\cykbfltr.inf
x64\All\3\Touchpad_Mouse\Cypress\1\cymfltr.inf

Well, I had a setback tonight.  I burned out one drive in my RAID-1 array.
So I'm down until the array has rebuilt itself.
Good thing I follow the 3-2-1 backup rules:
3 copies of critical data
2 copies on different media types (Hard drive, cloud storage, DVD, etc.)
1 copy stored off-site (mom's house)

I'll be back in the next day or so.

Here is the code in my working copy.  The REM'd lines are active in the version you are using.  You can see that Synaptics isn't touched.

:: Remove known problem Touchpad HID drivers from driver pool
REM IF /I EXIST "%SYSTEMDRIVE%\D\3\H\A6\" RD /S /Q "%SYSTEMDRIVE%\D\3\H\A6\" >nul
REM IF /I EXIST "%SYSTEMDRIVE%\D\3\H\E\ETD1.inf" DEL /F /S /Q "%SYSTEMDRIVE%\D\3\H\E\ETD1.inf" >nul
REM FOR %%i IN (Elantech\2\ Elantech\3\ Alps\2\ Alps\3\ Alps\4\ Alps\5\) DO (IF /I EXIST "%SystemDrive%\D\%ARCHP%\All\3\Touchpad_Mouse\%%i" RD /S /Q "%SystemDrive%\D\%ARCHP%\All\3\Touchpad_Mouse\%%i" >nul)
REM :: debug
FOR %%i IN ("%SystemDrive%\D\Known-problems*.txt") DO (FOR /F "eol=; tokens=* delims=" %%D IN (%%i) DO (IF /I EXIST "%SYSTEMDRIVE%\D\%%D" RENAME "%SYSTEMDRIVE%\D\%%D" "%%~nxD.bak"))

Now, a single line takes care of disabling the .inf problem kids.

I'll add the Cypress and the older Elantech to the list.
Can you also post your full HWID list?

Here's version 120428.
http://www.mediafire.com/?s15mqmy9661tx5c

I'll work on incorporating the new code to build the array from the new text files and build a few test packs to go with them.  This will add flexibility to SAD that will allow everyone to modify their own DriverPacks for their own use.

OK, I rewrote the cleanup phase with array processing to make it easier to add/remove designated touchpad folders for deletion.  One line:

FOR %%i IN (Elantech\2\ Elantech\3\ Alps\2\ Alps\3\ Alps\4\ Alps\5\) DO (IF /I EXIST "%SystemDrive%\D\%ARCHP%\All\3\Touchpad_Mouse\%%i" RD /S /Q "%SystemDrive%\D\%ARCHP%\All\3\Touchpad_Mouse\%%i" >nul)

But I don't really want to "hardcode" those paths into SAD.  It's not very flexible.
How about adding a "known-problems-Third Party DriverPack-touchpad.txt" file to the root of the touchpad Third Party DriverPack?
If the contents of the "known-problems..." file have the paths to each problem folder then SAD can remove those dynamically with a modified array.

Something like this:

The array processing can be handled very simply and each pack can have its own "known-problems" file.
Something like this (untested of course):

FOR %%i IN ("%SystemDrive%\D\known-problems*.txt") DO (FOR /F "eol=; tokens=* delims=" %%d IN ('DIR /B /S "%%i"') DO (IF /I EXIST "%SYSTEMDRIVE%\D\%%d" RD /S /Q "%SYSTEMDRIVE%\D\%%d" >nul))

Ideas?  Thoughts?  Stone-throwing?