Hi,


I got the case where a computer's Windows dir wasn't C:\WINDOWS and realized that I couldn't change the target_root variable either through SetTargetRoot, ERDRoot or the "set" command on my customized UBCD4Win 2.6 and I need it for some of the programs I added like ERD Commander.

So I tested it with the plain vanilla BartPE and the last UBCD4Win 3.12 and it didn't work either, even removing the hard written target_root definition in the registry, so ultimately the solution I found was to use TheTruth PE Shell Swapper (which was often used in those illegal "super winpe" cd's back in the old days ) which is the only way that changed the variable succesfully.

Well it's a good solution for me as I can change the resolution at boot time (which I would usually not do) and I even realized I can close the shell, which gets me back to shell swapper, and then eject the cd before rebooting, usually I would eject the cd before rebooting and BartPE shell would crash

But still can't help wonder where and when that stopped working because I have been able to select the windows installation dir with previous versions of BartPE...


Jon

I'm not sure if this is what you are talking about or not but here it is anyway...

Using the Recovery Console for XP as mentioned in this page http://support.microsoft.com/?kbid=314058

Type the following command

systemroot

at the command prompt and see if that resolves the issue


NOTE... this isn't for use in UBCD4Win or other PE enviroments. Its used to set the SystemRoot folder assignment in the Windows that you are logged into while in the Recovery Console.. ie if you are logged into C:\Windows then that will set it as the systemroot folder for that installation.

No, I'm talking about the %target_root% system variable which is used under a pe environment to indicate where your hard drive windows installation is for progams that need to makes changes to it (for example change the mass storage driver with FixHDC), read information from it (see the registry or the event logs with ERD Commander) or stuff like that.

Do you change Traget_Root within nu2menu?
This updates nu2menu environment. This includes later opened applications.

Previous opened applications are not updated.

No, I tried it with either SetTargetRoot, ERDRoot (2 applications) and the "set" command in a console window, maybe not the 3 of them in all 3 different environments, I don't remember exactly.

Started manually even before loading shell (through PE Shell Swapper) or by autorun for SetTargetRoot

@paranone
Remember each application use a unique environment (e.g. "set" command in a console window).
You may change enviornment of running application.
Environment changes goes to child application

Parent application dosnt't get environment changes.

Try default UBCD4Win. Use nu2menu options to change TargetRoot.

I guess it explains why it works with PE Shell Swapper.
What do you mean by nu2menu options, where is it?

Right where the Fix_IDE and Fix_HDC menu options are... under the Registry tools menu

You really need to update to the lattest version.
I changed all of that stuff within the systemcore as of 3.x and most of your questions are outdated because of a pre 3.x version.

Most of your customasations should move over eaisly, but you will notice a different menu structure and a lot of reduntant plugins were superseeded by the systemcore.

Set_Target root does work, so does the option within nu2menu. BTW: Which "SetTargetRoot" are you using? Paragliders automated version works very well, but we are still using a fixed key the can be located in the environment plugin if you want a different starting path hard-coded into the registry.

Ok, I got it now, I guess SetTargetRoot and ERDRoot stopped working when I changed nu2menu for ShellPE as they can't update the nu2menu environment variable (from SetTargetRoot help: "If it is found then nu2menumsg will be run to call @SetEnvVar(TARGET_ROOT,...)@Reload", I just realized that).

And as I didn't know how the environment variables worked I didn't do the tests right, for example I would leave the same console window open to check for the changing of the variable and that doesn't work as you explained.


By the way I did update my build to UBCD4Win 3.12 now as I wanted some of the benefits (like Windows Explorer and IE) but I use ShellPE instead of nu2menu/geoshell so there are differences which I have to be careful about when I update the core plugins (RunOnceEx->Autorun, nu2menu icons, etc.).


Thanks all for your explanations .


Jon