Jump to content

Search the Community

Showing results for tags 'Acronis'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 1 result

  1. On a BIOS PC, most folks use Grub4DOS to boot ISO images. But how to boot them on UEFI PC, especially without Legacy CSM Mode, since Grub4DOS doesn't support UEFI? Taking a popular Acronis True Image Home (ATIH2014) ISO as an example (either Linux or WinPE 5.0 based, or better BOTH), can someone explain, how to boot an ISO on UEFI Windows 8.1 PC? I found one example of booting seemingly WinPE-based UEFI ATIH2014 (release unknown) by Grub2. That didn't work for me - couldn't find dat8.dat and dat9.dat files in Boot.bif image extracted by UltraISO from the mounted ATIH2014 ISO boot sector. I couldn't also mount any *.img files from Floppy Image written on the ISO's CD track due to unknown *.img filesystem. Its unclear, why boot images extracted by ISOBuster were different from those extracted by UltraISO from the same ISO? As well, how an average user can derive similar grub.cfg menu section - based on what miracle vision? Any background explanation or more generalized logical approach would be handy... Also, how GOP-only HW support plays into this?
×
×
  • Create New...