• File transfer probs

    From Gordon Lewicky@1:153/307 to All on Mon Dec 30 01:08:26 2002
    Hi ya,

    I'm running Warp4, sio & vmodem, but cannot get my file transfers
    to work on the bbs. Twas wondering if there are any settings either
    in dos properties for the bbs bat (SIO related) or AT commands to
    vmodem which may solve the prob. Everything else works fine and all the settings for the file protocols are ok. I have VX00 & NANSI loaded as
    devices.

    Cheers...
    Gordon Lewicky (Pdk)

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


    --- EzyBlueWave/2 V2.00 00F90260
    * Origin: Milky Way, Langley, BC [604] 532-4367 (1:153/307)
  • From Chris Martin@1:219/308 to Gordon Lewicky on Mon Dec 30 07:19:42 2002
    Once upon a time, out on MARS.

    While reading the mail, wispering this:

    I'm running Warp4, sio & vmodem, but cannot get my file transfers
    to work on the bbs. Twas wondering if there are any settings either
    in dos properties for the bbs bat (SIO related) or AT commands to
    vmodem which may solve the prob. Everything else works fine and all the settings for the file protocols are ok. I have VX00 & NANSI loaded as devices.

    If you haven't already found it, there's a file called
    FULLOS2.ZIP, that was written by Tony Harrison (of WildCat! BBS
    fame) who put together a very useful help file with a slew of
    utilities included. It was meant for putting a DOS based BBS up,
    under OS/2, and may have some helpful insights. If you don't have
    it, do a web search for it by name, or email request it from me,
    using standard InternetRex format, FTSC to the node number below
    is ok, too.

    ex:

    To: MARSBBS@gte.net
    Subj:FREQ

    Text:FREQ FULLOS2.ZIP

    nothing else is needed, to get it via automatic reply email
    attach. If you would like to know what else is available, add the
    line "FREQ FILES" after the first one, and both should come your
    way.

    Chris Martin, The MARS Station BBS

    * WCE 2.1G1/2419 * Windows: the world's first commercially successful virus!

    --- ViaMAIL!/WC v1.60d
    * Origin: From an Echo heard on MARS. Call to be transported. (1:219/308)
  • From Gordon Lewicky@1:153/307 to Chris Martin on Mon Dec 30 13:52:54 2002
    Quoting Chris Martin to Gordon Lewicky
    Subj. File transfer probs, dated 30-Dec-2002 07:19

    Hi Chris,

    If you haven't already found it, there's a file called
    FULLOS2.ZIP

    Thanks, that was what I was looking for. Had it a long time ago
    but guess I lost it with a disk crash. Normally, I have all these
    types of things printed out and in a binder, but that one I
    remember as just having loose, since I was constanly refering to
    it, and guess I thru it out sometime. :)

    Crazy thing is, is that I have saved my working dos prop cfgs and can
    re-load them anytime. Currently using successful pstn settings.

    The file transfers work fine on my pstn node, so this is just
    telnet specific. The bbs doesn't even show the progress screen, it
    just jumps right to 0 files sent or received and the remote end
    doesn't even flicker at a hint of opening up it's up/down file
    manager.

    Only thing I can think of is maybe because it is behind a router
    using nat. Other then that, everything else works fine, including
    the doors. This is a strange and frustrating bug! :)

    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)
  • From mark lewis@1:3634/12 to Gordon Lewicky on Mon Dec 30 20:55:42 2002
    I'm running Warp4, sio & vmodem, but cannot get my file
    transfers to work on the bbs. Twas wondering if there
    are any settings either in dos properties for the bbs
    bat (SIO related) or AT commands to vmodem which may
    solve the prob. Everything else works fine and all the
    settings for the file protocols are ok. I have VX00 &
    NANSI loaded as devices.

    1. file transfers which way?

    2. what bbs software?

    3. which version of SIO?

    4. what fixpacks do you have applied?

    5. there are generally no at commands that can correct this type of problem.

    )\/(ark


    * Origin: (1:3634/12)
  • From Gordon Lewicky@1:153/307 to mark lewis on Tue Dec 31 04:31:32 2002
    Quoting mark lewis to Gordon Lewicky
    Subj. File transfer probs, dated 30-Dec-2002 20:55

    1. file transfers which way?

    Both ways don't work

    2. what bbs software?

    Ezycom v2.0 Others are running V2.0 just fine in Warp currently.

    3. which version of SIO?

    10 port 1.60 internal build 0.223

    4. what fixpacks do you have applied?

    Warp 4, FP 12, P166, 64 megs
    All is working fine except the file transfers. TCPIP is working,
    sharing connect via the router's NAT, port 23

    5. there are generally no at commands that can correct this type of problem.

    So I've read and re-read. :)
    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)
  • From Gord Hannah@1:17/23.1 to Gordon Lewicky on Tue Dec 31 06:56:38 2002
    Replying to a message from Gordon Lewicky 1:153/307 to Chris Martin,

    About File transfer probs, On Mon Dec 30 2002

    Only thing I can think of is maybe because it is behind a router
    using nat. Other then that, everything else works fine, including
    the doors. This is a strange and frustrating bug! :)

    That could also be the problem, perhaps some place you need to give it permission to allow it to send out, as well as receive.


    Hope this helps. Keep us posted.

    We are a fine board trying to make it better.
    http://www.pris.bc.ca/ghannah
    ghannah@pris.bc.ca
    Cheers! Gord
    -=Team OS/2=-
    --- timEd/2 1.10.y2k+
    * Origin: Marsh BBS (c), Dawson Creek, BC Canada (1:17/23.1)
  • From mark lewis@1:3634/12 to Gordon Lewicky on Tue Dec 31 15:55:56 2002
    1. file transfers which way?

    Both ways don't work

    what, if any, errors do you get... be specific...

    2. what bbs software?

    Ezycom v2.0 Others are running V2.0 just fine in Warp
    currently.

    using the internel protocol driver or external protocol drivers?

    3. which version of SIO?

    10 port 1.60 internal build 0.223

    ok...

    4. what fixpacks do you have applied?

    Warp 4, FP 12, P166, 64 megs
    All is working fine except the file transfers. TCPIP is
    working, sharing connect via the router's NAT, port 23

    ok...

    5. there are generally no at commands that can correct this type of
    problem.

    So I've read and re-read. :)

    <<gg>>

    )\/(ark


    * Origin: (1:3634/12)
  • From mark lewis@1:3634/12 to Gord Hannah on Tue Dec 31 15:57:08 2002
    Only thing I can think of is maybe because it is behind a router
    using nat. Other then that, everything else works fine, including
    the doors. This is a strange and frustrating bug! :)

    That could also be the problem, perhaps some place you need to
    give it permission to allow it to send out, as well as
    receive.

    shouldn't be part of the problem... its not a firewall... even if it was, it should be using port 23 already as that's the telnet port and that stuff is working...

    )\/(ark


    * Origin: (1:3634/12)
  • From Gordon Lewicky@1:153/307 to Gord Hannah on Tue Dec 31 15:20:42 2002
    Quoting Gord Hannah to Gordon Lewicky
    Subj. File transfer probs, dated 31-Dec-2002 06:56

    Only thing I can think of is maybe because it is behind a router
    using nat. Other then that, everything else works fine, including
    the doors. This is a strange and frustrating bug! :)

    That could also be the problem, perhaps some place you need to give it permission to allow it to send out, as well as receive.

    Nah, not the NAT or router. tracking it down tho. I have a cdrom
    door with it's own download routines and it works fine, so I has
    to be specific to ezy or it's files. I've floppy booted and
    chkdsk'ed but that didn't help. Now I wll try a delete of the main
    exe's then a chkdsk and then replace, just to rule out a disk
    access or file prob, but I don't think it is that.

    It's doesn't seem to be Ezy in general since it is working on
    other systems, but it's more spefic to my system, tho right now, i
    can't think of what it may be. The tcpip is fine, the lan is fine,
    everthing is fine except for telnet downloads within ezy proper.
    Argggg! :)

    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)
  • From Gordon Lewicky@1:153/307 to mark lewis on Tue Dec 31 19:37:32 2002
    Quoting mark lewis to Gordon Lewicky
    Subj. File transfer probs, dated 31-Dec-2002 15:55

    Hi Mark,

    1. file transfers which way?

    Both ways don't work

    what, if any, errors do you get... be specific...
    2. what bbs software?

    Ezycom v2.0 Others are running V2.0 just fine in Warp
    currently.

    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)