Search options (Page 105 of 213)

if you want to be treated like a big boy. then act like one. you have not listened and you have repeatedly posted inaccurate results. You've failed to verify your results and you have further failed to do good research on your own. you have gone off 'half cocked'  multiple times in every one of your 5 posts. You have failed to demonstrate good trouble shooting skills (or even basic ones).

these functions are documented on this site too... yes the wiki is gone but it did not have the wealth of knowledge that is contained in the posts here at DriverPacks. In fact the answers to all your questions are already answered here in detail. In posts you did not take the time to read. much as you did not take the time to actually read the changelogs for DriverPacks BASE which states clearly that only languages were updated. We are not here to hold your hand nor are we obligated to educate you.

DriverPacks has always had a no noobs policy you are no exception and you are in fact the type of user that reinforces that policy.

no contempt involved I merely observed... You're the one who posted the stupidity, I just narrated.
in fact i tried to offer you help. you ignored the advise and told me I was mistaken about devpath. (i did not make a mistake)

here is the place for noobs http://unattended.msfn.org/unattended.x … 29194ea61/

It is pretty arrogant of you to think you can do a better job than we can after we have been doing this everyday for 6 years.

have a nice day.

PS and you did not follow up with a report of success or offer helmi a thank you the last time you went of half cocked making false assumtions failing to do good research and basicaly needing us to cure problems you chose to create and were totaly unable to understand...  http://forum.driverpacks.net/viewtopic.php?id=3046

the functionality of the finisher is well documented... you should be able to come up with that on your own. but whatever....

don't change presetup.

the finisher finishes installing drivers. not all drivers can be installed simply by pointing hardware at the inf.
In fact some hardware will not function at all if it's setup program does not run.
that is the PRIMARY function of the finisher.
Deleting the files and cleaning up is 1% of what the finisher does.
the finisher is a crucial part of DriverPacks and is why it is included in SAD and is ANOTHER reason KTD fails since KTD can not call the finisher.
I have tried to explain to you that KTD is a looser but, You can lead a horse to water... in this case SAD, but you can't make it drink. (your not listening) The fact that you were not able to find out what the finisher does on your own tells me this is way beyond your current level of experience. plus you were able to get different results with base 8.12.3 and 8.12.4 which are identical. this means you can not limit your changes in testing to a single variable. Furthermore devpath does not have a 3 character limit. It is obvious you just do not have enough experience with DriverPacks, and basic testing in general, to go off on your own. Please don't. This is way beyond your level of experience. Just use SAD when you install new hardware. problem solved.

when you install new hardware run SAD...

Outdated drivers are not the answer... and hardware does not install itself your going to be there...

KTD uses makePNF which creates duplicate and unsigned INFs these unsigned PNFs are passed over since they are unsigned this is why KTD is dead and is why your video drivers will not install. KTD never worked very well... SAD does...

If you absolutely must have drivers needlessly takeing up space on your machine(s) and that will in all likelyhood never be used and by the time they are used they will be out of date, then the best thing to do is to create a SAD M1 folder and run DevPath.exe [path:\Driverpacks.net\D\] this will give you better than KTD funtionality (because it will not run makepnf which breaks the driversigning).

We don't just say KTD is dead because we like the way it sounds when we say it there are many reasons, I have just given you one of many good ones.

PS the ONLY difference between 8.12.2 8.12.3 8.12.4 are language updates
no changes were made to code in DriverPacks BASE or finisher

LOL... yeah you did

We don't replace the existing drivers. 
If you remove them then they are no longer supported at all.
Any driver in the packs that would depend on them will also fail.
Don't Delete Them!... ANY of them

the idea DriverPacks is based on is supporting ALL hardware removing drivers is the opposite of that
Questions about removing drivers are not appropriate in our forum...

If you wish to delete and repackage them in a 3rd party DriverPack - not supported... don't ask.
(It might work, but it is still not supported)

If you need help on the msfn guides, those questions are appropriate at MSFN. Ask over there.
DriverPacks has a no noobs policy.
questions about basics (the stuff covered by the msfn guide for example) are considered inappropriate.
We refer people with basic questions to MSFN...

TY

Moved from 'Feedback and Support - DriverPacks Base' to 'Other'
- Not a DriverPacks BASE related issue
- Not a DriverPacks issue at all
- asked and answered in first response.

driverpacks require you keep all the existing windows drivers in order for you to obtain your best results...

Thanks so much JakeLD... your time spent on the packs can not be measured nor fully appreciated by anyone who has not done it. If only there were medals for civilians... if there were i would recommend you for a chest full.

Please accept my deepest thanks, eternal gratitude, and undying respect as substitutes for gold which i do not have to give you!

your friend Jeff!

the error is windows not DriverPacks... the driver does not support your OS... seems like it is what it says it is...

altering the inf breaks driver signing we don't normaly break a drivers signing...

although this will work it is not the prefered method af adding support for hardware.
the prefered method is to use a signed (unmodified) driver that includes support for your hardware..

the normal proceedure is for you to point us at a OEM driver that supports your hardware and for you to included the HWID that is not currently supported...

so you were in the ball park and got a hit... you just did not hit a home run...

lol DriverPack Graphics A 8.12.1 does not have a CX_75974.inf  file... !

Well we had a million downloads last week, and we still only have 25 votes for xp-64

and it is abandonware to boot...

can we "stop whipping the dead horse" now

You must use nLite first  DO NOT integrate ANY drivers with nLite

YOU MUST USE DriverPacks LAST!

RTFM! (and the forum titles)

problem solved!