From owner-freebsd-emulation  Tue Jan 20 17:59:52 1998
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA29213
          for freebsd-emulation-outgoing; Tue, 20 Jan 1998 17:59:52 -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 RAA29209
          for <emulation@FreeBSD.ORG>; Tue, 20 Jan 1998 17:59:49 -0800 (PST)
          (envelope-from rhh@ct.picker.com)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Tue, 20 Jan 1998 20:58:44 -0500 (EST)
Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1)
	id AA11156; Tue, 20 Jan 98 20:58:38 EST
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id UAA07007; Tue, 20 Jan 1998 20:57:18 -0500
Message-Id: <19980120205718.24303@ct.picker.com>
Date: Tue, 20 Jan 1998 20:57:18 -0500
From: Randall Hopper <rhh@ct.picker.com>
To: Mike Smith <mike@smith.net.au>
Cc: emulation@FreeBSD.ORG
Subject: Re: DOSCMD: Misc questions
References: <19980118183139.14729@ct.picker.com> <199801190118.LAA00398@word.smith.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88
In-Reply-To: <199801190118.LAA00398@word.smith.net.au>; from Mike Smith on Mon, Jan 19, 1998 at 11:48:42AM +1030
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Mike Smith:
 |> When DOSCMD starts up, it seems to need a key hit to continue loading DOS.
 |> Is this normal?
 |
 |No.  It may be due to something that you are loading in your CONFIG.SYS 
 |file which is unhappy with the quality of the low-level keyboard 
 |emulation.  Have you tried working out what is hanging?  Do you load 
 |the KEYB.SYS driver? (this last is known to cause problems).

I renaming the CONFIG.SYS and AUTOEXEC.BAT so they wouldn't be found and it
still paused for a key.  I then reformatted that DOS partition completely
and fdisk /mbr'ed the disk to get rid of the boot manager (OS/BSbeta) I had
on it.  Still got the hang.

It may be related to DOS 6.2 -- I noticed the mention in the man page:

                                                It should be noted that MS DOS
     6.2 and higher appear to cause difficulties for doscmd.

 |> Funny thing is that this key stays around in the keyboard buffer and is fed
 |> to the next program requesting a key (HDM in my case, a hard disk manager
 |> utility, which I start up from my autoexec.bat).
 |
 |Not actually very surprising; I expect that there is a program waiting 
 |for status from the keyboard.  Hitting the key gets the status updated, 
 |but it never pulls the character itself.

Doesn't look like its getting to the config files, so since I see "Starting
MSDOS..." before the key-wait, I guess we're somewhere in IO.SYS or
MSDOS.SYS (?)

Randall