Bâshrat the Sneaky

Thanks, Beagz And I must say: clever idea Once thought of it myself, but it was far far away () in the misty and forgetting world that's called my brains P.S.: Did you use THIS method or Schalti's method (SetupCopyOEMInf.exe)? P.S. II: Double post removed.

I was updating the 'Read this first'-sticky that lists all major topics related to Device Drivers. Of course I was adding a link to this topic too. But I was wondering... where is the tutorial? I thought you wrote one somewhere in this topic, X-Savior? But I was only able to find erik_demon's .doc tutorial. For now I've linked to that one.

Intel drivers in DP Chipset updated, nForce drivers were 6.53, I guess I simply forgot to update the number... (6.53 was out before the first release of DP Chipset, but I had already an early build with the 6.39's in it for personal testing) And NO DP LAN does NOT install the hardware firewall! (I have been planning to though, but I don't know YET a method on which I can determine whether it should get installed or not. Do you know of a method that can checks for the presence of a HWID and if it's there, execute something? I don't. Unless I write a small prog for it, but sad enough I don't have the time for that ATM.

Eh... What do you mean by this: ?You can DELETE this folder after the installation has completed... And which driver is located where can be found in the readme's. Why are they abbrevated? Simply because of this: the OemPnPDriversPath is limited to 4096 characters. That's why I'm glad to hear from you that you would like to LEARN the process, so that you know how to do it yourself. Most users want to get things working as fast as possible, without really searching, learning and thinking. Nice to see that As for the advice.. You only have to compress the MAIN .sys file (some drives have 2 .sys files). Don't forget to use the LZX compression, it has a better compression ratio! That would be like this: MAKECAB /D CompressionType=LZX /D CompressionMemory=21 driver.sys That's possible, BUT you'll have to point to EVERY subdirectory. That would be 'Drivers\RAID\1;Drivers\RAID\2;...'. I hope this helped

Correct me if I'm wrong, but isn't this the thread for the Driverpack Graphics B?? Some copying and pasting BTS? ← LOL @ me Thanks @eben: what do you mean?

You don't have to add that .dll file to your I386 dir.

Uploaded to other servers. Problem fixed.

Uploading them ATM to another server.... Please have some patience. EDIT: all back online! Please post in the DriverPacks General Discussion next time... that's where this kind of problems belong! And then you'd have noticed there was already a topic running! It's not very grave, but it's just a remark for in the future EDIT2: Welcome to MSFN!!!

I will put a mirror online. I don't understand this, they claimed to provide unlimited bandwidth!

Are you a professional user? Or a hobbyist? I'd be glad if you post your personal use of the DriverPacks, it gives me the chance to estimate the audience, so I can adjust it to the specific needs of the gross of the users. Thanks in advance!

Poll ended. It seems, as I expected, that method 2 won with distance. Thanks for voting, now I have a better idea of what my users prefer.

Did you use the FIX? And WHAT is it missing?

I think you mean 'AutoRun-enabled disc' instead of 'bootdisc'?

No, people that have been using my DriverPack MassStorage reported it to be working, however that has been a whole while ago, which is why it isn't listed in the Success Devices. Please try it and let me know.

I know about that... I posted that a couple posts higher And it also says that it still has to be put online

So you want to integrate as much SCSI/SATA/RAID drivers as possible? Then try my DriverPack MassStorage and use the DriverPacks BASE to slipstream them. They do the exact same thing you're saying. If you want to use the same method you explained above, choose method 1 in the DriverPacks BASE.

Eh... you're mixing EVERYTHING up, I'm afraid! For all drivers: 1. OemPnPDriversPath in winnt.sif 2. Pyron's method 3. hybrid methods (combination of the 2 above) For MassStorage drivers @ TEXTMODE setup: 1. txtsetup.sif method 2. txtsetup.oem method If you're using my DriverPacks, I'd use Method 2, which is Pyron's method.

****... this is really strange :s then I'll switch to UPPERCASE filenames in the I386 dir :s

Do you care to do ANY search? It's a SWITCHLESS installer, as the site says.

@McDanger: that way it will probably NOT work, maybe in this case but... The way I just mentioned, it will ALWAYS work! EDIT: unless that hotfix of you isn't a driver of course...

Read this article.

@kingofthing: thanks for that info, I'll try to get it fixed. @BAM: 1 & 2 are fixed, please give more details about 3?! @midiboy: as several others already explained: that's NOT a requirement! Been doing it like this for months now, without any problems! @tchuyev: fixed now @BAM: probably it just didn't execute, as there were eh.. *certain errors* (=> big ones) in it @laza: those entries don't need to be there There's an error in it... Fixed i/t new FIX @muiz: fixed in the new FIX. @mark49: your remark made me remember something: CMD /C is needed to execute batchfiles from DetachedProgram. It's fixed in the new FIX. @SilverHaze420: I think I've got an idea to fix that problem . EDIT: P.S.: @all: this new FIX isn't online yet!

I know it's confusing, I thought the same thing at first. But you have to click the 'Free' button to continue

You changed his path c:\drivers\vid\intel to yours, I suppose?

It included drivers, but were that the NEWEST ones?