ImportListFromBootOptimize() in FileBoolean expressions

[poutnik]

I have tried to modify script to put layout.ini files from windows first,
then the rest. ( The file list contents files from many directories ).

But it seams my modification is ignored, processing all as the only fileselect,
as far as display watching. ( tried to visualize it by gap too, but no gap appeared )

  FileSelect
    ImportListFromBootOptimize() and directoryName("Windows")
    /*EXCLUDE*/
  FileActions
    Defragment()
    FastFill()
  FileEnd

  FileSelect
    ImportListFromBootOptimize() and not(directoryName("Windows"))
    /*EXCLUDE*/
  FileActions
    Defragment()
    FastFill()
  FileEnd

[jeroen]

I think the vast majority of files is in the Windows directory, and only a few are outside. Perhaps you can run MyDefrag with the "-d 3" commandline option, the "c:\Program Files\MyDefrag\MyDefrag.log" file will then show exactly which files were selected.

[poutnik]

No need to debug. I can see the Layout.ini filezone - it is about 3-4 GB big.

Browsing by cross to inspect files reveals
there are (very) many files e.g. from various Program files folders.

[poutnik]

I think the vast majority of files is in the Windows directory, and only a few are outside. Perhaps you can run MyDefrag with the "-d 3" commandline option, the "c:\Program Files\MyDefrag\MyDefrag.log" file will then show exactly which files were selected.

I was playing with custom analyze only script.
It seems about 60% of size of BootOptimizeZone is from Windows folder,
and 40% from other places.

[jimbo]

What seems to be happening, at least on my PC (ymmv) is that the boot optimise list includes everything referenced in the startup menu / registry auto-start as well as just windows.

For me, that includes a sidebar app-launcher, RocketDock, so its exe is added to the boot list, but, more, when that runs, it grabs the icons from every exe that is in its menu structure, which means that all of those are referenced as well. Some of which are quite definitely NOT startup-time programs

However, that is definitely a windows failing. I'm planning to extract the icons and reference them directly to tidy it up, here.

[Lundholm]

I was playing with custom analyze only script.
It seems about 60% of size of BootOptimizeZone is from Windows folder,
and 40% from other places.

Yes, I made the same observation a long time ago. My conclusion then was that the layout.ini file cannot be used for boot optimization. Still is.

[jeroen]

My conclusion then was that the layout.ini file cannot be used for boot optimization. Still is.

You can customize it with something like this:

Code:

  FileSelect
    ImportListFromBootOptimize()
    and FullPath("*\Windows\*")
    /*EXCLUDE*/
  FileActions
    Defragment()
    FastFill()
  FileEnd

[Lundholm]

You can customize it with something like this:

Code:

  FileSelect
    ImportListFromBootOptimize()
    and FullPath("*\Windows\*")
    /*EXCLUDE*/
  FileActions
    Defragment()
    FastFill()
  FileEnd

I'm not sure how to read this; I haven't studied version 4 much. If it's a logical AND, then it's not sufficient. The basic boot files are not in the Windows directory, afaik. But i trust that some sort of correct expression can be made, right? This should be part of the standard package, of course.

By the way, is it possible to download the standard scripts without installing? Any zip builds? I didn't find any, the last time I checked.

[poutnik]

.......I'm not sure how to read this; I haven't studied version 4 much.
If it's a logical AND, then it's not sufficient. The basic boot files are not in the Windows directory, afaik. But i trust that some sort of correct expression can be made, right? ......

I suppose it is in "system32", or in some of its subfolders.
But, anyway, they have windows in path.

[jimbo]

I'm not quite sure what people are trying to achieve, here....

IF you are trying to optimize boot time, then what you need to do is move all the files involved in booting into a single zone together. It doesn't matter if they are from windows or XyzApp or AcmeMenu or whatever. They are referenced during boot and therfore need to be fast to access to achieve minimized boot times.

Limiting this so that only "official windows" files are moved together makes the entire exercise futile, since it guarantees that many (or even most in some of the examples above) of the boot time accessed files are scattered across multiple zones. Since this is the case, why bother moving some of them to a zone of their own?

For those who feel that boot optimization matters, then the system as it currently is gets the best achieveable results, moving all the involved files.

For those who don't feel that it is important, don't do a bootoptimise. Easy.


I may have missed something, though, so can anyone explain to me why you would want just the "windows" boot files clumped together?


Personally, I use my PC far more than I reboot it, so boot optimization seems to be nothing more than an attempt to improve the perceived speed by shortening an easily measured metric.

[jonib]

I may have missed something, though, so can anyone explain to me why you would want just the "windows" boot files clumped together?

I think the problem is that Layout.ini lists some files that are not related to booting like I have *.mp3 files I listened to recently and other files, check you layout.ini if it has only boot/windows start related files listed.

jonib

[poutnik]

I think the problem is that Layout.ini lists some files that are not related to booting like I have *.mp3 files I listened to recently and other files, check you layout.ini if it has only boot/windows start related files listed.

I have there e.g. Nero.exe, which is for sure not related to booting time, I have not even its tray agent to be launched at startup.

Another thing, already mentioned, why so much optimize booting, if done weekly.

[jeroen]

But i trust that some sort of correct expression can be made, right?

Yes, it's very flexible. For a list of keywords see FileBoolean.

By the way, is it possible to download the standard scripts without installing?

No, not yet, perhaps in the future. The installer is very clean, it only places files in the installation folder, not anywhere else (such as DLL's in the Windows folder), and does not create keys in the Windows registry other than for the "*.MyD" association.

[jeroen]

I have there e.g. Nero.exe, which is for sure not related to booting time

Maybe you have a shortcut on your desktop? Icons are usually stored inside executables, so a program can be accessed at boot-time (and listed in the layout.ini file) just because of it's icon.

[poutnik]

I have there e.g. Nero.exe, which is for sure not related to booting time

Maybe you have a shortcut on your desktop? Icons are usually stored inside executables, so a program can be accessed at boot-time (and listed in the layout.ini file) just because of it's icon.

Yes, it will be a reason.