Using the following line in the boot.ini on my computer is having a
strange effect.
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /DEBUGPORT=COM1 /BAUDRATE=57600
After I boot with this option WinDbg no longer sees COM1
in windows debugger options.
In fact COM1 also dissapears from the device Manager.
If I boot without /DEBUGPORT=COM1 enabled I have no problem
with COM1.
Now this is OK if the machine in question is to be used as the host
for WinDbg as I only use the option /DEBUG and set the other settings
in WinDbg windows debugger options.
However this is the machine I want to use as the target. SO I think
I need to be able to set all options for debugging at the command line
i.e. /DEBUGPORT=COM1 /BAUDRATE=57600.
Any ideas what WinDbg is doing to my system.
Thanks in advance for any help.
Denis
Denis Gleeson
My opinions only.
This line is fine on the target or debuggee machine. Ensure you do not have
this line for the host or debugging machine or as you say, com1 will
disappear and WinDBG will not see it.
Hope this helps,
Carl
<denis....@dna.ie> wrote in message
news:3be7c7db$1...@ni-news.utvinternet.com...
This is by design.
/DEBUGPORT switch transfers the UART hardware ownership to KD, thus Serial driver cannot access the UART and COM1 device disappears.
Max
Maybe /CRASHDEBUG in boot.ini can do it.
See http://www.sysinternals.com/ntw2k/info/bootini.shtml
Leo Havmøller.
Thanks for the help.
It was my setup of the Host that was causing the problem.
Doing the following on the host is not a good idea.
>> multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000
>> Professional" /fastdetect /DEBUGPORT=COM1 /BAUDRATE=57600
Denis
>This is by design.
> Max