A true full optimize script that will actually make your system faster.

[Falcon4]

The point is, time stamps are unreliable because of the fact that "date accessed" means nothing and is often disabled (Vista, right?). Date Accessed could be pushed by virus scans, indexing, or any number of other things. There is _no_ way to accurately determine what files are frequently accessed based on time stamps. Since the other time stamps are totally useless (date created, date modified), they aren't used either.

If there were a "read count" attribute in the file system, that would be a whole 'nother story. I would certainly use an attribute like that, because it specifically counts "how often" files are accessed. But since "date accessed" is digital - either "recently" or "not recently" - there's really no use in using it. =|

[poutnik]

The point is, time stamps are unreliable because of the fact that "date accessed" means nothing and is often disabled (Vista, right?). Date Accessed could be pushed by virus scans, indexing, or any number of other things.

Well, it is just nice illustration of "unreliability by interpretation" :-)
They are useless if you do not use them properly.

There is no problem for Vista to turn Last Access time stamp on,
and there is no problem to create a script
conditionally using the timestamp if it is available.

I do not denying there can be improper timestamp pushing. It depends how SW is written.
But there are still many many files left untouched.
BTW, I recommend Avast AV, not modifying LastAccess while performing disk scan.

There is _no_ way to accurately determine what files are frequently accessed
based on time stamps. Since the other time stamps are totally useless (date created, date modified), they aren't used either.

LastAccess timestamp is aimed for negative, not positive selection.

There is easy way to determine  files that definitely cannot be frequently accessed.
Sure, it will left some not frequently accessed files,
but not using the timestamp lefts ALL of them.

BTW, date accessed is not digital, but must be converted to digital by comparison,
because all decisions are digital by principle.
Note: I used your term digital, however I would prefer logical - boolean value

If user cannot use info about file modification, he should not blame a timestamp.
Of course, it cannot be used to access frequency determination, it has other usage.
For example frequently modified files, in combination with creation date.
In opposite to LastAccess, it cannot not pushed.
One can use it for both positive and negative selection.

Even filecreation itself has its limited usage as an age of filesystem item ( not file content ).

Finally, if claiming timestamps say nothing, notice yourself that paths themselves does not say much.

[chupa]

I say I use it daily as in, I use it on different systems daily. I'd say I've used this script on over 100 systems so far, at least once a day (likely closer to 200). But I only use it once on a system, then delete it. It shouldn't need to be run again on that system for quite some time. Files don't just "move" on their own and system files aren't continuously updated (except the MFT, registry, and a few others). So you should just have to use it once and forget it

So, if I run this script and then later run a standard MyD script like OptimizeDaily or Weekly, will it wipe out all the changes your script makes?

[Darlis]

Yes. The only compatible script would be the Defragment script.

[skylar.sutton]

Failing in 4.2.3:

Code:

Fatal error, cannot execute the script: Syntax error at line 30 column 14.

The command 'no' is invalid, only the following commands are valid at this point:

Fixed
invisible
maximized
minimized
restore

[chupa]

It's a simple fix, just change line 30 to "WindowSize(restore)" instead of "WindowSize(normal)"

[Crimsonkage]

So I found something you might want to add to your script.
I am running windows 7 64 bit and I noticed your script doesn't move the Program Files (x86) folder.
So your script if ran on my system would optimize the 64 bit stuff and leave the rest (which is the majority) to be thrown to the end of the drive.

*Windows 7 64 bit has two seperate program files folders.*
Program files *The 64 bit programs*
Program Files (x86) *the 32 bit programs*

[greyowl]

I tried the script on my XP computer and it failed.  I got the attached message.

[dpc1970]

I get the same error (on Windows Vista Ultimate).

[Darlis]

The script is not compatible with the new versions. The attached one should work.

[greyowl]

It now works on my XP computer. 
How often do you recommend running your script?
Is it effective to still run the "Optimize Daily" script after running your script?

Thanks

[Darlis]

It is not my script, it's from Falcon4 .
Since the script does not use SortBy file actions, you can even use this daily.
And no, do not use any other scripts (except the defragment script).

[greyowl]

Thanks for the additional information.

Do you think this script is better than the weekly and monthly scripts supplied with MyDefrag?

[Darlis]

IMHO, Jeroen's scripts are better:
- The MFT is placed further in the disk and not directly at the beginning.
- Uses the layout.ini

Falcon4's script does not sort files, too(this can be easily changed though).
The grouping idea is good, but there are also lots of files which may never be accessed in a long time in between.

[greyowl]

Thanks for your thoughts on this.