pbatard / rufus

The Reliable USB Formatting Utility
https://rufus.ie
GNU General Public License v3.0
28.43k stars 2.54k forks source link

Hiren's BootCD - How to Boot in Surface Pro 2 #273

Closed Gustavo- closed 10 years ago

Gustavo- commented 10 years ago

Hello, I'm looking for a way to boot HBCD in my Surface Pro 2. I downloaded the HBCD .iso from this site: http://www.hirensbootcd.org/download/ but I can't write the .iso in my usbpen, because I get this error:

image

What am I doing wrong?

Gustavo- commented 10 years ago

I tryed also with this partition scheme, and this way I could write the .iso file; but i can't boot in my SP2

2014-01-17 17_46_19-rufus v1 4 1 348

pbatard commented 10 years ago

Yes, the "Target Type" in the error message refers to the "Partition scheme and target system type" dropdown, and since your ISO is not EFI compliant, you must set BIOS as your target system type.

However, the Surface Pro seems to be UEFI only, and from what I am reading, it can't boot in BIOS mode. I'm afraid this is a restriction that Microsoft added to the Surface Pro and that has nothing to do with Rufus, so you will need to ask Microsoft or the Surface Pro user forums how you can boot an USB in BIOS mode, if it's possible at all.

Or you may try to find if there is an HBCD image that supports booting in EFI mode.

Booting in BIOS or EFI mode is a bit like an application, that can be either compiled for Mac or Windows. Unless you ask the developers to create a version that runs on your machine, a utility such as Rufus cannot convert between one type or the other as they are simply too different. So there's really nothing I can do to help you here.

Gustavo- commented 10 years ago

thaks for your answer.

I'll try to work around this issue with a linux distro that can boot in UEFI mode; any suggestions?

pbatard commented 10 years ago

You should try Arch Linux as they have good EFI support. Since your issue is not Rufus related, I will now close it.

lock[bot] commented 5 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.