From owner-freebsd-emulation Thu Jan 29 15:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13136 for freebsd-emulation-outgoing; Thu, 29 Jan 1998 15:10:35 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA13129 for ; Thu, 29 Jan 1998 15:10:31 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 29 Jan 1998 18:10:01 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA25355; Thu, 29 Jan 98 18:09:59 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id SAA08908; Thu, 29 Jan 1998 18:09:56 -0500 Message-Id: <19980129180955.42881@ct.picker.com> Date: Thu, 29 Jan 1998 18:09:55 -0500 From: Randall Hopper To: emulation@FreeBSD.ORG Subject: DOSCMD: Ctrl-Enter doesn't work in Quicken Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-emulation" Back-tab was easy; this one is -- interesting. I verified that when Ctrl-Enter is hit, the same keycode and scancode pair are put in the DOSCMD BIOS keyboard buffer as in DOS 6.2 under DEBUG.EXE. I also verified the state of the keyboard shift flags in the DOSCMD BIOS seg. Oddly, Quicken just doesn't see Ctrl-Enter. "Enter" works, other Ctrl sequences work, but not Ctrl-Enter. I guess this might mean that Quicken is relying (at least partially) on keyboard probes at the port level. (I notice that Quicken sets its own INT9 KB intr hdlr when it fires up) Any tips on going after this one? Does someone possibly have a keyboard patch waiting-in-the-wings I could try :-) Thanks, Randall (Unfortunately, Ctrl-Enter is the only way to get out of the split-transaction dialog in Quicken 5, so I'm motivated to dig into this)