leen2

Member
  • Content count

    44
  • Joined

  • Last visited

Community Reputation

0 Neutral

About leen2

  • Rank
    Member

Profile Information

  • OS
    Windows 7 x64
  1. The original error you were getting was "0x80070002" = ERROR_FILE_NOT_FOUND. This is usually caused by a little known feature of DISM, that it is horribly case sensitive and treats C:\path... as different from c:\Path... even though Windows explorer and the command line see them as the same. Note, if copying and pasting text from a text editor, smart quotes are different characters than regular quotes, etc... and will generate the same error. So best advice is to locate the correct path in windows explorer and copy the entire path from the explorer bar as it is actually displayed. You can also copy it from the command line. This will copy the correct capitalization into the command. In the second post, error code "0x80070057" = "The parameter is incorrect", so something is incorrect in the command you are trying to execute.
  2. the correct value for ProcessorArchitecture for the x64 platform is "amd64". You should replace x64 with amd64 in your xml file and try again. e.g. the corrected line in your example would be: <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> Hope this helps.
  3. DISM is horribly case sensitive and requires that all path statements in its command line commands are entered exactly as they are displayed in windows. This is very Unix/Linux like and for example results in C:\temp and C:\TEMP being different locations to DISM even though to windows they are the same. I suggest that you copy and paste the full path to any driver files into the command to avoid case sensitivity issues. In addition, if you copy the path from Windows explorer to a text editor and need to add quotes to the command line you are editing, be careful that your text editor does not use smart quotes which will look the same as regular quotes on the command line but will also generate this error. The developer who wrote the code for DISM should be retrained on programming for Windows.
  4. In: <component name="Microsoft-Windows-Setup" processorArchitecture="x86".... you need to specify the OS version you want to install. e.g. <component name="Microsoft-Windows-Setup" processorArchitecture="x86".... <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Value>Windows Longhorn SERVERSTANDARD</Value> <Key>/IMAGE/NAME</Key> </MetaData> <Path>... path to install.wim file </Path> <Credentials> .... If needed to access source media on a file share <Domain> NT Domain </Domain> <Password> NT User Account </Password> <Username> NT User password </Username> </Credentials> </InstallFrom> <InstallToAvailablePartition>true</InstallToAvailablePartition> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> The names of the OS versions come from the catalogue files that ship with the OS. If you open the .wim file in Windows System Image Manager it will ask you to load the catalogue file for the OS you are building.
  5. I notice that you are using the 64-bit WAIK for a 64-bit image. I believe the 64-bit OS kernel requires signed drivers and will ignore any unsigned drivers. I would suggest obtaining the signed drivers from Dell for this and remove the /forceunsigned switch. I could be wrong, but it might help.
  6. Sorry for the delay in responding, I forgot to check back on this article: For Static DNS entries use the following: <component name="Microsoft-Windows-DNS-Client" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <DNSServerSearchOrder> <IpAddress wcm:action="add" wcm:keyValue="1">10.2.1.4</IpAddress> <IpAddress wcm:action="add" wcm:keyValue="2">10.2.1.5</IpAddress> </DNSServerSearchOrder> <Identifier>00-52-6C-93-04-75</Identifier> <EnableAdapterDomainNameRegistration>true</EnableAdapterDomainNameRegistration> <DisableDynamicUpdate>true</DisableDynamicUpdate> <DNSDomain>your.domain.name.com</DNSDomain> </Interface> </Interfaces> <DNSDomain>your.domain.name.com</DNSDomain> <UseDomainNameDevolution>true</UseDomainNameDevolution> </component> For static WINS entries use the following: <component name="Microsoft-Windows-NetBT" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <NameServerList> <IpAddress wcm:action="add" wcm:keyValue="1">10.2.1.6</IpAddress> <IpAddress wcm:action="add" wcm:keyValue="2">10.2.1.7</IpAddress> </NameServerList> <Identifier>00-52-6C-93-04-75</Identifier> <NetbiosOptions>1</NetbiosOptions> </Interface> </Interfaces> </component> For Static address set against a specific MAC address use: <component name="Microsoft-Windows-TCPIP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <Identifier>00-52-6C-93-04-75</Identifier> <Ipv4Settings> <DhcpEnabled>false</DhcpEnabled> <Metric>10</Metric> <RouterDiscoveryEnabled>false</RouterDiscoveryEnabled> </Ipv4Settings> <UnicastIpAddresses> <IpAddress wcm:action="add" wcm:keyValue="1">192.168.100.66/24</IpAddress> </UnicastIpAddresses> <Routes> <Route wcm:action="add"> <Identifier>1</Identifier> <Metric>10</Metric> <NextHopAddress>192.168.100.1</NextHopAddress> <Prefix>0.0.0.0/0</Prefix> </Route> </Routes> </Interface> </Interfaces> </component>
  7. DISM is horribly case sensitive and requires the full path to any driver file to be in the exact case as it appears on the system. I tend to use windows explorer to display the path in the address bar and then copy and paste it into the command to make sure the case matches. Also watch out for smart quotes if you paste this into a text editor to construct the command first, if the text editor formats the quotes, when you paste it back to the command line it looks correct but is actually different ASCII characters and DISM complains it can't find the file specified.
  8. Try the following: <component name="Microsoft-Windows-TCPIP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <Identifier>Local Area Connection</Identifier> <Ipv4Settings> <DhcpEnabled>false</DhcpEnabled> <Metric>10</Metric> <RouterDiscoveryEnabled>false</RouterDiscoveryEnabled> </Ipv4Settings> <UnicastIpAddresses> <IpAddress wcm:action="add" wcm:keyValue="1">192.168.100.66/24</IpAddress> </UnicastIpAddresses> <Routes> <Route wcm:action="add"> <Identifier>1</Identifier> <Metric>10</Metric> <NextHopAddress>192.168.100.1</NextHopAddress> <Prefix>0.0.0.0/0</Prefix> </Route> </Routes> </Interface> </Interfaces> </component> also we ude the MAC address of the network card for the identifier in the form of "00-52-6C-93-04-75" but it is supposed to work with the name of the connection however with multiple connectinos in a machine it easy to confuse which is which.
  9. Make sure you also add the appropriate language packs for any packages you add to WinPE. They are usually in a sub folder from where you added the packages from.
  10. The 0x0000007b stop code is for an "inaccessible Boot device", meaning that Windows does not have a driver loaded that it can use to access the local disk that it is being told to boot from. Normally during the boot process you would hit F6 when prompted to provide a driver, however I believe that the Recovery console can be run from the Windows install CD anyway, so not sure why you would even need this now anyway. But in any case this error is saying you don't have a driver for the disk.
  11. Tripredacus, thanks so much for the reply. I am using the .wim from the WAIK by using the copype.cmd. Below is the output: Updating path to include dism, oscdimg, imagex C:\Program Files\Windows AIK\Tools\PETools\ C:\Program Files\Windows AIK\Tools\PETools\..\x86 C:\Program Files\Windows AIK\Tools\PETools\..\x86\Servicing; C:\Program Files\Windows AIK\Tools\PETools>copype.cmd amd64 C:\winpe_amd64 =================================================== Creating Windows PE customization working directory C:\winpe_amd64 =================================================== 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\bcd C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\boot.sdi C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\bootfix.bin C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\efisys.bin C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\efisys_noprompt.bin C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\fonts\chs_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\fonts\cht_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\fonts\jpn_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\fonts\kor_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\fonts\wgl4_boot.ttf 11 File(s) copied C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\boot\bootx64.efi C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\microsoft\boot\bcd C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\microsoft\boot\fonts\chs_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\microsoft\boot\fonts\cht_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\microsoft\boot\fonts\jpn_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\microsoft\boot\fonts\kor_boot.ttf C:\Program Files\Windows AIK\Tools\PETools\amd64\EFI\microsoft\boot\fonts\wgl4_boot.ttf 7 File(s) copied 1 file(s) copied. Success Updating path to include peimg, cdimage, imagex C:\Program Files\Windows AIK\Tools\PETools\ C:\Program Files\Windows AIK\Tools\PETools\..\x86 Mount the image again using DISM and delete/rename the setup.exe file from inside the image. I Think it is in the windows\system32 folder, but it could be somewhere else. By default when PE loads it looks for the file and runs it automatically if it finds it. Of course if it runs it and you exit out of setup, WinPE reboots immediately and don't get the customized environment you thought you would.
  12. Seems like you all made a lot of progress on this. However when scanning through all the posts I failed to see any mention of the biggest problem with DISM here, so I am adding this note to assist those who don't know, or have not figured it out. Basically DISM is horribly case sensitive, particularly when it comes to file paths. As a result the paths "E:\drivers\driver.inf" and "E:\DRIVERS\DRIVER.INF and any variations of these are completely different to DISM, yet identical to windows. To fix the issue, I found I needed to copy and paste the actual paths in Windows explorer into the command line to get it to work. I also found that if I copied this to Notepad, and constucted the command line in Notepad first, then copied it to the command prompt it also worked. However you also have to be careful when doing this with smart quotes as some text editors convert quotes to smart quotes and this will also appear to be an invalid path to DISM. Hope this helps.
  13. This concept was originally was created by Citrix when they produced WinFrame as a way of handling multiple user sessions on the same machine as a way to handle keeping each user's temp location unique to each user. Microsoft added it to their OS subsequently as they added Windows Terminal Services to the OS, and this only happened when logging into a terminal services session. With the evolution of the OS in the Vista timeframe, Micrsooft added the ability for you to have multiple users logged into the OS console at the same time and switch between user sessions, to do that they used the same concept borrowed from the Windows Terminal Services side of the OS. It is just a mechanism to keep the temp variable locations unique and separate between users. The number used for the directory is actually the session ID number for the user session.
  14. Use the version that has SP2 already in it. You can download it from Microsoft.