Bâshrat the Sneaky

The download works, you just have to wait. There's a time indicator that says how many more seconds you have to wait.µ EDIT: took a look at your MP10SETUP.exe and if I'm right, you still have to edit the HIVEDEF.INF file, right?

It should be working fine when you're working with subdirectories... If you point to them well, no problems should exist! Are you sure you copied the drivers into the correct folders?

Very nice! I guess you want Windows to be able to decompress these drivers without problems, so you are using cab compression? So this program's main goal is to simplify the compression of driver files for in the I386 directory? P.S.: never heard of VC++ but it does exist apparently EDIT: is it difficult?

Yes there are people who used these DriverPacks in BartPE, however that's a minority. (that would be obvious...) In case you want to do that, you will also have to add the correct entries to your dosnet.inf file (only for DriverPack MassStorage)

Sorry... But I guess you can understand that would make the work even bigger...

I really can't be 'guilty as charged' (LOL), because: 1. there's no SFC_OS.dll file included in ANY of my downloads. 2. there's not at all a WMP 10 setup in my downloads. (firstly I despite WMP and secondly that would get the file size very high )

But you can disable the DriverSigningPolicy in another way as well, at least that's what I think. (came up with this myself, read nowhere about it, so I'm not sure, not tested yet) Windows XP searches the setting for DriverSigninPolicy. It looks in the HKCU and HKLM registers (also HKU\.Default?) The safest value is used. So what if we would change this default value? That would be possible: editing the HIVEDEF.INF and the HIVESFT.INF files in your I386 directory. That might make the difference IMO...

First complete DriverPack Sound. Then Update Method 2. DriverPack LAN is done, as well as a new update system, that is no longer sequential. All bugs in the method 1 batch files have been fixed.

Thank you. This was the last driver I needed for DriverPack WLAN! It now contains.... 212 drivers! That's absolutely a record to me Of course this 212 includes the driver you've uploaded. We'll see if I can add this one. (yes, surecom has sucky drivers... ) EDIT: now I've counted all .inf files: 246 of them. So I'd say that equals 246 drivers? Because each inf has at least one sys file...

Changes in Method 1 V007: -updated the OemPnPDriversPath (which was wrong) Changes in Method 2 V009: -updated the presetup.cmd (which wasn't updated with the change of 'Drivers' => 'DP')

Most of you won't be interested in this topic. The reason why I've started this topic is to improve the DriverPacks BASE. Also to prevent any more errrors. If this topic becomes dead, no problem. (this is very probable, but...) All current versions of the files will always be available at www.BTSunattended.net/DPBASE. Questions and suggestions should be posted in this topic. Current versions: -Method 1: V007 -Method 2: V009

Hehe It's indeed inthere, but it does nothing... It wasn't meant to get into the DriverPacks instructions. I have been trying to get this error flag to work, but couldn't manage to. Why would I want it? Because the RunOnceEx didn't work as it should: about 20 apps did get installed without any problems and one didn't get executed at all. So I tried this error flag, but without _any_ results. I'll remove it in the next version, but it doesn't hurt.

No offense man! How did you disable the DriverSigningPolicy? Only in your winnt.sif?

You HAVE to edit the txtsetup.sif file to get MassStorage drivers installed! Here's a guide EDIT: fixed wrong URL

I can only say it isn' caused by my DriverPacks. Are you sure you didn't use nLite?

Yes, please drop a mail and I'll mail you back with the FTP login.

And did you only disable WFP or did you also disable DriverSigningPolicy? You have to do both... WFP just prevents that you can disable DriverSigningPolicy in a easy way.

ATM I'm updating the batch files, because I have to add support for DriverPack WLAN. At the same time I'm trying to improve everything so I test everything. During one of these tests I discovered a bug :'(. For some it may be not important at all, for some it can be very important. It's this code: Patch_V004.cmd IF EXIST txtsetup.old GOTO ORIG IF NOT EXIST txtsetup.old GOTO NEW which should be: IF EXIST I386\txtsetup.old GOTO ORIG IF NOT EXIST I386\txtsetup.old GOTO NEW Due to this error, the batch file won't detect propery if you had applied my DriverPacks before. It always said 'this is the first time..'. Consequences: -If you have applied these batch files twice, then the entries to be added have been added twice. If you have applied it three times, then... and so on... :'( EDIT: this applies to BOTH methods. Quick fix: Edit it manually, as stated above. The new version should be available within days.

I did not test this yet. It's pure theory. Read the blue text . Do you understand me? I think I *have* to be wrong, because it 'look' so obvious... So I think I must be missing something. Edit: if THIS works, then I've got some other things to make this a completely new method.

I've been thinking... (hehe yes I do think ) And I'm convinced it must be possible to entirely disable DriverSigningPolicy. (so no more AutoIt script that automatically clicks 'continue anyway' when a WHQL violation screen pops up. The facts: 1. Windows looks in the registry how it should react when you try to install a driver that's not WHQL signed. It looks in the HKCU and HKLM registers (also HKU\.Default?) The safest value is used. 2. Driver Signing Policy Is Automatically Elevated for Unsigned Drivers This behavior occurs because your computer is configured to display a warning message whenever an installation program tries to install a device driver that does not have a digital signature. Windows automatically raises the driver signing policy from Ignore to Warn whenever an installation program tries to install a device driver that does not have a digital signature. This is a function of Windows File Protection to promote the overall stability of the operating system. source Conclusion: So we'd have to disable WFP completely in order to install _any_driver_ without problems. So how could we do that? Raverod provides a patched SFCOS.dll Here's the topic Or just use nLite to patch it! Now the question: am I really missing some point here or hasn't anyone noticed this option?

What drivers are you adding anyway? Are they WHQL signed? Because if they aren't, and if Windows has older ones but signed ones, then these will be used...

When using a RIS server I believe (if I remember well) you have to edit the dosnet.inf file as well!

No ***STOP: 0X0000007B messages after the File copy was over. Everything went smooth as silk. Whoa I am so relieved... Thanks a lot guys fro all your help... 3 Cheers to the MSFN Team!!! Yeah! That's the way everything should work But tell me, you DID edit the txtsetup.sif file, right?

Can anyone else please try to download this file? It's about 26 MB and thanks to the extremely slow server (2.5 KB/sec average, B) ) I can't get the download finished... Downloaded it completely 2 times and 2 times corrupt... :s