Topic: [IMPLEMENTED] Mute during KTD

I'd like to request a new feature of muting the sound while appling Keep-the-Drivers.  On the laptops I use, every time the "unsigned driver" window appears, the laptop beeps.  When keeping all the drivers, including 3rd party, this makes a lot of noise.  The mute/volume buttons on the laptop are software controlled and don't work during this time.  Also, oddly, having headphones plugged in does not disable the internal speaker.  Very annoying to me.  Unacceptable to my neighbors.

I've implemented a manual solution for this.  Since I use RUNONCEEX, I added a prior entry to mute, and a following entry to unmute as follows:

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY%\936 /VE /D "Mute Speaker" /f
REG ADD %KEY%\936 /V 1 /D "%~d0\$OEM$\mute.exe on" /f

REG ADD %KEY%\938 /VE /D "unMute Speaker" /f
REG ADD %KEY%\938 /V 1 /D "%~d0\$OEM$\mute.exe off" /f

(Note: I leave the DriverPacks at the defaulut 937.)

Since I couldn't find a reliable built-in mute method, I downloaded a file called "mute.exe" from:

http://www.pcworld.com/downloads/file_d … 480,00.asp

This does the job for me.  I thought others might benefit and it might be a nice feature for a future release. smile

proximous

Re: [IMPLEMENTED] Mute during KTD

proximous wrote:

Very annoying to me.  Unacceptable to my neighbors.

You must have thin walls, then! big_smile

Anyway, nice program/script.
I guess.
I always disable the SFC, so I don't get any pop-ups anyhow.
Though, once, I forgot to do so (no nLite prior to DP because I was testing some stuff) and I got this beeping galore. Must be very frustrating if you install a lot of PCs O_O

Re: [IMPLEMENTED] Mute during KTD

Ahh.  I was wondering why I didn't see other complaints about this.  I guess I should look up how to disable SFC.

Let me update my feature request then.  I'd like to see one of the following in a future version:

A) Mute during KTD
B) Option to disable SFC

Helmi wrote:
proximous wrote:

Very annoying to me.  Unacceptable to my neighbors.

You must have thin walls, then! big_smile

I work in a cube farm, so walls are few and far between, and VERY thin where the do exist.  wink

proximous

Re: [IMPLEMENTED] Mute during KTD

Wow smile big_smile

I'd never have thought of this smile

Founder of DriverPacks.net — wimleers.com

Re: [IMPLEMENTED] Mute during KTD

proximous wrote:

I guess I should look up how to disable SFC.

I'm using nLite for this task.
(The option is on the first page and a bit hidden under advanced options)

Re: [IMPLEMENTED] Mute during KTD

I've contacted the author to request permission to redistribute mute.exe in the BASE. Waiting for the reply now.

Founder of DriverPacks.net — wimleers.com

Re: [IMPLEMENTED] Mute during KTD

I've already gotten a reply from him and we have received permission smile

Founder of DriverPacks.net — wimleers.com

Re: [IMPLEMENTED] Mute during KTD

Implemented smile

- 0000355: [DriverPacks Finisher] Mute during KTD (BashratTheSneaky)

http://bugtracker.driverpacks.net/view.php?id=355

EDIT: included in 7.03rc3.

Last edited by Bâshrat the Sneaky (2007-03-25 08:50:17)

Founder of DriverPacks.net — wimleers.com

Re: [IMPLEMENTED] Mute during KTD

Excellent! Many thanks for making this a standard feature.  I hope it benefits many people.  I know it will make my neighbors happy.  smile

Re: [IMPLEMENTED] Mute during KTD

Is this feature available in 7.04?  If so, how do I enable it?  I just did an install using KTD (via RunOnce) with 7.04 Base and still heard the beeps.  Thanks.

Re: [IMPLEMENTED] Mute during KTD

proximous wrote:

Is this feature available in 7.04?  If so, how do I enable it?  I just did an install using KTD (via RunOnce) with 7.04 Base and still heard the beeps.  Thanks.

It's included and enabled in 7.04. Check your DPsFnshr.log for confirmation. (If you can't find it, post yur DPsFnshr.log (which resides in %SystemRoot%) here.)

Founder of DriverPacks.net — wimleers.com

Re: [IMPLEMENTED] Mute during KTD

Ok.  I tested a few times on a clean install (XP SP2 w/RyanVM 2.1.9) and I hear the beeps sad.  My DPsFnshr.log clearly says:

2007-04-29 22:21:44 : <KTD>  System sound muted (to prevent annoying beeping when unsigned driver warnings pop up).

Yet I still hear beeps.  I interrupted the process by rebooting, and I can see "mute.exe" at the root of the system drive.

Is there some other debug I should enable to more explicity see it turn on the mute?

Here is my full DPsFnshr.log (well, not the full file since it would makes my post >64KB...I noted where I cut the middle):

2007-04-29 22:21:38 : <INIT> DriverPacks Finisher 7.04 initialized.
2007-04-29 22:21:38 : <INIT> Splash screen initialized.
2007-04-29 22:21:38 : <INIT> Detected platform wnt5_x86-32.
2007-04-29 22:21:38 : <DBG>  Start logging of constants used in this program:
2007-04-29 22:21:38 : <DBG>  	$_DEBUG: True
2007-04-29 22:21:38 : <DBG>  	$_DPSTMP: C:\tmp
2007-04-29 22:21:38 : <DBG>  	$_LOGFILE: C:\WINDOWS\DPsFnshr.log
2007-04-29 22:21:38 : <DBG>  	$_NF: not found
2007-04-29 22:21:38 : <DBG>  	$_SETTINGSFILE: C:\DPsFnshr.ini
2007-04-29 22:21:38 : <DBG>  	$_SPLASHSCREEN: True
2007-04-29 22:21:38 : <INIT> Start logging of system variables available for use by the exceptions:
2007-04-29 22:21:38 : <INIT> 	%finisherdir% = C:
2007-04-29 22:21:38 : <INIT> 	%systemdrive% = C:
2007-04-29 22:21:38 : <INIT> 	%systemroot% = C:\WINDOWS
2007-04-29 22:21:38 : <INIT> 	%windir% = C:\WINDOWS
2007-04-29 22:21:38 : <INIT> 	%programfiles% = C:\Program Files
2007-04-29 22:21:38 : <INIT> 	%dpsroot% = 
2007-04-29 22:21:38 : <INIT> 	%dpstmp% = C:\tmp
2007-04-29 22:21:38 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2007-04-29 22:21:38 : <INIT> 1. ACPI devices

ACPI\ACPI0003\2&DABA3FF&0                                   : Microsoft AC Adapter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_13\_0                : Intel(R) Pentium(R) M processor 2.00GHz
ACPI\PNP0000\4&15F2F7D1&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&15F2F7D1&0                                   : System timer
ACPI\PNP0200\4&15F2F7D1&0                                   : Direct memory access controller
ACPI\PNP0303\4&15F2F7D1&0                                   : PS/2 Keyboard
ACPI\PNP0501\4&15F2F7D1&0                                   : Communications Port (COM1)
ACPI\PNP0800\4&15F2F7D1&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&15F2F7D1&0                                   : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C01\2                                              : System board
ACPI\PNP0C01\3                                              : System board
ACPI\PNP0C01\4                                              : System board
ACPI\PNP0C01\5                                              : System board
ACPI\PNP0C04\4&15F2F7D1&0                                   : Numeric data processor
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0F13\4&15F2F7D1&0                                   : Microsoft PS/2 Port Mouse (IntelliPoint)
ACPI\THERMALZONE\THM_                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Uniprocessor PC
25 matching device(s) found.

2007-04-29 22:21:39 : <INIT> 2. PCI devices

PCI\VEN_104C&DEV_8036&SUBSYS_01871028&REV_00\4&2FA23535&0&08F0: Generic CardBus Controller
PCI\VEN_104C&DEV_8038&SUBSYS_01871028&REV_00\4&2FA23535&0&0DF0: Texas Instruments PCI GemCore based SmartCard controller
PCI\VEN_10DE&DEV_00CC&SUBSYS_019B1028&REV_A2\4&27EA4097&0&0008: NVIDIA Quadro FX Go1400 
PCI\VEN_14E4&DEV_1677&SUBSYS_01871028&REV_01\4&2959CBDC&0&00E0: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_D3\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_2590&SUBSYS_00000000&REV_03\3&61AAA01&0&00 : Mobile Intel(R) 915GM/PM/GMS/910GML Express Processor to DRAM Controller - 2590
PCI\VEN_8086&DEV_2591&SUBSYS_00000000&REV_03\3&61AAA01&0&08 : Mobile Intel(R) 915GM/PM Express PCI Express Root Port - 2591
PCI\VEN_8086&DEV_2641&SUBSYS_00000000&REV_03\3&61AAA01&0&F8 : Intel(R) 82801FBM LPC Interface Controller - 2641
PCI\VEN_8086&DEV_2653&SUBSYS_01871028&REV_03\3&61AAA01&0&FA : Intel(R) 82801FBM Ultra ATA Storage Controllers - 2653
PCI\VEN_8086&DEV_2658&SUBSYS_01871028&REV_03\3&61AAA01&0&E8 : Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
PCI\VEN_8086&DEV_2659&SUBSYS_01871028&REV_03\3&61AAA01&0&E9 : Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
PCI\VEN_8086&DEV_265A&SUBSYS_01871028&REV_03\3&61AAA01&0&EA : Intel(R) 82801FB/FBM USB Universal Host Controller - 265A
PCI\VEN_8086&DEV_265B&SUBSYS_01871028&REV_03\3&61AAA01&0&EB : Intel(R) 82801FB/FBM USB Universal Host Controller - 265B
PCI\VEN_8086&DEV_265C&SUBSYS_01871028&REV_03\3&61AAA01&0&EF : Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C
PCI\VEN_8086&DEV_2660&SUBSYS_00000000&REV_03\3&61AAA01&0&E0 : Intel(R) 82801FB/FBM PCI Express Root Port - 2660
PCI\VEN_8086&DEV_266D&SUBSYS_542314F1&REV_03\3&61AAA01&0&F3 : Conexant D110 MDC V.92 Modem
PCI\VEN_8086&DEV_266E&SUBSYS_01871028&REV_03\3&61AAA01&0&F2 : SigmaTel C-Major Audio
PCI\VEN_8086&DEV_4220&SUBSYS_27218086&REV_05\4&2FA23535&0&18F0: Intel(R) PRO/Wireless 2200BG Network Connection
18 matching device(s) found.

2007-04-29 22:21:39 : <INIT> 3. HDAUDIO devices

No matching devices found.

2007-04-29 22:21:39 : <INIT> 4. USB devices

USB\ROOT_HUB\4&1A3FA9A8&0                                   : USB Root Hub
USB\ROOT_HUB\4&2FCC1C03&0                                   : USB Root Hub
USB\ROOT_HUB\4&32E54916&0                                   : USB Root Hub
USB\ROOT_HUB\4&BD95D31&0                                    : USB Root Hub
USB\ROOT_HUB20\4&293A87AB&0                                 : USB Root Hub
USB\VID_046D&PID_C016\5&1467709E&0&1                        : Corded Optical Wheel Mouse
USB\VID_413C&PID_8103\5&2A27AB68&0&1                        : Dell Wireless 350 Bluetooth Module
7 matching device(s) found.

2007-04-29 22:21:39 : <INIT> Logging of HWIDs complete.

****  THIS PART CUT DUE TO 64KB POSTING LIMIT ****

2007-04-29 22:21:43 : <FLTR> Finished filtering exceptions.
2007-04-29 22:21:43 : <DBG>  0 exceptions have forfilled the requirements to be executed!
2007-04-29 22:21:43 : <KTD>  KTD cache location set: "C:\WINDOWS\DriverPacks".
2007-04-29 22:21:44 : <KTD>  System sound muted (to prevent annoying beeping when unsigned driver warnings pop up).
2007-04-29 22:21:44 : <KTD>  KTD is enabled, in PATHS mode.
2007-04-29 22:23:01 : <KTD>  Moved drivers inside "C:\D" to "C:\WINDOWS\DriverPacks\D".
2007-04-29 22:23:01 : <KTD>  Successfully created the "%KTD%" environment variable, it has been set to "C:\WINDOWS\DriverPacks". It will be available after the next reboot.
2007-04-29 22:23:06 : <KTD>  Successfully updated the DevicePath registry value!

Re: [IMPLEMENTED] Mute during KTD

I've got the same problem - with the latest version 7.05.2 there are still a lot of beeps while the KTD-process!

Is there a solution for this "problem"?

Best regards

cool400 cool

Re: [IMPLEMENTED] Mute during KTD

Still beeping with 8.12.4... ("tested" on two totally different machines) :S

btw I'm using winnt32.exe install... but I don't think that it matters in this case...

Re: [IMPLEMENTED] Mute during KTD

It should be, not still, but, again.

For what it is worth, KTD is OUT. It never worked to satisfaction, and team found a much better alternative.
Less waste of time.
Updatable (KTD never was)
to your need. done proper, SAD will run a MINIsetup (with filtered by DriverPacks ) exceptions

The answer was 42?
Kind regards, Jaak.

Re: [IMPLEMENTED] Mute during KTD

I should have asked what DriverPacks BASE and DriverPacks you ran. and the logs.
I did not. I assumed you picked up on what you used, and what you read, and I dare bet there is a year's difference between what you read and searched for.
Get by, and welcome to US. We help you.
We CAN talk layman. We always assume you are a PRO.

The answer was 42?
Kind regards, Jaak.

Re: [IMPLEMENTED] Mute during KTD

FYI, this has never worked for me.  I still manually mute before the finisher runs.  I recently removed my own muting by accident, and noticed this has never been fixed.  I'm currently using 8.12.5.  Has anyone seen this work?  (Or should I say heard this work...or is it "not heard" and therefore know it works smile )

I'm still happy to debug if someone can point me in the right direction.

Re: [IMPLEMENTED] Mute during KTD

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?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [IMPLEMENTED] Mute during KTD

I use RUNONCE, so if I copy mute.exe myself, and set runonce to:

936: mute.exe on
937: DPfinisher
938: mute.exe off

Works great every time.  I have an addon that puts the mute on/off in my runonce, and I forget to include the addon in a recent build...and boy was I surprised when the PC started beeping like crazy. smile

...reminded me that the DP built-in version never worked for me.

Re: [IMPLEMENTED] Mute during KTD

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

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [IMPLEMENTED] Mute during KTD

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.

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?

Re: [IMPLEMENTED] Mute during KTD

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

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [IMPLEMENTED] Mute during KTD

Quick question...I'm trying to implement this...is "devpath" going to be at the root of the C drive before the finisher runs?  And am I correct to assume devpath is recursive?

Re: [IMPLEMENTED] Mute during KTD

I don't believe that devpath HAS to be at the root of the drive for you to do specificaly what you wish...

The DriverPacks Finisher will FAIL if it is not in the Root.

You should be able to write your script so that it expects "%SystemRoot%\devpath.exe".
Just be sure your copy of the files "KTD" is Prior to the finisher deleteing them, and devpath.
The finisher cleans everything up just like normal wink.

IE

 
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 1 /D "cmd /c start /wait copy %SystemDrive%\D\3\pack1 %SystemRoot%\D\"
REG ADD %KEY%\996 /V 2 /D "cmd /c start /wait copy %SystemDrive%\D\3\pack2 %SystemRoot%\D\"
REG ADD %KEY%\996 /V 3 /D "cmd /c start /wait copy %SystemDrive%\Devpath.exe %SystemRoot%\D\"
REG ADD %KEY%\996 /V 4 /D "cmd /c start /wait %SystemDrive%\DPsFnshr.exe"
REG ADD %KEY%\996 /V 5 /D "%SystemRoot%\D\Devpath.exe %SystemRoot%\D"

I have not tested the above example wink

yes devpath is recursive...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [IMPLEMENTED] Mute during KTD

Is there a reason you are running DPsFnshr.exe before Devpath.exe?  Does order matter?

Also, for anyone else trying to follow this, pay attention to %SystemDrive% vs %SystemRoot%.  Took me a while to track down that transcription error. tongue