Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!cbmvax!carolyn From: carolyn@cbmvax.cbm.UUCP (Carolyn Scheppner CATS) Newsgroups: comp.sys.amiga Subject: Re: printer.device troubles Message-ID: <1666@cbmvax.cbmvax.cbm.UUCP> Date: Mon, 13-Apr-87 09:57:17 EST Article-I.D.: cbmvax.1666 Posted: Mon Apr 13 09:57:17 1987 Date-Received: Sat, 18-Apr-87 18:37:34 EST References: <871@vaxb.calgary.UUCP> Reply-To: carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) Distribution: na Organization: Commodore Technology, West Chester, PA Lines: 38 Keywords: printer device SendIO In article <871@vaxb.calgary.UUCP> candym@calgary.UUCP (Mike Candy) writes: > >(RE: Asynchronous printer dump) >[] >The first thing he attempted using to stop the printer dump was AbortIO, >unfortunately there is very little documentation on this in the RKM and >all he got were visits from the GURU. Does AbortIO work on the >printer.device and if so how does one use it? > /* Test of screen dump abort after 10 seconds */ /* These lines replaced the DoIO(iodrp) */ SendIO(iodrp); Delay(1000); /* Replace with what you want to do here */ if(!CheckIO(iodrp)) AbortIO(iodrp); /* If not done, abort */ WaitIO(iodrp); /* This does some cleanup, removes request, etc. */ ------------------------------------------------------------------------- Two things to note: 1. If you don't do the WaitIO(), the request is not removed and a belated Printer Trouble requestor may appear, leading to a GURU. 2. Under 1.2, if you abort a graphic dump, the graphic buffer is never deallocated, leading to a memory loss (size dependent on printer) each time a dump is aborted. Hopefully, a future re-write of the printer device will eliminate this problem. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Carolyn Scheppner -- CBM >>Amiga Technical Support<< UUCP ...{allegra,caip,ihnp4,seismo}!cbmvax!carolyn PHONE 215-431-9180 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=