Search results

  1. J

    [EBCD-421] BootGrabber writes boot.ini to wrong partition in certain cases

    It's possible that the Windows partition may itself have it's own BOOTMGR and populated BCD and NST folder so the same situation occurs where multiple BCD's on different system disks are using the same NST folder because Windows is booted using an unmounted system disk. Unlike my original...
  2. J

    [EBCD-421] BootGrabber writes boot.ini to wrong partition in certain cases

    This is the case I am describing here. I have not mentioned any other cases. Browsing to another BCD is not required to encounter this issue. I have not mentioned editing multiple BCDs on the same disk and I don't think that would cause the same issue since they would all use the same...
  3. J

    [EBCD-421] BootGrabber writes boot.ini to wrong partition in certain cases

    I mean when the user is editing the system BCD when the system partition is unmounted, then EasyBCD will use an NST folder on a different disk which may be used by a BCD on that different disk. It is not inconceivable that a user may be using a BCD on an unmounted system disk without even...
  4. J

    [EBCD-421] BootGrabber writes boot.ini to wrong partition in certain cases

    The system partition might contain 1 ebcd.00# file but you could be writing easyldr's to an NST folder that contains 20 easyldr's already because the NST folder could be used by other BCD's. So the numbers would have to be unique in both places - on the system disk for ebcd.00# and in the NST...
  5. J

    [EBCD-421] BootGrabber writes boot.ini to wrong partition in certain cases

    That makes sense and it works. It's just a little confusing that the NST files are on a different volume than the BCD when usually they're on the same disk. For Windows XP entries, EasyBCD does the right thing by putting the boot.ini/ebcd.00# file on the unmounted disk even though \NST\ntldr and...
  6. J

    [EBCD-421] BootGrabber writes boot.ini to wrong partition in certain cases

    There's a thread that describes the EasyBCD Boot Device at What is EasyBCD Boot Device? - The NeoSmart Forums I have a disk that contained Ubuntu (primary active partition). I added 2 primary partitions to install Windows 7 on. I installed Windows 7 to one of the new partitions. When I booted...
  7. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    You can download an ext4 file system driver to view and edit the files on that partition. I don't know if a file system driver will make Bootgrabber get the correct arc path for the partition though. It doesn't matter for you though because that partition doesn't contain Windows XP. Maybe it...
  8. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    You erased the T: drive? This is what I see from the screen shots: Harddisk0\Partition1 -> rdisk(0)partition(1), HarddiskVolume1 -> C: * Harddisk0\Partition2 -> rdisk(0)partition(2), HarddiskVolume2 -> D: Harddisk1\Partition1 -> rdisk(1)partition(1), HarddiskVolume3 -> F...
  9. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    That means one of three things: 1) macycat isn't using the latest version (he said he was using 117) 2) he didn't follow the object manager ArcName symlinks properly and they are actually wrong (screen shots from macycat would prove this wrong) 3) bootgrabber is using the object manager...
  10. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    You're using \NST\ntldr for your first XP entry which uses boot.ini which defaults to all your XP drives instead of just one. Don't you want to use easyldr for that one too like you did for the other XP entry? I guess bootgrabber is using a different source for the arc paths instead of the NT...
  11. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    Oh, I didn't notice the rdisk(1) on disk 0. Good catch. I would check the ArcName directory using WinObj to test whether or not the problem is with EasyBCD or the NT Object Manager/registry. An incorrect arcpath should only be bad for a partition if the partition is Windows XP.
  12. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    You're output for the 2nd drive looks strange because it contains logical partitions which I haven't seen before. I've cleaned it up and rearranged it to make it more readable. I'm not sure why Bootgrabber ordered the partitions the way it did - for example, the first P0 and P3 of the 2nd drive...
  13. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    Did EasyBCD create the \NST\easyldr# files? You'll need those too. They are identical to the \NST\ntldr file except with boot.ini replaced with ebcd.00#. If you execute the two bootgrabber commands and post the output here then we might see a clue. Also verify that you can see the...
  14. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    The drive letters you see in EasyBCD are not used for booting. For booting, the Vista/Windows 7 BOOTMGR uses UIDs in the BCD file and Windows NT/XP NTLDR and EasyLDR# use ArcPaths in the Boot.ini or ebcd.00#. The drive letters in the entries in the View Settings window are just to tell the...
  15. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    1) I was thinking that making the output show what Disk Management does would be good. There are two kinds of un-mounted volumes - unformatted drives that have drive letters and appear in Disk Management and Explorer (e.g. my D: and E: in Parallels), and drives that have an unrecognized file...
  16. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    1) I was thinking you could look at the list of drive letters in the \GLOBAL?? directory. There's a SymbolicLink \DosDevices too. Named Device Objects (Windows Driver Kit) Introduction to MS-DOS Device Names (Windows Driver Kit) Local and Global MS-DOS Device Names (Windows Driver Kit)...
  17. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    All partitions now have correct arcptaths and /bootcfg now shows physical drive number for located active partition. Output from booting Windows XP: C:\Program Files\NeoSmart Technologies\EasyBCD\bin>BootGrabber /tlist Unable to get volume information for...
  18. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    The following is the BootGrabber output from the latest BootGrabber: C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bootgrabber /tlist Unable to get volume information for \\?\Volume{50280910-67dc-11dd-b05c-806d6172696f}\ Unable to get volume information for...
  19. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    I thought the boot block would always be the first 512 bytes of a partition. The code you linked to me before http://www.codeproject.com/KB/system/change_drive_sn.aspx makes that assumption. As for cloned partitions, does your method generate a different serial number for each partition? I...
  20. J

    [FIXED] EasyBCD 2.0.1 writes boot.ini to wrong partition

    All the partitions have unique serial numbers (The EFI partitions are actually FAT). Do they need to be mounted with a file system to get the serial number? Could you read the first block of a partition to get the number like NeoGrub does? Different file systems use different serial numbers...
Top