Absolutely! I have been testing and loving this program through all of the betas. Awesome work Jeroen. Thanks again for the great software for this Vista machine.
Rich

I have always used the Piniform Defraggler just to analyze my C drive (it has an easy to read visual block form read-out) and noticed something curious after using b12. All of the previous MyDefrag betas left empty spaces between some zones. I assume this is to allow growth. Beta 12 leaves no free spaces. It is most likely of no concern; my drive operates beautifully and is very "snappy". But since this is a forum for the beta users in the hopes of resulting in the optimum software, I figured I would pass this on. Other than that, the memory issues seem to be gone (for my system), the program exits gracefully, I have experienced no hang-ups or crashes, my data is intact, and as I said already, my Vista pc is very responsive and quick. Thanks again and have a great day/evening.
rich

I have run the slow optimize, fast update, and have checked the logfile and debug log and so far everything is working as it seems to be intended. Thanks Jeroen and all of the ever so knowledgeable folks here. MyDefrag is great software! Salutes to you!
Rich

After a slow optimize, I reanalyzed and found these files. I have not done any installs besides MyDefrag. I even ran Beta 7 after Beta * thinking it may be a bug. What are these huge files and can I reduce or remove them? Are they temporary? I have never seen them before. I know that my question is not MyDefrag specific, but so many of you on this forum are so informative and helpful I figured I may get an answer. By the way, I am running Vista 32 bit and have unhidden the hidden folders and still can not see the Install folders in my Windows directory. I've included the logfile just in case. Any ideas?

Same exact situation here. I posted details and debug log on the Questions category in the "analysis" topic that I started. Thanks everyone. By the way, GREAT program! It is shameful that there are not more people doing such great software. Also shameful that some are getting paid to release junk while people like Jeroen do it for free... Jeroen, I'm sure there are many people that would gladly buy your software.
Rich

Thanks everyone. This should maybe go in the "bugs" category, but here goes. There is a post with the same topic. I originally had the debug level on 1 when it ended up at 69MB and very slow "slow optimize", so I reduced it to debug 0. Much faster. It crashed on closing, so here is my debug log.
Thanks immensely, great program!
Rich

Thank you Jeroen for your info. I realize that the slow optimize script creates fragments, but this is the analysis right after running beta 7 slow optimize. The debug file for the slow optimize is 69MB's! What's up with that. Anyway, thanks again.
Rich

Can you tell me if this is "serious" or not? Anyone?

I have not seen a beta 8. Am I missing something??

After running Mydefrag beta 6, I ran the command line fragmentation analysis (-a C:) and it said 8% fragmentation. What percentage of fragmentation is considered "high" and in need of a defrag. I run the fast update every day or so and I know that the charts may look bad but it is all about optimizing, not necessarily "defragging". I'm just curious as to whether or not there is an "acceptable" and "unacceptable" percentage of fragmentation. Thanks again for teaching the newb!
Rich

Update. I reinstalled Beta 7 and ran the fast update, just to check it out. Fast update ran beautifully. Any ideas why the slow optimize would not run?
I suppose because I uninstalled it the logfile for the slow optimize is gone...? I am such a newb.
Rich

I love this program but have a question. Beta 6 worked like a champ. I ran beta 7 on slow optimize and it hung up on zone 7. It actually stopped for over 10 minutes so I stopped the process, reinstalled beta 6 and ran a fast update. I have kept my drive in good shape with beta 6 so it's not like it should be doing an overhaul. Slow optimize on beta 6 was much faster. Is it a bug in beta 7 or did beta 6 not do a thorough job so the beta 7 has to "clean it up"? Thanks.
Rich

I get that part. I am wondering why it is all the way at the end of the partition with the huge space between. Thanks Jeroen (or anyone else).
Rich

Not to sound stupid, but is it normal to have a rather large gap between the last files and the pagefile after a slow optimize? I have a 40G system partition with only 22G in use. The roughly 2G pagefile is all the way at the end of the partition with the 16 or so G empty space between. Thanks.
Rich

I saw these other reports of crashing so I had to try too! I just tried to analyze and it crashed. Here is my bug report. Go Jeroen!