Conference hydra::amiga_v1

    I can't answer your question, but...
    
    Why don't you use Access or Comm from Plink?  They both have the
    WXmodem protocall which is much faster than Xmodem.  Both are available
    on Plink and are pretty complete terminal programs.  Access is
    BEAUTIFUL.  It uses 16 colors at one time.  I know, I know...who
    needs all those colors in a terminal?  I think it is really nice
    to look at.  And it's free.  And transfers are faster, saving you
    more money.
    
    I use Smokey for calling into work.  Access for everything else.
    
    	Randy
    
    Of course, none of this is any help, if you can't successfully download
    one of these terminals from Plink to start with...
    

Ahhhh...   good info...

I got the impression that Xmodem and straight ascii was the only means of
transferring files from PLINK.  The manual I received with my subscription
to PLINK was sparse to say the least.  Does PLINK sense you are initiating
a WXmodem vs an Xmodem transfer automatically?

I haven't looked into the handshake on transfer programs at all and just
treat them as black boxes so bear with me....

I'll try to download Access and Comm tonight.


Any comments out there on the "best" program to use for up/down loading
from PLINK and also from our VAXes???  I have been using Diga! and Smokey
with average results (i.e. I get the file sometimes..).


Thanks!!!

John

    ACO is a modified version of Comm.  It supports WXmodem, and a new
    feature called ACO mode, which is a graphic conferencing protocol
    in which up to twenty 'faces' of other conference attendees are
    visible on the screen.
    
    I've posted a prior note on ACO, if you're willing to search for
    it.
    

    WXmodem is automatic.  You tell Plink you want to download using
    Xmodem.  Select WXmodem/Receive from your emulator menu.  The rest
    is automatic, and foolproof.  Since I've started using it, every
    transfer has worked.
    
    More about Access and Comm.  Under the screen display, they are
    identical.  The both use the same format for phone directory files
    and key macros.  Access has a two rows of onscreen gadgets for
    selecting functions.  It will also give you a nice interlaced split
    screen, the top of the screen is workbench, the bottom is the
    terminal...all selected from the gadgets.  The file requesters (used
    when transfering) are BEAUTIFUL.  The gadgets are color icons of
    disks, labeled with the appropriate drive.  Again, 16 colors are
    used to make the package look great.  You can select (again, on-screen)
    text attributes and color from another menu.  It's not bad for free.
    
    When you need VT100/200 emulation, it's hard to beat Smokey.  When
    using Plink, it's hard to beat some of their own public domain
    terminals.
    
    Watch out for your next phone bill!
    

        How does one down load all new notices? I read a message on how
        to do it, but didn't write it down. It would be cheaper to read
        them at my leisure locally.

        Mike

    What are the advantages of XMODEM over Kermit? I personally have
    never had any problems downloading with kermit but have had frequent
    problems (as stated in .0) with XMODEM.
    
    It seems that most BBS's use XMODEM.
    
    Chris

    I have had problems with Xmodem.  I have never had a problem with
    WXmodem and Plink downloads.  Kermit is not an option with Plink.
    I use Kermit for transfers to and from the VAX without trouble,
    as long as it is set up right.
    

    Re: .6
    
    Kermit vs. XMODEM is a topic showing up in several recent notes.
    Each protocol has advantages and disadvantages.
    
    Kermit is a public-domain protocol originating at Columbia University.
    Versions are available for most minicomputers and micros.  This
    has the advantages of excellent documentation (Digital Press book),
    wide academic and DEC user community support, good multi-file transfer
    and good compatibility with the default settings of VAX terminal
    lines (7 bit ASCII).

    The disadvantage of Kermit is its 7-bit-ness. When transferring binary
    files, characters with the high bit set, Kermit sends a prefix
    character.  This lengthens file transfer time by 10 - 50 percent
    compared to XMODEM. 

    Ward Christensen started XMODEM as a temporary file transfer solution
    about 10 years ago.  The protocol became the de facto standard for
    micro-based bulletin board systems.  It has undergone a number of
    extensions to improve reliability (CRC checksum) and multi-file
    transfers (YMODEM, ZMODEM).  Its advantages are wide use in the
    micro community and good implementations on most micros.
    
    Its disadvantages are poor documentation, spotty support since
    the demise of CP/M as a growing market, lack of support within DEC
    and the DEC user community, and an absolute requirement for 8-bit
    data.  The Amiga VT-100 implementation of XMODEM is not particularly
    robust (sorry, Dave).
    
    Both protocols have problems with XON-XOFF flow control, terminal
    servers and TSN.  All the above may be somewhat oversimplified.
    
    For more information, look in the Software Toolshed (VTX and possibly
    Notes) and the Kermit notesfile.  Kermit and XMODEM software is
    located in the Toolshed for VAXen and in the Kermit: and XMODEM:
    directories of either PAR5:: or MKTUP1::.

    Hope this helps.
    --Wes

    Re: .5 (downloading new notices)
    
    (start capturing)
    /go 68;lib;nopause;nomore;read new
    (end capturing)

    When I first started using ARC version 6 ? I saw no error messages
    unless the file actually was bad. The first time I ever saw the
    now infamous"0 bytes skipped" message was on a file I downloaded
    from the net.At this time the same person had uploaded a later
    version of ARC,and I assume that they are using this version.I never
    could figure out if it was the ARC program or a series of events
    in the way people transfered their files that caused this message.
    Now  I see it so often that I think it may be a bug in the arc program.
    While it is not a major problem(programs work)it is unsettling the
    first few times it is encountered.
    
    bill

    I think its related to "chopping" the files down after using xmodem
    which pads it out to even 128 byte chunks...I remember something
    in the comm doc about this, and how they automatically turn chop
    off for files with an .arc extension.....
    
    anyway...your right, the files are still ok.