[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ANSITERM 2.0 (3 OF 3)
Paul Parkhurst (paul.parkhurst@uttsbbs.uucp) wrote:
> Well, yes and no. If you set your scroll to 1, then only one line is
> scrolled. If you set it to 2 or 3 or whatever, that number of lines
> will be scrolled. It is an option that is available to speed up
> possibly sluggish screens. If you notice, the AWGS comm package always
> scrolls up a quarter of a page or so, to try to make up for Quickdraw's
> slow scrolling at high speeds. AT's scroll is much faster, but may
> still be sluggish at 19200 or 38400 baud.
It seems to me that would cause an ugly screen full of garbage if the
program generates a scroll and expects it to cause one line to scroll. I
guess that's why you can turn this off if you have to.
> I'm not sure what you mean by crashing with a $0201. Its never
The P8 program requires all the memory in banks 0 and 1. If it can't get
THAT memory, a memory error is generated. (Maybe there's an unmoveable block
in that area?). The annoying thing is that it's a system failure error and you
have to reboot after you get it.
> happened to me. Yes, it doesn't run under GNO, it doesn't access
> resource forks, and, at least in the initial version, it doesn't support
> upper and lower case file names. However, I think Jawaid's comm program
A P8 program will never be able to make upper/lower filenames, only read
them - unless you rewrite the whole opSys like FTA likes to do.
> differ with you. ANSITerm uses the SHR screen for 16-color, 80 column/
> 25 line text display, it makes extensive use of the memory manager to
> access all available memory in your GS, and as to drives, about the only
> real limitation with P8 2.x is that it won't access HFS partitions.
I like everything GS/OS introduced and I hate to go back to the ol' slot&drive
and allocating your own file I/O buffers and so on...
> Yes, as I said, it doesn't support GNO or any of the other
> multitaskers. If I made AT a GSOS program, I would want to also make it
> a desktop program. I would also want to add many, many new features.
You wouldn't necesarily have to make it a desktop program: use what you
already have. As a matter of fact, I don't think you can accomplish the
same speed you say AT's got if you make it desktop.
> Paul Parkhurst
--
______________________________________________________________________
|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Phillip Vandry | Vandry@Cam.Org | Suicide (n.): What to do if Macs |
|________________|________________|_______________take over the world__|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~