Jotnar

I found out what my problem was a few weeks ago. I was missing two registry entries: [Software.AddReg] 0x1, "Microsoft\Windows\CurrentVersion","ProgramFilesDir","%ProgramFiles%" 0x1, "Microsoft\Windows\CurrentVersion","CommonFilesDir","%ProgramFiles%\Common Files" Cheers

If you had a large enough key you could always partition it so the PE partition was fat and bootable but then you had a storage partition that was NTFS. I think 1GB USB Keys are going for around ~$150 now (SanDisk Cruzer Mini), so I guess it would be feasable. Cheers

Excellent disk! Worked w/ ghost on every machine I have at work. Cheers a reminder for those people who want to put this on a multiboot cd, the XP and ME dos boot disks can't be run by memdisk, but the other option for this boot floppy, a PC-DOS 7 boot disk, works with memdisk quite nicely

That method is totally illegal though as you are modifying one of microsofts binary files. Just FYI. Cheers

Does it still have the 256mb memory requirement? Cheers

I used isolinux/mkisofs so if you're using cdimage, I'd still give it a shot (Putting the files on the root of the cd and trying from there). The restrictions i noticed may be specific to the way mkisofs builds the iso. Let me know if it works if you decide try it. Cheers

So you can't put them all on one image. Cheers

The problem he's having is because the setup executable on the first floppy looks for the labels of the floppies... ie (Disk 1, Disk 2, and Disk 3) and since they have spaces in them there's no way to get around the setup unless use have the CD based setup. Cheers

I spent a few hours and finally slayed the beast that is cleanboot. Here's what I found out while I was trying to get it to work. 1. All files must be on the root of the CD. 2. You can have no file or folder starting with "A" on the root of the CD. 3. You can't have more than 16 folders on the root of the CD. I found that any deviation from the above resulted the program not working right. If the files weren't on the root of the cd, it couldn't find the sys files. If you had a file or folder starting with "A", it would say it couldn't find its license file. If you had more than 16 folders, it would sit at the "Loading..." screen forever. This method works for isolinux and I would guess cdshell too. The floppys won't work because its looking for the disk label on the second floppy. Cheers

*Deleted* - Forgot you were the guy from the other day

I was going to add cleanboot to my WinPE disc a while back, but it became such an issue getting it working that I put it on the back burner for the moment. I used isolinux to chainload loader.bin and had all the files on the root of the cd. The problem I had was that if I had a file or folder on the root of the cd that began with an "A" cleanboot would say it couldn't find its license file. Weird I know, so I renamed the three folders that began with an "A" and got rid of my autorun.inf file and then it would load and work. That said, after I added the I386 folder to the disc, it would get to the loading... screen and just sit there. Cheers

If you have access to or can buy older msdn discs ~1996, its on those as well. Cheers

What kind of drivers do you want to install? Cheers

So you are getting the errors when you are try to install windows from inside of WinPE? Where are you trying to install from (ie another CD-ROM, network...)? Cheers

Is anyone having the error "installshield script runtime could not be installed" with some installshield packages in WinXP w/ SP2? We have some in-house software that is packaged w Installshield and for whatever reason it simply won't install on the XPSP2 machine we have. Fresh install w/ SP2 slipstreamed and only Visual Studio.Net 2003 on the machine. I've read/tried what I could find on the net (unregistering/reregistering msiexec, making sure c:\Windows\Installer is not read-only), but nothing seems to help the issue. I'm going to reinstall the system today to see if it was maybe a glitch, but I figured I'd ask here first and see if anyone had any ideas. Cheers

They changed the way RPC works in SP2. Use the following inf in addition to whatever you already have. ; zmmc_sp2.inf ; MMC add-on for Windows XP SP2 [Version] Signature= "$Windows NT$" [PEBuilder] Name="MMC add-on for Windows XP SP2" Enable=1 [SetupReg.AddReg] 0x1, "ControlSet001\Services\RpcSs","Description","Provides the endpoint mapper and other miscellaneous RPC services." 0x1, "ControlSet001\Services\RpcSs","DisplayName","Remote Procedure Call (RPC)" 0x4, "ControlSet001\Services\RpcSs","ErrorControl", 0x00000001 0x1, "ControlSet001\Services\RpcSs","Group","COM Infrastructure" 0x2, "ControlSet001\Services\RpcSs","ImagePath","%SystemRoot%\system32\svchost -k rpcss" 0x1, "ControlSet001\Services\RpcSs","ObjectName","LocalSystem" 0x4, "ControlSet001\Services\RpcSs","Start", 0x00000002 0x4, "ControlSet001\Services\RpcSs","Type", 0x00000020 0x3, "ControlSet001\Services\RpcSs","FailureActions",\ 00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,00,00,00,\ 00,02,00,00,00,60,EA,00,00 0x7, "ControlSet001\Services\RpcSs","DependOnService","DcomLaunch" 0x2, "ControlSet001\Services\RpcSs\Parameters","ServiceDll","%SystemRoot%\system32\rpcss.dll" 0x3, "ControlSet001\Services\RpcSs\Security","Security",\ 01,00,14,80,a8,00,00,00,b4,00,00,00,14,00,00,00,30,00,00,00,02,\ 00,1C,00,01,00,00,00,02,80,14,00,FF,01,0F,00,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,00,78,00,05,00,00,00,00,00,14,00,8D,00,02,00,01,01,00,00,00,00,00,\ 05,0B,00,00,00,00,00,18,00,FF,01,0F,00,01,02,00,00,00,00,00,05,20,00,00,00,\ 20,02,00,00,00,00,18,00,8D,00,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,\ 02,00,00,00,00,14,00,9D,00,00,00,01,01,00,00,00,00,00,05,04,00,00,00,00,00,\ 18,00,9D,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,21,02,00,00,01,01,00,\ 00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00 0x1, "ControlSet001\Services\RpcSs\Enum","0","Root\LEGACY_RPCSS\0000" 0x4, "ControlSet001\Services\RpcSs\Enum","Count", 0x00000001 0x4, "ControlSet001\Services\RpcSs\Enum","NextInstance", 0x00000001 0x1, "ControlSet001\Services\DcomLaunch","Description","Provides launch functionality for DCOM services." 0x1, "ControlSet001\Services\DcomLaunch","DisplayName","DCOM Server Process Launcher" 0x4, "ControlSet001\Services\DcomLaunch","ErrorControl", 0x00000001 0x1, "ControlSet001\Services\DcomLaunch","Group","COM Infrastructure" 0x2, "ControlSet001\Services\DcomLaunch","ImagePath","%SystemRoot%\system32\svchost -k DcomLaunch" 0x1, "ControlSet001\Services\DcomLaunch","ObjectName","LocalSystem" 0x4, "ControlSet001\Services\DcomLaunch","Start", 0x00000002 0x4, "ControlSet001\Services\DcomLaunch","Type", 0x00000020 0x3, "ControlSet001\Services\DcomLaunch","FailureActions",\ 00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,00,00,00,\ 00,02,00,00,00,60,EA,00,00 0x2, "ControlSet001\Services\DcomLaunch\Parameters","ServiceDll","%SystemRoot%\system32\rpcss.dll" 0x3, "ControlSet001\Services\DcomLaunch\Security","Security",\ 01,00,14,80,b4,00,00,00,c0,00,00,00,14,00,00,00,34,00,00,00,02,\ 00,20,00,01,00,00,00,02,80,18,00,FF,01,0F,00,01,01,00,00,00,00,00,01,00,00,\ 00,00,20,02,00,00,02,00,80,00,05,00,00,00,00,03,18,00,8D,00,02,00,01,01,00,\ 00,00,00,00,01,00,00,00,00,00,00,00,00,00,03,18,00,FF,01,0F,00,01,02,00,00,\ 00,00,00,05,20,00,00,00,20,02,00,00,00,03,18,00,8F,00,02,00,01,02,00,00,00,\ 00,00,05,20,00,00,00,23,02,00,00,00,03,18,00,9D,00,00,00,01,01,00,00,00,00,\ 00,05,04,00,00,00,23,02,00,00,00,03,18,00,9D,00,00,00,01,02,00,00,00,00,00,\ 05,20,00,00,00,21,02,00,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,\ 00,00,00,05,12,00,00,00 0x1, "ControlSet001\Services\DcomLaunch\Enum","0","Root\LEGACY_DCOMLAUNCH\0000" 0x4, "ControlSet001\Services\DcomLaunch\Enum","Count", 0x00000001 0x4, "ControlSet001\Services\DcomLaunch\Enum","NextInstance", 0x00000001 Cheers

Its called Windows Desktop Deployment Resource Kit. Its a nice resource dealing with most of the things we talk about here. The author is Jerry Honeycutt. Peruse it the next time your at the bookstore, I think you'll find there's lots of good stuff in there. Cheers

Are you using PELoader.exe to get around the process limit? Cheers

According to TheTruth, if you kill smss.exe and then winlogon.exe you can get around the 24 hour limit. I don't know about the new version of WinPE. Cheers

Did you move your geoshell directory from the root driectory? It looks like that is where it is looking to load the registry file. As an aside, you should really look into building your own PE disc, its really not that hard (Unless you did and just borrowed the wallpaper from another, less than legal, pe disc). Then you can also be fairly sure whats going wrong when stuff fails, since you added the stuff to it yourself. Cheers

I guess you'd have to add Flash support first and then change the line in the registry (setupreg.hiv ?) that specifies the shell executable (cmd.exe by default). Changing the line in the registry is easy, but I'm not sure how you would go about adding Flash support in WinPE. Cheers

I'd also suggest Avast Home. My friend has it on his computer and it's worked well for him. Def updates are small too for those on dialup. Cheers

Try using /integrate instead of /s Cheers

Here This is my BartPE based build. My WinPE based build doesn't look quite so good...yet. Cheers

Does anyone know why the new ad-aware pops out that warning about not being able to load the reference file? I"ve fiddled with it off an on for a few hours, but I couldn't see anything that would be causing it. I'd ask at the pebuilder forums, but they are down at the moment. Thanks Cheers