mirror of
https://github.com/reactos/reactos.git
synced 2024-09-19 09:09:53 +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
18 lines
393 B
Plaintext
18 lines
393 B
Plaintext
HKCR
|
|
{
|
|
NoRemove Interface
|
|
{
|
|
}
|
|
NoRemove CLSID
|
|
{
|
|
'{44EC053A-400F-11D0-9DCD-00A0C90391D3}' = s 'Registrar Class'
|
|
{
|
|
InprocServer32 = s '%MODULE%' { val ThreadingModel = s 'Both' }
|
|
ProgId = s 'ATL.Registrar'
|
|
}
|
|
}
|
|
'ATL.Registrar' = s 'Registrar Class'
|
|
{
|
|
CLSID = s '{44EC053A-400F-11D0-9DCD-00A0C90391D3}'
|
|
}
|
|
} |