From owner-freebsd-current Thu Jul 23 11:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01687 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:15:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01664 for ; Thu, 23 Jul 1998 11:15:09 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id OAA00841 for ; Thu, 23 Jul 1998 14:14:41 -0400 (EDT) Date: Thu, 23 Jul 1998 14:14:41 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: More doscmd adventures/lockups Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yessiree, doscmd has ways of locking me up without a panic. I'll explore what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... after Starting msdos... the whole computer froze, I waited a few minutes, and hit reset when I was sure it was locked up solid. To recap: bochs was loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot the drive; this was standard access, no vn(4) problems. Cheers, Brian Feldman green@unixhelp.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message