Re: Installing Linux on Windows dual boot machine

From: imotgm (imotgm_REM_at_invalid-yahoo.com)
Date: 04/15/05

  • Next message: A. Ben Hmeda: "Re: Debian or Ubuntu??" 
    Date: Fri, 15 Apr 2005 04:32:53 GMT

    On Thu, 14 Apr 2005 21:05:45 -0400, xModem wrote:

    >>If the dual boot Windows installation is the typical Windows installation,
    >>this will leave XP unbootable, as the NTLDR and boot.ini are installed on
    >>the active C:\ partition, and must be so.
    >
    > Ouch.
    > Is there a way around this?

    There's always a way around. The trick is to proceed with caution, get all
    the information, and know what to expect at each step, and why.

    Don't listen to anyone telling you that any linux distro will take care of
    what you're trying to do automatically; they won't.

    Did you check your partition table? I don't see it posted. That's the
    starting point. Post it exactly as you see it. 

    -- 
imotgm
  • Next message: A. Ben Hmeda: "Re: Debian or Ubuntu??"

    Relevant Pages

    • Re: hibernation file location
      ... If a disk controller driver was copied to system partition (where NTLDR, BOOT.INI, and NTDETECT.COM reside), and renamed as NTBOOTDD.SYS, then NTLDR would be able to read a kernel and drivers from the boot partition on a drive connected to that controller, even if the controller didn't have a BIOS. ... IIRC the NTBOOTDD.SYS driver is only loaded if the the ARC path in the boot.ini file uses the SCSI or SIGNATURE format when specifying the system drive. ... This actually makes sense because the hiberfile contains all of the boot driver stacks and there would be no need to load the NTBOOTDD.SYS driver when resuming from hibernation. ...
      (microsoft.public.development.device.drivers)
    • Re: hibernation file location
      ... If a disk controller driver was copied to the system partition (where NTLDR, BOOT.INI, and NTDETECT.COM reside), and renamed as NTBOOTDD.SYS, then NTLDR would be able to read a kernel and drivers from the boot partition on a drive connected to that controller, even if the controller didn't have a BIOS. ... Thinking about the generalities of the BOOT.INI file, specifying a number of controllers and drives and partitions, I'm still trying to figure out how NTLDR could load drivers for all of those controllers when all of the drivers had to be given the same filename NTBOOTDD.SYS. ...
      (microsoft.public.development.device.drivers)
    • Re: hibernation file location
      ... If a disk controller driver was copied to system partition (where NTLDR, ... actually makes sense because the hiberfile contains all of the boot driver ...
      (microsoft.public.development.device.drivers)
    • Re: Recover my XPe image
      ... Even though I vote for the bootsector.DOS loaded by ntldr solution (the code is definitely really simple and just a few INT 13 ... there are many solutions as Slobodan mentioned. ... In one of "high level" approaches where I did not have a full control of the hardware (could not change partition layout), ... > This code would use int 13 for reading from second partition and writing to first partition. ...
      (microsoft.public.windowsxp.embedded)
    • Re: Bootfiles suddenly missing (NTLDR,...); CONVERT dont work
      ... This message is included in Partition boot record and not in MBR. ... ntldr is always read from original partition since ewf_ntldr is the first program that start using overlay data for loading other ... in some cases it's impossible to restore a EWF-level (how to do if NTLDR ...
      (microsoft.public.windowsxp.embedded)