[NYTAIceman]

Hi,

i'm very interested about the solution to stage a 64bit Server with a 32bit PE Session.

The solution from TonyPE with a compiled .exe seems to be a possible way, but i do like to have the source code, before i stage my servers with this tool.

I've try to contact TonyPE but he does not answer me.

Has anybody the sourcecode or the batchfiles (Before he has compiled as a native app)?

Thank you very much!

Greets

[killerb255]

Just make an x64 version of WinPE 2.0 and install from it.

Follow one of the tutorials within the forums, but use the AMD64 folders instead of the x86 folders.

Also, if the OS won't boot after initial setup, then check this article out:

http://support.microsoft.com/kb/931760

You don't have to call Microsoft for the patch. Just edit your PE registry according to the article before using DISKPART to create your partitions.

[NYTAIceman]

Hi killerbi255,

I'm sorry but you have not read my text... I need a solutions to stage a windows 64bit Version with a Windows PE 32bit Version.
I can't work with a PE 64bit because the code of my other applications isn't 64bit ready.

Windows PE 64 has no WOW64 on board, therefore I can't start my own applications.


Ok, again:
Has anybody the sourcecode of ManualWindowsSetup.exe or the batch files?

Thanks again.

Greets, Iceman

[jaclaz]

NYTAIceman, on Dec 14 2007, 11:04 AM, said:

Hi killerbi255,

I'm sorry but you have not read my text... I need a solutions to stage a windows 64bit Version with a Windows PE 32bit Version.
I can't work with a PE 64bit because the code of my other applications isn't 64bit ready.

Windows PE 64 has no WOW64 on board, therefore I can't start my own applications.


Ok, again:
Has anybody the sourcecode of ManualWindowsSetup.exe or the batch files?

Thanks again.

Greets, Iceman

Version 1 is here (not really "hidden" ) :
http://home.woh.rr.com/pombo/tools/
http://home.woh.rr.c...ndowsSetup1.zip

Besides being compiled, version 2.0 coorected bugs of version 1.0, so, without TonyPE's support, you might need to directly correct them in the .wsh, if those bugs affect your particular setup.

jaclaz

This post has been edited by jaclaz: 14 December 2007 - 07:58 AM

[imalone]

Hey all, I know this is a very old post but I was wondering if anyone still has these files that TonyPE has mentioned, or whether anyone knows of anyway to initiate a 64bit Windows 2003 unattended build using BartPE.

[cdob]

@imalone

Compare:
How to install an x64-based version of Windows Server 2003 by using an x86-based Windows Preinstallation Environment
http://support.micro....com/kb/925279/

[imalone]

cdob, you are a genious! Thanks so much for pointing me in the right direction, I will give this a go and hopefully will work the way I hope. that way I wont have to scrap an entire automated build structure and start from scratch. once again Thanks!

[imalone]

So seeing cdob was a genius to solve my last 64 bit issue, heres yet another:

Currently I am expanding on a automated O/S deployment tool inherited by another group at my company where the startup means to deploy is by using BartPE. I know this is a 32 bit preinstall and maybe a bit outdated but it's simple and easy to modify and in making long stories shirt, it runs quite nicely for what we need. Currently it deploys W2k, W2k3 x86 and x64, and 2k8 x86 with all needed apps and updates through specialized scripts. So now here is the dilema I am now faced with overcoming, the issue is with 2008 x64. I am able to start the setup and it will copy down and start the setup of all the needed files, but the issue is when it does it's reboot, it will reboot and display the following error:

\boot\bcd 0xc000000f

I know this probibly has to do with the fact that it was initaited from a 32bit preinstall and the boot records were set for 32bit and not the 64bit its trying to boot from. I have tried using MBRFIX but to no avail. I have also tried fixing it based on booting from the original DVD and doing the recovery option to automatically fix it. This does work but only for 1 reboot and the message is displayed again. Besides using the repair disk is not an option when doing the unattended build.

Any suggestions at this point would be greatly appreciated. I really don't want to abandon our current BartPE setup as everything else is running nicely.

[Jazkal]

what command line did you use for the win2k8 x64 install?

[imalone]

Hey Jazkal,

I called up the following command via batch script:

z:\w2k8aiosp1\distribution\setup.exe /installfrom:z:w2k8aiosp1\distribution\sources\install.wim /unattended:z:\answerfiles\win2k8\2008std_64b.xml

I should mention that this command is based on me merging the 2 seperate disks (x86 and x64) together into one install.wim

Previuosly I called it up the same way I did with 2003 by the seperate O/S folders such as this:

z:\w2k8std32sp1\setup.exe /installfrom:z:w2k8std64sp1\sources\install.wim /unattended:z:\answerfiles\win2k8_64\2008std_64b.xml

[Jazkal]

imalone, on Feb 3 2009, 11:30 AM, said:

I should mention that this command is based on me merging the 2 seperate disks (x86 and x64) together into one install.wim

I would try installing x64 from the original install.wim, to verify that this isn't the problem.

This post has been edited by Jazkal: 03 February 2009 - 02:06 PM

[imalone]

Jazkal, on Feb 3 2009, 03:06 PM, said:

imalone, on Feb 3 2009, 11:30 AM, said:

I should mention that this command is based on me merging the 2 seperate disks (x86 and x64) together into one install.wim

I would try installing x64 from the original install.wim, to verify that this isn't the problem.

Originally that was where i was trying to install it, from the original x64 install.wim and got the same \boot\bcd error. Then I tried to merge the 2 install.wim's together as per another post in this sites forum and it appeared that it might of gone a little future this way, but I'm not sure. Either way it still failed with this error, however it doesn't fail at all when it auto builds the x86 version, just the x64. I'm thinking it might have something to do with the way BartPE boots that not compatible with Win 2008 x64. Windows 2008 is suppose to be installable using 32bit for both x86 and x64. Is Microsoft only saying that as long as you use their WinPE product and no other 32bit preinstallation source.

[Jazkal]

Thats why I stopped using BartsPE years ago. I needed to have that official path of support from Microsoft.

I can say that I have our systems working great on WinPE2.1 x86. I can install all versions of Windows Server (2000, 2003, 2008, x86 and x64).

[imalone]

Jazkal, on Feb 3 2009, 04:48 PM, said:

Thats why I stopped using BartsPE years ago. I needed to have that official path of support from Microsoft.

I can say that I have our systems working great on WinPE2.1 x86. I can install all versions of Windows Server (2000, 2003, 2008, x86 and x64).

Well thanks for your time, guess it looks like I might have to redesign the whole setup and use WinPE, thanks again!

[zextra]

imalone, on Feb 3 2009, 10:39 AM, said:

So seeing cdob was a genius to solve my last 64 bit issue, heres yet another:

Currently I am expanding on a automated O/S deployment tool inherited by another group at my company where the startup means to deploy is by using BartPE. I know this is a 32 bit preinstall and maybe a bit outdated but it's simple and easy to modify and in making long stories shirt, it runs quite nicely for what we need. Currently it deploys W2k, W2k3 x86 and x64, and 2k8 x86 with all needed apps and updates through specialized scripts. So now here is the dilema I am now faced with overcoming, the issue is with 2008 x64. I am able to start the setup and it will copy down and start the setup of all the needed files, but the issue is when it does it's reboot, it will reboot and display the following error:

\boot\bcd 0xc000000f

I know this probibly has to do with the fact that it was initaited from a 32bit preinstall and the boot records were set for 32bit and not the 64bit its trying to boot from. I have tried using MBRFIX but to no avail. I have also tried fixing it based on booting from the original DVD and doing the recovery option to automatically fix it. This does work but only for 1 reboot and the message is displayed again. Besides using the repair disk is not an option when doing the unattended build.

Any suggestions at this point would be greatly appreciated. I really don't want to abandon our current BartPE setup as everything else is running nicely.

I have the solution to install windows 2008 x64 (or vista) using 32-bit bartpe. here are the steps, i hope someone finds this useful.

1. Download the attached bcd file. If it is no longer available this is how you generate it:

Install Windows 2008 x64, after installation grab c:\boot\BCD

2. Download Windows 2008 x86 32 bit iso

3. Open Windows 2008 x64 iso and extract install.wim

4. Open Windows 2008 x86 iso and replace the install.wim with the one from the x64 version. This is located in the sources directory of the iso.

5. Save the iso

6. Burn to cd or mount the iso from bartpe.

7. Run setup /noreboot from the root of the iso. You can add an unattend file as well

8. After it finishes phase one. Setup quits but does not restart the computer.

9. Then assuming your windows installation is on C: do this (get bcdedit from 32 bit version of win2k8)

copy BCD (from x64 version) c:\boot\BCD
bcdedit /set {bootmgr} device "partition=C:"
bcdedit /set {default} device "partition=C:"
bcdedit /set {default} osdevice "partition=C:"

10. reboot, windows installation will continue and you should not get a bcd error black screen.

The initial problem stems from the BCD not getting created when installing 64 bit windows 2008 using the 32 bit installer.

Enjoy!

One more thing, if you use an unattended file phase 1 needs to be spicified for x86 architecture and phase 2, after first reboot needs to be specified for amd64 architecture... wierd but works!

-Zex

Attached File(s)

•  BCD64.rar (3.62K)
  Number of downloads: 18

This post has been edited by zextra: 09 June 2009 - 12:42 PM