Jotnar

As to booting the entire ISO I have no clue as I don't use BCDW, but...as seperate components using ISOLinux here's how you would go about it: For the Linux version of the tools you'll need the two files BZIMAGE and INITRD.GZ (get them from the ISO). Drop them into a folder somewhere on your DVD and have ISOLinux.cfg lines like so (Modify to suit your paths): label PRKL kernel /PARAGON/RKP4/LINUX/BZIMAGE append initrd=/PARAGON/RKP4/LINUX/initrd.gz splash=silent quiet root=/dev/ram0 eng_ver vga=0x314 For the DOS version of the tools you need to edit the AUTOEXEC.BAT and menu.bat files inside DOS.IMG. You'll also need to put the DOS files from the ISO and DOS.IMG (you can zip the image if you have a newer verison of ISOLinux) somewhere on your DVD. The ISOLinux lines should look like this (Modify to suit your paths): label PRKD kernel memdisk append initrd=/PARAGON/RKP4/DOS/DOS.zip Cheers

Could you use a boot loader like XOSL? They can hide partitions and you can default it to boot into one or the other (and password protect it, I believe). You wouldn't be able to swap which is the boot partition in Windows though. Cheers

You could always just use the ISOLinux cdshell module w/ the kernel.dat and ramdisk.dat. if ($lastKey == key[??]); then isolinux /DD9/kernel.dat rw vga=788 acpi=off initrd=/DD9/ramdisk.dat /s ramdisk_size=20480 quiet kernel.dat and ramdisk.dat should be in your program folder. eg. C:\Program Files\Acronis\Disk Director\. Cheers

Some of the linux live cds (Knoppix?) have remote desktop clients that support the RDP protocol. You could always use one of those. Cheers

You need the file specific to the version of Server 2003 you're trying to install. For Standard I believe its WIN51IS. Cheers

Here is an updated list: Cheers LABELS.TXT

The guy on these forums with the nick likuidkewl seems pretty knowledgeable about WinPE, so you might try PMing him. I think WSH and VBS are build options with WinPE, but i'm not sure about IPX. As for other places to try, you can also check out the Windows PE board at the CD Forum. Cheers

Its a minor update from 9.0.2.1000. Cheers

If you want to use ISOLinux (probably needs some syntax modification for ISOLinux under CDShell?), you can also load Disk Director this way: kernel /DD9/kernel.dat append rw vga=788 acpi=off initrd=/DD9/ramdisk.dat /s ramdisk_size=20480 quiet kernel.dat and ramdisk.dat should be in your program folder. eg. C:\Program Files\Acronis\Disk Director\. Cheers

From my experience so far: 1. Ghost32 and PQIDeploy in WinPE image faster than in DOS over the network, but slower disk to disk. 2. Ghost 9 (rebranded Drive Image 7 that can work with .gho files) doesn't seem to go any faster than PQIDeploy and it requires 256mb of RAM to boot up so you can restore. 3. Symantec is basically replacing their consumer version of Ghost 2003 with Ghost 9 (rebranded Drive Image 7 that can work with .gho files). But I think they still include Ghost 2003 in the package? I'd stick with PQIDeploy (DOS version) for disk to disk and PQIDeploy (Win32 version) for network to disk. Hell, I think they even have a Linux version on the DeployCenter Library disc don't they? Cheers

Do the images your creating under WinPE have a higher compression level than what you used before? If you can track down ImageCenter32, its a WinPE GUI for PQIDeploy.exe that was created by a guy at PowerQuest and can help you make sure your command line is ok. I know that for me imaging over the network was slower in DOS because of the network drivers. Seems to go faster in WinPE but maybe thats just me. Cheers

I know alot of people will be happy to have this functionality inside PE. Thanks!

I think they said you'll be able to get email that way until about March, at which time it will be for paying customers only. Cheers

Here's my setup (using ISOLinux to multiboot). Have a folder in the root called NTOPC. Have another folder in NTOPC called CD030426 (or CD040818 depending on which version you're using). Extract all files from the Passwordchanger ISO there. If you open up the ISOLinux.cfg file in that folder you'll see a part that says "kernel" and a part that says append. Here's the section from original isolinux.cfg: kernel vmlinuz append initrd=initrd.gz vga=1 ramdisk_size=128000 root=/dev/fd0 All you have to do if you're multibooting w/ ISOLinux is to change the paths the reflect the new location of the files. The entry in my main ISOLinux.cfg file looks like this: label 12 kernel /ntopc/cd030426/vmlinuz append initrd=/ntopc/cd030426/initrd.gz vga=1 ramdisk_size=128000 root=/dev/fd0 All I did is tell it where to find vmlinuz and initrd.gz in relation to the root of the disc. Cheers

The best reason to use some form of PE is that it has reliable NTFS read/write access and you can do registry editing. I consider Linux NTFS writing to be not too reliable yet. If you want you can even multiboot PE with a smaller linux distro like SLAX and have the best of both worlds. Cheers

They just seem to prefer to use leaked/illegal software. Good thing Microsoft doesn't seem to care too much given that you can download the cdimage executable from this site. MKISOFS is a nice, free and non stolen alternative, made even more attractive now that there is a version that has integrated duplicate file linking. There was really no excuse to not use MKISOFS instead of cdimage outside of the lack of an advanced gui (now remedied by your work, Bobby). And for those who question the legality of cdimage, "For Microsoft Internal Use Only" pretty much spells it out. I say post updates anyway and ignore the whiners. Cheers

...is now freeware (for private, non-commercial use). This is the DOS NTFS loader that McAfee Cleanboot uses. See Here. Direct download Here. Cheers

Finally figured out what was killing the installshield install (and also msi based installs as it turns out). It was a few lines I had in my security templates. Apparently I didn't catch the part in the "Whats changed in SP2" readme that said the RPC service doesn't run under the SYSTEM account anymore. The have it running under the NETWORK SERVICE account (this is a good thing as it limits access). My templates would set security on the RPC service (rpcss) and unfortunately NETWORK SERVICE was not one that was allowed to access it (nor can I seem to add it either). I removed those lines and BAM! I can install stuff again. Something I did in the User Rights section was also making my network connections not show up (they existed, you just couldn't see/change them in the network properties, yet you could change them in netsh) but I seemed to have fixed that by removing some seemingly generic entries from the template. Maybe others will find this info useful. Cheers

What are you using as a bootloader? Cheers

You needed an additional two registry entries for Ad-Aware SE to work. See my post at the bottom of the page here: http://www.msfn.org/board/index.php?showtopic=24393 Cheers

You could also you pskill or something similar and kill the command window. Cheers

I've run 2K/XP setup before in BartPE, so thats not the problem. Try it with just the /s and /syspart . Cheers

You could use something like this: select disk 0 clean create partition primary size=20480 select partition 1 active assign letter=c Cheers

Maybe use diskpart to assign it a drive letter? That might work. Cheers

Most boot loaders (ISOLinux, cdshell, etc...) seem to use the cd-rom boot sector from a windows CD to kick off the boot process. With SP2 that works fine, there is no difference. You hex-edit the same files as before and everything works. If BCDW loads the setupldr.bin directly I guess it could have some issues. I don't see why it wouldn't use the normal setup sequence of xpboot.bin -> setupldr.bin -> txtsetup.sif to start. Cheers