Bâshrat the Sneaky

slimzky, did this happen with the newest version? That is DriverPacks BASE V5.04.2. Topic moved to DriverPacks General Discussion

@mark49: hmmm... I don't know, never seen that suggestion before, not here, not at microsoft.com... @dynaletik: thanks for that first one, that's indeed erroneus. And about that second thing: it should indeed be removed, but I knew about that one. It was from the V5.03 version of DP MassStorage & DPs BASE, when I was trying to add support for ALL nForce IDE/RAID controllers at TEXTMODE setup, but sad ly enough that failed. @buletov: I saw your PM too and you got a reply. Well, I think I might have been wrong doing that. I'll start the conversion to the plain old method... Update can be expected tomorrow (not very difficult to do) @Dynaletik: here you misunderstand it

DriverPack Sound B V5.04.1 Download

DriverPacks Sound A V5.04.1 Download

DriverPacks WLAN V5.04.1 Download

DriverPacks LAN V5.04.1 Download

BTS DriverPacks BASE V5.04.2 Download ... with all problems fixed!

Please ATTACH the txtsetup.sif, posting it completely won't work.

Ehm I *may* have figured out the key to a successfull nvraid slipstream, that works for all cases. In the txtsetup.oem file: [Files.scsi.RAIDCLASS] driver = d1,nvraid.sys,RAIDCLASS inf = d1,nvraid.inf >>>dll = d1,nvraidco.dll<<< catalog = d1,nvraid.cat [Files.scsi.BUSDRV] driver = d1,nvatabus.sys,BUSDRV driver = d1,nvcchflt.sys,FILTER inf = d1, nvatabus.inf >>>dll = d1,idecoi.dll<<< catalog = d1, nvata.cat My point is: do you see those dll files? Well, they NEED to be copied in order to make the whole **** thing work. At least that's what *I* think. So then we make them getting copied! Could one of you guys please try it? Just put the .dll files in $OEM$\$$\system32 in your UWXPCD disc, burn it (please use a CD-RW..) and let me know. Please DON'T copy nvcoi.dll, if it first fails then try again by adding it. I'd LOVE to test it, but unfortunately I can't: I'm using a nForce 2 mobo and I don't hae any problems with it. So I hear ya guys coming: 'why don't you have any problems with it?', well that's easy, my HWID isn't listed in the txtsetup.sif file, because it isn't listed in the txtsetup.oem file. You guys MUST have a controller named "NVIDIA nForce2 Serial ATA Compatible Controller" or "NVIDIA nForce2 Parallel ATA Controller" and I've got "NVIDIA nForce2 ATA Controller" Of course these are just names and they can be changed, but this is how it *SHOULD* be named. Please test and let me know.

On which MassStorage controller are you installing? I think that's the key. Also, do you have the same error without DP MassStorage?

OK, I did a test on my pc (ASUS A7N8X-E Deluxe) now, using all latest versions and method 2, the results: Everything is _working_ (this does not mean everything gets installed) fine, BUT these are the current bugs: 1) TEXTMODE setup: nVidia nForce ATA 2 controller recognised as ATAPI => missing hwid in txtsetup.sif (in regular Windows this DOES get installed correctly, doing some research whether this IS a real bug) 2) [FIXED] GUIRunOnce: the AudioUtl.exe does not get extracted, therefor no control panel Fixed in DP Sound A V5.04.1 (2 bugs in the control panels batch file) 3) [FIXED] ethernet device not installed Fixed in DP LAN V5.04.1 (missing driverfiles: these files were not included in the nForce 4 standalone driver and I forgot to add them...) 4) [FIXED] the nVidia APU driver DID get installed, but so did the Realtek drivers Fixed in DP Sound V5.04.1 (deleted some .inf files of the Realtek driver, removed entries in a couple of .inf files, this may lead to broken WHQL driver signing) And last but not least I found another bug in DP Sound A cpls batch file, which causes that the Creative Audigy LS control panel won't get installed, Fixed: in DP Sound A V5.04.1 (cpls batch file)

WTF is this... 1) Did you apply it to a CLEAN Windows XP share? 2) Please post your ORIGINAL Windows XP (Home or Pro?) German SP2 txtsetup.sif and dosnet.inf

I don't know if that's possible... But sooo much space they don't take... And it would take again more time to recompress the DriverPack. But I'll see what I can do.

Yes, I already figured that, kalavera

@glent: with which hardware is that? Which lang of Win XP?

Yes, I'm working on that one too, didn't get it finished last night... And I still need confirmation whether the dosnet.inf file needs to be edited or not when BartPE is used... EDIT: here's the test to proove that nothing is wrong... test.cmd: @ECHO OFF REM Sets method 1 as used method (just to test SET ME=1 REM Sets the fixed parts of the commands SET C1=ROBOCOPY "M%ME%\I386_original" "I386" SET C2=/MOV /NS /NC /NFL /NDL /NP /NJH /NJS REM Screen output of the command to be executed. ECHO %C1% adpu160m.sy_ %C2% PAUSE EXIT Screen output: So if anyone can point me to the problem, please feel free... EDIT: tsjakkaaaaaaaaaaaaaaa! Finally found it... It seems that you can NOT set variables INSIDE a conditional statement (IF ( statements ) ). Strange, but it seems that was it...

Thank you, this driver will be added to DP Sound B.

grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr I included the NEWEST version. I followed the guide at the DFI forums to the letter (not that there were much changes - in fact none but adding the new files and compressing nvcchflt.sys) and still no success, while they DO have success? Does it ever end? .... Yesterday I did not have the time to test it myself (uploading takes ages @192kbps/24KBps), but I will do that today.

@kalavera: I will continue to use the OFFICIAL drivers, not hacked ones. The differences between them are VERY minimal, only support for more cards is an advantage. However, I've contacted patje, the creator of the Mobility Modder program and he's helping me with adding support for the Mobility series. Foreign languages will stay included: MANY of us are from the Netherlands, Germany, France, etc. Please don't forget them.

1) Those drivers are included in the OTHER DriverPacks That's also why DP Chipset is so small (I guess you can even say tiny). 2) Yes you can.

@kalavera: working on ATI Radeon Mobility support And I did not find the wrong link in the intro.htm... :s @erik_demon: I don't see why it shouldn't work... I'll do some more testing... @celo: you did nothing wrong

Thank you. EDIT: updating done. V5.04.1 will be uploaded later today.

WTF!!!!!! How can this be possible that it installs V5.04 again if it's no longer online??? REALLY need my sleep... cya tomorrow...

I just noticed that Marvell has updated its Yukon driver... DriverPack LAN V5.04.1 tomorrow...

:o Now I don't know anymore... will be for tomorrow...