UEFI BIOS

Does the D20 Have a UEFI BIOS? I dont think it does, however, I Do not know for sure. How does one distinguish what type of BIOS they actually have?
Thank you
Solved!
Go to Solution.

no, the D20 is legacy and unfortunately cannot be updated to UEFI.
ThinkStation C20
ThinkPad X1C · X220 · X60T · s30 · 600

Similar Messages

  • How can I dual boot Windows 7 on a MBR disk and Windows 8 on GPT Disk with UEFI BIOS

    I have recently build a computer. I bought a Seagate 3TB HDD which I planned to install Windows 8.1 Pro on and I also bought another Seagate 1TB HDD which I planned to install Windows 7 Ultimate 64 bit. I wanted to dual boot the two systems.
    However, I want to format the 3TB HDD into GPT and format the 1TB HDD into MBR mode.
    Can this be done in a UEFI BIOS environment?
    Windows 7 Ultimate X64 ---------- MBR 1TB HDD
    Windows 8.1 Pro X64--------------- GPT 3TB HDD
    Please reply soon, because I am in a hurry to solve this problem.
    My family members need a working PC at home :)
    My Motherboard : AsRock Fatal1ty H97 Killer
    Please help !!!!!!!!!!!!!!!!!!!!

    Does these help?
    http://www.pagestart.com/win7win81db01171401.html
    http://www.pcmag.com/article2/0,2817,2425418,00.asp
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • Dual Boot Windows 7 with preinstalled Windows 8 on GPT-formatted hard disk and UEFI BIOS.

    Question for Jordon Wees,
    Hi,
    You wrote: I can successfully install both operating
    systems in UEFI mode, with Windows 7 on the first partition and Windows 8 on
    the second partition. <o:p></o:p>
    But I couldn´t!<o:p></o:p>
    Could you please provide me how to install Windows 7
    64 bit on a PC that already has Windows 8 64 bit preinstalled?<o:p></o:p>
    I have also a GPT-formatted hard disk with UEFI BIOS
    but I get the error message that windows can´t install Windows 7 on the disk
    because it is a GPT-formatted hard disk.<o:p></o:p>
    I don´t understand this because it is a GPT-formatted
    hard disk with Windows 8 on it!<o:p></o:p>
    I can´t change the hard disk to MBR format because I
    will lose Widows 8 and all other partitions.<o:p></o:p>
    In the BIOS for the storage dives Boot´ option I
    selected the: only UEFI, I could also select the option ´first UEFI´ but it doesn´t
    change the failure of installing Windows 7.<o:p></o:p>
    Thanks, Sia

    If I am reading your issue correctly. Windows 8 came pre-installed on a computer with a hard disk setup as a GPT with UEFI configured.
    If this is the case then the outcome you are experiencing is correct.
    Windows 7 does not inherently have the ability to install into a GPT disk from the base installation. 
    The Windows 7 DVD is designed to install using BIOS mode.
    Also note that Windows 7 x86 does not support UEFI mode.
    These two articles below may help you.
    http://technet.microsoft.com/en-us/library/dd744321(WS.10).aspx
    http://blogs.technet.com/b/askcore/archive/2011/05/31/installing-windows-7-on-uefi-based-computer.aspx
    Thanks
    Sean
    MCTS: Windows 7
    MCITP: Windows 7 Enterprise Administration
    MCSA: Windows 7

  • Request for a GOP UEFI bios for R9 270 gaming 2g

    Request for a GOP UEFI bios for R9 270 gaming 2g
    thank you

    Request for a GOP UEFI bios for R9 270 gaming 2g
    thank you
    BIOS
    http://qd.baidupcs.com/file/f854518f3ebcb6e0918296e99dedbe39?xcode=651e731f64d217396dcee8d89df53b8bbc89b6a7ca8cf985&fid=1141293504-250528-731006637695005&time=1396108361&sign=FDTAXER-DCb740ccc5511e5e8fedcff06b081203-QapW05N0P5fS7fKuuF9rsE%2BzbVI%3D&to=qb&fm=Q,B,T,t&newver=1&expires=8h&rt=pr&r=691888291&logid=3537789216&vuk=1141293504&fn=Pitcairn.rom

  • Request for a GOP UEFI bios for R9 280 GAMING 3G

    Request for a GOP UEFI bios for R9 280 GAMING 3G

    Quote from: flobelix on 25-April-14, 22:32:46
    You need to add a bit more: GOP / UEFI Vbios requests - Read Here First
    Hi,
    I'd like a GOP VBIOS for the R9 280 3GB
    SN: 602-V277-46SB1403050298-W92
    Thanks

  • R9 270X GAMING 4G UEFI Bios request...

    Request for newest R9 270X Gaming 4G UEFI Bios.
    S/N:602-V303-09SB1402065219
    Current Bios link:https://drive.google.com/file/d/0B476QJVZZgUBQk5Nb1FVSlF1R1E/edit?usp=sharing

     

  • UEFI Bios or latest bios gtx 770 TF 2G OC

    S/N : 602-V282-20SB1305076182
    TF GTX 770 2G GD5 GAMING
    GPU-Z 80.04.B4.00.2F (P2005-0000)
    anyone help me to find latest bios or uefi bios for this vga?
    thx in advance

    the bios size is 164Kb and 301
    but when is used gpuz save bios n verify with nvflash sho like this
    Image Size            : 98304 bytes
    Version               : 80.04.B4.00.2F
    ~CRC32                : 151A7C5E
    OEM String            : NVIDIA
    Vendor Name           : NVIDIA Corporation
    Product Name          : GK104 Board - 20050000
    Product Revision      : Chip Rev
    Device Name(s)        : GK1xx
    Board ID              : E12D
    PCI ID                : 10DE-1184
    Subsystem ID          : 1462-2825
    Hierarchy ID          : Normal Board
    Chip SKU              : 425-0
    Project               : 2005-0000
    CDP                   : N/A
    Build Date            : 04/29/13
    Modification Date     : 05/22/13
    UEFI Support          : No
    UEFI Version          : N/A
    UEFI Signer(s)        : Unsigned
    Sign-On Message       : GK104 P2005 SKU 0000 VGA BIOS
    MSINV282MS.302
    it's that ok to flash with this rom?
    https://forum-en.msi.com/index.php?topic=180332.msg1297642#msg1297642

  • Need UEFI Bios for my MSI R7 250 2GB OC Video Card

    Hello Need a UEFI Bios for my MSI Video Card R7 250 2GD3 OC
    Serial Number:   602-V301-04SB1309065283

    use this one https://forum-en.msi.com/index.php?topic=174255.msg1265552#msg1265552

  • Need UEFI Bios for my MSI Video Card R9 290 4GD5

    Hello Need a UEFI Bios for my MSI Video Card  R9 290 4GD5
    S/N:912-V803-844B1310000906-249
    Thanks you.

    its some generic card, don't have info about it
    have ask msi here about it: >>How to contact MSI.<<

  • [REQUEST] Latest UEFI/BIOS R9 270 GAMING 2G

    Hey
    I'm looking for latest UEFI/BIOS to R9 270 GAMING 2G _http://www.msi.com/product/vga/R9-270-GAMING-2G.html#hero-overview   (without "_" )
    s/n: 602-V305-030B1405069267
    My rom: _https://www.dropbox.com/s/2y0l4cphdxkq6vl/Pitcairn.rom?dl=0   
    sha1:  090b2b863cae8fdaaa78921fed7d570831c433d4
    Sometimes my graphic card showing artifacts in games or benchmarks and maybe UEFI/BIOS update will solve it.
    Earlier I requested for it at this topic: _https://forum-en.msi.com/index.php?topic=251368.0
    But i didn't get answer about differences between BIOS versions from Svet, just only to open new topic.
    Quote from: Svet on 10-February-15, 19:21:46
    @r4zen
    open new own topic
    this number is useless and its not real vbios version
    VBE7.0.0.7b showed me that number, then how could be useless...?

    Quote from: r4zen on 16-February-15, 19:37:31
    Then please tell me why hash of my bios version does not match with this:
    _https://www.dropbox.com/s/8x6ocfv6vojf1u4/Pitcairn3.rom?dl=0    (without _)
    sha1:  e75a890be8e5a88e85acdc287401c8ca3b0e5d0 0
    it's form the same card and You told it was latest (in Avelis topic), then how could mine be the latest version with differences hash, it can't be the same.
    Quote from: r4zen on 18-February-15, 16:54:21
    Right now i know that but if vbios .rom files have differences hashes, then those are different in some way, even if it are te same versions.
    Maybe my vbios version is somehow corrupted or Avelis modified his vbios. That's why i'm asking which one is original?
    i've checked this
    yes indeed they have a different hash,
    but neither is corrupted
    Quote
    That's why i'm asking which one is original?
    no one of them and both of them in the same time
    difference between them are in the padding fills method 00 instead FF,
    but those are as addiction padding tail after the vbios image and has no matter.
    in the matter of reliability they both are fine identical with original except the padding after vbios image which doesn't matter

  • Request for R9 270X Gop UEFI Bios

    I need the GOP uefi bios for MSI R9 270X Hawk
    Thanks!

    Quote from: ricardoryuma on 04-December-14, 06:17:10
    It did not work, I made the correct procedure, the atiflash at the end informs that was completed but the new bios and id data are blank. When I restart my pc will not let activate windows 8 so well. What can be? write-lock?
    See the image here: http://prntscr.com/5cy8uw
    it says its programmed
    Quote
    When I restart my pc will not let activate windows 8 so well. What can be? write-lock?
    save and upload the vbios after flashing to verify that's flashed
    Quote from: ricardoryuma on 04-December-14, 06:49:58
    Oh, LN2 vbios flash successful with 141.rom.
    =D Thanks
    oks

  • Confusion about UEFI/BIOS and GPT/MBR compatibility issues

    So a user said in another post that they were NOT able to boot in UEFI mode and install Fedora even though it is UEFI compatible.  But this person was able to useLegacy mode and install Fedora, and furthermore, was able to "keep the Windows partition."  I'm guessing that means that Win 8 that came with it, which would be installed in UEFI/GPT mode, correct?  I'm specificly referring to the Y510P but from what I understand *every* laptop that comes preinstalled with Win 8 must be UEFI/GPT.
    So the way I understand it is that the installed Fedora is in "BIOS"/GPT mode rather than "BIOS"/MBR mode because you can't have both GPT and MBR on the same disc.
    I have just started learning about this UEFI/BIOS and MBR/GPT nonsense, and it's going to drive me crazy until I finally understand it. So I guess what I'm asking is:
    1) When I get my y510p I assume it will be in UEFI/GPT mode. Can I install non-UEFI distros alongside it as I take it was done with Fedora?
    2) If I install a linux distro alongside Win 8, do I have to worry about compatibility issues with a drive that is in GPT format? Or does the MBR/GPT issue have nothing to do with it, so I don't have to worry about ever changing my drive to MBR?  
    For example, I read that Win 7 must be installed either as BIOS/MBR or UEFI/GPT.  This can not be mixed and matched.  This means that if I could not get the Windows 7 installer to boot in UEFI I would have to install as MBR.  This also means I would have to format the drive and reinstall Win 8 on the MBR.  
    So my question is do other OS's like Linux have these restrictions?  (For example, if a particular distro will not boot in UEFI and therefor MUST install on MBR)
    3) I have a pendrive with YUMI installed with a ton of distros/tools/Win installs/etc. (It is a USB boot tool like unetbootin that allow you to add multiple bootable images.) When I tried it recently on my dad's laptop.  I have used it many, many times with my older computers, none of which were UEFI.  It works great.  Now that I've had a recent encounter with my dad's ASUS Windows 8 computer (not with the y510p yet) I found out that UEFI seems to be complicating the crap out of things (for me, at least.)
    So when I used this computer, I noticed that when I boot (with legacy mode enabled) and enter the "boot selection screen" in order to boot with USB, I have two options a) UEFI:"name of usb" and b) "name of USB". The UEFI option would NOT boot, but it would boot without the UEFI: option.
    So does this mean that I am booting in non-UEFI mode and once I have booted this way and choose a distro to install that it CANNOT install in UEFI mode?  I recently saw a tool called Rufus that I have yet to try that has an option to set the bootable USB to UEFI, so that would possibly work if I wanted to install a UEFI compatible distro (Arch linux is what I'm wanting.)
    4)  If installing a UEFI compatible distro (such as Arch) requires that the USB device be able to boot in UEFI mode has anyone been able to do this?  Has anyone even been able to boot a device in UEFI mode to do *anything* such as run a live linux?  
    I'm 99% sure I would be able to boot in legacy mode and run a live linux (because I did so on my dad's computer) but the problems arise when I consider how to INSTALL.
    I would really like to know the answers to these questions (as scattered as they are.) Any help would be appreciated!
    Unnecessary info:
    (I started learning about BIOS/UEFI and MBR/GPT the hard way a few days ago by trying for hours to install Windows 7 on my dad's Windows 8 laptop because I could NOT get Win 7 installation to work...it kept asking for drivers before I could install until I finally used the Windows USB install tool, put the stick in a different USB, AND formatted the drive as MBR because Windows 7 would NOT install on the existing GPT drive until I used diskpart.exe -clean. And I have read that Win 7 64 bit will work fine on a UEFI/GPT setup. I used the Windows 7 USB boot tool which did NOT give me a UEFI: and regular option. It showed up simply as "name of usb" without a UEFI in front. Since I read that Windows 7 must either be in BIOS/MBR mode or UEFI/GPT mode that this drive would not boot in UEFI mode, and I don't know why...Although I believe I read that Win 7 cannot be installed from a USB in UEFI/GPT mode, only BIOS/MBR.  UEFI/GPT mode requires a DVD install but I did not have a drive to test this.)

    I have a Y510p which is running dual boot Windows 8.1 and Arch Linux.   I think that it is strongly advised to do plenty of reading ahead of any install if you will be using UEFI and Linux so that you understand all the issued before making critical changes to the existing system.
    Yes, if the machine comes with Windows 8 (as mine did) then the disk will be formatted with a GPT partition table (instead of the old MBR partitioning scheme), and will boot using UEFI. If you are going to try to keep the existing Windows 8 system and add Linux then you will need to keep the disk with its GPT partition table and partition structure, but you can shrink the Windows 8 C: drive to make space for the Linux partitions that are needed ( a root partition and at least a /home and/or /opt partition and possibly a linux swap partition also ).  If you want to boot the Linux install via UEFI then you can simply add the required boot directory to the EFI System Partition (ESP).
    However it is very important that before trying to do any linux install that you switch off Fastboot from within WIndows 8 (or 8.1). Also most Linux distributions are in some difficulty booting using Secure Boot, though a few such a Ubuntu and Fedora are supposed to be able to do so. Hence it is much easier to work with Linux if Secure Boot is first switched off from the BIOS settings menu.
    The order of operations that I used was;
    1) Switch off Secure Boot from the BIOS - and boot back into the Windows 8 system to check that it boots OK.
    2) With Windows 8 running go into the settings and switch off Fastboot (which does a hybrid suspend when it shuts down instead of a full normal shutdown - if you don't do this then the memory gets overwritten when booting Linux in the future which means booting back into Windows will fail). 
    3) Reboot back into WIndows and check all is well, and if so then use the disk management facility within Windows 8 to shrink the C: drive to make room for the Linux partitions.
    4) Reboot to check Windows 8 still boots OK.  
    5) If you are going to update to Windows 8.1 then do so, and then update everything once it is booted (it is a huge update and takes ages!). Once done then you will likely have to update drivers for the graphics cards, the clickpad and possibly the wireless chip and ethernet chip. I found that I needed to get drivers that were newer than were available on the Lenovo website, by going to the relevant hardware manufacturer website (eg for synaptics for the clickpad). Then spent a week or so in the evenings getting Windows 8.1 configured the way I like it.
    6) Then I did a lot of reading about the various options for the boot manager that would suit a UEFI boot for a dual boot system for Windows 8.1 and Arch Linux and there was a choice of Grub, Gummiboot, rEFInd, and others - and after reading the details I decided on rEFInd as my boot manager which can boot not only any new Arch Linux install but automatically finds the Windows UEFI boot files and presents the options in a nice graphical window once the system gets past POST at bootup.
    7) It was important to check which partition was the ESP and to know what partitions I needed to create for the Arch Linux system.  Then I went ahead and booted from a usbkey to a uefi install system, and very carefully proceeded with a standard Arch Linux install, being particularly careful to know where to put the rEFInd boot manager files and the kernel and initrd files. Also I used efibootmgr to write the appropriate NVRAM boot entry in the motherboard memory so that the uefi boot system knows where to find the rEFInd uefi boot files in the ESP.
    8) Once complete the system boots to Arch Linux as the default, with a nice Windows icon which you can select with the arrow keys within the boot timeout period (default 20 seconds).
    I noted also that it is possible to create boot stanzas in the rEFInd boot manager config files which allow rEFInd to chain load other Linux systems or even other bootloaders if you wish - so it is very flexible. So if you want to you could install a grub standalone set of diretories/files so that if the normal linux boot fails then you can select the grub icon from rEFInd and chainload grub to boot either the same Archlinux install, or point to a third linux distribution if you have more partitions containing that third install which might be Ubuntu or Mint or ....
    Either way although getting to understand how uefi boot works is a learning curve it is actually generally simpler than the old legacy BIOS boot. With uefi you no longer need an MBR on the drive, and only a suitable EFI System Partition which has to be VFAT formatted. However if you want to have one of the linux distributions booting from legacy MBR then you need to create an MBR at the start of the drive - so you would need to move the start of the first partition and create a suitable sized Master Boot Record otherwise MBR boot can't work. If you do that then of course you have to be careful if the Windows partition is the one being re-sized that it doesn't mess up the Windows boot! However since using uefi to boot rEFInd allows a chainload to grub/gummiboot or other bootloaders then there should be no need to mess with MBR booting if you go down that route.
    If you are interested in rEFInd then the author Rod Smith has a good set of documentation that describe the details at http://www.rodsbooks.com/refind/
    He is also the author of a really excellent disk partitioner for GPT disks - http://www.rodsbooks.com/gdisk/
    Clearly it is necessary to read up on the boot facilities available for any linux distribution that you plan to put on the system.
    One nice thing is that uefi boot with an efistub supported kernel build is really fast on the Y510p. My system boots Arch linux in about 7 seconds to the KDE login prompt once the POST is complete and that only takes a couple of seconds.  Of course Windows is much slower once it is selected at the rEFInd screen and takes somewherearound 40 seconds or so to boot, but at least Linux is super fast!
    Anyway I hope that this helps.

  • UEFI bios boot into safe mode w/o msconfig or F8

    Hi, thanks in advance for taking the time to answer.  First off I'm using an ASUS motherboard with UEFI bios on windows 7 64bit.
    I'm having trouble with my user account being corrupted and cannot be logged into.  I've already looked up how to fix this issue but it requires me logging into safe mode to do so. 
    I am aware of the 2 common methods people are prescribing (msconfig and F8) but neither are an option in this situation it seems.
    Being that I can't log in, and I do not have a second admin account, I cannot use the msconfig method.  I've already tried hitting F8 during start and it just gives me the option to either boot my HD or enter bios.  I also went through the bios
    options and didn't see anything there either.  There's got to be another method than the two I've previously mentioned, right?  Or am I just missing something simple here?
    == edit ==
    == Solved problem myself ==
    heres how for those with same problem:  after hard restarting my computer quite a few times (apparently its SUPPOSED to do this each time but other folks on the internet and myself find it to only work 40% or less) it went into automatic repair mode. 
    after that ran through, to no avail (BIG surprise), it allowed me to enter Command Prompt mode outside of windows.  there I was able to enable a safe mode boot loop so each time my computer boots it automatically goes into safe mode.  fixed what
    i needed and undid the safe mode loop in msconfig.
    back to business as usual!  woot woot

    Asus boards BIOS Boot Menu key is F8... this is annoying if you use their boards with Windows installed, as it is also the key for getting the Windows boot menu.
    What needs to be done is use the F8 to get the menu, select the hard disk (or boot manager if EFI) and then start hitting F8 after you press enter on the boot device. This is the easiest way I've found, as trying to guess when the boot is handed off from
    the board to Windows is hit and miss.

  • List UEFI Bios Settings Using PowerShell

    Create a file containing the uefi bios settings with values on your desktop by running this PowerShell script:
    gwmi -class Lenovo_BiosSetting -namespace root\wmi  | select currentsetting | where Currentsetting -ne "" |
    select @{label = "Name"; expression = {$_.currentsetting.split(",")[0]}}, @{label = "Value"; expression = {$_.currentsetting.split(",")[1]}} |
    Sort Name | ft -auto > $env:userprofile\desktop\"UEFI BIOS Settings.txt"

    Hi jasgud_RETSD -  Have you tried using PSEXEC?   PSExec lets you run items using the system account.  You can download psexec from the Microsoft page for Sys Internals.   Command - psexec \\localhost -s -h powershell.exe -executionPolicy bypass -Noninteractive -Noprofile -file %script%.ps1 -password %password% -file LockBIOSSetting-enable.txt -s = Run as System -h = no profile-accepteula - accepts eula I ran the your command (changing the powershell name) and confirmed you can call powershell.exe and use powershell flags (nointeractive -noprofile).   Once this to keep in mind when using psexec - the command being called (powershell.exe in this case) must be located in a directory referenced in path variables.  psexc can be executed multiple clients at once by specifying a txt file with the names of the clients you wish to target.  Multiple Clients PSEXEC @domainclients.txt -s -h powershell.exe -executionPolicy bypass -Noninteractive -Noprofile -file %script%.ps1 -password %password% -file LockBIOSSetting-enable.txt I am more insterested in getting the bios settings setup for deployments   Thanks Jeff Ragucci  

  • Installing Windows 8 using WDS on devices that use UEFI BIOS

    Hi all, sorry for the word wall.
    I am currently planning a deployment of Windows 8.1 Upgrade 1 on Toshiba Z10T's which I will be deploying using WDS, which is running on Windows Server 2012 R2.
    The Toshiba Z10T device in question is quite handy as it can switching between legacy CSM BIOS and UEFI BIOS.
    The devices are shipped out of the box with UEFI BIOS on, and obviously we would like to be able to just un-box & image them, however we have constant issues when trying to PXE boot devices with UEFI BIOS, and the only way I can get them to PXE boot
    is by switching over to legacy CSM BIOS.
    From what I have read from other forums on the internet, UEFI & WDS don't get on that well - so what I was wondering is this-
    We currently have SCCM 2012- I was wondering would we have more success booting to a UEFI BIOS if I used SCCM & MDT or will I still encounter the same issues?  Is it the PXE client in UEFI that is at fault?
    Problems that we encounter when we use UEFI to PXE boot are- Drivers not there to get into to the boot image; if we can get them to image, devices will not join to the domain; devices will image but not install any drivers.
    Thanks for reading this word wall.

    PXE itself doesn't use/need any drivers at all - it's the post-boot (boot image), and the full OS (install image) which need the drivers.
    PXE is totally contained within ROM, and that ROM will download the NBP (for non-UEFI this is typically wdsnbp.com)(for UEFI this is typically bootmgfw.efi).
    In a ConfigMgr (or MDT) scenario, the NBP then downloads boot.sdi, boot.wim(WinPE) and then install.wim(Full OS).
    Both boot.wim, and install.wim, need to have the correct network card drivers and also the correct storage controller drivers installed.
    This is how Windows deployment via PXE works (it's most often the lack of the correct drivers, at the required stage/phase, which causes grief)
    [background]
    Although we have a small number of Z10Ta and Z10Tb devices in my organisation, we are still using the factory image on them, so I haven't spent the time to incorporate them into our ConfigMgr OSD (PXE) supported-list yet.
    We are just starting our journey towards UEFI-boot. We are using MDT UFD bootable media for our lab and it's working fine for UEFI and Win8.1/64bit, on various devices (although not tried the Z10Ta/b). Am nearly finished moving that all into ConfigMgr, to
    then begin testing it all with PXE.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • How to enter the new UEFI( BIOS ), if UEFI does not respond to F10(esc, e.t.c.) at startup?

    1) I bought a HP 255 .. preloaded with licensed windows 8.1 (overpaying about $ 150 compared with the same nout. with pre-dos ,
    2)yesterday update the "BIOS" -UEFI- from HP website and on the recommendation and with the help of an assistant "Assistant HP",
    3)reload (successfully re-entered the windows 8.1), and
    4) wanted to put second OS (ubuntu Linux without removing the windows 8.1, which is totally legal action and a 100% user right !) in accordance with the instructions http://www.everydaylinuxuser.com/2014/05/install-ubuntu-1404-alongside-windows.html. (way before such procedures have been much easier! Have to completely abandon the windows!)
    5)After compression partition with win8.1 and release empty partition for second OS( Linux), off in the control panel windows "Fast Boot" I turned off the laptop (which is turned off and not in sleep mode switched). entered the UEFI, Turn off secure boot and Legacy Boot (probably in vain!)
    After saving and rebooting the laptop completely refused to accept from the moment of "power On" the F10 (et al. Keys esc, F2..12), and showed only "black screen" without any symbols and inscriptions, though, and respond to Ctrl-Alt-Del (blinking backlight -reload). external monitor also showed "No Signal".
    If I understand correctly, UEFI has been "upgraded" (not for the better by m.), And then at boot became a special check windows loader (type bootx64.efi) th right?
    1) where (is there?) correct installation instruction 2nd OS (for example Linux Ubuntu), without removing the pre windows 8.1 (with the new UEFI)?
    2) what can be done? How can I enter the UEFI-"BIOS"   to fix options (if i have not CD with windows8.1 liveCD, but have backup of pre-inst win8.1 from nout)?

    You can do that without going in the BIOS(UEFI).  At the Start screen, type System Settings and hit Enter.  There is a Boot Options tab there where you can make your boot choice. However, for when you do need to get in the BIOS in Windows 8.x, Shutdown the computer while holding down the Shift key.  Then, on Startup, hold down or rapidly tap F2 while hitting the Power  button.
    Yes, you do have a Recovery partition on your HDD and you were advised to make recovery media when first using your machine for even further protection in the future. It's up to you whether you wish to make even further images.  I do and I use Macrium also.
    You need to spend some time with your User's Guide particularly starting on page 46 "Recovery of The Internal Storage Drive".
    C.B.
    Toshiba Sat. C75D-B7260 Win 8.1 64 Bit--Toshiba Sat. L775D-S7132 Win 7 HP SP1 64 Bit and Win 10 PRO Technical Preview--Toshiba Sat. L305-S5921 Win Vista SP2 32 Bit

Maybe you are looking for