02-20-2019
Linux was such a hack back then because those ancient machines were a mishmash of old and new designs, never implemented the same way twice.. Manufacturers didn't feel a need to publish proper specs because BIOS extensions were mostly "good enough" to nursemaid whatever archaic non-Windows OS you had into the 21st century. That is to say, device drivers, included in the form of little microchips to be read upon boot...! Nowdays the BIOS is basically gone and drivers are taken a little more seriously.
7 More Discussions You Might Find Interesting
1. Programming
At time of installation I have to open the resource. and i have to insert a string serial number in the exe.
please provide me code to edit the exe (in solaris) to insert a serial number which can be used by exe at run time. (6 Replies)
Discussion started by: ssahu
6 Replies
2. Programming
I'm very new to c++ & unix programming. I have a c++ exe that runs on the unix box, but I am trying to write a c++ windows app that executes the program on unix. I have tried execv(), but it doesn't seem to work or I'm doing something wrong. Would really like to see examples if at all possible. ... (5 Replies)
Discussion started by: ch5082
5 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have a requirement to run multiple instances of an .exe file present in windows server from unix machine. The number of threads to be invoked is determined dynamically based on a variable field. We will be passing some parameters to windows .exe file for each instance.
I am a unix... (2 Replies)
Discussion started by: sam99
2 Replies
4. Linux
What are the differences, advantages, and disadvantages? (1 Reply)
Discussion started by: Advice Pro
1 Replies
5. Programming
I am writing java application on windows.
There are more than 100 threads run within java.exe.
I want to know what threads run within process java.exe so that I can find out if there are abnormal java threads. (4 Replies)
Discussion started by: mika
4 Replies
6. Shell Programming and Scripting
Hi,
I am triggering a windows exe file using the below command.
ssh user@remoteserver command.exe -option1:xx /option2:yy
This command is working fine from windows command prompt. When I am triggering the same command from ssh I get the error message cant load
Any ideas to deal with... (2 Replies)
Discussion started by: ahmedwaseem2000
2 Replies
7. Windows & DOS: Issues & Discussions
I ssh from Windows to Linux server and execute a few commands. I have ssh keys setup between them and works fine.
The commands get executed on the Linux server however I wish to stay on the Linux terminal that was opened by putty.exe. However, the terminal simply does the job and closes.
... (10 Replies)
Discussion started by: mohtashims
10 Replies
LEARN ABOUT NETBSD
acpivga
ACPIVGA(4) BSD Kernel Interfaces Manual ACPIVGA(4)
NAME
acpivga -- ACPI Display Adapter and Output Devices
SYNOPSIS
acpivga* at acpi?
acpiout* at acpivga?
DESCRIPTION
The acpivga driver provides generic support for brightness control and output switching, through ACPI video extensions. The ACPI specifica-
tion requires that systems containing a built-in display adapter implement these extensions in their ACPI BIOS.
The driver handles brightness hotkeys and display switch hotkeys. In addition, the following sysctl(8) read/write variables are provided
(when hardware support is available):
hw.acpi.acpivga0.bios_switch
BIOS output switching policy. This boolean variable controls the behavior of the BIOS when a display switch hotkey is pressed.
1 the BIOS should automatically switch outputs, with no interaction from acpivga.
0 the BIOS should only notify acpivga of the desired output state changes.
hw.acpi.acpiout0.brightness
Brightness level. This integer variable typically ranges from 0 to 100, but any integer value is accepted (the driver uses the clos-
est brightness level supported by the device).
Please note, however, that future versions of acpivga may remove these sysctl(8) variables without prior notice.
SEE ALSO
acpi(4), vga(4), sysctl(8)
Microsoft Corporation, Mobile System Displays and Windows, Version 1.2c, http://www.microsoft.com/whdc/archive/mobiledisplay.mspx, December
4, 2001.
HISTORY
The acpivga driver appeared in NetBSD 6.0.
AUTHORS
Gregoire Sutre <gsutre@NetBSD.org>
CAVEATS
The acpivga driver only supports PCI/PCI-X/PCI-E display adapters.
Many ACPI BIOSes implement only part of the ACPI video extensions. In particular, display output switching via these extensions often does
not work. For this reason, acpivga enables hw.acpi.acpivga0.bios_switch by default. If the display switch hotkey does not work with this
default setting, try setting hw.acpi.acpivga0.bios_switch to 0.
Brightness level should be controlled via wsconsctl(8) instead of sysctl(8).
BSD
October 28, 2010 BSD