Bâshrat the Sneaky

Err... I guess it contains the inf files for driver installations. I would be VERY suprised if it contained 'info about the things you can choose to install or not to install.."

Added to the list And.. you're welcome

Hey didn't notice... But I almost asked the exact same question in the DriverPack LAN topic. Please use devcon to determine the PCI DeviceID of your nForce with built-in Firewall. I'll take care of the rest then!

If anyone can point me to a method how to determine if the nVidia Network Access Manager could be installed, that would be great. I'd prefer a driverfile that only exists if it's available. But probably that won't be possible. Anyone who could post his DeviceID here? Untill then I'll remove it from DriverPack LAN.

Yes, I finished debugging! The plan was to use the txtsetup.oem method for the NVRAID controller, as well for many others. Eventually I only used that method for the 3ware controllers. Now I'm determining the filesizes of all DriverPacks when using Method 1 (with CAB compression!). Then I'll upload everything and update the website. I think you can expect everything within 4-7 hours. Doing everything relaxed now!

eh???? Is it just me, or is the style not so different at all? It looks VERY much like the old style... Only some lay-out changes, some extra options... and the stars... they're exactly the same here!

YES Finally complete... That DriverPack MassStorage wasn't that easy after all... BUT it's completely working now... I worked some 8 hours on it today only... And again djbe has been VERY helpful! : (thanks!!!) So I gues you guys understand I'm somehow *TIRED* now... What I still have to do tomorrow: -update website (takes about 20 mins) -add the new intel extreme graphics drivers (+- 10 mins) -last testing (+- 60 mins) -uploading (120 mins or longer, will do something else in the mean time of course) -update the posts here (+- 20 mins) -DONE So a bit more patience... But you will be AMAZED B)

Not when you PM.... Only when you start a topic or when you reply to a topic.

hehe Debugging now... (only the DP MassStorage part) note: DriverPack MassStorage: decompressed: 9.60 MB Method 1: 4.19 MB (yes, with CAB compression ) Method 2: 2.45 MB

link is fixed.

SEARCH! download vidchng cmd utility usage: 1365VidChng.exe 1024x768x32@85 -q pretty self-explanatory...

Very clear guide! Bâshrat the Sneaky has added a bookmark!

... and update your nLite... Currently we're at 0.99.7, you're using 0.99.5

Did you search? > probably you have Did you try to find out WHICH INSTALLER IS USED? > probably you haven't. Please try to determine which installer is used! Then use the correct switches and voila you're set! in the guide...

1. SEARCH!!! It has been asked soooo many times! Simply use a .reg file and apply it at cmdlines.txt, so all users will inherit this tweak. 2. I don't know if that's possible... But again: please search...

Didn't know about that.... I was going to say: use double backslashes in the path, that has worked for me in the past.

Done almost all drivers! Also txtsetup.sif modifying is completely automated. (take a look in RUN_ME.CMD when I released it and you'll see it was a hell of a job... currently 1500+ lines....) After all I used the old method (txtsetup.sif editing , add .sy_ file to I386, add in $OEM$\$1\<PnPdrivers>), because this method is the 'cleanest' method. This way everything really becomes part of the UWXPCD, as if it was by default. The only ones left are the 3ware's.... And now I know why you couldn't integrate them with the method described above: they need TWO .sys files, while the method above only supports one... Funny enough it seems not all drivers who have 2 .sys files or additional .dll files, require all these .sys and .dll files to load: often these extra files are only required for the utilities. I think (and really *HOPE*) I can release them today. But before I release everything, I will do some testing. Most things are already tested, so that shouldn't take to much time...

Thanks to all and Russian added to the list

It is a application, so it won't install by itself. You'll have to find a file that only exists when this nForce built-in firewall is available: IF EXIST %SystemRoot%\system32\driver.sys START /WAIT Firewall_Setup.exe /Silent_Installation_Switches

Or you can find this info at here, you should have looked in the 'read first' sticky before asking! EDIT: or Intel's instructions for the iaStor driver

Thanks! But it won't be for very soon! I'll do it brand-by-brand... And DriverPack Chipset is more important.

And where exactly are so many people complaining about it? Read through this topic and you'll see it works for almost everybody....

Well, I *do* know about one option: using the devcon utility. I think I've once read that someone accomplished an unattended XP upgrade installation with this. But of course this is only doable when you have system that have quite identical hardware....

In your case it might be easier to use the command suggested above, because it's only a limited list of printers.

That's quite impossible... *BUT* I suggest you add that Belkin Utility then... If you want you can use an IF EXIST statement to only install that utility when this driver is found. i.e.: IF EXIST %SystemRoot%\system32\<Linksys_Driver>.sys START /WAIT <Belkin_Utility_Setup>.exe /switches_for_silent_installation