2,201

(48 replies, posted in DriverPack LAN)

Actually, you could try extracting the C:\D\L\I\RIS_INF\e1k5132.zip .inf and overwrite the standard .inf.  The RIS driver may work better in your PE environment.
Also, that .inf is unchanged in the newest 15.3 Intel driver set (unreleased).

2,202

(103 replies, posted in 3rd Party DriverPacks)

Can you try changing this line for both [D] and [T] sections.
exc_1_tagFile2    = "%WINDIR%\System32\DRIVERS\tosrfusb.sys"

to this line
exc_1_tagFile2    = "%WINDIR%\System32\DRIVERS\tos*.sys"

I also found a bug in the [T] section.  It might have affected your install (might not).
Change
exc_2_+infFile2= "%DPSROOT%\D\3\BT\T\tosrfec.inf"

to
exc_2_+infFile1= "%DPSROOT%\D\3\BT\T\tosrfec.inf"

2,203

(48 replies, posted in DriverPack LAN)

So you've already tried the release DriverPack LAN 10.05 and it's not working for you?
Only reason I ask is because it already contains the latest drivers for that HWID.

You could try this resource: http://www.intel.com/products/ethernet/ … amp;s3=all
But from what I understand there's no PE drivers for that device yet.

2,204

(1 replies, posted in 3rd Party DriverPacks)

I think you're getting confused between the HID (nt5) and Input (nt6) Third Party DriverPacks.
wink
Technically, both still exist...for different platforms.

I'm moving this topic to DriverPacks BASE Feature Requests.
Because that is what you have reported.

In the past ACPI USB hdaudio HWIDs were always matched in full
As an example: HDAUDIO\FUNC_01&VEN_111D&DEV_7608&SUBSYS_103C308C&REV_1002 will not match with
HDAUDIO\FUNC_01&VEN_111D&DEV_7608&SUBSYS_103C308C or
HDAUDIO\FUNC_01&VEN_111D&DEV_7608 or
HDAUDIO\FUNC_01&VEN_111D&DEV_7608&REV_1002
this has never been an issue in the past.  And we like exact matches very much.  It removes any doubt which driver is used.  There are so many variants of IDT/SoundMax/etc. that a partial match would cause more problems than it would solve.
Besides, adding that parsing code would make the DriverPacks Finisher take about 4 times as long to complete.

At the moment, Jeff is our only DriverPacks member maintaining the DriverPacks BASE codebase. 
If more users request the same functionality as you did, then it will get moved up the priority list.
We'll add it to our list of feature requests.

But we're so close to having a final release of DriverPacks BASE that I don't want to add any potentially buggy code to an already very stable platform.  We need to get DriverPacks BASE v10 out the door...agreed?

OK, I modified the ich78id2.inf like techisgood148 reported and I'll upload as 10051 final.

OK, I can see from your side-by-side ENU/RUS installs that something is not right.  The english source is reacting exactly as it should with the DriverPacks Finisher.  The russian source is not.
It's impossible for Jeff and I to duplicate your problem because we only have English sources.
What I find very unusual is that you are the only person using a Russian localized source that is having problems.  In fact, no other foreign users have reported this issue either.
One of our respected testers, SamLab, is also from Russia and has NEVER reported a problem like yours since he's been here.  He tests all our DriverPacks heavily.
Since you are not communicating very well with us, and the language barrier is getting in the way, maybe you should contact SamLab and between the two of you figure out what's going on.
Then once you figure it out, the both of you can come back and let us know what we need to look for.
How does that sound?

IF there is a problem with our code, we want to fix it for everyone.

2,208

(103 replies, posted in 3rd Party DriverPacks)

@compstuff, have you had a chance to test the added bluetooth Dell drivers?  Did they work or can we remove them?

2,209

(2 replies, posted in 3rd Party DriverPacks)

@cheche, did my modifications to the Misc Third Party DriverPack work for you?

mr_smartepants wrote:

Would you please (just as a test) integrate unedited DriverPacks via DriverPacks BASE and let us know the outcome.

YikxX wrote:

Had to redo and repack test driverpack again. Hour killed for nothing.

2010-05-27 03:42:17 : <INIT> 	Detected DriverPack Graphics A 1005r4!
2010-05-27 03:42:17 : <INIT> 	Detected DriverPack Sound B 0000!

Why did you do that?  You had no reason to modify anything.  I asked you SPECIFICALLY to use unmodified DriverPacks for a reason.
What did you do to break the DriverPacks when you repacked them?
All I wanted you to do was take a simple hologramed XP disc, SP3, then use the current version of DriverPacks BASE to integrate the DriverPacks as you get them from us with no changes.
I don't care if the test DVD is not up-to-date.  I don't care if it doesn't have your cool pirated WPI installers. 
IT WAS MEANT TO BE A TEST.  And you failed.
This is getting us nowhere.  We can't help you if you refuse to follow our instructions.

Welcome to DriverPacks slckmstr!
Which version of DriverPack Chipset did you use that had the problem?

YikxX wrote:

A1\B_96537\ file atifglpf.xml is missing - fix it too.

LOL, I had already fixed that when I upgraded DriverPack Graphics A to 10.4 Catalyst. wink
BTW, a "please" would have been nice.

YikxX wrote:

integrate unedited

But HWID PCI\VEN_1002&DEV_9612 not present in your original driverpack Graphics_A

Yes I know.  I'm fixing that.  Thank you for reporting it.
I'll post a link to an updated pack for you to test for us.
But that shouldn't stop you from testing our other DriverPacks and methods.  I just want to make certain that there's nothing wrong with OUR process on YOUR hardware.

It's very difficult for the DriverPacks team to accept that anything is wrong with our tools.  They are all designed to work together.  You've made too many significant changes to simply isolate our DriverPacks Finisher as the culprit.  It wasn't designed to be taken out of context and used in the manner you're using it.  It's entirely possible that the DriverPacks Finisher is doing everything it was programmed to do, but is failing because of the changes you've made.
Everytime you change something, that change (however small) has a cumulative effect on the entire install.  One insignificant typo can have a catastrophic effect once the install is complete.
Would you please (just as a test) integrate unedited DriverPacks via DriverPacks BASE and let us know the outcome.

OK, here's the deal.
1) 1366x768 pixels isn't supported (I think).  I'll make sure it's added in the next release. smile
2) We say this all the time.  DriverPacks Finisher does NOT install drivers.  XP setup installs drivers via devpath.  When you integrate DriverPacks via DriverPacks BASE, all the correct settings are made for this.  If the driver isn't loaded during XP setup (between T-36 & T-33) then the HWID isn't recognized by DriverPacks Finisher because it's not "seen" by XP devmgr.

OK, I had a quick look. 
Your HWID for the Radeon HD3200 is not supported.  I'll have to fix that.  What screen resolution do you request?
Also.
What exactly did NOT work with the Sound \z6\ exception for DriverPacks Finisher?
Although the .inf isn't referenced in the finisher array.  It looks OK to me.
Quoted from the DPsFnshr.log you posted.

2010-05-24 23:41:33 : <INIT>     Processing driver exceptions section [z6].
2010-05-24 23:41:33 : <INIT>         Importing exceptions for this driver because the directory "D:\D\S\z6" did exist.
2010-05-24 23:41:33 : <INIT>         Importing the full requirements for exception 1 of 1 for this driver.

2010-05-24 23:41:34 : <DBG>          [z6] = array(
2010-05-24 23:41:34 : <DBG>             [tagFiles] = array(
2010-05-24 23:41:34 : <DBG>                  [1] => %SystemRoot%\system32\drivers\sthda.sys
2010-05-24 23:41:34 : <DBG>                  [2] => %ProgramFiles%\IDT\WDM\stacsv.exe
2010-05-24 23:41:34 : <DBG>             )
2010-05-24 23:41:34 : <DBG>          )

2010-05-24 23:41:34 : <DBG>          [35] =>
2010-05-24 23:41:34 : <DBG>              [0] => z6
2010-05-24 23:41:34 : <DBG>              [1] => %SystemRoot%\system32\drivers\sthda.sys|||%ProgramFiles%\IDT\WDM\stacsv.exe
2010-05-24 23:41:34 : <DBG>              [2] => 0
2010-05-24 23:41:34 : <DBG>              [3] => 0
2010-05-24 23:41:34 : <DBG>              [4] => 0
2010-05-24 23:41:34 : <DBG>              [5] => 0
2010-05-24 23:41:34 : <DBG>              [6] => regedit.exe /S %DPSROOT%\D\S\z6\sthda.reg
2010-05-24 23:41:34 : <DBG>              [7] => True
2010-05-24 23:41:34 : <DBG>          )

2010-05-24 23:41:39 : <FLTR> Verifying requirements for exception [z6] (35 of 40 exceptions).
2010-05-24 23:41:39 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2010-05-24 23:41:39 : <FLTR> 		Found tagfile "D:\WINDOWS\system32\drivers\sthda.sys" (1/2).
2010-05-24 23:41:40 : <FLTR> 		Found tagfile "D:\Program Files\IDT\WDM\stacsv.exe" (2/2).
2010-05-24 23:41:40 : <FLTR> 	=> All requirements for exception [z6] have been met!

2010-05-24 23:41:40 : <DBG>  1 exceptions have fulfilled the requirements to be executed!
2010-05-24 23:41:40 : <EXEC> Executing all commands (1) for exception [z6].
2010-05-24 23:41:40 : <EXEC> 	Executing command 1 of 1: "regedit.exe /S %DPSROOT%\D\S\z6\sthda.reg"

Very strange though that the finisher array is only searching for the same 4 HWIDs (and sub-variations) for each array segment.  Ignoring all the other HWIDs.

PCI\VEN_1002&DEV_4391
PCI\VEN_1002&DEV_4396
PCI\VEN_1022&DEV_1300
PCI\VEN_14E4&DEV_4315

Does that look strange to you too Jeff?

2,217

(3 replies, posted in Hardware)

Already requested & denied here: http://forum.driverpacks.net/viewtopic.php?id=4289
Do NOT duplicate this post again!  7 times is 6 times too many.
Do it again and you'll be banned.

2,218

(3 replies, posted in News)

ricktendo64 wrote:

BTW do any driverpacks have 197.45 with this AIO INF?

No.  197.45 is broken.  For the 10.05/10.06 release we're having the 197.13 desktop & 197.16 notebook.

I have the new beta 257.15 drivers now.  Unfortunately they do not contain any notebook drivers.

Well, some DriverPacks are getting too big to have a single pack, so we split them up and use A, B, C (and maybe D?).  For Graphics we tried to divide them by category.
A-ctive (actively developed.  ATI/Nvidia gaming cards)
B-usiness (for workstations.  ATI/Nvidia workstation-class cards, all Intel)
C-atch all (everything else.  rarely updated or derelict drivers.

The sound DriverPacks do not follow the above rule.

Yes, this looks very odd.  I can see a little of what you're saying now. 
But Jeff is right.  We need to see the unedited versions of the DPsFnshr.log from each affected system.  Please upload them to a free download site (mediafire/rapidshare/FTP)
The HWIDs from those systems should be within each DPsFnshr.log anyway so you shouldn't need to run the HWID tool separately.

Also, I got the same response about two years ago when I reported a DriverPacks Finisher bug (wildcard bug) when both Wim and Jeff said "there's nothing wrong with the Finisher!".  Then followed by "Oops, yeah we'll fix that". big_smile

We aren't ignoring you.  We look into every bug reported.  But we need more info to resolve this properly.

2,221

(7 replies, posted in 3rd Party DriverPacks)

Updated to 1005b1.
@Ra, I could only add the Asus drivers.  The other two are just crazy/encrypted.

2,222

(11 replies, posted in 3rd Party DriverPacks)

Updated to 10.05

2,223

(4 replies, posted in Software)

Interesting.  If I get the chance (big 'IF'), I'll have to check this out.

2,224

(7 replies, posted in 3rd Party DriverPacks)

Wow, I should have done this Third Party DriverPack ages ago.  I want to know who put symbols in for folder names?  sad
I'll bet each symbol is converted to an ascii character string during PE and that's what's contributing to our folder path problem.

We support the DriverPacks that WE build.  If you build your own, then you support them. wink
The DriverPacks Finisher requires specific entries in each pack .ini to work properly.
If you've updated your own pack, then chances are that YOU broke the DriverPacks Finisher .ini entries. wink
If you read the documentation in the DriverPacks BASE\docs\DriverPack_reference_wnt5_x86-32.ini file then you will see.
And folder names are VERY relevant.

We will help you fix it, but you have to provide the details we need.
Post the content of your DriverPack Sound B .ini and a screenshot of the folder structure and contents of the broken folder.