Re: Dual Boot, Grub, FC3-WinXpSP2, 2 drives. No go.

From: Jonathan Berry (berryja_at_gmail.com)
Date: 03/02/05

  • Next message: AragonX: "Re: Credit Card authorization from FC3" 
    Date: Wed, 2 Mar 2005 10:20:09 -0600
To: For users of Fedora Core releases <fedora-list@redhat.com>

    On Tue, 01 Mar 2005 10:54:52 -0500, Nat Gross
    <natgross.rentalsystems@verizon.net> wrote:
    > Robert Locke wrote:
    > >On Mon, 2005-02-28 at 17:55 -0500, Nat Gross wrote:
    > ><snip>
    > >>I thought so, too. But I just mounted both (vfat and ntfs) partitions
    > >>under FC3, and there is no boot.ini file. At this point I am certain
    > >>that for some reason (maybe due to an earlier install of Windows)
    > >>Windows kept the boot.ini on C, hda, and used that to boot from E.
    [snip]
    > >>
    > >So to speak. GRUB is passing control to the NTLDR and BOOT.INI files.
    > >Remember that they are hidden/system files usually, so depending on how
    > >you tried to locate them might be why you did not see them (probably a
    > >pipe dream)???
    > >
    >
    > I used the 'search for files' applet and turned on the hidden files option.
    [snip]
    > >--Rob
    >
    > Thanks again.
    > -nat
     
    Hidden files in Linux are different from in Windows. Windows has a
    file attribute that makes a file hidden. In Linux, a file with a
    filename beginning with a dot "." is hidden. What you need to do is
    to just mount your windows partitions and then list the contents of
    each partition. For instance, if you mount your NTFS parition on
    /mnt/windows/E (this is not a required place, just an example), then
    open a terminal and type the command:
    ls /mnt/windows/E
    If you see ntldr and boot.ini listed in the output, everything is
    fine. You don't need to search for them as they are necessarily in
    the root of the partition (this is, they will not be in a folder).
    Similarly, do the same with your vfat partition, just in case. If you
    do not find it in either place, then you do have a problem and you
    will need to restore these somehow. Probably with the recovery
    console and FIXBOOT as already suggested.

    Jonathan 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: AragonX: "Re: Credit Card authorization from FC3"

    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)