Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!cbmvax!cbmehq!cbmger!kbsaar!fjrei From: fjrei@kbsaar.UUCP (Franz-Josef Reichert) Newsgroups: comp.sys.amiga.programmer Subject: Re: "Task"'ing trubbles Message-ID: Date: 23 May 91 14:16:23 GMT Article-I.D.: kbsaar.fjrei.9418 References: <1991May21.063012.1358@m.cs.uiuc.edu> Organization: Private Amiga Site Lines: 15 In article <1991May21.063012.1358@m.cs.uiuc.edu> schwager@m.cs.uiuc.edu (Michael Schwager) writes: >So, it doesn't work. My main program calls the function "flash" that >creates the Task "flashTask". The Task "flashTask" calls another function >named "myDelay"... it works just like DOS' Delay() but using timer.device. Who is setting up the MsgPort/timerequest for your timer.device stuff? As I see, flashTask() didn't! So the mp_SigTask may be wrong (i.e. contain the address of the parent task's control block), which will cause flashTask() waiting forever for a signal which never occures. -- Best regards, Franz-Josef Reichert VOICE: +49 6805 7417 Kuchlingerstrasse 13 UUCP: ...uunet!cbmvax!cbmehq!cbmger!kbsaar!fjrei D-6601 Kleinblittersdorf GERMANY