On Sun, Jan 06, 2002 at 09:30:00AM -0500, Michel Samson wrote:
Bonjour Michel,
> HE> I used Piclab for cutting after adding text with Improces. I also
> HE> have Grafx installed, but found it a bit too much for the simple
> HE> editing I was doing.
>
> We find ourselves at opposite poles of a same spectrum. I couldn't
> get `PicLab' or `ImProces' to work but i was using `GrafX' in minutes...
Chacun son gout. :-)
> HE> A unix mailbox... ...begins with "From ....." (not From: ...).
> MS> I'm forced to conclude that this probably isn't what i'd need!
> HE> You don't have the "From..." line because you are capturing the
> HE> messages. A POP client (uka_ppp, NetMail, Ka9q, etc.) would add it
> HE> when it delivered the message to your PC.
>
> I compared both the `NetMail for DOS v2.12' files with my `{Commo}'
> capture files and it seems they're just the same, including the headers.
I just tried NetMail and it seems that you are correct. However, in
my netmail\mail directory there are two small programs ld.exe and
nm2mail.exe that are used to convert the individual .txt/.wrk files
to a single unix mailbox. These programs are included with John Lewis'
NetMail + Olim mailreader package, nmo-e03.zip.
> HE> It is just like standard telnet except that it has built-in zmodem.
>
> And it has support for external file transfer protocols as well, as
> i recall your previous post...
Perhaps I was mistaken. All I know is that after starting zmodem on
the server (bbs), you escape back to ztelnet (^]) and "rz -v" or
"sz -v" for built-in zmodem. I never tried a simple "rz" or "sz"
or any other external transfer.
> Since the ~TelNet~ protocol is built-in,
> and the `ZMoDem' protocol with it, either there's also support to access
> a HardWare Modem thru a serial-port or it can work as a "socket", if you
> prefer, so that any external protocol driver is actually usefull... :^)
I prefer to think of ztelnet simply as a tcp/ip client that works
over any tcp/ip network.
> HE> If a ztelnet-like program existed for DOS, I wouldn't find it
> HE> necessary to use a "shim" + comm program for telnet.
>
> `MS-Kermit' accesses, euh... the ~TCP~/~IP~ stack (?) directly and
The way I understand it, is that MS-Kermit (telnet version) includes
the Wattcp tcp/ip stack and talks to the packet driver.
> `IVT' does this as well but then one gets `ZMoDem', instead of `Kermit'.
>
> `MiniCOM' doesn't include `ZMoDem' nor `C-Kermit' but i thought the
> Virtual ~TelNet~ MoDem "shim" would have made them happy side-by side...
> I believe `C-Kermit' is just like its DOS counterpart, that's a terminal
> but a guy can also use it as any external file transfer protocol driver.
rz/sz works well enough with minicom over dialup. I don't have
C-Kermit installed, although I have used it on a shell account.
I believe it may be possible to use a "shim" + minicom for telnet,
but this mixing of dialup and network apps seems overly complicated
and mostly unnecessary to me.
Howard E.
--
<http://www.ncf.ca/~ag221/>
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
