Windows uses letters to represent physical drives on your machine, making it a lot easier to understand what’s happening where.<\/p>\n
The problem with Windows’ method of labeling the physical volumes and their respective partitions is that if you dual-boot, most of the time overlaps will occur. Right now it is all too likely that if you dual-boot you have different partition labels “facing” each operating system that don’t seem to add up. To clarify (just an example):<\/p>\n
Windows XP (installed on the first partition of the first drive) sees:
\n1. C:\\ for the XP partition
\n2. D:\\ for the Vista partition
\n3. E:\\ for a common data partition shared between the two<\/p>\n
Windows Vista (sitting on the first partition of the\u00a0second<\/em>\u00a0drive) sees: So what’s the right way to use drive letters in EasyBCD? It’s quite simple, actually:\u00a0Always use the drive letters that operating system\u00a0you are currently booted into<\/em>\u00a0sees!<\/strong><\/p>\n EasyBCD “translates” the letters that\u00a0current<\/em>\u00a0OS sees into numbers for the drive and partition. So if you’re in XP and EasyBCD asks for the Vista drive, tell it\u00a0 Different operating systems number their drives and partitions in different ways. The debate on the “right” way to do this is as old as time itself, and goes back to whether you consider “0” or “1” to be the “first number” in any index-based sequence.<\/p>\n The Linux Camp did it logically… For the most part. When you are dealing with Linux hard drive and partition numbers, start counting both from the number zero. For example,\u00a0 But when you’re\u00a0within<\/em>\u00a0Linux dealing with the drives and devices, you’ll be shocked (and rightly so) to realize that they’ve done away with this straightforward numbering scheme and opted to use a combination of\u00a0both<\/em>\u00a0letters and numbers… and categories too!<\/p>\n The different kind of “numbers” you will encounter in the Linux world:<\/p>\n In the list above “L” is a small-case letter, and “#” is a number. hd(#,#) has already been discussed, and is primarily used\u00a0before<\/em>\u00a0booting into Linux, in programs like Lilo and GRUB.<\/p>\n hdL# and sdL# are a bit more confusing. The “h” and “s” differentiate between IDE\/ATA drives and SATA\/SCSI drives respectively. Even more confusing, at this point numbering starts from\u00a0one<\/em>\u00a0again! So the third partition of the second\u00a0IDE<\/em>\u00a0drive on your PC is\u00a0 It gets worse. Linux doesn’t actually understand\u00a0 Ironically, in an attempt to make things a bit “easier,” certain Linux distributions (mostly just Ubuntu) now use sdL# notation for everything. Basically they’ve “merged” the two hdL# and sdL# lists into one, which does make it easier in a way\u2026 except of course that you don’t know whether it’s IDE or SATA drives that get listed first!<\/p>\n Microsoft may have picked a more unusual method of “counting” the drives and partitions, but at least they stuck to it the whole way through. Despite its weirdness, it’s quite easy once you get what’s going on:<\/p>\n On Windows (and therefore, in EasyBCD as well\u2026 for the most part), drives start counting at 0,\u00a0but partitions start from 1<\/em>! So drive 0, partition 2 is the\u00a0second<\/em>\u00a0partition of the\u00a0first<\/em>\u00a0hard drive. Drive 3 partition 1 is the first partition of the\u00a0fourth<\/em>\u00a0drive, and so on and so forth.<\/p>\n This may seem a bit off at first, but there’s a good reason for this. In Windows, you can access the MBR (something EasyBCD does quite often) of each drive by setting the partition equal to zero. So drive 0 partition 0 is actually the\u00a0MBR<\/em>\u00a0of the first hard drive. However, when dealing with EasyBCD and most other Windows programs, you will never reference the MBR, so just remember that drives start from 0 and partitions from 1. Even in boot.ini.<\/p>\n","protected":false},"excerpt":{"rendered":" Drive Letters Windows uses letters to represent physical drives on your machine, making it a lot easier to understand what’s happening where. The problem with Windows’ method of labeling the physical volumes and their respective partitions is that if you dual-boot, most of the time overlaps will occur. Right now it is all too likely […]<\/p>\n","protected":false},"author":505,"featured_media":0,"parent":64,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-258","page","type-page","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\t\n\t\t
\n1. C:\\ for the\u00a0Vista<\/em>\u00a0partition
\n2. D:\\ for the XP partition
\n3. E:\\ for the data partition<\/p>\nD:<\/code>, because that’s what XP thinks it is. Nevermind what Vista believes, it’s the operating system\u00a0you are currently in<\/em>\u00a0that matters.<\/p>\nDrive Numbers<\/h2>\n
Linux<\/h3>\n
(hd0,1)<\/code>\u00a0is the\u00a0second<\/em>partition of the\u00a0first<\/em>\u00a0hard drive. Pretty easy to follow, just\u00a0(hdd,p)<\/code>\u00a0where the second ‘d’ is the drive number and the ‘p’ is the partition number.<\/p>\n(hdx,y) syntax<\/h4>\n
(hd0,0) first primary partition on first hard disk\r\n(hd0,1) second primary partition\r\n(hd0,2) third primary partition\r\n(hd0,3) fourth primary partition (usually an extended partition)\r\n(hd0,4) first logical partition\r\n(hd0,5) second logical partition ...<\/pre>\n
Other syntaxes<\/h4>\n
\n
sdX vs hdY<\/h4>\n
hdb3<\/code>\u00a0while the second partition of the first SCSI drive on your machine is\u00a0sda2<\/code>. Confused yet?<\/p>\nsda1<\/code>\u00a0as referring to a drive \u2013 it’s just a combination of letters and numbers to it. To make Linux understand what you want, you have to prefix the letter & number combination with\u00a0\/dev\/<\/code>. So if you’re in the console and you want to tell Linux to access the 2nd partition of the 3rd SCSI drive, you would have to actually write\u00a0\/dev\/sdc2<\/code>.<\/p>\nWindows<\/h3>\n