Bâshrat the Sneaky

I removed them a couple of versions ago, because it didn't work properly. They WILL be added in the complete rebuild of this DriverPack! (with that method they work just fine)

I've tried to use as many variables as possible. Those parameters which are hardcoded hardly every change. (this will probably be the first and last time). Though I AM very interested how you could improve this, especially for the method files versions: I have to set it in many files: -the run_me_method_x.cmd: inside the file -the patcher: inside the file -add_to_txtsetupsif.txt: in the filename and this for both methods, and again for the Method_X.cmd in the main folder... Please post your thoughts for improvements in the 'DriverPacks BASE' topic I've started recently.

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAARGGGGGGGGGGGGGGHHHHHHHH AGAIN STUPIDITY!!!!!!!!!!!! Dammmmnnnn Will fix it immediately! @RyanVM: erm, that's about 2 and a half months ago, don't remember, but probably I simply added those drivers? EDIT: both are fixed now.... THREE versions of both methods in TWO days!!!!!

I've got another idea: Windows prefers the drivers in driver.cab over the ones we add, because sometimes the .cat file is missing, right? Then, what if we would remove every cat file out of driver.cab? Then Windows would choose our drivers! Because Windows choose drivers to install like this: (highest rule = first rule) 1. Driver signed 2. Driver version Do I sound like a fool now? Or is this again something nobody has ever noticed before?

Its a well known fact, that when you re-read any document you have written, that you read what you think you have wrote. Nvm, people always make mistakes but you put alot of effort into this comunity and im sure people are more than gratefull. I know that people appreciate my efforts. But I can't stand that I make such big errors... :'( Well, I think beta-testing will avoid that.

And of this archive about 57 MB should be of my DriverPacks...

From now on a new policy: a one week beta from now on, for all big changes! I'm sick of the fact that there are some huge errors in my work... Maybe it's just me, but I don't notice all these errors, simply because I don't *see* them, do you get what I say? So with the next big update I'll look for some volunteers.

Updated 9th of January 2005: DriverPack MassStorage version 5.01 Changelog Download! Please click the banner, it's all I ask in return! Thank you.

Here

I've fixed everything, uploading now. This required a new version of DriverPack MassStorage. (the only change is the new path: DP instead of Drivers) About the Method 2 + hotfixes problem: yes, it's a problem that's caused by Method 2. Ile5 has posted a fix for it. Why I didn't integrate it yet? Haven't had the time to test it, and not everyone is having this problem... Normally I would be reading the entire topic of Pyron's method at this very moment, but because of these new bugs...

[EDIT2] Putting REM in front of this line in Method_2_V008.cmd seems to work: "REM IF NOT EXIST "%D%s\%D%_%W%_V*.7z" GOTO NODP" I will try to add a feature that allows you to choose which DriverPacks you want to install. But that won't be for soon... Don't forget to change your OemPnPDriversPath if you use Method 1!

@beaumar, moesasji, sixpack: you are ALL right... I'm almost crying here :'( Such a HUUUUUUUUUUGE error!!!!!!! How the h*ll could I overlook such a huge error.... And the additional errors in the OemPnPDriverPaths!!!!!! :'( Working like a mad man to fix all these.... :'(....

Thanks. Will add it.

I'll add them in the next release! The reason why they aren't there yet: nobody has requested support for those. (didn't know they made ethernet cards...) Greetz, Bâshrat the Sneaky You did PM me? Then I must have deleted it and forgot it... I'm very very sorry! Will do it ASAP! (it's not much work, I'll get it done by Wednessday at last) OK? Sorry again...!!! (I feel ashamed now )

No, not all functionality is included. As I've mentioned in my first post, I've based this batch file on the info provided by Obliviator. Here you can find the things that aren't included: http://www.msfn.org/board/index.php?showtopic=35042&st=0

THANK YOU VERY MUCH!!!!!!!!!!!!!!!! I've been looking for a code like that for a while now (no, I'm definetely not a expert in batch coding) But fact is... I've removed the filedeleting part.... So I can't use this code anymore... But I can use it in the DriverPacks batch files Thanks again!

So what did you do now? Did you use all drivers (so you pointed to all folders) or did you only use the preNRM driver?

Have you already used the newest versions? There I've fixed it. (short explanation: Now a folder '$1files' is created instead of '$1'. Everything inside '$1files' gets moved into the $OEM$\$1 folder and if those folders don't exist yet, they are created)

It's really simple: -Method 1 keywords: winnt.sif, OemPnPDriverPath info: http://unattended.msfn.org/drivers.htm -Method 2 keywords: presetup.cmd, Pyron's method, SetDevicePath.exe, WatchDriverSigningPolicy.exe info (including a full explanation): http://www.msfn.org/board/index.php?showtopic=12566 No you don't have to change anything of the DriverPack structure. Just enter the OemPnPDriversPath that's provided in the Method_1_Vxxx.htm file in your winnt.sif. You can integrate drivers into driver.cab, but I would highly recommend not to do that. It's alot of work. While now, I've done the work for you. What you CAN do is the following: use Method 2, DON'T reset the DriverSigninPolicy and DON'T remove the DriverPacks folders. (currently %systemdrive%\Drivers and %systemdrive%\DP) Yes Windows DOES read the Driver.cab every time. They will come . And indeed you've got a point there

And what about this: Not working anymore? huh? And you can check my batch files and the DriverPacks, it's simply impossible that I could change anything related to WFP... What do my DriverPacks batch files do? 1. edit txtsetup.sif (remove ultra.sys entry, add other entries, this exists for more than one and a half year now (got it from RyanVM, the txtsetup.sif patching part) and you're the first one who's having this problem) 2. add files To change WFP I would have to EDIT files, not add files. Please try my DriverPacks on a clean UWXPCD (not nLited, no other things, just DriverPacks and winnt.sif), any method.

@beaumar & batman75: with Method 2 V007 the txtsetup.sif file was indeed not patched at all... That problem is fixed now with Method 2 V008! Just run your Update_Vxxx.cmd to get the new files.

Cool, isn't it Got it from somewhere about a year ago, don't remember from where.

You haven't asked... Will add them in the next release! @amd64: DriverPack Graphics will come, but I won't promise a date.

LOL you MUST be kidding! And swgreed too! :o

So I'll better update the slipstreamer batch file I guess? (just put online V1.1 )