<link href="../Styles/styles.css" rel="stylesheet" type="text/css" />
</head>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+
<body>
<h1>The rEFInd Boot Manager:<br />The Future of rEFInd</h1>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-2/1/2014, referencing rEFInd 0.8.5</p>
+3/1/2015, referencing rEFInd 0.8.7</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
receiving a patch.</li>
<li>If you use a true MBR disk on a Mac to boot Windows or some other
- BIOS-only OS, and if that disk has an extended partition, that
- partition may show up in rEFInd as a bootable FAT partition. The
- reason is twofold: FAT doesn't contain a simple "magic" signature
- like most filesystems, so it's easy to misidentify something else
- as FAT; and it's hard to positively identify boot code vs. other
- random data.</li>
+ BIOS-only OS, and if that disk has an extended partition, bogus
+ additional BIOS/legacy-bootable options may appear in the rEFInd
+ menu. The reason appears to be a bug in the handling of
+ extended/logical partitions in the <tt>refind/lib.c</tt> file, but
+ I haven't fully tracked it down.</li>
<li>The re-scan feature occasionally produces odd results, such as
ignoring new media or keeping old media that have been ejected.
<hr />
-<p>copyright © 2012–2014 by Roderick W. Smith</p>
+<p>copyright © 2012–2015 by Roderick W. Smith</p>
<p>This document is licensed under the terms of the <a href="FDL-1.3.txt">GNU Free Documentation License (FDL), version 1.3.</a></p>