ireboot

#1
I have easy bcd working with 2 installs of windows 7 64bit Home Premium and everything is great except when I click on the ireboot icon in the task bar to have it reboot to the other install it just goes to the main boot menu and it does not automaticly star the intall I picked. Does that make sence? Any Ideas would be wonderfull. You have done quality work on Easy BCD and ireboot Thank you for your hard work.
 

mqudsi

Mostly Harmless
Staff member
#3
Hi sd2000,

Please post the contents of EasyBCD's "Detailed Mode" so we can help you debug this issue.
 
#4
Hi computer guru thank you for your response. here it is. this is for my primary drive and I will post for the secondary drive in a few minutes.


Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
{ab1342d1-a1b6-11e0-b1e2-00123f77857a}
bootsequence {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
device partition=C:
path \Windows\system32\winload.exe
description Family
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {3ff1994e-a1b7-11e0-98b7-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {ab1342d1-a1b6-11e0-b1e2-00123f77857a}
device partition=F:
path \Windows\system32\winload.exe
description Games
locale en-US
osdevice partition=F:
systemroot \Windows
resumeobject {820e770a-a1b7-11e0-bce7-806e6f6e6963}

Addendum:

Here is the detailed mode for the secondary drive

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
{ab1342d1-a1b6-11e0-b1e2-00123f77857a}
bootsequence {ab1342d1-a1b6-11e0-b1e2-00123f77857a}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {ab1342d0-a1b6-11e0-b1e2-00123f77857a}
device partition=D:
path \Windows\system32\winload.exe
description Family
locale en-US
osdevice partition=D:
systemroot \Windows
resumeobject {3ff1994e-a1b7-11e0-98b7-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {ab1342d1-a1b6-11e0-b1e2-00123f77857a}
device partition=C:
path \Windows\system32\winload.exe
description Games
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {820e770a-a1b7-11e0-bce7-806e6f6e6963}



Thank You again for your help.
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#5
It's been a very long time since I used iReboot, certainly before W7, so I'm not sure if the W7 unlettered partition might be the cause.
Try assigning a letter to "System Reserved" and see if that helps.

(btw. You didn't need to post BCD details twice. That's the same BCD. The only reason it looks different is the disk letters and they're not part of the BCD. EasyBCD translates the BCD information into human-intelligible locations (disk letters) and they just reflect the way the running OS sees those locations)
 

mqudsi

Mostly Harmless
Staff member
#6
You're doing something odd with the way you dual-boot. You should only have one BCD.
 

Terry60

Knows where his towel is.
Staff member
#8
Don't confuse EasyBCD with the BCD.
You can install EasyBCD anywhere you want.
The BCD is installed by W7, and when you installed the second copy, it added itself to the BCD from the first.
When you look at the BCD from each W7, it's the same BCD you're seeing, as I said before.

Try giving it a letter and see if the behaviour changes. You won't do any harm, and you can always remove the letter later if it does no good.
 
#9
Don't confuse EasyBCD with the BCD.
You can install EasyBCD anywhere you want.
The BCD is installed by W7, and when you installed the second copy, it added itself to the BCD from the first.
When you look at the BCD from each W7, it's the same BCD you're seeing, as I said before.

Try giving it a letter and see if the behaviour changes. You won't do any harm, and you can always remove the letter later if it does no good.

Ok I added the system reserved and it shows up in Ireboot on both installation but it still does not reboot into selected drive and os.
 

Terry60

Knows where his towel is.
Staff member
#10
As I said, it's a long time (years) since I used iReboot, so I may be completely misremembering but isn't there some kind of "do it now" flag as well as the target system down in the notification area ?
Have you got that set ?
iirc, without that, iReboot is just saying which OS you want to be default at the next boot, not actually to go there right away.
 
#11
As I said, it's a long time (years) since I used iReboot, so I may be completely misremembering but isn't there some kind of "do it now" flag as well as the target system down in the notification area ?
Have you got that set ?
iirc, without that, iReboot is just saying which OS you want to be default at the next boot, not actually to go there right away.
yes I have the "reboot on selection" checked
 

mqudsi

Mostly Harmless
Staff member
#12
Terry, I think he's saying that when he reboots it freezes on the menu without a countdown and without automatically booting into the OS he selected in iReboot. Is that correct, sd?

I would try EasyBCD | Backup/Repair | Reset and then readding the entries and trying again.
 
#13
Terry, I think he's saying that when he reboots it freezes on the menu without a countdown and without automatically booting into the OS he selected in iReboot. Is that correct, sd?

I would try EasyBCD | Backup/Repair | Reset and then readding the entries and trying again.

I have Win7 installed on the "c" drive which is a 1 Tb hitachi I have it named "Family" Then I have another drive

with win7 installed on the "f" drive which is a western digital 750Gb I have it named "Games"

I have Easy Bcd installed on each drive as well as Ireboot. I go to Ireboot and right click it says "family" in the

first spot and "Games in the second spot say I am in "Family" then I say I want to play a game then I click on

"Games" (because I have the "reboot on selection checked) it reboots by it's self like it is supposed to but when

it gets to the boot menu it counts down 30 seconds like I set it to and then it boots into "Family". If I am in

"Games" and I click on "Family it goes to the boot menu and counts down 30 seconds and boots in "Family".


So nothing freezes or hangs up and 50% of the the time it works if I am going from "Games" to "Family"
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#14
OK, so try what I told you to.
 

mqudsi

Mostly Harmless
Staff member
#16
You're welcome.

You had a corrupt bootloader, and EasyBCD reset it.
 

mqudsi

Mostly Harmless
Staff member
#18
No problem. Glad you found EasyBCD and iReboot to be helpful!
 

mabo

New Member
#19
Hi there,
I've got 2 OS on my desktop: W7, XP SP3. Before I reinstalled both OS iReboot had worked properly. And now as the systems have have been reinstalled, the iReboot on Win 7 works pretty well while the other one on XP doesn't do the job at all. There's no icon in system tray and when I try to run it from the start menu, "application run (initialization) error (0x0000135).
Any idea how to fix it?
Thanks.
 

mqudsi

Mostly Harmless
Staff member
#20
Need to install .NET 2.0 SP2