mirror of
https://github.com/reactos/reactos.git
synced 2024-10-06 09:24:11 +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
19 lines
771 B
C
19 lines
771 B
C
#pragma once
|
|
|
|
#define _WINERROR_
|
|
|
|
#define NO_ERROR 0
|
|
#define ERROR_INVALID_FUNCTION 1
|
|
#define ERROR_NOT_ENOUGH_MEMORY 8
|
|
#define ERROR_DEV_NOT_EXIST 55
|
|
#define ERROR_INVALID_PARAMETER 87
|
|
#define ERROR_INSUFFICIENT_BUFFER 122
|
|
#define ERROR_INVALID_NAME 123
|
|
#define ERROR_BUSY 170
|
|
#define ERROR_MORE_DATA 234
|
|
#define WAIT_TIMEOUT 258
|
|
#define ERROR_IO_PENDING 997
|
|
#define ERROR_DEVICE_REINITIALIZATION_NEEDED 1164
|
|
#define ERROR_CONTINUE 1246
|
|
#define ERROR_NO_MORE_DEVICES 1248
|