I actually like those verbose diagnostic messages during bootup and I would be happy if I could enable them during Windows boot. If anything goes wrong, I most probably already have all the info I need to be able to troubleshoot the problem. It’s also less boring to watch the scrolling text than to see some static logo (especially when the logo is in wrong resolution which is painful for the eyes, or monochromatic).
When using macOS it’s possible to enable such boot with boot-args=-v nvram option. When installing macOS on VirtualBox, nvram is setup this way by default.
I use FreeBSD desktop for 14 years and I found such situation only once when FreeBSD system asked me upon boot process if I would like to panic or not - FreeBSD: Panic or not to Panic - it was some issue with dual AthlonMP SMP motherboard and dual AthlonXP processors modded to be AthlonMP ones ;)
But I also had a problem with the motherboard/CPU resulted in the kernel suddenly seeing only one core and not booting properly. Drive read failures because of corruption, bad SATA cables, slow boot because of some service taking too much time to start up, boot hang because of a broken network card, etc. I also have calls from friends from time to time asking why Windows doesn’t boot up. If only I had those diagnostic messages I wouldn’t need to guess :)
Every time I want some friend to read me these verbose error messages they read the LEAST important ones and remote assistance ends with remote visit :)
I actually like those verbose diagnostic messages during bootup and I would be happy if I could enable them during Windows boot. If anything goes wrong, I most probably already have all the info I need to be able to troubleshoot the problem. It’s also less boring to watch the scrolling text than to see some static logo (especially when the logo is in wrong resolution which is painful for the eyes, or monochromatic).
When using macOS it’s possible to enable such boot with
boot-args=-vnvram option. When installing macOS on VirtualBox, nvram is setup this way by default.I use FreeBSD desktop for 14 years and I found such situation only once when FreeBSD system asked me upon boot process if I would like to panic or not - FreeBSD: Panic or not to Panic - it was some issue with dual AthlonMP SMP motherboard and dual AthlonXP processors modded to be AthlonMP ones ;)
I understand it works for you, and it’s cool.
But I also had a problem with the motherboard/CPU resulted in the kernel suddenly seeing only one core and not booting properly. Drive read failures because of corruption, bad SATA cables, slow boot because of some service taking too much time to start up, boot hang because of a broken network card, etc. I also have calls from friends from time to time asking why Windows doesn’t boot up. If only I had those diagnostic messages I wouldn’t need to guess :)
Every time I want some friend to read me these verbose error messages they read the LEAST important ones and remote assistance ends with remote visit :)