Search options (Page 45 of 99)

oh,
you do need to slipstream each supported OS you want this done for, and copy the files for each OS.
You need only one OEM folder, though.
It must be in root of the DVD.
The other copies made when you slipstreamed can be deleted.
(when you do not change selection when you run DpsBase, they are all identical. Only the one you put in root is used.)

The spotlight utility is a free technet download used by "syprep" people.
The output is either INI or CSV, and the operator has to manually change the batch to needs.

What We did, is something like this.
We made the INFinfofinder cmd ask for the source folder. (drag drop it into it).
Once we have the raw CSV output, it can be put to use.

Oh, spotlight uses a VBS script. It is free to all.

Araxis, that is not free. Winmerge is next best. These tools are used to compare sytemfiles and folders.
JakeLD mentioned duplifind to get internal duplicates found in a single file.
The hilite formula for excell posted by one of our members was valuable, and that is doing it for the HWID or any other Column one puts it to. (Excell has a limit on those formula. Our need is met by doing it on one or another, the human brain can devise ways to put this to use..)

These are what I use now.
Ruud, Alex, Erik, Jon, Jeff, Geert, and all the testers I do not mention have had access to this tool for a good while.
It's been on ftp by me for more than half a year before I personally looked at it..
Now I use it.

Hi,
I'd like to know what format we need to put collected data in, because I have this uncanny feeling the new site will make have us change the way we work now.

To explain, at the moment, we collect data with "spotlight" and then use its raw CSV output and put it in Excell (We could put it in a Dbase too. ) because we found a way to quickly show duplicated hardware ID's (or version, or filename.. There are like eight important columns in that file.).

I knew Bâshrat the Sneaky was busy.
I hope he gets us on the track to the future.

Hi OverFlow.
I just looked at the PlugIn builder tutorial you prepared.

I will let these folks have a sneak preview.
BartPE/OverFlow/DPs_BartPE_HelpFile

I wonder about making the excell worksheet links available here.
The worksheets are on FTP, and those with access to tester forum should have found those.

I am not a data mining expert.
(hehe, I am not an expert in anything..)
The raw output from the tool has to be looked at with argus eyes, because there are drivers what have 'dupes' in the inf. The tool is not ALWAYS able to gather Operating System info from the Inf, so I had to look at content to see why dupes was there.
That was like work.

I've seen a driver that had "suspicious" lines in it, and sure enough, the next update fixed it.
It also added wdm copies of the INF files that had not existed before..

I've seen drivers that had dupes in it that were real errors by the OEM.
(like in, they added their HWID, and it already existed. It did not call different settings/registry sections.)
It was NOT for some particular dual card. The excell shows wher I found one of those.. I marked it "B" so it would no longer hilite.. The tool's raw output does show duplicate lines caused by sections which are duplicated across drivers for registry entries. They are not HWID dupes.)

The worst are those that let generic HWIDs exist, where the only thing they really had to have is their specific ones because they have changed SYS files.
The generics fight a battle.
Windows can get information from an INF what can claim that a driver is newer, where the systemfile is actually older or same, or not suitable.
Nobody said it was easy. You guys at least try to help.

Hi,
Welcome to DriverPacks.

The downloaded archive must be placed in \driverpacks folder.
You don't put unzipped files there.
dpsBase will unzip and process the archive.

(sorry.. yesterday I wrote a longer post, and submitted it, but it got lost in a forum glitch?)

HOW did you fix it?

Hi
I will look what I can do.
I see that REV_03 is not mentioned in the DELL M70 driver.
I see that the PCI\VEN_8086&DEV_266E&SUBSYS_01871028 is a unique in the current release.

I think the M70 will have a lot of duplicated HWIDs if we add it, and that could make it still take the wrong driver.
I suggest you replace the folder with content of your driver, and repack the sound_B pack..

I'll be available tonight.. or tomorrow.
Last few days I was extremeley buzy doing hardware fixing and I do shifts too.. and was at work

hi,
you can link to it.

Willkomma to DriverPacks. A 404 is better than 504, and worse than a blank.

Hi
welcome to DriverPacks

this is in that 2.exe (a self extracting file)

[3-2]
; Disabled! driver conflicts with the Silicon Image 3112r and Silicon Image 3132 drivers.
; if you need this, unzip, disable [S-5] [S-5-A] [S-B] and [S-C] and enable this section
; ( to enable, change ms_count=0 to ms_count=1  )
ms_count=0
ms_1_deviceName="AMCC 3ware 7000/8000 Series ATA RAID Controller"
ms_1_tag="3ware78k"
ms_1_sysFile="3wDrv100.sys"
ms_1_hwids="PCI\VEN_13C1&DEV_1001"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

Hi
when you do the slipstream, a more recent pack will be taking the place of the older.
in other words, it is updated.

PLEASE ENABLE QSC when you slipstream, even if it does NOT reccomend it.