From owner-cvs-sys  Thu Jul  2 08:39:27 1998
Return-Path: <owner-cvs-sys>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA11921
          for cvs-sys-outgoing; Thu, 2 Jul 1998 08:39:27 -0700 (PDT)
          (envelope-from owner-cvs-sys)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11460;
          Thu, 2 Jul 1998 08:37:51 -0700 (PDT)
          (envelope-from wpaul@FreeBSD.org)
From: Bill Paul <wpaul@FreeBSD.ORG>
Received: (from wpaul@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id IAA08204;
	Thu, 2 Jul 1998 08:36:36 -0700 (PDT)
Date: Thu, 2 Jul 1998 08:36:36 -0700 (PDT)
Message-Id: <199807021536.IAA08204@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/i386/boot/biosboot start.S
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

wpaul       1998/07/02 08:36:36 PDT

  Modified files:
    sys/i386/boot/biosboot start.S 
  Log:
  Add workaround to allow the FreeBSD boot block to work on
  Kapok Computer Co. notebook with AMI 'WinBIOS' which seems to insist
  on having a short jump and nop as the first instructions in the
  boot sector code. The prevailing theory is that the BIOS is doing
  some sort of boot sector virus detection and refusing to run any
  boot block that doesn't start with the same instruction sequence as
  MS-DOG boot sector code. If this is the case, it would be nice if it
  actually printed an error message to this effect instead of just
  saying 'FAILED.'
  
  This workaround has no effect on the boot sector code other than to
  increase its size by three bytes.
  
  Revision  Changes    Path
  1.11      +13 -1     src/sys/i386/boot/biosboot/start.S