4 replies to this topic

[nativar]

Hello ,

 

Sorry for my very bad english ...

 

I have compiled a 32 bits version of win8pese with succes .

Now i've started the same but with 64 bits source of Windows 8 .

All seems ok but the 32 bits programs are place in Program Files instead of Program Files (x86).

Is there any way to force Programs Files to be converted in Programs Files (x86) when use 64 bits source ?

 

Thanks a lot for any help for solve this issue .

[pscEx]

Allow me to first ask the standard question:

Why do you want to build a x64 PE?

• Usable memory bigger 2 gigabyte? (I do not know any project where this is needed)
• Because you do not have a x86 source?
• Why else ???

To your question itself:

**** In WinBuilder generally:

Where the added applications are placed, is defined by the WinBuilder app script.

Inside the script there must be a "procedure how to copy me into the PE build". This procedure should copy to either "Program Files" or "Program Files (x86)", depending on the build environment.

 

BTW: In the app script there should be also a decision where to write into registry. There should be some entry with "WOW6432Node" or perhaps something similar.

 

**** When the project or the app script neglects the WinBuilder standard rules, I cannot help here.

 

Peter

[nativar]

Hello ,

Thanks for answer .

 

I need 64 bits build to boot native UEFI (without disable secure boot)  and use optimised 64 bits programs.My build work but i some of my 32 bits programs don't like be in programs instead of Programs files (X86) .

 

Can you explain me  how to copy programs in programs files (X86 ) in a script ?

 

Thanks

[sbaeder]

if you have an example script you could name, we might be able to help.  Look at the log file, and it should have at the top a listing of the variables being used, and you should be able to see the different variables

 

The issue is that if the script and project is not designed for an X64 build (and does things to know if it is a 32 bit program, and so should be used instead inside the script), then it won;t have the logic to put it in the X86 directory.

 

Still not sure (as peter mentioned) why you need to boot an X64 based OS...Doing a temp disable of the secure boot shouldn't be an issue, and not sure why you need optimized programs???   Remember a PE environment is not the same as the full OS, and shouldn't be used instead of a full OS...

 

But as mentioned above, *IF* the project supports it - AND the script supports it, then it's possible to encode it to go to the right placed based on logic to determine the type of source...

 

Scott

[Agent47]

 

 

Still not sure (as peter mentioned) why you need to boot an X64 based OS...Doing a temp disable of the secure boot shouldn't be an issue, and not sure why you need optimized programs???

 

Disabling "SecureBoot" is not easy on all systems. I have seen some HP Probook models which needs several steps to be performed to disable "SecureBoot" and enable "Legacy Mode". Also you won't be able to do automatic startup repair  from the PE if "Legacy mode" is enabled. As a bonus you can perform additional system repair functions like offline SFC etc from a 64 bit PE ( Almost all laptops came with Windows 8 x64 pre-installed and a x64 PE will be ideal for repair and recovery ).

 

So the real question is when you can build a x64 Win8PE easily which allows native UEFI boot, offline system restore , offline SFC , Startup repair , refresh and recovery , why do you need a 32 bit Win8PE ?.

Edited by Agent47, 15 March 2014 - 05:37 AM.