Chipset Pack... Sysprep... Windows PE... Conflicts.... Headache!

Sounds like a very similar install method to our SAD2 script here: http://forum.driverpacks.net/viewtopic.php?id=5336
Maybe you could contribute/post your code there so we could use it to improve our script also (unless yours is a "trade secret").

Your problem was reported with an earlier DriverPack Chipset but I thought we fixed that.  I myself don't have hardware that supports that dual-hybrid-video...yet.  (I'm building a wish-list for a system upgrade that will incorporate that hybrid graphics on z68 chipset).

If you could tell us which specific driver folders cause the problem (or better yet, the driver files themselves), then we can quickly isolate the problem and issue a fix.

BTW, WTH are you doing posting this on Christmas day!?  Go away and be with your family!

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

The folder is the Intel One in the Chipset Pack... The issue did occur whether or not on the Z68 chipset machine because I did a  PRESYSPREP image and captured and deployed with imagex to a Acer laptop (B940 Sandy Bridge) that just had an integrated Intel graphics chipset, not dual GPU.

The issue persisted in Boot.WIM actually on a third machine... ASUS laptop with Nvidia GTX 460M. The other Acer laptop with integrated graphics could boot the boot.wim WinPE with the intel chipset folder integrated just fine. I believe the same with the Z68... not 100%. FYI The ASUS had an HM55 chipset. The Acer had  a newer HM65.

That's as specific as I could get since I didn't want to try integrating each folder one at a time and deploy an image for each scienario... Don't have the time.

I've actually tried using SAD2 (props to the complex script... can't wait till we have a new NT 6 compatible BASE...), but am not 100% sure what it accomplishes or the specific scenarios it is useful for... DPInst has to be executed manually (script).. and then what? Automatic scanning of all devices? This has to happen upon first login? It'll delete all drivers after completed if KTD not activated? A bit too complicated for me since, at the time, I didn't have as much experience with scripting or coding in general. An explanation would be appreciated.

Nothing special about the scripts I used... Here are the relevant parts:

Tasks.bat is run by FirstStart.vbs. This is to avoid seeing the black cmd window upon first login. FirstStart.vbs is placed in Startup folder of the default profile so it runs everytime a new user first logins and the Tasks.bat is placed one directory up from that to avoid automatic running in the Startup folder. It won't work if either are hidden (tried for purposes of hiding my "revolutionary" scripts).

The vbs actually started off as the one on the IT Bros site that organizes Taskbar Icons on first startup since Windows 7 does not save the configuration through Sysprep, but I have found that the icons and their orientation are kept in tact if you copy the entire folder of the User you customized to the Default profile, manually. I cut that part of the script out ever since that discovery was made. I used to use Windows Enabler to enable the Copy To button under Advanced System Settings -> User Profile -> Settings to copy the customized User to Default user, but manually copying the folder in Explorer copied ALL the files (including taskbar icon orientation) and the sizes of the profiles came out exactly the same.

In fact, most of these techniques/code was just found googling around and modified slightly for my purposes, so I can't take too much credit.

Tasks also does some other stuff like moves Chrome cache to a RAMDisk and creates a junction for that purpose.

Both scripts delete themselves after running, but are still stored in the Default user profile of course so that when a new user is created, they execute upon first login.

FirstStart.vbs

Option Explicit

'Run Batch Script

Dim sBatFile
Dim oShell
Dim oFSO
Dim sBatFileShort
Dim objNetwork

Set oShell = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")
Set objNetwork = CreateObject("WScript.Network")

sBatFile = "C:\Users\" & objNetwork.UserName & "\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Tasks.bat"

' just in case there is spaces in the path
sBatFileShort = oFSO.GetFile(sBatFile).ShortPath

' Run the batch file hidden, and let the VBScript wait for the batch file to finish
oShell.Run sBatFileShort, 0, True

'Delete the script
DeleteSelf

Sub DeleteSelf()       
        Dim objFSO
        'Create a File System Object
        Set objFSO = CreateObject("Scripting.FileSystemObject")
        'Delete the currently executing script
        objFSO.DeleteFile WScript.ScriptFullName
        Set objFSO = Nothing
End Sub

Tasks.bat

@ECHO OFF

xcopy /yqei "C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default" "R:\Program Files\Chrome\%USERNAME%\Default Profile" > NUL

:stillcopying

tasklist /fi "imagename eq xcopy.exe" | find /i "xcopy.exe" > NUL

if /i not %ERRORLEVEL%==0 (
goto donecopying
)

ping 127.0.0.1 -n 4 > NUL
GOTO stillcopying

:donecopying

rd /s /q "C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default"
ping 127.0.0.1 -n 4 > NUL
mklink /j "C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default" "R:\Program Files\Chrome\%USERNAME%\Default Profile" > NUL

rd /s /q "C:\Windows\inf\x64"

del %0

Last edited by rootMBX (2013-12-20 12:29:47)

Well that's disappointing!
When you get it up and running, can you post your entire HWID list?

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!