Bâshrat the Sneaky

Why did you post this in the DriverPack WLAN forum? Topic moved to Device Drivers! The easy way: download my DriverPack WLAN and get the files from there (the download is only 12.5 MB... your extracted folder is 35 MB and that's only one driver, go figure ) The professional way: FIND A WAY TO EXTRACT THEM! Probably you should use 7zip or WinRAR or anything alike to extact the files. Maybe you could post a list of filenames? That could be helpful!

EH???? IMHO: WTF!!! Please answer to the questions below: 1) did you use nLite or anything else to reduce the source? 2) what are the HWIDs for your SM Bus controller and your nForce 3 NIC? 3) anything special with your (modified) Windows worth noticing?

Did you modify the DriverPacks BASE, or DriverPack MassStorage or Sound A?

I wonder why it's doing that????? Any idea, djbe?

Check FIX #3. Please post whether this solves your problem or not!

Check FIX #3. Please post whether this solves your problem or not!

In the current DriverPacks BASE discussion thread

And I even didn't notice that one was missing... Did you read ANY guide, Skeeter6755?

Eh... it's necessary afaik... I've been doing that for 1.5 years now... And with me, several thousands of others... :s Please ATTACH your winnt.sif.

I hope you added a quote at the end of your OemPnPDriversPath? Like this: OemPnPDriversPath = "Drivers\dmlkj;Drivers\dsmlkfj;...;Drivers\dmslkfj"

With only a OS, we can't help you...

FIX #3 for DPs BASE V5.05.1 -Fixed: [DPB] slipstream_DPM.cmd: ASH1205.sys error when using winnt.exe/winnt32.exe to initiate setup. -Fixed: [DPB] Fedit.exe: the problems with Fedit.exe (current version: 1.2.2.1) -Fixed: [DPB] RUN_ME.cmd: the problem with the cleanup batch file not being executed. -Fixed: [DPB] RUN_ME.cmd: the problem with the erroneus REG ADD command in BTS_DPs_ROE.cmd. -Fixed: [DPB] RUN_ME.cmd: all method 3 related bugs should be fixed now. download How to apply the fix: 1) Download; 2) Open your DriverPacks BASE dir, open the FILES dir; 3) Move the downloaded file into that dir, click 'Yes' when asked to overwrite. P.S.: I got the strange feeling I overlooked some things EDIT: note that the changelog above is accumulating, i.e. it contains also the changes of the previous fixes.

Did you apply the FIX? FIX #3 is coming...

I don't have a 64 bit processor, so unfortunately I cannot post my experiences... if you buy me one, I'd be glad to test it Source. It's in Dutch... and apparently heavily moderated, because the positive report I read there is gone...

Productkey removed, OemPnPDriversPath shortened. @Skeeter6755: note that you did not properly close your OemPnPDriversPath!!!

Nice indeed I will definetely try this out this week-end EDIT: pinned topic!

@Gnome: if you want I can help you with auto-updating the dosnet.inf, txtsetup.sif,svcpack.inf and sysoc.inf files! PM me if you want this to be automated as well. And... thanks No there is no more pressure on me... I had lost the time to do it and was losing the motivation... I'm glad somebody else took the initiative

Eh doesn't that ONLY work for MassStorage drivers???

Note that the new nForce 6.56 drivers seem to work!!!

Did you press 'G' when asked which method should be used for the finishing batch file?

I'll post a new fix tomorrow. No time now...

Could you please verify that: -the files do not exist in the I386 dir; -there are no entries related to the files you posted in the dosnet.inf, nor the txtsetup.sif file.

Are you sure of that, htc? That way property.dll will ALWAYS be copied, REGARDLESS the hardware setup it's being installed on...

If you're using M2, yes.

Well, it *SHOULD*.