Tripredacus

Have you looked into Process Explorer? I am not sure if it can create a log file. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Unfortunately, we won't really be of much help in this. To be fair, the term for the concept you are inquiring about is "high-availability"

Unlike their desktop counterparts, notebooks aren't very tolerant to physical abuse.

http://www.theregister.co.uk/2012/11/15/surface_lawsuit/ Get in on this, if you feel you were wronged. For some reason I feel it will be a very small class.

I've done limited sound testing with Linux. Knoppix should be fine presuming it has the drivers.

Try using a startnet.cmd (blank out your winpeshl.ini for this test) and have this at first: wpeinit wpeutil initializenetwork ping 127.0.0.1 -n 16 -w 1000>null net use z: \\7SERVER\images password /user:kdineen I personally do not use winpeshl.ini for any boot images that connect to the internet. Note, the InitializeNetwork command may or may not be required. The ping is in place because not all NICs are immediately usable after being enumerated.

That error you are getting is generally seen when trying to boot an image. Is that when you get the error?

Windows renames the INF file. It is 146 because it is (probably) the 147th INF file that was injected into the WIM. If you use DISM's /GET-DRIVERS on the mounted image, you can view all the injected drivers, which shows the oem# as well as the original filename and other information. Since you have over 30-40 things in there, you'll probably have to > text file to be able to see them all.

What roles are running on this server?

You can also try Fraps, which has a trial version that doesn't expire... but puts a watermark on the top.

You will find any VBScript (HTA) related things in this section, including a recent thread about a progress bar. http://www.msfn.org/board/forum/66-programming-c-delphi-vbvbs-cmdbatch-etc/

Apoptygma Berzerk - Unicorn (Duet Version)

No need, we do not close solved topics here.

What NIC is it and what is the HwID?

Well you have a problem right now (for sure) but I think you're looking at it the wrong way. Right now we do not know if this problem is caused by either hardware or software. The age old "it used to work fine" really doesn't apply in electronics, especially since as they age their individual component tolerances change. The same is true of software, as I expect your Windows isn't running with a RAM Overlay on it, meaning that it too has changed in little ways that are impossible to know exactly. So we already know that Windows 7 does make changes to audio levels by itself in some way, as you have seen with multiple audio sources, and as experienced by me and others. So far none of us has determined a particular method of disabling this other than using another operating system. So in order to fully test your system you will need to try a different source to see if it is a problem with the software or the hardware. If you have another hard drive and can install XP on it with drivers, etc and try to duplicate the sound dropping problem. If you do not have an XP to install, you could probably get away with using the Windows Embedded Standard 2009 Trial. http://www.microsoft.com/windowsembedded/en-us/downloads/windows-embedded-downloads.aspx Or I suppose you could even install Linux and attempt to recreate the behaviour.

Map your drive before running diskpart.

Also, even though apparently it isn't required anymore, I still use: wpeutil initializenetwork In my startnet.cmd. Are you using it as well? You can see an example startnet.cmd I use here.

Well I looked at the specs of that card (on the website) and the latest OS it supports if Windows XP. Not even any Server 2003 support. It seems to me that the current firmware on that card probably doesn't know what an SSD is. Did you check to see if there was a firmware update is available for it?

I'd recommend doing your automation testing with startnet.cmd, and after you get all your commands down, switch it over to winpeshl.ini. The syntax is different for winpeshl.ini. Can you post the contents of it? (obfusicate things like server names, usernames, passwords). Also what version of WinPE are you using and what packages did you add during the build process?

You can do those with the Unattend. Look here for some samples: But not RAID configuration. I'm not sure what you specifically mean by this.

Are you getting an error?

Reminds me of long, long ago when some folks insisted 8088 systems had to be better than the 8086. Its sad in a comedic way, but I looked up 34bit CPU on google...

Welcome to the MSFN!

You can try disable UEFI boot option, or use the boot menu to choose your ODD without the UEFI prefix. With UEFI boot enabled, with the Windows 8 DVD in the drive, you should have 2 ODD options in the boot menu.

OK I think I know what you are experiencing... Tell me if this makes sense... the range of the music is greater than the range of (some piece of) hardware somewhere along the line. http://en.wikipedia.org/wiki/Clipping_%28audio%29 If this is the case, it may only be certain songs or types of songs that cause this problem. I have some MP3s that include both a wide range of sounds that I cannot trust Windows 7 to play accurately. These particular songs experience the clipping problem when I play them from an external device through my car stereo, but do not when played through my franken-stereo I built for myself. I wonder if this problem you experience happens with all songs or just certain ones.