Bâshrat the Sneaky

As I already said, I won't switch to the txtsetup.oem method after all... Because it simply can't work for all drivers.... (due to identical names). Maybe I will convert slowly to it. But for now I'm rebuilding the DriverPack MassStorage using the regular txtsetup.sif method.

Main question: would you need/want the utilities as well? If not, I would like to make it. But then I trust you, the users, to provide me with links to these drivers. I won't search for them myself, because there are SO many of them, as mentioned earlier.

secondary screen... And maybe you've got a AIW version?

I don't think everyone has a HKCU.reg

ROFL I was wondering where I got it from I guess I'm thinking to much in drivers... 4 days non-stop drivers everywhere B)

Is it a FX5600XT or a RX9600XT ?

This can't be true..... ????? !!!! Can anyone confirm this? :'(

NONE of them! iTunes... + WinDVD 6 Platinum + Nero Showtime 3 because: -iTunes has way better library features! -WMP can't play DVD's.. -Nero Showtime automatically detects subtitles, has more features, has a better interface...

Yes, I noticed, and added it to the list about an hour ago hmm.... I think you could fix that with the ASSOC command when you run it from cmdlines.txt?

Can you give me a link to the right page on their website (www.ali.com.tw)? Because I can't find it... Really sucky AND slow site... http://www.pcchips.com.tw/pccweb/index.aspx?MenuID=0&LanID=0 There's dozens and dozens of ALi drivers here. I downloaded the one and only GRAPHICS driver I could find on that site (which isn't the official site btw) and even that one was a very old nVidia driver... Any other link? Anyone? I'll add them in the next release then...

I will let the Mobility drivers out of the first release (V5.02) and I'll release an update within 1 or 2 weeks that supports the Mobility series. Of course with your help: you can verify it for me. I'll study the changes made by Omega and Patje's tool. But for now, DriverPack MassStorage is more important.

Can't you remove them with nLite?

hmm... Let's see if this problem will still be there in the new versions...

The current DriverPacks BASE isn't compatible with the old DriverPack MassStorage... I think I'll release everything tomorrow, if not tomorrow, Saturday. Of course not everything will be beta-tested by then, but everything should work fine... This time I spent ALOT more time on testing the DriverPacks BASE... And I'm quite proud of it now To give you an idea of size: uncompressed all DriverPacks are now 554.9 MB, while 7zipped they are 130.31 MB. (this is without DP MassStorage, and I have to update the Graphics DriverPacks again)

I'd suggest you use this pack for your BartPE disc, instead of mine http://home.earthlink.net/%7E1.414213563/P...eDriversNEW.htm

hmm.... I never tried that... What installer are you using? You could use a codec-pack

So are you saying it also worked with WMP10 MUI or are you asking if I could add that feature? @asbsamsf: Added

[quote name='muevelonyc' date='Feb 9 2005, 10:11 PM']sweet. This is the portion that WinPE needs to detect mass storage drivers, so this would work REALLY well! *edit* confirmed: [url="http://www.nu2.nu/pebuilder/help/drivers.htm"]http://www.nu2.nu/pebuilder/help/drivers.htm[/url] *edit2* Bashrat, might want to also look here at this driver pack that someone made for BartPE: [url="http://home.earthlink.net/%7E1.414213563/PEplugins/MassStorageDrivers/MassStorageDriversNEW.htm"]http://home.earthlink.net/%7E1.414213563/P...eDriversNEW.htm[/url] Just to compare drivers, to see if we have them all. I'm too lazy to compare it myself, but from the text, looks like a ton! Your method is better in that it'll support both PE and XP, which is what I need since I'm using PE to install XP unattended.[/quote] Now THAT's a list! I see they broke all driver signings... And they didn't remove tagfiles, txtsetup.oem files and readme's... Maybe this will be useful, but you can't directly use it.. (other file format...) EDIT: I *WILL* beat these guys (yes, it isn't one that did all the work) by providing you with more drivers

hmm... that must be an identical PCI DeviceID issue... Could you please: - specify as which EXACT Linksys controller it was installed - post your PCI DeviceID

Phew... found the bugs... I hope it's working now.. The list of DeviceIDs added is now longer than the ones of patje's tool and Omega's together! oops attached wrong file... gimme a min

I'd do it for... hmmm.... the newest PowerBook (of course the most expensive one), plus a PowerMac 2*2.5 GHz plus 2* 23" Cinema Display plus iPod Photo plus... (Yes, you're right, I'm getting obsessed by Apple ) ontopic: it really isn't that hard! Especially now the guide has been updated!

Indeed it worked quite well... The list above has changed: -3ware controllers -Intel controllers I was hoping you could provide me with a list of devices for which it DIDN'T work properly?

OK, as you guys may now I'm converting the entire DriverPack MassStorage to the txtsetup.oem method. But now I've ran into a huge problem.... You can't use any subfolders when you're using the txtsetup.oem method (all files must be placed in the TEXTMODE folder), but there are several drivers with IDENTICAL FILENAMES. At first I tought I could solve this by using subdirectories, but now I've done some more research and it seems that it's really impossible to do that... (thank you, Microsoft, for making this process such a painful job! :sarc: ) Conclusion: a complete convert is impossible. So I will use a combination of both methods: those controllers who don't work properly with the one method, will be slipstreamed with the other method! These ones will be installed with the txtsetup.oem method for sure: -NVRAID -all 3ware controllers

Thank you. That link looks great! I tried putting the drivers in the folder with all the other drivers, but my setup freezes once it reaches 100% on the detecting devices part of setup. However, I did not try expanding the already compressed files first. I'll try that and hope it works. BTW, I use svcpack for dx9c, ie6sp1, and media player 9 in addition to all the hotfixes. It works for them OK. That is why I thought it might work for installing the ti4200 drivers as well. Those are all installations for Windows components: they are an exception

You placed the files in I386\svcpack? huh? Application installs don't work properly from svpack All the info you need can be found in this topic.