Jump to content

imalone

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About imalone

imalone's Achievements

0

Reputation

  1. Well thanks for your time, guess it looks like I might have to redesign the whole setup and use WinPE, thanks again!
  2. 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.
  3. 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
  4. 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.
  5. 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!
  6. 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.
×
×
  • Create New...