Path: utzoo!attcan!uunet!clyde.concordia.ca!jarvis.csri.toronto.edu!utgpu!watserv1!watdragon!lion!ccplumb From: ccplumb@lion.waterloo.edu (Colin Plumb) Newsgroups: comp.sys.amiga.tech Subject: Re: A couple of AmigaDOS questions... Message-ID: <20807@watdragon.waterloo.edu> Date: 12 Feb 90 18:45:47 GMT References: <20642@watdragon.waterloo.edu> <10541@nigel.udel.EDU> Sender: daemon@watdragon.waterloo.edu Reply-To: ccplumb@lion.waterloo.edu (Colin Plumb) Organization: U. of Waterloo, Ontario Lines: 16 In article <10541@nigel.udel.EDU> new@udel.edu (Darren New) writes: > But can you abort the I/O once your other stuff has come back? I.e., if > I want to time out on a read of CON:, I can get my process to come back when > the timer.device message comes back, but since DOS is not a device I > can't AbortIO on the packet, can I? -- Darren Sorry, no. An AbortPkt() function *might* exist in 1.4, but it's dubious. To do something like you describe, you have to use the underlying console.device. There's a way, described in AmigaMail and other places, to get the console.device behind a CON: window and you can do AbortIO() to it. Currently, all DOS handlers that can block arbitrarily long (CON:, SER:, PAR:, AUX:) are layered over Exec .devices, except for The various flavours of PIPE:. I don't know if there's a hack in PIPE: to allow for timeouts. -- -Colin