New
#1
How to add a delay to HDD's on bootup?
Windows and bios don't agree on which HDD is 1st 2nd or 3rd.
So I need to delay 2 HDD's at bootup but once in windows they are ok.
Windows and bios don't agree on which HDD is 1st 2nd or 3rd.
So I need to delay 2 HDD's at bootup but once in windows they are ok.
Welcome to TenForums!
I don't think that you can delay the detection of drives, at least I'm not aware a way in which to do that.
However, note that it is absolutely normal for the BIOS and Windows to enumerate the drives differently.
However, I might be able to supply a better answer or workaround if I knew why this mattered to you in the first place. What issue is it that you are trying to resolve or what end result is it that you want to achieve?
Please provide as much detail as possible. For example:
When I start Windows, I am seeing this behavior, but what I would like to happen is this.
That's really odd that the backup software would not enumerate the drives using standard Windows procedures and thus enumerating the drives as Windows sees them.
By any chance, is this a backup software that has it's own bootable media from which you are running it or do you run the backup software from within Windows?
Would you be willing to share the name of that software so that I can attempt to do a little further research?
Hi
HyperOS is my software,everything works fine,it's just the order of the HDD's is the same as windows not bios.
It is a known thing,doesn't cause a problem except for my analness.
attached pic is how it should be,correct order same as bios,they are removable drives too.
if I boot up with them attached/not disabled then the order becomes mixed.
Switch cables around on SATA ports on the motherboard.
can I enable/disable specified HDD's at bootup/restart through task scheduler/scripts?
I used a setting in the BIOS back some 20 years ago when the computers started getting faster than the spin-up of new HDDs but that was for delaying the OS loading, probably won't work. The 2 files used back then for booting and running were the autoexec.bat and config.sys, not in use with more modern machines [I still have a DOS/Win3.x Notebook]. The biggest issue with using Task Scheduler, scripts or other Windows features or programs is that Windows has to be running first, might work on secondary drives but most likely not for the boot/system drive Windows is installed on.