cdob

Shure of course, there will be a solution. Contrary it took several years to appear a ISO file windows driver. Grub development rejeted El-Torito loopback in the past. http://lists.gnu.org/archive/html/help-grub/2013-11/msg00013.html http://lists.gnu.org/archive/html/help-grub/2013-11/msg00017.html https://lists.gnu.org/mailman/listinfo/grub-devel Current linux distributions ueses hybrid ISO mode: a fake MBR partition refers to the CD. It's possible to ISO hybrid the El Torito image. Asks the manufacturer to do this. Actually, yes from a hex editor initially. Didn't you extracted the image in between? bootx64.efi is the acronis efi loader. And reads the configuration file bootx64.xml. Can you open the file bootx64.xml? Read the file and convert to grub requirement. This is another approach, complelwete different to the mentioned one. Another manufacturer uses a previous existing name. It's readable from the boot drive directly. If you use single files, you may boot the Acronis boot.wim from from the boot media.

Yes, it's possible to 'set root=loop' and 'chainloader /efi/boot/bootx64.efi' This works: grub loads bootx64.efi. However bootx64.efi dosn't detect the loopback device, there is no support. The booting is truncated. Acronis Linux fails. And WinPE fails too: \boot\bcd is not found A UEFI wimboot may work in future http://forum.ipxe.org/showthread.php?tid=7261 Thanks for the awesome batch. Nice to know: present a idea, relax and wait for a appropiate solution. I call this teamwork. Good work. Yes, that would be fine. Neither Linux nor PE supports the loopback device. As for today, I dare to say: there is no ISO file PE UEFI way. Well, last ressort, follow the manufacturer approach: burn the ISO file to a real CD. And use a hex editor to extract the boot images in doubt. There is no GUI solution supporting all cases.

Isoinfo list first boot image only: this is the Acronis BIOS boot image. The UEFI image is not listed. And the files at CD file system are not the boot ones. Read the license models again: http://www.isobuster.com/license-models.php The FREE version supports the requested task, there is no need for another version.

Its possible that actual LBA numbers may vary depending on Acronis release Of course the LBA numbers differes at different ISO images, hence the "adjust LBA numbers yourself"

This combination can emulate a virtual CD drive and boot the El Torito routine. This works, as long following boot routines uses BIOS routines too. There is no similiar approach, no virtual CD drive. There is no El Torito boot routine: hence booting from a ISO file is impossible so far. Yes, there are work arounds, e.g. loopback the ISO at grub2 and read files from the loopback drive. This works up to a certain leveal and may fail at other. The example was posted at section "Boot Linux and other OS flavours". Maybe this relate to a Linux based Acronis, not to a WinPE-based. I don't know a UEFI ISO file WinPE soluiton.

Which old hardware do you use? Which Gigabyte H81 do you use? Which mass storage drivers are active currently?

@zamarac Yes, this would be the next USB boot steps. Both may work or fail. But remember, one small step after another. Sorry, I won't discuss Acronis at this thread, it's about windows booting.

The Dell BIOS offeres RAID or IDE, no AHCI. http://en.community.dell.com/support-forums/desktop/f/3514/t/19449394.aspx Most likley the old machine used IDE mode. Transfer a windows from IDE to IDE is pretty normal behaviour, nothing courious about this. If you like to enable AHCI http://support.microsoft.com/kb/922976

Any x64 ISO supports UEFI boot. Remember: this is about basic testing still: does machine works at Windows 7 UEFI? I expect: boot.wim is loaded to RAM and PE is processed: either hangs next: vga.sys can't connect to VGA bios. Then ignore UEFI Windows 7 at this machine. or does boot and Shift F10 is possible: UEFI Windows 7 is possible Yes, this was another idea. Be aware, windows 7 doesn't support USB booting. There are different approaches to circumvent this: different machines requires different solutions. Basic testing: clone the Thinkpad HDD. Boot from USB HDD at Thinkpad. A BSOD 0x7b is a good sign so far. Connect the USB HDD to the Toshiba. Turn on the machine, press the boot select hotkey. Do you get a USB HDD twice? One should refer to BIOS mode and antoher to UEFI mode. Select the non UEFI mode. Again a BSOD 0x7b would be a good sign so far.

Did you removed the internal hard disk? If you remove the 8GB SD-Karte: are there two or three disk involved?BIOS hard disk order is importand. Boot grub4dos, press C and run geometry (hd0)geometry (hd1) geometry (hd2)Post the output.At setup boot there are drive letters assigned: does C: refers to Target USB3 16GB? does C: refers to source disk?

There is a different \boot\bcd used. Verify the native \boot\bcd after upgrade again. No, no certain requriements. Diffeent partitions are possible. Yes, a expandable VHD will fail given low space at hard disk. Native VHD Boot: A Walkthrough of Common Scenarios http://download.microsoft.com/download/A/8/4/A847B017-B2CC-40E0-895A-266D88A43C99/Native-VHD-Boot-A-Walkthrough-of-Common-Scenarios.doc It's shown a BSOD 0x136. You may disable VirtualDiskExpandOnMount. Which VHD file size, and VHD disk size do you use? Which free space is at real hard disk? As jaclaz pointed already: make slow steps. The true reason is not resolved so far. Do you remember the question about real DVD Windows 7 UEFI booting? Next setp: build a new VHD (fixed size) file and apply install.wim. Given hardare / software request is unlear in detail. Nobody can provide a guaranteed working solution. It may be possible to resolve the request later, if some small lessons learned.

There are some vitual hardware, especial the graphic card including the VGA BIOS. Native booting uses native graphic card including the VGA BIOS or firmare. What about the real DVD Windows 7 UEFI booting?

Windows 7 UEFI/ GPT will work, given legacy BIOS Interrupt 10 (INT 10H) video transitioning at UEFI mode. Windows 7 UEFI/ GPT will not work, given a GOP = Graphics Output Protocol at UEFI mode. It will fail at a GOP only hardware. CSM Mode booting is not possible from GPT out of the box. Ignore this approach at a given hardware and software. Use a hardware solution: additional (USB) hard disk.

Good catch Windows 7 Setup hangs at "Starting Windows" on Surface Pro http://support.microsoft.com/kb/2828074/en-us I understand: the Dell option "Load Legacy Option ROM" enables legacy BIOS Interrupt 10 (INT 10H) video transitioning at UEFI mode.

Try a real DVD. Yes, should work at CSM mode, remember Do you have a fast USB drive? Best a SSD? Some UEFI firmware offers to select the boot drive, e.g. press F12 at the Thinkpad. I don't kown a way to proper "migrate" the applications and data.

Yes, it's confusing. Which part number do yo use? Break, do not flash the firmware so far. Go back to basic testings: Can you boot a Windows 7 DVD at BIOS mode? Can you press shift F10? Can you boot a Windows 7 DVD at UEFI mode? Can you press shift F10?

The best way: do not do this. There is no best way. The issue relates not to Disk2VHD, most likely there is another reason. P55T-B5235: http://support.toshiba.com/support/modelHome?freeText=1200008303 P55t-A5202 http://support.toshiba.com/support/modelHome?freeText=1200005514 I assume the P55T-B5235 uses GOP too. Which firmware version do you use? Yes, there can be another name. Or there is no option at all. As for apply the windows 7 intall.wim: You qouted already http://www.msfn.org/board/topic/129475-boot-windows-7-from-vhd-an-amazing-concept/page-5#entry1083966

Name the true model, not the family. Which one T6x/X6x do you use? Which one P55T do you use? Did you disable GOP at firmware at the unknown P55T? VHD layout is appropiate. Enable boot logging http://www.msfn.org/board/topic/162071-w2k12-show-os-boot-information/ Post ntbtlog.txt up to HdAudio.sys. No, VHD can be MBR or GPT nontheless. UEFI booting to a VHD GPT is possible. And UEFI booting to a VHD MBR is possible. What about apply Windows 7 install.wim to the VHD? Do you have a spare hard disk? Swap the Toshiba hdd and install Windows 7. Documentation list a friendly approach. Ignore the documentation.

Which hardware do you use? BIOS, firmware, driver relates to this. A basic driver is not resporting success to the kernel. Of course antoher driver, not the mentioned ony. Can be the driver itself (a OS default driver or a third party driver), BIOS, firmware, hardware. This would result antother error: BSOD 0x7b. No it's not the current issue. Does other users use Windows 7 at relating hardware? As for testing: mount the VHD format the partition apply a default windows 7 install.wim to this partition. unmount the VHD. Boot to the VHD. If it's boots, blame a third party driver at the other VHD. By the way: the VHD can be MBR or GPT style, both works from winload.efi.

Good catch, refers to a P5WD2 http://www.asus.com/Motherboards/P5WD2/HelpDesk_Download/ This refers to e1000325.inf. Last chance: Install the P5WD2 again. And copy and paste file e1000325.sys from Version 18.3, it's from 2008.

Can you check the HardwareID again? Which ID goes to the second device?It's a sever motherboard, Intel dosn't offers XP LAN drivers always. Try patching drivers at own risk. http://www.intel.com/support/network/sb/cs-006120.htm http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18717 File name: PRO2K3XP_32.exe Version: 18.3 (Latest) Date: 05/15/2013 Yes, no HardwareID 'PCI\VEN_8086&DEV_1081' PRO2K3XP_32\PRO1000\Win32\NDIS5x\e1000325.inf %E108ASA.DeviceDesc% = E108A.ndi, PCI\VEN_8086&DEV_108A E108ASA.DeviceDesc = "Intel® PRO/1000 P Dual Port Server Adapter" PRO2K3XP_32\PRO1000\Win32\NDIS5x\e1e5132.inf %E108BEC.DeviceDesc% = E108B.ndi.5.1, PCI\VEN_8086&DEV_108B %E108BEC.DeviceDesc% = E108B.ndi.5.1, PCI\VEN_8086&DEV_108C %E1096NC.DeviceDesc% = E1096.ndi.5.1, PCI\VEN_8086&DEV_1096 %E1098BC.DeviceDesc% = E1098.ndi.5.1, PCI\VEN_8086&DEV_1098 E108BEC.DeviceDesc = "Intel® PRO/1000 PM Network Connection" E1096NC.DeviceDesc = "Intel® PRO/1000 EB Network Connection with I/O Acceleration" E1098BC.DeviceDesc = "Intel® PRO/1000 EB Backplane Connection with I/O Acceleration" Guessed, edit: PRO2K3XP_32\PRO1000\Win32\NDIS5x\e1e5132.inf [Intel.NTx86.5.1]%E108BEC.DeviceDesc% = E108B.ndi.5.1, PCI\VEN_8086&DEV_1081or try [Intel.NTx86.5.1]%E1096NC.DeviceDesc% = E1096.ndi.5.1, PCI\VEN_8086&DEV_1081

copy boot files to c: or r: http://technet.microsoft.com/library/gg577238.aspx Either bcdboot c:\windows /s r:Or bcdboot c:\windows /s c:

@Dave-H Swithcing from a Intel Xeon Dual CPU to a Intel Xeon Dual CPU, and equal chipset manufacturer. Yes, matching hardware. Should be both ACPI mulitprocessor HAL: halmacpi.dll http://support.microsoft.com/kb/309283/ Which hal do you use currently? Name the real file name, not hal.dll. And the same SCSI storage system. Equal kernel, hal, running mass storage drivers connected to the same HardwareID: The old XP should boot up at new system. No preperation, no repair install. Of course a backup is highly recommended nontheless.

Use another media.

Thanks for the head up, the new heci.sys driver works at old wdfldr.sys. This elates to another test. VIA USB 3.0 4.5 driver refrences wdfcoinstaller01011.dll too. http://via-labs.com/en/support/downloads.jsp#driver xhdr.sys 6.1.7600.4501 works at default Windows 7 wdfldr.sys Yes, the same pattern: a old KMDF driver may work, even if the driver package includes a update. Missing MEI interface seems to be another reason.