Ohhhhh..... nice!
Can I please ask you to give an example of a menu configuration that can be used via PXE boot? I.e. I now have the following for installing Windows 2003 SP2 via an .ISO image from the network:
LABEL w2k3_cd_inst
MENU LABEL ^Windows 2003 Std x86 Install from CD
KERNEL http://192.168.2.1/boot/memdisk
APPEND iso raw
INITRD http://192.168.2.1/boot/w2k3.iso
What I would like to be able to do is to get rid of the .ISO file and instead have the contents of the CD image served via a harddisk image. Why? Well, because I find it to be cumbersome to have to re-create the .ISO file everytime I want to make a small change. It would be much easier to have all setup files in a disk image that I can manipulate via ImDisk instead.
I believe / hope that I have figured out how this can be achieved:
1. nLite a Windows CD to whatever SP and drivers needed
2. Add $OEM$ directory structure and whatnot
3. Copy all this into a pre-made disk image mounted with ImDisk
4. PXE boot a target computer
5. Select a menu with settings for mounting this disk image as the second hard disk AND a small PE or whatever that can start JFX's WinNTSetup v2 (
http://www.msfn.org/...-winntsetup-v2/) as the boot harddisk
6. Start the installation and hope for great results
Is this doable at all or should I settle for the working but clunky .ISO via PXE / HTTP method? Oh, and before I forget:
*a big thank you* for the excellent WinVBlock driver!
Edited by Krokodox, 15 September 2011 - 01:27 PM.