On Wed, Jan 30, 2002 at 07:15:00AM -0500, Michel Samson wrote: > ftp://ftp.tu-dresden.de/pub/soft/SimTel/msdos/graphics/piclb193.zip > (i find those northern European people have speedy mirror sites) > > ftp://garbo.uwasa.fi/pc/graphics/improc42.zip > (a favourite too)... > > `PicLab' is precious to me since it's available as an `XT' program, > `ImProces' would be nice on a LEGACY machine (with ~CGA~) but i'm afraid > i'm in love with `GrafX' at the moment... and source-code is available; > i wouldn't try to "enhance" its code but i may like it better in French!
Bonjour Michel, I used Piclab for cutting after adding text with Improces. I also have Grafx installed, but found it a bit too much for the simple editing I was doing. > HE> A unix mailbox or folder is more or less a plain text file where > HE> each message begins with "From ....." (not From: ...). > > ****************************************************[ `Commo.CAP' ]* > Return-Path: <...> > Received: from... > I'm forced to conclude that this probably isn't what i'd need! :-( You don't have the "From..." line because you are capturing the messages. A POP client (uka_ppp, NetMail, Ka9q, etc.) would add it when it delivered the message to your PC. You could probably add your own by changing the "Return-Path:". > The `NetMail for DOS v2.12' documentation mentions Unix and my very > limited experience of Unix made me notice the terminating dot but that's > not making this ~TelNet~ capture a "Unix MailBox" message, i guess. %-) As far as I know, the terminating dot is never transmitted. > HE> ...I don't see the point in converting them to SOUP... > > I'd rather not myself. Essentially, the .QWK interface lists those > messages individually, in sorted order and with color-coded areas... Most Internet mailreaders do this with the messages in text format. I have converted QWK to text and used a mailreader to read Fidonet (creating the .REP for replies is the tricky part). [Linux] > I can > understand that `ZTelNet' is very much like `MiniCOM', unless it will be > possible to use it as a ~TelNet~ "shim" for something like`C-Kermit' and > in that case that would make it a lot more interresting in my eye. As i > wrote, with `MiniCOM' i must also have a Vitual ~TelNet MoDem "shim" but > you seem to make a distinction as to what `ZTelNet' actually is and that > makes me ask you this other question: what's this `ZTelNet', precisely? Ztelnet is a tcp/ip client. It is just like standard telnet except that it has built-in zmodem. Like other tcp/ip programs, it doesn't require a "shim" to use the OS's native tcp/ip. Minicom is a serial communications program with built-in zmodem (and kermit?). It may be possible to use minicom as a telnet client using a "shim", but I don't see the need. If a ztelnet-like program existed for DOS, I wouldn't find it necessary to use a "shim" + comm program for telnet. > HE> ...<http://www.ncf.ca/~ag221/>... > > Ho, i wanted you to know that i checked your "DOS TCP/IP Resources" > link awhile ago (resource.html) and i'm sorry to say that the "I live in > Siberia" link (http://stud1.tuwien.ac.at/~e8926506/siberia.htm) is down. > > Luckily for me, i have a few copies of this instructive document... I think there are probably a few more dead links on my page. I'm not sure if I saved the document, but I know I still have the .gif of the walking polar bear. :-) 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
