#Addbuffers
10 messages in this thread
Does Addbuffers use "fast" ram or "chip" ram?
Thanks, George Glines
George,
I just checked..it uses both…I just added 30 buffers to a drive as a
test, and checked memory usage before and after…it took about 5k from
FAST and 35K from CHIP (in round numbers). Don
Thanks Don, I was hoping it was all FAST ram…oh well.
George
Something is drastically amiss there Don. That is a total of 40K for a 30
count, which should have been about 15K.
I just tried it (20 buffers) and it took 10880 from CHIP only. (20 buffers
comes out to 10240, or 10K, so the extra is obviously overhead).
Regards, Larry.
Larry,
Humm…I just looked at the mem command from CSH and then added the
buffers and looked at it again. Let me try once more when I'm home and see if
the same thing occurs.
Don
I was going directly from CLI Don, and used AVAIL to check the memory before
and after.
Speaking of shells, I have just received about a dozen new Fish disks. On one
of them is a beautiful little program called SiliCon, that is the first
acceptable command history/sort of shell that I have seen. It opens a window
into which you type your commands, and keeps a list of them. They may be
retrieved by using the up/down cursor keys or by single clicking with the
mouse. Once retrieved, they are activated with a CR. Alternatively, you may
double click on any command to activate it. Commands may be deleted from the
list easily, preventing the "clutter" that usually accompanies a history list.
Commands retrieved may be edited, cursor right/left, mouse positioning, and
shifted cursor right/left to go to the end/beginning of the line. <right Amiga>
X will delete the command line, and a shifted CR will leave the command in the
list and remove it from the command input line without executing it.
Script files are handled automatically, without having to type EXECUTE, a very
nice feature. One example is included, a quick reference page for SiliCon
itself, and is interesting for the fact that you only need to type in the name
of the file (quickref), and it "self types".
I'll be uploading it as soon as I have finished reading messages.
Regards, Larry.
Larry,
That sounds like what I've been looking for…I'll take a look at it
tonight…does it have my other wish list item… the ability to show current
directory in the prompt?
Don
There is no prompt Don. I don't mind though, because it's easy enough to double
click any CD xxx command that is in the list. I'll have to go back and take a
look at the doc file to see if it has provision for a prompt at all.
Regards, Larry.
Darn, I hate to use a mouse in a CLI environment…that's why I use
CLI, so I can keep my fingers on the keys…I don't mind the up/down arrows as
they are easy to get to thou. The mouse I have to grab and move and click and
then get back to the keys for the next thing I want to do..oh well.
Don
But Don, the mouse is optional! All functions can be accessed via the keyboard.
Take a look. I think you'll like it.
Regards, Larry.