Jeff, at 18:38 on Tue, Feb 21 1995, you wrote to Bill Grimsley ...

BG> Yet it transfers any size mail packet OK!

JG> Seems to (see below though). I just sent another one that 
JG> was over the 8192 bytes mark, so I don't see how it could be 
JG> the modems not talking correctly.

Neither do I.

JG> I even tried sticking the file in a message packet once :-)

Worth a try though.

JG> As the message packet is just a zip file I added it to the 
JG> message file in the normal manner eg 'zip -u 00000000.mo0  
JG> kwq12i.exe'. It added in without a hitch. The transfer died 
JG> with the usual message.

I wonder if it's that specific file itself (can't imagine why though). 
Have you tried sending anything else?

BG> AFA your modem is concerned, it's just another file, so the problem 
BG> is with Bink IMO.  What version again, 2.50 wasn't it? 

JG> 2.56 (with 'error' or 'transfer cancelled') and 2.50 (with 
JG> 'transfer cancelled'). The transfer cancelled on the 2.56 
JG> version occured the other day.

More or less eliminates Bink as the problem then.

BG> Have you tried either 2.50 EE or 2.59 yet?  It can't be your file 
BG> system either, as I run all HPFS here without any problems at all.

JG> Yeah, I'll try those versions soon.

I doubt they'll be any different though.  Just a thought, have you EVER
managed to send any files correctly on prior occasions?

BG>  your \outbound directory?  Its contents are similar to this...

BG> #\point\outbound\00000000.su1
BG> ;SEND generated by node 3:640/305.9{at}fidonet using BinkleyTerm-OS/2 
BG> Ver. 2.5 
BG> \POINT\TEST.ZIP

JG> Alomst...the third line on mine always (I think) has a drive 
JG> designation in it ie E:\point\test.zip. So does the message 
JG> packet though. 

If you don't specifically enter drive or path info, I believe the defaults
are taken from binkley.cfg, so that's not the problem. 

JG>> I give up.

BG> I wouldn't.  It's stuff like this which really gets the 
BG> juices flowing.  Don't you love a challenge?  |-)

JG> About two hours after I said that, I tried again :-) I'd 
JG> thought of something else to try. It brought on the 
JG> 'transfer cancelled' message instead of the 'error' message 
JG> using 2.56. I don't know if thats good or bad though :-)

Depends on your interpretation of bad, I guess, although it certainly ain't
good, that's for sure.  One final suggestion - have you tried calling with
Bink's terminal mode, and uploading the file manually?

You might also try placing a MODE command as the first line in your BT.CMD
batch file, as follows...

MODE COM2:38400,N,8,1,DTR=OFF,RTS=HS,OCTS=ON,TO=ON,XON=OFF,BUFFER=ON

The other thing I'd be doing is unzipping the offending file, re-archiving
it, and maybe even renaming it to something else.  I doubt that'll help,
but you have to cover all possibilities now.

Regards, Bill

--- Msgedsq/2 2.2e