iamtheky

Or maintain the data in an ini. The following autoitscript will facilitate building an ini of data for whichever file you choose. This seems like it would be easier than maintaining copies of entire files, especially if you are not importing the metadata and entering it yourself anyway. Just select a file, then add a Key (e.g. "Artist") , then add the data (e.g. "firstname lastname"). On subsequent runs if data already exists for the file selected it will display that data prior to the inputboxes. It will build the ini in the directory the script is ran from. #include<array.au3> $file = FileOpenDialog("Select File" , @ScriptDir , "ALL(*.*)" , 1) $aINI = inireadsection(@ScriptDir & "\metadata.ini" , $file) If @Error <> 1 Then _Arraydisplay ($aINI) $key = inputbox("Add Key" , "What type of data is this (one word)" , "Artist") If @Error = 1 Then Exit $input = inputbox("Add Data" , "Add the Data" , "FirstName LastName") iniwrite(@ScriptDir & "\metadata.ini" , $file , $key , $input)

I'll have to grab the drivers (they are no doubt a year or two old by now - and most likely were Dell repacks), but we certainly opened a couple of ATI drivers and used the standard DISM /recurse to drop them. So an alternative to Driver Magician may be grabbing an OEM driver if they still behave similarly.

http://www.theexperienceblog.com/2009/07/30/error-30-when-injecting-nvidia-driver-into-windows-7-image-using-dism/ this might be your issue, we had to unpack many of our drivers as well, though we just used 7z on the package rather than the expand command.

yeah it probably had nothing to do with the forums being jacked the past week. just as bphlpt couldnt see the attachment, most likely because it still wasnt there 9 hours after being posted, not because he is being dense. Just saying you could probably give folk a pass on any oddities you notice.

Here is an autoit solution. In my test: 1) The Folder list is a txt file named 'FolderList.txt' and is relative to the script 2) The Files are all in a folder named 'Files' (also relative to the script). The files can be scattered in sub folders beneath that folder. Upon execution it will create a folder named 'Folders', and beneath, for all files that contain one of the strings from the list in their name, it will create the folder using the name from the list and copy the file to that destination. RecFileListToArray UDF #include<RecFileListToArray.au3> #include<File.au3> Dim $FolderArr _FileReadToArray("Folderlist.txt" , $FolderArr) $FilesArr = _RecFileListToArray(@ScriptDir & "\Files" , "*" , 1 , 1) For $i = 1 to ubound($FilesArr) - 1 For $k = 1 to ubound($FolderArr) - 1 If stringinstr($FilesArr[$i] , $FolderArr[$k]) Then DirCreate (@ScriptDir & "\Folders\" & $FolderArr[$k]) FileCopy(@ScriptDir & "\Files\" & $FilesArr[$i] , @ScriptDir & "\Folders\" & $FolderArr[$k]) EndIf Next Next

if this happens to be a laptop with a touchpad try the latest synaptics driver. Fixed drift issues for me, and has additional selections to disable the touchpad when an external mouse is present.

I like Melba23's AutoIt implementation of the same name, http://www.autoitscript.com/forum/topic/108445-how-to-make-toast-new-version-13-feb-12/ We use it in our PE and pipe the imagex progress to it. Though I dont know if its real toast, nor if it is special.

So if you set as policy the behavior you want: Specify the Unattended Sleep Timeout (plugged in) , enabled, and set to 0. Does it still timeout?

group policy? If present, you can either undo the previous settings that are causing this, or if not set some policy and maybe that will persist.

Im reworking an AutoIt version of an integrity checker, this may give you the means to roll your own... #include <Crypt.au3> #include<RecFileListToArray.au3> #Include <File.au3> #Include <Array.au3> #include <WindowsConstants.au3> #Include <WinAPIEx.au3> _CreateHashFile() sleep (2000) _CheckHashFile() Func _CreateHashFile() $path = FileSelectFolder ("Select Directory" , "c:" , 2) $Farray = _RecFileListToArray ($path ,"*" , 1 , 1 , 1 , 2) Dim $HashArray[$Farray[0] + 1] Dim $ComboArray[$Farray[0] + 1] For $i = 1 to $Farray[0] $HashArray[$i] = _Crypt_HashFile($Farray[$i], $CALG_SHA1) Next For $n = 1 to $Farray[0] $ComboArray[$n] = $Farray[$n] & "||" & $HashArray[$n] Next $ComboArray[0] = $path _FileWriteFromArray (@ScriptDir & "\hashfile.txt" , $ComboArray , 0) EndFunc ;;;===============================CHECKING AN EXISTING FILE==================================== Func _CheckHashFile() $GUI = GUICreate("", @DesktopWidth, @DesktopHeight, 0, 0, $WS_POPUP, $WS_EX_LAYERED) GUISetBkColor(1, $GUI) _WINAPI_SETLAYEREDWINDOWATTRIBUTES($GUI, 1, 255) GUISetState(@SW_SHOW) Dim $ReadArray _FileReadToArray(@ScriptDir & "\hashfile.txt" , $ReadArray) $path = $ReadArray[1] _ArrayDelete($ReadArray , 0) $FArray = _RecFileListToArray ($path ,"*" , 1 , 1 , 1 , 2) Dim $HashArray[$Farray[0] + 1] Dim $ComboArray[$Farray[0] + 1] For $i = 1 to $Farray[0] $HashArray[$i] = _Crypt_HashFile($Farray[$i], $CALG_SHA1) Next For $n = 1 to $Farray[0] $ComboArray[$n] = $Farray[$n] & "||" & $HashArray[$n] Next $ComboArray[0] = $path ;~ ;FIND MISSING ELEMENTS For $S = 0 To UBound($ReadArray) - 1 _ARRAYSEARCH($ComboArray, $ReadArray[$S]) If @error = 6 Then GUISetBkColor(16711680, $GUI) ExitLoop EndIf Next For $K = UBound($ComboArray) - 1 To 0 Step -1 $FIND = _ARRAYFINDALL($ReadArray, $ComboArray[$K]) For $M = UBound($FIND) - 1 To 0 Step -1 _ARRAYDELETE($ReadArray, $FIND[$M]) Next Next $MISSINGARRAY = $READARRAY _ArrayDisplay($MissingArray , "Missing or Modified Files") If NOT IsArray ($missingArray) Then $flag = 0 ;FIND ADDED or Modified Elements _FileReadToArray(@ScriptDir & "\hashfile.txt" , $ReadArray) $path = $ReadArray[1] _ArrayDelete($ReadArray , 0) For $K = UBound($READARRAY) - 1 To 0 Step -1 $FIND = _ARRAYFINDALL($ComboARRAY, $READARRAY[$K]) For $M = UBound($FIND) - 1 To 0 Step -1 _ARRAYDELETE($ComboARRAY, $FIND[$M]) Next Next $ADDEDARRAY = $ComboARRAY _ArrayDisplay($AddedArray , "Added or Modified Files") If NOT IsArray ($AddedArray) And $flag = 0 Then msgbox(0, '' , "Directory contents are the same") _ArrayConcatenate($AddedArray , $MissingArray) _ArrayDisplay($AddedArray , "All Modifications") EndFunc

Im just curious now, far more than I have been helpful. we have seen our fair share of wim deployment issues and I like to be aware of potential new ones (and hopefully their solutions).

can you put an imagex /info in between your copy and apply? that might help determine if its an issue with actually accessing the wim (and if its contents are all present) or if its an issue with just applying the payload.

that is hella odd if WinPE can format and copy, but not unpack. and it is failing as soon as you kick off the /apply? can 7zip unpack the wim once staged, its not a path or access issue, or bad copy from media? We have seen issues with disks, but they are not revealed until the restart and windows is actually trying to start. Since everything else is just an unpack.

Have you added the SSD driver to the WinPE? As well as the install wim? mounting those and doing a line similar to: ...substituting the location of the disk driver for "DP_LAN_wnt6-x86_1001\x86\L" , naturally

whats the exact error? How are you staging the Wim on that SSD? and are you running imagex /apply out of a WinPE environment?