[Download] UAC-Free iReboot BETA

Status
Not open for further replies.
On my triple boot it only keeps the "Reboot on selection" in memory - at least I think that's the case.
 
CG, we're obviously tuned to slightly different wavelengths here.
What I interpreted bernie's request to be was
"semi-permanently change the boot menu to default to the currently booted system, until another iteration of iR requests a different system, at which point the boot menu is changed to default to that system. (not just temporarily for the one boot, but semi-permanently again)"
i.e. iR becomes a dynamic "default boot" editor as well as a booter.
Am I right in thinking that build 9 changes the boot menu to whatever you last selected in iR, which is not necessarily the booted system ?
For example, if Bernie uses XP's iR to boot Vista, then Vista's iR to boot XP, then in XP does WUD which reboots, which system will he get ?
The way I interpret your description of build 9, he'll get Vista because that's what was last flagged in XP's iR, when what he wants is to get XP.
This is all conjecture and speculation on my part, because I'm not using iR for the moment so I can't test it to see for myself, and is also based on what I think Bernie meant in his original post.
I await correction from either of you if my assumptions are incorrect.
For the record, I like what I think Bernie was suggesting too. That was the jist of my previous post that you couldn't fathom.

I guess we're not on different wavelengths after all :smile:
As of build 9, iReboot will tell the bootloader to boot into the OS you're currently in. So in your example above, it'll boot to XP actually. (and does with build 9).

Is this what you want? Or are you suggesting different behavior?

On my triple boot it only keeps the "Reboot on selection" in memory - at least I think that's the case.

That's correct.
 
That is what I want, but I'm still confused, by your post #76 now !
 
I'm also confused by it - nvm that anymore...

So does Build 9 do exactly what you want? Or should I revert the default behavior per my first response on the matter?
 
Booting the currently running system by default would be my choice, but I agreed with your doubt about changing the MS default behaviour, so I think that it should be a conscious choice of the user, a positively selected option to change the MS natural behaviour, rather than what iR does by default.

My only other question was whether, if you're adding an install or runtime option for this purpose, whether you could, in the same place, put an option to suppress the currently booted system in the iR list.

You obviously wouldn't exercise it, because you use iR as a complete substitute for the start button options, but I have keyboard buttons for those, so I'd only ever use iR to go straight to the non-booted system.

This is all academic at present of course, but I'm thinking ahead to when you add HnS support to version 2.0
 
Guys, you lost me about 8 million versions ago. Which one do I need that has the Windows default behaviour?
By that I mean doesn't override whatever I have setup as the default boot system in EasyBCD.
 
The latest :smile:

The second-to-last one changed that, but installing the very latest should revert all the default behavior :smile:
 
You are a gentleman and a scholar CG, no sooner mentioned than implemented !
(Can't wait to be able to use it. It's much more galling to have to wait around for the boot menu, once you've got used to the joys of iR, and are deprived of them)
 
You're welcome :smile:

I don't know if you've seen it yet, but this is what iReboot.exe.config looks like:
Code:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <userSettings>
        <iReboot.Properties.Settings>
            <setting name="AutoReboot" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="SetDefaultOnStartup" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="ShowCurrentOS" serializeAs="String">
                <value>True</value>
            </setting>
        </iReboot.Properties.Settings>
    </userSettings>
</configuration>

The first value is set (and displayed) from within iReboot as the value of "Reboot on Selection" so that it's remembered between iReboot sessions. The other two are manually set, and indicate the behavior of setting the current OS as default on iReboot startup and whether or not the current OS should appear in the list, respectively.

Peter, I'm not going to say "hopefully this is the last build" again, since it seems every time I do, another great feature is proposed. But we'll see :wink:
 
Thanks........I think....LOL What's the betting that I'll wish I'd stuck with this version (9)?
 
I just installed 10 so we'll see. I'd prefer to control which boots next myself, so this one should be fine.
 
CG I just tried to install it in my XP # 2 and got an error saying it wouldn't start, although the icon did appear for a moment in the taskbar. I did all the usual things - uninstalled the old one completely first. This is a new occurrence and seems to be exclusive to version 1.1.0.10.
irebooterror001.jpg



Addendum:


Got the same in the other XP and after a second reboot too.....:frowning:
irebooterror002.jpg
 
Last edited:
Can you go to C:\Windows\Assembly and tell me if there is an entry for "BcdLibrary" there?
If so, can you right-click it and select "Uninstall?"
 
Ok, have done. I'll stay signed in to C: for a while to see what you suggest. I did try to be lazy and uninstall it from Vista and got "access denied"...of course.
Ireboot still throws up the error if I try to start it. Strange, I wonder why it doesn't like my XP?

I'd post the full error report if I knew where to find it.


Addendum:


I have a couple of errands I must do down the street - bank machine and the butcher's shop (only open a couple of hours on Sundays) so will be back in an hour or even less.


Addendum:


OK, I've uninstalled v10 and installed the publicly available 1.0.0.12619 version in both XP's and now I have no errors.


Addendum:


If it's any help CG here are two of the associated errors from XP's Event Viewer. The first one is the "bytes" view and the second one earlier one) the "words" view.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 13/04/2008
Time: 2:26:07 PM
User: N/A
Computer: R2D2
Description:
EventType clr20r3, P1 ireboot.exe, P2 1.1.0.10, P3 4800cab8, P4 mscorlib, P5 2.0.0.0, P6 471ebc5b, P7 dc, P8 5, P9 a4dh5wwiwww1yjtmp0c0kv4zwcalu4in, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 69 00 72 00 65 00 .i.r.e.
0018: 62 00 6f 00 6f 00 74 00 b.o.o.t.
0020: 2e 00 65 00 78 00 65 00 ..e.x.e.
0028: 2c 00 20 00 31 00 2e 00 ,. .1...
0030: 31 00 2e 00 30 00 2e 00 1...0...
0038: 31 00 30 00 2c 00 20 00 1.0.,. .
0040: 34 00 38 00 30 00 30 00 4.8.0.0.
0048: 63 00 61 00 62 00 38 00 c.a.b.8.
0050: 2c 00 20 00 6d 00 73 00 ,. .m.s.
0058: 63 00 6f 00 72 00 6c 00 c.o.r.l.
0060: 69 00 62 00 2c 00 20 00 i.b.,. .
0068: 32 00 2e 00 30 00 2e 00 2...0...
0070: 30 00 2e 00 30 00 2c 00 0...0.,.
0078: 20 00 34 00 37 00 31 00 .4.7.1.
0080: 65 00 62 00 63 00 35 00 e.b.c.5.
0088: 62 00 2c 00 20 00 64 00 b.,. .d.
0090: 63 00 2c 00 20 00 35 00 c.,. .5.
0098: 2c 00 20 00 61 00 34 00 ,. .a.4.
00a0: 64 00 68 00 35 00 77 00 d.h.5.w.
00a8: 77 00 69 00 77 00 77 00 w.i.w.w.
00b0: 77 00 31 00 79 00 6a 00 w.1.y.j.
00b8: 74 00 6d 00 70 00 30 00 t.m.p.0.
00c0: 63 00 30 00 6b 00 76 00 c.0.k.v.
00c8: 34 00 7a 00 77 00 63 00 4.z.w.c.
00d0: 61 00 6c 00 75 00 34 00 a.l.u.4.
00d8: 69 00 6e 00 20 00 4e 00 i.n. .N.
00e0: 49 00 4c 00 0d 00 0a 00 I.L.....

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 13/04/2008
Time: 7:30:08 AM
User: N/A
Computer: R2D2
Description:
EventType clr20r3, P1 ireboot.exe, P2 1.1.0.10, P3 4800cab8, P4 mscorlib, P5 2.0.0.0, P6 471ebc5b, P7 dc, P8 5, P9 a4dh5wwiwww1yjtmp0c0kv4zwcalu4in, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 006c0063 00320072 00720030 002c0033
0010: 00690020 00650072 006f0062 0074006f
0020: 0065002e 00650078 0020002c 002e0031
0030: 002e0031 002e0030 00300031 0020002c
0040: 00380034 00300030 00610063 00380062
0050: 0020002c 0073006d 006f0063 006c0072
0060: 00620069 0020002c 002e0032 002e0030
0070: 002e0030 002c0030 00340020 00310037
0080: 00620065 00350063 002c0062 00640020
0090: 002c0063 00350020 0020002c 00340061
00a0: 00680064 00770035 00690077 00770077
00b0: 00310077 006a0079 006d0074 00300070
00c0: 00300063 0076006b 007a0034 00630077
00d0: 006c0061 00340075 006e0069 004e0020
00e0: 004c0049 000a000d
 
Last edited:
To be honest, none of that tells me anything - it's saying that there's an error that happened in a .NET application without specifying which or where.

However, I have a shrewd guess as to what's causing this - let me try some things and upload a new build.
 
Status
Not open for further replies.
Back
Top