Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!tut!mt87692 From: mt87692@tut.fi (Mikko Tsokkinen) Newsgroups: comp.sys.amiga.tech Subject: Speed vs Multitasking (WAS: Low 16k memory) Message-ID: Date: 25 May 90 08:58:13 GMT References: <1623@lpami.wimsey.bc.ca> Sender: News@tut.fi Organization: Tampere Univ. of Technology, Finland. Lines: 23 In-reply-to: lphillips@lpami.wimsey.bc.ca's message of 22 May 90 22:15:18 GMT In article <1623@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: > Has somebody checked what low 16k ($0000-$ffff) memory contains. I'm asking ^^^^^^^ Because of brain damage I wrote 16k when I ment 64k! To be more precise first 32k and last 32k. The Idea is to use short absolute addressing which is actyally quite a bit faster than long! > this because that's the fasted memory in standart 512k machine. All alloc- > mems fail. I think I will kick the operating system out, move low 16k > somewhere and when the program has ended move it back. Somebody said that > it contains some track.device buffer but that doesn't matter, I'm using > my own disk-routines anyway. Any other solutions? I need the speed for > real time 3D landscape & object handling. MITT -- ----------------------------------------------------------------------- : Mikko Tsokkinen : I'm not a number ... I'm a free man : : Internet mt87692@tut.fi : UUCP tut!mt87692 : Bitnet mt87692@fintut : -----------------------------------------------------------------------