LC.YRS@forsythe.stanford.edu (Richard Stanton) (02/16/90)
I've been experimenting with protocols other than KERMIT, particularly to try to use one of the background transfer programs that exist. However, there seem to be problems using MS-KERMIT 3.0 with these programs. I have tried using DSZ and a background program called RCOMM (v 2). In each case, everything works fine if I call the appropriate program from the DOS prompt, but odd things sometimes happen if I call them from KERMIT. DSZ warns about possible locking up. I have not experienced this, but the download usually crashes when the 'rb' command tries to download the filename (this works fine from the DOS prompt). Similarly, if I start the transfer (sb or sx) from within KERMIT, then pop up RCOMM (either from within KERMIT or at the DOS prompt), and try to receive the file, the transfer works fine, but every block complains about data communications errors. If I do the whole process from within RCOMM (i.e. type the sb / sx here as well), the transfer proceeds without any complaints. Does anybody know why this is happening (according to DSZ.DOC, KERMIT send XOFF characters at times, but I don't see why this should affect a program that pops up rather than getting shelled to), and can anybody suggest a solution that would allow use of these other protocols with no hassle from within KERMIT 3.0? Please post replies, as this may be of interest to other people. Richard Stanton If this just appeared on c.b.i.p. (not that that seems exactly likely), I'm sorry. I forgot to type the .d