Date: Wed, 16 Jun 2004 07:56:10 +0000 From: Dave Hart <davehart@gmail.com> To: Chris Pepper <pepper@reppep.com> Cc: freebsd-current@freebsd.org Subject: Re: ACPI hangs on HP 7915 Message-ID: <85d95418040616005652adb3b7@mail.gmail.com> In-Reply-To: <p06200101bcf55bcf3548@10.0.1.102> References: <p06200101bcf55bcf3548@10.0.1.102>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Jun 2004 00:58:15 -0400, Chris Pepper <pepper@reppep.com> 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
> <http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?product=62761&os=228&cc=us&lc=en&dest_page=softwareCategory&tool=softwareCategory&dlc=en&softwareitem=pv161en>;
> (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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85d95418040616005652adb3b7>