home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.amiga.datacomm:5994 comp.sys.amiga.misc:13288
- Newsgroups: comp.sys.amiga.datacomm,comp.sys.amiga.misc
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu!gblock
- From: gblock@csd4.csd.uwm.edu (Gregory R Block)
- Subject: Re: The cause for Term problems? (Now: A problem FOUND!)
- Message-ID: <1992Aug31.225938.23599@uwm.edu>
- Sender: news@uwm.edu (USENET News System)
- Organization: University of Wisconsin - Milwaukee
- References: <1992Aug28.193647.18120@uwm.edu>
- Date: Mon, 31 Aug 1992 22:59:38 GMT
- Lines: 72
-
- gblock@csd4.csd.uwm.edu (Gregory R Block) writes:
- : Okay... I give up. Nobody else seems to be having problems, so...
-
- Wow! I've had several responses. The good majority of the responses
- I've got through mail are one of two types:
-
- 1) Job Manager is a problem, don't use it. I've stopped, and one and
- a half problems seem to have disappeared.
-
- 2) I'm not the only one having problems with Term. However, most of
- them don't bother to POST thier problems, they just survive with them,
- and hope they'll be gone soon. So I'm not alone in this.
-
- Well, thought I'd update the bugs that I've been able to reliably
- reproduce to this date.
-
- I _WAS_ using JM 1.1b. Since removing, there has been a change in the way
- things have been happening, though not dramatic enough to make me happy.
-
- Note: If I could _FIND_ any of these problems in the source, or what
- would cause them, I'd have fixed it, and sent a diff instead of a
- complaint. ;)
-
-
- Known bugs:
-
- When one tries to clip text on the buffer _SCREEN_, the system gurus (not
- caught by 2.0!) the entire system. Eminently reproducible.
-
- When one tries to clip text on the terminal itself, the results were
- different than when JM 1.1b was running. Now, I'm able to hold down the
- mouse button, and BEGIN to clip text... The cursor changes... then,
- at a
- seemingly random point in time during the clip action itself, 2.0 catches
- a guru. (Note: these are ALL 80000003 gurus...) My best guess is either
- a message problem between term and intuition, or a problem with the way
- the code works... But I think probably the first.
-
- The status-window-close problem bug is gone, by removing JM. This is sad,
- because I liked two of the utilities that came with JM in particular, PRI
- and PS. PS gave a full listing of all processes and tasks, and PRI let
- you change any of the priorites for any task or process...
-
- Another problem which HASN'T changed is a bug with opening an 8-color
- hires display. I'm able to reliably guru the machine with one dialing
- preference in particular, and I'm anxious to send this out to someone to
- see if it can be reproduced.
-
-
-
- There's another small problem:
-
- I've noticed, through MungWall and MungList, that term is allocating
- memory and leaving some behind when it closes... I'm not sure on what,
- where, or what kind, but careful use of these programs is vital in finding
- memory losses. Use the NAMETAG feature of MungWall, and munglist can tell
- who allocates what...
-
-
-
- However, it does seem that there are no more MungWall reports from Term
- and the buffer, so I'm overjoyed. :)
-
- Thanks, all.
-
- Greg
-
- --
- (: (: (: (: Have you overdosed on smileys today? Why NOT!?! :) :) :) :) :)
- (: "...and here's Clinton giving the correct spelling of bong-resin..." :)
- (: gblock@csd4.csd.uwm.edu Gregory R. Block :)
- (: (: (: (: (: (: (: (: (: (: (: (: (:) :) :) :) :) :) :) :) :) :) :) :) :)
-