Bâshrat the Sneaky

Link is fixed. The DriverPack WAS uploaded, but there was a typo in its name...

@mark49: the control panels batch file is still copied using the OemPreinstall method... So I'm afraid that's a no... However I could change that of course...

Thx nazgul, will fix it. I found another minor mistake by me: I included the wrong changelog file for DP MassStorage... The one of V5.04.1, which isn't finished yet, nor is it online... Sorry @muiz: that might be the best yes... But remember this: the more reports, the sooner it will get stable

DriverPack Graphics A V5.04.2 Download in this version: 'The return of the 71.84'... Sorry guys, won't happen again!

BTS DriverPacks BASE V5.04.8 Download All bugs have been fixed. Again except the aliide.sys, ql12160.sys, mraid35x.sys etc. one (well maybe it is, but not sure). If anyone knows more on how to solve this last big bug, please tell me! Another note: my 2 week vacation is over. :'( As you can see, 2 VERY active weeks: I spent more than the half of it on this DriverPacks project! It's possible that there won't be much updates the next weeks... School is starting again and so are coming lots of tests... But I'll do my best!

You can laugh at me, yes , but I got it fixed New version very very very soon....

Do you have OemPreinstall=Yes in your winnt.sif?

I like it Nice find :

Nice I'll be using it too Thanks, totoymola

This one already existed, in batch file format. Check the Device Drivers forum, search for 'OemPnPDriversPath snippet'.

Trust ... the most sucky brand ever... they don't develop ANY own technology afaik, so their hardware MUST be supported indeed. Sweex... don't know... they might build something of their own? To be sure, I'll download their drivers as well... (let's hope they don't have too many)

@buletov: I'm quite convinced I saw weeks or months ago someone's post in which he/she was claiming that with OemPreinstall=Yes, but some other setting set different, he could load drivers from the floppy using F6... A few weeks ago, 2 or 3 topics about this have been started and in none of them somebody found the solution... But are you really sure there isn't any other way? (you're a senior member here too, so you might know it...)

@simpleman: probably this will be inevitable then... As it seems that ctzapxx.exe will keep on running untill it ends when GUIRunOnce is done, and the deleting process is BEFORE the end of GUIRunOnce, then it's not abnormal that the folder where ctzapxx.exe is located in, is not being deleted... Anyone an idea for a work-around? I don't see any possibilities...

This is still an unsolved error... nobody seems to know the solution... :'(

Final solution found! Separate hwid reported for the viaSraid driver! (which exists on *some* ASUS boards with VIA chipsets: the A8V (Deluxe) and the A7V880 , but NOT the K8V (Deluxe) ) More confirmations are still wanted. But it seems this problem has been solved at last! :

@swaro2000 & mark49: THANK YOU now the problem should be solved... I'll link this hwid PCI\VEN_1106&DEV_3149&SUBSYS_80ED1043 to the viasraid driver. I'll keep this thread open for more replies with hwids.

again Will be for the next one! Thanks!

@all: I'll try to get it fixed... tonight... (been busy all day) @mark49: yes, it's that section I'm talking about... Are you very sure it doesn't work? EDIT: retested, and indeed it doesn't work! WTF I tested it yesterday evening and it worked flawlessy???

****.... I've been saying for MONTHS now that I only want official releases. But several have been telling me that those WHQL drivers are equally stable... Stupid me I'll upload a new version with the old drivers... sorry guys...

I've been told that they're equally stable?

Ehm, no the cpl batch file system has drastically changed since then... sorry... You could edit your winnt.sif, copy the new cpl batch file and then... you're settled. But that'd take more time I think B)

OK, maybe sad news for some of you: I will NOT update this slipstreamer untill somebody tells me what files have to be edited, which files I should include etc. In short: the entire process that's required to get the full functionality of WMP10 to work. I will automate the process, or if you'd rather do it yourself, fine with me. If I do it, proper credit will of course be given. Why am I doing this? Lack of time, and most importantly lack of motivation: I don't use WMP10 myself so... Sorry... and thanks for your kind reactions!

Probably it's a regtweak?

So Windows detects 3 monitors instead of 2?

Check this article for extracting it and this one for slipstreaming the drivers This should be sufficient!