MagicAndre1981

yes, or use Vista/7 with the PAE Hack of Geoff Chappell (http://www.geoffchappell.com/viewer.htm?doc=notes/windows/license/memory.htm) if you want a x86 Windows.

there is no MSU version. You can run the Win7 Sp1 Installer with /X:C:\Sp1 to extract the CAB to C:\Sp1

from what we know, he is no longer developing the tool. Only the MUI integration (MS renamed the MUI packes internally) doesn't work, but the rest still works for Sp1.

no, the XP Sp0 kernel allows you to use the complete 4GB. In XP Sp2 the PAE kernel is the default kernel, because this PAE kernel is needed for DEP/NX Bit An ugly hack is to convert the Windows Server 2003 to XP: but this is ugly and requires hacking license files and you have issue updating Windows.

You're welcome

it's much better. The ReadyBoot prefetcher is now trained very well (you have good prefetch and hit values, the cache misses are gone) <timing bootDoneViaExplorer="16735" bootDoneViaPostBoot="36835" Your Windows boots in round 17s to the desktop and is booted completely in 27s. most time is needed to start all startup apps (Google, AMD CCC, µtorrent, Samsung Tools, Adobe programs). So reduce the amount of started tools with AutoRuns.

The Sp1 installs the removed packages again. I tested this with Sp1 Beta. The mums are stored in the Windows\Servicing folder. Windows is stable because you don't force a deletion of files like RT7Lite, vLite, 7Customizer Live.

use pkgmgr and give the MUM as Packagename parameter. I use this to completely remove packages like the DVD Maker and the Hyper-V drivers from my Windows 7.

disable the ATA channel 0 and 1 but create a system restore point first, if you can't boot.

ok, make a system restore point and try to disable them in the device manager. After doing this, run the optimization I linked in the first post. If this doesn't speedup run a new trace (this time, let Windows count down the 120s).

ok, first enumaration of all IDE/ATA channels takes some time: - <phase name="bootStart" startTime="23" endTime="4070" duration="4047"> <pnpObject name="PCIIDE\IDEChannel\4+27dec4d+0+1" type="Device" activity="Enum" startTime="329" endTime="2834" duration="2504" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 1" /> <pnpObject name="PCIIDE\IDEChannel\4+27dec4d+0+0" type="Device" activity="Enum" startTime="329" endTime="1342" duration="1013" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 0" /> <pnpObject name="PCIIDE\IDEChannel\4+ba41d32+0+1" type="Device" activity="Enum" startTime="330" endTime="1337" duration="1006" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 1" /> Which IDE devices do you still use? If none, disable the IDE channel i the BIOS. The delay occurs here: Provider Name, Task Name, Opcode Name, Time (s), Microsoft-Windows-Subsys-SMSS, , , , , , , , , , 21, , , , , , , , , , smss:ExecuteImage, , , , , , , , , 13, , , , , , , , , , smss:BootExecuteList, , , , , , , , , 2, , , , , , , , , , , win:Start, 12.900334820, , , , , , , 1, , , , , , , , , , , win:Stop, 40.808546912, , , , , , , 1, , , , , , , , , so, it takes 28 seconds to run the programs from this key: http://technet.microsoft.com/en-us/library/cc963230.aspx The smss.exe is busy writing the C:\Windows\bootstat.dat file. Run chkdsk /r /f on C: and make sure the file is not compressed, set to readonly.

the internal Kernel function MmAddPhysicalMemoryEx blocks the additional RAM on Personal Edition (Home, prof) and lower Server Editions (Web and standard).

marcusj0015 is right, you delete the files and registry settings like vLite, RT7Lite. Use DISM to remove the packages like Hyper-V common drivers.

check this KB article: http://support.microsoft.com/kb/2028504 maybe it gives you some helpful information

post the hardware specs and try to generate the dump.

ok, I've updated the first post and added the links. I was able to install the RSAT update on top of my hack without any issue.

@Rick do you have this InstallWimTweak somewhere?

thanks. I will test how to update my hack to the offical installers.

any news?

do you run it from a command prompt with admin rights?

I never tried it. Make a complete backup first.

don't use such nonsense scripts. generate the XML summary from the ETL and look at the values.

so your boot is not improved? make a full trace: zip the ETL and upload the zip.

you must install the wpt_x64.msi first.

Hi, the link doesn't work. I don't have the permissions to see the files. Put them into your public folder.