Tripredacus

How do these appear in the WinPE you are using for deployment?

Wouldn't it be easier to manage if you only used the Memory Drive to boot the OS, but then use a Ramdisk after Windows loaded? That should solve the write issues such as pagefile, hyberfil, etc.

Try out what the others have mentioned, but if you really want to run a project of your own, you may try either of these places: http://forums.devshed.com/hire-a-programmer-57/ http://forums.devshed.com/project-help-wanted-40/

Indeed!

Go into the BIOS, change the HDD type to IDE. If this is not an option you need to F6 the AHCI driver.

Here is the memory dump instructions again. Also, I fixed the typo in the topic title, seeing the word "svshot" was killing me

The disk numbers are typically assigned to match the enumeration order that the BIOS provides to the WinPE. In almost all cases, Disk 0 is the drive connected to SATA 0 on the motherboard. How are your drives connected? If you want the SSD to be Disk 0, connect it to SATA 0 and then connect the HDD to SATA1 or higher.

Heh interesting... I'll have to keep an eye out for that one. Bruce Springsteen - Secret Garden

It certainly can. Some technologies are already being used for such things but the number one concern that must be taken first is securing whatever your service is.

I have here an Intel DQ67EP board that says: On the side of the box, but I haven't a clue how to test or use it.

Just click the "View and request Hotfix downloads" link at the top-left of that page.

I'd be interested to know what USB controller you have installed. You may not have a USB 2.0 controller there, just a 1.1. Hopefully not a 1.0 tho.

It was possible under Vista (haven't tried 7) to have an image that is sysprepped using /unattend:unattend.xml. You needed the full path, but I liked to put it in Panther, so path to c:\windows\panther\sysprep.xml. Then you mount the image and overwrite the sysprep.xml file, deploy and reboot. Basically, windows only records the filename specified during sysprep. It doesn't actually parse it until the system boots for the first time, so you could replace the file.

The only time this would be an issue is if you take out something that is a pre-requisite for another update that you leave installed. Remember, when you use DISM/Imagex, any time you add or remove something, it does not remove the (replaced) file from the WIM, just the index. That means it can roll back to previous versions of files when you take something out. The only time those old files no longer exist is when you export the WIM out of itself.

You can find most of the silent install methods in the Application Installs section, just where this topic will be going.

Hope you don't just stop there!

Ok that was just weird. I saw a young Eddie Murphy singing, an old dude with a light sabre and Jean Reno on drums! Anza - Tobira wo Akate TV Size:

May be a good idea to zip anyways. I have seen some log files that are huge! Maybe that's why.

The WinRE in vista is in a separate WIM. How do you boot into the Recovery?

For IE, you can download AutoIT and look up RegWrite in the help file.

Full driver package is available here: ftp://ftp.wsisiz.edu.pl/pub/pc/drivers/modem/cobra_win_95-98.exe Individual files (for inspection) are here: http://ftp.slavka.kiev.ua/pub/programs/DRIVERS/MODEM/CONEXANT/56K%20CONEXANT/WIN9X/ I found these by way of searching for the correct INF name (S215DT9.inf) like so: http://www.lmgtfy.com/?q=S215DT9.inf+ftp HOWEVER these will not install in Win7 x64 because these drivers are not only not signed, but they are not even for Windows XP. You can see it is all VXD (the old driver model) and not a CAT file in sight.

This is more of a programming question... You could try automating Devcon, or come up with another idea.