pmy@boole.acc.virginia.edu (Pete Yadlowsky) (01/07/88)
[At the end of yesterday's episode, we left Yadlowsky to ponder the integrity of his 1.5M internal FAST mem...] Thanks [didn't get the name, sorry], for the tip on the Spirit Technologies board with regards to the shield placement. I haven't had any problems resembling the one you mentioned, but I think I'm gonna follow your lead. After further investigation, I don't think the problems I was having in my attempts at multi-tasking were memory-related. In review, I had written a program which spawns a task which sends timer "ticks" to the originating program. This was working/failing in odd ways. So, I wrote a simple program which does what the timer-task was intended to do, and just RUN'd it under AmigaDOS. Then I re-wrote the original program to receive messages from this timer process. Worked just fine. No gurus. No funny stuff. No corrupt RAM: files. Therefore, I conclude that there was something wrong in the way I was spawning that task. What could it have been? Questions: 1) The spawned task made several calls to entry points in a shared, disk-resident .library which was OpenLibrary'd by the parent program. Things seemed to be working, in that these calls were having their desired effects. BUT, can this sort of cross-calling (for lack of an appropriate term) have side effects? 2) The spawned task was doing some memory allocation via things like CreatePort. Does it need to have memory reserved for this purpose before it's AddTask'd? Or can tasks go ahead and ask the system for memory just as a process would? 3) The Exec manual mentions a ChangePri() (change priority) function, but says nothing about its use. Does anyone have any info on this? Put more directly, how can one set the priority of a program started from the CLI? Enough for today. -- Pete Yadlowsky Academic Computing Center University of Virginia e-mail: pmy@vivaldi.acc.virginia.EDU