Maz Hoot wrote on 2025-03-08, 16:19:
"- Wait for primary hard drive ready (everyone has a primary hard drive and you wouldn't
want to boot from something else that might access it before it's ready)"
You are probably right but I still doesn't understand why there is an option to boot from hdd2 (yea this option is weird, I totally agree but it's here so it can't be ignored). Why let people boot from hdd2 if everyone si suppose to have an hdd1 connected and if you can't boot without waiting enormous time without an hdd1 ? It's a contradiction... like "hey guys, you can boot from hdd2, but you will regreat it !! haha"
Couple of simple rules to keep in mine then trying to "figure out" this industry.
- Not everyone thinks like you, or always logically
- Things that may cause problems for <0.1% users are rarely considered
I'm sure the manufacturer thought that >99.9% users would be booting from HD (or
CD to restore OS) both of which want hard drive ready.
The option is there for the very few users who might want to "stuff in another drive and boot
from it" from time-to-time - most likely service people. And almost all of them would want to
access the primary hard drive (or at least not remove it)
From manufacturers viewpoint - if hard drive or caddy fails, we'd be happy to sell them a new one.
Manufacturers almost never consider how their products might be used after they are no longer
producing them ... I very much doubt that anyone ever considered how to make the system usable
booting from HD2 without HD1 (and to be fair - in the <0.0000001% cases where it might have been
needed when the product was in production - it does work!)
"I suspect the only way to "fix" this is to either find/make a cable to connect the HDD as primary
- or - [find a]/[modify the] BIOS to not do the "wait for ready"."
I don't have enough knowledge to do that sadly...
If you are lucky, maybe someone else has come across this - and made a BIOS patch.
Of maybe there's an alternate compatible BIOS that allows complete disable of
primary HD access....
If it were my machine, and it was driving me nuts and no other solution could be found,
I'd probably spend a few days with a debugger/disassembler and see if I could:
a) figure out how to patch it to bypass the wait.
b) figure out if/how the BIOS was checking itself so that value could be patched.
But even then, I'd probably not do it on the original BIOS chip - I'd want to be able to
put it back if the patch failed to the point where you couldn't reflash.
Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal
Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal