href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-7/6/2014, referencing rEFInd 0.8.3</p>
+2/1/2014, referencing rEFInd 0.8.5</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>
upper-left corner of the screen. Having an option to support a
transparent background is desirable to some users.</li>
- </ul></li> <!-- Improvements -->
+ <li>When delivering rEFInd as a boot loader from a network server,
+ rEFInd is limited to its default options and can boot only local
+ OSes, not network OSes. The cause is that the server delivers a
+ single file, so rEFInd is divorced from its configuration and
+ support files.</li>
+
+ <li>A way to identify specific Windows versions and present unique
+ icons or change the text is desirable. Currently, a crude
+ distinction of XP and earlier vs. Vista and later is possible for
+ BIOS-booting on Macs, but no such distinction is made for EFI-mode
+ booting, and nothing finer-grained is attempted. Improvements will
+ probably require identifying unique features of each version's boot
+ loader files or boot sector code.</li>
+
+</ul></li> <!-- Improvements -->
<li><b>Known bugs that need squashing:</b>
have the equipment and skill to do so, I'd be interested in
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>
+
<li>The re-scan feature occasionally produces odd results, such as
ignoring new media or keeping old media that have been ejected.
This should be investigated and fixed.</li>
<ul>
- <li>EFI supports network boots. rEFInd doesn't, but it would be nice if
- it would.</li>
-
<li>There's currently no way to create a manual boot stanza for a
BIOS-booted OS. This isn't a big priority for me personally, but I
can see how it could be for some people.</li>
stanzas override auto-detected boot loader definitions for the same
boot loader file.</li>
+ <li>Along similar lines, some users have asked for a way to take
+ detected boot programs and create a set of manual boot stanzas for
+ them, so that they can be modified manually.</li>
+
+ <li>Support for touchscreens and/or configurable buttons for rEFInd's
+ actions would enable use of rEFInd on tablet computers that lack
+ complete keyboards.</li>
+
+ <li>GRUB provides a configuration-file command called <tt>outb</tt>
+ that enables manipulating hardware registers. Something similar,
+ via the <tt>mm</tt> command, can be done in the EFI shell. I'd like
+ to add such a feature to rEFInd, since it enables doing things like
+ disabling one or another video output on Macs with two video
+ cards.</li>
+
<li>I have thoughts about creating an EFI configuration tool and
information utility—something to tell you about your hard
disks, enable you to manage MOKs, adjust boot loader priority in
that there were problems with the installation, although this isn't
really the case.</li>
+ <li>rEFInd's support for network booting is primitive and relies on the
+ external iPXE package. In my own testing, iPXE retrieves the
+ BIOS-mode boot loader from some servers that offer both, which
+ makes it useless on those networks.</li>
+
<li>A Mac-specific package is highly desirable.</li>
</ul></li>