Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!warwick!csuwr From: csuwr@warwick.ac.uk (Derek Hunter) Newsgroups: comp.sys.acorn Subject: Re: Removing MEMCfaster from FishDemo Keywords: MEMC FishDemo Message-ID: Date: 18 May 91 08:07:19 GMT References: <1991May17.100004.15705@comp.vuw.ac.nz> Sender: csuwr@cu.warwick.ac.uk Organization: Computing Services, Warwick University, UK Lines: 27 Nntp-Posting-Host: lily In article <1991May17.100004.15705@comp.vuw.ac.nz> gavin@comp.vuw.ac.nz (Gavin Flower) writes: > >On behalf of The Master of the Arcane, I proudly present... > >----------------- >Subject: Removing MEMCfaster from FishDemo... [stuff] >However, I'm not sure if removing the MEMCFasters will help you much, as the >demo gets nasty and jerky on Memc 1's (i.e. 310's), and will probably do the >same without the Memcfaster... Yeah, but the whole point is that the later Arcs (A3000, A410 etc) don't need the MEMC update because they use MEMC1a s rather than MEMC1 s, and the 1a s don't have the kludge that slowed the 1s down. On my machine in particular, it objects to the `speedup' by crashing. I did try to follow the unsqueeze, but I got confused, and gave up. I'll be writing a patch to intercept SWIV and mask out just one MEMC 64,64 call. This wo'n't slow the machine down if it dissociates itself after that one call. I guess I can't just make the SWI a SWINV because that won't be supported in future releases [snigger]. - I don't know, he just phoned up and said something about the goat. - Derek Hunter.