Execute the command Keyboard.SetLayout <filename> ~ to choose a keyboard layout at runtime. The filename parameter is the name of one of the Key*.Bin files (e.g. KeyUS.Bin, KeyCH.Bin, ...). To make this change permanent, add the command mentioned above to the autostart section in Configuration.XML. Alternatively, you can assign the filename as value to the config string 'Keyboard' (see Configuration Strings: Keyboard).
Execute the command UsbKeyboard.SetLayout devicename <filename> ~. The only difference between setting the layout for PS/2 keyboard and USB keyboard is that there can be multiple USB keyboards attached, hence you have to specify the devicename (keyboard name) where the change should apply. The get a list of the device names, use the command SystemTools.List plugins ~
You have to set the configuration string (see Configuration Strings: Display) 'Init' to a reasonable value.
Examples: Init=117 results in 1024x768x16, Init=11A in 1280x1024x16
I know only one way to get information about what other values for Init strings are supported by a specific graphics card: The Bluebottle BootManager has an option to display the VESA modes (value for Init string)
Note: The three digit VESA modes always result in a display refresh rate of 60Hz
See also the answer to the next queestion.
The module DisplayGTF.Mod offers a command (DisplayGTF.Mode) that can be used to generate a Init string that initializes display resolution, color depth and display refresh rate. Not that you also have to manually set DWidth, DHeight and DDepth in this case. For more information, have a look a the comments found at the end of the module DisplayGTF.Mod.
Warning: Don't use refresh rates that are higher than supported by your display.
If you want to set up changed display properties permanently, you can do the following.
Find out which modes are possible, e.g. by using the Hardware Detection tool of the Syslinux project ([http://hdt-project.org/ HDT].
Then use the tool DisplayGTF:
DisplayGFT.Mode mode width height depth refresh~
It will tell you what you should insert into the configuration string section of the boot loader. You have to edit the output of DisplayGTF slightly. and combine it with the output of Partitions.GetConfig
No, it can't.
A2 does support multiple displays. Some information has been posted by Thomas Frey on the old mailing list: See https://lists.inf.ethz.ch/pipermail/oberon/2003/002772.html and there is some more information in Setup.Text, Sec. 2.3.5 Multi-moniotor desktop. The latter refers to the Permedia driver, which is not in the distribution due to copyright issues.
In WinAOS, you can specify the startup size and the position of the WinAOS window. To make WinAOS start at "multiscreen-fullscreen", edit the parameters of the DisplayWin32.Install command in the file /WinAos/aos.ini.
Example: DisplayWin32.Install 2560 1024 -1280 0 ~ sets the WinAOS window size to 2560x1024 pixels and the position to x-offset -1280, y-offset 0 (relative to the primary display). If you have two screens with 1280x1024 pixels resolution and the primary screen is the right one, this results in a window spawning both screens.
Copyright © 2007 ETH Zürich
Page last modified on July 05, 2013, at 12:56 PM