Path: internal1.nntp.ash.giganews.com!border2.nntp.ash.giganews.com!border1.nntp.ash.giganews.com!firehose2!nntp4!intern1.nntp.aus1.giganews.com!border1.nntp.aus1.giganews.com!nntp.giganews.com!newsfeed.tpinternet.pl!newsfeed.gazeta.pl!news.atman.pl!news.intercom.pl!f124.n480!f127.n480!f112.n480!f200.n2432!f605.n774!f500.n123!f2000.n106!f12.n3634!not-for-mail
Newsgroups: fido.4dos
Distribution: fido
From: mark lewis 
Date: Mon, 08 Dec 03 20:04:18 +0100
Subject: long BTM file
Message-ID: 
References: 
 2443/1181
Lines: 19
Xref: intern1.nntp.aus1.giganews.com fido.4dos:460


 JB> I just posted a fairly long BTM file in a message
 JB> if it was corrupt4ed or you were unable to read
 JB> it because of its size (or it didn't arrive)
 JB> let me know and I'll slice it up and try again.

it made it thru to here with no problems... i have, however, located a problem
in it, i think...

STEP_2.BTM                                   ³11-15-03³AP7


it does ask about executing it but it didn't actually execute it... FWIW: i've
also added FD style logging capabilities to it... if i can figure out how to
work DIFF on the linux box and get it to give me something that i recognise, i
can send you the update...

)\/(ark