Path: utzoo!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!rg20+ From: rg20+@andrew.cmu.edu (Rick Francis Golembiewski) Newsgroups: comp.sys.amiga Subject: Re:Game vs Multitasking Message-ID: Date: 31 May 90 14:57:22 GMT Article-I.D.: andrew.gaNH3Gm00UgyM2OJlY Organization: Class of '92, Carnegie Mellon, Pittsburgh, PA Lines: 17 In all the talk about games, it seems that one thing people are agreeing on is that HD owners really want to be able to put their games on the HD (I agree!), but then when it comes to multi tasking developers argue about how their programs need the entire CPU resources etc. One thing that some developers might just want to consider is that if you kill multitasking, you will probabily kill access to the HD (unless you want to write a driver for EVERY HD on the market), since the drivers run a tasks. A classic example F-18, F-18 has a code wheel, so there is no reason that you can't copy the files to HD, but when you try running it it kills multitaking before it finishes loading everything into memory! They could at least have waited until the program was fully loaded in (as it doe not do any disk access after loading). So, remember if you want to be friendly with HD owners don't kill the O/S or stop multitasking. -Rick Golembiewski rg20+@andrew.cmu.edu