Jump to content
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. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About necrosis

  1. Wow nice! I have something to mess with this weekend. Meh. Can not install both versions on the same machine. Guess im going to have to build a machine in VM to test this out.
  2. I finally got back to this post. Yes. It does seam that the bootmgr.exe in WinPE 2.1 is the reason for the options showing up as "Ramdisk Options". Using the exact same BCD file and the bootmgr.exe from WinPE 2.0 the labels show up properly. GO MICROSOFT! Going to read over the BCD creator doc's again to see if they changed a command or something.
  3. I have a fully working unattended install of all drivers for the dell computers where I work... except the sound drivers. The Sigmatel and Realtek drivers do not want to install via INF method/OEMDriversPath. Is there any way around this other than making a VBScript file that checks the model number and runs a silent install of the setup.exe?
  4. I am trying to make a external USB HDD boot two WinPE images. A x86 and a x64 image. Everything is working fine except for the image label's when booting. Here is the script I use to make the BCD file. @ECHO OFF Rem Creates BCD (boot configuration data) for x86 and x64 Windows PE 2.1 images set BCD-File="%HOMEDRIVE%%HOMEPATH%\Desktop\BCD" IF EXIST %BCD-File% del %BCD-File% Bcdedit /createstore %BCD-File% Bcdedit /store %BCD-File% /create {ramdiskoptions} /d "Ramdisk Options" Bcdedit /store %BCD-File% /set {ramdiskoptions} ramdisksdidevice boot Bcdedit /store %BCD-File% /set {ramdiskoptions
  5. Answered my own question. Net installs the $OEM$ folder has to go IN the i386 folder. Now to get the bastard to bind to the domain on install.
  6. Was SP3 slipstreamed into the install?
  7. I have a working install setup using WinPE to install WinXP Pro. I want to add drivers to the install for NIC and what not. I specified the OemPnPDriversPath setting, put the $OEM$ folder on the same level as i386, ect, ect. but when I do the install it does not pull in the drivers. Because I am doing a unattended net install instead of a unattended CD install does this folder have to go in a different place? Do I need to specify a different option to inject the drivers? HALP!
  8. When I PXE boot WinPE the bootmgr.exe file has to be in the root of the TFTP server to load correctly. My problem is when I go to setup another option to boot x64 do I have to load a x64 version of the bootmgr.exe? Or will this program work for both versions? If not, how to I get it so that the startup process looks in the /boot folder (or whatever I happen to call the folder) for bootmgr.exe? Also another side question: Does the TEXT HELP option for PXELINUX menus even work in PXELINUX? Or only ISOLINUX or SYSLINUX? I have the LABEL set up like below and it does not display the extra "help" b
  9. Please tell me where they are then. I searched for nvidia and ive gone through every one and they had nothing close to the problem im having.
  10. 1) Nvidia Video Drivers- I cant seam to get the OS to isntall the current Nvidia Video Drivers during the install. Everything else installs with no problems even the Nvidia Chipset Drivers (NIC, Mem conteoler, IDE, SATA). All it seams it will install is the default ones that come with WinXP. 2) Selecting Partition- When i start the install with no winnt.sif file the installer lets me select the partition to install then it asks me how i want to format the drive (FAT32, NTFS, FAT32 Quick, NTFS Quick). When i set the parmater to not auto partition and turn off the option to not format and instal
  • Create New...