From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v4QDQfIs022535 for ; Fri, 26 May 2017 09:26:41 -0400 Received: by smtp.corp.redhat.com (Postfix) id 0BD0F7BCC1; Fri, 26 May 2017 13:26:41 +0000 (UTC) Received: from mx1.redhat.com (ext-mx05.extmail.prod.ext.phx2.redhat.com [10.5.110.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 063DF7C776 for ; Fri, 26 May 2017 13:26:39 +0000 (UTC) Received: from omta01.suddenlink.net (omta01.suddenlink.net [208.180.40.71]) by mx1.redhat.com (Postfix) with ESMTP id D310A37EEB for ; Fri, 26 May 2017 13:26:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com D310A37EEB Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=suddenlink.net Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=martin.m@suddenlink.net DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com D310A37EEB Received: from localhost ([47.217.105.76]) by dalofep01.suddenlink.net (InterMail vM.8.04.03.22 201-2389-100-167-20150619) with ESMTP id <20170526132634.MUHJ5456.dalofep01.suddenlink.net@localhost> for ; Fri, 26 May 2017 08:26:34 -0500 Received: from localhost ([127.0.0.1]:53035) by localhost with esmtp (Exim 4.80) (envelope-from ) id 1dEFGD-0001SB-Ni for blinux-list@redhat.com; Fri, 26 May 2017 08:26:33 -0500 To: blinux-list@redhat.com Subject: Command-line DOS Emulators MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5589.1495805193.1@localhost> Date: Fri, 26 May 2017 08:26:33 -0500 Message-Id: X-Cloudmark-Analysis: v=2.2 cv=F/wVTepN c=1 sm=0 tr=0 a=kj9zAlcOel0A:10 a=tJ8p9aeEuA8A:10 a=qXzEXkxMQUacSq-gsp4A:9 a=CjuIK1q_8ugA:10 X-Greylist: Sender passed SPF test, Sender IP whitelisted by DNSRBL, ACL 203 matched, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 26 May 2017 13:26:38 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 26 May 2017 13:26:38 +0000 (UTC) for IP:'208.180.40.71' DOMAIN:'omta01.suddenlink.net' HELO:'omta01.suddenlink.net' FROM:'martin.m@suddenlink.net' RCPT:'' X-RedHat-Spam-Score: 2.998 ** (BAYES_99, BAYES_999, RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD, SPF_PASS) 208.180.40.71 omta01.suddenlink.net 208.180.40.71 omta01.suddenlink.net X-Scanned-By: MIMEDefang 2.78 on 10.5.110.29 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2017 13:26:41 -0000 What I want to do is see what a particular DOS diskette prints when one boots it up. I downloaded a zip file that has a whole tool kit of interesting goodies that will let a person boot an older PC from a usb drive even when the system in question has no usb drivers in it's BIOS. The DOS disk simply has a usb driver which probably runs just long enough to allow a bootable thumb drive to get a Linux or other kernel up and running which then goes through it's boot sequence, sort of a case of a boot for a boot. This application is called plpbt and was written in Germany but the English documentation is very good. I guess one could even boot a version of Windows this way but as soon as the usb drive begins it's boot procedure,one isn't going to gain anything in accessibility. What I am interested in is what shows up on the screen so I will know what keys to press when booting it blind, so to speak. I should also add that if the dos disk writes directly to video memory, this is not going to work but my question again is strictly about a way to run the DOS boot far enough to get some output. For those who are curious, the zip file is called plpbt-5.0.15.zip My hopes are to use the dos to usb booter on a couple of Dell systems I have that tend to keep rearranging their boot order so that the hard drive boots the system if there is no floppy, leaving the CDROM drive for last. When that happens, you can't just try a live CD without first going in to the BIOS setup which, as we all know is a royal pain on the vast majority of PC's. If this works, I can beat those systems at their own game and start the boot from a floppy. Thanks for any constructive ideas. Martin McCormick