href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 4/19/2012; last Web page update:
-2/1/2014, referencing rEFInd 0.8.5</p>
+2/8/2015, referencing rEFInd 0.8.6</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>
to boot Windows with rEFInd, since Windows stores its EFI boot loader
on the (FAT) ESP, and the BIOS boot process (generally used when
dual-booting on a Mac) relies only on the partition's boot sector,
- which is read without the benefit of this driver. You might use this
- driver if you want to store large boot files, such as EFI-accessible
- RAM disk images, from Windows. Also, if you have NTFS data partitions
- on a Mac, loading this driver should exclude them from the boot menu;
- and you should see NTFS volume names in the boot menu on a Mac if you
- load this driver.</li>
+ which is read without the benefit of this driver. Reasons to use this
+ driver include:
+ <ul>
+ <li>If you want to store large boot files to be read from EFI, such as
+ RAM disk images, from Windows.</li>
+ <li>If you have a Mac and NTFS data partitions, loading this driver
+ should exclude those data partitions from the boot menu.</li>
+ <li>If you have a Mac that dual-boots with Windows, using this driver
+ should provide NTFS volume names in the boot menu.</li>
+ </ul>
+ </li>
</ul>
<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>