Typically, what I've done, is made the 2K partition NTFS, so that Win98 can't see it, and then I've just made the other partitions invisible to 2K. Even if 2K labels a drive wrong, for example, it makes the drive you want as C: into the D: drive, you can still change it. Go to computer management, and give the disk a new label. You'll need to make D: into X: then make C: into D: and finally X: into C:. It's not hard, and it doesn't carry over into other OSes. Drive letters are not used by 2K. They are occasionally used by sloppy applications, but they really aren't needed, so changing them is not a problem.
In the above example, booting to Win98, the C: vs D: drive assignment will not have changed. So it is entirely possible to have 1 HDD running 98, and 1 HDD running 2K, and in each OS, the %systemroot% is on the C: drive. The letters come after the system has booted, and they are pulled from the registry. Changing them is easy and doesn't affect the OS (or related components). It will probably screw up low end applications that were instaled before you made the change. Programming C: is easier than %systemroot%. BTW, that variable may well be wrong. It'll be close, but it might be %SystemRoot%, or %System_Root% or something. I don't program enough to remember these things. Basically, each OS will see it's own lettering scheme, and they will not cross over into different OSes. Even if they are on the same box. The real question is, if you're rebuilding a machine, why are you putting a legacy OS onto it. (He asks, before pressing reply in Outlook Express...) Kev. ----- Original Message ----- From: "Dave Lee" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 20, 2002 11:16 PM Subject: Re: (clug-talk) XP, Win2k Advanced Server and Linux > > Kevin Anderson wrote: > > Windows isn't stuck with them anymore. They're supported mount points since > > Win2K. > > > > I suppose you sort of still need a C: drive, but that's it. Think of C: as > > / > > true, still if you install multiple OS's, the windows installer might > decide to be smart and label some other partition as c:, as was noted > previously, and I dont know how to fix this, anybody?. seems the wxp > installer will even call a pre-existing linux partition c: which is not a > good thing. > > Dave > > >
