TIP: Click on subject to list as thread! ANSI
echo: pdnecho
to: Janis Kracht
from: Maurice Kinal
date: 2009-11-15 16:06:46
subject: very interesting

Hey Janis!

You may have noticed that I've moved this discussion to here.  Offhand I am
guessing it is a good idea.

> I did some testing here and it did work for bluewave archived
> packets.

> First I had to set my GF (grab format) to BlueWave in the
> Utilitey menu

I saw that and at one session did change it but changed it back to text
after since I couldn't find the grab via ftp.  However ...

> zip file was in my telnet program download directory when I
> exited.

> down/testgrab.su5

Errrrr ... where is that wrt the chroot jailed directory?  Also the text
archive doesn't seem to require a telnet login and can be tweaked into
action with either a wget or ftp login given a username and password which
makes it perfect for scripting into a client.

The only outstanding problem is the uploaded reply's expected filename and format.

However I am willing to try the more traditional method of offlining as
long as it doesn't require zmodem.  In that case I am going to have to know
where to upload to and if an ftp session cannot work without telnetting
then I cannot see how any of this will be of any consequence.

For my part I'd rather leave the faking it to the DOS-think people and
totally get rid of anything other than 8 bit characters in the headers,
etc. and then use transfers that are less hoggy resourse-wise than faking
out a serial connection - especially nonstandardized ones - on a tcpip
connection.  We both know this is doable since we've done it this way in
the past.  In that case it was Fido formats but the actual transfers of
those pkt's was ftp.  That worked better, no doubt about it, and I was
tranferring raw Fido compliant pkt's.  I still have the scripts here that
generated those but personally would much rather to ditch the headers for
ones that stuck to purely 8 bit characters and strings (<- null
terminated) not unlike what I see in the BBS's echo bases. Far more
standardization there with REAL standards as opposed to FTN so-called
standards that aren't standards and never were.  The whole argument about
backwards compatibilty is a joke at best.

Like I've been saying all along, I am in no rush about any of this, and if
I am just here to repeat past mistakes then I'll stick to the way I am
doing this now.  Seems to work excellent all things considered and doesn't
require ANY DOS-think to be compatible across the board. No faking either. 
:-)

Life is good,
Maurice

--- BBBS/LiI v4.01 Flag
* Origin: Prism bbs (1:261/38)
SEEN-BY: 10/1 11/200 331 34/999 53/558 120/228 123/500 128/2 187 140/1 222/2
SEEN-BY: 226/0 236/150 249/303 250/306 261/20 38 100 1404 1406 1410 1418
SEEN-BY: 266/1413 280/1027 320/119 393/68 396/45 633/260 267 285 712/848
SEEN-BY: 800/432 801/161 189 2222/700 2320/100 5030/1256
@PATH: 261/38 633/260 267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.