ooky

XP, SP2. Actually I may have found the answer. It may have something to do with the "RpcSS needs to launch DComLaunch Service first - SP2 only." I found an alternative which seems to be working. http://www.911cd.net/forums//index.php?showtopic=16549 I think it may have something to do with the fact that the PXE boot needs ramdisk.sys from 2003.

Bump

--Bump--

That did not work either. It goes through the same sort of loop. This works perfectly booting BartPE off a cd, just not when booting through PXE.

Hello all! I have a BartPE bootable via PXE and I am attempting to do an unattended install over the network. The install starts then during 'Preparing the Installation' it goes back to 'Collecting Information' and stays there. If I attempt to do a manual install by executing winnt32.exe, the install complains that it is out of memory after the language and accessability settings. It will actually go into an loop of asking the same questions until it just stops and won't go any further. Other functions of the boot image at this point no longer work, such as rebooting, clicking on menus, and task manager. I have been able to boot off of CD and conduct a successful unattended install with the same image as the one used for PXE. I have tried this on systems that have 512 meg of memory up to 4 gig. I have tried this on multiple systems with varying standard hardware. Here is my winnt.sif: [setupData] BootDevice = "ramdisk(0)" BootPath = "\i386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=PEBUILDER.ISO" I have NTLDR (aka ntdetect.exe), startrom.0 and ntdetect.com from Windows 2003 SP1 in the default tftp directory. I appreciate your patience if this has been dealt with before.

I have toyed with this and have heard it is possible, but it did require BartPE (or similarly WinPE). The trick was to replace the ramdrive.sys (or ramdisk.sys) with one from Windows 2003. This creates a ramdrive that the system boots into, thus booting into BartPE, from there you are in a Windows environement where you can initiate an installation. Starting an installation from BartPE is particularly helpful with unattended installs. I never was able to get this working with a USB drive on some systems, so I resorted to (and I am very glad I did) to booting into Bartpe through the network using PXE. I was able to get this working without RIS or any SIF files. It is just a pure PXE environment that uses syslinux (aka pxelinux) for the menus. With syslinux I am able to create menus for selecting floppy and other images to boot into. This can be hosted on a windows system or Linux system, so don't let syslinux scare you away. This is by far the best thing I did. I work in a server and PC systems building environement where having a single copy of any tool on the network makes things easier for our builders. Enough about me, here are some links that you might find helpful: http://www.911cd.net/forums/index.php?showtopic=9685&st=0 http://www.nu2.nu/pebuilder/ Searching msfn or 911cd might also be helpful.

Which BTS script option is recommended for a network install? (options 1,2, or 3?)

Is this even possible? From what I have seen and read on the forums network unattended is slightly different then doing one from the a cd. I also read that BTS Driver pack does not work with network unattended installs. I am using nLite with a few of my own drivers that I have loaded, but I would like the ease and conveniance of using Bashrat's pack. Does someone have a good suggestion on how to do this?