Hi twig123
I was not aiming my "rocket fire" at anyone in particular..
A careful observant may have noticed I did not mention which pack(s).
I posted above so people should realise that their work (and their work is welcomed) should meet some minimum standard.
We want to at least have the people realise that a third party "release" can create problems in other DriverPacks.

806E removed

Northland wrote:

Thanks for the idea OverFlow. Unfortunately, I don't think that will work unless I stop using the entire ATI driverpacks folder in A1.  The ATI inf files reference the X300 (the mobility.inf does not - as someone commented out the X300 entry. -I think they should add it back in and fix the hardware id of ati2mtag_M22, PCI\VEN_1002&DEV_5461 to 5460 instead of the x200's 5461 - which is why I think it is commented out.)

Hi,
I think our graphics guru should read this.

I still think we'll have to consider a real split.
DriverPack Graphics A / b /c and dpgM  for the Mobile drivers (because they share common silicon and code, but fight about how it gets used.)

and I am a mecanic.. not an IT guy.. grinz.

Hi,
welcome to DriverPacks.

the short answer is.. It depends.
In DriverPack MassStorage, NO. For DriverPack MassStorage and textmode support, you need the know-how. But a seasoned IT guy can do it after reading the FAQ.
For other DriverPacks, it could and should most likely work, but it may not.
You will probably not pick up the knowhow for building a dp like DriverPack Graphics A and DriverPack Graphics B overnight.
But, most other DriverPacks and 3rd party DriverPacks can be edited and added to by a savvy user..
(actualy, every DriverPacks can be edited. How else would we be able to update them, eh?)

We do like to see the link to the driver you need, though.
Think about it for a second.
When you add it for personal need and it fixes your need and it works for you, then it should be put in a future release so that all our users can benefit later on.

When the larger user base finds it creates no issue, we are happy, and you don't have to fix our newest release each time we release without your driver.
(OK, it took two seconds.)

My only regret is that SamLab does not use ATI CPL (he removes them), and I think we actually still have no reports that the CCC or CCP work?

I don't blame SamLab for not testing that, because I too used to disable tray CPL after install. (DriverPacks BASE now has choice to not install CPL, and I love that.)
But? Does it work when you want it?

My hero of this month is SamLab, for working out which of the various Nvidia is best choice, and not giving up when things seemed at a standstill.

All properly documented reports have helped, so SamLab was not our only hero.
Krige came aboard. He arrived here, was shown what we are about and probably almost instantly decided DriverPacks was worth his time.

I speak Flemish. It shows in how I write.
I am not a programmer. It shows in how I write.
I am not in IT. It shows in my vespa. wink

EDIT:
note, I mention a standstill.. I do not make packs for fun, and none of us do, I guess. I figured that the DriverPack Graphics A I built was not too bad. BUT it was not good enough and I had to finalise other projects before I went on holidays. While I was away for holidays I could not work on DriverPacks (I logged in from a cybercafe in Spain), and when I came back I found a cartload of things I had to do at home. Couple days ago a capacitor popped in my main machine. I still have a huge backlog of work at home, so I may not be able to do much at DriverPacks for a while. I'll be "Thin on the ground", so to speak, in contrast to the past three months. Surgery on both knees had tied me to home, but they are mending quite well and I expect to be back at the plant in july.  smile

Hi
DriverPack MassStorage grew by requests.
These requested drivers will sometimes, later on, show as a problem device because the requester used  the driver to satisfaction and the testers did not have hardware so they could not try all combinations in BIOS settings for same chip.

Windows update driver database does not look (not yet, not yet methodoligically.) for conflicting HWIDs but it is entirely possible that OEM supplied drivers conflict with its own hardware, or itself.
(hmmm.. a diferent mask, or a deviant  revision can get a driver where the 'generic' was  not meant for it but it was still there.) .

ahci is looking for problems.
It sounds like that when you do not have native command cueing (which was apparently not supported natively in XP for all chips.) you gain no speed benefits.

Some people running vista see speed gains, some don't. The percieved gains depend on the controller and type of hard drive, and BIOS settings.
Switching between these settings in BIOS in a live system (after windows set up drivers..) is begging for trouble.

Dear gentlebeings,
I am sure we do not want moderated submission approval when a user wants to submit a "testpack", but I also realise that having 3rd party DriverPacks ftp access code in the "public" has caused a few "mishaps" when non-team updated. (I mean the instances when non-team removed older releases.).

Over two months ago I looked at a 3dr party pack and saw a path-hog which is, to me, sign of ineptitude and totally in disregard to what a clean tested pack should be.
We do understand enthusiasts.
We should not allow that enthusiasts simply add their driver to a pack when it should have been an update (which means the Developer did not look at other content, across ALL DriverPacks.)
We should also not allow the wild growth of folder path names.
(a long name folder with long name nested folders is a poor substitute to proper update of the supported device list.)

I am not sure about how we can teach people to do it in a proper way.

We will eventually have to use a Dbase of sorts.
Of that I am sure.
the weakest point (and you have no idea how many hours of work went into supported device list on main DriverPacks..) is the Third Party DriverPacks supported devices list.
It will probably have to be get done by volunteers in the team. But, it will have to be teamwork.

A team-member looking at the collections and looking at a submission before approving a release (so it gets linked to in main 'sticky") can question and remedy the work.
I think nobody here wants to add a driver which creates issues and misery in another DP.

here is the QUESTION.
Which driver?
do you have a LINK to it?

Hi,
I use DriverPacks primarily on disc based install. I wonder about the universal image utility you used.
Siginet's autoimage is recommended.

I have to say that DriverPacks mass storage will never be fully perfect.
Let me rephrase that.
DriverPacks mass storage cannot have ALL drivers and be perfect because some drivers just won't work no matter what we try.

my main machine motherboard decided to quit on me.
I had to look for a motherboard with similar raid capabilities to get access to the two data arrays. (all data still readable in this more modernn mobo, thank god.)

Hi time we get repair sorted out.
system drive went 07 when I migrated it, so I set up on a blank.
(I had not used M1 KTD when I set up that machine so long ago. I think M1 ktd -short'path'ed- is capable of surviving a mishap like this.)

C400?
bios is set to IDE? as default?

we need proof it is supported or not.
load order can also prove our INI setting load order musses ((fukks )) it up.

265

(9 replies, posted in Installation Platforms)

how?

HI C400

Question 1;
Have you tried the link to latest testpack yet?

Question 2;
Have you tried to determine what driver this aspire 5100 uses? (if you can, please link to it.)

Question 3;
This for the the geeks ballroom.
The real oddbal is for geeks. Have you tried find out out what INI edit can do for you? Load order and/or elimination can help us find out about conflicts better than any database match can.
(( we sometimes read about conflicts and then do not get the detail. We have learned that duplicates are not the ONLY worry. ))

267

(9 replies, posted in Installation Platforms)

hi
that is how I used to do this for my MSDN DVD..

I already had the bootfiles which offer me the choice of what I want to install, so this worked for me.
I hope I find the time to test the DriverPacks BASE multiboot function for real..
(Making the build offer you the choice sounds like the toughest part.)

268

(9 replies, posted in Installation Platforms)

16 januari
MSDN WITH RAID SUPPORT during TXTmode
first webblog article ever, here goes..

SLIPSTREAMED MSDN DVD with RAID support and other drivers integrated.

This post is about MSDN DVD versions (with the subscriber DVD's as source)

The intent was to make the DVD boot WITH RAID SUPPORT during TXTmode.

The DVD has a choice of FIVE operating systems. This is about the 32 bit versions.

XP; XP home sp2, XP pro sp2, Media Center Edition 2005  and SERVER; 2003 standard and enterprise.

I slimmed down the source.

For this DVD, The ISO files are not needed. (You can Zap them, or don't select these folders when you burn your compilation) .

For all XP versions; Migration tools folders were zapped. (or not selected.)

One needs only ONE support folder, so I moved the NTbackup folder one finds in Home into support, and called it HOME_NTbackup, then moved this support folder out of Home. I decided to keep one VALUEADD folder.
I now find support and valueadd folders in the folder where the three XP versions are in..

Another note, for MCE 2005, content of disc2 was moved to disc1. This was done because MCE setup asked for disc2 which interupted unattended.
note >>It was difficult to browse it to disc 2, so I changed that layout.
TIP, when you don't do that, and it asks for disc 2, just change the 1 to 2 in the line, that works easier than browse. smile

If you want unattended, put your WINNT.SIF files in the i386 folder.

Next came the real work.

1; N-Lite; Nlite out unused languages and keyboards in all five windows versions.

2; RVM; Slipstreamed Hotfixes and addons to MCE2005 and the XP versions. I did NOT DO server.

3; DPs_Base; Slipstream all driverpacks to each of the five versions. (method 2, select all button, KTD off, and QSC OFF.)

Then I moved one of the five OEM folder to ROOT of DVD (These folders have the same content, but after DPs_Base was used the setup process wants the OEM folder in ROOT.) I then deleted the other four unneeded copies of the OEM folders.

The tricky part was to get the textmode drivers work on all five.

Root of source has five small folders. They contain "textmode" content.

2ENL (enterprise 2003 dutch)

2SNL (standard 2003 dutch)

XHNL (home)

XMNL (MCE2005)

XPNL (pro)

COPY and OVERWRITE the most recently added/modified files from the respective i386 folders to their corresponding "textmode" folder.

Do not copy the driver.CAB.. This was done while sorted on date in detail view... (btw, RVM updated that file, not DPsBase.)

Then COPY and OVERWRITE the *.SY_ files from the i386 folders to the corresponding "textmode" folders. (sorted on TYPE in detail view) This is done so textmode will work.  Over a hundred additional mass storage devices get added to avoid F6 at boot.

4; prepare for burn.

Use isobuster to get the bootfiles off the source DVD.

Use nero to burn your compilation.

Use the bootfile from the MSDN DVD, no floppy emulation, sectors set to 4. Hex is 07C0.

No multisession, disc at once, finalise.. And burn.

Once you licked it, it sounds sooooo simple...

269

(10 replies, posted in DriverPack WLAN)

link fixed

Hi
you can use this test pack.
Several people have been using it, and the only thing I see is that we was asked to update the VIA hyperion driver.

I was abroad for a while and felt like I could use some rest.
I will probably do the Via REQuest soon, and we may be able to test and then get it to release before end of June.

271

(23 replies, posted in Software)

hi
When I looked at the HWIDs I saw two sound HWID lines.
the first one almost at the top.
PCI\VEN_1002&DEV_AA10&SUBSYS_0561107B&REV_00\4&239D83FF&0&0108: Microsoft UAA Bus Driver for High Definition Audio
and then this one.
PCI\VEN_8086&DEV_284B&SUBSYS_0561107B&REV_03\3&B1BFB68&0&D8 : Microsoft UAA Bus Driver for High Definition Audio

the ATI graphics drivers have HDMI (w/i sound for TV out?).
I had some trouble installing ATI HDMI drivers not too long ago and now think of it as a problematic installer.

the other is intel's.
We had some issues with IDT in the past.. sad

Thank god there is no modem in there.

272

(8 replies, posted in DriverPack LAN)

for google sake, let's post it again.
I will say this.. You will eventually spot the problems we created while we tried to solve a puzzle in this match up.
- - - - -
NVIDIA homework on LAN
(could still have errors and could have wrong ideas.)

<<<<< <<<<< means there is a secondary match with the corresponding controller for the PCI HWID in the same driver

example
{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV07DC
PCI\VEN_10DE&DEV_07DC  <<<<< <<<<  because 07DC matches (as seen in 16.08)

When a combination like this is in a driverset, it should be compared to other combinations
In the ideal world, the newer combo has to be kept.

I think that when a PCI has no matching NVNET_DEV line in same driver set, and in an other you see it has, the combination should not be broken.
I also think that in such case, the PCI HWID without NVNET_DEV match must be commented.

You will find PCI HWIDS like PCI\VEN_10DE&DEV_XXXX without such ..bbf5}\NVNET_DEVXXXX tied to it.
And you will also find ..bbf5}\NVNET_DEVXXXX lines with NO PCI\VEN.. tied to it.

PLEASE always try to find the newest possible combos.

-----------------------
MUST BE USED  LOCATED IN NV6

nforce_winxp_16.08_international_whql.exe
nVIDIA nForce 630i/610i ForceWare Driver 16.08 WHQL Windows 2000/XP International
nForce 610i / nForce 630i / GeForce 7150 / GeForce 7100 / GeForce 7050 
Version: 16.08 Release Date: 10.12.2007
Operating System: Windows XP (32-Bit) Language: English (International) 
File Size: 90.6 MB

Ethernet Driver (v67.64) WHQL
CAN (supposedly) support

see 16.08 (v67.64)

{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV07DC

; PCI\VEN_10DE&DEV_008C (look at 5.10 and 5.11)  >> see (5.11) (4.82)
; PCI\VEN_10DE&DEV_00DF (look at 5.10 and 5.11)  >> see (5.11) (4.82)
; PCI\VEN_10DE&DEV_0038 (look at 5.10)   >> see 5.11 (v4.82)
; PCI\VEN_10DE&DEV_0057  >> see 9.53 (v60.24)
; PCI\VEN_10DE&DEV_0269  >> see 9.46 (v67.67)
; PCI\VEN_10DE&DEV_0373  >> see 9.53 (v60.24)
PCI\VEN_10DE&DEV_0389
; PCI\VEN_10DE&DEV_03EF >> see MCP61 (v65.21)
PCI\VEN_10DE&DEV_03E6
PCI\VEN_10DE&DEV_0452
PCI\VEN_10DE&DEV_0453
; PCI\VEN_10DE&DEV_054E  >> see 14.10 (v65.65))
PCI\VEN_10DE&DEV_054F
PCI\VEN_10DE&DEV_0086
PCI\VEN_10DE&DEV_00E6
PCI\VEN_10DE&DEV_0037
PCI\VEN_10DE&DEV_0056
PCI\VEN_10DE&DEV_0268
PCI\VEN_10DE&DEV_0372
PCI\VEN_10DE&DEV_03E5
PCI\VEN_10DE&DEV_03EE
PCI\VEN_10DE&DEV_0450
PCI\VEN_10DE&DEV_0451
; PCI\VEN_10DE&DEV_054C   >> see 14.10 (v65.65))
PCI\VEN_10DE&DEV_054D
PCI\VEN_10DE&DEV_07DC  <<<<< <<<<
PCI\VEN_10DE&DEV_07DE
PCI\VEN_10DE&DEV_07DD
PCI\VEN_10DE&DEV_07DF
PCI\VEN_10DE&DEV_0760
PCI\VEN_10DE&DEV_0761
PCI\VEN_10DE&DEV_0762
PCI\VEN_10DE&DEV_0763
PCI\VEN_10DE&DEV_0AB0
PCI\VEN_10DE&DEV_0AB1
PCI\VEN_10DE&DEV_0AB2
PCI\VEN_10DE&DEV_0AB3

--------------------------------------------------
MUST BE USED  LOCATED IN NV6A (NEW folder in 27/05/2008)

14.10_nforce_630a_winxp_english_whql.exe

nForce 630a - Windows XP/2000
Version: 14.10 Release Date: May 3rd, 2007
WHQL Certified English
File Size: 69.3 MB
Installation Notes:
Installation of DirectX 9.0 or higher is required in order to use NVMixer.
Windows XP/2000 Driver Versions
Ethernet Driver (v65.65) WHQL


{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV054C
PCI\VEN_10DE&DEV_054C <<<< <<<<

{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV054E
PCI\VEN_10DE&DEV_054E <<<< <<<<


----------------------------------------------
; 8.44_nforce_650i_winxp32_international.exe
; nForce 650i Ultra - Windows XP/2000 (32-bit)
; Version: 8.44  Release Date: April 27, 2007
; WHQL Certified English, File Size: 69.3 MB
; Release Notes
; WHQL driver package and NVIDIA nTune 5.05.38.00 for nForce 650i Ultra motherboards.
;
; Ethernet Driver (v67.15) "WHQL"
; Network Management Tools (v67.27)
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269 >> see (9.46) (v67.67)
; PCI\VEN_10DE&DEV_0269 >> see (9.46) (v67.67)
----------------------------
; 8.43_nforce_650i_winxp32_international.exe does not include Ntune,
; which is the ONLY difference with 8.44_nforce_650i_winxp32_international.exe
------------------------------
;
; nForce4_intel_8.22__whql.exe
; nForce 570 SLI Intel Edition - Windows XP/2000 (32-Bit)
; nForce4 SLI XE and Ultra Intel Edition - Windows XP/2000 32-Bit
; nForce4 Intel Edition 
; Version: 8.22 Release Date: January 17, 2006
; Operating System: Windows XP/2000 32-Bit Language: English (International) 
; File Size: 35.4 MB
; Notes: WHQL driver package for nForce 570 SLI /SLI XE and Ultra Intel Edition motherboards.
; Release Notes: First driver release to support nForce4 XE motherboards.
;
; Windows XP/2000 Driver Versions:
; Ethernet NRM driver version 5.09 (WHQL)
; Network management tools version 5.09
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269 (see 8.44)  (v67.15) >> see (9.46) (v67.67)
; PCI\VEN_10DE&DEV_0269 (see 8.44) (v67.15) >> see (9.46) (v67.67)
;

--------------------------------------
;
; 9.16_nforce_win2k_international_whql.exe
; Nforce 590 SLI (AMD), nForce 570 SLI/570/550  (AMD)
; nForce 570 SLI/570/550 
; Version: 9.16 Release Date: June 28, 2006
; Operating System: Windows XP/2000 (32-Bit) Language: English (International) 
; File Size: 35.6 MB
; Release Notes:
; WHQL driver package for nForce 590 SLI // 570 SLI, nForce 570 Ultra, nForce 550 motherboards.
;
; Windows 2000 Driver Versions:
; Ethernet Driver (v55.21) "WHQL"
; Network Management Tools (v55.23)
; notes;
; The online descriptions do NOT mention AMD.
; One knows which product was selected, and makes extra notes..
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373 (see 9.53) (v60.24) >> see (9.64) (v67.74) >> see (9.46) (v67.67)
; PCI\VEN_10DE&DEV_0373
;
-------------------------------------------
  (removed from NV5A)

; Nforce 590 SLI (AMD)
; 9.35_nforce_winxp_international.exe
; Version: 9.35  Release Date: June 28, 2006
; Operating System: Windows XP (32-Bit) Language: English (International) 
; File Size: 33.8 MB
; Release Notes:
; WHQL driver package for nForce 590 SLI motherboards.
; Windows XP Driver Versions:
; Ethernet Driver (v60.15) "WHQL"
; Network Management Tools (v60.18)
;
; notes; The online descriptions do NOT mention AMD.
; One knows which product was selected, and makes extra notes..
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373 (see 9.53) (v60.24) >> see (9.64) (v67.74) >> see (9.46) (v67.67)
; PCI\VEN_10DE&DEV_0373


---------------------------------------------
MUST BE USED  LOCATED IN NV5A (replaces 9.35 60.15)

9.53_nforce_680i_winxp_international_whql.exe
files for nForce 590 SLI Intel Edition - and nForce 680a SLI - Windows XP (32-Bit) are all IDENTICAL to  nForce 680i SLI/680i LT SLI
(Package downloads have other DATE, but content are binary identical.)
nForce 680i SLI/680i LT SLI - Windows XP (32-Bit)
nForce 680a SLI - Windows XP (32-Bit)
nForce 590 SLI Intel Edition - Windows XP (32-Bit)

Version: 9.53 Release Date: 8.11.2006
November 8, 2006 WHQL Certified WHQL driver package for nForce 680i SLI/680i LT SLI motherboards.
Language: English (International) 

Version: 9.53 Release Date: October 13, 2006 WHQL Certified
Release Date: 16.10.2006 Operating System: Windows XP (32-Bit)
Language: English (International) 
This WinXP nForce (C55/MCP55) driver package consists of the following components:

Ethernet Driver (v60.24) "WHQL"
Network Management Tools (v60.26)

{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057
PCI\VEN_10DE&DEV_0057 <<<< <<<<

{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373 ( look at 9.64 (v67.74))  >> see (9.46) (v67.67)
PCI\VEN_10DE&DEV_0373  >> see (9.46) (v67.67)



---------------------------------------------
;
; 12.12_nforce_520_winxp_international_whql.exe 
; nForce 520/560 - Windows XP/2000 32-Bit
; Version: 12.12 Release Date: January 26, 2007
; WHQL Certified  English File Size: 45.9 MB
; Release Notes: WHQL driver package for nForce 520/560 motherboards.
; Windows XP Driver Versions:
; Ethernet Driver (v65.44) "WHQL"
; Network Management Tools (v65.44)  (see version 12.15)
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0450 (see 12.15) (v67.49)
; PCI\VEN_10DE&DEV_0450
;
-------------------------------------------------
MUST BE USED located in NV5

12.15_nforce_520_winxp_international_whql.exe
nForce 520/560   
Version: 12.15 Release Date: July 24, 2007
Operating System: Windows XP/2000 32-Bit Language: international English
File Size: 81.6MB Release Notes:
WHQL driver package for nForce 520/560 motherboards.
Windows XP/2000 Driver Versions:
Ethernet Driver (v67.49) "WHQL"
Network Management Tools (v65.44) “Sedona”

{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0450
PCI\VEN_10DE&DEV_0450 <<<<< <<<<<

-----------------------------------
MCP61 MUST BE USED  LOCATED IN NV4 (replaces 6.86 (50.25))

8.26_11.09_nforce_winxp_international.exe
nForce 430/410/405/400 
v 8.26 for nForce 430 (MCP51), 410
v 11.09 for 430 (MCP61), 405, 400
Release Date: January 5, 2007 Operating System: Windows XP/2000 32-Bit
Language: English (International)  File Size: 88.5 MB

Release Notes
WHQL driver package for nForce 430, nForce 410, nForce 405, and nForce 400 motherboards.

; nForce 430 (MCP51), 410
; Ethernet Driver (v50.23) "WHQL"
; Network Management Tools (v50.23)
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269 (see 8.44) (v67.15) >> see (9.46) (v67.67)
; PCI\VEN_10DE&DEV_0269 >> see 9.46 (v67.67)

Driver Versions
nForce 430 (MCP61), 405, 400
Ethernet Driver MCP61 (v65.21) "WHQL"
Network Management Tools MCP61 (v65.23)

{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV03EF
PCI\VEN_10DE&DEV_03EF  <<<<< <<<<

---------------------------------------
; 8.26_nforce_winmce_international.exe
; nForce 430/410 - Windows XP Media Center Edition
; Version: 8.26 Release Date: June 22, 2006 WHQL Certified
; Driver Versions
; Ethernet Driver (v50.23) "WHQL"
; Network Management Tools (v50.23)
; (for which see 8.26_11.09_nforce_winxp_international.exe \ MCP51)
--------------------------
;
; we probably do NOT want to use this one.
;
; bussiness platforms
; nsip20101_2k_xp.zip
; 233MB
;
; This Win2K/XP nForce driver package consists of the following components:
; Ethernet Driver (v54.05) "WHQL"
; Network Management Tools (v54.05)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C >> see (7.15) (4.82)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF >> see (7.15) (4.82)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038 >> look at 5.10, 5.11 >> see (7.15) (4.82)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 >> see 9.53 (v60.24)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373 >> see (9.46) (v67.67) >> see (9.64) (v67.74)

; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0389
; (not tied to any PCI in this driver.
; However, See 16.08 (v67.64) which is located in NV6 for this PCI.. This may cause a crash.)

; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269 >> look at 8.44 (v67.15) with generic PCI\VEN_10DE&DEV_0269 >> see (9.46) (v67.67)
PCI\VEN_10DE&DEV_0269&SUBSYS_CB8410DE
PCI\VEN_10DE&DEV_0269&SUBSYS_E0001458
PCI\VEN_10DE&DEV_0269&SUBSYS_72521462
PCI\VEN_10DE&DEV_0269&SUBSYS_72071462
PCI\VEN_10DE&DEV_0269&SUBSYS_816A1043
PCI\VEN_10DE&DEV_0269&SUBSYS_81D31043
PCI\VEN_10DE&DEV_0269&SUBSYS_0D00105B
; above are unique specific PCI HWIDS, but look at (9.46) (v67.67) with generic PCI\VEN_10DE&DEV_0269 >> see (9.46) (v67.67)
; >> 5.10 has PCI devices listed for DEV0038
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269
; (the unique specific PCI may benefit if this driver is used. Have to get an URGENT REQUEST before you consider adding this one.)

--------------------
; (REMOVED FROM NV4)
; 6.86_nforce_win2kxp_international_whql.exe
;
; nForce4/500 series - Windows 2000/XP
; Version: 6.86
; Release Date: July 7, 2006
; WHQL Certified
; English
; File Size: 43.1 MB
;
; Windows XP/2000 Driver Versions
; Ethernet Driver (v50.25) "WHQL"
; Network Management Tools (v50.19)
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C >> see 5.11 (4.82)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF >> see 5.11 (4.82)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038 >> see 5.11 (4.82)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 >> see 9.53 (v60.24)
; PCI\VEN_10DE&DEV_0057 <<<< <<<<  >> see 9.53 (v60.24)

; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269 >> see (9.46) (v67.67)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373 >> see (9.46) (v67.67) >> see (9.64) (v67.74)
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0389 >> see bizz 54.05
;
;
;
-----------------------------------------------
; http://www.nvidia.com/object/nforce_nf4 … chive.html
;
; nForce4_intel_7.15__whql.exe
;
; nForce4 SLI Intel Edition - Windows XP/2000 32-Bit
; Version: 7.15 Release Date: November 2, 2005 WHQL Certified English File Size: 34.2 MB
; Release Notes: General compatibility fixes for nForce4 SLI Intel Edition motherboards.
;
; Windows XP Driver Versions:
; Ethernet NRM driver version 4.82 (WHQL)
; Network management tools version 4.88
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C
; PCI\VEN_10DE&DEV_008C <<<< <<<<
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF
; PCI\VEN_10DE&DEV_00DF <<<< <<<<
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038
; PCI\VEN_10DE&DEV_0038 <<<< <<<<  (see 5.10) (also see 16.08) (v67.64))
;
; ; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057  >> see 9.53 (v60.24)
; ; PCI\VEN_10DE&DEV_0057 <<<< <<<<
;
; ; PCI\VEN_10DE&DEV_0269  (see 5.10, 5.11, bizz and 8.44)   >> see (9.46) (v67.67)
;
; this is actually same as the driver found in NV3 and content is identical with 5.11\

--------------------------------------------------------
;
; 6.70_nforce4_pro_international_whql.exe
;
; nForce Professional - Windows XP/2000 (32-Bit)
; Version: 6.70 Release Date: March 8, 2006 WHQL Certified
; international English File Size: 39.9 MB
;
; Release Notes
; General compatibility fixes for nForce Professional motherboards.
;
; Windows XP/2000 Driver Versions
; Ethernet NRM driver version 4.82 (WHQL) (see nForce4_intel_7.15__whql.exe) >> see 5.11
; Network management tools version 4.88 (see nForce4_intel_7.15__whql.exe)
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF
; PCI\VEN_10DE&DEV_0038
; PCI\VEN_10DE&DEV_0057
; PCI\VEN_10DE&DEV_008C
; PCI\VEN_10DE&DEV_00DF

; PCI\VEN_10DE&DEV_0269 (see 5.10, 5.11, bizz and 8.44)   >> see (9.46) (v67.67) (See NV7)

--------------------------------------
; (I still cannot see how this driver can work)
;
; Nforce 1 and 2 (and 3)
;
; nForce_5.10_WinXP2K_WHQL_international.exe
;
; Windows XP - Unified Driver
; Version: 5.10
; Release Date: September 17, 2004
; International
; File Size: 30.5 MB
; WHQL Certified
;
; Release Notes
; WHQL certified kit
; Unified drivers with support for nForce, nForce2, and nForce3 products, including support for dual-processor systems.
;
; Ethernet driver 4.42 (WHQL)
; note>> PreNRM 4.16 ( which is same as in 5.11\preNRM and 7.15)
; note>> Network management tools version version unknown
;
; 5.10_\Eth_4.42\nvenetfd.inf    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038 (see bizz, where it should be remarked))  >> see 5.11 (v4.82)
; 5.10_\Eth_4.42\nvenetfd.inf    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 >> see 9.53 (v60.24)
; 5.10_\Eth_4.42\nvnetbus.inf PCI\VEN_10DE&DEV_008C (see 16.08(v67.64) >> see 5.11 (4.82)
; 5.10_\Eth_4.42\nvnetbus.inf PCI\VEN_10DE&DEV_00DF >> see (5.11) (4.82)
;
; 5.10_\Eth_4.42\PreNRM\Win2K\nvenet2k.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_0038  >> see (5.11) (PreNRM 4.16)
; 5.10_\Eth_4.42\PreNRM\Win2K\nvenet2k.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_0057  >> see 9.53 (v60.24)
; 5.10_\Eth_4.42\PreNRM\Win2K\nvenet2k.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_0269 (see bizz and 8.44)  >> see (9.46) (v67.67)
;
; 5.10_\Eth_4.42\PreNRM\WinXP\nvenetxp.inf 01/29/2004, 4.1.6    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C >> see 5.11 (PreNRM 4.16)
; 5.10_\Eth_4.42\PreNRM\WinXP\nvenetxp.inf 01/29/2004, 4.1.6    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269 (see bizz and 8.44) >> see (9.46) (v67.67)
; 5.10_\Eth_4.42\PreNRM\WinXP\nvenetxp.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_0269 (see bizz and 8.44)   >> see (9.46) (v67.67)
;
------------------------
MUST BE USED (this one is currently in NV3)

Nforce 3

nForce_5.11__whql.exe

nForce3 - Windows XP/2000 32-bit
Version: 5.11
Release Date: November 2, 2005
WHQL Certified
International
File Size: 35.6 MB

Release Notes
General compatibility fixes for nForce3 motherboards

Driver Versions
Win2K_WinXP ethernet driver version 4.16 (WHQL) in PreNRM
Ethernet NRM driver version 4.82 (WHQL) (identical to nForce4_intel_7.15__whql.exe)
Network management tools version 4.88 (identical to nForce4_intel_7.15__whql.exe)
PreNRM 4.16

5.11_nforce\v4.16\nvenetfd.inf  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C
5.11_nforce\v4.16\nvnetbus.inf PCI\VEN_10DE&DEV_008C <<<< <<<<

5.11_nforce\v4.16\nvenetfd.inf  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF
5.11_nforce\v4.16\nvnetbus.inf PCI\VEN_10DE&DEV_00DF  <<<< <<<<

5.11_nforce\v4.16\nvenetfd.inf  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038
5.11_nforce\v4.16\nvnetbus.inf PCI\VEN_10DE&DEV_0038

5.11_nforce\v4.16\nvenetfd.inf  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057
5.11_nforce\v4.16\nvnetbus.inf PCI\VEN_10DE&DEV_0057  <<<< <<<<

; 5.11_nforce\v4.16\nvnetbus.inf PCI\VEN_10DE&DEV_0269  >> see 9.46 (v67.67)

5.11_nforce\v4.16\PreNRM_4.82\Win2K\nvenet2k.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_01C3
5.11_nforce\v4.16\PreNRM_4.82\Win2K\nvenet2k.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_0066
5.11_nforce\v4.16\PreNRM_4.82\Win2K\nvenet2k.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_00D6

5.11_nforce\v4.16\PreNRM_4.82\WinXP\nvenetxp.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_01C3
5.11_nforce\v4.16\PreNRM_4.82\WinXP\nvenetxp.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_0066
5.11_nforce\v4.16\PreNRM_4.82\WinXP\nvenetxp.inf 01/29/2004, 4.1.6    PCI\VEN_10DE&DEV_00D6


http://www.nvidia.com/object/nforce3_winxp_5.11.html
5.11_nforce\v4.16\nvenetfd.inf  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF is used in exception
Main 5.11 folder content is identical to 7.15 which is NRM 4.82, and this 5.11 driver has added an older PreNRM v4.16 .


-----------------------------------
;
;
; (2003_only) found out I had old version, this is a NEWer version.. sad
;
; nForce Professional 3000 Series   
; Version: 9.24
; Release Date: October 11, 2007
; Operating System: Windows Server 2003
; Language: U.S. English
; File Size: 32.8 MB
; WHQL driver package for nForce Professional 3000 Series motherboards
;
; Ethernet Driver (v67.64) "WHQL"
; Network Management Tools (v67.64)
;
; {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373
; PCI\VEN_10DE&DEV_0373 (look at 9.64 (v67.74)  >> see (9.46) (v67.67)
;
;
--------------------------
9.46 MUST BE USED located in NV7 (replaces 9.64 (v67.74))
; downgraded because it supports more.

9.46_nforce_winxp_international_whql.exe
Version:9.46
Release:17 Dec 2007
Update:19 Dec 2007
9.46_nforce_winxp_international_whql.exe
File Size:47.24 Mb

nVIDIA nForce 780i SLI ForceWare Driver 9.46 WHQL Windows XP x32 International.
Windows XP Driver Versions:

Ethernet Driver (v67.67) "WHQL"
Network Management Tools (v67.67) "Sedona"

10/12/2007, 67.6.7    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269
10/12/2007, 67.6.7    PCI\VEN_10DE&DEV_0269 <<<< <<<<
10/12/2007, 67.6.7    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373 >> look at (9.64) (v67.74)
10/12/2007, 67.6.7    PCI\VEN_10DE&DEV_0373 <<<< <<<<

; this driver should cover what the "newer" 9.64 covers, and covers more.
; (9.46 can replace 8.44, and supports 9.64 as well)
;
; 9.64 cannot replace 8.44 nor 9.46
;
; 9.46 MUST BE USED
---------------------------
; (could be used but does not replace 9.46)
;
; REMOVED FROM NV7
;
; 9.64_nforce_winxp_english_whql.exe
; nForce 790i Ultra SLI
; nForce 790i SLI
; nForce 780i SLI
; nForce 680i SLI
; nForce 680i LT SLI
;
; Version: 9.64
; Release Date: March 18, 2008
; Operating System: Windows XP 32-Bit
; Language: U.S. English
; File Size: 50.0 MB
;
; Windows XP Driver Versions:
; Ethernet Driver (v67.74) WHQL
; Network Management Tools (v67.74) "Sedona"
;
; 12/24/2007, 67.7.4    {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0373
; 12/24/2007, 67.7.4    PCI\VEN_10DE&DEV_0373
;
; DO NOT USE until a BETTER update comes along.
--------------------

I will repeat, these findings are not the bible.
I had to eyeball. I was using techniques and some common sense just like any good Watson would.
I never said Watson was equal to Holmes. Holmes is a nobody. He has to explain the puzzle. Watson solves no puzzle without getting clues.

(There is no such thing as Hari Seldon.)

Hi SamLab,
yesterday I looked at ATI catalyst driver changelog txt and got sad.

It looks like you pinned some of those quite accurately.

changelog in catalyst 8.6 is interesting.

sad
((.. unresolved issues with via and other hardware like SiL 3112.. We should look up if nForce chipsets are in their changelogs as well.))

275

(76 replies, posted in DriverPack Mass Storage)

Hi C400,

most testers have learned ways to find the conflicting driver.
Load order can change result.
Not loading a 'suspect' competing driver can also change result.
HWIDs Readouts help, testers with the hardware can read the %SystemRoot%\setupapi.log and %SystemRoot%\DPsFnshr.log and when such logs are used to single out the problem competitor 'by smart halving' or by 'load order changes' they (the tester doing IT..) can help team to find the solution to this puzzle.

I hate puzzles.
Today I read a request for a yamaha driver and I looked at the microsoft update driver for it. I find a M$ WU driver WHQL for yamaha.. I look at the HWIDS and see a SiS competitor with exact same HWID.
Nvidia and many other drivers are re-using same HWID for different hardware.
What is worse is that there are also ill written drivers competing non-related components.
(real hardware based conflicts/non-resolvable?)

I see that the latest catalyst driver has a few unresolved issues with VIA and SiLicon in the catalyst changelog.
Erm? HELP?
I really mean 'WE NEED HELP'.