href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-4/24/2016, referencing rEFInd 0.10.3</p>
+10/9/2016, referencing rEFInd 0.10.4</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>
0.8. Developing a better solution to that problem is a high
priority.</li>
- <li>The support for booting legacy (BIOS) OSes on UEFI-based PCs
- currently has a number of limitations. Most importantly, it works
- off of the list of boot devices stored in the computer's NVRAM. I'd
- prefer to have it scan disks and partitions, as the Mac's legacy
- boot support does. Also, the UEFI legacy boot code presents empty
- optical drives and uses generic icons rather than OS-specific
- icons.</li>
-
<li>rEFInd's <tt>Makefile</tt>s and, to a lesser extent, C code,
support <i>x</i>86, <i>x</i>86-64, and ARM64 CPUs. EFI is also
available for Itanium (IA-64) and ARM32 CPUs, so I'd like to add
probably require identifying unique features of each version's boot
loader files or boot sector code.</li>
+ <li>The support for booting legacy (BIOS) OSes on UEFI-based PCs
+ currently has a number of limitations. Most importantly, it works
+ off of the list of boot devices stored in the computer's NVRAM. I'd
+ prefer to have it scan disks and partitions, as the Mac's legacy
+ boot support does. Also, the UEFI legacy boot code presents empty
+ optical drives and uses generic icons rather than OS-specific icons.
+ This said, BIOS support is becoming increasingly unimportant as the
+ transition from BIOS to EFI continues, so I'm unlikely to put effort
+ into this issue myself.</li>
+
</ul></li> <!-- Improvements -->
<li><b>Known bugs that need squashing:</b>
debugging, especially when dealing with problem reports from
users.</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>
-
<li>I'd like to find a way to enable users to enter customizations for
boot options and then save them to the <tt>refind.conf</tt> file.
One possible way to implement this would be to have manual boot
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>Better support for touchscreens and/or configurable buttons for
+ rEFInd's actions would enable use of rEFInd on tablet computers that
+ lack complete keyboards. (Version 0.10.4 supports <i>some</i>
+ touchscreens, but this feature relies on support in the firmware,
+ which is not universally present.)</li>
<li>The ability to rotate the display for users who rotate their
monitors or who use tablets would be helpful.</li>
to visually impaired users when rEFInd is ready to accept input would be
helpful.</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>
+
</ul></li> <!-- New features -->
<li><b>Improvements to the EFI drivers:</b>