Slashdot Mirror
Windows XP and Incompatibilities with Multi-Booting?
Morgan asks: "
Windows XP (Whistler) won't boot from disks with MBR partition tables, requiring a new GUID Partition Table (GPT). It will still read and write MBR disks. In a cursory search, I find no work to support GPT with LILO or other multi-booting Linux loaders. I'm a 'one OS, one disk' man, especially since disks are so cheap, but what about those who aren't handy with a screwdriver (and an IDE cable)? An easily installable Linux distro that shrinks the Windows partition, but allows multi-booting without requiring a re-install of Windows is a great Trojan horse: 'here, try this real OS, but if you don't like it, or you need a particular app, you can always boot Windows.' Will GPT make this harder?" What reasoning was behind the move to GPT? By making Whistler incompatible with the standard MBR, this could be seen by many as another move to stifle competition in the PC market. How do you feel about it?
Yeah, and issuing a mandatory federal ID card could be seen by many as government oppression. Which, of course, would not be true.
Microsoft is not under any obligation to make their operating system to coexist with other, competing operating systems. Insisting that a corporation, which is in business to make money, should respect competing products is just plain lunacy.
Your CS prof must consider the entire open source movement an exercise in stupdiity, then. For that, his comments warrant no creditiblity whatsoever.
...not been developed as a result of a requirement analysis.
...not been designed before coding.
...not been audited before coding.
...not been formally block tested.
...not been formally integration tested.
...not been formally documented, meaning all the steps mentioned above.
a)
Open source software, in general, comes into being as a result of a coder scratching a personal itch. This is about as close to a requirements analysis as you'll get, and it's good enough for me. A coder had the presence of mind to notice a lack, and he set out to meet it.
b)
Well, it's a safe bet a lot of OSS coders actually do have educations, and are at least marginally intelligent. So yes, at least some of the projects are designed.
c)
Extraneous formality that doesn't really fit into the type of development models most OSS projects employ.
d)
e)
f)
See above. Do we look like a bunch of coders in suits to you? Reality check time. If the OSS world worried about this sort of formaility, nothing would ever get done. Sheesh, get your head out of the sand.
Dealing with for-profit corporations is very easy. When you buy their product, you are giving a vote of confidence and approval in them - their products, their people, and their practices. When you don't buy their products, you are doing just the opposite. Since they want to make money, successful for-profit corporations will alter their products, people, and practices in ways that maximize the number of people who buy their products. If you buy a product from a company of which you do not approve, you are voting for Buchanan when you claim you wanted Gore. And, like those who did that, you are being incredibly stupid.
Proudly 100% Microsoft-free for over 5 years.
The Extensible Firmware Interface (EFI) is an attempt to bring ancient PC "standards" up to something reasonable. Almost all hardware and OS/driver vendors are _for_ this. This is an attempt to give PC's real firmware, rather than the hack they have now.
If you've ever used big iron UNIX hardware, you've probably enjoyed the conveniance that the firmware itself provides (or maybe not).
Replacing the MBR is one aspect of this. This is not something to worry about unless MS pulls the embrace and extend crap, but I doubt they'd stoop to it on such a low-level aspect.
With some exceptions, all OS, Driver, and Hardware developers/vendors want EFI.
Possible conspiracy theories:
Realistically, the worst that EFI can do is give us something better than what we have now. At best, it could make PC's pleasurable (but don't bet on it).
Any time Microsoft does something which is an improvement it is an attempt to stifle competition.
.Net, etc. :(
Look at the recent whining regarding
It's just a fact of life, we move on and ignore these people.
Actually, VAX is a hardware architecture, not an OS. Normally, you'd run VMS on it, which I agree was a pretty good OS. But you could also run Ultrix (a UNIX variant) on it. There is a project porting Linux to it as well. But I doubt that you could set up any multi-boot on it.
Software sucks. Open Source sucks less.
Yes, this sucks. I highly doubt there's any good technical reason to go to this other boot record system. Honestly it just seems mean.
/other/ product /less/ attractive.
But it is competitive, not "stifling to competition". A better choice of words would be "stifling to THE competition," similar words, but diametric meanings.
Despite what economics textbooks say, competition isn't a market state, it's a process. When one firm drives another out of business with lower prices (ala Wal Mart), that's competition. When one firm makes its product more attractive than the other guys' to buyers, that's competition.
What MS is doing here is basically an odd case of that second point. By making it more difficult to use their product alongside a competing product, they are (to some degree) making their product relatively more attractive, essentially by making the
For another example, consider if a car maker had a policy that if you used aftermarket parts in significant repairs (eg: new brakes, cylinder heads, etc), it voided part of the warranty. This causes the buyer to lean toward using the dealer's repair services or at least official factory parts rather than (possibly cheaper and/or "better") aftermarket parts. It's not nice, it may actually be detrimental to consumer utility, but it's COMPETITIVE.
MoNsTeR
Well, none unless one wants to remove many of the more arcane constraints of MBR. Frankly everyone who knows anything about drives and layouts agrees MBR was obsolete over a decade ago and should been retired back then.
Furthermore for most users this won't be a big deal, certianly not for Jane-hobbyist. If you actually bothered to do a bit of research you'll discover that this implementation is fairly backwards-amendable except for some high-end configurations where it's unlikely to be an issue anyhow.
Finally, hard drives retail for ~US$100/20GB, anyone installing XP is likely to be able to pony up the cash. This change won't affect ye olde 486s.
By your logic is any hardware advancement possible or shall the industry remain forever stuck in 1980's technology? At least Apple moved to OpenFirmware along with the rest of the workstation market or is that somehow part of an evil plot too? Ahh, so it's not StUdLy enough for yeah, huh? Luckly you'll be able to change the chrome to a camoflauge background and Matrix-themes to assauge your offended aesthetics. Debunked. Yeah, patching things Baaaaadddd... right. Doi! The market gets what it buys. IS Depts & consumers continue to buy on sizzle & psuedo-feature sets then MS will continue selling it to them. It built a megacompany so they're doing something right.I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
Check out hardware prices, and what users were willing or able to pay, and the state of the art at the time, and you'll see that those limitations weren't so arbitrary.
Of course that doesn't make them any less infuriating, but if Henry Ford had tried to design the Model T so that you could easily retrofit disc brakes, air bags, electronically controlled fuel injection, and emission control plumbing, he'd have burned through all his venture capital before he ever got any product out the door.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
How many primary partitions can you have on a SCSI hard drive? How many extended? How many logical in an extended?
I see even classic Slashdot is now pretty much unusable on dial up anymore.
WD drives (but not Maxtor, annoyingly) will take a 10 pin socket (like on serial port header connectors) which will make it easier to get the wire length that you need, but why screw around with printed circuit boards, headers, etc., when you can just solder the other ends to a double-pole, double throw switch?
I see even classic Slashdot is now pretty much unusable on dial up anymore.
Actually "...cause more problems than Win2K." makes just as much sense in that context, maybe more.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
I hope you're not thinking that Windoz would be better... At least Linux can be trimmed down to a very small amount of code to fit the purpose. If someone is dumb enough to blindly take Linux code and run a Nuke sub or powerplant with it then we are in trouble. I don't think engineers working on this type of equipment are that dumb. Though I have seen the BSOD on way too many non critical devices ( scoreboards, billboards, airline screens, etc ). If engineers are dumb enough to use Windoz on mission critical devices.....
NOW THAT SCARES ME! Oh wait, isn't Bill Gates paying the US DOD to use Windoz on Aegis class ships and a new aircraft carrier? ;)
Time to head for the hills.
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
Or, indeed, problems such as making sure your cruise missiles don't hit non-combatant's embassies...
-- Proud descendant of semi-nomadic cattle-herders.
From your first link, it looks like the new boot process requires some small partitions (ESP Extensible Firmware Interface System Partition and MSR Microsoft Reserved Partition.)
Shades of the old OS/2 boot manager partition or the EISA Config partition that seemed to confound certain users with itchy FDISK fingers.
Anyway, it's nice to see something that looks like real boot firmware and not a CP/M-compatible kludge. Any hope of support for this on standard IA32 boxes?
--
Business. Numbers. Money. People. Computer World.
After the marketing implosion of the PIII CPUID, the BIOS spec was altered so that it provides a unique ID number for each motherboard (which is a better solution than a CPU ID even for the assent management departments that wanted this sort of thing).
This is really nothing new either, custom BIOSes from IBM and Compaq have provided serial numbers for years and years, it's just now a standard call so that Windows can get this info and use it for it's registration voodoo.
Anyway, it's only in the last couple years that PCs have had a GUID number other than the NIC.
--
Business. Numbers. Money. People. Computer World.
Is it your intention to make the Linux community look like idiots? Seriously. You post these half-baked articles so frequently, often incorrect and always misleading, and they always get the community fired up to the point of seeing who can make the dumbest post about something that's not even true.
Not sure how many people here are familiar with it, but it's almost like a digital equivalent of the Phil Hendrie Radio Show. It's a hilarious show, btw, if anyone has a chance to listen to it. He'll have guests on (actually voiced by himself) who make dumb and subtly inflammatory comments, but keeping it halfway believable. So every show, you end up with all these people calling up the show and getting irate arguing with some fictional character. (Hendrie = ./ editors, Guest = story submission, Callers = Linux advocate posters). In both places the comedy comes in large part from listening to or reading the opinions of the idiots who believe what they just heard and subsequently make incredible asses of themselves.
Cheers,
When you look at other partitioning schemes (such as the RDB system that the Amiga has used since the 80s) the whole MBR/fdisk thing is a complete joke. The anachronistic partitioning system on x86 PeeCees has caused me to waste significant time on something that should be trivial, and there's a whole sub-industry of bootloaders and utilities just to get around the arbitrary limitations that were built in by some visionless idiot in the early 80s.
Dumping it is a good move. And I note that this time (for a change) MS isn't replacing it with a proprietary decommoditized MS-only defacto standard de jour. This one is open and anyone can be compatable with it. What's not to like?
---
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
Until we get mother boards that includes the new EFI approach, we will definetly see transition solutions to support GPT drives.
It will be great to have this technology - sure it will break a lot of the old systems, but then again sometimes when you go forward there are sacrifices to be made.
If MS has decided to limit the addition of GPT support for 64-bit XP, then this is probably because 64-bit motherboards would break most 32-bit OS anyhow, and thus they are unlikely to have people complaing that Windows 98 doesn't work on those machine.
For more info on EFi and GPT, check ou the following link: http://developer.intel.com/technology/efi/download .htm
Jumpstart the tartan drive.
I think we need to suspend paranoia mode for a second here.
:)
At the risk of sounding like "user friendly" software, Are you sure?
From the GPT/EFI FAQ:
Each GPT partition has a unique identification GUID and a partition content type, so no coordination is necessary to prevent partition identifier collision.
With a unique identification, is it possible that this could be used for some basic, broken form of DMCA-style "content protection"?
My journal has hot
I'd just like them to stop posting ask /.'s that are obviously flamebait. I mean, even ignoring the fact that this submission wasn't news worthy, (who's going to be running a dual boot on a IA64? And where are they so I can punch them in the face?) It's worded to get the hot-heads going.
/. could go a long way by not baiting the morons out there, But hey, maybe that's what they're after anymore. Maybe prepping for a new fox special they're trying to push, "When Angry, Misinformed, Geeks Attack!!"?
As stated in the Win XP FAQ, GUID partitioning is a replacement for MBR partitioning that allows more partitions on the disk, of any size, without the silly BIOS limitations. It's a part if EFI, the Extensible Firmware Interface that is replacing the old hairball that is the BIOS. The IA-64 Linux distributions already have a version of LILO that works with EFI.
In short, don't worry, Linux adapts, as it always does.
Meldroc, Waster of Electrons
I have 2 dual boot boxes running XP Beta 2 and Mandrake 8.0. It's using Mandrake's graphical LILO as a bootloader, and it's working just fine. Is this something that will be "implemented" for the final release of XP?
Need Free Juniper/NetScreen Support? JuniperForum
Note that this only applies to the 64-bit (Itanium) version of XP, not the 32-bit.
Just goes to show how many slashbots are ready to flame without even reading the material linked to (about 30% at the time I was reading, comments at +1 and above). That's a scary amount of political power if CmdrTaco is ever looking to mobilize the ignorant forces...
:)
deus does not exist but if he does
Yes.
14. Can the 64-bit version of Windows Whistler read, write, and boot from MBR disks?
The 64-bit version of Windows Whistler can read and write MBR disks, but cannot boot from MBR disks.
15. Can the 32-bit version of Windows Whistler read, write, and boot from GPT disks?
No. The 32-bit version will see only the Protective MBR. The EE partition will not be mounted or otherwise exposed to application software.
16. Can the 32-bit version of Windows Whistler read, write, and boot from MBR disks?
Yes.
Note that this only applies to the 64-bit (Itanium) version of XP, not the 32-bit. Frankly, I wished it worked with the 32 bit version too, since the current MBR-based scheme sucks. Try having FAT + NTFS + Linux + FreeBSD + Plan 9, etc on one disk and you'll wish for something better too.
False. As a monopoly, Microsoft has to be careful that its actions do not act exclude competitors from the marketplace. In this case they deviated from a long-time practise for no other reason than to make things more difficult for its competitors. It took EFFORT for Microsoft to make this change, a change that hardly affects anyone outside of Powerquest, the Linux distributions and the *BSD flavours. It is a clear-cut abuse of their market power, and yet another annoyance we can chalk up to them. But its not so big a deal, because it's a temporary annoyance. Red Hat, Debian et. al. will find some way to deal with it, and things will be back to normal.
"Anyone that has ever gotten an idea based on any of my work and done something better with it-good for you."--J.Carmack
i agree that it is the responsibilty of the readers to read the stories, but the editors should bare some of this responsibility also. when you include the following in a story:
Windows XP (Whistler) won't boot from disks with MBR partition tables, requiring a new GUID Partition Table (GPT).
and add no clarification, what do you expect? my inital impression was not good, but i read further befor i started typing. hell, i'm not sure cliff read the entire story either.
use LaTeX? want an online reference manager that
-- john
The real question is if Whistler will support more than 26 partitions on a single disk.
For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
yes, it is possible. and, when you pay for phone service, they also give you a "unique identification" number. this could no doubt be used for some form of DMCA enforcement, somehow. or maybe even personal tracking! quick, run! hide from the government and corporations alike! you have been tagged, numbered, and identified--you have...a PHONE NUMBER!
those cheeky bastards.
sean
I think we need to suspend paranoia mode for a second here. according to the FAQ, the GPT disk partitioning specification is a documented Intel standard. and, really, isn't it about time for the old MBR scheme to die? the architectural limit to 4 primary partitions is getting old. GPT can scale far better and has a less arcane internal structure (cylinder and head arithmetic, anyone?)
and if you read more carefully you will see that it is only the 64-bit version of Whistler that won't boot on MBRs. the 32-bit version should boot just fine.
I think MS is just scaling with their new OS architecture. anything can be viewed through an anti-competitive lense. the important question is: will we be getting a better OS? I think so.
sean
I am not expecting /. to send investigative reporters to far off techie conventions and the like. I just want them to read through an article before they post it. I don't think I am asking too much here. This doesn't really require too much extra money. While I would love real technical editors, I understand that /. may not be able to afford it. I find it hard to believe they can't afford to read an article before they post it though.
/. is trying to manipulate readers with outrageous headlines just to get people to read on. I can't stand when traditional news sources do this and /. is no different.
/. doesn't do it on purpose. Perhaps it is just that their editors don't have the time or money to check stories before rushing them out the door. I just don't understand how someone can read a post enough to believe it is worth an AskSlashdot but not bother to read the article sourced in the post.
/. on the whole. I just think that it could be even better. The only way the powers that be will know that people want change is if they say it. So I am saying it.
What really bothers me is that often it seems that
Perhaps I am just too pessimistic and
Don't get me wrong, I really like
-- soldack
First about this post. As others have commented, this only applies to Windows XP/2002 running on IA-64 processors. All operating systems wishing to boot on these systems will need changes to work with Intel's firmware for IA64 based systems. /. that keeps raising its ugly head. All too often stories are posted that are not checked up on. I understand that those who run /. can not be expected to be experts in everything but stories are often posted that only required a simple reading of a FAQ or two to see that the post is just plain wrong. I had high hopes of /. getting much more professional when it was purchased by Andover. But nothing has changed. The staff seems about the same size and quality that it was before the corporate move. /. really has such great potential. If it could start using expert editors who only post stories that have been properly checked. One reason I love magazines like Discover and Popular Science because the stories are usually checked out pretty well. I understand the need to post things that generate interest but the site also claims to be a news site. No self respecting news site would allow such a low level of checking into the background of the stories they present. Is /. a news site at its heart or just entertainment? It has the potential to be both a high quality and entertaining news site and discussion forum. I understand that /. is a business and the object of a business is to make profits for their shareholders but I don't understand why this has to be in direct opposition to high quality.
/.er who hopes things get better...
This brings a fact about
from a
-- soldack
You don't need to throughly research the topic. Fifteen minutes of reading the site and doing some quick searches on Google would turn up enough information. Its not like these are minor errors here. These are full blown the article is attributed the wrong meaning errors. These don't take extensive research to catch.
A deep unwavering belief is a sure sign you're missing something...
Is it just me, or does anti-MS fud have a fast path to the main page somewhere in the Slash code? I'm still trying to prove that Slash has an anti-BeOS hack that requires Net+ users to type their password twice before the system accepts the login, but my new project is finding the filtering software that gives priority to MS anticompetitive stories. Seriously, though, the volume of traffic on the /. main page isn't that big. Maybe ten stories per day max. You'd think they'd actually check out the stories that make it far along in the submission processes for them to consider posting it.
A deep unwavering belief is a sure sign you're missing something...
Of course we dual booted our vaxen - VMS and Unix .... plus we ran Unix and RSX virtually under VMS (sort of a per-process dual booting :-)
Of course, the problem with that is that people will use the old way until its no longer an option.
GTP is a good thing and frankly its not Microsoft's responsibility to worry about linux dual booters. In the long run this will be good for linux, because GTP is far better than MBR which is older than the pyramids. However, in the near term this will be a huge hassel for those who know and love the current configuration of LILO and want to dual boot XP. This will really hit the small developer shop that relies on dual boots for office compatibility.
Someone you trust is one of us.
Converting MBR System Disks for 64-bit Windows Whistler
Partition Manager Help
LILO
LILO mini-HOWTO
Multi-Booting with LILO
Multiple Boot Advice for x86
The Ultimate Windows Whistler News
Usability comparison: Windows Whistler vs. Gnome 1.2, KDE 2.0, Mandrake Update
How to Download YouTube Videos
Mike
-- Could you use my software consulting serv
The article is a bit on the flamy side to bad we can't mark them as such. Reading the faq supprisingly left me with a much different attitude than I went in with. It seems if you are using XP now you can use the XP bootloader in the same way people use the NT boot loader now. This setup should work for 64bit XP and 32Bit XP. If your using 32bit xp it looks like you have a few more options however as it plainly says it can read,write and boot from MBR disks. It doesn't look all that complicated after reading the faq which is pretty straight forward. My only concern is the GUID. While I can't quesion mob mentality I can question why someone didn't read this prior to posting the story as all questions seem to be answered there in black white and blue.
36. What is a Microsoft Reserved Partition (MSR)?
The Microsoft Reserved Partition (MSR) reserves space on each disk drive for subsequent use by operating system software. GPT disks do not allow hidden sectors. Software components that formerly used hidden sectors now allocate portions of the MSR for component-specific partitions. For example, converting a basic disk to a dynamic disk causes the MSR on that disk to be reduced in size and a newly created partition holds the dynamic disk database. The MSR has the Partition GUID:
DEFINE_GUID (PARTITION_MSFT_RESERVED_GUID, 0xE3C9E316L, 0x0B5C, 0x4DB8, 0x81, 0x7D, 0xF9, 0x2D, 0xF0, 0x02, 0x15, 0xAE)
*Shiver* <paranoia> Mental note: Do not install XP, for fear of Microsoft gathering information and storing it in a hidden partition.</paranoia>
-Ted
How low can you go? The very name of the standard, "Extensible...", makes the hair on my neck stand up. You can put all your fears into this one.
BIOS extentions break stuff. I've got an Athalon board with virus protection built right in. The stupid thing recognizes LILO as a boot sector virus. I can turn it off, and I'd return it if I could not. The motherboard drivers that came with a couple of computers I've built give me the shudders.
There are two reasons I could care less about this one, however. The first is that there will be work arounds for any software I care about far sooner than for MS BS. The second reason is that I will never ever install MS BS on another computer I own.
Friends don't help friends install M$ junk.
It's Funny...laugh
--
-- @rjamestaylor on Ello
Indeed, a simple Google search reveals that the Linux community is on this.
--
-- @rjamestaylor on Ello
By making Whistler incompatible with the standard MBR, this could be seen by many as another move to stifle competition in the PC market.
I am so anti-M$ that it oozes from my pores on a daily basis. However, this is the sort of shit that the Free Software® movement needs least! We keep hearkening for Microshaft to drop their FUD campaigns, yet here we have Linux zealots blatently trumpeting the same thing. (Apropos, Cliff, I hear isopropanol does wonders for cleaning FUD out of your horn.)
The MBR-style partition table has been in use for, what, fifteen years? At least? It is a roadblock in the exploding mass-storage market. The entire concept of a maximum of four partitions (there are, after all, only four slots in an MBR partition table) was smoothed out by the molestation^Wchanging of the standard to permit "extended partitions", and within those, "logical drives". However, with hard drive capacities soon to break 100 gigabytes (!), it's high time we, as members of the computing indutry, came up with something better.
I've never heard of GUID partition tables until now, and therefore know absolutely nothing about them; therefore I can't comment on whether or not GPT is truly better. But can anything be much worse than what we're currently stuck with?
--
Looking at the FAQ page linked to, I think this is a false alarm. Microsoft has several legitimate reasons for introducing this new partitioning scheme. It is an open standard; they link to the definition here.
It looks like a lot of the reason they are doing this is support for larger systems and disks. See these Q/As:
Q: If the disk is larger than the maximum size an MBR can report, will the entire disk contents be protected? A:The EE partition in the Protective MBR is specified to be the maximum size allowable in an MBR.
So the maximum size supported by the new format is greater than the old.
Q: Can the 32-bit version of Windows Whistler read, write, and boot from GPT disks?
A: No. The 32-bit version will see only the Protective MBR. The EE partition will not be mounted or otherwise exposed to application software.
This doesn't affect your current system at all. If you install Windows Whistler on your ia32 machine, it will use the old format.
Linux already has the support for many different partitioning schemes. I don't see this as different. There is no support for it now, but there will be when someone decides to develop it.
GPT isn't proprietary, is it? If not, Linux should support it. MBR was a pain, anyway.
I've XP beta 2 and Mandrake 8.0 on one harddrive, and both boot fine, using the nice mandrake bootmenu. So where's the beef?
--
Never underestimate the relief of true separation of Religion and State.
Now admittedly, that's 32 bits of 512 byte sectors, which works out to be two terrabytes... the 128 gig limit is due to ATA's definition of LBA being 28 bits, which is due to byte-wide registers for cylinder and sector but only a single nibble for the head, all of which got recycled for LBA, with a then unthinkable 128 gig limit!
Rumor has it (from Hale Landis, a pretty good source) that ATA/ATAPI-6 will allocate 48 bits (somehow?) for LBA numbers. It's gonna be pretty damn hard to fit those 48 bit LBA start and length numbers into the 32 bit wide slots of legacy MBR partition table.
Thus continues the saga of hard drive size barriers and the long PC legacy of kludge upon kludge, 512 megs (CHS bios call), 2 gig (fat16), 8 gigs (kludged CHS bios call), numerous bios bugs along the way... just when it seems like all that's behind us, >128 gig IDE drives will be upon us soon since you can already get SCSI larger than that, and someday two terrabytes hard limit within the partition table will also become an issue. Hopefully by then we'll all have fiber-to-the-home, so it'll be easier to fill up a couple terrabytes with mp3z, p0rn, DivXs, etc.
In an ideal world, one might expect that the PC industry could collectively plan ahead and make a smooth migration to new standardized formats long before the legacy ones how signs of obsolescence... Oh well.
PJRC: Electronic Projects, 8051 Microcontroller Tools
Maybe I'm just a little dense, but I have no idea why this is "from the another-attempt-to-stifle-competition dept." If you can get the specification, how are they attempting to be incompatible?
Look here. More than 4 partitions without hacks like extended partitions..... Personally, I'm looking forward to this becoming mainstream.
--
--
We have fought the AC's, and they have won.
13. Can the 64-bit version of Windows Whistler read, write, and boot from GPT disks?
Yes.
14. Can the 64-bit version of Windows Whistler read, write, and boot from MBR disks?
The 64-bit version of Windows Whistler can read and write MBR disks, but cannot boot from MBR disks.
15. Can the 32-bit version of Windows Whistler read, write, and boot from GPT disks?
No. The 32-bit version will see only the Protective MBR. The EE partition will not be mounted or otherwise exposed to application software.
16. Can the 32-bit version of Windows Whistler read, write, and boot from MBR disks?
Yes.
17. Can Windows 2000, Windows NT 4, or Windows 95/98 read, write, and boot from GPT?
No. Again, legacy software will see only the Protective MBR.
18. What about mixing and matching GPT and MBR disks on the same system?
GPT and MBR disks can be mixed only on 64-bit systems, and the following restrictions apply:
* The Windows Whistler loader and the boot partition must reside on a GPT disk. Other hard disks can be either MBR or GPT.
* Both MBR and GPT disks can be present in a single dynamic disk group. Volume sets can span both MBR and GPT disks, However, the MBR cylinder alignment restriction might cause some difficulties mirroring or striping MBR and GPT disks.
I'm not punishing myself by giving MS more of my money in exchange for the headache of reinstalling another Windows, reinstalling apps, etc. It's crap. I'll do whatever I can to prevent new versions of Windows from entering my workplace (approx 1000 pcs, approx 12 knowledgeable users). There really is NO need for it. I say we all band together and say, Win9x is fine for Gomer. Office97 is fine for Gomer. Only order pcs that work with win9x, order them without the latest stinky version of Windows, ghost them all identically, and leave Gomer alone. Maybe Gomer will learn how to use what he/she has if we leave it alone long enough?
"Would it kill you to put down the toilet seat?" -- Maya Angelou
Claus
Even so, I know I have to be ready for the other OS screwing up MBR, so I've got a boot disk ready. This is a perfectly working option for trying out Linux, albeit slower to boot. But it may take time to convince a typical Windows user that floppies still exist and are actively used by many of us... which reminds me, there's always Loadlin.
--
Escher was the first MC and Giger invented the HR department.
I'll bash Microsoft as much as the next luser, but once again this is FUD spread by Slashdot's inability to read the stories it's linking from.
There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
with the move towards having EFI as the intermediate between the BIOS and the OS, the GPT is a step to get rid of the one more legacy element in the PC. The MBR is considered a legacy agent, mainly by the fact to get to it, you have to use software interrupts. These are trying to be phased out. Now, with the GPT, you can install as many OSs as you would like, they each just need an entry in the table (which is very easy to do) and a file on the harddrive that actually tells it where to go.
Unfortuatly, that's not exactly true. When I was consulting to the IT department of a steelworking company, we would order Win98 machines (as 98 was the only OS our supplier would ship) and then whipe and install Win95. The reason behind it was the version of CA-OpenIngres we were using, along with a custom written app, wouldn't run correctly on Win98. Everything was going fine until some third party bitch was asked to audit our office site license. Apparently, according to the auditors, we were violating license agreement by transfering Win98 licenses to Win95 installations.
The resulting payout the company was forced to do for licenses cost me and a few other contractors our jobs. The budget could no longer afford us. Several other projects got scrapped. Big pain in the arse.
So, according to licenses, you are forced to upgrade. Thought I'd give you a heads up of potential problems you could run into if this is a buisness you are installing the old software on.
--Demonspawn
Kant speel, don't kare.
If you had real computing problems to worry about such as soviet missle trajectory prediction, then you wouldn't even think about booting into multiple operating systems.
-vax computer, vi, lynx. 'nuf said
I could see a company selling a premade version of this.
"Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
boot floppy.
this is getting old and so are you
blog
When I was younger, I thought putting a few OS's on the same hard drive should/would be a snap. But little did I know the enemy MBR was silently laughing in my face! My eyes were opened when I tried to get LILO to boot NT, win9x, OS/2 and Linux all on the same HD. I learned about MBR alright! I then added more HD's and learned about Master, secondary Master, slave and more MBR issues! I learned about hardrive jumpers and why I would need tweasers to install a hard drive! Ever since, I have been trying to figure out who invented the whole MBR thing and SHOOT THEM. The next thing that has to go is master/slave nonsense on HD's.
I miss the Karma Whores.
Well, first off, I don't think anyone capable of running today's Linux distros will have much problem jumpering a drive to slave, dropping it in and plugging in two cables. I can't see it taking very long for someone to get a multiboot manager working, even if it requires a patch to XP's boot sequence.
MBR has been a thorn in the side of OS development ever since people wanted to create more than 4 partitions, and has also chronically stood in the way of hard drives' exponential capacity growth. It has been begging to be replaced for years, and I'm glad someone is finally doing it.
The FAQ says that only the 64-bits versions of Whistler will require GPT to boot from, 32-bits versions of Whistler will use the normal MBR.
(Qoute)
15. Can the 32-bit version of Windows Whistler read, write, and boot from GPT disks?
No. The 32-bit version will see only the Protective MBR. The EE partition will not be mounted or otherwise exposed to application software.
(/Qoute)
--
Two witches watched two watches.
Which witch watched which watch?
On the one hand, we have graduate students from various universities, industrial and academic researchers, and industrial software developers. On the other hand, we have some nebulous people deep inside the bowels of some defense, medical, and aerospace contractors that have been writing "life-critical systems" for decades. The kind of people who managed to blow up the Osprey and the Ariane in software and punch holes into patients with radiation machines. They use and create low-volume, proprietary software with little or no peer review. A review of the kinds of blunders these professionals make shows that there are quite a few bad apples in the bunch and just leaves people scratching their heads. So, no, it isn't obvious to me that the "amateur" open source code is any worse in principle than the professional code.
Off-the-shelf Linux itself is probably not a good choice for "life-critical systems" because it wasn't developed with that goal in mind. I'd still trust it more than some of the supposedly "reliable" proprietary systems being sold. If you wanted to make Linux truly reliable, you would probably start by throwing out 90% of the drivers and other extensions and carry out a lot more additional code review and testing. In userland, you'd also limit yourself to a small set of very strictly tested tools.
More generally, however, given the same goals and the same resources for testing and development, I'd trust the open source community considerably more to develop reliable and safety critical systems than a bunch of proprietary professionals: I think the open source community has better people in it, and the open source process brings more resources to bear on code review and bug fixing.
Intel's Extensible Firmware Interface specification contains the spec for GPT. All systems incorporating EFI (currently, this is only IA-64 systems) need use GPT, for others it is optional.
I wrote the Linux IA-64 kernel GPT support, and it has been included in the IA-64 kernel port since September 2000. It allows use of either MBR-style or GPT-style partition records per disk. With minor tweaking, it could be used on Linux IA-32, but it is not currently.
Boot loaders such as LILO remain unaffected. LILO takes a file system location (i.e. /boot/vmlinuz), from which it asks the kernel for the physical location of that file on the disk (i.e. where in /dev/sda is the file?). The file location is entirely independent of the partitioning strategy, thus LILO works with both MBR-style and GPT-style partitioning. Linux IA-64 uses its own boot loader (elilo.efi) which again does not need to be aware of the partitioning strategy of a given disk.
Partitioning tools such as fdisk and GNU Parted need to become GPT-aware. I have created a patch for GNU Parted and have made it available to the IA-64 distributions. It could use a bit of cleanup, but is quite functional. I don't believe that anyone has written GPT support into fdisk, and would encourage anyone who wishes to please do so.
I've also written a new Linux IA-64 application "efibootmgr" which manages the EFI Boot Manager options (as defined in the EFI spec above). This tool is both MBR and GPT-aware, and allows for booting your OS off of any disk/partition in your system provided the partition contains a FAT-12,-16, or -32 file system. Additional work will go into EFI in the future to add ext2 file system awareness to avoid even this restriction.
All of these topics have been discussed on the Linux IA-64 developer mailing list. If you care to join the Linux IA-64 developer community, please see www.linuxia64.org.