PATA/SATA boot order anomaly?

Just tried adding XP 64-bit for dual-boot fun and discovered the following BIOS quirk (bug?). Has this been noted somewhere else? Here's my setup and problem:
No RAID anywhere, two HDDs total: 1 on SATA 1, 1 on PATA 2. I have a DVD drive on PATA 1.
I usually boot XP Pro from SATA 1. I had to change the HDD order in BIOS so it won't try my non-bootable PATA HDD first. This has worked (almost) every time until now.
Discovered that if I have a bootable CD (like 64-bit installer) in my PATA DVD drive, the BIOS overrides the SATA priority if I don't choose to boot from CD. I.e., I don't push "any key to boot from CD" and when BIOS moves on to boot from HDD, it goes for PATA rather than SATA, apparently because it's just tried a device (DVD) on the parallel controller so why not try the next parallel device, despite the SATA priority setting in BIOS. No boot files on PATA HDD so failed boot. Then I suppose then it normally tries SATA and everything's fine.
Except 64-bit is now installed on a partition on PATA drive (don't ask), and apparently the BIOS quirk I'm describing with such piercing clarity made the 64-bit installer write a new MBR and/or set the PATA drive as boot (? - I'm over my head here), with the result that I get different NT boot screens depending on whether or not I have a bootable CD in the drive -- regardless of whether or not I actually boot from it.
Practical result: if I have a bootable CD in the DVD drive (but don't boot from it), I get XP 64-bit 'cause it boots from PATA drive first. If I take out the CD, I get XP Pro 32-bit like I used to, booting from SATA drive first.
Further result is that neither 64-bit nor regular XP Pro boot loader routines can accurately boot into the other OS even if boot.ini is manually edited, because of BIOS disk enumeration quirks I'm guessing.
Okay this now makes little sense even to me, but if someone sees a flaw in my logic (rather than the BIOS HDD priority setting), well I'd be grateful to hear it. Otherwise I'll send it along to MSI.

Quote
Originally posted by tagaste
Just tried adding XP 64-bit for dual-boot fun and discovered the following BIOS quirk (bug?). Has this been noted somewhere else? Here's my setup and problem:
No RAID anywhere, two HDDs total: 1 on SATA 1, 1 on PATA 2. I have a DVD drive on PATA 1.
I usually boot XP Pro from SATA 1. I had to change the HDD order in BIOS so it won't try my non-bootable PATA HDD first. This has worked (almost) every time until now.
Discovered that if I have a bootable CD (like 64-bit installer) in my PATA DVD drive, the BIOS overrides the SATA priority if I don't choose to boot from CD. I.e., I don't push "any key to boot from CD" and when BIOS moves on to boot from HDD, it goes for PATA rather than SATA, apparently because it's just tried a device (DVD) on the parallel controller so why not try the next parallel device, despite the SATA priority setting in BIOS. No boot files on PATA HDD so failed boot. Then I suppose then it normally tries SATA and everything's fine.
Except 64-bit is now installed on a partition on PATA drive (don't ask), and apparently the BIOS quirk I'm describing with such piercing clarity made the 64-bit installer write a new MBR and/or set the PATA drive as boot (? - I'm over my head here), with the result that I get different NT boot screens depending on whether or not I have a bootable CD in the drive -- regardless of whether or not I actually boot from it.
Practical result: if I have a bootable CD in the DVD drive (but don't boot from it), I get XP 64-bit 'cause it boots from PATA drive first. If I take out the CD, I get XP Pro 32-bit like I used to, booting from SATA drive first.
Further result is that neither 64-bit nor regular XP Pro boot loader routines can accurately boot into the other OS even if boot.ini is manually edited, because of BIOS disk enumeration quirks I'm guessing.
Okay this now makes little sense even to me, but if someone sees a flaw in my logic (rather than the BIOS HDD priority setting), well I'd be grateful to hear it. Otherwise I'll send it along to MSI.
You mean you have boot device 1 2 3 setup lets say
Hard Drive
CDROM
Floppy
And you leave something in the cdrom iboots to it anyways? or you have the cdrom disabled?

Similar Messages

PATA SATA connections of hd(s) for least working conflicts

Just setting up my new unit and attempting to avoid conflicts when editing movies, transfering/recording music and my daily "stuff" by not having unneeded programs messing things up. My hope is (but not certain) that upon working in a different area, I can boot to CMOS, change the boot device and thereby eliminate a lot of the stuff that loads that is not needed for work at hand. I have the ability to connect 8 devices (4 PATA & 4 SATA). Here's my plan, what problems or suggestions might anyone give me?
Primary PATA Master = Hot Swap HD, will insert my daily work programs drive and can use for data/backup with other tasks (ext bay)
Pri PATA Sl = not used
Sec PATA MA = DVD Burner (ext bay)
Sec PATA Sl = not used
3rd SATA MA = Hot Swap HD used for data with movie editing, backup and transfer of data (ext bay)
4th SATA MA = Video editing programs drive (int bay)
5th SATA MA = Music transfering and recording programs drive
6th SATA MA = Not sure yet
The 4th ext bay will have the Creative Labs Live IR Box for front connections
Will this work, or should I take a different path of just using the hot swap drives.

There is no support of hotswap for PATA chl's.
I recommend you install OS on Pri Master PATA disk and leave this attached all the time .
Same with optical drive on Sec Master PATA chl .
The swap all you need on the sata ports .
This way you also avoid Harddisk boot order to change each time from removing/adding 1'st IDE master .

How to install Windows on a SATA boot drive

Here is how to install Windows XP on a SATA boot drive. This procedure was first developed by syar2003 and has been used by many iusers ncluding myself. Although it was originally developed for Neo2 mb's and Windows XP Pro, it has general applicability to systems as well.
1. Have only the SATA drive you want to be the boot drive active in your system. Disconnect the power to all other HDD's if any.
2. Have only one optical drive active. Disconnect the power to the other opticals if any. (Best to have a burner optical as master on IDE1.)
3. Plug SATA drive into SATA 1 on the mb. (it may show us as an IDE drive somewhere down the list in BIOS. That's okl)
4. Enable appropriate SATA options in BIOS. Set boot order to floppy, cd, SATA drive. Set boot priority to SATA drive.
5. Partition and format the SATA HDD using the utilites CD that came with the SATA drive. (If you don't have an HDD utilities disk, download one from the website of your HDD manufacturer.)
6. Run Windows setup. No need to load drivers at the F6 promt unless you are planning to do a RAID configuration.
7. Windows XP should install without incident.
8. After you are up and running, plug the power back into your other HDD and optical drives if any.
If you have a board older than the K8 series, it may be necessary to load the SATA drivers at the F6 prompt. If the above procedure does not work, than try it again loading the SATA drivers.
If this procedure does not work for you, it is likely that your particular SATA HDD has some compatablity problem with Windows setup and/or your motherboard. The solution to this is to try another SATA drive. In general, most failures using this procedure have been traced to certain WD, Seagate and Hitachi SATA drivers of smaller capacities. Fewer problems seem to have occured with Maxtor HDD's.

Kaplan, from an earlier post of mine regarding sata2 hdds - I have them plugged into the sata1&2 ports, installed the nvidia raid first and then installed winxp (in both raid 0 and raid 1). My bios is 3.1 and its a known problem that bios 3.3 & 3.4 have nvidia raid problems but seems to be fixed in the beta bios 3.53:
I just purchased 2 hitachi deskstar sata2 80gb hdds ($60 each at zzf) and the interesting thing about them is that you have to "enable" sata2. I have been testing the performance of sata1, sata2, raid1 and raid0 and the results are below.
The drives themselves are factory default set at sata1. Since I purchased OEM, no software or instructions were included. I had to go to the hitachi website download section to download a dos based program (the features program) to enable sata2. After enabling the hdds to sata2, they were recognized in winxp in the nforce ADMA controller device driver and the screen reads with the primary channel as Serial ATA Generation 2 - 3G...and all 4 boxes below it are checked (the boxes enable bios select xfer mode, enable read caching, enable write caching and enable command queuing are checked). An interesting thing about the sata2 spec is that all sata2 hdds must come standard with NCQ...its not advertised on these 80 gb hdds on the hitachi website (unlike the larger hitachi sata2 hdds) but its a standard sata2 spec and these 80gb hitachi hdds are recoginized in winxp as sata2.
The other interesting feature about the hitachi sata2 hdds is setting them up to operate in an adjustable "performance" to "silence" mode. The hdds are default set at high perfromance but you can manually lower the performance to increase the silence of the hdds which is fully adjustable to your liking. I tested the highest silence/lowest performance setting and you cannot hear the hard drive at all.
Testing - I tested the 2 hitachi sata2 deskstars with the first result in sata1 mode, the second in sata2 mode, the third in raid1 mode and the fourth in raid0 mode.
First, a significant increase in raid0 over sata1, sata2 and raid1 with sequential reads and writes (PC Wizard).
Write: 28mb/s vs 29mb/s vs 27mb/s vs 53mb/s
Read: 45mb/s vs 46mb/s vs 43mb/s vs 83mb/s
Second, significant increase in sata 2, raid 1 & raid 0 over sata1 with buffered reads and writes (PC Wizard).
Write: 104mb/s vs 176mb/s vs 165mb/s vs 266mb/s
Read: 123mb/s vs 200mb/s vs 200mb/s vs 293mb/s
Third, significant increase in sata 2, raid 1 & raid 0 over sata1 with burst reads (HD Tach).
Burst Read: 133mb/s vs 225mb/s vs 219mb/s vs 334 mb/s
It is interesting to note that raid1 is better than sata1 but marginally slower in all tests over sata2. Raid0 is significantly faster on all tests.

Having difficulty in Win 8.1 changing boot order drive at the Bios level

My desktop computer has 32GB of DDR3-1600Mhz Memory plus a 128GB SSD boot drive "C" and 2 2TB SATA drives and finally a 1TB Sata drive.
My problem is that the 128GB SSD drive is maxed out space wise. I want to change the boot drive to the 1TB drive, but when I go into the Bios, and slect "Boot Order" it only lists two CD Rom drives and "Windows Boot Manager". If i go out to look at available drives, it shows all my drives. How the heck can I select the 1TB drive to become the boot drive if its not even listed under "Boot Drives"?
Using disk partitioning software, it advises that before copying everything over from the boot SSD drive to the new 1 TB drive, I should change the boot drive so that when it starts up again, it will go directly to the correct drive.
Thanks so much,
Ken

That is impressive for a OEM. However, I think it is probably not a good idea to try to make a different drive the boot drive. Typically with a unit set up like that, the SSD is only used for essentially the OS and special programs that need the extra speed of the SSD. Then use the other drives for data and nonessential ( for speed ) software. About the only advice I can give is to reassess the way software is installed to get some things off the SSD or replace the SSD with a larger capacity unit. I think switching boot drives will be a nightmare you will not enjoy.
{---------- Please click the "Thumbs Up" to say thanks for helping.
Please click "Accept As Solution" if my help has solved your problem. ----------}
This is a user supported forum. I am a volunteer and I do not work for HP.

Gaming 5 mixed legacy and uefi boot order problem

Hi,
I've got an issue with my gamin 5 mainboard regarding uefi/legacy boot order.
System setup:
. M.2 SSD (recognized as pci-e device) with a working windows 7 o.s., bootable from uefi bios.
. Normal hard drive on SATA port 1
. cd/dvd/blu-ray burner on SATA port 3 (from here on calling it the 'dvd drive')
I've tried to boot from a backup program's emergency cd to make a drive image of my ssd's O.S. partition, but the uefi cd/dvd boot option doesn't recognize the disc as being bootable. Setting it to legacy cd/dvd worked fine so that's probably because disc isn't uefi compatible. So, for that reason I've enabled the 'legacy + uefi' mode and added the legacy cd/dvd option to the top of the boot order list. Problem is, the system doesn't want to boot from the SSD anymore.
Here are some things I've tried:
When I set the boot order to: 1) uefi cd/dvd, 2) uefi windows boot manager, and NO disc in the dvd drive, the system boots from the SSD.
This is correct.
When I set the boot order to: 1) uefi cd/dvd, 2) uefi windows boot manager, and a non-uefi disc in the dvd drive, the system also boots from the SSD.
I think this is correct too because legacy cd/dvd is required to boot a legacy disc, right?
When I set the boot order to: 1) legacy cd/dvd, 2) uefi windows boot manager, and there is NO disc in the dvd drive, the system won't boot at all. Saying: "reboot and select proper boot device or insert boot media in selected boot device and press a key".
If I put a non-uefi disc in the dvd drive, the system boots from the dvd. The backup software also recognized all devices, including the SSD.
And if I go to the bios boot menu (F11), I can select the uefi windows boot manager and the system correctly boots into the O.S.
In 'the old days' , having a boot order like that, the system would skip an empty dvd drive and continue on to the next item in the boot priority list. Somehow, this system does not.
What am I doing wrong here?
I do have an old bios though. v1.2. Although looking at the descriptions of the newer bios versions, I don't see any mention regarding this issue.

I don't have an answer for you, I too wonder why the bios doesn't just skip a bootable device if it's empty.
I had to use a UEFI USB key to update bios and figured to leave it as the first boot after updating for further updates and I received the same message so had to move the UEFI USB back down the line.
Not the same as the old days Bios I guess.
When it's looking for the boot device it needs to see it or else.

Boot order problem

I have an msi k8n neo2 motherboard.
My two hard drives are, a western digital raptor (sata), which is my boot drive, and an ata western digital 160gb drive, for my music and movie projects.
I am running xp with sp2.
My problem is, when my media drive is plugged in to the motherboard, the computer cannot find a bootable drive. In bios, the hard drive boot order has the raptor above the ata drive. I’ve tried using both sata controllers, and having the media drive plugged into both ide ports. The media drives jumper is set to slave.
Any help would be appreciated.

With SATA you don't have to think about Master/Slave settings because they're essentially not there. Technically, every SATA slot is a master but it's not the same thing as the ATA hard drive.
In short, your SATA drive doesn't count as primary master on the IDE chain. Set your jumper to master on the ATA drive.
I have my system set up this way to dual-boot between Windows x32 on RAID and Windows x64 on the ATA drive. No problems.
I know where the confusion is coming in. The operating system doesn't have to be on the Primary Master ATA drive if you have it on a SATA drive. You do, however, need a Primary Master. Well, you probably don't NEED one, but it's a good idea.

BIOS Changed Boot Order By Itself

I have a Pavilion H8-1360t. When I got it in March I installed a Samsung SSD. I copied the original Hard Drive to the SSD and made the SSD my boot drive. I also swapped the SATA ports becasue the HDD was on the high speed on. For the next 4 months I've been booting every morning and shutting down at night with no problems. The SSD boots quick and again, no problems. The SSD was my C drive and the original HDD was now my F. I only used it for Ghost backups of the C drive. I also Ghost to an external USB3 drive.
This morning when I booted I noticed that all my icons were missing as was all my data and all my programs I had installed. AFter some research I found, in the Computer display of my system, that my SSD was now the F drive and the original HDD was now my C drive. So I was booting using the original HDD that came with the system.
I tried to figure out how to tell the BIOS to boot from the SSD as it had been, but I cannot figure out which drive in the display list is it and besides that I want it to do that by default. I'd also like to know how or why the PC decided to reassign thedrive letters and boot from the HDD now.
HP refuses to help saying that since I have user installed devices they do not have the tools to help. They also cannot tell me how to get the Boot Order changed. But even if I could do that, and I've tried going into BIOS setup and Boot Priority, I cannot get it to boot using the SSD. HP suggested I go to some third party. But there's got to be a solution I can do. My last choice would be to copy the entire SSD to the HDD (the SSD id only 500GB and the HDD is a Terrabyte). I assume then that when it would boot from the HDD the data I copied over to it (using Ghost) would make it look then like the SSD did. My loss would be speed but at least I'd have critical data that I now cannot access.
I am really up the creek right now Any ideas?
Thanks

I took the PC to Fry's. They think there's a problem with the SSD. Even though I am able to see it and to move data off of it, there is some problem during boot that tells W7 and BIOS that is cannot boot and that is what is causing the system to then look for another boot drive. It then finds the hard drive, which came with the system and is connected, and is bootable, and thus it boots from that drive and also remaps the drive letters, effectively swapping the C and F between the SSD and HDD.
Now I am trying to move all my data to the HDD, install Office and other programs, and just boot to the HDD until I can get the SSD examined for problems and a new one, if necessary, put in.
PC's are such a joy.

PATA + SATA!!!!!!!!!!!

Ok.. I have the following system specs..
MSI Neo 2 -LS
Intel Pentium 4 2.8 ghz 800mhz
Corsair TWINX 512mb (256mb x 2) 3200mhz
Volcano 7+ Heatsink & Fan
Western Digital Raptor SATA
Western Digital Special Edition 120 gig
Western Digital Special Edition 120 gig
LiteOn 52x24x52 CD Burner
LiteOn 16x DVD-Rom
Prolink FX5200 128mb
Sound Blaster Audigy 2
US Robotics Modem
With 4 System Fans
Antec TruePower 550Watt
Ok I'm trying to get the following configuration Achieved..
Boot-up Hard Drive
Western Digital Raptor SATA
Storage Drives
Western Digital Special Edition 120 gig
Western Digital Special Edition 120 gig
CD ROMs
LiteOn 52x24x52 CD Burner
LiteOn 16x DVD-Rom
I've tried putting SATA in with Both Hard Drives on Master and CD-Rom's on Slave on IDE 1 and IDE 2.. I will not detect all the drives.. It will leave out what ever drive that is wants to.. I've set it to PATA + SATA and SATA 1 Channel..
I've also tried both hard drive on the same channel as in Master/Slave of IDE 1 and CD-Rom's on IDE 2.. Nothing that I do can work.. I know how to build system this board has some picky ways of doing things.. I still can't get into Ultra Turbo or Turbo mode either.. My DRAM voltage is up to 2.65 like everyone recommends. What am I don't wrong here..
Techman1013

since techman is using Neo2-LS, would the option to set "As Raid" be available? Cuz the LS version of the mobo doesnt come with the ICH5R rather it comes with the ICH5 chipset.
Techman,
Try settin the On-Chip ATA(s) Operate Mode to Native, this will allow you to have up to 6 devices connected, 2 SATA's and 4 PATA's, instead of 4 with Legacy Mode
ATA Configuration - S-ATA only (since you want the SATA drive the boot drive, i believe this option will allow you to set your SATA drive as Primary instead of Third w/ "P-ATA only)
P-ATA Keep Enabled - YES
P-ATA Channel Selection - Both
As for the RAID option, since you got the LS version of the mobo, I dont think it will let you change it to "Yes".

BiosConfigUtility BOOT ORder issues.

I've read posts from years ago, and have yet to see a resolution. But when using the BiosConfigUtility to set the boot order I am unable to set sub boot orders.
Example I get:
Legacy Boot Order
   Hard Drive
   ATAPI CD-ROM Drive
   USB Floppy/CD
When I need to set:
Legacy Boot Order
   Hard Drive
USB Hard Drive
SATA0
ATAPI CD-ROM Drive
   USB Floppy/CD
Has there been any work around, or update to this issue?
P.S. This thread has been moved from Business PCs - Compaq, Elite, Pro to HP PC Client Management. - Hp Forum Moderator

Hi Folks, I came across this thread as I was facing the very same issue with a HP EliteDesk 800 G1 model. We are introducing a USB MDT solution and having the USB boot before the Hard Drive (SATA0) when imaging this model isn't ideal and can cause a bit of confusion with Technicians building for the first time. Its quite easy to forget and walk away and think the deployment will complete only to see it boot back into the MDT WINPE environment. Anyways much like yourselfs I couldn't deal with the sub menu for the Hard Drive Boot order. tried many things. What seemed to work for me is as follows. Get the config file using the BiosConfigUtilty.exe /GetConfig:config.txt Open up the config.txt and change the Hard Drive Entry to include the following: Hard Drive (SATA1 or USB Hard Drive)orHard Drive (SATA1) The values are what you see when you do a F9 boot, my test machine Hard Drive was being identified as SATA1 and the USB value as USB Hard Drive. Your system may identify the Hard Drive as SATA0 so just adjust as necessary. The first option suits me as I need to initially boot to a USB flash drive, although as I am testing as I write it does't seem to make much of a difference. By appending the (SATA1) entry or whatever sata port your device is using, seems to force the BIOS to use the Proper Hard Drive as the first device rather than using the USB. Once happy apply the settingBiosConfigUtilty.exe /SetConfig:config.txt and reboot. Hopefully this will ammend the boot order. Just as side note, if you reget the config you will not see the settings that you added. It does work but keep the ammended file for future use. I am hoping to incorporate this into a MDT task sequence within the WINPE phase so that when the pc reboots it goes straight to the Hard Drive. Cheers, Ewen.

Z87-G45 Gaming boot order changes itself causing boot problems

Okay so I got this new motherboard and everything worked fine yesterday.
But today when I tried to boot it couldn't find the boot.mgr so I looked from were
it tried to boot and it was my SSD were my games are located and it should be my SSD
where my system is installed, so I changed it and it booted right up with no problems.
then I just maked sure everything is okay so I restarted my pc and same thing only then
when I wanted to change the boot order my System SSD was gone So i restarted and
there it was again, so again I changed it and it booted right up and again I wanted to make sure it
would boot again when I restarted and.. well no it didn't and now it was my HDD which was my first boot
order so I have no idea what this mean and how I can solve this

Did you install your windows system using UEFI method or just the standard legacy mode?
If standard legacy mode then your first boot should be set to your HDD, and if you still can't get in the Windows,
try to plug the SATA cable and connect it again, also make sure that it is not your SSD itself that have problem,
cause i got Samsung 840 SSD before and it's causing many weird issues, sometimes even don't let me go to windows mode https://forum-en.msi.com/Smileys/msi/undecided.gif

BootCamp drivers crash Windows 7, slow startup, boot order?, backup drive

I have 3 issues that may be related or possibly not related to each other. I use an iMac (currently with Leopard 10.5.8 on a completely clean installation of both Leopard and Windows 7 on a freshly formatted and partitioned drive).
Issues:
1. Before reformatting and installing Leopard and Windows 7, I tried to install Snow Leopard and then Snow Leopard Bootcamp drivers into Windows 7. This crashed Windows 7.
2. Slow startup of Windows 7 - Drivers needed?
3. Firewire backup drive never re-mounts after using WIndows and then going back to OS X.
*Details of issues*:
In the past, before I completely re-installed Leopard 10.5.8 with a new Windows 7, with this same pair of operating systems, I always had a slow startup of Windows 7 on Boot Camp. Sometimes this would take up to 6 minutes to completely open Windows 7. The "Starting Windows" message would appear usually soon, but it would tale a very long time before the Windows logo Flag would appear. The slow startup still continues, even after a complete reinstallation of these on a freshly re-formatted and re-partitioned hard drive (This re-installation was done for reasons shown below).
For a long while I have thought that because I had never installed any BootCamp drivers into Windows 7, then it might start better if I were to install the BootCamp drivers from an installation disk. Thus when I the other day briefly upgraded to Snow Leopard, this time I went ahead while operating under Windows 7 to install into my already existing Windows 7 the set of Boot Camp drivers from the Snow Leopard installation disk. The installation seemed to go well, but it then hung up and never continued when it tried to install the Intel chipset driver. An an hour had passed with no further progress. Thus I force-shutdown the computer, and Windows then never opened until I restarted under safe mode. After that when I would restart Windows 7 "normally", I found also that the Apple wireless keyboard under BootCamp no longer was recognized. The "normal" slow booting of Windows 7 still remained.
Because of I was not sure just what all might have been messed up, and because I am waiting for new versions of several programs that I use to be made as versions compatible with Snow Leopard, I reformatted the complete drive (Both partitions were merged into 1), and then I reinstalled Leopard on a freshly prepared drive, followed by newly installing Windows 7 on a new BootCamp partition. Both systems were fresh installs on a freshly prepared drive and partitions. These were not from clones of the previous installations. This time I did not try to install any drivers from the Leopard disk. The slow booting of Windows 7 continues.
Things I have suspected might cause the slow booting:
1. Boot order of the Windows partition may be set to look for a CD-ROM before booting from the Windows 7 on the BootCamp Partition. To solve this, I have tried to open the BIOS on startup of Windows 7 in order to set the boot order. I am not sure which function key to press, but in trying several, I have gotten a DOS screen that shows Windows 7 as an option, but nothing else. When I select "Advanced", I get a list that includes "Safe Mode", "Boot Logging", and other items, but not anything for boot order.
2. The drivers for BootCamp might not yet be made for Windows 7, and I need to wait until these are so that these can be installed. After such, then maybe the slow startup might be fixed?
3. Possibly my Firewire backup drive interferes (permanently?) with the Windows startup process, because after I use Windows and then go back to OS X, the backup drive (Maxtor OneTouch III firewire drive) will not load on the MacIntosh desktop until I unplug the firewire from both the computer and the Maxtor drive and unplug the power cable to the backup drive, followed by replugging all of this in. (Note: The backup drive is formatted for Macintosh and is never seen as a drive in "My Computer" or in "Network Places" when I operate Windows 7).
Are you able to help/ Thank you.
Sincerely,
Wilson

Extra comments;
I also tried the following, which did not fix the startup (*Once up, Windows works well!*):
1. Checked for file and disk errors (ckdsk?? on startup).
2. Purged temporary internet and other temporary files (using internet options and disk cleanup utilities)
3. Cleared out Prefetch files.
4. Emptied trash.
5. Under "msconfig", I found 4 items there as startup items. I disabled Adobe Reader and Quicktime helpers, leaving only thus 2 startup items of the 4 enabled (Bulldog and some Microsoft thing).
6. Defragmented.
No better results.
Sincerely,
Wilson

Changing Boot Order on Dual Boot Windows 8 and Ubuntu

Hi there,
Recently got a HP Pavilion g6 2213sa which came with Windows 8 (spit!) and this disgusting UEFI BIOS replacement (double spit!).
Anyway, I need to dual boot Ubuntu on my system, so I installed Ubuntu. Normally, on a non UEFI system, a "Grub" bootloader installed by Linux would take over the startup process, and allow you to choose between either Windows 8 or Ubuntu on startup.
However, on this computer, startup is just booting straight to Windows 8 despite the fact that Ubuntu and Grub IS installed.
Now, upon startup, if I press F9, then I get to change the boot-device on a one-time basis. I can either select "OS Boot Manager", which loads Windows 8, or "Ubuntu" which loads the Grub bootloader which allows me to select Windows 8 or Ubuntu.
However, when I press F10 to enter the Bios Setup with the intention of changing the boot order permanently, the Ubuntu option isn't there. Instead it has OS Manager, USB Disk, CD Rom, USB CD Rom and Network Card.
Thanks, HP for, the crappily designed BIOS.
Anyway, can anyone PLEASE provide me a way of changing the boot order so that GRUB is loaded first and NOT this crap Windows 8 rubbish (that I would happily bin if I didn't need it for work).

There is the same problem in HP 2000 laptops (in my case specifically, HP 2000-2D22DX). I did some investigation using trial and error, and this is what I found out:
There is some sort of a "recovery feature" or so that on every boot sets the very first UEFI load option to point to one of the two locations, in this order:
\EFI\Microsoft\Boot\bootmgfw.efi
\EFI\Boot\bootx64.efi
This option is displayed as "OS boot Manager" (for the first path) and something akin to "UEFI partition" for the second path, completely ignoring the actual name given to it (when you look at the EFI variables through efibootmgr, you can see that what is displayed as "OS boot Manager" actually is set to the name "Windows Boot Manager"; why anyone would do such renaming is beyond me). If you try to change the boot order so that this slot isn't the first, the UEFI will overwrite the BootOrder variable on next boot and reset it to point to "OS boot Manager" anyway.
By default, both of the paths above contain the same Microsoft bootloader (if you check the md5sum of both, you'll see they match).
So, until HP releases an updated UEFI that allows turning this "feature" off or rearranging boot options through the F10 UEFI setup, this is what you can do to get dual boot with the least amount of hackiness:
In Windows, mount the UEFI partition (mountvol S: /S mounts it as the S: drive) and copy the file \EFI\Microsoft\Boot\bootmgfw.efi to use some other name (for example, I copied it to "\EFI\Microsoft\Boot\bootmgfw.efi~", but you can change the name to anything else).
In the Windows command prompt, update the Windows UEFI entry to point to the new name: bcdedit /set {bootmgr} path \EFI\Microsoft\Boot\bootmgfw.efi~ (adapt to your set name accordingly).
Optionally, change the name of the Windows boot loader so that you would be certain that it points to the new file location: bcdedit /set {bootmgr} description "Fixed Windows path"
Install the other OS. In my case the bootloader was installed into \EFI\opensuse\grubx64.efi.
Delete the two files, \EFI\Microsoft\Boot\bootmgfw.efi and \EFI\Boot\bootx64.efi.
Use efibootmgr to delete the "OS boot Manager" entry: sudo efibootmgr -b 0000 -B
Set the new OS bootloader to be the default bootloader by using efibootmgr with the -o option. In my case, I had an entry called "opensuse" in slot Boot0001 and the updated path Windows entry in slot Boot0002, so I had to do sudo efibootmgr -o 0001,0002
Update GRUB to point the Windows entry to your renamed file (you'll have to create a new file in /etc/grub.d and rerun grub-mkconfig).
And that's it, now the UEFI will boot GRUB by default (it won't regenerate the "OS boot Manager" entry since it won't be able to find either of the two hardcoded paths and will "fall back" to properly reading the BootOrder variable), and the F9 menu will still allow choosing to boot Windows directly.

How to change the boot order? Frustrated!!!

Guys, I feel stupid. A frustrating place to be. Please bear with me if I am doing something stupid. I added a mSata second drive. Works fine. Lenovo X220, Bios 1.16. PC boots from the new drive. I don't want an operating system on the new drive, just want it for storage. So I entered the bios by pushing the blue thinkvantage button and can't find a way to permanently change boot order. I hit F12 to TEMPORARILY change boot order, every time I boot the PC. Major PAIN! I tried to enter the Intel Boot Extension Management Engine, but it needs a password and I don't have a password. Any thoughts?
Solved!
Go to Solution.

That is not the boot list. Select >Boot to get the boot list. You're looking in the wrong place.
Z.
[edit] "click"
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Regarding query or code to get Bios Boot Order list display in windows

hi ,
I wAnyone can help me that i want to display bios boot order list in windows system without going to Bios Setup.So is there any query or command to get boot order list in windows system which is applicable to any company like hp,compaq,dell,lenova.
Thanks in Advance,
Isha Priya

In 64 bit with UEIF boot it is BCDEdit.
On other systems it is not possible.
There is no script for this.
bcdedit /?
¯\_(ツ)_/¯

Change the boot order of an RHEL ESXi server

How to programmatically change the boot order of an RHEL ESXi server?

Broken Arrow wrote:
Harold asked a perfectly reasonable and necessary question, but how is that a Solution ???
I believe it is called the Socratic Method.
Sea-Story time
I had the privledge of working for Ron Davis when he managed the Allegheny District of DEC. He was an ex-WO4 (Highest possilbe rank for non-commisioned officer in US Navy, required act of congress to confirm).
Ron never answered any question I ever saw presented to him. I remember a group of managers in a frenzy over some issue running to him to to see what he thought. He asked them a series of questions that lead them to the solution and soon they were smiling and slapping each other on the back as they walked away.
Who is that has a signature that read "it is the questions that guide us"?
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

PATA/SATA boot order anomaly?

Similar Messages

Maybe you are looking for