检查MS-DOS(C/C )中的键是否关闭
Checking if a key is down in MS-DOS (C/C++)
是的,我的意思是真正的MS-DOS,而不是Windows的cmd.exe
shell Console。
有没有办法检查键是否在MS-DOS中降低,类似于Winapi中的GetAsyncKeyState()
函数?
目前我正在使用kbhit()
和getch()
,但是它确实很慢,在第一个字符之后有延迟,不允许同时允许多个键等。
我正在使用涡轮C 3.1。谁能帮忙?
(顺便说一句,不要问我为什么要在如此古老的系统上编码我的游戏)
涡轮C ,MS-DOS或与Windows功能GetAsyncKeyState
相对应的BIOS没有提供的功能。BIOS仅跟踪哪个修饰符键(Shift,Ctrl或Alt)的固定,它不会跟踪任何其他键。如果要执行此操作,则需要直接与键盘控制器进行交谈,然后监视其从键盘收到的Make(键)和断开(键发布)扫描代码。
要做到这一点,您需要连接键盘中断(IRQ 1,INT 0x09),从键盘控制器中读取scancodes,然后更新自己的键盘状态表。
这是一个简单的程序,演示了如何:
#include <conio.h>
#include <dos.h>
#include <stdio.h>
unsigned char normal_keys[0x60];
unsigned char extended_keys[0x60];
static void interrupt
keyb_int() {
static unsigned char buffer;
unsigned char rawcode;
unsigned char make_break;
int scancode;
rawcode = inp(0x60); /* read scancode from keyboard controller */
make_break = !(rawcode & 0x80); /* bit 7: 0 = make, 1 = break */
scancode = rawcode & 0x7F;
if (buffer == 0xE0) { /* second byte of an extended key */
if (scancode < 0x60) {
extended_keys[scancode] = make_break;
}
buffer = 0;
} else if (buffer >= 0xE1 && buffer <= 0xE2) {
buffer = 0; /* ingore these extended keys */
} else if (rawcode >= 0xE0 && rawcode <= 0xE2) {
buffer = rawcode; /* first byte of an extended key */
} else if (scancode < 0x60) {
normal_keys[scancode] = make_break;
}
outp(0x20, 0x20); /* must send EOI to finish interrupt */
}
static void interrupt (*old_keyb_int)();
void
hook_keyb_int(void) {
old_keyb_int = getvect(0x09);
setvect(0x09, keyb_int);
}
void
unhook_keyb_int(void) {
if (old_keyb_int != NULL) {
setvect(0x09, old_keyb_int);
old_keyb_int = NULL;
}
}
int
ctrlbrk_handler(void) {
unhook_keyb_int();
_setcursortype(_NORMALCURSOR);
return 0;
}
static
putkeys(int y, unsigned char const *keys) {
int i;
gotoxy(1, y);
for (i = 0; i < 0x30; i++) {
putch(keys[i] + '0');
}
}
void
game(void) {
_setcursortype(_NOCURSOR);
clrscr();
while(!normal_keys[1]) {
putkeys(1, normal_keys);
putkeys(2, normal_keys + 0x30);
putkeys(4, extended_keys);
putkeys(5, extended_keys + 0x30);
}
gotoxy(1, 6);
_setcursortype(_NORMALCURSOR);
}
int
main() {
ctrlbrk(ctrlbrk_handler);
hook_keyb_int();
game();
unhook_keyb_int();
return 0;
}
上面的代码已与Borland C 3.1编译,并在Dosbox和MS-DOS 6.11下进行了测试,在VirtualBox下运行。它显示了键盘的当前状态为0和1的字符串,一个1
表示与该位置的扫描代码相对应的键。按ESC键退出程序。
请注意,该程序不会链接原始键盘处理程序,因此在键盘中断挂钩时,普通的MS-DOS和BIOS键盘功能将无法工作。另请注意,它在退出之前还原原始键盘处理程序。这至关重要,因为MS-DOS不会执行此操作。它还正确处理了发送两个字节扫描代码的扩展键,这是您在这里答案中链接到的问题中的代码的问题。
你为什么要在su&hellip上编码游戏;只是开玩笑!
在MS-DOS中," API"函数被用作中断服务器。在X86汇编语言中,您使用INT
指令并指定要执行的中断的数量。大多数中断要求在执行INT
之前,将其"参数"设置在某些寄存器中。在INT
指令将控件返回到您的代码之后,其结果将被放置在某些寄存器和/或标志中,如中断呼叫的文档所定义。
我不知道Turbo C 如何实现中断,因为这可以预先参与编程,但我确实知道它可以使您执行它们。Google在周围进行语法,或检查您的Turbo C 文档。
知道这些中断会在您搜索时为您带来解决方案的90%。拉尔夫·布朗(Ralf Brown)编译并出版了著名的DOS和BIOS中断代码清单。它们也应该在任何有关DOS编程的书中可用 - 如果您认真对待复古编程,那么您绝对应该考虑使用一本。亚马逊上的二手副本只能让您退缩几美元。当今大多数人都认为这些毫无价值。
这是一个网站,列出了可用于DOS中断21H的子功能。与您使用相关的是01
,06
,07
和08
。这些基本上是C标准库(例如getch
)在引擎盖下进行的功能。我发现很难想象,但是我听到有报道说,当天程序员回到当天的速度更快地打电话给了DOS。我质疑的原因是,我无法想象运行时库实施者将是如此愚蠢,以提供不必要的缓慢实现。但是也许是。
如果DOS中断对您来说仍然太慢,那么您的最后一个追索方法是直接使用BIOS中断。这可能会在速度上产生明显的影响,因为您绕过了可能的每个抽象层。但这确实使您的程序大大降低了便携式,这就是像DOS这样的操作系统提供这些较高级别功能的原因。同样,检查拉尔夫·布朗(Ralf Brown)的列表中是否与您使用相关的中断。例如,带有01h
子功能的INT 16
。
按箭头键射击两个键盘中断?(INT 09H)这个问题中的实现效果很好,因此,如果有人出于某种原因需要准备好功能,那么您就可以了:
unsigned char read_scancode() {
unsigned char res;
_asm {
in al, 60h
mov res, al
in al, 61h
or al, 128
out 61h, al
xor al, 128
out 61h, al
}
return res;
}
(编辑:对未签名的char更正的char,因此将此函数的返回值放在"如果"语句中,诸如scancode & 0x80
实际上有效)
按下键时,它返回其中列出的scancodes之一http://www.ctyme.com/intr/rb-0045.htm,当它发布时,它返回了相同的scancode,但带有80h。P>
如果您实际运行的是在游戏循环中运行的,则最终将溢出BIOS键盘缓冲区,并且计算机会向您发出哔哔声。释放键盘缓冲区的一种方法当然是while(kbhit()) getch();
,但由于我们在286 Realmode上,并且我们所有的硬件都可以使用,因此这是一个更低级的解决方案:
void free_keyb_buf() {
*(char*)(0x0040001A) = 0x20;
*(char*)(0x0040001C) = 0x20;
}
如果您正在寻找解释如何以及为什么起作用,那么您就可以了:
BIOS键盘缓冲区从0040:001Ah
开始,看起来像:2字节"头"指针,2字节"尾巴"指针和32个字节的2字节scancodes。"尾部"指针指示从键盘缓冲区开始读取的何处,"头"指示指示停止的位置。因此,通过将两个设置为0x20
(因此它们实际上指向0040:0020h
),我们基本上欺骗了计算机认为没有新的击键可以提取。
所以,我最近经历了所有这些内容,只是碰巧拥有所需的代码。(另外,我将链接您的一些很棒的书,以从PDF格式获取信息。)
因此,这种工作方式是您需要在索引9H处覆盖内存中的中断向量表。中断向量表只是一个内存表,指向当中断触发时要运行的代码(这些称为中断处理程序例程或ISR)。当键盘控制器准备好使用scancode时,触发中断9H。
无论如何,我们首先需要通过调用键盘installdriver()函数来覆盖旧的int9h isr。现在,当触发int9h时,键盘isr()函数被调用,并且从键盘控制器中获取scancode,并根据值(key_pressed)或0(key_realed)在键盘中设置一个值[]从键盘控制器检索的扫描代码。
已设置了键盘[]数组中的相应值之后,您可以调用键盘getKey(),将其作为您想知道的状态的键的scancode,它将在键盘中查找[]数组并返回状态。
有很多细节,但是在这里写的太多了。所有详细信息都可以在我将在此处链接的书籍中找到: IBM PC技术参考, IBM PC在技术参考, 3D游戏编程的黑色艺术 希望这些链接保持活跃一段时间。另外,在每个小细节上," 3D游戏编程的黑色艺术"书并不总是完全准确。有时会有错别字,有时会出现错误信息,但是IBM技术参考文献有所有细节(即使有时有点隐秘),但是它们没有示例代码。使用这本书获得一般的想法,并使用参考来获取详细信息。 这是我从键盘获取输入的代码:(对于所有可能的钥匙和某些其他事情,它都没有完全完成,但对于大多数程序和游戏来说都很好。) 另外,还有一些代码可以处理"扩展"键。扩展键的0xe0前缀以其常规扫描代码。还有更多疯狂的细节,所以我不会介绍它,但是,无论如何,有主要工作的代码。 键盘 键盘 键盘_scan_codes.h (只需将所有scancodes定义为qwerty按钮布局)#ifndef KEYBOARD_H_INCLUDED
#define KEYBOARD_H_INCLUDED
#include "keyboard_scan_codes.h"
unsigned char KeyboardGetKey(unsigned int scanCode);
void KeyboardClearKeys();
void KeyboardInstallDriver();
void KeyboardUninstallDriver();
void KeyboardDumpScancodeLog();
#endif // KEYBOARD_H_INCLUDED
#define MAX_SCAN_CODES 256
#define KEYBOARD_CONTROLLER_OUTPUT_BUFFER 0x60
#define KEYBOARD_CONTROLLER_STATUS_REGISTER 0x64
#define KEY_PRESSED 1
#define KEY_RELEASED 0
#define PIC_OPERATION_COMMAND_PORT 0x20
#define KEYBOARD_INTERRUPT_VECTOR 0x09
// PPI stands for Programmable Peripheral Interface (which is the Intel 8255A chip)
// The PPI ports are only for IBM PC and XT, however port A is mapped to the same
// I/O address as the Keyboard Controller's (Intel 8042 chip) output buffer for compatibility.
#define PPI_PORT_A 0x60
#define PPI_PORT_B 0x61
#define PPI_PORT_C 0x62
#define PPI_COMMAND_REGISTER 0x63
#include <dos.h>
#include <string.h>
#include <stdio.h>
#include <conio.h>
#include "keyboard.h"
void interrupt (*oldKeyboardIsr)() = (void *)0;
unsigned char keyStates[MAX_SCAN_CODES];
unsigned char keyCodeLog[256] = {0};
unsigned char keyCodeLogPosition = 0;
static unsigned char isPreviousCodeExtended = 0;
unsigned char KeyboardGetKey(unsigned int scanCode)
{
// Check for the extended code
if(scanCode >> 8 == 0xE0)
{
// Get rid of the extended code
scanCode &= 0xFF;
return keyStates[scanCode + 0x7F];
}
else
{
return keyStates[scanCode];
}
}
void KeyboardClearKeys()
{
memset(&keyStates[0], 0, MAX_SCAN_CODES);
}
void interrupt far KeyboardIsr()
{
static unsigned char scanCode;
unsigned char ppiPortB;
_asm {
cli // disable interrupts
};
/* The keyboard controller, by default, will send scan codes
// in Scan Code Set 1 (reference the IBM Technical References
// for a complete list of scan codes).
//
// Scan codes in this set come as make/break codes. The make
// code is the normal scan code of the key, and the break code
// is the make code bitwise "OR"ed with 0x80 (the high bit is set).
//
// On keyboards after the original IBM Model F 83-key, an 0xE0
// is prepended to some keys that didn't exist on the original keyboard.
//
// Some keys have their scan codes affected by the state of
// the shift, and num-lock keys. These certain
// keys have, potentially, quite long scan codes with multiple
// possible 0xE0 bytes along with other codes to indicate the
// state of the shift, and num-lock keys.
//
// There are two other Scan Code Sets, Set 2 and Set 3. Set 2
// was introduced with the IBM PC AT, and Set 3 with the IBM
// PS/2. Set 3 is by far the easiest and most simple set to work
// with, but not all keyboards support it.
//
// Note:
// The "keyboard controller" chip is different depending on
// which machine is being used. The original IBM PC uses the
// Intel 8255A-5, while the IBM PC AT uses the Intel 8042 (UPI-42AH).
// On the 8255A-5, port 0x61 can be read and written to for various
// things, one of which will clear the keyboard and disable it or
// re enable it. There is no such function on the AT and newer, but
// it is not needed anyways. The 8042 uses ports 0x60 and 0x64. Both
// the 8255A-5 and the 8042 give the scan codes from the keyboard
// through port 0x60.
// On the IBM PC and XT and compatibles, you MUST clear the keyboard
// after reading the scancode by reading the value at port 0x61,
// flipping the 7th bit to a 1, and writing that value back to port 0x61.
// After that is done, flip the 7th bit back to 0 to re-enable the keyboard.
//
// On IBM PC ATs and newer, writing and reading port 0x61 does nothing (as far
// as I know), and using it to clear the keyboard isn't necessary.*/
scanCode = 0;
ppiPortB = 0;
ppiPortB = inp(PPI_PORT_B); // get the current settings in PPI port B
scanCode = inp(KEYBOARD_CONTROLLER_OUTPUT_BUFFER); // get the scancode waiting in the output buffer
outp(PPI_PORT_B, ppiPortB | 0x80); // set the 7th bit of PPI port B (clear keyboard)
outp(PPI_PORT_B, ppiPortB); // clear the 7th bit of the PPI (enable keyboard)
// Log scancode
keyCodeLog[keyCodeLogPosition] = scanCode;
if(keyCodeLogPosition < 255)
{
++keyCodeLogPosition;
}
// Check to see what the code was.
// Note that we have to process the scan code one byte at a time.
// This is because we can't get another scan code until the current
// interrupt is finished.
switch(scanCode)
{
case 0xE0:
// Extended scancode
isPreviousCodeExtended = 1;
break;
default:
// Regular scancode
// Check the high bit, if set, then it's a break code.
if(isPreviousCodeExtended)
{
isPreviousCodeExtended = 0;
if(scanCode & 0x80)
{
scanCode &= 0x7F;
keyStates[scanCode + 0x7F] = KEY_RELEASED;
}
else
{
keyStates[scanCode + 0x7F] = KEY_PRESSED;
}
}
else if(scanCode & 0x80)
{
scanCode &= 0x7F;
keyStates[scanCode] = KEY_RELEASED;
}
else
{
keyStates[scanCode] = KEY_PRESSED;
}
break;
}
// Send a "Non Specific End of Interrupt" command to the PIC.
// See Intel 8259A datasheet for details.
outp(PIC_OPERATION_COMMAND_PORT, 0x20);
_asm
{
sti // enable interrupts
};
}
void KeyboardInstallDriver()
{
// Make sure the new ISR isn't already in use.
if(oldKeyboardIsr == (void *)0)
{
oldKeyboardIsr = _dos_getvect(KEYBOARD_INTERRUPT_VECTOR);
_dos_setvect(KEYBOARD_INTERRUPT_VECTOR, KeyboardIsr);
}
}
void KeyboardUninstallDriver()
{
// Make sure the new ISR is in use.
if(oldKeyboardIsr != (void *)0)
{
_dos_setvect(KEYBOARD_INTERRUPT_VECTOR, oldKeyboardIsr);
oldKeyboardIsr = (void *)0;
}
}
void KeyboardDumpScancodeLog()
{
FILE *keyLogFile = fopen("keylog.hex", "w+b");
if(!keyLogFile)
{
printf("ERROR: Couldn't open file for key logging!n");
}
else
{
int i;
for(i = 0; i < 256; ++i)
{
fputc(keyCodeLog[i], keyLogFile);
}
fclose(keyLogFile);
}
}
#ifndef KEYBOARD_SCAN_CODES_H_INCLUDED
#define KEYBOARD_SCAN_CODES_H_INCLUDED
// Original 83 Keys from the IBM 83-key Model F keyboard
#define SCAN_NONE 0x00
#define SCAN_ESC 0x01
#define SCAN_1 0x02
#define SCAN_2 0x03
#define SCAN_3 0x04
#define SCAN_4 0x05
#define SCAN_5 0x06
#define SCAN_6 0x07
#define SCAN_7 0x08
#define SCAN_8 0x09
#define SCAN_9 0x0A
#define SCAN_0 0x0B
#define SCAN_MINUS 0x0C
#define SCAN_EQUALS 0x0D
#define SCAN_BACKSPACE 0x0E
#define SCAN_TAB 0x0F
#define SCAN_Q 0x10
#define SCAN_W 0x11
#define SCAN_E 0x12
#define SCAN_R 0x13
#define SCAN_T 0x14
#define SCAN_Y 0x15
#define SCAN_U 0x16
#define SCAN_I 0x17
#define SCAN_O 0x18
#define SCAN_P 0x19
#define SCAN_LEFT_BRACE 0x1A
#define SCAN_RIGHT_BRACE 0x1B
#define SCAN_ENTER 0x1C
#define SCAN_LEFT_CONTROL 0x1D
#define SCAN_A 0x1E
#define SCAN_S 0x1F
#define SCAN_D 0x20
#define SCAN_F 0x21
#define SCAN_G 0x22
#define SCAN_H 0x23
#define SCAN_J 0x24
#define SCAN_K 0x25
#define SCAN_L 0x26
#define SCAN_SEMICOLON 0x27
#define SCAN_APOSTROPHE 0x28
#define SCAN_ACCENT 0x29
#define SCAN_TILDE 0x29 // Duplicate of SCAN_ACCENT with popular Tilde name.
#define SCAN_LEFT_SHIFT 0x2A
#define SCAN_BACK_SLASH 0x2B
#define SCAN_Z 0x2C
#define SCAN_X 0x2D
#define SCAN_C 0x2E
#define SCAN_V 0x2F
#define SCAN_B 0x30
#define SCAN_N 0x31
#define SCAN_M 0x32
#define SCAN_COMMA 0x33
#define SCAN_PERIOD 0x34
#define SCAN_FORWARD_SLASH 0x35
#define SCAN_RIGHT_SHIFT 0x36
#define SCAN_KP_STAR 0x37
#define SCAN_KP_MULTIPLY 0x37 // Duplicate of SCAN_KP_STAR
#define SCAN_LEFT_ALT 0x38
#define SCAN_SPACE 0x39
#define SCAN_CAPS_LOCK 0x3A
#define SCAN_F1 0x3B
#define SCAN_F2 0x3C
#define SCAN_F3 0x3D
#define SCAN_F4 0x3E
#define SCAN_F5 0x3F
#define SCAN_F6 0x40
#define SCAN_F7 0x41
#define SCAN_F8 0x42
#define SCAN_F9 0x43
#define SCAN_F10 0x44
#define SCAN_NUM_LOCK 0x45
#define SCAN_SCROLL_LOCK 0x46
#define SCAN_KP_7 0x47
#define SCAN_KP_8 0x48
#define SCAN_KP_9 0x49
#define SCAN_KP_MINUS 0x4A
#define SCAN_KP_4 0x4B
#define SCAN_KP_5 0x4C
#define SCAN_KP_6 0x4D
#define SCAN_KP_PLUS 0x4E
#define SCAN_KP_1 0x4F
#define SCAN_KP_2 0x50
#define SCAN_KP_3 0x51
#define SCAN_KP_0 0x52
#define SCAN_KP_PERIOD 0x53
// Extended keys for the IBM 101-key Model M keyboard.
#define SCAN_RIGHT_ALT 0xE038
#define SCAN_RIGHT_CONTROL 0xE01D
#define SCAN_LEFT_ARROW 0xE04B
#define SCAN_RIGHT_ARROW 0xE04D
#define SCAN_UP_ARROW 0xE048
#define SCAN_DOWN_ARROW 0xE050
#define SCAN_NUMPAD_ENTER 0xE01C
#define SCAN_INSERT 0xE052
#define SCAN_DELETE 0xE053
#define SCAN_HOME 0xE047
#define SCAN_END 0xE04F
#define SCAN_PAGE_UP 0xE049
#define SCAN_PAGE_DOWN 0xE051
#define SCAN_KP_FORWARD_SLASH 0xE035
#define SCAN_PRINT_SCREEN 0xE02AE037
#endif // KEYBOARD_SCAN_CODES_H_INCLUDED
- MSHTML编辑在MS Edge中是否等效
- 检查MS-DOS(C/C )中的键是否关闭
- CreateFile打开在另一个终端会话中创建的MS-DOS设备
- 是否可以在DOS 6.22中运行java应用程序
- MS中的内联组装是否需要易失性之类的东西C++以防止优化器干预
- 在 Windows 中自动将 xlsx 文件转换为多个 (MS-DOS) CSV 文件(每张一张一个)
- 是否将资源(声音文件)添加到exe?[MS Visual Studio 2012]
- 是否可以使用现有API修改windows功能区控件,使其看起来更像MS Word 2010中的功能区
- 是否有可能一个项目只能由MS Visual c ++ express构建
- 如何在MS DOS而不是Borland上手动编译和运行(通过单个命令)C++程序
- 是否可以将MS单元测试从EXE转发到DLL
- MS Stl库是否包含内存泄漏
- 如何编译c/c++到ms-dos .com程序
- 如何判断屏幕保护程序是否在Qt (C/ c++)程序中运行?Windows (MS)
- 是否有一种方法可以从VS环境之外的MS单元测试框架中获取信息
- 在没有ms-dos窗口的情况下运行exe
- 在MS-DOS中使用长参数列表(超过128个字符)编译
- 是否可以用MS迂回注入多个Dll
- 是否有一个开源的免费工具为MS Visual c++ Express构建使用gcc
- MS Visual Studio 2010 c++预处理器-如果函数在宏中定义并在其他地方调用,当未定义时是否会有任何开