Tripredacus

I've since stopped writing a diary about my computers, but felt like I should mention... Uncle Socks brought back to life.

It appears that via Server 2012 that that particular system did in-fact boot via UEFIx64 method and booted to my WinPE 4.0 x64 boot image. Relevent logs: The following client booted from PXE: Hardware Address: 00-24-25-0E-15-53 IP: 10.12.41.42 Device ID: {00000000-0000-0000-0000-0024250E1553} ClientArchitecture: 4 Prestaged: false ------ The Following Client completed TFTP Download: Client IP: 10.12.41.42 Filename: \Boot\x64\bootmgfw.efi File Size: 1354480 Client Port: 8334 Server Port: 53942 Variable Window: false ------ The Following Client started TFTP Download: Client IP: 10.12.41.42 Filename: \Tmp\x64uefi{1061C2D4-44E6-4B02-AFA7-C73189EE9239}.bcd File Size: 12288 Client Port: 8352 Server Port: 53942 Variable Window: false BUT, still unable to image Windows 7 (did not try Windows 8, don't have the time with the hardware) since BCDBoot cannot write the boot files.

I do not use any of those tools, so I couldn't recommend any. What is giving the BSOD? Is it on installation, or during injection? What is the error?

Disk numbering in WinPE is determined on the speed it takes to enumerated the detected disks. I have done a ton of testing in the past using Spindle disks, SSDs and card readers. On certain systems, the numbering can change between a HDD and a card reader on multiple boots. Plus, how the devices are connected physically (board-level) seems to have an effect on disk numbering. Disks connected via the PCI or SATA bus typically enumerate faster than those connected via the USB bus. But this isn't always the case. When it comes to installing an OS onto a system with a data disk, I always unplug that drive for instalation just because I don't trust Windows to install on the correct disk, whether or not I am using an answer file.

Link removed! Warez found in download! Winterstorm if you want to bring RT here from the old forum you'll need to abide by our forum rules, including: Files in question: - imagex.exe - oscdimg.exe In order to provide users a shortcut to downloading the WAIK or ADK, you should refer them to JFX's tool: No further warnings will be given.

You would want to find which folder has the driver for your hardware. You can search file contents of the INFs for the Hardware ID you need to have support for.

Can you get into Safe Mode?

PuntoMX and I are tied in the birthday battle... until now... Happy Birthday PuntoMX!

It certainly is. And the worst part is there is no setting you can use to pick the "Check for updates but let me choose whether to download and install them" setting. What had the permission before? Was it TrustedInstaller?

Previously mentioned "SMSC LAN9500 USB 2.0 to Ethernet 10/100 NIC" has been found capable of doing a UEFI PXE boot! BUT there is a problem. Server 2008 R2 gets the arch value from the NIC and reports it as 7. Now it is already known that Server 2008 R2 does NOT support UEFI PXE boot, but seems to understand what to do with Arch 7. So it ends up serving out the Itanium EFI boot option (bootmgfw.efi) to the NIC. While this appears to work, the PE is loaded with the Itanium EFI rom and the actual hardware is using UEFI. The expected result (as with BIOS based PXE boot to UEFI/GPT systems) is that BCDBoot is unable to write to the BCD Store. Interestingly enough, if you disable the UEFI Boot option in the BIOS, it automatically will disable the onboard NIC and boot ROM. It does not appear that this system is capable of doing a BIOS level PXE boot. Even if you enable the LAN Option ROM, the other networking related pages in the BIOS are unavailable (grayed out) and it won't even attempt to boot from LAN even if you set LAN as the first boot item and disable everything else. This NIC is included in the CZC U116T Ultrabook. Unfortunately, this product is out the door, so while I have built a new system with Server 2012, I won't be able to test this functionality until another one comes in or something else shows up that can do a UEFI PXE boot.

Are you in Audit Mode? You can tell by going to the Desktop and you will see the Sysprep box on the screen.

Intel Desktop boards DH77KC and DH77DF have new BIOS version 0100 that adds BGRT support. Note from the PDF they speak of an error you get using the ITK 5: http://downloadmirror.intel.com/21846/eng/KC_0100_ReleaseNotes3.pdf

I'm getting "Bing points" every time I click on that link.

Well you can definately use it for onsie-twosies... plus then you'd already have the ability to scale up your operation in the future.

Have you looked into using MDT and a deployment share? http://technet.microsoft.com/en-us/solutionaccelerators/dd407791.aspx

I can't really find any pay products, but these 2 IBM apps: IBM version of EZ-Smart http://www.techrepublic.com/article/get-smart-to-predict-hard-drive-failures/1055303 IBM Feature/Align Tool: http://download.chip.eu/en/IBM_Hitachi-Feature-Tool_1573833.html http://www.hgst.com/support/downloads/#FeatureTool But those aren't for files. Maybe something on the UBCD, which has a lot of hard disk related programs included: http://www.ultimatebootcd.com/

It picks from the 3 Update options in OOBE. I can't find a good picture of it, but it is equivalent to "Install Updates Automatically (Recommended)" option in the "Choose how Windows can install updates" page in Control Panel.

Are you using one of the pre-built solutions as listed here: Or are you using your own method?

When Test Mode is on, does it say "Test" above "Windows 8" and the build number on the desktop if the OS is not activated?

I can't wait to use the hottest selling OS of 2013 to do my taxes from 2011!

UEFI PXE driver found for SMSC LAN9500 USB 2.0 to Ethernet 10/100 NIC. http://www.smsc.com/index.php?tid=145&pid=137&cid=&tab=5 NIC is used in the dock for the CZC U116T Ultrabook/Tablet: http://www.czctech.com/en/t3c/U116T.html SMSC requires registration to download. Have not tested this device to see if it is capable of doing a UEFI PXE boot or not. Update: The UEFI PXE "driver" as the website mentions is actually a .EFI file to be used to flash the EEPROM on the NIC itself. It can be done via the EFI Shell (if present) or presumably a utility. It contains 32/64bit Itanium and 32/64bit UEFI types. UEFI PXE code added to BIOS version 0089 for Intel DH77EB motherboard: http://downloadmirror.intel.com/21749/eng/EB_0089_ReleaseNotes.pdf see also: Update: Intel (apparently) added UEFI PXE support to the DH77KC and DH77DF boards in BIOS version 0100. http://downloadmirror.intel.com/21846/eng/KC_0100_ReleaseNotes3.pdf

This project is dead and left open for historical reference only. The current project is here: http://www.msfn.org/board/index.php?showtopic=138048

If this disk was originally formatted on another computer (or possibly user) then you will get messages about it. It is because you are not the owner of that disk as far as Windows is concerned.

Welcome to the MSFN!