Tag Info

Hot answers tagged

8

The last time they even put out an update was almost 2 years ago. I really don't think there is even any development on it anymore. According to their site Windows 8 is not supported at all. Here is the supported OSs page. http://www.truecrypt.org/docs/supported-operating-systems I am currently using Bitlocker for one encrypted drive. Bitlocker is native ...


7

Solved :) The cause seems to be a strange feature in the UEFI implementation, which can also be seen in the Open Source TianoCore implementation: https://github.com/tianocore/edk2/blob/master/IntelFrameworkModulePkg/Library/GenericBdsLib/BdsMisc.c#L1425 I ultimately found it after diffing my EFI variable dumps after the last 21MB "loss" and finding ...


5

First, you're conflating two or three different things (perhaps because of poorly worded program messages): Firmware type -- Old PCs used the Basic Input/Output System (BIOS), but new computers use the Extensible Firmware Interface (EFI) or its newer variant, the Unified EFI (UEFI). The main duty of both the BIOS and the EFI is to start the boot process, ...


4

You can do it, but it depends a bit on your hardware and your expectations of a properly functioning Windows 8.1 + TrueCrypt installation. TC still works for encrypted containers in W81, but since it relies on having an MBR partitioned disk and integrated bootloaders, for full disk encryption, it will not work in a sensible way, since W81 need GPT formatted ...


4

Although TrueCrypt have announced their intentions to support Windows 8 and UEFI, their last version still dates from 2012. As far as I can see, your options today are : Partition your disk into two parts, Windows and TrueCrypt. If you are worried about unauthorized boot of your computer, put a password on the BIOS. Use BitLocker instead of TrueCrypt, if ...


4

I ran into the same error on an Asus UX21E machine. The latest BIOS (v 214) didn't fix the trick, and my USB disk was properly prepared as a EFI boot devices. I was able to work around the problem using a hack I found on a related thread on the ArchLinux BBS. The gist of it is that since this system shipped with Windows 7 it doesn't have Secure Boot stuff ...


4

UEFI doesn't guarantee any kind of graphical interface. It provides the ability for companies like Gigabyte to create and design their own graphical BIOS. This is explained fairly well in the Wikipedia article for UEFI. So now I wanted to ask you if somebody knows how to enable/get into this interface? Do I have to enable UEFI somewhere UEFI isn't ...


4

Windows 7 doesn't support UEFI with 32Bit. So it is BIOS/legacy mode.


3

WUBI has always been a second-best method of installing Linux, even in BIOS mode, so its incompatibility with EFI-mode booting is no great loss, IMHO. WUBI's greatest strength is that it enables installation without modifying existing partitions, and that can be done as well, if not better, via virtualization technologies like VMware or VirtualBox. Rather ...


3

At the moment of writing none of the win8 built-in recovery option or asus backtracker are able to reset the system to the factory shape when new disk is installed. They create USB recovery backup disk but restoring from it is impossible. The goal of this guide it to show how to create win8 factory backup that can be restored to new disk and boot to the ...


3

EFI by itself isn't troublesome. Windows 7 also supports (U)EFI very well, so you can easily wipe the Windows 8 partition during the Windows 7 setup. EFI is the mode of the firmware itself. If you want to change back to legacy BIOS (oh boy, it really is legacy, possibly the oldest artifact in today's modern PCs), you have to also change your disk ...


3

Easy BCD can boot image files from your hard drive, I have done this on windows 7. It may work on windows 8.1 too.


3

I'm pretty sure that EXTLINUX is a BIOS-only sub-tool of SYSLINUX. That said, SYSLINUX is available in an EFI form, but this EFI version of SYSLINUX does not use EXTLINUX and requires that the kernel be stored on the same partition as the boot loader itself, which will normally be on the EFI System Partition (ESP). Ubuntu doesn't set things up to do this by ...


3

First the firmware looks for EFI variables Boot#### (e.g. Boot0000, Boot0001, and so on). They describe the EFI boot menu entries, and contain the complete location of the corresponding executable. For example: $ sudo efibootmgr -v BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000,0001,0006,0007 Boot0000* Linux Boot Manager ...


3

Using Boot Repair, as MariusMatutiae suggests, may work; however, that program sometimes does more than is wise, so I prefer to avoid it. There are at least three less radical solutions: Solution 1: Use the Firmware Many EFIs provide a built-in boot manager that enables you to adjust the boot order. Your Ubuntu/GRUB entry probably still exists, so all you ...


2

The entire point is the "chain of trust" it creates. If I have a piece of software that I need to make sure that nothing malicious can intercept what I am doing and put their own code in I need to trust the program launching my program. To trust that program that launched my program, you need to trust the program that launched the program that launched my ...


2

Error 0xc000007b may relate to mismatch between 32- and 64-bit, so may be caused by 32-bit grub4dos trying to boot a 64-bit OS. The grub4dos latest release dates from 2009 and knows nothing about UEFI, so shouldn't be used. You should probably start from scratch and use the tool UEFI MULTI. The purpose of this tool is described as : Tool to format ...


2

Hardware (even virtual hardware) is often initialized by firmware (the BIOS, pre-EFI hardware-initialization code in the firmware, or the firmware built into a device itself). This is especially true of video hardware and some other devices that are built into motherboards. Furthermore, the EFI provides a framebuffer driver for accessing video devices, which ...


2

Some BIOS implementations may only allow either all UEFI boot or all Legacy boot, and it would not be possible to mix the two. Other BIOS implementations are able to deal with both. It sounds like the CSM mode allows you to boot both UEFI and Legacy drives. My motherboard does this, and so it has a "UEFI Hard Drives" and then a regular "Hard Drives" group, ...


2

The manual exists on Asus' support site and it contains the beep codes on page 2-16 ("Chapter 2: Getting Started"):


2

I think this isn't possible (I've got an X230 and I'm pretty sure it isn't possible with this model and I assume there's no difference with Yoga), but you could install an EFI bootmanager like rEFInd. I'd prefer this approach since normally it's a lot easier to change a bootloader's configuration than fiddling with efibootmgr et al.


2

FIRST: I have not had to boot off external drive and choose not to work with windows 8 because no concurrent user hack. That being said: I usually run Darik's Boot And Nuke It will clean the drive or any drive with sensitive information. Since it is new I would run the default. It gives you choices. method (predetermined number of TimexRounds the ...


2

So having tried several other BIOS flashing tools on this system to no avail, I decided the BIOS might be so borked that it wasn't going to be able to flash itself and that it needed outside help. Unfortunately I imported this board and getting warranty service on it would be a lot of hassle. I was unable to locate a new BIOS chip, so I decided to try to ...


2

The article Problem with installing Centos 6.3 on USB Stick might pertain to your problem : If you ever face a "kernel panic" issue when trying to boot Centos 6 from your USB stick, this is due to the EFI bootloader not pointing to the root of your USB stick. To fix this, go under the EFI folder in your USB stick, then find those files ending ...


2

This is because in the UEFI firmware setup, no specific keyboard layout has been loaded. So it falls back to a firmware default, which almost certainly happens to be a US keyboard layout. The computer doesn't really know what's printed on the various key caps on the keyboard. What it does know, is how to map keyboard scan codes to character numbers ...


2

You're operating under the misapprehension that PKs are tied to ESPs; they aren't. The Secure Boot cryptographic features require that individual boot loader files be signed, but those files are stored on ordinary FAT filesystems that are themselves not signed, encrypted, or otherwise cryptographically interesting. A signed boot loader file can be moved from ...


2

My first suggestion is to upgrade your firmware. Check your manufacturer's Web site for such an upgrade. (It will probably be called a "BIOS update" or something similar; manufacturers usually call their EFIs "BIOSes," although IMHO this just creates confusion in the long run.) My second suggestion is more of a comment: The Windows 7 disc is a bit weird ...


2

What's difference between installing an OS on BIOS or UEFI mode?? For example Win 8 must be installed in BIOS mode or what?? Simplest difference is the fact you will be unable to use GPT partitions which means your unable to use 2TB+ drives. There are ways to do it, involves doing a few things, but the main system partition is limited to 2TB. I ...



Only top voted, non community-wiki answers of a minimum length are eligible