Tripredacus

I have removed your duplicate topics.

It looks like the XMP spec is for overclocking your memory. It may be that this chipset cannot handle the additional voltage used by dual channel (think 3 sticks vs 6 sticks of RAM) when overclocking? Since this is fairly recent for Intel, it may become possible in future chipset revisions. It also looks like the ability to use XMP memory is highly dependent on the CPU you are using. Some say you need an i7 Extreme series CPU.

The official instructions have you copy the winpe.wim into sources\boot.wim. So you have the "original" and untouched winpe.wim, and your production boot.wim. You could just skip that whole step and use the winpe.wim. It doesn't need to be called boot.wim either, you could call it bananas.wim and WDS isn't going to care. Basically, if you did the xcopy winpe.wim sources\boot.wim, AND you mounted and modified the boot.wim, then you need to add that one.

Microsoft recently released a tool called Express Deployment Tool that I checked out the other day. After going through everything, it turned out to not be of any use to me, since I already have a custom setup that does everything it does. Concerning a "Cloud WDS" is a subject I'm interested in, however I already have a working Cloud WDS model and can't particularly share it because it would be a "business secret." However, this tool from Microsoft may give you some ideas or potentially be just what you are looking for. The link above does go to MS OEM but it doesn't require you to be logged in to get there. It does say it requires the OPK Tools, but I am wondering if maybe it will work with the WAIK as well. At worst, you may need to have a standard Partner account to log in.

I believe that bootfix.bin is the file that has that prompt. However, I find lots of info on how to put it on a CD/ISO but not a USB key. You can try just putting it there and see if it prompts you.

You can use Windows Backup that is in the Control Panel. I can't find the appropriate documentation on TechNet at the moment, but you can use Windows Backup to create an image of your OS. Then in case of failure, after running recovery or reinstalling the OS, you can load the System Image Backup back onto your system. What is Windows RE?

Oh really? I ran Windowblinds on a 133MHz Windows 98 PC with Transparencies enabled, and yes it was a little too slow. It would lock up after 10 minutes of moving windows around when transparencies were turned on. However my current Win98 PC has no problems running Windowblinds (it has the same HDD in it that was originally in the 133MHz) as can be seen here: Anyways, we have a forum about modifying Windows appearance, so I'll move this topic there.

The only problem I've encountered so far is that some websites that "say" they need to install Active-X controls, the prompt doesn't actually show up. I only use IE for MS websites, and have only seen this on the Update Catalog website.

Lynyrd Skynyrd - Sweet Home Alabama

Its because of bootfix which removes the "press any key to boot" message. Also BIOS differences can cause different results. Some BIOS will see a USB key as a removable drive, or as a fixed disk. And you can change these settings. Some BIOS have a "boot USB devices first" option as well. So you could see there would be a lot of differences in people's personal experience. Here is one example: On an Intel desktop board, it will see the USB key as a hard drive, and will boot off the USB key if the hard drive is blank. After the install is done on the USB key and reboots, it will boot off the hard drive because the Intel BIOS prioritizes HDD to UFD for booting. If you still needed to boot off the UFD, you can change the Fixed Disk boot order in the BIOS or use the One-Time Boot Menu. I currently do new installs using a DVD and a USB key that has an answer file on it.

This is one of the greatest misconceptions about that screen shown during Safe Mode boot. It doesn't FAIL at MUP.SYS, but whatever loads AFTER mup.sys. If you do a Step-By-Step boot instead, after you choose Y to mup.sys, it will prompt for something else. I would start looking there. Also you can try to turn bootlogging on.

There looks to be drivers for this model, so that's a good start! Win7 Drivers

I believe that MED-V is more on the lines of XP Mode for the Enterprise, which lets you run XP in a VM on Win7, but managed on a Server. There is a comparison here: http://technet.microsoft.com/en-us/magazine/ff458350.aspx

Firstly, Hirens is warez and you shouldn't be using it. Second, disconnect all external drives, including any USB keys or whatnot. Also make sure you optical drive does not have a disc in it. The blinking cursor usually means that it is having trouble using the bootloader. Have you tried safe mode?

I found some more things you might try: http://support.microsoft.com/kb/958055 You could possibly rename or delete this: c:\9b53f85f7ed01fc7c7830c4f\amd64\mp_ambits.msi A leftover file there, Also in C:\windows\temp and %userprofile%\Local Settings\Temp, etc could have read-only files left over from other installers/programs that this update needs to overwrite and cannot. This used to be a big problem back in the Win9x days but it never hurts to empty out those folders. Some other leads: http://social.answers.microsoft.com/Forums/en-US/msestart/thread/908fad3e-f9fc-4d8a-be83-ae7d3bc48db5 These logs aren't very helpful. Neither of the MSIb8c2x logs really have any info you need to worry about. The only "error" in there is the APPCOMPAT message, but I am fairly certain that can be ignored. The CBS log doesn't seem to have any related info either. You can see the MSI logs are recording at 12:02 but the latest time on CBS is 11:59. If this wasn't done already: http://support.microsoft.com/kb/223300 we want to enable the switch /l*vx I've had problems determining why MSSE wouldn't install in the old version, and the cause of the problem was that MSSE installs with a Wrapper and isn't very friendly or responsive to troubleshooting. My problem was that MSSE wouldn't install on an x64 system that had Office installed on it. It was never resolved.

That is annoying when old links stop working. And especially when those sites aren't on the wayback machine. You'll definately be able to find some help here, as we have a large number of day-to-day Win98 users.

This XML looks like it is only used with sysprep and not install. If you are using it for sysprep you can pretty much name it anything.

You know, I remember working my first tech job and encountered this issue quite often. At that time I had actually gone about and debugged Win98 and determined a clear-cut solution to msgsrv32 errors and problems. Unfortunately, that was so long ago that I forgot it (and how to debug Win9x) But just seeing that file name for the first time in 10 years warmed by heart!

Unfortunately, as previously mentioned, we cannot help you if you are using an pirated version of Windows.

We have this topic already: And this one too:

There doesn't seem to be anything inherently wrong with that update. I see that the newest versions of FEP (Forefront) require this update, and since MSSE is the "public" version of FEP, I can see it requiring it also. However, your log file says that one of the updates it has downloaded is corrupted and cannot be opened. Therefore it can't install it either. I am not able to determine (by that log) which update that specifically is, or where it may be located.

The log file you posted was created DURING sysprep, before the image was captured. There should be another log file (in a different folder than where you found the one you posted) that will detail the system's actions during the second phase of sysprep that is done after deployment.

Well you want to try the Live CD first. If there is a problem with the hardware (ie the system not announcing the audio hardware to the OS) then a reinstall is going to be a waste of time! Definately check those BIOS settings and try a Live CD before doing a reload. What we can see here is that you likely have a hardware problem rather than an OS problem.

Ah too hasty, I'll merge these.