np, Sil 3132, Bios v7.3.13 (Asus crosshair)
1 2007-02-11 07:26:49
Re: [SOLVED] Remove DriverPacks? (7 replies, posted in Feedback and Support - DriverPacks Base)
2 2007-02-11 06:22:31
Re: [SOLVED] Remove DriverPacks? (7 replies, posted in Feedback and Support - DriverPacks Base)
I kept bsoding during windows setup (installing on nvidia raid 0, sil sata.) I noticed mass storage drivers had been updated from 701 to 7011. Slipstreaming the DriverPacks again fixed the problem. thanks for your input.
3 2007-02-09 21:56:07
Re: [SOLVED] Remove DriverPacks? (7 replies, posted in Feedback and Support - DriverPacks Base)
it was the raid drivers. Is there a way i can just remove the text mode drivers from my install cd, or must I start over?
4 2007-02-08 12:24:54
Topic: [SOLVED] Remove DriverPacks? (7 replies, posted in Feedback and Support - DriverPacks Base)
I have just finished the perfect xp install..... and I happened to loose all my switchless installers and addons. I am having trouble setting up raid and would like to remove DriverPacks to eliminate it as the problem. How can i remove the driverpacks so that i can use my own sata/raid drivers without messing anything up?
Can i simply remove ROE.exe, the cmdlines.txt entry, and remove the oem folder it creates?
5 2006-10-19 13:48:37
Re: If Nlite and DriverPacks are giving you problems (8 replies, posted in Other)
nlite is going ok for me EXCEPT!!!!
Nlite visual effects are not working for me. Can I use reg tweaks or other methods to get the following results upon install? I also want cleartype enabled upon first boot.
6 2006-10-09 05:08:21
Re: If Nlite and DriverPacks are giving you problems (8 replies, posted in Other)
(I have been loyal and a fan of nlite for quite some time.... a year maybe two, but lately...) With both nLite-1.0.1 and nLite-1.2rc, I have experienced problems with visual tweaks not being implemented, the "Found New Hardware" wizard durring runonceex, etc, etc, etc...
It may very well be the corporate version of xp I am using causing the conflict. Nevertheless, the conflict is there... and after exhausting all other possibilities, I found that cutting nlite out of the process alltogether was the best solution (in my case.) I have access to an old retail copy of xp (pre sp1.) I will use this copy to try narrowing the cause of my problems.
Sorry for taking offense , Helmi
7 2006-10-09 01:38:24
Re: If Nlite and DriverPacks are giving you problems (8 replies, posted in Other)
I used to have issues with found new hardware wizard durring my runonceex application installs (some computers it would be an ethernet card, others a cd rom, etc.) After I cut Nlite this problem vanished. It may be my build (VRMPVOL_EN 2180.)
@Helmi and your insinuation that maybe i am too stupid to use nlite correctly.
I even got this problem when using Nlite ONLY to creat winnt.sif. In addition, I never removed much with nlite.... security center, error reporting, games, search assistant, tour, etc.
8 2006-10-08 12:32:09
Topic: If Nlite and DriverPacks are giving you problems (8 replies, posted in Other)
I started out using nlite, and then RVM Integrator. Ryan's post SP2 update pack turned a long tedious job into a one click process. Still, I stayed true to nlite, using it to intigrate the RVM update pack and many addons.
The third step in this evolution was DriverPacks by Bâshrat the Sneaky. At this point, I discovered several conflicts between the driverpack finisher and nlite.... So I began wondering if nlite was really needed.
Nlite is a great app for easy and fast tweaks, removing components, creating a winnt.sif. etc. But, I have recently discovered all these things can be done by hand, and (of course) by using the RVM intigrator.... thus nlite (although faster) is expendable. The rvm intigrator works great, when used with REGTWEAKS
and the addons for REMOVING WINDOWS COMPONENTS. (Thanks, keytotime)
I then discovered that there was no need to write the winnt.sif by hand. By extracting XPCD\SUPPORT\TOOLS\DEPLOY.CAB, and deleting all files except deploy.chm and setupmgr.exe, you can run setupmgr.exe to create your winnt.sif.
Since I have stopped using Nlite, and use only RVM Integrator (and my reg tweaks added at cmdlines.txt,) no more issues with DriverPacks driverpacks, or other Nlite (commonly experienced) bugs.
NOTE: This post is not ment to slander Nlite..... it is a great app and usefull tool. This post is meant as a solution for those who experience problems when using nlite in conjunction with DriverPacks.
9 2006-10-06 14:42:33
Re: [SOLVED BUG #272] Extra "D" Directory after KTD applied (24 replies, posted in Feedback and Support - DriverPacks Base)
same results with latest release
10 2006-10-05 09:19:04
Re: Injury... (19 replies, posted in News)
Be a man...... you can code with your nose! JK
Rest up, get well, get back to us when you are ready.
11 2006-10-03 12:33:46
Re: [SOLVED BUG #272] Extra "D" Directory after KTD applied (24 replies, posted in Feedback and Support - DriverPacks Base)
same problem here
C:\WINDOWS\DriverPacks\D\D
HKLM\Software\Microsoft\Windows\CurrenvtVersion\DevicePathis too large for me to post here... (it doesnt let me post it... is there a particular section you need?)
here is a portion
%KTD%\D\D\W\X\5;%KTD%\D\D\W\X\6;%KTD%\D\D\W\X\7;%KTD%\D\D\W\Z\2;%KTD%\D\D\W\Z\3;%KTD%\D\D\W\Z\4[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot = "%SystemDrive%"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "paths:D"
; system variables supported: %SystemDrive%, %SystemRoot% and %WinDir%, one
; location cannot be used as KTDlocation: the root directory specified in
; [Settings]\DPsRoot
KTDlocation = "%SystemRoot%\DriverPacks"12 2006-09-30 03:55:35
Topic: [SOLVED] MCE 2005 supported? (3 replies, posted in Feedback and Support - DriverPacks Base)
will driverpacks work ok with MCE 2005? I think some drivers are specifically for mce, but not sure.
13 2006-09-27 11:46:36
Re: [INACTIVE] Found New hardware wizard (9 replies, posted in Feedback and Support - DriverPacks Base)
i will buy some RWs tomorrow. my machine is set up so all my saved files and "My Documents" folder is on another hard drive..... so clean installing is no problem for me. I assumed the problem was Nlite, but after muiz3's statement I am not so sure. I will get back to you after tomorrows tests.
14 2006-09-25 13:53:15
Re: [INACTIVE] Found New hardware wizard (9 replies, posted in Feedback and Support - DriverPacks Base)
well... it defeats the purpose of pushing the install over a network. If i have to manually run around to 50 machines and hit ok, restart later..... I may as well manually install all the apps. there must be a solution.
15 2006-09-25 06:16:35
Re: [INACTIVE] Found New hardware wizard (9 replies, posted in Feedback and Support - DriverPacks Base)
i used nlite, and ryanvm update pack.... and i only removed a few components.....
nlite removed components:
;# Applications #
Internet Games
Pinball
Screensavers
;# Multimedia #
Media Center
Movie Maker
Music Samples
Speech Support
;# Network #
MSN Explorer
;# Operating System Options #
Desktop Cleanup Wizard
Disk Cleanup
DR Watson
Help
Out of Box Experience (OOBE)
Search Assistant
Security Center
Service Pack Messages
Tour
User Account Pictures
;# Services #
Alerter
Beep Driver
Error Reporting
Indexing Service
Messenger
Remote Registry
Removable Storage
System Restore
Telnet Server
I did use nlite to intigrate RVM post sp2 pack, along with a few other addons.
furthermore, I dont het this when installing in vmware, so i am making dvd coasters in order to fix this problem.
16 2006-09-25 05:59:34
Topic: [INACTIVE] Found New hardware wizard (9 replies, posted in Feedback and Support - DriverPacks Base)
Upon first boot, I get a found new harware wizard.... cdrom drive. I have used same installation on many machines and always get the same thing. Its no big deal, but its annoying because it happens durring app install via runonceex. Any suggestions how to fix this? I AM NOT INSTALLING AL120 OR DAEMON TOOLS. Found new hardware wizard just appears out of the blue.
17 2006-09-15 10:51:02
Re: DriverPack CPU 6.09 (39 replies, posted in DriverPack CPU)
Where do i find cpu 608, and does this mean i have to completely redo my xpcd, and re-apply driverpacks?
18 2006-09-15 03:46:58
Re: DriverPack CPU 6.09 (39 replies, posted in DriverPack CPU)
Same issue. dual core is also unknown cpu..... until i put the correct drivers in "3rd party" folder.
19 2006-09-14 17:59:43
Topic: [SOLVED] AMD dual core drivers (2 replies, posted in Feedback and Support - DriverPacks Base)
all drivers install fine.... except my cpu drivers. I downloaded the packs again to be sure nothing was corrupt. (The old nvidia drivers are installing as well.) I am using runoncex methos and kdt is enabled. any clues as to what the problem is?
finisher log:
2006-09-14 01:33:01 : <INIT> DriverPacks Finisher 6.08.6 initialized.
2006-09-14 01:33:01 : <INIT> Detected platform wnt5_x86-32.
2006-09-14 01:33:01 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-09-14 01:33:01 : <INIT> 1. ACPI devices
ACPI\ACPI0003\1 : Microsoft AC Adapter
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_35\_0
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_35\_1
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\PNP0001\4&5289E18&0 : EISA programmable interrupt controller
ACPI\PNP0100\4&5289E18&0 : System timer
ACPI\PNP0200\4&5289E18&0 : Direct memory access controller
ACPI\PNP0303\4&5289E18&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0400\5&324D5432&0 : Printer Port (LPT1)
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0501\2 : Communications Port (COM2)
ACPI\PNP0700\5&324D5432&0 : Standard floppy disk controller
ACPI\PNP0800\4&5289E18&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0A05\4&5289E18&0 : Generic Bus
ACPI\PNP0B00\4&5289E18&0 : System CMOS/real time clock
ACPI\PNP0C02\1F : Motherboard resources
ACPI\PNP0F13\4&5289E18&0 : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
20 matching device(s) found.
2006-09-14 01:33:02 : <INIT> 2. PCI devices
PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10\3&61AAA01&0&88 : AMD PCNET Family PCI Ethernet Adapter
PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61AAA01&0&80 : VMware SCSI Controller
PCI\VEN_1274&DEV_1371&SUBSYS_13711274&REV_02\3&61AAA01&0&90 : Multimedia Audio Controller
PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\3&61AAA01&0&78 : Video Controller (VGA Compatible)
PCI\VEN_8086&DEV_7110&SUBSYS_00000000&REV_08\3&61AAA01&0&38 : Intel 82371AB/EB PCI to ISA bridge (ISA mode)
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\3&61AAA01&0&39 : Intel(R) 82371AB/EB PCI Bus Master IDE Controller
PCI\VEN_8086&DEV_7112&SUBSYS_197615AD&REV_00\3&61AAA01&0&3A : Intel(R) 82371AB/EB PCI to USB Universal Host Controller
PCI\VEN_8086&DEV_7190&SUBSYS_00000000&REV_01\3&61AAA01&0&00 : Intel 82443BX Pentium(R) II Processor to PCI Bridge
PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_01\3&61AAA01&0&08 : Intel 82443BX Pentium(R) II Processor to AGP Controller
9 matching device(s) found.
2006-09-14 01:33:03 : <INIT> 3. HDAUDIO devices
No matching devices found.
2006-09-14 01:33:03 : <INIT> 4. USB devices
USB\ROOT_HUB\4&3788CC09&0 : USB Root Hub
1 matching device(s) found.
2006-09-14 01:33:03 : <INIT> Logging of HWIDs complete.
2006-09-14 01:33:03 : <INIT> Processed settings.
2006-09-14 01:33:04 : <FLTR> Collected the HWIDs for this system.
2006-09-14 01:33:04 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0001__D-G-A-1] (1 of 21 exceptions).
2006-09-14 01:33:04 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:04 : <FLTR> Found tagfile "C:\ATICCC.ins" (1/2).
2006-09-14 01:33:04 : <FLTR> Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-09-14 01:33:04 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-09-14 01:33:04 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2006-09-14 01:33:04 : <FLTR> Checking .inf file 'C:\D\G\A\1\C2_35179.inf'.
2006-09-14 01:33:05 : <FLTR> Checking .inf file 'C:\D\G\A\1\CX_35179.inf'.
2006-09-14 01:33:06 : <FLTR> Checking .inf file 'C:\D\G\A\1\CX_35181.inf'.
2006-09-14 01:33:06 : <FLTR> Checking .inf file 'C:\D\G\A\1\E2_35179.inf'.
2006-09-14 01:33:06 : <FLTR> Checking .inf file 'C:\D\G\A\1\EX_35179.inf'.
2006-09-14 01:33:06 : <FLTR> Checking .inf file 'C:\D\G\A\1\mobility.inf'.
2006-09-14 01:33:07 : <FLTR> ! Could not match any of the +infFiles.
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0002__D-G-A-1] (2 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0021__D-G-A-2] (3 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> Found tagfile "C:\ATICCC.ins" (1/2).
2006-09-14 01:33:07 : <FLTR> Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-09-14 01:33:07 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-09-14 01:33:07 : <FLTR> ! Could not match any of the +infFiles.
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0022__D-G-A-2] (4 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0003__D-G-A-3] (5 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> Found tagfile "C:\D\G\A\3\CPanel.exe" (1/1).
2006-09-14 01:33:07 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-09-14 01:33:07 : <FLTR> ! Could not match any of the +infFiles.
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0004__D-G-3-1] (6 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\3dfxV2ps.dll' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0005__D-G-S-1] (7 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sigrp.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0007__D-S-CR-1] (8 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha20x2k.sys' (1 of 2 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0008__D-S-CR-2] (9 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha10x2k.sys' (1 of 3 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0009__D-S-CR-3] (10 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\P17.sys' (1 of 2 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0010__D-S-H-2] (11 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-09-14 01:33:07 : <FLTR> ! Could not match any of the +infFiles.
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0011__D-S-N] (12 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\nvapu.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0012__D-S-S-U] (13 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sthda.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0013__D-S-SI-1] (14 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7012.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0014__D-S-SI-2] (15 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7018.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0015__D-S-T-2] (16 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\FM801.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0016__D-S-T-3] (17 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\cmaudio.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0017__D-S-T-4] (18 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\TT1724ht.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0018__D-S-T-5] (19 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\dmxsens.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0019__D-S-V-1] (20 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\envysens.sys' (1 of 1 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0020__D-S-V-2] (21 of 21 exceptions).
2006-09-14 01:33:07 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-09-14 01:33:07 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\vinyl97.sys' (1 of 2 tagfiles).
2006-09-14 01:33:07 : <FLTR> => This exception will not be applied.
2006-09-14 01:33:07 : <FLTR> Finished filtering exceptions.
2006-09-14 01:33:07 : <EXEC> No exceptions left to execute: none have met all requirements!
2006-09-14 01:33:07 : <KTD> KTD cache location set: "C:\WINDOWS\DriverPacks".
2006-09-14 01:33:07 : <KTD> KTD is enabled, in PATHS mode.
2006-09-14 01:33:07 : <KTD> Copy drivers inside "C:\D" to "C:\WINDOWS\DriverPacks\D".
2006-09-14 01:40:36 : <KTD> Successfully created the "%KTD%" environment variable, it has been set to "C:\WINDOWS\DriverPacks". It will be available after the next reboot.
2006-09-14 01:40:47 : <KTD> Successfully updated the DevicePath registry value!
2006-09-14 01:47:02 : <KTD> Successfully created the .pnf files. KTD has been applied! It will be available after the next reboot.
2006-09-14 01:47:35 : <CLNP> Deleted the DriverPacks, which were located in 'C:\D'.
2006-09-14 01:47:35 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-09-14 01:47:35 : <CLNP> Deleted 'C:\devcon.exe'!
2006-09-14 01:47:35 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-09-14 01:47:35 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-09-14 01:47:35 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-09-14 01:47:35 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-09-14 01:47:35 : Program terminated.