home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!uwm.edu!rutgers!cmcl2!panix!rjo
- From: rjo@panix.com (Robert Olivier)
- Newsgroups: comp.os.os2.programmer
- Subject: Re: Help: Kernel Debugger
- Message-ID: <1992Sep8.143441.14463@panix.com>
- Date: 8 Sep 92 14:34:41 GMT
- Article-I.D.: panix.1992Sep8.143441.14463
- References: <1992Sep7.145724.22530@hns.com>
- Organization: PANIX Public Access Unix, NYC
- Lines: 38
-
- In <1992Sep7.145724.22530@hns.com> oneil@hns.com (Pat O'Neil) writes:
-
- >Anyone have any experience with the OS/2/2.0 Debug Kernel? I have installed
- >it and can't get it to respond to an async terminal on COM1. I've
- >read the directions pretty carefully and done everything they say, including:
-
- >- Install the debug kernel in the root directory of the hard disk
-
- >- Add the "/C1" option to the "device=pmdd.sys" command in config.sys
-
- >- Put a null modem in the cable that connects com1 and the async terminal
-
- >- Set the async terminal to 9600 b/s, no parity, 8 bits, 1 stop.
-
- >Despite all this, I can't seem to raise the debugger. None of the attention
- >characters work -- not 'r', 'p' <SP> or ^C. I am absolutely sure I am
- >hooked up to COM1.
-
- >One thing I tried was to disable loading of the COM drivers by deleting the line:
- >"device=\os2\com.sys" from config.sys. That didn't do any good.
-
- >I would greatly appreciate any help.
-
- >Pat O'Neil
- >Hughes Network Systems
- >Germantown, Md.
-
- I had similar problems when I installed my debug kernel. I found that it
- didn't like my Tandy NULL modem and I had to construct my own that only passed
- pins 2,3 (crossed) and 7 through.
-
- Hope this helps
-
- rjo@panix.com
- --
- Robert J. Olivier
-
- rjo@panix.com
-