ektorbarajas

Hi enoskype, thanks for the advice. I guess that iobit needs to provide clearer options for the users, but will try your suggestion regards

I'd appreciate any input from iobit Staff Thanks

I'm familiar with them. but since older versions, there are some things that are not very clear (you can see that I'm not the only one, several other users have such questions in the forum)

Hi. I'm confused since ASC autocare has a module that checks and free ram as needed, but it seems that smart RAM is more advanced, so should I enable smart RAM to run at startup? is there any conflict having Smart ram enabled and with ASC ram module??

Blackviper integration? Hi. I've read in the forum that a Service Optimizer has not being implemented to ASC since Blackviper is a very good and reliable source for manually optimizing Windows services. But has IObit ever considered integrating blackviper's recommendations and create a Service Optimizer? perhaps working together with Blackviper, or asking permision? I've checked other "System tweakers" and only few of them offer a service optimizer, and it's very scarce! It would be great that ASC has that function also, and to provide a detailed information of the recommendations and perhaps even manage profiles. Regards

Here is a third suggestion: 3) make Context Menu Manager capable of also adding new entries and sub-entries (not just delete them), so you could add a new item directly or inside a folder.

A better and more visual Context Menu Manager (WYSIWYG) Hi. I just purchased ASC 7.3 pro and so far I like it :-D I have some suggestions for the "Context Menu Manager" Instead of "hiding" it inside "IE Helper", put it right under "Repair" I've tried several context menu tools, and I have found in all of them (including ASC) that they are hard and difficult to understand, why? because they MUST have a visual preview, for example, to have a WYSIWYG interface so if you enable/disable something, then on a right panel you will have a real visual representation of how the context menu will look with that change. IObit has the opportunity to be the pioneer of this WYSIWYG context menu manager!8-) Kind regards

Hi. Here another suggestion: Automatic Update: Currently when there is a new version, the software opens a webpage and you have to manually download and install the app. Would be great to have an option to enable or disable "automatic updates", Then if automatic update is enabled to have two options: 1) Download and install updates automatically 2) Just download the update and notify the user Either option should also display the changelog, the first one just after the update finished and the second one among the notification of a new version. In case the setting "Automatic update" is disabled, then the update process will be done manually (as it is currently with SD3). Regards

Hi. Hope my suggestions posted for SD3 get considered for SD4: Here is the original post: http://forums.iobit.com/showpost.php?p=98705&postcount=70 And here they are again with additional comments: IN RED ARE SOME ADDITIONS BASED ON MY EXPERIENCE WITH SD 3 1) SD run as a service not just as a startup program: The reason for this is for SD to start working even if no user has logged in, this is a must have for windows servers, but for other editions of windows it's also great because as soon as windows starts or a user logs off, SD is able to start working before loading some additional files, hence further optimizing the HDD. 2) make SD 64-bit: 32-bit programs works on 64-bit, but if a program "IS" 64-bit then it performs better in 64-bit environment. This could be handled in two different ways: A) to have two installers, one for 32-bit and another for 64-bit B) that the installer has both versions, it will install 32 bit for 32 bit windows and 64 bit for 64 bit windows or let the user decide what version to install. 3) Allow to fully resize columns, list of drives and drive map (and any other layout item) and to store the new configuration, so that every time you open SD the customized layout presentation is preserved. I noticed that this point is well explained in this thread: http://forums.iobit.com/showthread.php?t=15675 by enoskype 4) A more comprehensive boot time defrag: Right now boot time defrags: Page file, Hibernation file, MFT and system files. Would be great to add the default defrag methods to also be performed at boot time: A) Defrag B) Defrag and Fast Optimize C) Defrag and Full Optimize D) Defrag and prioritize The reason?, for SD to further defrag and/or optimize the drive(s). Specially for the "C" drive, since some files could not even get defragmented by SD because they are in use. For example. If I have a startup program like an AV, firewall, etc. the open files are not defragmented and they are not considered system files, hence they are not defragmented with the current boot time defrag And let the user choose when to do a “Boot Defrag”, “Boot Defrag and Fast Optimize”, and “Boot Defrag and Full Optimize”. and a "Boot Defrag and prioritize" For example, the recommended boot time is every 7 day first boot. So in a separate setting you could choose how often the other defrag methods will be run, and allow each method to be configured individually, for example: Defrag - Every 7 day first boot Defrag and Fast Optimize - Every 14 day first boot Defrag and Full Optimize - Every 60 day first boot. Defrag and prirotize - every 120 day on first boot. Obviously Iobit would define the default setting, just as the "every 7 day first boot" for the current boot time. Perhaps the recommended setting will be to have disabled those additional 3 boot time defrag? NOTE: i think Iobit approach for default settings has being great, so for novice users the default would work, and a more advanced or experienced user could further configure SD with those additional boot defrag methods (and other options as well) 5) SD to be aware when a USB drive is going to be safely remove: Sometimes when you want to safely remove a USB flash drive or USB EHDD, SD will not allow to do that, even if the USB drive is not set for automatic defrag. That feature should also work for USB drives that are set for automatic defrag and that are being defragmented, so SD detects the "Safely Remove" request and releases the drives for safe removal. NOTE: I believe that this is already working with SD 3.1.0.319, since I has being able to safely remove my USB devices, just keep an eye on that so that SD4 also has this feature 6) Improve the drive map, so SD mark with a different color the page file, the hibernation file, the VSS files and the system files: Doing so will give a better idea of how fragmented are those files, since at this moment all that files are all grouped as "ummovable files" 7) All users installation: SD 2.9 installs only for the current user, so if another user logs then SD will not start. AND SD 3.1.0.319 also installs just for the current user check my post regarding this topic: http://forums.iobit.com/showthread.php?t=16678 This could be addressed with two methods: 1) Include an option to install to all users. and also to make sure that SD not only installs for all users, but that it will run for all users, even new users 2) Make SD to run as a service. I think this is the best approach, sine SD could start working without any user logged. I would really like to see this approach of SD run as a service, this is the only way for making SD run without any user logged in, and so start optimizing and defragging the drives when the computer is idle AND no user has logged in yet. Hope my suggestions get considered to improve SD :-D Hope now they are considered for the upcoming SD4 :-D

SD GUI must me able to diplay more than 4 drives I noticed that no matter of what size you set the GUI, the max number of drives displayed are 4, if you have more than 4 you're not able to move the division in the GUI so that more than 4 drives are displayed. In my case sometimes I have a total of 6 drives (local, EHDD and USB Flash) and I'd like to move that division. Attached is a screenshot to explain this

Regarding SD and multiple users accounts Regarding SD and multiple users accounts: I've noticed that SD 3 beta 2 can be started from another user account, even if the program was installed by other user. I remember that SD 2 was different, only the user that installed it was able to run it. BUT I also noticed that the settings defined by the user who installed the program do not appear if the program is started from another user account, when another user starts the program it appears as a new installation. My guess is that SD 3 beta 2 stores the setting in the user's profile folders. Would be great to fix this so that SD starts and runs with any other user AND the settings are shared among all the users. Regards

Hi Cicely. If I select "do not display removable drives", the changes are not reflected immediately, I have to completely close SD (from the tray icon, not just the GUI) and open it again, then just the local drives are displayed. But that is for no use for me, since I have EHDD that would like to be monitored and worked by SD. Also If I disable the "do not display removable drives", I have to completely close SD and reopen again, since the changes are not reflected immediately. I guess that SD must refresh automatically, with the change of "do not display removable drives" AND with a USB drive insertion/removal. That will avoid the issue if analyzing or defragmenting a phantom drive. About that issue (issue #2 on my post), here are the steps to recreate it: Pre-requisites: To have attached a EHDD, so that SD detect it and display it 1) Open SD GUI 2) SD GUI should display the EHDD 3) Without closing SD GUI, proceed to safely remove the EHDD 4) Disconnect the EHDD 5) SD GUI keeps displaying the EHDD (even that it was removed) 6) Perform an "Analyze" or "Defrag" on the phantom EHDD 7) SD tray icon display an animation like doing something but the GUI displays nothing 8) back on the GUI press stop on the phantom drive 9) but still the tray icon displays an animation like SD doing something 10) back again on the GUI, you're no longer able to perform an analyze or defrag to any drive (local or external), due to the phantom process that SD just started. 11) so the only option is to completely close SD (GUI and tray icon) and reopen SD again Hope I was clear enough :wink: EDIT: I believe using "non existent drive" or "the drive which is not connected to the computer" instead of "phantom drive" may be more clearly understood. :razz::wink: enoskype

I've also noticed that sometimes. when a USB drive is removed, just by closing and reopening the GUI the drive is removed from SD, but other times even after doing that, the removed USB is still displayed in SD. This happens at a random basis. Another issues I've just noticed is that for USB drives, the "recognize as SSD" setting is not saved, so if you remove and reinsert that drive SD still detects it as a HDD, I guess that this change (HDD or SDD) must be stored by SD based on the USB drive unique ID. Cheers

Attached is a screenshot for the issue #2. On that screenshot you can see that even that I have checked the C drive and it’s highlighted the buttons for analyze and defrag are disabled. I'm unable to perform such operations in ANY drive. And while that happens the tray icon shows the animation like SD is doing something. (the phantom defrag on the phantom drive) This happens every time that the GUI is open and a USB drive is removed, the removed drive is still displayed in SD GUI and SD allows to click analyze and defrag for that removed drive. So in order to stop that phantom defrag, SD must be restated (close the tray icon and open again). I also noticed that if SD GUI is open and a USB drive is connected, it's not displayed; you have to close and open again the GUI for the drive to appear in SD. I think that SD should automatically refresh after a USB drive removal or insertion. About issue #9, I further test it and seems to work fine, just when you choose “only next boot”, after the reboot the setting goes to the default of every 7 days, so I guess its working. But perhaps add an option to completely disable boot time? So if a user only wants to do a defrag on the next boot but then never again?

Oh BTW I noticed that all my 3 computers are faster and more responsive :-D It's important to mention that after installing SD 3 beta 2, in the 3 computers I performed a boot defrag for C drive, then when windows started I immediately performed a "Defrag and prioritize files". Also in my laptop I was using PerfectDisk 13, I uninstalled it and after installing SD 3 beta 2, performing the boot defrag and the prioritize; I rebooted again and noticed a significant improvements in the boot time :mrgreen: I'm really impressed of how SD 3 works, and it's amazing that it outperformed PerfectDisk 13! even with all the bells and whistles that Raxco claims of it's software. IObit, congratulations and keep making SD the best disk defragmenter and optimization available. it's important to also avoid turning SD into a bloatware (like several commercial defragmenters are today) I know that you will certainly be able to implement user's suggestions without bloating SD. Cheers!

My feedback on SD 3 beta 2 I installed SD 3 beta 2 on two desktops and one laptop, all with Win7 SP1 in spanish language, here are my feedback: 1) When a USB drive is removed, and if the program GUI is open, the USB drive is still displayed in SD. This does not happen if the program GUI is closed (if the program GUI is closed and a USB drive is removed, when the GUI is opened the USB drive no longer appears, which is ok) 2) Then if analyze or defrag is attempted on the “phantom” drive, SD do nothing but after stopping then SD no longer offer the Analyze or Defrag options for any of the available drives, the option remains greyed. Also noted that the tray icon shows animation, like SD doing something (perhaps working on the phantom drive). The only solution is to restart SD (Attached is a screenshot) 3) SSD are similar to USB flash drives, but it would be great and a better approach to let SD autodetect USB Flash, also in case SD identifies incorrectly a drive to also add the option to “Recognize this disk as USB Flash” among “Recognize this disk as SSD” 4) Still SD only starts and run with the user that installed it, it’s a must that SD also starts with any other user. The best approach I think would be that SD run as a service, but for now a “all users installation” option would be a great workaround 5) With SD2 the map displayed several unmovable blocks, now with SD3 there are no unmovable blocks, what does this means? That SD 3 is now able to defrag/optimize what SD2 flagged as unmovable? Or just SD3 is hiding the unmovable blocks and they are not displayed on the map?. (and perhaps ignored by SD3) 6) What about SD also check the disks health (SMART) and Temperature? 7) What about that SD based on the disk health, suggest when a chkdisk must be performed? And eventually that SD could automatically trigger that event? (also let the user decide if SD automatically trigger chkdisk or just notify that a chkdisk is suggested) 8) Does SD 3 is able to suggest when a “fast optimize”, “Fully optimize” and “Prioritize files” must be performed? (based on the disks performance), if not then I think that would be a neat feature 9) Boot time defrag settings are restored to default (recommended) after computer is rebooted (settings are not saved)

I think a must have feature is: All users installation. SD 2.8 installs only for the current user, so if another user logs then SD will not start This could be addressed with two methods: 1) Include an option to install to all users 2) Make SD to run as a service. I think this is the best approach, sine SD could start working without any user logged.

SD 2.8 and above - suggestions Hi. After reading this long thread, here are my suggestions and justification: 1) SD run as a service not just as a startup program: The reason for this is for SD to start working even if no user has logged in, this is a must have for windows servers, but for other editions of windows it's also great because as soon as windows starts or a user logs off, SD is able to start working before loading some additional files, hence further optimizing the HDD. 2) make SD 64-bit: 32-bit programs works on 64-bit, but if a program "IS" 64-bit then it performs better in 64-bit environment. this could be handled in two different ways: A) to have two installers, one for 32-bit and another for 64-bit B) that the installer has both versions, it will install 32 bit for 32 bit windows and 64 bit for 64 bit windows or let the user decide what version to install. 3) Allow to fully resize columns, list of drives and drive map (and any other layout item) and to store the new configuration, so that every time you open SD the customized layout presentation is perserved. I noticed that this point is well explained in this thread: http://forums.iobit.com/showthread.php?t=15675 by enoskype 4) A more comprehensive boot time defrag: Right now boot time defrags:Page file, Hibernation file, MFT and system files. Would be great to add the default defrag methods to also be performed at boot time: A) Defrag B) Defrag and Fast Optimize C) Defrag and Full Optimize The reason?, for SD to further defrag and/or optimize the drive(s). Specially for the "C" drive, since some files could not even get defragmented by SD because they are in use. For example. If I have a startup program like an AV, firewall, etc. the open files are not defragmented and they are not considered system files, hence they are not defragmented with the current boot time defrag And let the user choose decide when to do a Defrag, Defrag and Fast Optimize, and Defrag and Full Optimize. For example, the recomended boot time is every 7 day first boot. So in a separate setting you could choose how often the other defrag methods will be run, and allow each method to be configured inidividually, for example: Defrag - Every 7 day first boot Defrag and Fast Optimize - Every 14 day first boot Defrag and Full Optimize - Every 60 day first boot. Obviously Iobit would define the default setting, just as the "every 7 day first boot" for the current boot time. perhaps the recommended setting will be to have disable those additional 3 boot time defrag? 5) SD to be aware when a USB drive is going to be safely remove: Sometimes when you want to safely remove a USB flash drive or USB EHDD, SD will not allow to do that, even if the USB drive is not set for automatic defrag. That feature should also work for USB drives that are set for automatic defrag and that are being defragmented, so SD detects the "Safely Remove" request and releases the drives for safe removal. 6) Improve the drive map, so SD mark with a different color the page file, the hibernation file, the VSS files and the system files: Doing so will give a better idea of how fragmented are those files, since at this moment all that files are all grouped as "ummovable files" Hope my suggestions get considered to improve SD :-D

Hi Cicely. Do you still need help with that? If so, does the recommendation must be installed? or just need to check if we are able to see it? I'm from Mexico and if you still need help with that please let me know Regards

Hi. If the answer is there then it's hidden :-( I only see at the beginning of post 40 the following verdy_p is just confirming that the article does not say where SmartDefrag takes the dates of creation/mofication. and then gives an explanation of MFT, USN, etc. But again, it's not explained

Hello.... we need a clear answer to that basic and critical question ! Thanks

Yet still no answer to that simple question? Guys, gals... please answer this critical question, since Iobit is the developer of the software they should know that answer !!!

Still no answer for that question? IMHO this is very important and needs to be addressed in a correct manner, please give a useful advise! Regards

How are "frequently used" files determined? Still that question seems to not being answered by iobit, and it applied for the most recent version (1.11). Sine many of us (if not all) should known, NtfsDisableLastAccessUpdate=1 disable the last access update which according to all tuning and tweaking tools improves performance (including Advanced SystemCare). Also some Antivirus programs are reported to updated that last access value So if SmartDefrag uses the NtfsDisableLastAccessUpdate then it's not reliable nor usable to have "frequently used" files Please iobit, give us a deep & complete explanation of how smartdefrag determines the "frequently used" files. Regards