Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!uoft02.utoledo.edu!desire.wright.edu!arc From: arc@desire.wright.edu Newsgroups: comp.sys.amiga Subject: Re: Multitasking (was re:Powermonger etc.) Message-ID: <1990Dec13.002959.2048@desire.wright.edu> Date: 13 Dec 90 05:29:59 GMT References: <9012130059.AA08767@ucbvax.Berkeley.EDU> Organization: University Computing Services, Wright State University Lines: 44 In article <9012130059.AA08767@ucbvax.Berkeley.EDU>, i0046145@WATER.FIT.QUT.EDU.AU (Lukacz Alex) writes: > I've been having major problems with multitasking lately, anyone care to tell > me what exactly is happening or a fix? > > 1) When using DiskMaster (V1.4) and NComm (V1.9) I often copy files or unarc > just-downloaded files while online. Trouble is, when I try to get a > directory (through the 1.3 'List' or 'Dir' commands) whilst unarcing is > taking place, the disk drive managed to 'crunch, crunch' back and forth > for MINUTES. > > I think what is happening here is that the dir command is trying to get to the > tracks around 880 for the list of files whilst the arcing program is still > trying to unarc the program which would be spread over the tracks of the disk. > > Now I think this is rather silly. Surely one task should take priority over > the other, so the 'dir' could intercept the unarcing and get the list of files > and then let arc get back to work. > > I have tried changing the task priority of 'dir' and 'list' but it doesn't seem > to have much (read: any) effect. > > 2) When online a BBS or the VAX/UNIX, the text output to my monitor slows > down IMMENSELY if I'm doing disk-accesses at the same time. For example, > I'm looking for a particular file which I wish to upload. I am certain > it is on one of two disks sitting in my disk-mailer. I wish to get a > directory of both disks so I can find out which one the file is on. I > change windows to the CLI window and then issue 'dir'. Click back to the > NComm window and SHAZAAM! - text output is slowed to an annoyingly slow > rate. This happens both at 2400 and 9600 baud. > > I have absolutely no idea of what is going on here. > > > Any hints/solutions (no flames, send 'em to /dev/null) would be appreciated. > > Alex. Okay, to answer your statements... Your drives EACH have 2 tasks each to "drive" them... Just because we have a processor for some disk accessing, doesn't mean that you won't have a slow down. When writing/reading from a disk drive, each drive has it's own "buffer", and programs have no real priorities to access these. I think someone could explain this better, and also I think you oughta get more info before you post such a message on here, like a book, maybe?