Stephen Keung
Stephen Keung wrote:
>
> The interesting part of this problem is that the setup was working fine
> with my old WinNT4 box as my development machine. As soon as I switched
> to my new W2k laptop (keeping the same cable), the whole debug
> environment falls apart. I am sure the serial link still works fine as I
> can optionally redirect the CLI (interface) to my W2k hyperterminal.
> Thanks for the follow-up though.
>
> "Stephen Howe [TeamSybase]" wrote:
> >
> > "Stephen Keung" <ssk...@yahoo.com> wrote in message
> > news:3D08DB41...@yahoo.com...
> > > Thanks for the advise. However, I don't have much luck with the 3-link
> > > approach either. The debugger (#3) could talk to vdmserv (#2) fine (at
> > > least a session is started), but #2 couldn't talk to the target (#1)
> > > with an "Unable to connect to server" message. Do you think it might
> > > have something to do with the c:\watcom\binw\vdmserv?
> >
> > It could be the serial cable. Do you have two 2 DOS PC's (alternatively do
> > you have 2 Windows 95/98 PC's you can start in MSDOS mode???). If you cannot
> > debug a 16-bit DOS or 32-bit DOS app across this combination then it is
> > unlikely to work for Windows 2000.
> >
> > Your cable has to be a null modem cable (pins 2 & 3 are crossed). This is
> > from the debugger manual:
> >
> > Task Machine Debugger Machine
> > Serial Serial
> > Connector Connector
> >
> > Pin # Pin #
> >
> > 1 (PG) <---------->1 (PG)
> >
> > 2 (TxD)<---------->3 (RxD)
> >
> > 3 (RxD)<---------->2 (TxD)
> >
> > ------- 4 (RTS) 4 (RTS) -------
> > | |
> > ------> 5 (CTS) 5 (CTS) <------
> >
> > ------> 6 (DSR) 6 (DSR) <------
> > | |
> > | 7 (SG) <---------->7 (SG) |
> > | |
> > |------> 8 (DCD) 8 (DCD) <------|
> > | |
> > ------ 20 (DTR) 20 (DTR) -------
> >
> > Stephen Howe [TeamSybase]
> > London, UK
> >
> > General reminder (READ THIS, IT IS NOT FOR SHOW):
> > 1. Make sure you specify the version number of the product
> > 2. Make sure you specify the host operating system
> > 3. Make sure you specify the type of target executable
> >
> > Thank you
I don't think it is doable. The serial support is not for Win32. But it
should not be hard to do. All that is required is a Win32 driver.
It might be doable in 3 stage not 2.