• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jazkal

Contact Methods

  • Website URL
  1. I have tried Win7 Enterprise, Windows 2008 R2, and Windows 2012. Run the /log does not give any additional info. Can anyone else verify the new RTM ISO's are causing them problems? Or verify that you were able to extract all the files from the ISO? I do not have this problem with any of the other ISO's I've gotten from Microsoft in the past.
  2. E: is the Source ISO D: is the destination, and I verified that it is NTFS Here is the output from the Robocopy try: C:\>robocopy.exe E:\ D:\DVD\ /MIR /ETA------------------------------------------------------------------------------- ROBOCOPY :: Robust File Copy for Windows------------------------------------------------------------------------------- Started : Fri Oct 18 11:06:56 2013 Source = E:\ Dest : D:\DVD\ Files : *.* Options : *.* /S /E /COPY:DAT /PURGE /MIR /ETA /R:1000000 /W:30------------------------------------------------------------------------------ 4 E:\ 6 E:\boot\ 1 E:\boot\en-us\ 16 E:\boot\fonts\ 1 E:\boot\resources\ 0 E:\efi\ 1 E:\efi\boot\ 0 E:\efi\microsoft\ 6 E:\efi\microsoft\boot\ 16 E:\efi\microsoft\boot\fonts\ 1 E:\efi\microsoft\boot\resources\ 0% New File 18272 bootres.dll2013/10/18 11:06:56 ERROR 1 (0x00000001) Copying File E:\efi\microsoft\boot\resources\bootres.dllIncorrect function.
  3. Starting with a brand new ISO: Windows Server 2012 R2 RTM Datacenter/Standard ISO My default ISO tool is 7Zip, easy, simple, my standard default app. But it doesn't read UTF. I see the following when I open it: [bOOT] - Folder README.TXT - File The readme says: "This disc contains a "UDF" file system and requires an operating system that supports the ISO-13346 "UDF" file system specification." So we tried a native 2012 install to mount the ISO. But that could see the files, but not copy them all. Then I tried Virtual CloneDrive. This way I can mount the ISO under Win7. Here is where I get different errors based on the tools used. 'E:' drive is the ISO mounted through Virtual CloneDrive 'D:' drive is a NTFS partition First command to test directory creation. xcopy E:\* D:\DVD\* /E /V /F /G /H /Y /T creates all 871 directories (correct amount) Second command to copy the files. xcopy E:\* D:\DVD\* /E /V /F /G /H /Y Gets down to this file: E:\efi\microsoft\boot\resources\bootres.dll Error: The target volume does not support symbolic links Add the option /B - "Copies the Symbolic Link itself versus the target of the link." xcopy E:\* D:\DVD\* /E /V /F /G /H /Y /B Gets down to this file: E:\efi\microsoft\boot\resources\bootres.dll Error: The target volume does not support symbolic links Add the option /J - "Copies using unbuffered I/O. Recommended for very large files." xcopy E:\* D:\DVD\* /E /V /F /G /H /Y /J Gets down to this file: E:\efi\microsoft\boot\resources\bootres.dll Error: The target volume does not support symbolic links Next tool to test was TeraCopy Running a copy of everything in the ISO, minus the 'sources' folder, yields 145 files and 18 folders copied to D:\DVD\, and the mounted ISO has 160 files and 18 folders. Tracking down these files gives this list: 1 - e:\efi\microsoft\boot\resources\bootres.dll 2 - e:\support\adfs\en-us\migrate-federationconfiguration.psd1 3 - e:\support\adprep\en-us\adprep.dll.mui 4 - e:\support\adprep\en-us\csvde.dll.mui 5 - e:\support\adprep\en-us\ldifde.dll.mui 6 - e:\support\logging\en-us\actionqueueetw.dll.mui 7 - e:\support\logging\en-us\auditetw.dll.mui 8 - e:\support\logging\en-us\cmisetupetw.dll.mui 9 - e:\support\logging\en-us\oobeldretw.dll.mui 10 - e:\support\logging\en-us\setupcletw.dll.mui 11 - e:\support\logging\en-us\setupetw.dll.mui 12 - e:\support\logging\en-us\setupugcetw.dll.mui 13 - e:\support\logging\en-us\sysprepetw.dll.mui 14 - e:\support\logging\en-us\windeployetw.dll.mui 15 - e:\support\logging\en-us\winsetupetw.dll.mui xcopy E:\Sources\* D:\DVD\Sources\* /E /V /F /G /H /Y Gets down to this file: E:\Sources\dlmanifests\microsoft-windows-storagemigration\en-us\stormigplugin.dll.mui Error: The target volume does not support symbolic links Then tried using TeraCopy and got lots of errors on multiple .mui and .dll files Error: Read Error: Incorrect function. Does anyone have any other ideas for extracting these files cleanly?
  4. Thanks for the link. However, I don't see a portable version to download.
  5. I am trying to add the ability to mount an ISO file from inside WinPE. Anyone tried this before?
  6. Wow, that's an old thread. ;-) What is your WinPE platform (version?) What have you tried so far?
  7. Thankfully I don't have to worry about logging into our proxy, so maybe I'll have better luck with it. I'll update here with my results.
  8. Great work! I will try and duplicate it in my system sometime next week. This is a life saver.
  9. Anyone know how to enable proxy in WinPE 3.x? I've tried to run through the same steps that I have to do under Win2k8 R2, but netsh.exe under WinPE is a different version that doesn't support winhttp settings. Anyone else had to deal with proxy under WinPE?
  10. No, not sure how to do that on something like this. I was going to try and repackage the vmware tools, yank out what I see as the driver related stuff, and then try and create a winpe plugin for what was left. "C:\Program Files\VMware\VMware VIX\vmrun.exe" listProcessesInGuest "E:\VMWARE\Win2k8_SP2_Standard\Windows Server 2008 (experimental).vmx" net localgroup administrators SYSTEM /add net user SYSTEM $trongPassword 'The user name could not be found.'
  11. Yes, but I have spent hours looking over google results, and haven't found anything useful. I have no idea what "VM Additionals" is.
  12. We have our Image creation application that runs on WinPE. We want to automate the selection of options (command line options will work), so that we can create and capture the images. I have everything working for when the OS is actually installed in the virtual machine, but the first steps in WinPE aren't looking to good.
  13. Yes, I am trying to automate some system builds inside of VMWare, and WinPE is the first stage. I have verified that the firewall is off. ( I know this because I can VNC to the system when the firewall is off, but not when it is on) The error I get is: Error: The VMware Tools are not running in the virtual machine: E:\VMWARE\Win2k8_SP2_Standard\Windows Server 2008 (experimental).vmx I may have a second problem, as the vmrun command requires the username and password of the admin account so that it has the correct rights to run files, etc. However, WinPE doesn't have a real user account, is shows as "SYSTEM" and I can't change the password.
  14. I've got all the vmware tool drivers integrated and working in WinPE(Win7/Win2k8R2). However, I can not get vmrun.exe to connect to the WinPE once it is loaded in VMWare Workstation. Anyone got this working? Or know what piece of VMWare Tools I need to work on?