[syslinux] Win32 syslinux needs to support mount points, disk numbers or volume names in addition to drive letters

[Shao Miller]

On 5/14/2012 17:41, Robert wrote:
> This is just a follow up to the reply (by Gene)to the subject (see 
> subject line) that I initiated earlier.

Newlines, please.  Again, I've inserted some.

> 1. It seems to me when talking about replacing the MBR and making a 
> drive bootable by mark one of the partitionsactive(in Windows), disk 
> numbers are the ones that make the most sense. Because a disk number 
> represents the entire disk not just a partition of it. Don’t you think?

I believe that you either don't understand how the PC BIOS boot process 
works, or there is a communication failure.

Installing a Syslinux MBR doesn't tell BIOS which disk to boot from.  
This is why disk number is a silly choice as a parameter to the Syslinux 
installer.

My understanding is the the Syslinux installer's purpose is...  To 
install Syslinux to a filesystem.  The option to install an MBR on the 
disk containing that filesystem is a bonus; it is obvious which disk to 
use (without considering RAID scenarios).

> Any drive letter may just represent a partition of the disk. Volume 
> name is also unique 
> (\\?\Volume{f3421bd0-145d-11e0-9cd0-00270e03f84a}\) and usable. MBR 
> belongs to the disk not partitions; drive letters represents 
> partitions. So disk number is the more qualified than drive letters.. 
> Just my 2 cents.

Why would you install an MBR to a disk that doesn't contain the 
filesystem that you're installing Syslinux into?

- Shao Miller