Xref: utzoo comp.sys.ibm.pc.misc:5152 alt.msdos.programmer:2332 comp.os.msdos.programmer:2624 Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!xrtll!silver From: silver@xrtll.uucp (Hi Ho Silver) Newsgroups: comp.sys.ibm.pc.misc,alt.msdos.programmer,comp.os.msdos.programmer Subject: Re: Writing my own print spooler Message-ID: <1991Jan1.171918.2399@xrtll.uucp> Date: 1 Jan 91 17:19:18 GMT References: <1990Dec30.160422.27898@xrtll.uucp> <1990Dec31.090454.13869@ecst.csuchico.edu> Reply-To: silver@xrtll.UUCP (Hi Ho Silver) Organization: Yeah, right. Lines: 15 In article <1990Dec31.090454.13869@ecst.csuchico.edu> madams@ecst.csuchico.edu (Michael E. Adams) writes: $ Good posting! I liked what you had to say, but my DOS reference $guide seems to think that int 0Fh should be AVOIDED! [...int 0Fh may not come from the printer port...] Hmm, that sheds new light on the situation :-) Well then, I suppose one could still use an int 0Fh routine; you'd just have to make sure you checked the printer port's status every time before trying to send a character (which would be a Good Thing to do anyway). And perhaps a clock tick hook would also be useful in case an int 0Fh failed to get through. -- __ __ _ | ...!nexus.yorku.edu!xrtll!silver | always (__ | | | | |_ |_) >----------------------------------< searching __) | |_ \/ |__ | \ | if you don't like my posts, type | for _____________________/ find / -print|xargs cat|compress | SNTF