Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rochester!cornell!vax1!jsm From: jsm@vax1.ccs.cornell.edu (Jon Meltzer) Newsgroups: comp.sys.ibm.pc Subject: Re: Trapping DOS error message Message-ID: <244@vax1.ccs.cornell.edu> Date: Wed, 14-Jan-87 23:24:56 EST Article-I.D.: vax1.244 Posted: Wed Jan 14 23:24:56 1987 Date-Received: Thu, 15-Jan-87 20:11:27 EST References: <243@vax1.ccs.cornell.edu> <58200015@gorgo.UUCP> Reply-To: jsm@vax1.UUCP (Jon Meltzer) Organization: Cornell Computer Services, Ithaca NY Lines: 31 In article <58200015@gorgo.UUCP> ddrex@gorgo.UUCP writes: > >/* Written 11:00 am Jan 9, 1987 by jsm@vax1.UUCP in gorgo.UUCP:comp.sy.ibm.pc */ >/* ---------- "Trapping DOS error message" ---------- */ >I need a way to trap the error message > >"Insert diskette for drive A: and strike > any key when ready" > >that appears on single floppy-drive machines. >/* End of text from gorgo.UUCP:comp.sy.ibm.pc */ > >Your question is not clear. If your problem is that some software you run >expects to find certain files on the floppy drive, while those files are >actually on the harddisk, you can "fake it out" using the dos 'assign' >command: No,no. Here's the problem : my program asks the user to put a floppy in a user-predefined disk drive. On single drive machines,the error message will occur if the program is looking for the A:, but DOS thinks that the drive is the B:. The resulting error louses up the program screen design. I can get around it by redrawing the screen, but would rather trap the error and display the message in a format compatible with my other error messages. Unfortunately, I've been told that the message is produced by the device driver and has nothing to do with the critical interrupt vector .... Jon Meltzer DML Cornell University Ddrive