Fernando Saldanha wrote in a message to All:

 FS> I installed the Debug kernel and was able to use the Borland
 FS> debugger. Unfortunately, the Debug kernel uses a COM port
 FS> for output (I don't know why). If the machine has only one
 FS> COM port it uses COM1, if it has two, it uses COM2. In my
 FS> case, my modem is connected to COM2. Due to this, I was
 FS> unable to continue using my modem. I was still able to dial
 FS> and access BBSs, but as I attempted to do a download the
 FS> whole system would freeze after a few characters. CAD would
 FS> not work, so I had to press the reset button. 
Debugger waits for commands.

 FS> As I reinstalled the standard kernel, the problem disappeared. 
 FS> By the way, I tried a couple of different BBSs with the same
 FS> results. 

 FS> Is there any way to fix these problems, either by having the
 FS> standard kernel support DosDebug, or by preventing the Debug
 FS> kernel from sending output to COM2? Thanks for any help.

There is no way to use the debug kernel when receiving data from COM2. The
debug kernel (really a whole debugger) waits for Ctrl-C (ASCII 3) appearing
on COM2 to enter the debugger (# prompt). This Ctrl-C character will sooner
or later appear in your download and your system freezes.
Somebody should type a "g\n" to COM2 to continue 

It is a nice thing to debug drivers but in your case you have to find a way
to use the standard kernel.


Tschuesz,
           Vitus

--- timEd/2-g1