@ cheapstyle,
welcome to DriverPacks.

mr_smartepants is our leading Graphics Master but has other obligations at the moment, and the answer about DriverPack Graphics C he gave showed his expertise.
We have been trying to work around conflicting drivers, and the question I asked @ mr_smartepants is about a list of hardware (HWID READOUT from INF files) whis is basically the entire hardware support across the three graphics DriverPacks.

We have sophisticated tools, but I was not able to put together a complete worksheet together yet.
(I use CSV files to build some sort of database in Excell)

I would like to know if this testpack works for you
http://forum.driverpacks.net/viewtopic. … 613#p20613

if it does not, you may want to NOT use DriverPack Graphics A.
You could learn how to edit DriverPack Graphics C in which you could probably add your driver.
Sooner or later a good deal of how to create a pack will become available to active problem solvers.
We need active problem solvers and a good start is to become one of our active testers.
(we often post links to testpacks in public.. I linked to one now)

Mr_smartepants?
I have only recently discovered the utilityspotlight05.exe tools do not create usable output for Nvidia Graphics.
Do you have a HWIDS list you built by other means?
(the SED scan tool was no use either.. I hope the member looking at this comes up with a HWID scanner that does not fail on some, or that we find a scanner tool works on those that the others fail on.. sad )

Hi
we have a testpack graphics A you could try.
http://forum.driverpacks.net/viewtopic. … 613#p20613

hmm,
no testers reply?
does it work that well?

No news is good news?

Anyway, it should work for Nvidia.. it worked here.
ATI CCC may not work (when I tested in an english source I may have fubar'ed the dot.NET framework addon..).
When I used CCP ATI install worked here.. and without CCC/CCP it also installed.

a sidenote:
ATI tests were done on a Gigabyte card HD 2600 pro.. which is a bear to install from the original supplied CD..
(the new download Gigabyte put up worked a lot better)

hi
look up presetup.cmd in a DriverPacks BASE 7502 streamed source.

add this line at the top of the file

DEL /F %systemroot%\system32\setupold.exe

I have to err on the safe side.. for backward compatibility.
When I test the new 805 chipset testpack I know it works with DriverPacks BASE 805, but a good many users may not have upgraded to DriverPacks BASE 805 yet, and when we release chips 805? with a single intel folder we'll have to tell people to please upgrade their DriverPacks BASE 7052 if they want all features.

Hi.
Well, this is what we do..
The content of "all" folder gets dropped into the chipset folder (and we leave the older files in because intel drops support for old hardware).

Right now, this content is copied three times.. because the DriverPacks BASE uses three specific folders for method 1.

Hi kuspete,
welcome to DriverPacks.

DriverPack MassStorage has been updated since then.
and the johny that put the illegal XP on a torrent gets no help from me.

slipstream a legal copy.

the via update in DriverPack MassStorage 804 might fix this.. but I must tell you that we have had a few testpacks since. We have not released yet because their are some reports on the updates we have put in the 805 trial packs.
The vendors do not put truly unified drivers up, and tend to drop hardware support while using same filenames..

I will also note that SP3 includes a VIA hyperion of itself now, which is NOT in SP2..
johny did not know that.

I see..
DriverPack MassStorage 7092 used 3ware9k tagname
DriverPack MassStorage 711 uses a new tagname (it updated to the 2006 version then)
and dpm805xx will have to use a the 2008 version of this driver.

(funny how some drivers behave when they get renamed by a tag.. but, since we have not used 3ware9k tag since november 2007 I get this feeling this happened after restreaming the plugin.)

the 2008 version presents me with a problem.. it has two INF files now..

Hi
DriverPack MassStorage does not have a 3ware9k?

Lan 8.05.2 was 805E... which does not crash for rmgalley, but causes a bsod for samlab.. and 805D does not crash for samlab..

I will go ahead on that 'you can help figure out Nvidia LAN' topic, in which I planned to put all LAN network drivers together for investigation by users..

when I read this earlier today I thought of very very long paths..
%SystemRoot%\inf;C:\DriverPack\D\C\A\1;C:\DriverPack\D\C\A\2;etcetera etcetera

and when I get back to this I see Jeff mentioned method 1.

Well, here is something for you.
C:\DriverPack\D\C\A\1;C:\DriverPack\D\C\A\2; is TWO folders weighing in at 44 characters for two folders..
I bet that with your method you still have a problem with path longer than 4096 characters, so why should I not tell you what I did a mont or so back..
Here goes.
------------
How can you have a

SUPER SHORT PATH FOR METHOD 1
_____________________________

1: Benefits;
a) You can stay well under 4096 path lenght with all main packs and several third party included.
b) Method 1 can be used to UPGRADE CDROMs.
c) A Disc built with Method 1 has a searchable driver repository. (the Soem$ folder )
d) The driver repository and path built in WINNT.SIF can be used in an ACRONIS image.
in your example, everything in C:\D\... so your path would look like
%SystemRoot%\inf;C:\D\C\A1;C:\D\C\A2;etcetera etcetera
which you can easily accomplish by a little edit and then search replace on ;D\ to ;C:\D\
(which, incidentally, still sees me under 3400)


2: Disadvantage
a) It will take you a couple hours to do this.
b) You cannot do KTD (but, surprisingly, KTD is not needed because the drivers were copied and path is referenced anyhow.)

- HOW -

Copy the DriverPacks and DriverPacks BASE to a project folder.
I extracted DriverPacks BASE 805 in the "special" project folder called SUPERshort.
In there, I created two subs for the SHORT3rdparty and SHORTmain
Then I extracted the DriverPacks and 3rd party in there.
--------

WLAN has well over two hundred folders, and has NO INI.
Copy the foldername, and make a new folder where you add SHORT (or S) after the version number.
make a D folder in there, and then make seventeen folders in the D folder.
wa, wb, wc, wd, we, etcetera.

You can perhaps use DUPEFINDER to see which folders contain duplicate filenames...
Move the files from the official WLAN into one of the 17, and take care.. You do not want to overwrite a single file.
When you are done, your fingers hurt, but because you moved files from 200 folders into 17 folders you have a MUCH shorter path.

Copy the DP_WLAN_xxxSHORT foldername to clipboard and 7zip the D folder in that supershort folder, giving it the name from clipboard.
--------

LAN is another one with a high number of folders.
This one has an INI.
Copy the foldername, and make a new folder where you add SHORT (or S) after the version number.
Make a D folder in there, then make an L folder, and then make eight folders in the D folder.
1, 2, 3, 4 etcetera

Move the NV3 folder and INI to the "short" pack. (because it gets referenced in INI)
Then move content of the other hundred thirty odd folders to one of the nine folders in there, WITHOUT OVERWRITING a single file.

let zip do its magic and get a coffee.
--------

Sound B has over a hundred folders, and only six are referenced in the INI.
You may think I will suggest you move the referenced folders and INI over to the short pack and then move files.
Well, it sure looks almost every folder has duplicate filenames in it.. (I see 178 dupes.)
I can tell you that getting this to 70 folders is NO fun at all..

I know D\S\CR8 is longer than D\SCR8
So, I changed the INI

[DriverPack]
platform    = "wnt5_x86-32"
name        = "Sound B"
; version 804
rootDir        = "D"
( instead of "D\S" )

And wrote an S into the folder reference in INI
[CR8] became [SCR8]
I then used bulkrename, added an S before each foldername, and was going to move the lot to the shortpack.
hey.. it has 117 folders, so I would get 117 characters less..

But? NOTHING says you CANNOT move files.
So, I started by moving the edited INI and the six referenced folders to short, and then combined some folders..
When I was done, I had 70 folders left.
47 times (example) D\S12; was approx another 300 characters less.

----------

I knew I was under 4096 by now.. (by doing WLAN and LAN I had already shortened path a great deal)

I looked a third party, and saw path hogs.
I really mean path hogs.
I got the third party packs I use from over 2000 chars to a LOT less.

My total path with all the mains and the four third party I use is under 2300..

I applied the rootDir = "D" INI edit I used for sound B in LAN, Graphics A and B.

For the third party files the path looks like
D\3MoA;D\3MoB;D\3MoC; (monitors combined to less than five folders)
D\3MA;D\3MB;D\3MC; (modems combined into 31 short folders. From around 80 nested.)
D\3xA;D\3xAO; (Misc was combined into these two folders. From around 36 nested.)

hmmm.. chipsets is another special..
Chipsets will probably not have triplicated folders for intel in a next release.
(the content in those three intel folders is exactly same folks.)
If you are doing this for XP, you can pretty much put everything what says XP in the intel folder..
If you want to play it safe, keep the triplicated intel, and copy the rest to all three, but don't put folders what say 2k3 (for server) to an XP folder. If it says server, it goes to server.. some Nvidia and some Via have different catalog files for XP/2000/server.. and that's it.


"============================="
"Attention folks, heed this warning."
"You cannot do this to mass storage."
"============================="

Mass storage uses almost thousand characters in path, but you should not touch that.
It used to add over 1500..:)
There was a reason behind the change of folder structures we started months ago.

it should work now..
JakeLD found the same driver I found.. smile

thanks.. this stop error was serious enough.
testfile 805E has been released as 8.05.2

I wish this buleltin board alowed me to to move this post to to the other topic.
http://forum.driverpacks.net/viewtopic. … 670#p20670

I was going to suggest the same..
We do ask that you submit the drivers to a team member as a REQ.

what is a odp?
0DP_SmartCardReader_wnt5_x86-32_80228.7z
(probably a rename so that DriverPacks BASE will not use this)

---------
you are not gonna believe this.
I have to ask for DriverPacks BASE log again, and do you know why?
smile

your list does not have LAN.

we need academy for a LOT of things, and this is one of the examples we have to adress.

I am a mecanic.
I have a hobby.
20 years of dabbling at hardware and 16 years of windows install have learned me that YOU need us, and that I need YOU..
Hardware goes wild.
WHQL for XP? None for Vista?
We still deal with WDM and older.
DriverPacks have had the decency to not drop support for old (sometimes non whql/seldom not even WDM) and tried get the best combo up.

There is going to be a time that ancient hardware is not used for windows 2000.
I am 52. I figure that will be in 2015 because the hardware will then be reallly really obsolete.

Old hardware tends to outlive manufactor support.
People stay and I'll be 115 by the time my micronized mobo implant fails.

to the public..
Thanks for your patience with the Watsons.. Timewarp and Versionwarp are the main reason we ask for logs.

People like Dan meyer and chaz, maa, and hectorfx, Ravennt, wooddy22 and others.. give feedback with little detail, or more detail, and some of them are like Dr Watson.
(They work out what is wrong and help us find solution).
Some people give really helpful feedback. I see the better testers as Dr Watsons.

Hextorfx and Danmeyer are like watsons, and wooddy22 gave detail what helped me help the watsons.

OK.
the 805E LAN is different to what YOU probably used

I just editedt that http://forum.driverpacks.net/viewtopic. … 679#p20679 post..
I intended to show a dirty version of what changelog would say.

Dan..
you are ON TO something.
Nvidia chips, Nvidia mass storage, (graphics and sound too) and lan are a bloddy mess to sort out.

chips and mass are essential. period.
I'd like to see the combo you had when you streamed that..
( the DriverPacks BASE log. )

EDIT

WAS this was caused by a change in LAN? (or your fix in lan? what did you combo with?)

-----------------
latest lan test version LAN changelog.. (dirty version)
8.05.2
(testversion 805E)

fixed
I2\ DELL propriatary intel (Dan Meyers made this work along with I1\. )
(Dan also made DELL in i2\ go along with intel I1\ for BartPE.)

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 (team and Dan Meyers)
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
unified i1\ I2\ and i3 (teamwork)
Moved I4\ to I2\ (team, with Dan Meyers)

I2\ DELL proprietary (Team, with Dan meyers. Dan fixed this for BartPE.)

NV4, rollback. Put driver we used in 805 back in.
this "update" caused a serious error. sad

NV5A, the driver that was in NV4 was for SLI 590 AMD..

@ rmgalley
your report in that other topic had me look at the differences and I think your report has most likely helped solve the issue.
(when the Dr Watsons look at packs, they look at the changes and why they was made.. which can have a Watson look at dozens of things and come up with an "aha" for Holmes.)

http://forum.driverpacks.net/viewtopic. … 670#p20670
that link is about issues, and it sports the 805E testfile which should be a release candidate we want up ASAP.

please test.

http://forum.driverpacks.net/viewtopic. … 670#p20670

Dan, you will get credit for the bartPE fix..
Thanks for that.

http://forum.driverpacks.net/viewtopic. … 670#p20670