Search options (Page 157 of 213)

it may have to do with how autoit is parsing nested double quotes in the code

try useing a pathname without double spaces

welcome to DriverPacks jbbjshlws, We are glad your here...

Thanks for the good details. It makes it so much easier to help you.

same question as before did the files end up in the destination folder?
also were you useing a clean source or were you running base a second time on the source?

I am thinking, at the moment, that the base's dpinst file check is not done yet...

9.0.0.1008 is already in a test pack

please dont waste our time... it is posted all over the site and stickied

do not request ATI Nvidia or Intel files... WE are fully aware of thier releases (it is what we do)

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

C:\windows\Setupapi.log  log please sam

the 8.06 release was the addition of the dozen or so language packs that have been submitted...

so unless you are useing simplified chinese there should be no dif...

DHCP sucks and it doesnt matter if your on pc mac or unix

simply removing the unattended section of a m2 installs winnt.sif will enable repair.
of course you will also have to NOT use ROE method to launch the finisher.

obviously M1 will fail without the unattended section so this could be used in conjunction with M1.
however his code doesn't address an m1 source so i belive it would fail on an m1 source anyway.
however m1 is all but dead atm furthermore m1 doesnt require extraction so dpinst can simply be run.

this is really way to complicated for somthing quite simple and since it fails on an m1 source is maybe not complete. (although presetup.cmd IS specific to M2) most admins know where their files are in advance. if they don't they shouldn't be admins. it is reasonable to expect that the drivers are in a certain folder and it is resonable that we will know in advance where we put that folder. (we may not know which drive letter - but certainly what path is known)  it is a half completed excersise in making a mountain out of a mole hill.

if i were going to custom code this for myself it would be half the size - not twice the size... smaller is faster

that would be because those notes are in the testing team forum

and your not on the testing team

I just thought of somthing that i just assumed you were aware of...

this is not technicaly supported but should work just fine.

all packs except the mass storage can be substituted.

IE you can replace the old pack with a new one... just rename it to be 8.3 compliant (same as the one you replace)

remove DPGA804.7z and insert DPGA805.7z

if the main packs fail and you see a post that is related and has a test pack then it's probably a good idea to try it.

if you find that a device is not included and there is a post from someone else about that device then it's probably a good idea to try it.

It is great! that you are haveing the same issue... If the testpack fixes it for both of you it will be considered a valid fix. Please report back if it works (or not) for you.

Thanks for posting... it does help a great deal.

Packs are released when neccessary...

It is our goal to support all hardware and be stable and reliable.
We like to try to stay current too... but that takes a back seat to stability.

so

1 support all PC hardware
  (although laptop support is growing)
2 cause no issues
3 stay current

Welcome to DriverPacks krige thanks for being here

so you are useing an alternate NTDETECT.COM (I assume the one from the 2k3 servicepack)

you do this to support USB boot

and you find that it is interfereing with the mass storage driver support?

Is that correct?