20 Mar 16 11:03, you wrote to me:

 ml>> as those files originate at 1:120/544, the operator of that system is
 ml>> who needs to be contacted about the problem... preferrable by someone
 ml>> with those two TICs delivered from that system to theirs... first hop
 ml>> data is best in this instance because it will prove whether there is
 ml>> some sort of data corruption going on on the first hop system or
 ml>> not... if there are any other systems connected to 1:120/544 for the
 ml>> I-BINKD area, they will have first hand TICs to work with and see if
 ml>> the problem exists in them...

 Al> Sounds like Janis has net mailed Jame about the problem. I suspect
 Al> it's a typo but in any case once we hear what he has to say we'll know
 Al> how to proceed.

hehehe...

 Al> Do you know of any reason the replaces line would be BINKD,TXT instead
 Al> of BINKD.TXT? My best guess is that it is a typo.

typo is the only legitimate excuse i can think of... i'm more in awe that
allfix doesn't have a problem with it and properly tosses the new files into
the directory overwriting the existing ones as desired... it might be a setting
that i have in place for that area so that it is done no matter if the TIC has
a replaces line or not...

)\/(ark

Always Mount a Scratch Monkey

... Go the extra mile. It's never crowded.
---