#Conman & Startup-Seq.
21 messages in this thread
There's something that's bugging me about CONMAN. It seems as though it
cannot "yank the handler out of the already existing CLI" (to paraphrase the
DOCS" so CLI #1, off of which the STARTUP-SEQUENCE is going, is the old-style
CON:. To get a CONMAN CLI, I have to do a NEWCLI, then ENDCLI to get rid of
old-style #1. However, a startup-sequence won't continue into the new CLI.
Plus, it's a bit "odd" to me to call a NEWCLI and have it as number one. Is
there any way around all of this?
Henry, let the startup-sequence complete normally and end with an endcli >
nil:. During the startup-sequence, load POPCLI III or equivalent (DMOUSE?).
Once teh old CLI is gone, start a new one with an ALT-LEFTAMIGA (or yuk!
ALT-COMMODORE) keystroke. That's all there is to it!
-Greg
OK great thanks. Listen, what does ENDCLI > NIL: do? I see that everywhere in
various shapes/forms and it puzzles me.
ENDCLI >NIL:
ends the current CLI, and writes its signoff message to the proverbial
Bit-Bucket (NIL: is just a buffer that gets deleted and never written anywhere)
Larry Rosenman
What's the "signoff message?" Is this an important step or will something go
wrong or different if it's left off? (referring to ENDCLI).
The signoff message is the
CLI Task 1 ending
or whatever, the >NIL: just avoids that coming out on the screen
Larry Rosenman
The signoff message is the
CLI Task 1 ending
or whatever, the >NIL: just avoids that coming out on the screen
Larry Rosenman
Henry why don't you just put all the calls that release the cli in your
startup-sequence in the old cli window and then use newcli "con:n/n/n/n/
Henry's ConMan CLI" FROM sys:s/Finish_the_START or whatever I call it Xbegin,
to RUN programs that won't release the CLI. This way you can endcli > nil: like
usual and have a custom sized ConMan CLI for your use and loadwb form it. Just
remember to use start after the newcli and argument, upper lowercase doesn't
matter, as long as you tell it to look in the right dir and sys:s should do
fine.
Chris
I'm sorry – that sounds good, but I just don't understand. 🙂 Could you try
again for a dodo? 🙂
Translation:
Put everything from your Startup-Sequence that DOESN'T release the CLI window
into another file in s: In your original s-s, put a newcli…FROM s:<file> to
start it up. If you use ConMan, have it start up just before the NewCLI so the
new CLI is running under it. Use RUN for commands where possible. This will
allow you to endcli >NIL: as normal, leaving you witha ConMan CLI.
Easier method, when you don't want ANY CLI: runback those things that don't
release the window.
Henry, OK sorry about that I'll try again,
; Here's my startup-sequence
ff gulch.font ;I hate those topaz fonts get rid of them NOW! conman
-q newcli "con:0/0/640/280/Chris' ConMan CLI" FROM S/START ; This is where
endcli
; you'll get your ConMan CLI and get rid of the
; the old AmigaDos one !
; This is my START script
mount VD0: dir vd0: wait 3 IF EXISTS VD0:S/xBegin ; This checks for the file
in my RRD ram. execute VD0:S/xBegin Endif IF NOT EXISTS vd0:s/xBegin execute
DF0:S/XBegin ; and if it's not there it'll get it from here ENDIF
; xBegin is where I start making directories in Vd0:
; Start FaccII look for vd0:c or make it, etc, etc.
run faccII +300 wait 2 run facction -w off wait 2 IF not Exists vd0:c makedir
VD0:c finish 0 endif
; I hope this helps,
; Chris
Thanks for your suggestions. I just "kept" your message and will look
through it later.
I honestly don't know, although I read that it was technically required. Plain
old ENDCLI has never bit me, either.
-Greg
Henry,
Another alternative for your ConMan startup is to do a NEWCLI and declare a
"from file" to complete your startup. It might look something like this:
; real startup-sequence
(initial commands here ….)
conman -c NEWCLI CON://640/100/New FROM s:startup2 endcli >NIL:
and then put the remainder of the startup in the second file. How you divide
things is up to you.
-Bill Hawes
Sorry, my previous message got run-on. (How do I turn off this
auto-formatting, anyway??)
Should be:
conman -c
NEWCLI CON://640/100/New FROM S:STARTUP2
ENDCLI
As others have mentioned, the >NIL: on endcli is optional.
-Bill
Another way to have the startup sequence to continue into a "NEWCLI" is to use
the NEWCLI CON:xxx/xxx/xxx/xxx/NewCli FROM file option.. I use this now on my
harddisk, it works great.
Larry Rosenman
I'm, sorry, but NEWCLI CON:xxx/xxx/xxx/xxx/NewCli FROM is over my head – could
you explain that a bit more? Thanks a bunch.
Sorry if I wasn't real clear…
In your Startup-Sequence, you can put a line like the following:
NEWCLI CON:0/100/640/100/NewCLI FROM file
which will open a NEW con: window on the bottom half of the screen and attach a
CLI to it, and then take its initial commands from file
I do this in my startup sequence.
Does that help??
Larry Rosenman
Yes it does. I will try it and get back to you if I have troubles – thanks a
bunch!
Here's what you do:
1) Rename your present s:startup-sequence to s:conman-startup
2) Create a new s:startup-sequence that reads in its entirety:
conman
newcli from s:conman-startup
endcli > nil:
3) Go into s:conman-startup and remove any references to conman so you won't
have to start it twice.
OH WOW! Brilliant! Thanks