Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!hsdndev!wuarchive!usc!bbn.com!nic!kira!news From: pegram@kira.UUCP (Robert B. Pegram) Newsgroups: comp.sys.atari.st Subject: Re: Quick ST vs Turbo ST Message-ID: <1991Feb25.182842.6162@uvm.edu> Date: 25 Feb 91 18:28:42 GMT References: <1991Feb22.182952.16058@ecst.csuchico.edu> Sender: news@uvm.edu Distribution: comp Organization: University of Vermont, Department of Computer Science Lines: 40 Raymond-Protection: enabled From article <1991Feb22.182952.16058@ecst.csuchico.edu>, by ekrimen@ecst.csuchico.edu (Ed Krimen): Previously quoted article deleted, Ed replies: > Here's what I'd tell any person who's interested in TST and QST: > >If you want all the other goodies that QST has, like background pics >and fills and the file viewer and stuff, then go for it. However, if > you use something like NeoDesk that already has background pics, >fills, and a file viewer, and you like the little bit of screen speed > increase that TST gives over QST, then get QST. > > Also keep in mind that QST takes up less memory than TST (if you > don't have the picture installed on QST). > > I bought QuickST and now I don't use it. I use Turbo ST 'cause it's > faster. Ed, I have both also. Only one thing confuses me - if TST is faster for replacement mono fonts, why is it *much* slower for GDOS fonts and fonts using attributes such as italic and bold? I find the difference in speed maddening when I use WordUP 3.0 (still need the last upgrade disk 8-) and therefore stick to QST for now. Try the QST test for text with attributes and/or GDOS to see what I mean. Oh yeah I, run *both* the QST background picture and the NEODESK one (that's one reason why I got 2.5 Meg, for frills 8-) that way - or if I used the QST fills - I can get a picture (or fill) behind my Gem programs as well as on the Desktop. Finally (I know, RTFM 8-) is there a way to store and reread NeoDesk fill patterns - a RSC file perhaps? thanks, Bob Pegram pegram@griffin.uvm.edu or ...!uvm-gen!pegram