1,651 Reply by OverFlow

(39 replies, posted in Feature Requests)

proximous wrote:

I've only used KTD for mobile phone drivers and LCD monitor drivers (aka things I know don't have installers and that likely won't be connected at install time, but will likely be connected soon thereafter).  This seems simpler having a SAD disc and using that for phones and monitors.

That does seem like one of the best examples of a good reason to use KTD I have ever been presented with big_smile.


proximous wrote:

I'm not familiar with DevPath.exe.  Is that explained somewhere?  So if I have a custom script run before the finisher and have it copy the drivers I want somewhere, and run DevPath.exe, then I can skip KTD?

YES!

if you copied your drivers to C:\KTD

devpath C:\KTD

big_smile

Go to forum: Feature Requests

1,652 Reply by OverFlow

(37 replies, posted in News)

ChiefZeke wrote:

How to I download anything? I went to Simple CDN and and found no link to download - just comments about how great they are.

LOL

All DriverPacks are available from links on our home page here at DriverPacks http://driverpacks.net/driverpacks

But the easiest way to do it is just to use the update checker page in DriverPacks BASE wink.

Go to forum: News

1,653 Reply by OverFlow

(39 replies, posted in Feature Requests)

OK so mute.exe works... So that means the call to mute is the failure. Thanks for clarifying for me!

The truth is we don't need mute.exe. KTD needs to be fixed is the real problem.
Mute is put in place to address the symptom, beeping. It doesn't fix the problem.

I have been telling everyone that "KTD is and has always been broken" for some time now, and trying to migrate everyone to SAD. not everyone is on board yet.

The REAL problem is KTD uses MakePNF.exe. MakePNF.exe totally incapacitates KTD and it's the cause of this annoying issue too. wink  I intend to upgrade KTD with SAD and eliminate MakePNF and Mute in DriverPacks BASE very soon.

More:
The Idea behind makepnf is solid, to Cache the infs to speed up driver matching. Sounds good don't it?
Here is the problem the PNF is a Duplicate and UNSIGNED copy of the original inf. Right out of the chute this Doubles the number of files that windows has to read to find a driver (it reads all the PNFs and all the INFs). Now if that were not bad enough here is more, The PNF file is Prefered to its original counterpart and is unsigned. What we end up with is a full duplicate set of unsigned drivers that are prefered to their originals. So if you use KTD you break signing on every single driver in your KTD folder. This really really just kills the DriverPacks because signing is KEY to the included drivers all working correctly. Now the popup and the beep are the warning that an unsigned driver is being installed. in all actuallity the driver in question is probably signed. So again i have to say Don't use KTD wink it doesn't work.   

The best thing to do until then is to simply extract whichever drivers you want to a folder and then run DevPath.exe on that folder. BAM... you have performed KTD correctly and will have no beeps wink.

So yeah i need to fix it but the fix is not what you think it would be but might be pretty easy to implement. wink big_smile

Persoaly i disagree with the whole KTD concept... Because Hardware does not add itself, if your installing new hardware you probably need to install the newest drivers too wink

Go to forum: Feature Requests

1,654 Reply by OverFlow

(1 replies, posted in Feedback and Support - DriverPacks Base)

Thanks for giving us positive feedback!

We actually need reports of success just as much as we need reports of failure.

You are here by awarded both a get out of jail free card AND a brownie point! big_smile tongue


Seriously, a report of success like yours is what we strive for everyday.

Thank you for taking the time to let us know it's working! That totaly Rocks!

Have a great day M8!

Go to forum: Feedback and Support - DriverPacks Base

1,655 Reply by OverFlow

(353 replies, posted in Software)

ROFL...

I run on caffeine, sadly that means i run on water too, Man... I really am old sad

Go to forum: Software

1,656 Reply by OverFlow

(39 replies, posted in Feature Requests)

If you manually run mute, does it work?

Hint
Run Mute
Open NotePad
Hit ALT+G

sound or no sound?

does the sound icon on the task bar show that it worked - is mute checked after running it manualy?

Go to forum: Feature Requests

1,657 Reply by OverFlow

(37 replies, posted in News)

and the crowd went wild!!!

well at least two of them did!

Once again a simply outstanding job Mr_Smartepants!

No news is always the best sign of success! Sad but true...

Well done sir... you're my hero!

Go to forum: News

1,658 Reply by OverFlow

(1 replies, posted in Software)

never heard of SAM DriverPacks?

hmm... found this... Link to msfn.org

I really don't feel like sitting through a google translated russian site... Perhaps the best thing to do is ask him?

Go to forum: Software

1,659 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

Yup. They call that perjury and it has a mandatory ten year prison sentence.

In light of that, I have mitigated the lifetime ban to a much more reasonable ten years... big_smile

Ten in da Pen for da xman!

Go to forum: Feedback and Support - DriverPacks Base

1,660 Reply by OverFlow

(41 replies, posted in News)

@eethball
Excellent details! thanks for helping us to help you!

@banshee
120! wow, nice work!!!

Go to forum: News

1,661 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

I warned you that you were on thin ice.  Banned for life!

You should have apologized for wasting everyones time...

Go to forum: Feedback and Support - DriverPacks Base

1,662 Reply by OverFlow

(2 replies, posted in 3rd Party DriverPacks)

Which pack? What virus scanner detected it? have you submitted and confirmed it with your AV company?

Most reports here are false positives.
We have millions of users with thousands of virus scanners...
it is unlikely that a single isolated report is an actual virus.

Please update your definitions and engine.
If the report is repeated with the latest definitions
then submit it to your AV company for confirmation (virus or false Positive).

if you tell us which pack we will arm the photon torpedos and raise our shields!
Well... at least the team will rescan the pack wink
Since we each have our our own opinions and all use different scanners we can run it through all the top engines in a few minutes... Since we all use on some type of on access scanning this has already been done many times wink. It is also why i feel confident it is a false positive. On the other hand hundreds of new virus defs are added each month... perhaps yours is the first one to detect it... Problaby not... BUT... It never hurts to be too careful.

Thanks for reporting

jeff

PS if you are useing topheal read this... http://forum.driverpacks.net/viewtopic. … 463#p35463

Go to forum: 3rd Party DriverPacks

1,663 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

yeah you lied... Every single tutorial we have says in big bold print "no changes after DriverPacks".
I asked and confirmed this with you several times... you were adamant you made no changes after DriverPacks. (a lie)

Please realize that Helmi's directions are spot on Identical to what you originally told us you were doing.

I will say it again: If you would have done what you told us you did...
It WOULD have worked without issue, and you would not have needed to post here at all...

the fact is you did made changes (with nLite) after you slipstreamed DriverPacks and you definitely lied about it several times.

had you told the truth from the beginning (I run DriverPacks first then nLite...)
We would have solved this issue in one post wink
but you simply refused to admit (until post #20) that you did not follow the directions.

please note: Your issue was solved in post 21. (the very first post after you told the truth)

edit....
Please consider...
There was no need for Helmi, or anyone else, to explain the steps to you like you were a child...
NOT UNTIL AFTER You finally admitted that you made changes to your source after slipstreaming the DriverPacks.
Helmi's simple instructions have been posted, verbatim, by me personaly many times.
There was simply no need to do so until you stated that you made changes with nLite after DriverPacks.

Also consider...
Had you done something else, other than nLite, after DriverPacks Helmi's instructions would not have helped at all. wink
It was only your admission that IT WAS nLite that you ran after DriverPacks that made his instructions useful...

please also note you can run nLite after DriverPacks as long as the ONLY thing you do is create ISO.
If you make ANY changes at all with nLite after DriverPacks then your source is FUBAR.
In this case because nLite deleted and replaced the winnt.sif after DriverPacks edited the winnt.sif.
Had you done your steps in the proper order (per our tutorial)... you would have been successful every time.
We already knew that nLite will delete an existing winnt.sif... wink Therefore we must always be after nLite big_smile.
DriverPacks last is plastered everywhere for a reason. Actually lot's of reasons... but this one is as good as any.

That is why we provide our tutorials, in order to avoid support issues.

end edit...

We have been doing this for many years, I knew from the very start you had to have changed something after DriverPacks.

We were at a loss to be able to help, until you told us what you did after DriverPacks.

The truth is that you absolutely DID make changes after you ran DriverPacks.
(And it only took twenty posts to discover that it was with nLite) 
ANY one or all of our users could have solved it after that revelation...
Statistically speaking there was only one possable answer -  ID ten T + PEBKAC

Go to forum: Feedback and Support - DriverPacks Base

1,664 Reply by OverFlow

(2 replies, posted in Software)

Always nice to have you around Helmi!

thanks for being here!

Go to forum: Software

1,665 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

How many freaking times did i ask this dweeb what he did AFTER DriverPacks!

"Oh no... I did not make ANY changes AFTER DriverPacks. I swear!"

from post #3

xman wrote:

Hi Overflow,

I made my XP Pro SP3 setup with nLite with IE7, Sidebar and WMP11 integrated without finalising the .iso. Then I slipstreamed the drivers with DPs_BASE with the settings set at M2, guirunonce default start (937), KTD off and QSC enabled.

Had you done what you told us / said you did it WOULD have worked!


You lied to me... and wasted my time, do it again and your banned.


If you make ANY changes after DriverPacks then it will fail, nLite can make LOTS of changes.

The only valid step after DriverPacks is create ISO / Disc. RTFM!

Go to forum: Feedback and Support - DriverPacks Base

1,666 Reply by OverFlow

(13 replies, posted in DriverPack Sound)

I'm sure you will be able to contribute!

Every machine is unique the broader our base of testers the broader our base of hardware, and, the less likely a bug will slip out. It's simply a matter of odds / statistics.

I already know you can provide good details, That you can find files not linked to on the main site, you read the documentation, and your polite!

Adding you was a "No Brainer"


Have an awesome day!

Go to forum: DriverPack Sound

1,667 Reply by OverFlow

(15 replies, posted in Other)

Nice... Now that is what I want to do, Sit there and continually press CTRL+ALT Waiting for the "next" button to appear, 30 times.

This issue certainly defeats any chance at an unattended installation Disc.
If you can't add it to your installation successfully then it is not any good, If it is not any good then why use it?

Think about this: How many hours have you sat there fooling with it. I am not just referring to this broken unattended disc / false positive issue. I'm sure that there are other issues too! Add the time you wasted posting here, troubleshooting, and CTRL+ALTing through your installs. Take the total hours and multiply by your Hourly Rate. Q) What did it cost you? A) More than it is worth. Get a decent AV program and cut your losses.

Go to forum: Other

1,668 Reply by OverFlow

(13 replies, posted in DriverPack Sound)

SA = South Africa?

Greets M8, see you in the team forum!

Go to forum: DriverPack Sound

1,669 Reply by OverFlow

(1 replies, posted in Feedback and Support - DriverPacks Base)

those entries are normal and required... (they are / will be added by DriverPacks BASE if they do not exist already wink.)

Can you check off a few of the items in "read before you post" (link in my signature)

DPs_BASE.log and HWIDs, minimum... Please.

Go to forum: Feedback and Support - DriverPacks Base

1,670 Reply by OverFlow

(30 replies, posted in DriverPack Graphics)

I meant Doom 3 not Doom the original LOL too funny!!!

with ICH7 chipset and a Nvidia 7900 it should be pretty perky in 2d mode (explorer, IE, device manager, etc...)

Go to forum: DriverPack Graphics

1,671 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

xman wrote:

After I've slipstreamed the DriverPacks I seem to lose the "command9="%SystemDrive%\DPsFnshr.exe" code.

I Know you said after you ran DriverPacks BASE the lines were there?

Post #14

xman wrote:

I've made a new CD setup and the lines are there.

your log states clearly

2009-12-08 23:06:03 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.

The line was successfully added today at 11:06 pm your time to C:\1\I386\winnt.sif. big_smile


That means #1 is true... you MUST have made changes after you Slipstreamed the DriverPacks with DriverPacks BASE.
They WERE THERE! You confirmed it in post #14. AND your log confirms it!!!

So... What happened to them. They did not evaporate.

What did you do AFTER you ran DriverPacks BASE??? Spill it, Tell us what you did AFTER DriverPacks.

They didn't just get up and walk away... and the HDD troll didn't eat them either...


Your on thin ice now...


I am getting tired of playing footsies with you. You say one thing then two posts later recant or say the opposite.

DriverPacks is downloaded at the rate of a million times a week... Yet YOU ALONE have this issue.
If you Can't tell us what you are doing that millions and millions of other users are not then I can't help you.

Whatever the problem is it is related to something that YOU (specifically you) are doing.
You alone. IE - Millions and millions to one odds. Five years worth.
So if it is working for millions of other people who all use nLite and DriverPacks together with no issues at all, and no one except you has this problem then we know for sure where the problem exists. Statistically speaking there is no other viable answer... The process is tried and proven over many years, and multiple OS's and every conceivable language for each of those OS's.

So either tell us truthfully and specifically what you're doing or we simply can't help.
If you use DriverPacks BASE and the DriverPacks the way it is explained in the tutorial IT WILL WORK.
It will absolutely delete the DriverPacks and related files automatically. Guaranteed, Period.
Billions of successful installs can't be wrong... 

I only have limited amount of patience. think carefully about everything I have already posted.
I have either already given you the answer or you have omitted Critical info from your responses or both.
(How do you create your disc? answer In Detail, step by step, right up to the burning of the disc!)

Two guesses here -

a) You burned the wrong source / ISO to the disc... DUH! wink
b) You made changes after DriverPacks BASE was run wink

Go to forum: Feedback and Support - DriverPacks Base

1,672 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

mr_smartepants wrote:
xman wrote:
2009-12-08 23:06:03 : <SLIP> Slipstream finished in 4 seconds.

That can't possibly be correct! yikes  Something MUST be wrong.
I've got a quad-core Q6600 and 8GB of DDR2 RAM and this is my score:

2009-12-06 12:33:41 : <SLIP> Slipstream finished in 1 minutes and 23 seconds.

I guess it's time to upgrade! big_smile

answer is in the log

DP_MassStorage_textmode = "no"

Still copying a few hundred meg of 7zip files in 4 seconds is cool wink

Go to forum: Feedback and Support - DriverPacks Base

1,673 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

Cool!

I thought they would be wink

Test it yet?


Oh Boy! I love logs!!!!

Wow... Slipstream finished in 4 seconds.  NICE machine you have there!
Looks like the slipstream went flawlessly and you stated the Winnt.sif entrys are there.
Now it should work - the finisher should e called right around the time of the first login to the GUI.
you should see the finisher banner on the screen... reboot after you get to the desktop. After the reboot then check for files wink I bet they are gone...

Go to forum: Feedback and Support - DriverPacks Base

1,674 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

if those lines don't exist in your winnt.sif then one of the two following things is true.

1) you made changes AFTER you slipstreamed DriverPacks. (although you stated previously you did not)

2) you had a critical error slipstreaming DriverPacks
  (please provide a valid DPs_BASE.log. The one above is no good since you only opened and closed the DriverPacks BASE gui. You did not slipstream anything wink you should be able to find an old one in C:\DPs_BASE_8125\LogFiles\. Hint: it will be bigger than the others wink OR you could slipstream a fresh source. and get a current log. [preferred])




Q) "I have MsDosInitiated=0.  Is 0 the same as NO?"
A) Same thing - Good question! It translates to "was this install started from floppy = no" 1=yes 0=no IDK if true and false work too, but they might smile



Again either the entry is not being written or it is being overwritten...


- Based on the fact that the following entry is missing from your winnt.sif

[GUIRunOnce]
command9="%SystemDrive%\DPsFnshr.exe"

- I bet 100% on the DriverPacks Finisher call is not even being written to the registry...
   The command to write it to the registry is missing from winnt.sif big_smile.
   That is a guaranteed failure, 100% probability.

Lets fix the missing lines in the Winnt.sif first.

Start with a clean source...
slipstream DriverPacks...
Are the winnt.sif lines shown above in the file? (yes or no)

If Yes then test the disc.

If No then choose from either #1) or #2) above to proceed with troubleshooting.

Go to forum: Feedback and Support - DriverPacks Base

1,675 Reply by OverFlow

(30 replies, posted in Feedback and Support - DriverPacks Base)

I am correcting you - you are wrong - the files should be deleted automaticaly~ tongue big_smile

I cross posted with your edit ( you edited your post after i posted wink )


* * * * * * You are running the finisher manually... That explains everything!!! * * * * *
Ok now we're getting somewhere!


the problem is that the guirunonce entry is not being added to the registry or is being overwritten....

from my post #4 of this thread... (I already asked you this - and told you this was what I thought the issue was)

OverFlow wrote:

I suspect that the finisher call, is not...  DPsFnshr.log wil be in %systemroot% (\Windows\DPsFnshr.log ?)
IF not then we know that your guirunonce call to the DriverPacks Finisher is failing wink

Are you editing the WinNT.sif (or anything else) after you slipstream the DriverPacks?

does this code exist in your \I386\Winnt.sif ?

[Data]
	MsDosInitiated=No

[Unattended]
	OemPreinstall=Yes
	DriverSigningPolicy=Ignore
	NonDriverSigningPolicy=Ignore
;
; Edited by DriverPacks BASE 8.12.5
; http://www.driverpacks.net/
;


[GUIRunOnce]
	command9="%SystemDrive%\DPsFnshr.exe"

There may be other lines and sections but we require at least the ones I pasted above.

Go to forum: Feedback and Support - DriverPacks Base