benjt

Here is the result of the Net Stop command H:\>net stop msiserver The requested pause or stop is not valid for this service. More help is available by typing NET HELPMSG 2191. H:\> The RunOnce key was a good thought, but unfortunately there is nothing in there.

Yes.

My laptop has been running really slow lately. I ran Process Explorer and I see that msiexec.exe is consuming lots of resources. This has been going on for a week or more. I have tried killing the msiexec.exe process but it keeps coming back. When I installed some software I got a message that msiexec.exe was already installing other software. It appears that some installation in its queue is stuck in a loop. Is there some way to instruct msiexec to end the installation permanently and/or clear its queue?

I'm working on a script that will do something (what is not important for the purposes of this discussion) based on the attached monitor's make and model number. Neither the Windows driver nor WMI provide this information, so I'm using the EDID information. So far so good. I downloaded a pdf from vesa.org that describes the EDID standard format. Using this I'm able to extract lots of information including screen size, supported resolutions, serial number, etc. Still no problem. Among the EDID data I am able to extract there is a "manufacturer ID code" and a "product ID code." Both are 2-byte hexadecimal numbers. For example on my Samsung SyncMaster 320PX the manufacturer ID code is 2D4C and the product ID code is 027B. That brings me to my questions. It seems logical to assume that all Samsung products will have the same manufacturer ID code: 2D4C. Can anyone say for sure if this is true? Similarly can we say that the same model numbers will have the same product ID codes (e.g. a 320PX will always be 027B)? Also if the previous statements are true, then is there a publicly available cross-reference chart which maps these values? Thanks in advance for any help.

I'm changing the mouse pointers by using a script to change registry values. This works well except it requires that the user log out and log in for it to take effect. I would rather not have to do this. Is there a way to instruct Windows to re-examine the mouse settings in the registry and apply the new settings?

You don't need to specify the partition for NTLDR, C:\BOOT.INI determines what partition XP will boot from. I use the command "bcdedit -set {ntldr} device boot". That appears to have fixed my issue. Thanks very much.

Here is my setup. Partition 1 is 10GB with Win PE 2.0 configured to restore a Ghost image to partition 2. It is type 0x27 (hidden/OEM). This is the active partition. Basically it is a homemade restore partition. I used bcdedit to configure a dual-boot configuration according to the M$ walkthroughs as follows: bcdedit -createstore c:\temp\bcd bcdedit -store c:\temp\bcd -create {bootmgr} device boot bcdedit -store c:\temp\bcd -set {bootmgr} device boot bcdedit -store c:\temp\bcd -create /d "WINPE" -application osloader bcdedit -import c:\temp\bcd bcdedit -set <GUID copied from above> osdevice boot bcdedit -set <GUID copied from above> device boot bcdedit -set <GUID copied from above> path \windows\system32\winload.exe bcdedit -set <GUID copied from above> systemroot \windows bcdedit -set <GUID copied from above> winpe yes bcdedit -set <GUID copied from above> detecthal yes bcdedit -displayorder <GUID copied from above> -addlast bcdedit -create {ntldr} /d "Windows XP" bcdedit -set {ntldr} device partition=x: bcdedit -set {ntldr} path \ntldr bcdedit -displayorder {ntldr} -addfirst bcdedit -timeout 10 bcdedit -default {ntldr} Partition 2 is about 76GB with a sysprepped version of Windows XP. I copied ntldr, boot.ini, and ntdetect.com from the XP partition to the root of the WinPE partition. Here's the problem. At first boot it works great. XP boots and mini setup runs as expected. However after mini setup finished and it automatically reboots, XP will not boot again. When you select the option to boot XP you get the following error: Windows failed to start. A recent hardware or software change might be the cause. File: \ntldr Status: 0xC000000E Information: The selected entry could not be loaded because the application is missing or corrupt. Booting into WinPE and running bcdedit reveals that the "device" entry for "Windows Legacy OS Loader" has changed from "partition=X:" to "unknown." Re-issuing the command "bcdedit -set {ntldr} device partition=x:" fixes the issue. However I cannot use a manual process for each system. I must either configure some sort of automated fix (e.g. a script that runs at first boot) or prevent the issue from occurring in the first place. Thanks in advance for any help.

Thanks for the info but unfortunately I need a solution that is completely automated. I won't be doing the installs.

Did you find a solution to this issue? I'm having almost exactly the same problem.