<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[DriverPacks.net Forum - Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
		<link>http://forum.driverpacks.net/viewtopic.php?id=5336</link>
		<description><![CDATA[The most recent posts in Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7).]]></description>
		<lastBuildDate>Mon, 02 Mar 2026 12:20:19 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=59292#p59292</link>
			<description><![CDATA[<p>I&#039;ve made some significant progress to my powershell project.&nbsp; My prior post had the basics here: <a href="http://forum.driverpacks.net/viewtopic.php?pid=59275#p59275">http://forum.driverpacks.net/viewtopic. … 275#p59275</a></p><p>The below code (generated with the help of AI) seems to run just fine in Win10/Win11 post-install environments, but should work in Win7/8 also.&nbsp; Because of syntax differences between powershell versions, I&#039;ve added an OS discriminator to handle the different command options. I&#039;m not convinced this new longer script is any &quot;better&quot; than my previous short script.&nbsp; I&#039;m not sure the AI code can be trusted.<br />I may toy with placing everything in the $WinPEDriver$ folder at the root of the install medium to make the drivers available during the OS install process for a future version.&nbsp; There are valid reasons to NOT use $WinPEDriver$ folder, but the benefits outweigh the problems I think.<br />It has basic logging and is launched by a &quot;helper&quot; install.bat.</p><p>Install.bat<br /></p><div class="codebox"><pre><code>@echo OFF
SET WorkingDir=%cd%
SET PSPath=&#039;%WorkingDir%\Install-SpecifiedDrivers.ps1&#039;
PowerShell -NoProfile -ExecutionPolicy Bypass -Command &quot;&amp; %PSPath%&quot;</code></pre></div><p>Install-SpecifiedDrivers.ps1<br /></p><div class="codebox"><pre><code># ========================
# Version 2.2 by Erik Hansen
# Universal driver installer with privilege elevation using existing Microsoft OS tools.
# Install and/or upgrade any drivers specified in the .\drivers directory using pnputil.exe
# Recursively finds each driver installer file INF in the specified folder and uses pnputil to inject the driver into the running OS.
# ========================
# Don&#039;t execute this .ps1 script directly, use &quot;helper script&quot; Install_1st.bat
# ========================
# =============================================================================
# Self-Elevation Check - MUST BE AT THE TOP OF THE SCRIPT
# =============================================================================
#
# 1. Check if the current session is running as an Administrator.
# 2. If not, it re-launches the script in a new, elevated PowerShell window.
# 3. The original, non-elevated script then immediately exits.
# =============================================================================
# Get the identity of the current user
# =============================================================================
 
$currentUser = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$windowsPrincipal = [System.Security.Principal.WindowsPrincipal]$currentUser
 
# Check if the user is a member of the &#039;Administrators&#039; group
if (-not $windowsPrincipal.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)) {
    # If not an admin, re-launch the script with elevated privileges
    try {
        Write-Warning &quot;This script requires administrator privileges. Attempting to re-launch with elevation...&quot;
        # Build the arguments to pass to the new process
        $arguments = &quot;&amp; &#039;$PSCommandPath&#039;&quot;
        # Start a new PowerShell process with the &#039;RunAs&#039; verb to trigger UAC
        Start-Process powershell.exe -Verb RunAs -ArgumentList $arguments -ErrorAction Stop
        # Exit the current, non-elevated script
        # The &#039;exit&#039; is crucial to prevent the rest of the script from running in the non-admin context and failing.
        exit
    }
    catch {
        Write-Error &quot;Failed to re-launch with elevated privileges. Please right-click the script and choose &#039;Run as Administrator&#039;.&quot;
        # Pause to allow the user to read the error before the window closes
        Start-Sleep -Seconds 10
        exit
    }
}
# If the script reaches this point, it is confirmed to be running as an administrator.
Write-Host &quot;Script is running with administrator privileges.&quot;
# =============================================================================
# End of Elevation Check
# =============================================================================
 
# =============================================================================
# Begin actual work
# =============================================================================
 
# Set string variables, paths, and environment
# Explicitly sets the log path.  If running from a read-only device, change this path to a writeable directory.
$TempLogs = &quot;$env:HOMEDRIVE\Temp\Logs\Install-SpecifiedDrivers_LOG.txt&quot;
$PSScriptRoot = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition
 
# Start log.  Remove the &#039;-Append&#039; option to create new log from scratch.
Start-Transcript -Path $TempLogs -Append
 
# Get all INF files from the drivers directory
# Explicitly sets the path to the drivers directory. Change this to where your drivers are stored.
$driverFiles = Get-ChildItem -Path &quot;$PSScriptRoot\drivers&quot; -Recurse -Filter &quot;*.inf&quot;
Write-Host &quot;Found $($driverFiles.Count) driver packages. Checking for installation or upgrade...&quot;
 
# =============================================================================
# --- OS Version-Aware Driver Enumeration ---
# =============================================================================
$installedDrivers = $null
 
# Get the Major version of the OS. Windows 7 is 6.1, Windows 8 is 6.2, Win 8.1 is 6.3, Win 10/11 are 10.0
$osMajorVersion = [System.Environment]::OSVersion.Version.Major
 
if ($osMajorVersion -ge 10 -or ($osMajorVersion -eq 6 -and [System.Environment]::OSVersion.Version.Minor -ge 2)) {
    # OS is Windows 8 or newer (including 10 and 11)
    Write-Host &quot;OS is Windows 8 or newer. Using &#039;Get-WindowsDriver&#039;...&quot;
    $installedDrivers = Get-WindowsDriver -Online | Where-Object { $_.ProviderName -ne &quot;Microsoft&quot; }
}
else {
    # OS is Windows 7. Use the WMI fallback.
    Write-Host &quot;OS is Windows 7. Using &#039;Get-WmiObject&#039; fallback...&quot;
    # The property names from WMI are different, so we use calculated properties
    # to make the output object look the same as the one from Get-WindowsDriver.
    $installedDrivers = Get-WmiObject Win32_PnPSignedDriver | `
        Where-Object { $_.Manufacturer -ne &quot;Microsoft&quot; } | `
        Select-Object @{Name=&quot;ProviderName&quot;; Expression={$_.Manufacturer}}, @{Name=&quot;Version&quot;; Expression={$_.DriverVersion}}
}
 
if ($installedDrivers -eq $null) {
    Write-Warning &quot;Could not retrieve a list of installed drivers. The upgrade logic will assume no drivers are installed.&quot;
}
# =============================================================================
# --- Begin Driver Enumeration and Comparison ---
# =============================================================================
 
foreach ($infFile in $driverFiles) {
    try {
        # Read the INF file content as an array of lines
        $infLines = Get-Content -Path $infFile.FullName -ErrorAction Stop
        # Find the initial Provider line and Driver Version using regex
        $providerLine = $infLines | Select-String -Pattern &quot;^\s*Provider\s*=\s*(.+)&quot;
        $versionLine = $infLines | Select-String -Pattern &quot;^\s*DriverVer\s*=\s*(.+)&quot;
 
        if (-not ($providerLine -and $versionLine)) {
            Write-Warning &quot;Could not find a valid Provider or DriverVer line in $($infFile.Name). Skipping.&quot;
            continue
        }
 
        # --- Resolve the Provider token two-step---
       
        # 1. Get the initial token (e.g., &quot;%ManufacturerName%&quot;)
        $providerToken = $providerLine.Matches[0].Groups[1].Value.Trim()
        $resolvedProvider = &quot;&quot;
 
        # 2. Check if it&#039;s a token that needs resolving
        if ($providerToken.StartsWith(&#039;%&#039;) -and $providerToken.EndsWith(&#039;%&#039;)) {
            # It&#039;s a token. Let&#039;s find its value in the [Manufacturer] section.
           
            # Remove the &#039;%&#039; characters to get the lookup key (e.g., &quot;ManufacturerName&quot;)
            $lookupKey = $providerToken -replace &#039;%&#039;
            # Find the start of the [Manufacturer] section
            $mfgSectionLineNum = ($infLines | Select-String -Pattern &#039;^\s*\[Manufacturer\]&#039; -List).LineNumber
           
            if ($mfgSectionLineNum) {
                # Search for the key only in the lines *after* the [Manufacturer] section header
                # The pattern looks for &quot;key = value,...&quot; and captures &quot;value&quot;
                $resolvedLine = $infLines[$mfgSectionLineNum..($infLines.Count - 1)] | `
                    Select-String -Pattern &quot;^\s*$lookupKey\s*=\s*([^,]+)&quot; | `
                    Select-Object -First 1
         # From here, use the $resolvedProvider variable for either option              
                if ($resolvedLine) {
                    # The actual provider name is the first captured group
                    $resolvedProvider = $resolvedLine.Matches[0].Groups[1].Value.Trim()
                }
            }
        } else {
            # It&#039;s not a token, so the value is literal.
            $resolvedProvider = $providerToken
        }
 
        if ([string]::IsNullOrWhiteSpace($resolvedProvider)) {
            Write-Warning &quot;Could not resolve provider name for token &#039;$providerToken&#039; in $($infFile.Name). Skipping.&quot;
            continue
        }
 
        # ----------------------------------------------
        # The rest of the logic remains the same, using the now-correct $infProvider
        $infProvider = $resolvedProvider
        $infVersionString = ($versionLine.Matches[0].Groups[1].Value.Split(&#039;,&#039;)[1]).Trim()
        $infVersion = [System.Version]$infVersionString
 
# =============================================================================
# --- Begin Driver Injection using pnputil.exe ---
# =============================================================================
        # Rack and stack the INF file content array and only process driver files that are newer than already installed.
        Write-Host &quot;Processing driver: $($infFile.Name) | Provider: $infProvider | Version: $infVersion&quot;
        $matchingInstalledDriver = $installedDrivers | Where-Object { $_.ProviderName -eq $infProvider } | Sort-Object -Property Version -Descending | Select-Object -First 1

        if ($matchingInstalledDriver) {
            $installedVersion = [System.Version]$matchingInstalledDriver.Version
            # We matched a newer driver than what is installed on the system.  Yay!
            Write-Host &quot;Found installed driver from provider &#039;$infProvider&#039; with version $installedVersion.&quot;
            if ($infVersion -gt $installedVersion) {
                Write-Host &quot;Newer version $infVersion found for $($infFile.Name). Upgrading...&quot;
                pnputil.exe /add-driver $infFile.FullName /install
                Write-Host &quot;SUCCESS: Upgraded driver from $($infFile.FullName).&quot;
            } else {
                Write-Host &quot;Installed version ($installedVersion) is the same or newer. No action needed.&quot;
            }
        } else {
            # We didn&#039;t find an existing driver to match the scanned driver. Pushing the driver through pnputil and let the system sort it out.
            # If it works, great.  If it fails, not our problem.
            Write-Host &quot;No existing driver found for provider &#039;$infProvider&#039;. Installing...&quot;
            pnputil.exe /add-driver $infFile.FullName /install
            Write-Host &quot;SUCCESS: Installed new driver from $($infFile.FullName).&quot;
        }
    }
    catch {
        Write-Error &quot;An error occurred while processing $($infFile.FullName): $_&quot;
    }
    Write-Host &quot;---&quot;
}
 
# Stop log
Write-Host &quot;--- All processing complete at $(Get-Date) ---&quot;
Write-Host &quot;--- Finished on computer: $env:COMPUTERNAME ---&quot;
Stop-Transcript</code></pre></div>]]></description>
			<author><![CDATA[null@example.com (mr_smartepants)]]></author>
			<pubDate>Mon, 02 Mar 2026 12:20:19 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=59292#p59292</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=59278#p59278</link>
			<description><![CDATA[<p>Hi,<br />I accidentally glanced at the forum while doing some tidying up on my portable drive ;-). Have you moved anything forward with the project? I currently run SDI after installing Windows which does the job most of the time, and if not WindowsUpdate. Nice to have been involved in the development of such a useful tool when I was young.</p>]]></description>
			<author><![CDATA[null@example.com (dziubek)]]></author>
			<pubDate>Sat, 14 Sep 2024 08:55:58 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=59278#p59278</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=59275#p59275</link>
			<description><![CDATA[<p>Hi all.<br />Despite the rumors to the contrary, I am very much alive and well.&nbsp; I just checked the site logs and it looks like my last post here was nearly 10 years ago (yikes!).&nbsp; I spent a few years working for LinMin building a bare-metal deployment toolkit for them (which is sadly VERY closed-source by NDA).&nbsp; The source code for this was more than 3000 lines of code and incorporated code obfuscation and piracy countermeasures...I&#039;m pretty proud of it, but nobody will ever see it. <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /></p><p>I poked my head in here to see if anyone had done any scripting work on getting drivers loaded into Windows 11.&nbsp; We&#039;ve taken delivery of several hundred Dell laptops at work, and the USAF Win11 SDC (standard desktop configuration) image doesn&#039;t have any drivers included for this hardware.&nbsp; I spoke with one of our IT members and they&#039;ve been struggling to load all of these drivers manually (and individually)...what dumbasses!&nbsp; Several years ago I wrote a script to take the SDC image apart, inject drivers for mass-storage, and include a $OEM$ folder containing a universal driver deployment folder before repacking the image for deployment.&nbsp; Apparently, they&#039;re not allowed to do that anymore, so my prior work goes unused.<br />Anyway, they&#039;re pulling this old fart out of retirement so to speak (this is not part of my daily job) to build a PowerShell scripting tool to help them automate the driver updating process.&nbsp; This needs to be done in-house and without the use of external utilities (like SDI or 7zip) and rely purely on applets included within the OS.<br />The core function of updating drivers on running Win10/Win11 is provided by the included utility of PNPUtil.exe which can be expressed simply with the command: </p><div class="codebox"><pre><code>Get-ChildItem &quot;C:\mydrivers\&quot; -Recurse -Filter &quot;*.inf&quot; | 
ForEach-Object { PNPUtil.exe /add-driver $_.FullName /install }</code></pre></div><p>Here&#039;s more info on some of the modularity available with powershell.&nbsp; <a href="https://hudson.tel/post/mass-driver-installation-using-powershell-and-intune/">https://hudson.tel/post/mass-driver-ins … nd-intune/</a><br />I might post my results here once I&#039;m done with a proof-of-concept.<br />If anyone has ideas to help me along, I&#039;m all ears.&nbsp; I&#039;m at day-1.<br />*Edit<br />The below code seems to run just fine.&nbsp; It has basic logging and is launched by a &quot;helper&quot; install.bat.<br />Install.bat<br /></p><div class="codebox"><pre><code>SET WorkingDir=%cd%
SET PSPath=&#039;%WorkingDir%\Install-SpecifiedDrivers.ps1&#039;
PowerShell -NoProfile -ExecutionPolicy Bypass -Command &quot;&amp; %PSPath%&quot;</code></pre></div><p>Install-SpecifiedDrivers.ps1<br /></p><div class="codebox"><pre><code># Install any drivers specified in the .\drivers directory using pnputil.exe

$TempLogs = &quot;$env:HOMEDRIVE\Temp\Logs\Install-SpecifiedDrivers_LOG.txt&quot;
$PSScriptRoot = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition

Start-Transcript -Path $TempLogs

Get-ChildItem &quot;$PSScriptRoot\drivers\&quot; -Recurse -Filter &quot;*.inf&quot; | 
    ForEach-Object { 
        $DriverFullName = $_.FullName
        pnputil.exe /add-driver $DriverFullName /install
        Write-Host &quot;Driver: $DriverFullName&quot;
    }

Stop-Transcript</code></pre></div><p>Works by scanning the /drivers/ subfolders for any .inf files and then using pnputil to install that driver and move on to the next.&nbsp; It will not upgrade existing installed drivers (I need to tinker with the &quot;enumerate&quot; command for that).&nbsp; It also does not run from a optical drive (CD/DVD).&nbsp; It&#039;s simple, and it works.</p>]]></description>
			<author><![CDATA[null@example.com (mr_smartepants)]]></author>
			<pubDate>Mon, 18 Mar 2024 18:56:09 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=59275#p59275</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58984#p58984</link>
			<description><![CDATA[<p>That didn&#039;t help.</p><p>I&#039;ve done a bit more testing stuff. Here is the DP_Install_Tool.log from one of the affected PCs:</p><div class="codebox"><pre><code>v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
Z:\installers2\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
Z:\installers2\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
Z:\installers2\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
C:\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
C:\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
C:\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
v13.08.25 Log and Attended output section 
*
*
Method 2 was found at:
C:\SAD3\NT6\x86
List INF&#039;s that were matched with this system
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\l\realtek\2\win7\rt86win7.inf&#039;.
Successfull installation of &#039;c:\d\x86\win7\c\amd\1\smbus\w7\smbusamd.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\realtek_hda\wdm\hdart.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\win2000\atk2000.inf&#039;.
Successfull installation of &#039;c:\d\dp_ebcf_wnt6-x86_1604\all\ebcf\acpi\acpi\winvista\asacpi.inf&#039;.</code></pre></div><p>The first three runs, from Z:\, were automatic with the /SR switch and did not have access to my custom pack. Already I notice something odd: Driverpacks reporting it installs a Matrox driver from the Graphics B pack. I&#039;m pretty sure the PC has ATI graphics not Matrox.</p><p>The fourth run was with the standard script, again with the /SR switch, with my custom pack. (Which I tweaked the folder structure of a bit). It picks up some drivers out of that pack, but not the ATI graphics.</p><p>The fifth (and subsequent) run was with your modification.</p><p>The sixth run is where I&#039;m frankly baffled. For this run I had only my custom pack in C:\SAD3\NT6\x86. None of the standard packs. There was no C:\D folder before or after the run. And yet Driverpacks still reports itself installing the drivers from the standard packs. Where is it even getting those files from? The log says <em>&quot;Successfull installation of &#039;c:\d\x86\all\g_b\matrox\1\mxeff.inf&#039;.&quot;</em> when that file should not even have existed.</p><p>For the seventh run I ran it with the /CR switch, still with only my custom pack, just for the sake of trying something. Afterwards, C:\D contained only that custom pack.</p>]]></description>
			<author><![CDATA[null@example.com (cantab)]]></author>
			<pubDate>Wed, 04 May 2016 15:52:05 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58984#p58984</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58977#p58977</link>
			<description><![CDATA[<p>you can try to change line 439 in DP_Install_Tool.cmd from<br />Start &quot;MicroSoft Driver Installer Tool Running&quot; /wait /separate /realtime /min CMD /C DPInst.exe /c /s<br />to<br />Start &quot;MicroSoft Driver Installer Tool Running&quot; /wait /separate /realtime /min CMD /C DPInst.exe /c /s /f</p><p>The /f (force install older) switch may work for you in this case, or not. Since this looks like a custom pack for this machine you may just get away with it. Try it and let me know.</p><p>Jeff</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Thu, 28 Apr 2016 14:30:26 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58977#p58977</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58975#p58975</link>
			<description><![CDATA[<p>Yeah. This is the directory structure of my custom pack</p><div class="codebox"><pre><code>.
|-- 10-02_legacy_vista32-64_dd_ccc
|   |-- Bin
|   |   |-- ATILog.dll
|   |   |-- ATIManifestDLMExt.dll
|   |   |-- ATISetup.exe
|   |   |-- CRCVerDLMExt.dll
|   |   |-- CompressionDLMExt.dll
|   |   |-- ControlCenterActions.dll
|   |   |-- DLMCom.dll
|   |   |-- DetectionManager.dll
|   |   |-- EncryptionDLMExt.dll
|   |   |-- InstallManager.dll
|   |   |-- InstallManagerApp.exe
|   |   |-- InstallManagerApp.exe.manifest
|   |   |-- LanguageMgr.dll
|   |   |-- Microsoft.VC80.ATL.manifest
|   |   |-- Microsoft.VC80.CRT.manifest
|   |   |-- Microsoft.VC80.MFC.manifest
|   |   |-- Microsoft.VC80.MFCLOC.manifest
|   |   |-- Microsoft.VC80.OpenMP.manifest
|   |   |-- PackageManager.dll
|   |   |-- Setup.exe
|   |   |-- Setup.exe.manifest
|   |   |-- atidcmxx.sys
|   |   |-- difxapi.dll
|   |   |-- mfc80u.dll
|   |   |-- msvcp80.dll
|   |   |-- msvcr80.dll
|   |   |-- xerces-c_2_6.dll
|   |   `-- zlibwapi.dll
|   |-- Bin64
|   |   |-- ATILog.dll
|   |   |-- ATIManifestDLMExt.dll
|   |   |-- ATISetup.exe
|   |   |-- CRCVerDLMExt.dll
|   |   |-- CompressionDLMExt.dll
|   |   |-- ControlCenterActions.dll
|   |   |-- DLMCom.dll
|   |   |-- DetectionManager.dll
|   |   |-- EncryptionDLMExt.dll
|   |   |-- InstallManager.dll
|   |   |-- InstallManagerApp.exe
|   |   |-- InstallManagerApp.exe.manifest
|   |   |-- LanguageMgr.dll
|   |   |-- Microsoft.VC80.ATL.manifest
|   |   |-- Microsoft.VC80.CRT.manifest
|   |   |-- Microsoft.VC80.MFC.manifest
|   |   |-- Microsoft.VC80.MFCLOC.manifest
|   |   |-- Microsoft.VC80.OpenMP.manifest
|   |   |-- PackageManager.dll
|   |   |-- Setup.exe
|   |   |-- Setup.exe.manifest
|   |   |-- atdcm64a.sys
|   |   |-- difxapi.dll
|   |   |-- mfc80u.dll
|   |   |-- msvcp80.dll
|   |   |-- msvcr80.dll
|   |   |-- xerces-c_2_6.dll
|   |   `-- zlibwapi.dll
|   |-- Config
|   |   |-- DLMServer.cfg
|   |   |-- InstallManager.cfg
|   |   |-- Language.Dat
|   |   |-- MMTableRev0.MSI
|   |   |-- MMTableRev1.MSI
|   |   |-- MMTableRev2.MSI
|   |   |-- Monet.ini
|   |   |-- MonetCHS.xml
|   |   |-- MonetCHT.xml
|   |   |-- MonetCSY.xml
|   |   |-- MonetDAN.xml
|   |   |-- MonetDEU.xml
|   |   |-- MonetENU.xml
|   |   |-- MonetESP.xml
|   |   |-- MonetFIN.xml
|   |   |-- MonetFRA.xml
|   |   |-- MonetGRK.xml
|   |   |-- MonetHNG.xml
|   |   |-- MonetITA.xml
|   |   |-- MonetJPN.xml
|   |   |-- MonetKOR.xml
|   |   |-- MonetNLD.xml
|   |   |-- MonetNOR.xml
|   |   |-- MonetPLK.xml
|   |   |-- MonetPTB.xml
|   |   |-- MonetRSA.xml
|   |   |-- MonetSVE.xml
|   |   |-- MonetTHA.xml
|   |   |-- MonetTRK.xml
|   |   |-- OEM.Dat
|   |   |-- OS.Dat
|   |   |-- OSMajorMinor.Dat
|   |   |-- OSServicePacks.Dat
|   |   |-- PackageSubType.Dat
|   |   |-- PackageType.Dat
|   |   |-- Security.Dat
|   |   |-- Splash.bmp
|   |   |-- TVW_USB_ID.MSI
|   |   |-- atiicdxx.msi
|   |   |-- chipset.MSI
|   |   |-- eulaCHS.txt
|   |   |-- eulaCHT.txt
|   |   |-- eulaCSY.txt
|   |   |-- eulaDAN.txt
|   |   |-- eulaDEU.txt
|   |   |-- eulaENU.txt
|   |   |-- eulaESP.txt
|   |   |-- eulaFIN.txt
|   |   |-- eulaFRA.txt
|   |   |-- eulaGRK.txt
|   |   |-- eulaHNG.txt
|   |   |-- eulaITA.txt
|   |   |-- eulaJPN.txt
|   |   |-- eulaKOR.txt
|   |   |-- eulaNLD.txt
|   |   |-- eulaNOR.txt
|   |   |-- eulaPLK.txt
|   |   |-- eulaPTB.txt
|   |   |-- eulaRSA.txt
|   |   |-- eulaSVE.txt
|   |   |-- eulaTHA.txt
|   |   |-- eulaTRK.txt
|   |   |-- licenseCHS.txt
|   |   |-- licenseCHT.txt
|   |   |-- licenseCSY.txt
|   |   |-- licenseDAN.txt
|   |   |-- licenseDEU.txt
|   |   |-- licenseENU.txt
|   |   |-- licenseESP.txt
|   |   |-- licenseFIN.txt
|   |   |-- licenseFRA.txt
|   |   |-- licenseGRK.txt
|   |   |-- licenseHNG.txt
|   |   |-- licenseITA.txt
|   |   |-- licenseJPN.txt
|   |   |-- licenseKOR.txt
|   |   |-- licenseNLD.txt
|   |   |-- licenseNOR.txt
|   |   |-- licensePLK.txt
|   |   |-- licensePTB.txt
|   |   |-- licenseSVE.txt
|   |   |-- licenseTHA.txt
|   |   |-- licenseTRK.txt
|   |   `-- tvtablerev1.MSI
|   |-- Images
|   |   |-- a.jpg
|   |   |-- b.jpg
|   |   |-- c.jpg
|   |   |-- d.jpg
|   |   |-- e.jpg
|   |   |-- f.jpg
|   |   |-- g.jpg
|   |   |-- h.jpg
|   |   `-- i.jpg
|   |-- Microsoft.VC80.ATL.manifest
|   |-- Microsoft.VC80.CRT.manifest
|   |-- Microsoft.VC80.MFC.manifest
|   |-- Microsoft.VC80.MFCLOC.manifest
|   |-- Microsoft.VC80.OpenMP.manifest
|   |-- Packages
|   |   |-- Apps
|   |   |   |-- CCC
|   |   |   |   |-- Branding
|   |   |   |   |   |-- Branding.msi
|   |   |   |   |   `-- Branding.msi.old
|   |   |   |   |-- Core-Implementation
|   |   |   |   |   `-- ccc-core-implementation.msi
|   |   |   |   |-- Core-PreInstall
|   |   |   |   |   `-- ccc-core-preinstall.msi
|   |   |   |   |-- Core-Static
|   |   |   |   |   |-- 1028.mst
|   |   |   |   |   |-- 1029.mst
|   |   |   |   |   |-- 1030.mst
|   |   |   |   |   |-- 1031.mst
|   |   |   |   |   |-- 1032.mst
|   |   |   |   |   |-- 1033.mst
|   |   |   |   |   |-- 1034.mst
|   |   |   |   |   |-- 1035.mst
|   |   |   |   |   |-- 1036.mst
|   |   |   |   |   |-- 1038.mst
|   |   |   |   |   |-- 1040.mst
|   |   |   |   |   |-- 1041.mst
|   |   |   |   |   |-- 1042.mst
|   |   |   |   |   |-- 1043.mst
|   |   |   |   |   |-- 1044.mst
|   |   |   |   |   |-- 1045.mst
|   |   |   |   |   |-- 1046.mst
|   |   |   |   |   |-- 1049.mst
|   |   |   |   |   |-- 1053.mst
|   |   |   |   |   |-- 1054.mst
|   |   |   |   |   |-- 1055.mst
|   |   |   |   |   |-- 2052.mst
|   |   |   |   |   |-- 2070.mst
|   |   |   |   |   |-- 3084.mst
|   |   |   |   |   `-- ccc-core-static.msi
|   |   |   |   |-- Graphics-Full-Existing
|   |   |   |   |   `-- ccc-graphics-full-existing.msi
|   |   |   |   |-- Graphics-Full-New
|   |   |   |   |   `-- ccc-graphics-full-new.msi
|   |   |   |   |-- Graphics-Light
|   |   |   |   |   `-- ccc-graphics-Light.msi
|   |   |   |   |-- Graphics-Previews-Common
|   |   |   |   |   `-- ccc-graphics-previews-common.msi
|   |   |   |   |-- Graphics-Previews-Vista
|   |   |   |   |   `-- ccc-graphics-previews-vista.msi
|   |   |   |   |-- Help
|   |   |   |   |   |-- cs
|   |   |   |   |   |   |-- 1029.mst
|   |   |   |   |   |   |-- 1033.mst
|   |   |   |   |   |   `-- ccc-help-cs.msi
|   |   |   |   |   |-- da
|   |   |   |   |   |   `-- ccc-help-da.msi
|   |   |   |   |   |-- de
|   |   |   |   |   |   `-- ccc-help-de.msi
|   |   |   |   |   |-- el
|   |   |   |   |   |   `-- ccc-help-el.msi
|   |   |   |   |   |-- en-us
|   |   |   |   |   |   `-- ccc-help-en-US.msi
|   |   |   |   |   |-- es
|   |   |   |   |   |   `-- ccc-help-es.msi
|   |   |   |   |   |-- fi
|   |   |   |   |   |   `-- ccc-help-fi.msi
|   |   |   |   |   |-- fr
|   |   |   |   |   |   `-- ccc-help-fr.msi
|   |   |   |   |   |-- hu
|   |   |   |   |   |   `-- ccc-help-hu.msi
|   |   |   |   |   |-- it
|   |   |   |   |   |   `-- ccc-help-it.msi
|   |   |   |   |   |-- ja
|   |   |   |   |   |   `-- ccc-help-ja.msi
|   |   |   |   |   |-- ko
|   |   |   |   |   |   `-- ccc-help-ko.msi
|   |   |   |   |   |-- nl
|   |   |   |   |   |   `-- ccc-help-nl.msi
|   |   |   |   |   |-- no
|   |   |   |   |   |   `-- ccc-help-no.msi
|   |   |   |   |   |-- pl
|   |   |   |   |   |   `-- ccc-help-pl.msi
|   |   |   |   |   |-- pt-BR
|   |   |   |   |   |   `-- ccc-help-pt-BR.msi
|   |   |   |   |   |-- ru
|   |   |   |   |   |   `-- ccc-help-ru.msi
|   |   |   |   |   |-- sv
|   |   |   |   |   |   `-- ccc-help-sv.msi
|   |   |   |   |   |-- th
|   |   |   |   |   |   `-- ccc-help-th.msi
|   |   |   |   |   |-- tr
|   |   |   |   |   |   `-- ccc-help-tr.msi
|   |   |   |   |   |-- zh-CHS
|   |   |   |   |   |   `-- ccc-help-chs.msi
|   |   |   |   |   `-- zh-CHT
|   |   |   |   |       `-- ccc-help-cht.msi
|   |   |   |   |-- HydraVision-Full
|   |   |   |   |   `-- ccc-hv-full.msi
|   |   |   |   |-- Localization
|   |   |   |   |   `-- All
|   |   |   |   |       `-- ccc-all.msi
|   |   |   |   |-- MOM-InstallProxy
|   |   |   |   |   `-- ccc-mom-installproxy.msi
|   |   |   |   |-- Skins
|   |   |   |   |   `-- ccc-skins.msi
|   |   |   |   |-- Utility
|   |   |   |   |   `-- ccc-utility.msi
|   |   |   |   `-- Utility64
|   |   |   |       `-- ccc-utility64.msi
|   |   |   |-- CIM
|   |   |   |   |-- Win32
|   |   |   |   |   |-- 1028.mst
|   |   |   |   |   |-- 1029.mst
|   |   |   |   |   |-- 1030.mst
|   |   |   |   |   |-- 1031.mst
|   |   |   |   |   |-- 1032.mst
|   |   |   |   |   |-- 1033.mst
|   |   |   |   |   |-- 1034.mst
|   |   |   |   |   |-- 1035.mst
|   |   |   |   |   |-- 1036.mst
|   |   |   |   |   |-- 1040.mst
|   |   |   |   |   |-- 1041.mst
|   |   |   |   |   |-- 1042.mst
|   |   |   |   |   |-- 1043.mst
|   |   |   |   |   |-- 1044.mst
|   |   |   |   |   |-- 1046.mst
|   |   |   |   |   |-- 1049.mst
|   |   |   |   |   |-- 1053.mst
|   |   |   |   |   |-- 1054.mst
|   |   |   |   |   |-- 1055.mst
|   |   |   |   |   |-- 2052.mst
|   |   |   |   |   `-- ATICatalystInstallManager.msi
|   |   |   |   `-- Win64
|   |   |   |       |-- 1028.mst
|   |   |   |       |-- 1029.mst
|   |   |   |       |-- 1030.mst
|   |   |   |       |-- 1031.mst
|   |   |   |       |-- 1032.mst
|   |   |   |       |-- 1033.mst
|   |   |   |       |-- 1034.mst
|   |   |   |       |-- 1035.mst
|   |   |   |       |-- 1036.mst
|   |   |   |       |-- 1040.mst
|   |   |   |       |-- 1041.mst
|   |   |   |       |-- 1042.mst
|   |   |   |       |-- 1043.mst
|   |   |   |       |-- 1044.mst
|   |   |   |       |-- 1046.mst
|   |   |   |       |-- 1049.mst
|   |   |   |       |-- 1053.mst
|   |   |   |       |-- 1054.mst
|   |   |   |       |-- 1055.mst
|   |   |   |       |-- 2052.mst
|   |   |   |       `-- ATICatalystInstallManager.msi
|   |   |   |-- VC8RTx64
|   |   |   |   |-- vc864.msi
|   |   |   |   `-- vcredist_x64
|   |   |   |       |-- Microsoft.VC80.ATL.cat
|   |   |   |       |-- Microsoft.VC80.CRT.cat
|   |   |   |       |-- Microsoft.VC80.DebugCRT.cat
|   |   |   |       |-- Microsoft.VC80.DebugMFC.cat
|   |   |   |       |-- Microsoft.VC80.DebugOpenMP.cat
|   |   |   |       |-- Microsoft.VC80.MFC.cat
|   |   |   |       |-- Microsoft.VC80.MFCLOC.cat
|   |   |   |       |-- Microsoft.VC80.OpenMP.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.ATL.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.CRT.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.DebugCRT.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.DebugMFC.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.DebugOpenMP.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.MFC.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.MFCLOC.cat
|   |   |   |       |-- policy.8.00.Microsoft.VC80.OpenMP.cat
|   |   |   |       |-- vcredis1.cab
|   |   |   |       `-- vcredist.msi
|   |   |   `-- VC8RTx86
|   |   |       |-- vc832.msi
|   |   |       `-- vcredist_x86
|   |   |           |-- vcredis1.cab
|   |   |           `-- vcredist.msi
|   |   `-- Drivers
|   |       `-- Display
|   |           |-- LH6A_INF
|   |           |   |-- B_95503
|   |           |   |   |-- amdpcom32.dl_
|   |           |   |   |-- amdpcom64.dl_
|   |           |   |   |-- ati2edxx.dl_
|   |           |   |   |-- ati2erec.dl_
|   |           |   |   |-- ati2evxx.dl_
|   |           |   |   |-- ati2evxx.ex_
|   |           |   |   |-- atiadlxx.dl_
|   |           |   |   |-- atiadlxy.dl_
|   |           |   |   |-- atibrtmon.ex_
|   |           |   |   |-- aticalcl.dl_
|   |           |   |   |-- aticalcl64.dl_
|   |           |   |   |-- aticaldd.dl_
|   |           |   |   |-- aticaldd64.dl_
|   |           |   |   |-- aticalrt.dl_
|   |           |   |   |-- aticalrt64.dl_
|   |           |   |   |-- atidemgx.dll
|   |           |   |   |-- atidxx32.dl_
|   |           |   |   |-- atiedu64.dl_
|   |           |   |   |-- atiicdxx.da_
|   |           |   |   |-- atikmdag.sy_
|   |           |   |   |-- atimuixx.dl_
|   |           |   |   |-- atio6axx.dl_
|   |           |   |   |-- atiogl.xml
|   |           |   |   |-- atioglxx.dl_
|   |           |   |   |-- atipdl64.dl_
|   |           |   |   |-- atipdlxx.dl_
|   |           |   |   |-- atitmm64.dl_
|   |           |   |   |-- atiumd64.dl_
|   |           |   |   |-- atiumd6a.ca_
|   |           |   |   |-- atiumd6a.dl_
|   |           |   |   |-- atiumdag.dl_
|   |           |   |   |-- atiumdva.ca_
|   |           |   |   |-- atiumdva.dl_
|   |           |   |   `-- oemdspif.dl_
|   |           |   |-- CH_95951.cat
|   |           |   |-- CH_95951.inf
|   |           |   |-- CH_95951.msi
|   |           |   `-- atiiseag.ini
|   |           `-- LH_INF
|   |               |-- B_95503
|   |               |   |-- amdpcom32.dl_
|   |               |   |-- ati2edxx.dl_
|   |               |   |-- ati2erec.dl_
|   |               |   |-- ati2evxx.dl_
|   |               |   |-- ati2evxx.ex_
|   |               |   |-- atiadlxx.dl_
|   |               |   |-- atibrtmon.ex_
|   |               |   |-- aticalcl.dl_
|   |               |   |-- aticaldd.dl_
|   |               |   |-- aticalrt.dl_
|   |               |   |-- atidemgx.dll
|   |               |   |-- atiicdxx.da_
|   |               |   |-- atikmdag.sy_
|   |               |   |-- atimuixx.dl_
|   |               |   |-- atiogl.xml
|   |               |   |-- atioglxx.dl_
|   |               |   |-- atipdlxx.dl_
|   |               |   |-- atitmmxx.dl_
|   |               |   |-- atiumdag.dl_
|   |               |   |-- atiumdva.ca_
|   |               |   |-- atiumdva.dl_
|   |               |   `-- oemdspif.dl_
|   |               |-- CL_95951.cat
|   |               |-- CL_95951.inf
|   |               |-- CL_95951.msi
|   |               `-- atiiseag.ini
|   |-- Setup.exe
|   |-- Setup.exe.manifest
|   |-- mfc80u.dll
|   |-- msvcp80.dll
|   `-- msvcr80.dll
|-- ACPI
|   |-- Acpi
|   |   |-- AsAcpiIns.exe
|   |   |-- AsusSetup.exe
|   |   |-- AsusSetup.ini
|   |   |-- WIN2000
|   |   |   |-- 2000UNIN.EXE
|   |   |   |-- ATK2000.CAT
|   |   |   |-- ATK2000.INF
|   |   |   `-- asacpi.sys
|   |   |-- WINVISTA
|   |   |   |-- AsAcpi.inf
|   |   |   |-- AsAcpi.sys
|   |   |   `-- asacpi.cat
|   |   `-- install.ini
|   |-- Acpi64
|   |   |-- AsAcpiIns.exe
|   |   |-- AsusSetup.exe
|   |   |-- AsusSetup.ini
|   |   |-- WINVISTA
|   |   |   |-- AsAcpi.inf
|   |   |   |-- Asacpi.sys
|   |   |   `-- asacpi.cat
|   |   |-- install.ini
|   |   `-- win2000
|   |       |-- ATK2000.CAT
|   |       |-- ATK2000.INF
|   |       `-- Asacpi.sys
|   |-- AsusSetup.exe
|   `-- AsusSetup.ini
|-- drivers
|   `-- audio
|       `-- Realtek_HDA
|           `-- VISTA
|               `-- Jan07
|                   |-- ChCfg.exe
|                   |-- JACK.reg
|                   |-- MSHDQFE
|                   |   |-- Win2K3
|                   |   |   `-- us
|                   |   |       `-- kb888111srvrtm.exe
|                   |   `-- Win2K_XP
|                   |       `-- us
|                   |           |-- kb888111w2ksp4.exe
|                   |           |-- kb888111xpsp1.exe
|                   |           `-- kb888111xpsp2.exe
|                   |-- Readme.txt
|                   |-- RtlExUpd.dll
|                   |-- SetCDfmt.exe
|                   |-- Setup.exe
|                   |-- Vista
|                   |   |-- HDA.inf
|                   |   |-- HDA861A.inf
|                   |   |-- HDACPC.inf
|                   |   |-- HDAHP880.inf
|                   |   |-- HDAHPNB.inf
|                   |   |-- HDALC.inf
|                   |   |-- HDART32.cat
|                   |   |-- HDARt.inf
|                   |   |-- RTCOMDLL.dll
|                   |   |-- RTKVHDA.sys
|                   |   |-- RTSndMgr.cpl
|                   |   |-- RtHDVCpl.exe
|                   |   |-- RtkAPO.dll
|                   |   |-- RtkCoInst.dll
|                   |   |-- RtkPgExt.dll
|                   |   |-- RtlCPAPI.dll
|                   |   |-- RtlUpd.exe
|                   |   |-- SRSTSXT.dll
|                   |   |-- SRSWOW.dll
|                   |   `-- hda32.cat
|                   |-- WDM
|                   |   |-- ALSndMgr.cpl
|                   |   |-- AlcWzrd.exe
|                   |   |-- Alcmtr.exe
|                   |   |-- CPLUtl64.exe
|                   |   |-- HDA.inf
|                   |   |-- HDA01.inf
|                   |   |-- HDA104D.inf
|                   |   |-- HDA861A.inf
|                   |   |-- HDAApple.inf
|                   |   |-- HDACPC.inf
|                   |   |-- HDAHP880.inf
|                   |   |-- HDAHPNB.inf
|                   |   |-- HDALC.inf
|                   |   |-- HDARt.inf
|                   |   |-- HDX.INF
|                   |   |-- HDX01.INF
|                   |   |-- HDX104D.INF
|                   |   |-- HDX861A.INF
|                   |   |-- HDXApple.inf
|                   |   |-- HDXCPC.inf
|                   |   |-- HDXHP880.INF
|                   |   |-- HDXHPNB.INF
|                   |   |-- HDXLC.INF
|                   |   |-- HDXRT.INF
|                   |   |-- MicCal.exe
|                   |   |-- RTCOMDLL.dll
|                   |   |-- RTHDCPL.exe
|                   |   |-- RTKHDA64.sys
|                   |   |-- RTKHDAUD.sys
|                   |   |-- RTLCPL.exe
|                   |   |-- RTSndMgr.cpl
|                   |   |-- RtlCPAPI.dll
|                   |   |-- RtlUpd.exe
|                   |   |-- RtlUpd64.exe
|                   |   |-- SkyTel.exe
|                   |   |-- SoundMan.exe
|                   |   |-- hda32.cat
|                   |   `-- rtkhda64.cat
|                   |-- data1.cab
|                   |-- data1.hdr
|                   |-- data2.cab
|                   |-- engine32.cab
|                   |-- layout.bin
|                   |-- setup.ibt
|                   |-- setup.ini
|                   |-- setup.inx
|                   |-- setup.isn
|                   `-- setup.iss
`-- tree.txt

79 directories, 453 files</code></pre></div><p>The other drivers in the pack, for sound and power management, seem to be installed fine by DriverPacks.</p>]]></description>
			<author><![CDATA[null@example.com (cantab)]]></author>
			<pubDate>Tue, 26 Apr 2016 12:44:12 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58975#p58975</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58973#p58973</link>
			<description><![CDATA[<p>do you put the extracted drivers in the custom pack?</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Tue, 19 Apr 2016 05:51:43 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58973#p58973</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58970#p58970</link>
			<description><![CDATA[<p>I have an issue with SAD3 not installing a driver with a signature problem. It&#039;s the legacy AMD display driver for 32-bit Vista, I&#039;m installing it on 32-bit Windows 7. And it appears to be signed with an expired certificate.</p><p><a href="http://support.amd.com/en-us/download/desktop/legacy?product=Legacy1&amp;os=Windows%20Vista%20-%2032">http://support.amd.com/en-us/download/d … a%20-%2032</a></p><p>After running the .exe only far enough to let it extract the files, I can copy those files to the target PC and install the driver using Device Manager telling it to look in the folder in question, so I know it&#039;s a correct driver. But when I put them into a custom driverpack .7z SAD3 does not install them. I suspect this is due to the signature problem, though I don&#039;t know for certain.</p><p>Is there a way to make SAD install this driver?</p>]]></description>
			<author><![CDATA[null@example.com (cantab)]]></author>
			<pubDate>Mon, 04 Apr 2016 11:50:39 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58970#p58970</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58774#p58774</link>
			<description><![CDATA[<div class="quotebox"><cite>mizar11 wrote:</cite><blockquote><div class="quotebox"><cite>OverFlow wrote:</cite><blockquote><p>No. Just got distracted.&nbsp; <img src="http://forum.driverpacks.net/img/smilies/tongue.png" width="15" height="15" alt="tongue" /></p><p>DO NOT DO THIS ON OPTICAL MEDIA...<br />for thumb drive or better. All drivers extracted (M1 or M3)</p><p>create folder on the root of your thumb drive called &quot;OEM&quot;</p><div class="codebox"><pre><code>SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST &quot;%%i:%TAGFILE%&quot; SET THUMBDRIVE=%%i:&amp; GOTO DPsFound
:DPsFound

Start /wait /high /separate &quot;&quot; %THUMBDRIVE%\OEM\dp_install_tool.CMD


EXIT</code></pre></div><p>that should solve your issue.</p><p>= Since M1 (or M3) source is not deleted or extracted or copied it runs much faster (except on ODD devices) this solves two issues for you. The file copy / extraction and the removal of the D drive.</p></blockquote></div><p>Hi OverFlow,<br />Thanks for your time, hope you&#039;ll have patience with me... I&#039;m not sure to have clearly understood: I have to make a folder in my pen drive root directory, and put inside a new file called dp_install_tool.cmd containing instruction you wrote above. Is it correct? And what about the dp_install_tool.cmd existing in the sources\$OEM$\$1\D\SAD3 directory? Have I to delete it? And about setupcomplete.cmd file, in the sources\%OEM%\$$\Setup\scripts folder? What have I to do with these 2 files? I ask you that because I tried to keep everything original, just joining new dp_install_tool.cmd file in the root OEM folder, and install it from a pen drive on a virtual machine. But nothing happened... <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /> Hope you&#039;ll understand me, I know my english is very bad...<br />Thank you again for you kindness</p></blockquote></div><p>I like quote pyramids...</p><p>Move the dp_install tool folder FROM the sources\$OEM$\$1\ TO the root OEM folder. Like<br />ThumbDrive:\OEM\DriverPacks.here.please\D</p><p>Leave setupcomplete.cmd where it is and add the code above to it so...</p><p>{Win7-Disc source folder}\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd</p><p>contains</p><div class="codebox"><pre><code>REM echo off

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST &quot;%%i:%TAGFILE%&quot; SET THUMBDRIVE=%%i:&amp; GOTO DPsFound
:DPsFound
Start /wait /high /separate &quot;&quot; %THUMBDRIVE%\OEM\dp_install_tool.CMD /s

REM START %systemdrive%\D\SAD2\DP_Install_Tool.cmd /s

EXIT</code></pre></div><p>See how that goes...</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Thu, 10 Sep 2015 03:46:38 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58774#p58774</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58773#p58773</link>
			<description><![CDATA[<p>Still alone... <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /> <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /> <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /> I&#039;m not able to modify the script, I depend from you for everywhere...</p>]]></description>
			<author><![CDATA[null@example.com (mizar11)]]></author>
			<pubDate>Wed, 09 Sep 2015 19:27:03 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58773#p58773</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58757#p58757</link>
			<description><![CDATA[<div class="quotebox"><cite>OverFlow wrote:</cite><blockquote><p>No. Just got distracted.&nbsp; <img src="http://forum.driverpacks.net/img/smilies/tongue.png" width="15" height="15" alt="tongue" /></p><p>DO NOT DO THIS ON OPTICAL MEDIA...<br />for thumb drive or better. All drivers extracted (M1 or M3)</p><p>create folder on the root of your thumb drive called &quot;OEM&quot;</p><div class="codebox"><pre><code>SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST &quot;%%i:%TAGFILE%&quot; SET THUMBDRIVE=%%i:&amp; GOTO DPsFound
:DPsFound

Start /wait /high /separate &quot;&quot; %THUMBDRIVE%\OEM\dp_install_tool.CMD


EXIT</code></pre></div><p>that should solve your issue.</p><p>= Since M1 (or M3) source is not deleted or extracted or copied it runs much faster (except on ODD devices) this solves two issues for you. The file copy / extraction and the removal of the D drive.</p></blockquote></div><p>Hi OverFlow,<br />Thanks for your time, hope you&#039;ll have patience with me... I&#039;m not sure to have clearly understood: I have to make a folder in my pen drive root directory, and put inside a new file called dp_install_tool.cmd containing instruction you wrote above. Is it correct? And what about the dp_install_tool.cmd existing in the sources\$OEM$\$1\D\SAD3 directory? Have I to delete it? And about setupcomplete.cmd file, in the sources\%OEM%\$$\Setup\scripts folder? What have I to do with these 2 files? I ask you that because I tried to keep everything original, just joining new dp_install_tool.cmd file in the root OEM folder, and install it from a pen drive on a virtual machine. But nothing happened... <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /> Hope you&#039;ll understand me, I know my english is very bad...<br />Thank you again for you kindness</p>]]></description>
			<author><![CDATA[null@example.com (mizar11)]]></author>
			<pubDate>Sun, 30 Aug 2015 18:57:31 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58757#p58757</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58754#p58754</link>
			<description><![CDATA[<p>No. Just got distracted.&nbsp; <img src="http://forum.driverpacks.net/img/smilies/tongue.png" width="15" height="15" alt="tongue" /></p><p>DO NOT DO THIS ON OPTICAL MEDIA...<br />for thumb drive or better. All drivers extracted (M1 or M3)</p><p>create folder on the root of your thumb drive called &quot;OEM&quot;</p><div class="codebox"><pre><code>SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST &quot;%%i:%TAGFILE%&quot; SET THUMBDRIVE=%%i:&amp; GOTO DPsFound
:DPsFound

Start /wait /high /separate &quot;&quot; %THUMBDRIVE%\OEM\dp_install_tool.CMD


EXIT</code></pre></div><p>that should solve your issue.</p><p>= Since M1 (or M3) source is not deleted or extracted or copied it runs much faster (except on ODD devices) this solves two issues for you. The file copy / extraction and the removal of the D drive.</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Sat, 29 Aug 2015 01:15:41 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58754#p58754</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58753#p58753</link>
			<description><![CDATA[<p>Did you leave me alone? <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /></p>]]></description>
			<author><![CDATA[null@example.com (mizar11)]]></author>
			<pubDate>Fri, 28 Aug 2015 15:09:24 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58753#p58753</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58748#p58748</link>
			<description><![CDATA[<div class="quotebox"><cite>OverFlow wrote:</cite><blockquote><p>Welcome to DriverPacks.net. </p><p>Thank you for the kind words. I think you may have missed something that most of us either think is obvious, or at least well known. the way the tool works is; it sets a RunOnce registry command to delete the folder when the computer is next rebooted. If you haven&#039;t rebooted the computer before checking for the &quot;D&quot; folder. There is a very high probability that it WILL still be there... Since it is not supposed to be deleted until the First Reboot AFTER the tool runs. Again this is often missed or not known. Sometimes users overwrite or erase the RunOnce command by accident. The reason is simple it gets around any issues of files that may or may not still be in use <img src="http://forum.driverpacks.net/img/smilies/tongue.png" width="15" height="15" alt="tongue" />.</p><p>Please reboot the target machine before verifying whether or not that the cleanup is complete. </p><p>Report your results. Hope I guessed correctly.</p><p>PS please don&#039;t wait 6 months to ask, someone here prolly already knows the answer. <img src="http://forum.driverpacks.net/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /></p></blockquote></div><p>Hi OverFlow, thank you so much for your kind and quick reply. I follow your advice, I tried to make a fresh installation of win7 home premium x86 in a virtual machine on VMWare, but, after rebooting, that damn &quot;D&quot; folder was still there! <img src="http://forum.driverpacks.net/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /> I also noticed that, after finishing drivers installation, machine is very very slow, almost frozen, and replies to commands in a very slow way. When I reboot it, a message of &quot;waiting to close program&quot; appears, referrring to Windows host. After several seconds, system reboots, but &quot;D&quot; folder is still there at the logon.<br />Where&#039;s my mistake?<br />Thanks a lot, and, please, forgive my ignorance... <img src="http://forum.driverpacks.net/img/smilies/sad.png" width="15" height="15" alt="sad" /></p><p>Edit:<br />I tried to download again a fresh version of SAD3, because I was not sure of my old DP_Install_Tool.cmd. I again tried the same installation above, but... Nothing happened. After reboot, the &quot;D&quot; folder was still at her own place. Pleeeeeeease, help me...</p>]]></description>
			<author><![CDATA[null@example.com (mizar11)]]></author>
			<pubDate>Sun, 23 Aug 2015 08:36:03 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58748#p58748</guid>
		</item>
		<item>
			<title><![CDATA[Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=58747#p58747</link>
			<description><![CDATA[<p>Welcome to DriverPacks.net. </p><p>Thank you for the kind words. I think you may have missed something that most of us either think is obvious, or at least well known. the way the tool works is; it sets a RunOnce registry command to delete the folder when the computer is next rebooted. If you haven&#039;t rebooted the computer before checking for the &quot;D&quot; folder. There is a very high probability that it WILL still be there... Since it is not supposed to be deleted until the First Reboot AFTER the tool runs. Again this is often missed or not known. Sometimes users overwrite or erase the RunOnce command by accident. The reason is simple it gets around any issues of files that may or may not still be in use <img src="http://forum.driverpacks.net/img/smilies/tongue.png" width="15" height="15" alt="tongue" />.</p><p>Please reboot the target machine before verifying whether or not that the cleanup is complete. </p><p>Report your results. Hope I guessed correctly.</p><p>PS please don&#039;t wait 6 months to ask, someone here prolly already knows the answer. <img src="http://forum.driverpacks.net/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /></p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Sat, 22 Aug 2015 20:25:08 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=58747#p58747</guid>
		</item>
	</channel>
</rss>
