Hi
I sold the box with the ati testcard. (CCC not automatically installing in desktop was something I experienced in June. I could not figure this out. The CCC.exe would install the CPL proper when I manually ran it afterward.
I still think we can blame this on HDMI and sound conflicts, but Samlab chose to not use CCC, yet was bent on looking at graphics conflicts and found them. ((but I could not always accept his reports for validation.)). )

Shiitt. I have just heard a hardware screech in this vista testbox. (sounds like HDD bearing.)

edit, those older maxtors do run hot. This diamondmax 10 series, 250Gb, is stressed by vista and live-one-care and HOT.
I hope it dies, so I could RMA .
edit two
confired diagnosis.. it is HDD axle bearing screech.

Hi,
DriverPacks has not yet released an PE optimised LAN DP.

But, it is in the works. The DriverPack LAN was already looked at (over a year ago, actually) and we did it without proper tools.
Intel and Nvidia (especcially Nvidia) are using same filenames across different chips.
Jeff started the work for LAN PE 'exception code' some weeks weeks ago, and we can but hope that new updates don't always drop spanners in the work.
There is a topic in LAN forum where all Nvidia LAN drivers  can be looked at. It is an eye opener.
(It has a link to a collection with the original drivers I collected early June..)
It does not have the Joshua plugin driver, though. (Nvidia filtered by Joshua)

PE users can help Jeff by reporting best combinations..

I agree too. sad

I sometimes do not want to undo the fine tuning.

There is a lot of Legacy in DriverPacks. I doubt there is an active current team member whom has all original drivers on his drive. Are there any?
I don't have all.
There are quite a few members with more expertise than I have, and I think they all know we have to make choices every now and then.
Jeff has summarised how we have to make our choices more than once.

oldest is reference intel 5.5
adaptec copied those?

we have to choose between reference generic (with CC_104) or a third party with generic.

we have an issue with an LSI (simmpi simmpy simmp1) wich misbehaves (a coded temp copy routine in the inf most likely) and in PE it adds a space when you nor I can find duped in an INF nor INI.

D4 will create an issue.
in INI, snub the two HWIDs.
in PnP, the reference (well, we broke signing for the syspreppers by renaming the iastor55 inf and sys.) the adaptec will win war in PnP.

what do we do? Renaming a sys and so on was never a good idea?

after the few tests I did without sound DriverPacks and suitable hardware, I think samlab has the key to conflict.
HDMI in video cards could be clashing with sound.

Erik, when I tried to corroberate that, I used low cost motherboards and graphics cards and I knew that the driver CD supplied with the mobo had a bad install routine because it clashed with its own IGP, and no third party graphics card was plugged.

when I used other testbeds, I saw that some ati drivers (supplied on the CD) had problems with hdmi.
What I am saying is that we see a mess, and it is not your/my/our fault.

Nvidia graphics and ATI with TV and sound capability will (this is for real.. it is a statement) clash with things like realtek.
We could have a perfect DriverPacks combo for 99.98 percent of users, and the next update in any of the main DriverPacks or third party (third party like modems with sound/and TV with sound..) can and (a prediction; they will) introduce issues to 20 percent.

edit;
HDaud sound capability and HDMI will, in my opinion, be an issue because the manufactors don't get their drivers right, and they seldom (if ever) look at conflict issues (with/against other manufactors // OEM implentations.) like we had to do...

D4, two generic, they will cause problem
PCI\VEN_8086&DEV_24DF,PCI\VEN_8086&DEV_25B0,

@ babyboy,

we have a Dutch language forum.
Real important problems will get escalated and translated. I think you can explain what happened in our native Dutch language a lot better.

7zip is freeware.
Winrar (last time I looked it was not free..) is not needed, and may have introduced an "unknown" error.
Actually, you only need to uncompress when you want to edit the DriverPacks.

Far as I know, you can not include the hash in the archive, because the hash is calculated after the archive was made.
(which made me write the daft suggestion to make the DriverPacks, calculate the hash, pack the DriverPacks with the hash info into a new file, and give it a new extention (not an archive extention) so that base 'could' unpack the BTX "zip" wich included the hash txtfile and then read the content of the hash/compare to hash of the real 7z of the DriverPacks... and, actually, nobody could guarantee that THAT hash was not tampered with.. If you were to modify your own dp and did this yourself... The hash we post online cannot be tampered with unless you hack the site. We post the size, the hash, and have always allowed users to modify their DriverPacks because advanced users can/and will. We rely on advanced users to solve issues with driver conflicts.)

(A re-iteration is something else.. I used the word because it was the first that came to mind.)

IDK means, I don't Know.

the time it takes to apply KTD depends on system speed as well.
Two hours seems long, but in a virtual machine, who knows.
If you reset while it is still churning and editing the registry... yikes.. I think that would spell trouble.

listen, I can give 512Mb to a VM, and I can give it plenty processing power. It will still not be the same as real metal.
I have not used KTD for a while now, because DPinsT can replace that function, and, DPinsT can do this with updated DriverPacks, which is not a feature you will find in KTD (what you streamed and told windows is there is what is there..)

Next thing I know somebody asks Warmsnow if he wants to write a KTD update module for DPinsT.
(and the cleanup of old drivers from the registered files in windows... aarh.)

anyway, I will run a KTD session in real metal, and see how that goes.

sounds impossible to me.
it is like a re-iteration?

Suppose you have a 7z file, you calculate its hash, then write that hash as txtfile (or whatever, with standardised naming) and include the hash in the new 7zip, with a new extention (BTX), so that the DriverPacks BASE has to unpack hash and real DP, check hash txt against file hash..

huh?
pop a warning when the file was edited by user..

I have nothing against posting the hash, but I think coding strict file hash safety in DriverPacks BASE is not easy.

235

(10 replies, posted in Software)

a blank drive is a blank hard disk

welcome to our nightmare.

welcome to DriverPacks. smile

here is an OLDer worksheet. (april)
http://dev.driverpacks.thesneaky.com/dr … sB_804x.7z

have you tried with only sound A?
(gut feeling. A holds main and tends to play boss. B has a great many rebranded realtek.)

@ team
it looks as if there are active generic we did not snuff causing conflicts, because what I see time and time again is that those I (we) left in are resurrecting their ugly head each time there is a new device in the market.

Have you tried looking up wether the HWID exists in sound A and sound B? (both.)
I am almost sure
PCI\VEN_8086&DEV_24C5&SUBSYS_4760414C is killed by PCI\VEN_8086&DEV_24C5 (generic) in a wrong driver.

238

(5 replies, posted in Software)

Jeff, the BBS has a tendency to mess with tabs when you put a txt in "code" tags.

(and I think that when I undo the code tags, it will not correctly resolve to original state.)

a link to the code on a skydrive or whatever else that does not drop spyware and adverts (or long waits) is fine by me.

(besides, google loves long posts and code.)

I am not going to be testing this if this does not add choice for third party and then separate third party.
(and it also has to work in M1.)

240

(10 replies, posted in Software)

VBP2004EP3
I forgot to say welcome.

the thought on writing something helpful that had not yet been written on HOW to find out what will/will not be supported occured after the third carriage return in first post.

We usually ask, please post HWID (and we think you know what we mean.).
(We explain HOW quite easy. We actually always meant the HWIDS from the computer that needs the drivers. I sometimes think we also have to explain that little important fact as well..)

clarity edit previous
reread

Hi folks.
I have not been able to look at SamLabs script trickery for folder manipulation.
The link was dead.

I do know that I can not write scrips to do this, but I have been able to manipulate DriverPacks folder layout in the DriverPacks INI after I manipulated folder structure for really really (REALLY) short method 1.

@ Samlab
What is the good in changing G to V? (sound first. Then graphics. I can follow that train of thoughts. BUT.... There are TV and graphics cards, and MODEM with HDaudio. ((Not only sound.))
And I am thinking it is a conflict, not so much a load order. BUT Samlab, you do know what you are doing; and I know that graphics HDMI can cause a yeller. )

also @ samlab.
when you change folder name.. You realise you HAVE to edit the dpg INI, do you?

243

(10 replies, posted in Software)

for the not so new.
you can use dragdrop INF info reader which is available in the testing FTP, under worksheets. (it is in some of those worksheets)

The worksheets themselves are NOT a complete set.
you run that tool against the folder where you extracted all driverpacks. (takes a while)
It builds a CSV.
Run search against that build, or create a dbase or excell from the CSV, and search in there.

The CSV (or excell) will have about 98 percent of what we carry, but not every thing.

There is alse a SED scanner in there. (it SADLY, uses a different format in rows)

That will only scan PCI, but will scan ALL PCI. (the vbs driverinfinforeader will read all sorts of hardware, but there are some drivers with malformed tabulation it does not read.)

(I know I wrote sed scanners for USB and audio but a drive failure zapped those)
I have SED scanned some and then manually added the output in the VBS format.. but you would not know that. sad

244

(10 replies, posted in Software)

Hi
you can find out.

get to overview, download all current DriverPacks you think they need (including 3rd part dp) and DriverPacks BASE.
Copy a 'test' OS like a corporate or a current XP SP3 (which does not ask key and has a nice grace period.) to hard disk, run the DriverPacks BASE, and build a source to burn to DVD.

connect a blank drive to one of those laptops (you can get a blank, I hope.)
(I know there ARE laptops with TWO hard drives.. if your company has those,  remove both and replace with two blanks)

set up.
report.
We do not have databases on individual laptops.
What YOU could do is post the HWID readouts from a working laptop, so we can look at those lines, but, you would actually also be able to do so.

HWID readout has like 40 lines.
you uncompress all DriverPacks.
you run a HWID readout
then you run search for content 'txt content' of a single line with 'PCI_VEN_ subsys (and no more) against extracted DriverPacks folder.
When there is NO match, search generic PCI_VEN_

there is a description on the meaning of life in the FAQ link in my sig.

and we have four iastors.. good grief.

these are notes sad

asus (weve had a good many reports on asus, it sounds like it uses a proprietary)
ICH8 82801HB & JMB363

Jmb (like on my crapola testplank )
affected hwids

PCI\VEN_197B&DEV_2363&SUBSYS_81E41043&REV_03\4&18CD42CE&0&00E4: JMicron JMB36X Controller
PCI\VEN_197B&DEV_2363&SUBSYS_81E41043&REV_03\4&18CD42CE&0&01E4: Standard Dual Channel PCI IDE Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&11583659&0&F0: Intel® 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2810&SUBSYS_00000000&REV_02\3&11583659&0&F8: Intel® ICH8/ICH8R Family LPC Interface Controller - 2810
PCI\VEN_8086&DEV_2824&SUBSYS_81EC1043&REV_02\3&11583659&0&FA: Intel® ICH9 SATA AHCI Controller

QUESTION;
1; what mode is BIOS set at?
2: are you running a raid array?

JakeLD,
please do not see this as a rebuke.
I made 806E with unadulerated drivers because I think the single HWID that some see as (we wanna have that OLD hwid) was most probably causing more issues than what it solved, and editing out lines for x64 also breaks signing.

I did not pull links to 806C.
806C has syprepped optimised INFs for Via.
806E has WHQL.
We will no longer look at size because size does not mean much in download price now.. We look at quality.
I am not saying that we will undo all syprep optimisations, but we must at least find out why via became a thorn in our hide.

I would like to add some links to interesting articles and topics.

first off; dissappearing drive letters, with USB storage and other USB devices.
http://www.uwe-sieber.de/usbtrouble_e.html

second; are card readers the only ingredient in lettersoup?
http://forum.driverpacks.net/viewtopic.php?pid=11012

TIP;
forum search changed to google search.
it automagically filled in driverpacks as key word in search field. LEAVE IT IN.

FORUM wide tip
1; Always use rightclick and open in new TAB or window when you want to follow a link..
2; hit the subscribe link to a topic you answer to.
(And to a topic you want to see replies to when you did not yet participate in that topic as starter or by replying yourself.)

Hi,
Bâshrat the Sneaky is still with us and last thing he told me is he is working hard to get the new site a fact.
There are several people helping at DriverPacks now, and team members help those people make this project get better.
When you run DriverPacks BASE and get to the "credits", you will also see the words he wrote about this.
They actually form a link to the donation page.

I'll look at those links you just provided, and will see what we can do.

hehe, I forgot to say "Welcome".

the reasoning behind putting unedited files back in the VIA is that signing probably got broken for PnP.

the name "8.06.E" was on purpose.
JakeLD mentioned he wrote a 806D (which he had not yet uploaded), and I did not want to use 807a.