DriverPacks.net Forum - Annoying beeps when dpsfnsher does it's work

Re: Annoying beeps when dpsfnsher does it's work

2009-03-19T05:12:25Z

KTD is not the way to go for many reasons all of which SAD is the answer for.

Lets use your scenario for an example network card replacement
The tech is at the PC (self installing cards are still years away )
two possabilities exist have ODD or not.
if ODD is present drop SAD Disc in and run.
if ODD is unavaliable a SAD folder could have been left on the drive at install (KTD).
a SAD M2 Folder weighs in at like 320 MB for the main packs,
Physx and Language packs are 100 MB more if needed.

With a KTD setup the drivers take almost 2 GB...
and the driver will likely not install properly
- this is a result of the way KTD was designed, it has a few flaws.
- These flaws are addressed with SAD

Here is some related INFO it outlines SAD as a full replacement for KTD
Useing an M1 source for SAD gives you all the functionality of the MS DPInst.exe and the DriverPacks Finisher at the click of a button

Leaving the SAD M1 folder on the machine when it is loaded will provide BETTER than KTD results.
http://forum.driverpacks.net/viewtopic. … 710#p29710

hint
Install M1 with base
(make sure you turn on QSC so you only have to cab them once )
edit the Finisher INI (DPsFnshr.ini) and add this line
DPsRootDel = "false"
this is very important because the finisher will then not delete the folders - (and we have KTD)

Re: Annoying beeps when dpsfnsher does it's work

2009-03-18T23:06:57Z

Yes, I am using KTD. Is there a good reason I shouldn't use it? I figured that if someone ends up replacing a network card or sound card, etc. that it will be able
to utilize the drivers from the driver pack that way.

Also, Just verifying on my Winnt.sif file and the Driver Signing stuff is set to ignore, but the warnings still pop up during the 'KTD/Driver Pack cleanup' routine

[Unattended]
UnattendMode=FullUnattended
UnattendSwitch="No"
OemSkipEula="Yes"
FileSystem = LeaveAlone
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
Hibernation="No"
OemPreinstall=Yes
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

Re: Annoying beeps when dpsfnsher does it's work

2009-03-18T02:54:16Z

you did not tell us what you did... so i will assume you used KTD

KTD is not neccessary. dont use it, if you must use it then tell us why and we will see what can be done.

Re: Annoying beeps when dpsfnsher does it's work

2009-03-17T22:20:01Z

I'm getting the same problem. With previous versions of Driver Packs, there were only path problems where it couldn't find certain files and it would beep maybe 12-20 times and of course I'd have to click OK each time. Now, it doesn't complain about paths, but complains that it has not Passed Microsoft Windows blah blah blah and it moves on but ends up beeping about 300-400 times which can get annoying. Is there anyway to force windows to ignore that it has not passed therefor eliminating the beeps?

Re: Annoying beeps when dpsfnsher does it's work

2009-02-14T15:40:31Z

if you care to edit the hive - you can do it on the ISO

the answer is as early in the process as you wish

svcpack.inf might work nicely

more info here http://unattended.msfn.org/unattended.xp/view/web/27/

i will assume since the suggested user creation there is at T12 (around cmdlines.txt)
that since svcpack.inf runs just prior at T13 that is as good a place as any.

Re: Annoying beeps when dpsfnsher does it's work

2009-02-14T13:45:53Z

Once again, thanks for your patience and time spent on this thread.
After doing some investigation, I found the bug in our procedure.
Some time ago a problem with dpsfnshr.exe, that did not run correctly at the end of the presetup process, appeared.
As a workarround we placed a call to dpsfnshr.exe in RunOnceEx.cmd to overcome the problem.
Now, that dpsfnshr.exe runs as expected, it is called twice and generated these beeps and annoying pop-up windows.
Removing the second call to dpsfnshr.exe solved this issue.
Now our BartPe-, Driverpacks-, Database- and webconfigured unattend-install system does it's job nearly perfect.

Slight out off topic:
Although I did a lot of reading and investigation about unattended installs, I was not able to clear one important point at all.
In which phase of the windows setup process the settings for the default user and/or All users can be modified?

My approach to do it in RunOnceEx.cmd with:
REG ADD %KEY%\003 /V 2 /D "REGEDIT /S %systemdrive%\Apps\userset.reg" /f
only affects the Administrator or other autologged-in account after next login.
Where is the right place and time to do this kind of stuff?

Thanks for any hints and have a nice weekend
Guido

Re: Annoying beeps when dpsfnsher does it's work

2009-02-13T20:08:53Z

Thanks for the good details...

As Jaak always says "Help us to help you" and good details are the key to that

the read before you post is a good outline i always recomend reviewing it right before you start a topic or right before you save it, it may spark a memory of a detail you forgot about. in this case telling me you always modify presetup would have imediately told me where the issue was

Thanks so much for your feed back and please let me know if I can help!

Have a great day and best of luck!

Jeff

Re: Annoying beeps when dpsfnsher does it's work

2009-02-13T11:47:40Z

Thanks for your explanations regarding dpshnshr.exe and ist's components.
I think our problem is the automatic generated presetup.cmd.
We did some tweaking inside this file generated by an older version of dps_base.exe and used it as a template.
After each new run of dps_base.exe we placed a copy of this "template" into i386 directory, overwriting the actual
generated from dps_base.exe.
Since something inside presetup.cmd must have been changed, I'll have a closer look at the presetup.cmd generated by the new dps_base_8124.exe.

SAD is on my to view list.
:-)

Re: Annoying beeps when dpsfnsher does it's work

2009-02-13T10:38:54Z

it will only use the newest pack

That log is no good it shows base was opened and closed and no slipstream was done

mute is in OEM\bin\DPsFnshr.7z and should be extracted by presetup and then run when finisher is performing KTD on the target machine

KTD is now obsolete
please take a look at SAD as a replacement for KTD

Re: Annoying beeps when dpsfnsher does it's work

2009-02-13T08:21:36Z

Sorry, but I can't find find mute.exe in any location, perhaps this is the problem...
Method 2 was used for integrating DriverPacks into our install-share.
After examening the logfile, I found an actual and an older version of MassStorage detected through
the dps_base script.
Is this a problem and do I have to move the older dps_x_packs to a different location?
Until now I thought dps_base script only uses the newer version of any found DriverPacks.

Here is dps_base.log:
----------------------------------------------------------------------------------------------------------
2009-02-11 19:05:29 : DriverPacks BASE 8.12.4 initialized.
2009-02-11 19:05:29 : Host environment: WIN_XP Service Pack 2 on X86 CPU.
2009-02-11 19:05:29 : Created temporary working directory.
2009-02-11 19:05:29 : Imported proxy settings from Internet Explorer.
2009-02-11 19:05:29 : Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-02-11 19:05:29 : Detected DriverPack Chipset 803!
2009-02-11 19:05:29 : Detected DriverPack CPU 804!
2009-02-11 19:05:29 : Detected DriverPack Graphics A 804!
2009-02-11 19:05:29 : Detected DriverPack Graphics A 8121!
2009-02-11 19:05:29 : Detected DriverPack Graphics B 8121!
2009-02-11 19:05:29 : Detected DriverPack Graphics C 8121!
2009-02-11 19:05:29 : Detected DriverPack LAN 8053!
2009-02-11 19:05:29 : Detected DriverPack LAN 8121!
2009-02-11 19:05:29 : Detected DriverPack MassStorage 805!
2009-02-11 19:05:29 : Detected DriverPack MassStorage 901!
2009-02-11 19:05:29 : Detected DriverPack Sound A 804!
2009-02-11 19:05:29 : Detected DriverPack Sound A 805!
2009-02-11 19:05:29 : Detected DriverPack Sound B 805!
2009-02-11 19:05:29 : Detected DriverPack WLAN 803!
2009-02-11 19:05:29 : Detected DriverPack WLAN 806!
2009-02-11 19:05:29 : Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-02-11 19:05:29 : Finished scanning.
2009-02-11 19:05:29 : Detected settings file "\\asterisk\Software\Unattend\install\DP\DPs_BASE.ini".
2009-02-11 19:05:30 : Windows XP Professional - OEM SP3 detected.
2009-02-11 19:05:30 : [Settings]\DPsMethod not specified: default (2) was set.
2009-02-11 19:05:30 : [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-02-11 19:05:30 : [OptionalSettings]\KTD not specified: default (none) was set.
2009-02-11 19:05:30 : [OptionalSettings]\QSC not specified: default (yes) was set.
2009-02-11 19:05:30 : [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-02-11 19:05:30 : [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-02-11 19:05:30 : wnt5_x86-32_disc is the selected installation platform .
2009-02-11 19:05:30 : Imported settings from settings file.
2009-02-11 19:05:30 : Initialized GUI.
2009-02-11 19:05:30 : Created a list of all available language files.
2009-02-11 19:05:30 : Set the last used language, English, as the GUI language.
2009-02-11 19:05:48 : Closed GUI.
2009-02-11 19:05:48 : Saved settings!
2009-02-11 19:05:48 : Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"

[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "\\asterisk\install\os\UXPPSP3"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "all"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"

; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "all"
; , to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"

; this section is optional!
[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl = "CCC"
Nvidia_cpl = "2"
2009-02-11 19:05:48 : Create a DPs_Base.log backup @ \\asterisk\Software\Unattend\install\DP\LogFiles\DPs_BASE_09-02-11_19-05.log
2009-02-11 19:05:48 : Program terminated.

------------------------------------------------------------------------------------------

Re: Annoying beeps when dpsfnsher does it's work

2009-02-12T22:59:01Z

for some reason MUTE.EXE is not running.

Perhaps if you provide some details... IE DPs_BASE.log and some details about yoru process to create your disc?

Annoying beeps when dpsfnsher does it's work

2009-02-12T17:44:16Z

While dpsfnsher runs and kills popup-windows from the driver signing policy each action
is followed by a beep.
In older version(s) of dps_base these windows closed silently.

Anyone an idea what happened and what can be done to fix this behaviour?

Regards

Guido