Bâshrat the Sneaky
Content Type
Profiles
Forums
Events
Posts posted by Bâshrat the Sneaky
-
-
Are you sure of that, htc? That way property.dll will ALWAYS be copied, REGARDLESS the hardware setup it's being installed on...
0 -
You've got an InstallShield setup there (I can see that by the fact you have 2 data.cab files).
Use the command line utility i6comp to extract them. Google will provide you with al the information you need
0 -
Well, in that cse, could you please verify the .exe files ARE in %DPDIR%? (commonly %DPDIR% is the variable for %SystemDrive%\D)
0 -
Indeed. You stated 'VIA Vinyl AC'97', and there is a VIA driver what that exact same name, so I suggest you'd use that one.
0 -
What is your OS? And your hardware? Which specific driver didn't work?
0 -
Interesting, didn't think that it would work at that stage
But unfortunately unusable for my DriverPacks - they would not yet be extracted at that stage... unless you use method 2 or method 1.
May I ask on how many drivers (the number of .inf files) you're applying this? And how many megabytes?
0 -
to add:
nircmd.exe inisetval I386\winnt.sif Section_Name Value_Name Value
to delete:
nircmd.exe inidelval I386\winnt.sif Section_Name Value_Name
0 -
You can do that with nircmd.exe or Fedit.exe.
0 -
And those are the MAX & theoretical data rates... IRL it's MUCH lower!!!
0 -
If you want it to be done automatically, use my DriverPack MassStorage + the DriverPacks BASE. But please wait for V5.05.1 of the DriverPacks BASE!! The current one gives trouble... Though it works (nearly) fine with DP MassStorage only, only the cleanup doesn't work.
0 -
Use any decent archiving program (e.g. 7-zip (freeware)) to extract the driver files.
Did you read the tutorial?
P.S.: welcome to MSFN.org!
0 -
I'm afraid you'll have to leave out one part at the time to see what's causing it. So first add nothing, test, add RyanVM's updatepack, test, my DPs, test, WMP10, test. (however WMP10 would be VERY unlikely
)0 -
It seems several users of my DriverPacks have reported that, when SetupCopyOEMInf.exe is doing its job, alot of annoying 'not WHQL signed warnings' pop up. I found a way to easily circumvent this:
START %DPDIR%\WatchDriverSigningPolicy.exe
START /WAIT %DPDIR%\SetupCopyOEMInf.exe %DPDIR%
TASKKILL /F /IM WatchDriverSigninPolicy.exeThat is: using WatchDriverSigninPolicy.exe to get rid of them! (Thanks again, Pyron
)0 -
If you only use DP MassStorage, you can use method 1, but if you want to use more DriverPacks, it's recommended to switch to method 2 (because this saves space on your UWXPCD).
Don't forget to use the FIX!
For more info, check 1. in this topic.
0 -
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.
0 -
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.
0 -
Eh... What do you mean by this:
?Honestly I do not like the file structure (I dont want a folder named D on my system drive that I have to keep there becasue windows needs to load a RAID driver from it all the time.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..
I read greenmachine's tutorial which is good and definetly helped me slipstream the si3112 drivers. The only line that honestly messed me up was this one: MAKECAB E:\XPCD\$OEM$\$1\DRIVERS\006\SI3112\SI3112.SYSE:\XPCD\i386\SI3112.SY_. I know how to compress a file using the MAKECAB function but I'm not exactly sure which files I need to compress and intigrate into my I386 folder. Do I have to do this for every file? Is this only for the .sys files?
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
Will each set of drivers have a different file I need to compress? Should I compress them all just to be safe? Also the OEM PNP path in greenmachines tutorial is set to: OemPnPDriversPath="Drivers\006\SI3112". If I wanted to add 5 different sets of drivers for 5 different controllers would I put them all in (for example) the $OEM$\$1\DRIVERS\006\SI3112\ folder and point to it? Could I create 5 directorys named 1, 2, 3, 4 and 5, place them all in the folder "$OEM$\$1\DRIVERS\RAID" and set OemPnP like this OemPnPDriversPath="Drivers\RAID"? If I do that will windows include all the SubDir in its search for drivers?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
0 -
I think you mean 'AutoRun-enabled disc' instead of 'bootdisc'?
0 -
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.
0 -
Do you care to do ANY search?
It's a SWITCHLESS installer, as the site says.
0 -
@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...
0 -
Read this article.
0 -
I know it's confusing, I thought the same thing at first.
But you have to click the 'Free' button to continue
0 -
You changed his path
c:\drivers\vid\intel
to yours, I suppose?
0
) in the misty and forgetting world that's called my brains
Nvidia driver slipstream?
in Windows XP 64 Bit Edition
Posted
Note that the new nForce 6.56 drivers seem to work!!!