mirror of
https://github.com/reactos/reactos.git
synced 2024-11-05 06:09:58 +00:00
e1ef078741
The idea then would be to have the following behaviour (when specifying the following options in the kernel command line): /DEBUGPORT=COMi --> load KDCOM.DLL and use COMi port (i == 1,2,3,4) if possible. /DEBUGPORT=FOO --> load KDFOO.DLL (useful for KDUSB.DLL, KD1394.DLL, KDBAZIS.DLL for VirtualKD, etc...) /DEBUGPORT=ROSDBG:[COMi|SCREEN|FILE|GDB|...] --> load KDROSDBG.DLL which contains the ROS kernel debugger, and use COMi or SCREEN or... as output port. svn path=/branches/kd++/; revision=58883
10 lines
194 B
C
10 lines
194 B
C
#pragma once
|
|
|
|
typedef struct _ACCELERATOR_TABLE
|
|
{
|
|
HEAD head;
|
|
ULONG Count;
|
|
LPACCEL Table;
|
|
} ACCELERATOR_TABLE, *PACCELERATOR_TABLE;
|
|
|
|
PACCELERATOR_TABLE FASTCALL UserGetAccelObject(HACCEL);
|