Bâshrat the Sneaky

Then please tell me how to solve it otherwise... If I'd know another method, I'd use it... Well, if you go back several pages in this topic, you will see that fixing the OemPnpDriversPath solved the problem for several people. And because Method 2 creates the OemPnpDriverPath itself, Method 2 didn't suffer this bug... Do you understand what I mean? And now, there are indeed several others who have AGAIN the portcls.sys error. This time not by my mistake (the wrong OemPnpDriversPath), but due to the drivers used, to which I cannot make any changes without voiding the WHQL signing... I hope I answered your questions with this?

Thanks! But could you please PM me next time instead of making a new topic for it? I know you're posting this for everyone, not just for me, but if everyone would make a new topic for a new driver update, this forum would become quite messy...

Hmm... You definetely got a point here. I guess I had REM'd it out before, cause it definetely has worked... I'll change it in the next update....

@Incroyable HULK: if you (or anyone else of course) could confirm that adding this driver could solve the problem, I'll add it.

Thanks, will add them. I guess this topic will stay a bit longer active than expected... :s :'(

Well, as you know the same problem occured with method 2 (so OemPnPDriversPath isn't concerned). I DO have several people who confirmed everything to be working fine with Method 2... That's the strange thing about it, but hey, maybe they were just using some older versions of my DriverPacks, in which the OemPnpDriverPath of method 1 still had that error....

You can make a fake file: create a new txtfile, save it as DriverPack_MassStorage_V501.7z (don't enter anything in it) and move it to the DriverPacks folder. But then, when the batch files try to compress the MassStorage drivers and so on, it will show errors I'm afraid. Making it possible to chose which DriverPacks you want to be installed, is definetely on the to-do list

You should have read the guide before posting... You can find a tutorial on how to slipstream MassStorage drivers to avoid pressing F6 here

Already downloaded those Thanks anyway

Hi, don't know what the difference is, but in the new version there will be updated versions of both Broadcom drivers, so that problem should be fixed. About the DP Sound problem: I'll investigate that one later on.

Spraken Sie Englisch bitte! (I know, my German sucks )

This is what I'll try to get done this weekend: -fixing the minor bugs (missing devicepaths) -updating DriverPack LAN with SMC drivers (already downloaded all of them) -adding cab compression for method 1 -changing method 2 according to a06lp's edited guide. (yes, still Pyron's method, he just changed some things and it seems to work for everyone)

Indeed! I've already sent hp38guser a PM a couple of days ago I will definetely use cab compression for the winnt.sif method from now!

Erm? 'of of'??? Please clarify (or am I being dumb again? )

@RogueSpear: very interesting idea, but I don't have a clue either... Your 'master-inf file' would have to contain all DeviceIDs, so I'd have to copy them from every single inf file... But that might be possible to be automated with a batch file. But I truly don't know if it's possible to refer to another inf file from another inf file, when you're trying to do this for a driver installation. Anyone else with more .inf file experience around here?

Hmm... I'm wondering what the problem could be then... the OemPnPDriversPath error is fixed now, so that can't be the cause... Anyone else an idea?

I'll check it later (I'm at school ATM), but I guess there are also some differences in the inf files. EDIT: late edit, but better late than never It seems the PCI ID's are different, so I need both!

YEAH! Belgium rules!!!! B)

Not anymore That has changed with DriverPack MassStorage V5.01! @everyone: I'm agreeing that that method is the 'ultimate' method. But do you guys have ANY clue what a hell of a job that is? -I'd have to change EVERY inf file (about 300+ atm). There's not a single driver that I can simply copy... -Not a single driver will be WHQL signed. (WHQL signing is no longer valid from the moment you change *one* character in a inf file) -I'll have to edit the inf files again with every driver update...

Try www.asus.com, www.intel.com and www.google.com. I'm sure you'll find them! For installing them, check out the guide

You've posted THREE new topics, just to get the info you need! 1. You should have SEARCHED 2. You should have posted all your questions in ONE topic! Now, please use the search function to find it! I've replied to 2 out of the 3 questions you've asked.

It should work perfectly when you're installing it like is explained in the guide. Just point to all the directories that contain a inf file. Like this: Drivers\nForce\GART;Drivers\nForce\Mem;Drivers\nForce\...

Google for the executable named 'i6comp.exe'. Then place it in the %windir%\system32 folder. Open a cmd window in the folder in which you've extracted the setup of the monitor drivers. Now enter the following command: i6comp.exe x data1.cab And voila: there's the inf file (and the other files) you need!

Translated: What I want to say is that my knowledge of al this is very limited. It seems to me that it's more complicated than simply inserting a file into the I386 folder. As far as I've read in this forum you will also have to edit the txtsetup.sif file, but there I don't understand anything at all... If you could help me modifying these entries, that would help me getting started, because I'm using my main system, I can't risk alot. Thanks So far my translation Some words I didn't know, so excuse me if it's not translated a 100% correctly. (Excusez-moi si mon traduction n'est pas tout a fait correcte!)

It will be named DriverPack Graphics, and yes, it's coming. Also DriverPack Chipset will be added. I won't post ANY ETA, I'll just post the new topic when I've finished it. (no more time pressure for me )