Hi,


I'm quite satisfied with the Lite version. I'm just not sure what to do here. Everything is at default settings and I'm running x86 of Vista Ultimate.


I get a pop-up when I try to fix everything checked (not word for word):


Removing (modifying) C:\Windows\system32\LogFiles\WMI\Readyboot.etl is dangerous? Are you sure?

Yes, No, Cancel


I always hit No until it stops popping up.


What's left are these:


MRU and History Data

Microsoft Windows - Explorer MRUs

Microsoft Windows - Explorer MRUs

Microsoft Windows - Explorer MRUs

Microsoft Windows - Explorer MRUs

Microsoft Windows (logs)

Microsoft Windows (logs)

Microsoft Windows (logs)

Microsoft Windows (logs)

IIS Log Files

IIS Log Files

IIS Log Files

IIS Log Files


Temp Files

C:\Windows\Temp\logishrd\LVPrcInj01.dll


Is it safe to just hit Yes?


Thanks,

bucow

bucow wrote
. . .

Removing (modifying) C:\Windows\system32\LogFiles\WMI\Readyboot.etl is dangerous? Are you sure? . . .

I don't know what the Readyboot.etl file is. I suspect that it is not dangerous, and that the message appears only because of the word "boot."


You could do web searches for Readyboot.etl, and then for just .etl -- maybe you can decide if it's dangerous. Otherwise, you can wait for the developer to look into it. I think he's tied up with the next PT2009 release right now.

bucow wrote
. . . What's left are these:


MRU and History Data

Microsoft Windows - Explorer MRUs

. . .

Microsoft Windows (logs)

. . .

IIS Log Files

. . .

Temp Files

C:\Windows\Temp\logishrd\LVPrcInj01.dll


Is it safe to just hit Yes? . . .

I wonder why you listed some of those things four times?


Anyway, I find it safe to click "Fix" for those items on my PCs. The MRU/History stuff actually can't be fixed, so the program will remove most of those things.


Some of the files (in MRU/History and Temp Files) may be open in other processes, so windows will refuse to delete those. They will show again when you run PTLite. That is normal.


In any case, regarding safety, everything removed is backed up. You can restore individual backups with the Undo tool. The backups do occupy disk space, so after a time you feel comfortable with, you can use the Undo tool to delete any backups you wish.


If you want to examine the detail about the stuff that was backed up (and presumably removed) do this:

  • Click the Undo button--> right click the backup you want to see-->chose Custom restore. The resulting window shows the registry items and files in separate tabs.

Hi tullik,


Thanks for the reply.


I guess I'll wait for jv16.


I listed them multiple times because there were multiple files under the one name. When I right-click and copied the data to clipboard, it copied it times the number of files found.


Readyboot is a Vista thing, I too am not sure what an etl is. I did google but did not do much of searching since I am busy with school (ALMOST DONE!).


Thanks again.

bucow wrote
... I guess I'll wait for jv16.

FYI: he posted elsewhere that he will only do part-time for two months after May 26.

I listed them multiple times because there were multiple files under the one name. When I right-click and copied the data to clipboard, it copied it times the number of files found.

That's sort of a bug (IMO).

Readyboot is a Vista thing, I too am not sure what an etl is. I did google but did not do much of searching since I am busy with school (ALMOST DONE!).

Perhaps it is an "event trace log" (see http://www.filesuffix.com/extension/etl.html ).


Until jv16 advises otherwise, to avoid that pop-up, you could:

  • Either risk removing it by answering "Yes" (there will be a backup).


    or try right click-->Never show again on the Microsoft Windows (logs) line.

Here' what Tweaking Companion for Windows Vista says about ReadyBoot:

Not to be confused with ReadyBoost, ReadyBoot is another feature designed to use memory to optimize the boot process, but ReadyBoot uses normal system RAM to do this rather than an external device. After every bootup, ReadyBoot calculates a caching plan for the next boot and stores part of this information under the \Windows\Prefetch\ReadyBoot folder, and part in the Registry. The end result is that each time you boot up Vista, ReadyBoot can improve boot times through use of this cache. After bootup the memory used for caching is automatically freed up after 90 seconds, or sooner if required. Importantly, ReadyBoot relies on the ReadyBoost Service to function, so you should not disable this service even if you don't use ReadyBoost; it should be left at Automatic - see the Services chapter for details.

And here's a link to Microsoft: http://technet.microsoft.com/en-us/magazine/cc162480.aspx

5 days later

Thanks for that link redseujac, made for some good reading.

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.