Search options (Page 52 of 99)

Hi
yes.. move approx 1.4 giga uncompressed to windows\drivers\dp is pretty quick, and then let windows know where the INF files are and what they are for takes a while (doPNF).

Hi again.

another tip I posted long ago was that I use the advanced settings in RVM, and let it do uni 2 ansi.

------

Another thing I look at is when I use NLite.
It changes the setting for OEMpre-install (it is set by default) to YES, which is not the setting DriverPacks normally uses.

Oh, interesting thing is, when one changes it to NO, the nLite.cmd is still processed.

--------

And last, we do have a bug.
I recommend to ALWAYS use QSC.

percsas error fixed

weird, txtsetup.sif is OK here, and percsas.sy_ is cabbed into i386.

Did you have QSC ON?
There are some bugs when it is OFF. (in Method 2 too.)

hi,

if this is the first time you will do this, then you should read this.
http://users.pandora.be/jtdoom/basetute/Eng_tut6b.htm

http://downloadcenter.intel.com/Detail_ … p;lang=eng

for folder I\1.
let's see if it does not DROP too many device IDs. (that's a trend with them..)

I figure server was filled up.
Just had another abort midway.. I deleted some old files.

edit; removing some files from OLD folder, that did the trick.

Checked changelog/supported device list, and repacked.
Then recalculated.
7.09.22 RELEASE got uploaded.

I had an error, uploaded fixed file.

http://forum.driverpacks.net/viewtopic.php?id=2039

here was a test pack link.. tested in virtual PC

see lower for link to a new testpack made on 2007/09/30.

hi, it is already in a TESTpack.
(Just posted it.. )

hi

when you do this, I wish you good luck, because we have set some drivers to load AFTER another because of reported conflicts if they was loaded in front of particular ones.