Conference hydra::amiga_v1

    Sure .. just edit your Workbench:s/startup-sequence file.

    I am genuinely amazed at how powerful the startup-sequence can be.
    
    You can make your Amiga yell at you at a specified time, if you
    like.  I even read of an interesting Startup-sequence that will
    automatically keep a log of all the time used at the computer, for
    tax purposes.

    I tried inserting various lines at different points in the
    startup-sequence file but couldn't make a CLI open at the right
    time. I was completely at a loss as to what command to use to get
    a workbench window to open. Is this explained in any of the manuals?
    If not, could you tell me what lines I need and where they go in
    the standard startup-sequence file? Thanks.
    
       mitch

	I dont'have the manuals with me, so i won't be precise.
	When you first introduce the WB disk a window is open automatically.
	By magic you're already under CLI. At this point the file
	S:STARTUP-SEQUENCE       (SS from this point on )
	is executed ( like login.com). The last line of the SS is :
	ENDCLI >NULL
	this command CLOSE the window and put you in WB icons world. 
	If you just want to have a window open, remove the last line,
	(put a semicolon in front of it, 't becomes a comment)
	; ENDCLI >NULL
	If you want to have more that one window ( CLI's) simply put
	
	NEWCLI 

	anywhere in your SS. If the size/position is not of your taste
	you can resize/ replace it. Procedure:

	COPY C:NEWCLI C:MYCLI

	now MYCLI does exactly as NEWCLI (  opens a new window)

	FILEZAP C:MYCLI 

	Filezap is a FILE_PATCHER. While browsing the file you may notice 
	close to the end a piece of data such as:

	200/0/100/40

	which are  Xpos, Ypos ( left top corner ) Xsize, Ysize of the
	window you're going to open . replace at your pleasure. 
	Try it  with
    
        MYCLI
    
	Remeber. If you 'run' a process from your SS ( such as:

	RUN CLOCK

	the WB CLI window will not close until you stop the spawned process.
	Hope this helps.
	marco

    I think he wants to know what the command is that cranks up a
    workbench.  I don't remember what it is (you delete it form the
    default startup-sequence to stay in the cli), but it's the last
    command in the default startup-sequence.
    
    len.
    

The command which kills the initial CLI is the ENDCLI command
in S:startup-sequence.  The command which loads the workbench is LOADWB.
The commands are not related, you may issue one, both, or none.

Dave

    It is not necessary make a copy of newcli to get a different size
    cli.  You can enter:
    
    NEWCLI "x1/y1/width/height/my_cli_title"
    
    x1,y1 locate the upper left corner.
    width and height are in pixels.
    my_cli_title will be placed in the title bar of the new cli.
    
    (I might not have the syntax for this exactly so play around with
    it if this doesn't work.)
    
    My startup-sequence opens up a TINY cli in the lower right corner
    of my screen.  When I need it its there.
    
    regards,
    
    Steve McAfee
     

    Re: .o
    The documentation that comes with the Amiga doesn't even touch on
    the use of the CLI and Startup-sequences.  I seggest you check the
    bookstores for one of the many books that has been written about
    AmigaDOS.

    Here's mine as an example ... POPCLI is a slick CLI/SCREEN SAVER
    utility.
    
    
    
    addbuffers df0: 25
    addbuffers df1: 25
    dir ram:
    chfont ericbd.font
    if EXISTS sys:system
        path sys:system add
    endif
    if EXISTS sys:utilities
        path sys:utilities add
    endif
    BindDrivers
    say Hello Paul. Welcome to the Amiga Workbench Version 1 point 2.
    echo " "
    echo "Last logged on:"
    type sys:s/Last-Startup-Date
    echo " "
    echo "Date and time now in memory:"
    date
    echo " "
    say Please enter the current date and time.
    echo " "
    failat 21
    date >nil: ?
    say Thank you Paul.
    if fail
    echo " "
    say Please try again.
    say This time, use a space to separate the date and time.
    echo " "
    date >nil: ?
    endif
    echo " "
    echo "Current date and time:"
    date
    date to sys:s/Last-Startup-Date
    echo " "
    LoadWb
    setmap usa0
    run popcli 360 newcli >nil: con:0/0/640/200/PopCLI
    endcli >nil:
    
    

    re .8: I'll definitely get a book. Do you have a recommendation?
    
    I've been able to get a CLI window opened at startup, but can't
    get exactly what I want. I'm not sure if it's possible. This is
    what I'd like:
    
       1. The original AmigaDOS window gone
       2. A CLI window open
       3. PopCLI running
       4. Workbench window open 
    
    If I run PopCLI from the AmigaDOS window, the window becomes dead
    but won't go away. In the startup-sequence file I've tried various
    permutations of  LoadWB, RUN PopCLI, NewCLI, and EndCLI but it hasn't
    come out exactly right. Is there an easy way to do this? Thanks.
    
       mitch

    Re: .9
    Hope this is not a ridiculous question but where does CHFONT come
    from?  My local Amiga dealer has so far recieved one (1) copy of
    the "official" 1.2.  He's been copying the disks for interested
    souls but has not gotten any of the $15 packages to sell to us yet.
    So, I have no docs and I really haven't made time to poke around
    in C: yet.  Is this CHFONT a CLI command or is it user written?

    Gary  

RE: .9
    What does addbuffers do?
    Also, What does BindDrivers do?
    
    .. Rich

    Those are V1.2 commands .. you'll probably get errors if you try
    that with V1.1.

    The enhancer docs describe a new 1.2 option on the newcli command.
    This is the FROM keyword.  Apparently "newcli from start_file" will
    open a new cli and execute the "com" file start_file at startup.
    As mentioned earlier if you put "run popcli" in your startup then
    that cli will not go away when you do an endcli.
    
    Since my startup-sequence already does a newcli, I'm going to put
    "run popcli" in a file with some of the other non-critical system
    configuration commands and execute this with the from option of my
    newcli command.  (No use waiting for commands like addbuffers to
    complete.)  I haven't done this yet,  I just noticed the "from"
    option.  I'll post a reply if I have problems.
    
    regards,
    
    Steve McAfee