I have a bunch of Neoware CA10 thin clients that I am configuring as diskless workstations for a class I'll be teaching this fall. In documenting my efforts, I've had to reference BIOS settings to ensure the device is ready for PXE boot as well as configuring the various hardware in the device so they are each in a consistent state (I want to use a single file-system image to serve all of them).
One of the switches in the BIOS allows the "Summary Screen" to be displayed at POST. This summarizes the resources in the target, disks installed, ram present, processor speed, etc. Useful tidbits to have EASILY accessible (though some can be found elsewhere in the Setup Mode).
The BIOS writers tried to dress this up with line graphics, etc. AS IF it would occupy the entire display at some point during the boot sequence (makes sense to be able to quickly review the capabilities of the machine!).
*But*, it is immediately followed by an enumeration of the PCI devices in the target. As a result, the "Summary Screen" scrolls off the top of the display -- before you can even get a peek at it! (it actually *appears* in it's scrolled position; it never *moves* off the screen!) [I've filmed the display with a movie camera and examined the results in slow motion to verify the top part of the "summary" is never "visible"]Of course, no way to route this to a printer or to a log file as the system hasn't even tried to boot an OS, yet!
I've tried to stop the scroll with XON/XOFF, Scroll Lock, etc. but it seems to be intent on doing its thing BEFORE listening to the user.
There's no way to shrink the PCI device inventory as everything is on the "motherboard" -- it's not like I can pull out cards to eliminate devices! And, no BIOS setting that shows the "Summary Screen" WITHOUT the PCI device enumeration.
[I.e., developers weren't really THINKING when they made these decisions!]Any other suggestions to try? I'm presently looking through google images to see if I can recognize a similar screen (as the last few lines ARE visible at the top of the display).
I may also grep the boot ROM images on the assumption that there is probably a const template that is filled in at display time and I could recreate the data that should be displayed by examining the "field labels" in that template.
If push comes to shove, I can just "carelessly forget" to include this information in my documentation. But, I tend to be far more thorough than that.
[OTOH, I have other things fighting for my time and, in The Grand Scheme of Things, I could just as easily type up a table of the targets characteristics and ignore the "Summary Screen" entirely...]Thx!