new  file for testing

DP_LAN_wnt5_x86-32_805E.7z (link pulled for release)

We want it tested.
smile

edit> LET'S TELL YOU MORE..
NVIDIA LAN drivers were reported to cause error.
That should be fixed now.

intel LAN would clash if you used the DELL version (which uses an older version with proprietary files for DELL.)
I made the error of releasing this too fast, but we did that because we knew there were issues with the previous pack that had to be adressed.

updates in other drivers

people with NVIDIA issues in the current release should use this testpack and test, and report..
(and PLEASE, let us at least know what that hwid readout said about the LAN driver, and if this testpack still does not work, PLEASE link to the manufactor driver that DOES work.)

Hi Dan,
That looks like a good job.

Thanks.

Thanks.
I'll make a note in that folder that this is one we must NOT update.

We'll have a new testpack in a couple hours.

NV45_rest contained 6.86, and was recently renamed to NV4

Thanks.
I'll check the version we have in there.

Hi
I think we saw it as harmless..
I remember reports by some people whom would list all the files they (usually correct too) saw as "not needed for the workings of the driver".

a helpfile in html, a changelog, device list, or a readme.. that should not be an issue.
@ Third Party DriverPacks we ASK that a changelog/device list is included.

I figure slipstream tools will read the INF files and use the info like [copyfiles] in there to do what they do..
(you won't find the html file reference in that..)

I wish the people using DriverPacks in their own projects would help here

woody22
I will say this every time I feel I must.

PLEASE give us more detail like a DriverPacks BASE log, a HWID readout, and please link to the driver you know works for the bloody thing.
your report doesn't help us solve this riddle.

I don't mind the short life-span, but must at least find out if this DriverPack Graphics A 805B works.

458

(13 replies, posted in Other)

Hi
I have still not figured out what they did in some of those. They "seem" normal, but output has zilch.
I couldn't get in contact with the utilityspotlight05 coder sad

459

(14 replies, posted in DriverPack Chipset)

@ paulo_sor
Hi
please do not make us look up details on that mobo.
A link to the drivers page for the motherboard you use is appreciated.

I do want to THANK you for the report.
I would like to know some details like the settings in BIOS.
(AHCI?)
Also, a DriverPacks BASE log because I want to see what other testpacks you used.

testpacks need testers, we really do need testers.
anybody who is grabbing a testpack is expected to give more detail that what you did, but, NO report is worse than a report with little detail.

how long have you used DriverPacks?

DriverPacks forum has no PM.
(and that's fine with me.. because PM tends to get discussions hidden from public)

hit email.

WLAN has NO INI at all..

shaz?
I could not find the Nvidia LAN driver for this mobo at Asus site (I found lan for RIS.. but not the LAN.)

I've looked through the HWIDS and could not find this subsys.
Can you point me to the driver which has this LAN driver with this HWID?

for those wondering what HectorFX is talking about..

We had a testpack called DP_LAN_wnt5_x86-32_805D.

This topic started with a testpack posted in may, so we started with a version 805a.
And then things went on..

In mid June I went on holidays and Mr Smartepants came back from his trip. Mr Smartepants has since then took over developement of the DriverPack Graphics A and other graphics DP's and has updated this post about the latest dpg test packs.
When you read this topic you can see that getting it done right is not enough.
The drivers themselves are also under scrutiny. We can all learn from what you experience so we want reports, good, or bad.
Your insights and proposed fixes will help the real master.
(That's YOU, Erik.)

Links to previous testfiles pulled.
-------------------------------------

hmmm
this sounds like it is a problem with the installer..
http://www.usr-emea.com/support/s-prod- … ;prod=2210

hi,
you can also rename logfiles before you run DriverPacks BASE wink

hi
Like Jeff says, there is more to it.

you may want to learn what changes are made.
1; get winmerge or araxis and install it (a comparison tool)
2; make a copy of a XP CD to a folder
3; copy that folder (so you can later compare)
4; run base with DriverPack MassStorage and txtmode in M1 to one of those folders.
5; compare
--------
you will see where the files where added and replaced files will also show.

you will see that dosnet.inf is also changed
compare it
you will see that txtsetup.sif was changed
compare it

--
I think that since you can do this manually, you could learn how to add your drivers to DriverPack MassStorage.
two important rules:
unique tagnames in INI
no duplicate HWIDs in INI

you could link to the exotic drivers we do not have, and show us how you try add those.
(like an academy..)

Dan,
we don't mind the number of posts..
You are letting us know what you find out, and how you make it work.

Jeesh..
Thanks.
The generic in reference intel overruled that DELL specific?

I would also advise you test the latest DriverPack MassStorage testpack.

Hi
there is a "copy of " file in the release of DriverPack MassStorage 805.

we have a testpack where we removed a redundant copy (Kopie van si3132r5.inf)
(It has a lot of other things....)

you find a link here
http://forum.driverpacks.net/viewtopic.php?id=2699
-------
there is also a new DriverPack LAN testpack, and a chipset testpack

DP_MassStorage 805C testpack
4,91 MB (5.148.764 bytes)

MD5 HASH
ea19c853060b6c4415a1961325bcf090

8.05.c (14 may 2008. team)
link pulled.. testpack updated to 805D

Changed
'[I3] iastor 7.8, keep support for hardware not covered by new intel iastor driver. (JakeLD)'.
'|Rename/moved \I4\ (RAID/Cluster Miniport driver)  to \I5\ to make new \I4 home for yet another intel Iastor (JakeLD)'.
'|[P7] correction in INI, a disabled HWID was re-enabled.'.
'|PB\ and [PB] INI section deleted'.
'|[V3] Commented 64 bits lines (JakeLD)'.
'|removed a redundant copy (Kopie van si3132r5.inf).'.
'|removed DpInst.exe from IB4\ and IB5\ folders.',

New

'H10\ Highpoint RocketRaid RR3xxx controller 01/03/2008, 1.2.13.3(JakeLD)'
'|[I4] Intel Matrix Storage 04/15/2008,8.0.0.1039 (team)'.
'|L7\ LSI Megasas 05/05/2006,1.20.0.32 (JakeLD)'.
'|[M4] Marvell 64xx/63xx SAS Controller 12/06/2007,2.1.0.11 (JakeLD)',

Updated

'J\ JMicron JMB36X/37X Controller from 11/26/2007, 1.17.31.00 to 04/03/2008, 1.17.33.03 (JakeLD)'.
'|M\ Marvell 61xx RAID from 05/22/2007,1.2.0.45 to 10/18/2007,1.2.0.51 (JakeLD)'.
'|N\6\ from 05/04/2007,10.1.0.12 to 07/27/2007,10.1.0.15 (team)'.
'|V4\ VIA SATA from 10/18/2007,6.0.6000.230 [5.16a] to 04/03/2008,6.0.6000.252 [5.17a] (JakeLD)'.
'|[SB5] Silicon Image 3132 SATALink from 06/05/2007, 1.0.21.1 to 10/03/2007, 1.0.22.0 (team)'

Hi
the original downloads have the file in the driver.
But, you are right, it is is not used and can be removed.

Hi,
the files are different because DELL's have another version.
(they also had immense overlap, and I don't want to risk a proprietary load a generic when we have a reference driver for that.)

8.05.D (internal name 8.05.2a)

http LINK REMOVED

New
B4\ Broadcom Netlink Gigabit 02/24/2008,11.7.1.1 (JakeLD)

Updated
AT2\ Atheros L2 from 08/21/2007,2.5.6000.5 to 12/21/2007,2.5.7.9 (JakeLD)
I1\ Intel PROSET from 13.0 to 13.0.1 (JakeLD)
M\ Marvell Yukon from 04/04/2008, 10.57.3.3 to 04/29/2008, 10.60.6.3 (JakeLD)
R3\ Realtek RTL8168/8111 01/03/2008,5.686.0103.2008 (same file version but more hwids supported) (JakeLD)

Changed
Removed I2\ and I3\, now inclued in I1\ (JakeLD)
Moved I4\ to I2\ (JakeLD)

I2\  (DELL proprietary) after update in I1\ and made corrections.
--------------------------
When you test this file, please do us a favour and test this 8.05.D.. as is.
Then please move the DELL***.INF files from I2\ to I1\ and then delete I2\ and test that too..

or, simply rename the INF files in I4\ and repack

if this works, then DELL's proprietary set is still complete

Dan,
you could try this..

unzip
RENAME the INF files in i4\.
move the renamed INF files into I1\
delete i4\ folder
recompress.. test