do you not think that zone 5 could be split into 2 zones? Having all that Windows folder stuff so closely together with the Program Files seems unnecessary?
Why is that unnecessary?
So ALL winsxs folder should be okay at the end of the drive? Nothing in that folder needs to be in a more accessible place at all? The only thing I see is that you instead of using VolumeFree use VolumeSize quite a bit, putting all the System Files at like 1MB? I mean I got a 500Gig, but that's not all my System Partition... C: Drive is only like 156MB, it just seems like everything at the beginning of the drive is sooo crammed and that organization isn't taking place too efficiently as far as drive accessibility?
After defragging... All USB devices (except keyboard/mouse) must now be unplugged and plugged back in to find.
It's unlikely that this is a problem caused by my scripts or MyDefrag. Did you defrag them too or does this happen after defragmenting any volume?
Well, my thoughts being that after using the default scripts, I boot up fine... USB's are ALL recognized, including memory card reader using the internal USB port. After using your script, I have to unplug USB keys and the memory card reader is not on; however, during BIOS load is fine. So, yes drivers somewhere are going where Windows can't find them.
Lots of drivers are not taken into consideration... I was scared of that seeing all my winsxs folders going to the end of program files.
Are you sure that these drivers are actually used? Windows keeps a lot of backups.
Pretty sure... AMD Catalyst took about 4 times longer than usual to start, USB drives unrecognized? Drivers are going somewhere that Windows is like what's going on here...?
No matter what you do as far as running this... it seems like the first zone keeps getting bigger and bigger?!
The directories zone? Or do you mean zone 3 with the boot files?
-> Your Zone 3 leaves no gap between boot optimization and program hints zone.
That's indeed a bug. The VolumeSize * 0.. has gone missing somehow.
I'll fix that later.
Yeah, I think these both are hand-in-hand issues.
-> I noticed that you have basically just flip-flopped zones 1 & 2 vs. default monthly system disk.
The directories zone is usually more stable in size than the NFTS system files zone. If the latter one changes in size, the first one would have to be shifted around (moving a lot of small files 'expensive')
-> I had seen you reply to someone's script and say that putting the $MFT and stuff at the beginning of the disk is a step backwards in performance, your monthly script... puts them so much closer to the beginning of the disk than default?!
Most people like like to see short boot times. And since these files are at the beginning of the volume (along with a lot of other program files) I've come to the conclusion that this is a good place. You can change the location of the first zones if you like, that's what the Variables script is for.
Another thought is instead of right after the BootOptimization or where ever the Fonts are organized in... would it be beneficial for a monthly script since it should be the most lengthy anyways to FileSelect not(FileName("*.ttf") or FileName("*.font") or FileName("*.fnt"))?
So, we could maybe get those after the $MFT and all the ntfsFiles? They seem to be all bunched right at the beginning before these files... seems like leaving a bigger gap, and putting them afterwards with a gap before ProgramHints might be more optimized, rather than going through all these little font files to get to the necessities?
So, I'm failing to see the benefits in your script vs. the defaults?
Look what I've written in the first post. I've optimized them for faster optimizing without reducing performance. You can see the difference in my benchmarks
So basically this is for the speediness of the defrag and not necessarily a lengthy Windows FileSystem optimization? I just feel like there are a lot of files in the Windows directory that could have been placed more properly on the drive. Seeing Acrobat Reader and miscellaneous files (etc.) going right after $MFT can't bee the most proper placements... I dunno, I can't seem to type a proper Google search to find an informative lengthy Windows 7 FileSystem structuring/engineering article.
Not meaning to get on your bad side by any means, it just felt after looking at some things that they could be improved upon, but I would like to know for sure booting orders, driver orders (AMD & nVidia w/ programs necessary), and everything prior to writing a script... do you have any suggestions on reading material persay?
Also, based on your benchmarks this could be... not the best option for 7 as comparative to XP, correct?
/* Zone 3: files used when booting, and a gap. */
AddGap(RoundUp(ZoneEnd + maxGapSize, roundGapSize))
Change to end of Zone 5:
AddGap(RoundUp(ZoneEnd + maxGapSize, roundGapSize))
/* The minimum gap size between zones */
/* The maximum gap size between zones */
/* The size to round a gap between zones to.
* This is used to stabilize the position of a zone. */
SetVariable(roundGapSize, VolumeFree * 0.01)
So, far with these small changes... it looks like nothing that has been .dll or in the Windows folder has really gone to the end of the drive at all... Just things unused that I can tell, 70% done with Zone 5, but yeah not many .dll's or .sys files have gone to the end of the drive... lots of winsxs files have been bumped up to the lower end such as drivers, etc... but yeah... ALL of this folder and the majority was at the end of the drive. We'll see how it does after a boot up?
Possibly just a gapping issue in Windows 7 that caused everything and I mean EVERYTHING in winsxs folder to go to the end of the drive and it felt like the basic drivers were not close enough during boot?
Or maybe rather your values of VolumeSize * .01 on a 1TB roughly 10MB, 500Gigs roughly 5MB? 156 roughly 1.5MB, correct? So it can get pretty darn crammed...Boot results:
- 1st/2nd - Everything boots fine... Catalyst long wait time to load.
- 3rd - USB key/Memory Card reader are unrecognized, Catalyst still long load, un-plug/plug-in USB key Windows recognizes asks to explore or readyboost
- 4th - USB key/Memory Card reader work again.
- 5th - Unrecognized... unplug/plug in still workaround, but memory card means to open the case.
In Windows 7, there isn’t a ‘dllcache’ folder and nor can you find the ‘i386′ folder, where the system caches (like in XP) all it’s source modules. It is this WinSxS folder which stores the shared components of side-by-side applications. These files can be multiple versions of the same assembly or application. Every side-by-side assembly has a unique identity. One of the attributes of the assembly identity is its version. “Side-by-side assemblies are used by the operating system as fundamental units of naming, binding, versioning, deployment, and configuration. The Winsxs folder includes all manifests, optional components and 3rd party Win32 files”.
So maybe in the zone that sorts the Program Files and winsxs and all the "regular files" it would be best to sortby LastAccessed? Just thoughts, because after realizing this is deemed XP optimized... well, I just know that something gets in a whacked order when using this on Windows 7, because this is the only times I have these problems at all, honestly.
Which sorting by Ascending may not technically affect XP negatively in anyway as "dllcache" and "i386" folders would be relatively close to the beginning of this zone.It appears that certain "Registry HardDrive Performance Tweaks" were having a negative impact on the way my system was defragging, after setting LastAccess, 8Dot3, All Prefetch values, and many other FileSystem related registry values, it appears to be corrected. I am 100% sure of this as I realized that $Top should have NOT been moving with $MFT.
So, my apologies for everything I have said!
And a word to anyone else looking for "optimizing" Windows "HardDrive" performance tweaks are mainly geared towards SSDs NOT HDDs! Be careful even with SSDs Windows has pretty much turned off Prefetch, SuperFetch, etc. for your optimal performance! HDDs are defaultly optimized in the registry, basic routine maintenance is all that should be upheld for optimal system and hard drive performance!