Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About richard

Profile Information

  • OS
    none specified
  1. i used Intel CT Desktop NIC, but this NIC only support PXE by default, you need to flash its rom to support EFI + PXE using bootutil. you can find more info in intel's website
  2. i don't think so. i have set up a RHEL 6.1 server and config UEFI PXE boot, now my client machine could boot from a NIC which support UEFI PXE. My question is how to load windows set up menu like legacy BIOS to load BCD.
  3. hi there, as i know in legacy BIOS, pxelinux.0 would load bootmgr.exe and BCD, and then bootmgr.exe read BCD so that we can select different OS to install. But how to do similar work in UEFI mode? i tried bootx64.efi, but it seems would not auto load bootmgr.efi and BCD as legacy BIOS, anybody could help? thanks in advance!
  4. thanks for reply. i also reviewed the web link in your last reply, and created my own disk configuration file, as following, however, i still met “windows cannot be installed to this disk, the selected disk is of the GPT partition style”. <DiskConfiguration> <Disk> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition> <Order>1</Order> <Size>400</Size> <Type>EFI</Type> </CreatePartition> <CreatePartition> <Order>2</Order> <Size>128</Size> <Type>MSR</Type> </CreatePartition> <CreatePartition> <Order>3</Order> <Size>50000</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition> <Order>4</Order> <Size>50000</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition> <Order>5</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition> <Extend>false</Extend> <Order>1</Order> <PartitionID>1</PartitionID> <Label>System</Label> <Format>FAT32</Format> <Letter>S</Letter> </ModifyPartition> <ModifyPartition> <Extend>false</Extend> <Format>NTFS</Format> <Letter>C</Letter> <Label>SYSTEM</Label> <Order>2</Order> <PartitionID>3</PartitionID> </ModifyPartition> <ModifyPartition> <Extend>false</Extend> <Format>NTFS</Format> <Label>TACCBOOT</Label> <Letter>D</Letter> <Order>3</Order> <PartitionID>4</PartitionID> </ModifyPartition> <ModifyPartition> <Format>NTFS</Format> <Label>TACC_2HD</Label> <Letter>E</Letter> <Order>4</Order> <PartitionID>5</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration>
  5. Hi All, i want to auto clean GPT hard disk after UEFI installation using Autounattend.xml, but system report error "could not format GPT disk", my system is windows 7 sp1 x64? any idea would be appreciated, thanks!
  6. Hi All, after i installed vista sp2 x64 using Autounattend.xml, i found there was not network connection. But the same autounattend.xml. window 7 could get network connection, did vista need special setting for autounattend.xml?
  7. i found a tool named setaclx86.exe in this forum which can do this. Update register would be ok only after system finish installation, but setaclx86.exe could get it done during system installation.
  8. any feedback? i met similar question, the commands in setupcomplete.cmd did not run. even a simple command mkdir c:\11
  9. attached log files for setupcomplete.cmd, but i did not see any execution log in them. setuperr.rar
  10. unattendant, I am pretty much out of ideas. Are you testing on a virtual system? All the information I have ever seen show $OEM$ in all capitals. You show it sometime in caps and sometime in lower case. I would think it would make no difference, but I am surprised often. I should note that after I install W7 (Ultimate x64), my setupcommand.cmd is still present in the Windows\setup\scripts folder. Is your setup\scripts folder there? If not, then I would think it is not getting copied. Enjoy, John. did your commands in setupcomplete.cmd auto run after system boot up? my commands seemed did not run. i just put some test commands such as mkdir c:\11
  11. it's ok using Autounattend.xml in my side, i put it under sources folder Well I am not sure about sources folder, I keep my Autounattend.xml @ root of the DVD and it works fine for me. install OS from Network or local DVD using Autounattend.xml may be different, i have tried to put the file at the root folder, but it didn;t work
  12. the issue why new added files couldn't be found was fixed, when i unmount the install.wim, i used wrong index. But setupcomplete.cmd still did not run, after system boot up, i manually run it, it's ok. The following were my commands in setupcomplete.cmd mkdir c:\1_test_1 c: cd c:\ call c:\autoexec.bat
  13. may i know how you make your setupcomplete.cmd work in install.wim? i put a setupcomplete.cmd in intall,wim, but did not see after system finish installation.
  14. it's ok using Autounattend.xml in my side, i put it under sources folder
  15. i agreed with your idea, but first thing is that setupcomplete.cmd should be in target system. i did not see it after system finish installation. To be more clear, my steps were: 1. unmount install.wim and put setupcomplete.cmd in it and them commit 2. install Windows using Autounattend.xml from PXE, which means launch the whole installation from PXE and auto install system using Autounattend.xml
  • Create New...