First Boot Device

To be able to use the key "Selecting the First Boot Device", in what order shall I install Win98 and WinXP?
My wish is to install Win98 on one hard disk the ATA 100 IDE1 channel, while the XP should be installed on one of the SATA connectors (Intel or Promise, depending on what is recommended), later to be mirrored.
Advice please

You should install 98 first, and then XP. Not sure how multibooting works over SATA and IDE hard drives though as I ahven't tried it myself.

Similar Messages

Problem in formatting ,scan disk i need to set cd rom as first boot device

hi,
For formatting ,scan disk i need to set cd rom as first boot device
But whenever i do it from manager and restart the machine It takes long to get back the console of the machine.
By the time machine boot's up, its from hard disk.
How would i avoid such situation?
Please advice....

hi
could you describe more precisely where are you?
do you mean BIOS boot settings? if yes, you choose CDROM as first, boot and your systems start from CD disk.
what operating system do you use?
what console do you mean?

"Reboot and select a proper boot device..." error on a p6214y

i have this problem where my computer boots and hangs at the HP blue screen mostly ... sometimes it wont and then go through to the "Reboot and select a proper boot device or insert boot media in selected boot device and press any key" message....
and sometimes if i leave the computer alone for weeks... it will boot into windows. and immediately go into slow response. then the process repeats from atop...
but then i connect my hard drive to another CPU, and it logs in fine ... so i know its not the HD...
i have taken out the battery, checked the cables .... is there something we dont know about this issue???

The Boot tab of the BIOS Setup shows the following typical items on the screen. (Your system might be different and not include all items):
Figure 8: Example of a Boot screen
Boot-time Diagnostic screen
Boot Device Priority (The order for the boot process. For example, removable devices, DVD optical drive, and hard disk drive).
I would recommend turning on the computer and immediately tapping F10. When Bios pulls up use your arrow keys to move right until you highlight the BOOT tab. Press enter. Scroll down and select boot device priority by pressing enter. Make sure the HDD is listed as the first boot device. Hope this helps!
While I am a HP employee, I am not an expert on all our products. When I offer advice, I'm not speaking for HP.
Make it easier for other people to find solutions, by marking my answer “Accept as Solution” if it solves your problem.
***Click on “Kudos” STAR to say thanks!***

Fresh install of Server 2012 R2 causes inaccessible boot device on first Reboot

Hello Everyone,
Doing a fresh install of Windows Server 2012 R2 on a SuperMicro X9DRT-HF+ motherboard based server. The server is using iSCSI boot, setup detects the iSCSI disk and copies its files, finishes the "Getting files ready for installation" "Installing
Updates" phase, reboots, takes a while and eventually gives a Blue screen with Inaccessible Boot Device error. I have tried some changing options in the BIOS, I've had Nimble (storage array) support on the phone and they confirmed the setup is correct
but for some reason after the first reboot Windows can no longer find its install files and gives a BSOD.
Additional Information:
Server: SuperMicro X9DRT-HF+ (no internal disk)
Storage: iSCSI disk provided from Nimble CS220 Array
Windows 2008 R2 Server installation will proceed without any problems.
I checked the \Windows\Panther\Setupact.log / CBS.log file and there doesn't seem to be anything indicating a problem.
I have googled a number of times to find solutions but most articles reference a similar problem after installing a particular KB (which shouldn't be the case here). Need some help :)

Hey Tim,
Thanks for your reply, since the start of this post I have also installed MDT to try a different approach to installing the OS. Using MDT I have injected the Intel I350 driver into the installation so it should be restarting with the driver loaded.
The odd thing is that when the server reboots the Windows startup screen loads for about 4 minutes before it gives the INACCESSIBLE_BOOT_DEVICE error. This would indicate to me that it sees the disk and tries to boot from it but then something goes wrong.
Other than the \Windows\Panther location is there another place I should be looking for log files during this part of the Windows install? I have reviewed all the locations listed under the TechNet library article "hh824819" (I can't post
a link to the article but a google search brings it up) but I can't seem to find a log of when the server crashes what it is doing at that point.

Change Boot Device to Use CD First - Win7 - HP1360t

In trying to solve another problem with my PC I loaded my Ghost CD so that on reboot I could use Ghost to revert the system. But the system never went to the CD drive and instead booted normally. As it turned out the boot worked and somehow my origianl problem was solved. But I still need to make sure the CD device is tried first.
I've gone into the BIOS and I notice that the CD drive is 1st in the list under the Legacy list and I can move the arrow up and down, and hit enter all I want, but nothing indicates that the CD is the first drive to try on boot.
What am I doing wrong, or not understanding?

When requesting assistance, please provide the complete model name and/or product number of the HP computer in question. HP/Compaq makes thousands of models of computers that are all different. Without this information it may be difficult or impossible to assist you in resolving your issue.
"HP1360t" doesn't appear to be a valid model name or product number. Assuming you mean you have a HP Pavilion HPE h8-1360t CTO Desktop Computer and it is has a UEFI compatible BIOS, the Legacy boot options will always occur after the UEFI boot options. For example...
UEFI - Hard Drive
UEFI - Internal CD/DVD
Legacy - Internal CD/DVD
Legacy - Hard Drive
As long as the UEFI Hard Drive is connected and functional, it will boot ahead of any Legacy device. If you move the UEFI CD/DVD above the UEFI Hard Drive and the Ghost CD is UEFI boot compliant, it may be possible to get it to boot before the Hard Drive.Additionally, you should be able to tap "ESC" or "F9" immediately after turning on your computer and directly select at boot device from the menu. This method should allow you to boot the "Ghost CD" regardless of it being UEFI or Legacy.
Please send KUDOs
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

OSD Failure - Windows 7 - Blue Screen on First Boot in Full OS

Hi,
We are experiencing a really strange problem with our OSD which is hard to pin down. Our setup is SCCM 2012 R2 with 4 PXE enabled DP's (VMWare VMs) across 2 data centers and on seperate hosts and we are delivering Windows 7 (32 and 64) with recaptured WIM
files. Ouor deployments work fine for around a week and then they suddenly start experiencing a reboot look and blue screening at the first boot into the full OS.
This occurs on multiple different physical machines and we inject driver packages for different builds with WMI filters on motherboard as is common. The really weird part is that this will work for days then stop working. The only workaround we have is to
recapture the WIM file (we have a build and capture task sequence for this) and then it works again, even though the content and drivers are exactly the same from the same B+C task sequence. Even the windows updates are the same with no new ones. It doesn't
seem to be the drivers themselves but rather the process of DISM injecting them offline in windows PE which appears to break the registry. The last thing we see before blue screen is "Updating registry" in windows 7 boot.
These are the things we have tried are...
- Recapturing the WIM (works for around a week but not a fixed period)
- Host the WIM on a physical DP (to rule out VMWare) with only the WIM and a single driver package. Again this worked fine for a week or so.
- Built several different physical machines. All fine but when this stops, it stops for all of them
- If we remove all drivers but the LAN driver it can work but our testing has ruled out a specific bad driver as we have used different models of machine and if it was, then it would never work.
- We have set the TFTP block size to default of 1024 (we had it higher as 8192) to rule out the boot image being corrupted on download. It made no difference other than being a lot slower.
- Compared MD5 hashes for the WIM to rule out corruption.
- Removed and redistributed the WIM and drivers to different DP's (that it had never been on before)
The DISM.log on a failed device shows entries like
CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
Any advice would be greatly appreciated. This question on
Dell's forum sounds very similar.
What we are really struggling with is why would the same WIM, with the same driver package, from the same distribution point, to the same physical machine, work every day for a week the permanently break? Aaargh!
Thanks everyone,
Shaun

Hi,
Have this problem been resolved? How?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

HP Pavilion g6-2330dx. "No Boot Device. Insert boot disk and press any key" Memory test failed

Hi. So I am trying to help a friend with her laptop. It's a HP Pavilion g6-2330dx.
Product #: D1C01UA#ABA
Serial #: [Personal Information Removed]
Windows 8
ADATA 4GB RAM
Toshiba 640GB HDD from the looks of it.
The laptop is unable to boot into Windows, so I suspect the hard drive. But I ran the hard drive test and it passed all the tests. The SMART test and both the short and long test. I ran the tests multiple times and it passed each time. I tried reseating the hard drive and still no go. I also removed the HDD and connected it to my desktop PC to see if it detects and it did. Ran the Windows 7 own HDD test and it passed.
Currently, there doesnt seem to be any operating system at all on the HDD. When I check, there is a C: drive of ~90GB partition that is ~90GB free, but inside there are Windows files/folders. There is also a D: drive Recovery partition that says ~26GB with only ~2GB free, but when I go inside there's only ~350MB worth of data.
So then I ran the memory test (in BIOS) and it failed immediately. I reseated the RAM module. I tried the other slot. It still failed. So is it safe to say the memory is the cause of this problem?
Pressing the F11 key that is supposed to take me to the System Recovery only leads me back to the black screen with "No Boot Device. Insert boot disk and press any key"
I even tried to install Windows 7 to see if it'll work. I was able to get the laptop to boot/read off the Windows 7. But when I click to install, it asks for a boot device driver or something like that.
My friend doesn't have the recovery disk either. I guess she lost it.
Anyway, is it as simple as replacing the memory or could it actually be the HDD (even though it passes)?
EDIT: This is what the System Log in BIOS says
0021           Time: 10/13/2014
03F0           Time: 10/13/2014
03F0           Time: 10/13/2014
The date was the first time I ran the tests. I havent received those numbers (error codes?) since.
EDIT: Just for kicks, I ran Memtest 2.11 just now (forgot I had the disc) and it immediately went red with thousands of errors, hah.

Hi bghs,
Welcome to the HP Forums!
It is a fantastic place to find answers and information.
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I understand that you were unable to boot into Windows, and you suspected the hard drive and tested it, but it passed both short and long test. With that being said and the fact that it also passed leads me to believe the hard drive is fine.
You tested the memory and it failed. You tried reseating and swapping slots but they still failed the test.
I would test each card individual with the memtest to determine if it is just one or both cards that have an issue.
When you installed it in another computer, you did see the recovery partition. Once the memory issue is resolved, if you are still unable to boot into Windows, I suggest you do a recovery with the minimized image.   Here is a link to Performing an HP System Recovery (Windows 8) to assist you with that process.
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Can't detect boot device after factory format to new HDD

First off, I have an HP Pavilion G6 that I purchased in December 2012. Yesterday I decided to get a new HDD to upgrade it and start fresh. It's a 1TB SSD+HDD hybrid by Seagate. It installed without a hitch, and I used my HP recovery CDs to do a factory format of the disk.
It finishes, reboots, but instead of rebooting to the HP Windows 8 setup screens, it goes to what looks like Windows 8 safe mode with a box containing the date, time, and it says something along the lines of "HP diagnostics driver installation" with an OK. Clicking that or not makes it disappear, and there's a command prompt bar at the bottom left hand corner of the screen.
The screen changes to an HP screen that begins to install drivers. It finishes, and reboots to a black screen that says "no boot device detected, please install OS."
I ran a check of the drive and it's fine. I swapped my regular drive back in, and it loaded up fine. In fact that's what I'm using right now to type this.
What could be the problem here? The boot order was never changed in the BIOs. If it were the connector failing I doubt it would load the drive that's always been in the computer. Loading up the newly formatted drive in an external enclosure shows that Windows 8 is indeed on it, but on a 93GB partition even though the drive is 1TB.
I'm at a total dead end here and no one seems to know what to do!
This question was solved.
View Solution.

Hello @kylemcauliffe15,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I have read your post on how your notebook is displaying an error message that your new SSD is not detected as a bootable device after a factory format. I would be happy to help you, but first I would encourage you to post your product number for your computer. Below is a is an HP Support document that will demonstrate how to find your computer's product number. In addition, it will also help if you indicate which operating system you are using; and whether your operating system is 32 or 64 bit. The more information you can provide, the better!
How Do I Find My Model Number or Product Number?
Which Windows operating system am I running?
Is the Windows Version on My Computer 32-bit or 64-bit?
Please re-post with the necessary information, this way I will be able to research this further for you. I look forward to your reply!
Cheers!
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Boot Device Not Found. Please install an operating system on your hard drive. Hard Disk - (3F0)

Model HP-G72-257CL. Purchased new Operating System & Hard Drive from HP. Error message Boot Device Not Found popped up after attempting to installing hard driveon laptop

RonDNor wrote:
Model HP-G72-257CL. Purchased new Operating System & Hard Drive from HP. Error message Boot Device Not Found popped up after attempting to installing hard driveon laptop
Hi,
Try this first:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01443463&lc=en&dlc=en&cc=us&product=4308966#N16...
Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
Testing - HP 15-p000
HP Touchpad provided by HP
Currently on Debian Wheeze
*Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

Mac Mini first boot and bluetooth keyboard not recognised

Hi Apple Support Community-
I have just purchased a brand new Mac Mini and App Wireless Keyboard. Unfortunately upon first boot, the Mac Mini is requesting I connect my bluetooth keyboard by switching it on, however even though the green light flashes, after the 5 second startup acknowledgement, there is no response from the Mac Mini.
To confirm the keyboard is working, I have successfully paired it with my MacBook. I do not have a USB Keyboard or Mouse and without purchasing additional hardware, do you have any suggestions to work around this problem?
Thanks, Julian

Hi Julian,
Sometime a Mac can't pickup the connection of a bluetooth keyboard or mouse is normal. Whatever your Mac is brand new or not.
I will do the following if the brand new Mac can't pickup the bluetooth connection, but make sure the bluetooth keyboard and mouse is not yet paired with other computer, that means you have to un-pair the keyboard and mouse from your MacBook before you perform the follow step:
- Switch off the Mac
- Switch off the Keyboard and Mouse which not yet paired with other computer, remove its battery, and re-install the battery after 10 seconds
- Switch on the Keyboard and Mouse first, make sure both devices have a green light flashes (the light flashed at intervals, like a pulse **...**...sorry my poor English), that means the devices is discoverable.
- Switch on the Mac asap if all the bluetooth keyboard and mouse is ready, and let the Mac pair both device (according the screen instruction)
If the method still doesn't work, the worst case is: i'm afraid you have to connect wired keyboard and mouse to finish the Setup Assistant, and pair both bluetooth devices by Bluetooth Preferences. Once both bluetooth devices connected, disconnect wired keyboard and mouse.

Firmware 1.0.1 boot device order - efi password

Hi.
Having an "open firmware" (EFI) password set, firmware version 1.0.1 ignores the password and boots a boot cd like rEFIt boot helper. Boot CDs are always booted first without considering the so called "open firmware" password.
This is a security desaster!
What i want:
With an open firmware password set:
Always boot "Mac OS X" or "Windows" first. When holding down the "alt" key, let me choose the boot device, like a boot cd!
Please have some developer read this!
with kind regards
Thomas

Good Morning,
I'm going to type this out in English and try to translate it to Italian so pardon any mistakes on my part...
You can always verify your MacBook's BootCode version by going into Applications -> Utilities -> System Profiler and checking out...
Boot ROM Version: MB21.00A5.B07
SMC Version: 1.17f0
That should give you a good idea if you need any updates!
Hope this helps! 
David
(Thanks Google Translator)
Potete verificare sempre la versione di BootCode del vostro MacBook entrando in
Applicazioni - > programmi di utilità - > Profiler del sistema e verificare…
Versione della ROM del caricamento del sistema: MB21.00A5.B07
Versione di SMC: 1.17f0
Quello dovrebbe dargli una buona idea se avete bisogno di qualunque aggiornamenti!
Sperare che questo aiuti! 
David

Solaris 10 installation says I changed boot device when I didn't

Hello,
I'm new at Solaris 10, and have been trying to do a net install with Solaris 10 8/07 (127111-11, s10s_u4wos_12b) on
a brand new (but older version of Solaris 10, which is now wiped out) V245 Sunfire.
When it comes to setting up the disk for installation, I have tried a couple of different things, but all seem
to result in
"Warning: Different Boot Device
Because you have changed the boot device (where the root ('/')
file system will be created) from its previous location, you
must re-layout your disks to sync up file systems. "
So -- I have tried manual layout, auto layout (following is what I want) -- and the first
screen tells me that c0t0d0 IS my boot device!
Customize Disk: c0t0d0
Boot Device: c0t0d0s0
Entry: Recommended: MB Minimum: MB
================================================================================
Slice Mount Point Size (MB)
0 / 61801
1 swap 8193
2 overlap 69994
3 0
4 0
5 0
6 0
7 0
================================================================================
Capacity: 69994 MB
Allocated: 69994 MB
Free: 0 MB
Immediately after the "remote server" and next screen, it says:
Warning: CHANGING DEFAULT BOOT DEVICE
Then it suggests going back and changing the default for EEPROM -- but -- does not allow me to go back!
At this point it appears to be installing. But it just sits at the timeline screen
"Solaris Initial Install
MBytes Installed: 0.00
MBytes Remaining: 3772.80
Installing: Open Card Framework
Forever.
Where am I going wrong?
Thanks for any clues!!!
- Judy

Well, actually I don't have a console directly plugged in -- so I only have the secure console server
access, which seems to lock me into the single window mode where the installation stalls.
I left it going all weekend and it still stalls immediately when the installation is
supposed to begin (the "solaris initial install" screen with the percent completed bar at the bottom).
So I am unable to access the system (ctrl-c, ctrl-z do not seem to have any effect) other than
the installation guide interface. How do I get past this problem? Is it something to do with
when I turned off the firmware that keeps popping up the DHCP message (I'm not going to have
this machine's IP dynamically assigned)??? Is there something in the firmware that I need
to set???
Thanks again for help!
- Judy

Equium A110-233 - I need select manually the boot device from menu

In the last few days when I turn on my laptop the Toshiba screen appears but I need to manually go in and select the boot device to start windows.
(Down the bottom the message 'Press F2 for set up. Entering boot device selection menu')
Why has this started and what can I do to get it to go straight into Windows XP like it used to?

After switching your notebook ON please use F12 button and you will be able to select the first bootable device.

[SOLVED] external USB HDD fails to install arch w/boot device ERROR

I've been working on installing arch linux via an external USB harddrive (specifically seagate free agent go 320GB) for 1 week now, and everytime I failed - until TODAY! thankfully I found this post, where user Dieter@be references this link, which displays BUG ID#17231 at the top titled "Can't boot LiveCDs 2009.08 (/dev/archiso doesn't show up)". the bug report states ::
I can't boot the LiveCDs 2009.08, neither netinstall nor core.
When it tries to access /dev/archiso it shows these messages:
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
reading further thru this bug report, I found a very insightful post by Heiko Baums (cyberpatrol) where he says the following, and I quote ::
Problem found. The link /dev/archiso wasn't created.
After
ramfs$ cd /dev
ramfs$ ln -s sr0 archiso
ramfs$ exit
it continued booting correctly.
And sg was also loaded after this. ;-)
as you see, the bug report was for the CD version, not the USB version - yet, my issue with the USB bootdisk was the same, (no matter which boot disk I tried = netinstall, core, .img, .iso, etc) meaning I got the EXACT same error = "ERROR: boot device didn't show up after 30 seconds ..." ! well, I figured that I'd try one of the new fancy ISOs found @ http://build.archlinux.org/isos/ - specifically I use/used archlinux-2010.03.04-netinstall-x86_64.iso.
upon running Unetbootin from windows 7, and choose to install the ISO archlinux-2010.03.04-netinstall-x86_64.iso to my first partition on my USB harddrive (that first partition being FAT32, and had already been set as bootable previously), that completed successfully. I rebooted, and choose to boot from USB drive, the ISOlinux bootloader came up as normal, I choose DEFAULT and off it went.... sure enough, it errored out at the same place as listed in the bug report ::
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
this time though, I issued the following 2 commands ::
ln -s /dev/sdb1 /dev/archiso
exit
from there, EVERYTHING worked as it should!
to recap: the solution for me was create a symbolic link pointing /dev/archiso => to my partition which held the archlinux netinstall (which is where I told Unetbootin to install it to)! done and done. I felt this needed to be posted here, as I could not find this solution after MANY google searches, archlinux wiki searches, forum searches, etc. honestly, I think it would be prudent to have this tidbit of information added to the Install from USB stick archwiki page as a side note to those that may run into this issue.
this is not the FIRST time I have run into this problem with a USB install of archlinux, but this is the FIRST time I found a fix! thanks to all the great posts I reference here, without this information I dont think I would have been able to install archlinux on my new alienware m11x laptop.
-peace-
PS: no amount of rootdelay=XX nor pmedia=usb nor usbdelay=XX would work in my above attempts either.
Last edited by fnord0 (2010-03-12 04:54:26)

FAT16 here. Parted Magic sees my USB drive as sdd. I tried your way and surprise, surprise, it didn't work.
ln -sf /dev/sdd /dev/archiso
mount -t vfat /dev/archiso /bootmnt
mount : Invalid argument
I thought maybe you meant mount -f vfat /dev/archiso /bootmnt instead. I tried it too, it resulted in a kernel panic.
What else can I try besides installing from a IDE/SATA CD drive ? Because this issue is NOT solved. At least not for me. Wonder if "archlinux-2010.04.05-netinstall-i686.iso" from the here will solve it (really hope so).
SOLVED IT HERE (with yet another image): http://bbs.archlinux.org/viewtopic.php?id=93645
Last edited by DSpider (2010-04-17 14:21:27)

Windows 8.1 first boot time too long

After Sysprep, windows 8.1 tooks long time to boot, is it normal?
N.A.Malik

Hi,
Generally, when you sysprep an image and deploy it to other devices, it would prepare the device settings, registry update and other computer configuration. This phase would take some time. We call it as specialize and OOBE pass.
Here we have a metric to assess the first boot time, you can take a look at this guide:
First Boot Performance
http://msdn.microsoft.com/en-us/library/windows/hardware/jj130825.aspx
Alex Zhao
TechNet Community Support

First Boot Device

Similar Messages

Maybe you are looking for