Subj : File transfer probs
To   : mark lewis
From : Gordon Lewicky
Date : Tue Dec 31 2002 07:37 pm

 Quoting mark lewis to Gordon Lewicky 
 Subj. File transfer probs, dated 31-Dec-2002 15:55 

Hi Mark,

 ml>> 1. file transfers which way?
 
 GL> Both ways don't work

 ml> what, if any, errors do you get... be specific...
 ml>> 2. what bbs software?
 
 GL> Ezycom v2.0 Others are running V2.0 just fine in Warp
 GL> currently.

 ml> using the internel protocol driver or external protocol drivers?

No errors what so ever. so far I have determined that it does not
make it to the Ezy's auxilary exe which contains the actual transfer
routines. Found this out by removing it and I still get the same
results, and also verified it with pmlm from sio. It just goes
right from the display line just prior to tha call for the
internal transfers to the display line showing # files transfered.

Something is causing it to jump right over the actual transfer
itself. It may or may not be Ezy specific as other Ezy telnets
work. It may be something in my actual vdm properties, tho all of those
are identical to my pstn node which works just fine.

I have further found out that my cdrom door which has it's own
internal transfer routines works, so that essentially proves
everything is working fine except for Ezy's routine, which then
leads me to suspect it might be case specific to my puter and ezy
and not ezy as a whole.

IOW, something is causing Ezy to jump over the call to the
transfer routine, maybe uart buffer, kbd buffer, or some memory
register, rts/cts dsr/dtr, something. It doesn't make any sense
since vmodem just replaces a physical modem with a very simplistic
virtual one, which already has proved itself on many other bbs packages,
including Ezy and various cpus. So it has to be specific to my box, that
may or may not be outside of the vdm settings.

The router works, the firewall works, the lan works, the sio
drivers work, vmodem works, file transfers from an external
door works and other ezy systems work!

So, the question is, what could it be about my box? :)

The only thing different about my pstn line and the telnet line,
is that the telnet line is stand alone, no mailer, and I don't
utilize baud trapping since vmodem always sends 57600.
And all are using locked ports.

This one is a head-scratcher indeed! :)

Cheers...
Gordon Lewicky (Pdk)

Sysop - Milky Way 1:153/307, NC 153, AdventureNet 33:500/150
email glewicky@telus.net   web www3.telus.net/public/glewicky/milkyway
telnet://milkyway.tzo.com,  binkp milkyway.tzo.com


--- EzyBlueWave/2 V2.00 00F90260
 * Origin: Milky Way, Langley, BC [604] 532-4367 (1:153/307)

.