Tripredacus

I can't think of a reason why the image would disappear from WDS. Either way, you are using WAIK for Windows 7 on Server 2003? or 2003 R2?

Well the log file you posted, I can't see any real errors in there. One thing you left out that may be important (who knows) is that the XP installed on the notebook is x86, and the Windows 7 image is x64. That is what the log file says anyways. There are two additional log files that the BDD.txt references, maybe it will be of some help. C:\Temp\SMSTSLog\SMSTS.LOG C:\MININT\SMSOSD\OSDLOGS\zticopyUSMT.txt

Welcome to the MSFN!

You know its too bad that SVG animation never really got adopted, as that would definately be my choice to create an image such as that. But like Flash, it does require a plugin, and unlike Flash doesn't work on all browsers. Seemingly HTML5 animation is the next step to do things like this.

AVI and WMV should be easily cut up using Windows Live Movie Maker. I had used it in the past and it seemed pretty simple for that. If you have Windows 7 or Windows Live installed, you should already have that and can check it out. Of course there are probably better ones out there that can do more things than MM can.

It would appear so. Have you looked in both the Sound section and in System Devices too? For reference, there is no Win7 driver for this device. See Creative Support which shows XP and under. So if you do not have your HwID yet, you need to find out what it is. Creative's Vendor ID is VEN_1102, so you can use MSINFO32 (or your favorite driver program) to find the DEV_ number which should be your soundcard. Finding drivers with a HwID is a lot easier than a model number or marketing name.

I may have noticed that slowdown. I've seen them a few times live, but last time they had a strange lineup. Kirinji - Bluff Spirit from Katamari Damacy

KMFDM - Lund end Eled

A driver before mup.sys causes this. Name the drivers before mup.sys. Real issue can be hardware or software. Which external hardware can you use? USB floppy, USB keyboard, USB mouse Usually I would think it would be whatever is after Mup.sys. Doing a step-by-step confirmation boot would allow you to know exactly which item causes the error.

The link had a wayward period at the end. The board formatted the [ URL ] tag to include this period. I simply did a URL tag wrap on the link and removed the period.

Update chipset drivers for your motherboard to start. I've seen this before but I usually just wait. I know that removable drives aren't indexed. I can imagine this is a pain when doing a lot of disc insertions, but my use of ODs have dropped greatly since starting to use UFDs.

Ok now you can do the next step. Unlike ProcMon, I don't think you can export a bunch of info (you can do one at a time) in order for someone else to look at a log file. So when you open Process Explorer (ProcExp) go to View, Show Lower Pane. When this dot is present (you shouldn't have to use the crosshair anymore), click on the Explorer.exe on the top. In the lower pane it is going to show you all the things that Explorer is doing, such as files, regkeys/paths, handles, mutants, etc. You could try to screenshot the lower pane and post a link to that picture. Also, you should do a test and try dropping the crosshair on some other place on your desktop (the wallpaper where no icon is) and see if ProcExp still says Explorer. It may be that ProcExp can't see that dot like Au3info can?

I have seen this sometimes in the update list, but I just right-click and hide updates that I already have but WU seems to want me to get.

We have another topic that adds things to the context menu, not sure if it will help any...

I would gladly pay you Tuesday for a hamburger today.

Yay Graveworm! I did get to see him solo live once, but I wish I had been around to see him in his prime. Even when I saw him, over 10 years ago? I think so since his latest album at the time was Homebrew 2. Anyways he seemed kinda shakey to me at that show, but I do like his music. Except GTR that is. Not a big fan of that experiment, although the album cover is pretty neat. Burning the Masses - Arms Raised, Eyes Closed

I am reading that WinPE 4.0 has better EFI support than 3.0... also that hardware with UEFI 2.3.1 should have the PXE support, but figuring out what spec boards use for UEFI is pretty difficult.

This is true, the password gets removed, however the number does get used. I've tested with both 1, 3 and 10. I wonder where that value is kept in the OS?

From what I can tell so far, the boot time is "decreased" by moving certain functions to after the desktop shows up. So while full system functionality may take the same amount of time as Windows 7, Windows 8 will appear to boot faster because loading Metro/Desktop is earlier in the order of operations.

There is no harm in creating a second account. He would never end up seeing it unless he did a log-off and saw the welcome screen. Having an extra account can come in handy if the primary account becomes corrupted or has a virus in it or whatever.

I think so. Its is an escape character probably because reg.exe is not smart enough to determine the difference between physical (disk) paths and registry paths.

I can't say about the Account problem, as I never enable the built-in Administrator account. So I have no experience with the OS' behaviour during unattended setup with it enabled. For AutoLogon, I'm not sure why you wouldn't want to use the AutoLogon in Unattend. Presuming you get your account creation thing taken care of, you'll see that it shouldn't be a problem. The only issue you'll run into after that is any user accounts created via Unattend will have their password expire after 2-3 months. Running this in your FirstLogonCommands will fix that: wmic useraccount where "name='AccountName'" set PasswordExpires=false It may also be possible to set AutoLogon using WMI, but I did a quick look in UserAccount with the WMI Object Browser but didn't see it there. Another option may be to write to the appropriate registry values.

Well since you are getting an error, we can start there. When you go into the F8 menu (to choose Safe Mode), choose the Disable Automatic Restart on System Failure. Then when you try to go to Safe Mode and you get the BSOD, it won't reboot automatically and you can tell us what it says.