[Essexboy]

OK so what we have here is once of the services taking to long to load

The two options open to you now are

1. If all your programmes are functioning correctly leave it in the clean boot state
2. If you want to find out what is causing it we need to play detective

Your choice

[Advertisements]

im gonna go with 1 generally cause i dont think there is much time for me to do number 2 lol

[Fatie32]

im gonna go with 1 generally cause i dont think there is much time for me to do number 2 lol

[Essexboy]

OK I can agree to that

Any other problems apparent ?

[Fatie32]

unless you have any other tips to improve the speed of the system i am aware it is limited by its hardware.

[Essexboy]

We could use xboot to organise your drivers on the disc so that they are in the optimal position, but that will just affect the boot and not the general speed

It will take about 30 minutes to run and you will need to be there to elevate the tool after each boot. Have a look at the instructions for it

Download the SDK web installer from here
Run the installer and select the following:

Leave the location to default


Windows Performance Toolkit


You must reboot on completion of the install

After reboot set aside about 30 minutes when you will not need the computer

When ready start an elevated command prompt :

Go Start > All Programs > Accessories
Right click Command Prompt and select Run as Administrator

Then copy and paste the following command into the black box :

xbootmgr -trace boot -prepSystem -verboseReadyBoot



Now your PC will be restarted 6 times. With a two minute pause before the tool runs after the desktop loads
After the second reboot the MS defragmentation program is running and is placing the files into an optimized layout, so that Windows will boot up faster
The last Reboots are training of readyBoot. After the training is finished, you'll notice a huge improvement in startup.

Readyboot
 

The logical prefetching described above is used when the system has less than 512MB of memory. If the system has 700MB or more then an in-RAM cache is used to further optimize the boot process (its not clear from the book whether or not this ReadyBoot cache completely replaces the logical prefetching approach or just builds on it, my assumption is that both work together).
After each boot the system generates a boot caching plan for the next boot using file trace information from up to the five previous boots which contains details of which files were accessed and where on the disk they were located. These traces are stored as .fx files in the

[Fatie32]

i will run this later today.

[Essexboy]

Due to lack of feedback, this topic has been closed.

If you need this topic reopened, please contact a staff member. This applies only to the original topic starter. Everyone else please begin a New Topic.