From owner-freebsd-emulation Thu Mar 1 22: 3: 2 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from aeon.conundrum.com (aeon.conundrum.com [216.191.219.140]) by hub.freebsd.org (Postfix) with ESMTP id 4A92637B719 for ; Thu, 1 Mar 2001 22:02:59 -0800 (PST) (envelope-from mattp@conundrum.com) Received: from smtp.conundrum.com (smtp.conundrum.com [216.191.219.134]) by aeon.conundrum.com (8.9.3/8.9.2) with ESMTP id BAA28535 for ; Fri, 2 Mar 2001 01:02:58 -0500 (EST) (envelope-from mattp@conundrum.com) Date: Fri, 2 Mar 2001 01:02:58 -0500 (EST) From: Matt of the Long Red Hair To: freebsd-emulation@freebsd.org Subject: doscmd booting floppy on 4.1.1-STABLE Message-ID: X-URL: http://www.conundrum.com/~mattp/ X-PGP-Fingerprint: 40 E8 24 BC C1 98 00 F2 56 2F F6 7B 36 34 58 01 X-NIC-Handle: MP1229 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having some issues getting doscmd going under 4.1.1-STABLE (Nov 4, 2000). I've started with the example from the man page, using the following .doscmd file: assign A: /dev/fd0.1440 1440 assign A: /dev/fd0.720 720 assign hard drive-c 1224 15 17 I have two bootable DOS floppies: an 720K IBM DOS 5.0 install and a 1.44M MS DOS 6.22 install. Neither seems to want to boot. My doscmd session looks like this: % doscmd -b Unknown interrupt 15 function 4101 Unknown interrupt 15 function 8706 at which point doscmd hangs -- I can ^C out of it. I've tried commenting out the assign lines I don't need, and tried a variety of fd0 device files to access the floppies.. fd0a, fd0c, rfd0.720, rfd0.1440, etc. and nothing works. When I seem to be on the right track, I get the interrupt errors as above, if I'm off track I simply get short read errors from the device. The 'drive-c' file has been touched, but even with that assign commented out I get the same errors. I've attempted this as root, and as a user in group operator (/dev/fd0* are all group operator), and I've even tried turning on the group write bit on /dev/fd0*. In short, I've run out of troubleshooting ideas, and am beginning to think that this is a problem with with 4.1.1-S as of the date I cvsup'd it. I have done a search through the -emulation archives, and haven't seen anything related to this. Is this possibly a known issue, or am I missing something obvious, or what? Any help is appreciated. Matt Pounsett ---------------------------------------------------------------------- ``Chaos often breeds life, when order breeds habit.'' -- Henry Brooks Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message