easybcd2.0 build75 don't work well in windows2008sp2

#1
I installed easybcd 2.0 Build 75 to make dual boot( windows2008 ent sp2 and ubuntu 9.10), but when I select "Add/Remove Entries","Linux/BSD",the program "bootgrabber.exe" don't work, it is canceled by windows system.
 

Attachments

mqudsi

Mostly Harmless
Staff member
#2
Thanks for providing the dumps, it usually takes me days of explanation to get my hands on those :smile:

I'll look into it and let you know what I find.
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#3
OK, can you please replace Program Files\NeoSmart Technologies\EasyBCD\bin\BootGrabber.exe with the one attached to this post and let me know if it still crashes?

If so, please attach the crash dumps once more.

I appreciate your patience on this matter thus far.
 

Attachments

#4
Thank you very much!
I installed easybcd2.0 beta build 76. Now it don't crash, but when I add an entry for linux , I select "linux/bsd" and type "grub(legacy)" , it don't show the device list.
when I select type "grub2" and rebooting, I select "neoSmart Linux" , the screen show "Grub rescue", don't load ubuntu9.10.
I installed ubuntu 9.10 in /dev/sda7, /boot under /dev/sda8
after rebooting , the screen show the infomation:
Starting cmain() .... (hd0,0)
[Multiboot-kludge, loadaddr=0x100000, text-and-data = 0x6211, bss=0x0, entry = 0x10027c]
error: unknown filesystem
grub rescue>
 
Last edited:
#5
maybe EasyBCD pointed at the wrong partition (i.e. your root partition, instead of /boot)...
just a possibility.
 

mqudsi

Mostly Harmless
Staff member
#6
H,

Can you please open EasyBCD | Useful Utilities | Power Console
type in
Code:
bootgrabber.exe /list
and copy and paste the output here?

Much appreciated,
 
#7
hi!
Code:
c:\Program Files\NeoSmart Techologies\EasyBCD\bin>bootgrabber.exe /list

BootGrabber utility
Copyright NeoSmart Technologies 2009 <http://neosmart.net/>
 

mqudsi

Mostly Harmless
Staff member
#8
And then it hangs? Or returns to the command prompt?
 

mqudsi

Mostly Harmless
Staff member
#10
Weird. You wouldn't happen to have another Windows Server 2008 machine to test this on, would you?