cdob

Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/windows-8/create-reset-refresh-media

http://www.msfn.org/board/topic/107504-integration-of-intels-sata-ahci-and-raid-drivers/ http://www.win-raid.com/t22f23-Integration-of-Intels-AHCI-RAID-drivers-into-a-Windows-XP-CD.html http://www.win-raid.com/f37-Specific-NVIDIA-nForce-AHCI-RAID-Drivers.html

How do you boot to First Part of Windows setup? Do you press a hotkey like F12 and select the USB boot device? And next reboot to "first internal disk" by default? It's fine to boot that way and not use "Second part of Windows setup/Boot first internal disk" It's not really needed in that case. This option refers to (older) machines rebooting to USB disk by default. In that case "Second part of Windows setup/Boot first internal disk" is nice to continue.

There are JMicron JM2033x FW Update Utility http://www.usbdev.ru/files/jmicron/ No idea how to use them or the firmware solve the issue.

A firmware update may help. No firmware update at distributor: http://www.newlinkproducts.co.uk/prodinfo.asp?catID=6&prodID=294 Which chipset is used internally? Can you make some pictures?

Thank's to ambroseg1 for asking the USB question. I've to admit: I did't expected a USB at a desktop machine. My fault. And assumed using a plain XP install CD before. That's why a community is nice. Different pre defined opinions, expectations, conditions and knowledge produces a solution finally.

Use annother approach: from running Windows 7 use WinNTSetup. http://www.msfn.org/board/topic/149612-winntsetup-v372-375-beta-1/ It's causes some issues adding a older OS to a existing machines (XP in addition to Windows 7). Offer a free partition. And restore/create the dual boot configuration. Start a new thread, if this is unclear.

Yes, try the existing one

PCI\VEN_1002&DEV_4380&CC_0101 That's IDE emulation mode. No SATA drivers required. OS default drivers support this machine. The BSOD 7b refers to another reason: e.g. USB boot device It's a Dell. Read FAQ 3 http://www.msfn.org/board/topic/116766-faqs/

Which Windows release do you use? Yes, use XP SP3 at a Core2 machine. That's PNP driver installation: a device dosn't respont properly to driver loading. If XP SP3 hangs still: fix the half broken hardware. Remove as much hardware as possible. Test the hard disk with manufacturer tool.

The integrated driver dosn't support the virtual box hardware. Use another driver (v7.8) or another hardware. http://www.msfn.org/board/topic/107504-integration-of-intels-sata-ahci-and-raid-drivers/

In addition: http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=1371&MenuID=17&LanID=0#fragment-SPEC The manufacturer supports 32 bit Windows out of the box only. I understand: the stock one is a 32 bit UEFI firmware at a x86-64 CPU, searches a file /efi/boot/bootia32.efi Break: there is no UEFI Windows 7 32-bit. No, I don't understand this configuration. And the custom BIOS from ECS is a 64 bit UEFI firmware. Yes, a very nice testing board. IsoBuster free part list file names, there should be a (virtual) folder FAT(BootImage.img) If not, then enable: Options, File System(s), El Torito (Boot), Check boot-images(s= for FAT and list files and folders if present. Acronis docments 64 bit UEFI firmware only so far.

Can you verify again? Does floppy image contains a file /efi/boot/bootia32.efi or e /efi/boot/bootix64.efi ?

That's interesting: The CDC-I/D2550 uses a 64 bit CPU ATOM D2550 http://ark.intel.com/products/65470/ So far I know: CPU matches UEFI code: the manufacturer implements a 64 bit UEFI firmware at a 64 bit CPU Or the manufacturer implements a 32 bit UEFI firmware at a 32 bit CPU. E.g. a tablet with a Z2760 http://ark.intel.com/products/70105/ Appearantly a manufacturer can implement a 32 bit UEFI firmware at a x86-64 CPU too. It's getting more confused.

No, not this direction. Linux-based bootable media http://www.acronis.com/en-us/support/documentation/AcronisBackup_11.5/index.html#1230.html A UEFI (WinPE) ISO is either 32 bit or 64 bit. No, UEFI specification supports one EFI boot catalog entry only. A 32 bit UEFI searches file /efi/boot/bootia32.efi Acronis dosn't support 32-Bit UEFI devices at boot: https://kb.acronis.com/content/43091 There is no 64 bit BIOS. It's independent from the OS. The BIOS reads the Boot Catalog and selects the BIOS entry. The UEFI firmware reads the Boot Catalog and selects the EFI entry. One ISO for both: BIOS and UEFI Do you like to boot from a USB Thumb? This was not specified so far. Yes, this assume a USB HDD booting at current hardware. Windows differs a USB Thumb and a USB HDD, actually a removable or fixed disk... I'm claiming amnesia next. Use previous mentioned grub.cfg: this works at BIOS and UEFI 64 bit machines. Add a loopback grub.cfg entry to 32 bit BIOS machines. Yes, you may extract files as another option. https://kb.acronis.com/content/46255 https://kb.acronis.com/content/41723 https://kb.acronis.com/content/11071 There are a lot of different cases: different WinPE versions add components to ISO or to WIM image. Use the manufacturer solution. It resembles a default WinPE. Diskpart section similiar http://msdn.microsoft.com/library/hh825109.aspx And copy extracted files to USB thumb. I'm claiming amnesia at Acronis WinPE ISO questions...

Which WinSetupFromUSB version do you use? The current version supports your request.

Well, this is asking for http://en.wikipedia.org/wiki/El_Torito_(CD-ROM_standard) It's 20 years old only. Time to learn some basics? The El Torito specification requests one boot catalog. CD sector 17 contains a pointer to the boot catalog. Details clarifies the specification and a hex editor. The system reads CD sector 17 and the boot catalog next. There is one BIOS and another EFI entry at the boot catalog. The system interprets the boot catalog and select one appropiate entry. A USB Thumb resembles a hard disk. Booting from hard disk rules apply here. The UEFI and BIOS reads hard disk structures and boot this More basics http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface http://en.wikipedia.org/wiki/Master_boot_record The BIOS process the MBR code. A 64 bit UEFI reads NVRAM or searches file \efi\boot\bootX64.efi By the way: the 64 bit Acrornis dat*.dat UEFI files works at a 64 bit machine with a BIOS too. No need for the 'BIOS' files at a 64 bit machine. The 'BIOS' files refers to 32 bit machines.

The 64 bit UEFI firmware reads the El Torito boot catalog, mounts the EFI referenced FAT floppy and lauch the EFI application \efi\boot\bootX64.efi.

Thanks, this works at a proper image: -boot-info-table was used to patch isolinux.bin. Unfortunately slitaz-3.0.iso is a exception, isolinux.bin is not patched. BootImage.img is listed at size 2048 bytes, despite it's a isolinux.bin header. What todo in such a case: just display the 2048 bytes or display isolinux.bin file size? Another case ubuntu-14.04.1-desktop-amd64.iso I wonder a special isolinux.bin case: if a BootImage.img LBA 484052 matches a file name isolinux.bin LBA 484052, display isolinux.bin file size. Yes, it's guessing still. Of course not, feel free to use names you like. Yes, I like the extents approach. I don't expect any new feature at free version, [Professional] license is fine. You shouln't mention extents, I've two old testing files arround. a Insane_3PiT.iso (exploring the limits: several extents to the same 3 GiB section), IsoBuster lists at 700 TiB file. Just laugh about the crazy file. a chars.iso (9 extents to a 26 byte section each): IsoBuster displays size 234 bytes correctly and extract a file 16618 bytes

Well, we have a "Windows PE" section too http://www.msfn.org/board/forum/81-windows-pe/ And a "Install Windows from USB" section, two sticky support Windwos 8 ISO install http://www.msfn.org/board/forum/157-install-windows-from-usb/ What about asking specific questions there?

As for Acrois EFI image: good work BootImage.img list correct LBA and Size. Properties, Advanced lists Virt.Sect L.S.: 0 Yes, a user can detect real data. Platform: Undefined. Can you list EFI? Acronis.img list the whole BIOS data: the loader and the FAT image. Can you slit the display: Acronis.bin (loader) and Acronis.img (image) Slitaz: BootImage.img LBA 33, size 2048 bytes \boot\isolinux\isolinux.bin starts at LBA 33 too. Size 14336 bytes. Can you assume BootImage.img size 14336 bytes, Virt.Sect L.S.: 4 still

http://geniatech.com/pa/mp725.asp I understand: You may connect a 2.5” or a 3.5” SATA HDD to the motherboard directly. No cable required.

Which real space is available? Can you connect a 2.5" HDD directly to the motherboard?

Yes, this is the idea. The no emulation "Acronis.img" contains a proprietary boot loader. This loader mounts the FAT image located behind the boot loader. There is no file system or El Torito hint about this FAT image. The interesting files are located at the FAT image. The WinPE5 and Linux ISO uses different layouts. Don't mix this two one.

It's working in BIOS mode, with certain limitations. I don't know any hint at UEFI mode. As for wimboot: "wimboot DaRT70-x64.iso" loopback boot at BIOS mode http://reboot.pro/topic/19970-grub2-wimboot-windows-setup/ There is efi wimboot. http://ipxe.org/wimboot http://git.ipxe.org/releases/wimboot/wimboot-latest.zip How to adapt this to UEFI WinPE booting? Well, both drivers are at a higher level. Windows core boot files are running already. The current issue is more basic: Create a virtual disk: let windows loader find bcd, boot.sdi and boot.wim.