From owner-freebsd-current@FreeBSD.ORG Wed Jun 16 07:56:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B84AF16A4CE for ; Wed, 16 Jun 2004 07:56:53 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with SMTP id 59EAF43D2F for ; Wed, 16 Jun 2004 07:56:53 +0000 (GMT) (envelope-from davehart@gmail.com) Received: by mproxy.gmail.com with SMTP id 34so71470rnh for ; Wed, 16 Jun 2004 00:56:10 -0700 (PDT) Received: by 10.38.97.26 with SMTP id u26mr107509rnb; Wed, 16 Jun 2004 00:56:10 -0700 (PDT) Message-ID: <85d95418040616005652adb3b7@mail.gmail.com> Date: Wed, 16 Jun 2004 07:56:10 +0000 From: Dave Hart To: Chris Pepper In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: cc: freebsd-current@freebsd.org Subject: Re: ACPI hangs on HP 7915 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2004 07:56:53 -0000 On Wed, 16 Jun 2004 00:58:15 -0400, Chris Pepper wrote: > > I'm going to try upgrading the PhoenixBIOS from 3.04 to 3.07 > ("Core Version" is at 4.06 -- I don't see an update), if HP and > Windows XP can agree on what a Windows executable is > > (Windows won't run the self-extractor -- may try WinZip next). If the BIOS download .EXE is supposed to create a floppy, invoking it under Windows' forcedos might do the trick. Save the .EXE somewhere, open a command prompt, and do something like: cd \download forcedos biosdl.exe Typically the problematic .EXEs are combined OS/2 and DOS binaries ("bound EXEs") and the OS/2 emulation on Windows doesn't include direct disk access bypassing the filesystem as needed to write a floppy image. Forcing it through Windows' DOS emulator allows it to work. Incidentally, typically the DOS program in such "bound" OS/2 and DOS .EXEs is just a small OS/2-compatible loader and emulator for common and single-tasking OS/2 system interfaces. In other words, the same code is running either way, but it presents to the OS as needed as either OS/2 or DOS. Dave Hart