home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!mintaka.lcs.mit.edu!chaos!random.ccs.northeastern.edu!mharm
- From: mharm@damon.ccs.northeastern.edu (Michael Harm)
- Newsgroups: comp.sys.mac.system
- Subject: Summary of bad f-line problem?
- Message-ID: <1992Aug17.140134.14474@random.ccs.northeastern.edu>
- Date: 17 Aug 92 14:01:34 GMT
- Sender: news@random.ccs.northeastern.edu
- Organization: College of Computer Science, Northeastern University
- Lines: 25
- Originator: mharm@dec3100e.ccs.northeastern.edu
-
- Hi y'all.
- I recall a while back there being a bezillion posts
- about the infamous "bad f-line instruction" problem.
- I haven't been on the net in a while, but folks over
- on other mac groups (comp.sys.mac.programmer, for one
- I believe) are asking about it. Were any conclusions
- reached about this? Any fixes? Any patterns noticed
- in the machines affected? (for a while it seemed
- to me that all the machines hit were of the sort that
- run virtual memory, so I suspected that. Counter-examples?)
-
- Please email summaries (if any) to me, or post to the
- net if you think its of general interest.
-
- Thanks,
-
-
- Mike Harm
- mharm@damon.ccs.northeastern.edu
- Northeastern Univ.
- ---------------------------------------------------------------
- "I agree that 'two times two makes four' is an excellent thing;
- but if we are dispensing praise, then 'two times two makes five'
- is sometimes a most charming little thing as well."
- -Fyodor Dostoevsky, "Notes From Underground"
-