The obsession with the "Quiet Boot"

From OS2World.Com Wiki
Jump to navigation Jump to search

It is a personal thing for Operating System, but I have an obsession with the "Quiet Boot". If your computer and OS configuration is stable, why do you want to see all the messages on the boot of the OS every time you turn it on?

The idea will be that you will only see some error on boot if something is not working as it should, like the case of some device driver being not able to start the device, or something that had changed on your computer that is causing issued on boot.

I want to use this wiki page to document which drivers are not able to be quiet on boot, just to dream forward that someday this list will change.

Which drivers are not being "Quiet"

This driver can not be turned into silent or quiet mode, you always see a message of those on boot.

ACPI.PSD
JFS.IFS

QBoot ACPI-JFS.png

TCPBEUI.OS2
I think it is putting an empty space.

QBoot-NETBIOS.png

NETBIOS.OS2
It produce a blank line when booting.

QBoot-NETBIOS.png

VMANWIN.SYS
It produce a blank line when booting.
MIDIDMON.EXE
It produce a blank line when booting.
CNTRL.EXE
It produce a blank line when booting.

QBoot-CNTRL.png

ACPIDAEMON.EXE
It produce a blank line when booting.

ACPIDAEMON.png

A step closer to the dream

ASPIROUT.SYS
No longer produces a blank line when booting. (2017-01-04 20:10 / 1.01.0)

ASPIROUT.png

LVMALERT.EXE
No longer produces a blank line when booting. (2001-10-16)

QBoot-LVMALERT.png

EXTENDFS.EXE
No longer produces a blank line when booting. (2016-10-24 9:48a / 1.09.07 )

EXTENDFS.png

IFX.EXE
For version 1.22 a /Q mode was included. Thanks.
VBOXGUEST.SYS
I opened a ticket suggestion this (2017/07), [1]. It was finally address.

Why?

OCD.png