Conference hydra::amiga_v1

    The Metacomco Shell comes with a handler for an AUX: device
    which will, when activated, create a working CLI from the
    serial port. You can't do it with CON:/SER: because, naturally,
    there can only be one console active at a time and once you
    deselect it by clicking somewhere (anywhere) it's going to
    be a pain to get back to it.
    
    ***RUMOR TIME***
    
    I thought I heard someone wrote a PD AUX-handler and released
    it on USENET, can anyone verify?

    
    Yeah, there is a public domain version.  I haven't used it, but
    I noticed it was still laying in my account.  You can get it for
    a while from
    
       ant::bipolar:[smcafee.public]aux.shar

    regards,
    
    steve mcafee

	Has anybody used this PD AUX?  I would like to use MODEM
	on the VAX on occasion to get to my Amiga but haven't had
	any success in getting the Scholar modem attached to the
	Amiga to answer the phone.  Is there something I'm missing
	in seting up the Scholar to auto answer?  ( I never did get this
	to work with the PD BBS package that was floating around a few
	months ado either ) Also need some suggestions on how to make 
	this operation secure after I get it working. 

	Thanks,
	Dick

    Hmmm ... answers okay for me and always on the second ring. Just
    make sure you have autoanswer ON in the setup menu and the Data/Talk
    switch OUT. It will only autoanswer with the DATA/TALK switch OUT.
    
    Paul

    Hmmm ... discovered a problem that may more accurately reflect the
    problem you are having:
    
    I have a DF224 connected to my Amiga and another DF224 connected
    to my PRO350. When I attempt to call one from the other the phone
    rings one very short ring and the screen displays "BUSY." Needless
    to say, I can use either system to call out and connect to other
    computers and networks without any problem. However, using a DF224
    to connect to another DF224 appears to result in a BUSY response
    (even though the line is not busy and the phone rings).
    
    Anyone have some insight on this one? Is it an inherent problem
    with the DF224. I can't imagine why two DF224 shouldn't be able
    to communicate with one another.
    
    Paul

    I wrote the PD AUX-HANDLER you saw posted to the usenet.
    You can find the lastest version, slight mods, smaller executable.
    In my directory:
      CGFSV1::DISK$73G:[DREW.AMIGA.AUX]*.*
    	AUX_HANDLER. is the file you'd put in your l: directory
        and call aux-handler
    	Mountlist. should be added to your dev:mountlist file.
    

    I found that AUX: needed to be separated in the MOUNTLIST file from
    VD0: using a # sign. Tis true?

    Well, the DF224 modem problem was cured rather easily. By appending
    a "W" to the phone number, enough of a delay was added to allow
    the other DF224 to answer properly. For example, using T2233439!
    didn't work but T2233439W! did work.
    
    At any rate, the AUX: worked terrific. Of course without an ansi
    text editor, about all I could do was use a few CLI commands like
    DIR and TYPE. Invoking an editor like EMACS causes it to appear
    over on the Amiga, but merely hangs the AUX: window on the remote
    terminal. 
    
    At any rate it does work and there is a need for an editor that
    can be used through the SER: port.
    
    Paul

    Oh, one other things, after connecting, there was about 45 seconds
    of garbage across the remote's screen which final ended with the
    appearance of the CLI prompt.

    I'm obviously missing some fundamental step. Using DBW's VT100, I set
    up the modem with ^B then % to get the menu, make sure auto answer is
    on then try to get out with a ^Z or <ret> at the end of the menu after
    taking all of the defaults. It doesn't come back and say Ready as in the
    documentation. However, if I exit VT100 at this point and start up AUX,
    it does answer the phone in two rings from VAX MODEM.  This is as far
    as I've gotten since I have yet to figure out the BAUD, PARITY, STOP BITS,
    etc. that are present on the Amiga end and somewhere in the middle of
    this, AUX decided for some reason to hang the Amiga ( warm boot required
    to get any activity ).

    I would be really interested in other methods used to configure this and
    also the associated VAX MODEM "MODEMINI.DAT" file you are using. 

    Thanks,
    Dick

    After hitting several RETURNs to bring you through the remaining
    menu selections and out of the menu, you'll need to hit another
    CTRL-B to bring up the READY prompt again. 
    
   
    Paul

                             -< CTRL-B not CTRL-Z >-

Ok I'll give it a try but that's not what the book says!?

Dick

    I added some  code to micro emacs 3.8b so that it can
    tell if it's being 'Run or just invoked via 1> emacs'. Then if
    it is Run it opens a new window, if it's invoked it just uses the
    current window or AUX: device. So if you are dailed up all you type
    is 1> emacs and va vooom you get a full microemacs just like at
    home. That's as long as your on a ANSI (VT100) compatable terminal.
    About the only thing that doesnt work is the arrow keys, so you
    have to use the CTRL-N CTRL-B ect.. equivalents. But then again
    if you compile microemacs 3.8b on a VAX with the VT100 option the
    arrow keys still dont work. Maybe I'll fix that some time. Anyway
    this hack only took about 5 lines of code. And it all works because
    I included ACTION_SET_SCREEN support in my AUX: handler just like
    the 1.2 console.device.
    
    If anyone's interested I'll upload it.
    
    Steve Drew
    

RE: < Note 526.13 by CGOU01::DREW "Steve Drew" >
...    If anyone's interested I'll upload it.

     Please do.

I think I also found my problem ( if all else fails, read the documents ).
I don't remember a baud rate selection for the serial port in preferences
but I'll look.

Dick

    Yes .. please upload Steve. Thanks.
    
    RE: .14
    
    Yes, you can select the SERIAL PORT box (upper left side of the
    main preferences screen. Choosing that displays another window that
    allows you to alter a number of params including baud rate. I was
    using 2400 baud with a DF224.
    
    Paul

    
    MicroEmacs version 3.8b with aux: mod's. is now available in
    	
    	CGFSV1::DISK$73G:[DREW.AMIGA]EMACS.38B;1
    
    Steve.
    

Still no luck reaching my Amiga with MODEM and AUX.  All I seem to get is a 
stream of garbage that never stops.  Below is my current setup so that some
kind soul can tell me where I've screwed up.

!  Scholar modem with default settings and auto-answer enabled.
!  Command line to start AUX  "NEWCLI AUX:".
!  Running under ASDG-RRD using SHELL_206.
!
!  MODEMINI.DAT				PREFERENCES SELECTIONS
!
HELP=N
DEFAULT=Y
LINE=A
DEVICE=TTB6:
SPEED=2400				!	2400
BITS=8N					!	8 bits, no parity
XON=Y					!	XON/XOFF
SCROLL=23
PHONE=x-xxx-xxx-xxxx

When I use DBW's VT100 emulator, my script sends a ^B to the modem to get it
in a ready state. I was wondering how AUX does anything more than bring up the
serial line at preferences settings and if it were possible to redirect modem
initialization commands through AUX.

Thanks,
Dick

    Do a CTRL/C at the Amiga, and that will clear up the garbage going
    out on the prot. Dunno why it works that way.

    Make that "going out the port."

You mean from my shell prompt of $, after entering NEWCLI AUX:, typing ^C at
the next shell prompt of $ will get intercepted by AUX and clear the line?

Do I really want to use this that badly?

    Actually, I believe any keyboard input on the Amiga side will terminate
    the flow of garbage and leave you with a nice little CLI prompt
    at the remote console.

Guess I'll have to teach the dog to type while I'm at work ;^}