CKOKer32.EXE has a problem (read: bug) in it somewhere...
...i didn't expect ~TelNet~ using `SIO'/`VMoDem' to redirect data to ~COM1~... A "Named Pipe" or else was mentioned...
Under OS/2, using SIO/VMODEM, everything uses comports... It's all
as if you're using a dialup BBS (which is why Telegard/2 works so
well with it). You don't use any sockets, named pipes, et al.
I am actually having a harder time getting the configuration of
TG/2's protocol setup rather than getting Kermit to work. For that,
we should probably move this over to TG_SUPPORT.
Quoting Michel Samson from a message to Sean Dennis <--
Oh, then wouldn't it be simpler just to use `MS-Kermit.EXE'
Then i'll meet you in the `TeleGard Support' area and hope for
less noise than what i've been able to observe everywhere else this month!...
...wouldn't it be simpler just to use `MS-Kermit.EXE'...
I have C-Kermit installed on my OS/2 box, but isn't that more the
actual terminal program than the protocol driver?
...i'll meet you in the `TeleGard Support' area and hope for less
noise than what i've been able to observe everywhere else...
It's pretty quiet in there.
|Location:||Riverside County, California|
|Nodes:||15 (0 / 15)|