Recommended Posts

K... I've gotta fix what I said in my last post.

Leave the prefetcher as it is! The prefetcher does not access any files listed in the layout.ini file unless they are loaded. It's not a cache, or something that's pre-loaded into memory.

Up to 128 .pf files can exist in the Prefetch folder, and items will automatically be deleted if they are not used.

Windows probably knows how to take care of itself better than you do. The people at Microsoft did take a lot of time to make things work, and it's people who "tweak" that break things - not fix them.

  • 10 months later...

I have noticed that a large amount of People on the net have been saying that this Layout.ini file rebuild no longer works in Vista,,but it does.

Everything is the same as in the earlier info for XP except that now you just have to enter the:

(rundll32.exe advapi32.dll,ProcessIdleTasks ) thread from the "Run command "and not the command prompt in Vista.

BINGO Layout.ini is rebuilt in seconds.

Also it is good to make a copy of the ReadyBoot folder that now resides in the prefetch folder as well, sometimes Vista has a tizzy fit & won't rebuild it straight away, although going by my own experences it does eventually.

  • 5 weeks later...
I have noticed that a large amount of People on the net have been saying that this Layout.ini file rebuild no longer works in Vista,,but it does.

Everything is the same as in the earlier info for XP except that now you just have to enter the:

(rundll32.exe advapi32.dll,ProcessIdleTasks ) thread from the "Run command "and not the command prompt in Vista.

BINGO Layout.ini is rebuilt in seconds.

Also it is good to make a copy of the ReadyBoot folder that now resides in the prefetch folder as well, sometimes Vista has a tizzy fit & won't rebuild it straight away, although going by my own experences it does eventually.

can i edit Layout.ini ?

deleting

[OptimalLayoutFile]

Version=1

C:\WINDOWS\system32\ntoskrnl.exe

C:\WINDOWS\system32\BOOTVID.dll

C:\WINDOWS\system32\KDCOM.dll

C:\WINDOWS\system32\hal.dll

C:\WINDOWS\system32\config\system

C:\WINDOWS\system32\config\software

C:\WINDOWS\System32\c_1252.nls

C:\WINDOWS\System32\c_850.nls

C:\WINDOWS\System32\l_intl.nls

C:\WINDOWS\Fonts\vga850.fon

C:\WINDOWS\system32\drivers\ACPI.sys

C:\WINDOWS\system32\drivers\WMILIB.SYS

C:\WINDOWS\system32\drivers\aswMon2.sys

C:\WINDOWS\system32\drivers\AavmKer4.sys

C:\WINDOWS\system32\drivers\atapi.sys

C:\WINDOWS\system32\drivers\Cdfs.sys

C:\WINDOWS\system32\drivers\disk.sys

C:\WINDOWS\system32\drivers\CLASSPNP.SYS

C:\WINDOWS\system32\drivers\dmio.sys

C:\WINDOWS\system32\drivers\dmload.sys

C:\WINDOWS\system32\drivers\Fastfat.sys

C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\DATA\LOG\

C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\ASHMAISV.EXE

C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\AAVM4H.DLL

C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\AHRESMAI.DLL

C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\DATA\LOG\ASWMAISV.LOG

C:\WINDOWS\SYSTEM32\MSWSOCK.DLL

the entries

C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\DATA\LOG\
C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\ASHMAISV.EXE
C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\AAVM4H.DLL
C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\AHRESMAI.DLL
C:\PROGRAMMI\ALWIL SOFTWARE\AVAST4\DATA\LOG\ASWMAISV.LOG

because i haven't avast , now i use nod32

I just found this with a Google Search. (I should have bookmarked where...darnit.)...

After deleting files out of the prefetch directory you should run the command

Rundll32.exe advapi32.dll,ProcessIdleTasks

So, I went ahead and opened my Prefetch folder and deleted its entire contents, including the Layout.ini file.

While leaving the now empty Prefetch folder open for my view, I typed in the above command to my Run Box.

..I'll be buggered...the Layout.ini file was re-created IMMEDIATELY! No need to even reboot the 3 times as prescribed.

Well, I think we all learned something from this thread.

i did what u said but Layout.ini was 500k and after i deleted it , it appears new of 500K!

why?

i did what u said but Layout.ini was 500k and after i deleted it , it appears new of 500K!

why?

The best thing you could possibly do is go to a shop.

Go to a shop and ask them to sell you a genuine copy of Windows and so you can stop using a hacked version which probably conatins bugs.

(im not causing flame bait, i have proof this guy is using an iligit version of Windows)

The best thing you could possibly do is go to a shop.

Go to a shop and ask them to sell you a genuine copy of Windows and so you can stop using a hacked version which probably conatins bugs.

(im not causing flame bait, i have proof this guy is using an iligit version of Windows)

:)

u are right

today i was where i bought my pc , he sold me a pc with an xp that doesn't work

today i bought a orginal copy of XP PRO for 139,99? and i'm very happ:D:D

this afternoon i will repair my xp

Edited by drugo
After quite a lengthy experimentation process I have discovered what the "Tweak Gurus & PC Geeks" don't tell you in their posts on the subject of cleaning the Prefetch folder.

This guide has not been plagiarized. It is totally compiled by me and was once posted by me at the SoftZone Forums.I decided that I did not wan't to be a member of that comunity because they have more rules than posts so I removed this post and others I had made and canceled my membership.So if you have seen it before that is where it came from.

I hope it can be of assistance to some of you that have cleaned your Prefetch folder because you have been told it will speed XP up. But now "like I did" you find that after you have cleaned the prefetch folder your PC now suffers from slow boot up's and general lack of performance. Here is the real deal about the Prefetch Folder

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

If this has happened to your prefetch folder DON'T WORRY because I will now show you in 5 easy steps how you can rebuild the -> (layout.ini) <- file again.

1): make sure that the task scheduler is enabled.If you are un sure go to-> Start/Contrl Panel/Administrative Tools/ Click on Services/ Then in the list of services make sure the Task Sheduler is enabled & restart the service by clicking on Start. Close the Services Folder & go back to desktop.

2): Then go to START/RUN/ and TYPE IN/->cmd<-(without the arrows) CLICK OK. This will bring up the DOS Command screen.

3):You will need to copy and paste this entry in at the flashing cursor

-> rundll32.exe advapi32.dll,ProcessIdleTasks <-(without the arrows) and press ENTER.

4):Now reboot three times and your Prefetch folder will be rebuilt.(It takes 3 reboots for the prefetch folder to work out what it needs)

5):Then go BACK to ->Start/Contrl Panel/Administrative Tools/ / Services/ Once again find TASK SHEDULER in the list and stop the service and then set it to disabled.This will stop any more entries going into your Prefetch folder.

If you need to leave your task sheduler enabled,(No Drama) you will just have to clean out your Prefetch folder manually from time to time.Just remember not to remove the layout.ini file

You should only clean out files ?other than Windows Start up files? in the Prefetch folder.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

No one bothers to tell you the consequence of deleting the (layout.ini file) in all the tips I have seen about cleaning out the Prefetch folder.

Also if you use one of the many programs that are availabe to clean the prefetch folder you will find that they delete the layout.ini file also.

I have now tried about 50 of these so called Prefetch clean programs and they all disable the Prefetch folder completely and for ever which is a crazy thing to do.The Prefetch is one of the best things about XP.

The truth is that only people who don't know what the Prefetch folder is actually for and don't know how it works say that it is useless.

All I can say is that there must be a lot of people with a verry sluggish XP Windows PC's around,,especially at Boot up.

I just found this with a Google Search. (I should have bookmarked where...darnit.)...

After deleting files out of the prefetch directory you should run the command

Rundll32.exe advapi32.dll,ProcessIdleTasks

So, I went ahead and opened my Prefetch folder and deleted its entire contents, including the Layout.ini file.

While leaving the now empty Prefetch folder open for my view, I typed in the above command to my Run Box.

..I'll be buggered...the Layout.ini file was re-created IMMEDIATELY! No need to even reboot the 3 times as prescribed.

Well, I think we all learned something from this thread.

i have a question

after how much time does windows xp refresh Layout.ini ?

in short after how much time does windows xp change/add new entries in Layout.ini?

  • 6 months later...

Just stumbled in here after realizing my Win Xp system *is not suposed to* take 3.5 minutes to power on and be ready for user input. (That is, all desktop icons displayed)

Every program runs slower than molasses on a wintery day.

Only thing in the last two weeks that has changed has been hollowing out the prefetch folder and the installation of micro$oft's .net framework 2.0

(Wife purchased a photo printer that required installing it)

My question is...Is .net framework to blame for the slowdown?

I have defragged the drive, eliminated unnecessary programs, etc...

I am hoping one of the resident gurus can assist

Just stumbled in here after realizing my Win Xp system *is not suposed to* take 3.5 minutes to power on and be ready for user input. (That is, all desktop icons displayed)

Every program runs slower than molasses on a wintery day.

Only thing in the last two weeks that has changed has been hollowing out the prefetch folder and the installation of micro$oft's .net framework 2.0

(Wife purchased a photo printer that required installing it)

My question is...Is .net framework to blame for the slowdown?

I have defragged the drive, eliminated unnecessary programs, etc...

I am hoping one of the resident gurus can assist

Minister Muffy you are hijacking another OP?s thread, you should start your own one! Oh and welcome to Neowin.:):) Do yourself a favour and go and get yourself up-to-date with the forums do?s and don?ts!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.