mirror of
https://github.com/reactos/reactos.git
synced 2024-08-31 07:38:48 +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
24 lines
566 B
C
24 lines
566 B
C
#pragma once
|
|
|
|
#define IDB_BOOT_LOGO 1
|
|
#define IDB_HIBERNATE_LOGO 2
|
|
#define IDB_SHUTDOWN_LOGO 3
|
|
#define IDB_LOGO 5
|
|
#define IDB_LOGO_HEADER 6
|
|
#define IDB_LOGO_BAND 7
|
|
|
|
#define IDB_BAR_SERVER 4
|
|
#define IDB_BAR_PRO 8
|
|
#define IDB_BAR_HOME 9
|
|
|
|
#define IDB_PROF_TEXT 10
|
|
#define IDB_HOME_TEXT 11
|
|
#define IDB_EMBEDDED_TEXT 12
|
|
#define IDB_MCE_TEXT 18
|
|
|
|
#define IDB_SERVER_LOGO 13
|
|
#define IDB_SERVER_HEADER 14
|
|
#define IDB_SERVER_BAND 15
|
|
#define IDB_STORAGE_SERVER 16
|
|
#define IDB_CLUSTER_SERVER 17
|