#Expand Boot Shell
20 messages in this thread
I was trying to expand the Shell window that appears when I boot. I'm using
a HiRes interlaced WB and the initial Shell window didn't fill the screen.
I was told to use the newshell command before the startup-sequence output
to the Shell and to use the full screen parameters in the command. I did
this and it didn't work.
Upon booting, I got a full screen shell, but with different colors than
WB. This was a result of my newshell command. Then, that window closed and
another Shell opened with the correct colors, as the startup-sequence
continued. The problem is it was using HiRes mode, instead of HiRes
interlaced mode. After booting was completed, I had a HiRes WB, instead of
the HiRes interlaced WB I usually had.
All I did was add a newshell command after the setpatch and version
commands in the startup-sequence. The command allowed for a full screen
Shell window with slight overscan in HiRes interlaced mode.
Did I do something wrong like put the newshell command in the wrong spot?
I was told to use the command before the script output to the shell window,
if I wanted to create my own shell window on bootup.
My goal is to have a full screen shell window on bootup. How do I do this?
Thanks for any help.
Dom Fontana
Dom,
Aha. Basically, you want a full shell window after bootup- same as I do.
Go back and set things up to spec as per your hardware and 2.04 spec,
leaving the Startup-Sequence as much alone as possible. Use the stocker,
which normally kills the booting shell window leaving you in WB. Now just
add that NewShell command to you User-Startup.
It works, as I'm living proof. 8) Anyway, the booting shell seems to be
tied into too many things whilst the system is setting itself up to fool
with. Following the recommended procedure in this case is the wise thing
to do, IMHO.
Doug the Scrutable (On Thursdays)
Doug,
Not quite. I don't want a full shell window AFTER bootup. I want one
DURING bootup. You don't think it's possible?
Dom Fontana
Dom,
It might be possible, but there's an awful lot going on under the sheets
when that first window pops up.
Considering that it's primarily a problem of aethetics, I personally
wouldn't mess with it. If it's a matter of life and death, I'd just put a
newshell <stuff> FROM s:My_Startup ; transfer to other window/shell endcli
>NIL: ; Done so soon?
in the startup-sequence, and transfer everything else to the new script
while ending the first. Bypass the original s-s completely, as it were, so
that first window doesn't even get seen. NOT the recommended method at
all, but would probably do what you desire. Worth an experiment, anyway.
Doug
Doug,
Thanks, but I agree that it's not worth the trouble. I thought that maybe
there was an easy way to do it. Apparently, the Shell opens in interlaced
mode, but doesn't know to expand to the full screen size. As I said, it
would be the size of the screen if I weren't in interlaced mode.
Dom Fontana
You have to make your startup-sequence _completely_ quiet, so the first
window that opens is the open that you open with newshell. Basically, you
want to avoid having the other window open at all.
Your newshell command should come right after the LoadWB.
But you have to make sure that nothing in either your startup-sequence or
your user startup will cause the first window to open.
What I generally do is let the first window open, then close. The next
shell I open is the right size.
andy
Andy, I remember how long it took me to get that startup to be 'quiet', but
it was worth the effort to have things look the way I wanted them to.
BTW, an unsolicited compliment to Commodore; 2.04 is very, very impressive.
Ron
Thanks. andy
Andy,
I think we're misunderstanding each other. I don't want a full Shell
window AFTER booting. I want it DURING booting. I have many echo commands
in my user-startup file. If I were using a hi-res WB, the Shell that
appears during booting is the full size of the screen. However, I'm using a
hi-res Interlaced WB, so the booting Shell is only 1/2 the height of the
screen. It is this Shell that I would like to be the full size of the
screen while I'm booting.
Dom Fontana
I'm gonna toss in my two cents here. I use a program called RSIZE that
changes the size of a shell window. Maybe using this command in your SS at
the beginning would be able to resize it to a full size window? I think I
DL this from CIS, if you can't find it let me know and I'll upload it.
Paul,
Thanks for the RSIZE info. If I can't find it, I'll let you know.
Dom Fontana
Paul,
Do you recall where you DLed RSIZE from? I can't find it here.
Thanks.
Dom Fontana
Dom;
I would suggest NOT trying to mess with the initial shell window. I don't
know about WB_2.x but under 1.3 and older, that initial CLI was quite a bit
different than any subsequent CLI or Shell.
I also would suggest that you should consider getting Bill Hawes's WShell.
WShell will give you a scroll bar on your Shell. Plus, of course, you can
open it at any size you wish.
While it is best if you don't "mess with" the CBM "Startup-Sequence" file,
Doug's suggestion is a reasonably elegant solution. Rename your S-S to
something like "StartupII" and create a new S-S that has a line that reads
"newshell con:0/0/600/400/Start_Shell from S:StartupII". Of course it
would also be best if you moved the line "setpatch >NIL:" from the original
S-S to the first line of your new one.
-bill/ARS KB7LX
Bill,
That's a good idea. I think I'll try it.
Dom Fontana
Dom,
Then why not just change the invocation of user-startup to a fully spec'd
window?
-larry
Larry,
I'm running WB in HiRes Interlaced. When I invoke user-startup with a
fully spec'd shell command, after booting is completed, I have a HiRes WB
that is NON-Interlaced. I thought maybe there was another way.
Dom Fontana
Dom,
I don't know of an easy way to change the WB from interlace to not. Are
you SURE you aren't mucking around with your env:sys directory?
Vic,
I have not altered my env:sys directory.
Dom Fontana
Dom,
Hmmmmmmmmm, verra verra odd. Have you tried changing your preferences
to interlace and SAVEing them?
Vic,
Yep. I did save my interlace prefs and still no luck.
Dom Fontana