Jan 12, 2015 - Interested in a learning how to write a feature screenplay? Check out NYFA's list of the top 10 websites to download movie scripts from and get. MyDefrag Scripts. Contribute to tumpio/mydscripts development by creating an account on GitHub. Tumpio / mydscripts. Pull requests 0. Projects 0 Insights Dismiss Join GitHub today. GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
HowTo This is a short guide that explains the basic functions of MyDefrag Script Creator (MDSC). A detailed version is in progress. To create a script with MDSC, three basic steps are required:. Select the volumes to be processed. Splitting the files on the volume into file groups. Set of actions to be executed for each file group The first point is self-explanatory, there are only few special cases. The management of the file groups will now be explained in more detail.
File groups Using file groups, files in one volume can be grouped and are then placed in appropriate zones on this volume. For example, all files of a program can placed on one place of the volume (and sorted, if necessary) to shorten the loading time of the program.
![Mydefrag Scripts For Movies Mydefrag Scripts For Movies](http://video.findmysoft.com/2012/05/11/jkdefrag.jpg)
Create file groups File groups are created under 'Volumes & Actions' - 'File groups'. A common way to group files together is by their file extension (eg. '.mp3') or all files in a folder (eg. Easy View In the easy view there is a toolbar with two columns on the right edge. Files that are selected by the symbols in the left column (with the '+' symbol) will be added to the group. Reversely, the files selected by an icon from the right column (with the '-' symbol) will be excluded from the group. The order in which files are in- or excluded does not matter: the exclusion symbol is more dominant.
If the folder 'Music' is included, but all files with the extension '.mp3' are excluded, then only those files will be included in the group which are in the 'Music' folder but do not have the extension '.mp3'. Advanced and free view In contrast to the easy view, the order of the entries is crucial: The list is strictly processed from top to bottom. From the second entry on in the list there is a connector visible, which decides how the selection criterion in this line is used in conjunction with the above entries. 'Add' means that the files, which are selected by the selection criterion, will be added to the group. 'Filter' however, means that only those files are included in the group, which both meet the criteria from all above entries, as well as meet the criterion in the current row. For example, if the 'Music' folder is selected as the first entry and the second entry are all the files with the extension '.mp3' and they are connected with 'Filter', then only those files files will be included in the group which are both in the 'Music' folder, and which also have the extension '.mp3'. If there is now a third entry created, which selects files with the extension '.wav' and with the connector 'Add', then, in addition to the mp3 files in Music folder, all wav files on the entire volume would also be included in the group.
If the connector would be set to 'Filter', too, then no files will be included in the group, as there is no file which has both the '.mp3' and '.wav' extension. File group priority If multiple file groups are created, it is almost impossible to avoid that some groups overlap, so that the file X can be in both group A and group B.
To decide in which zone this file will finally be placed, each group has a different priority. Basically, the higher the priority of a file group, the more files end up in the zone. If the file X is included in both Group A and Group B, it will be placed in Zone A, if Group A has a higher priority than group B. The priority of a group is independent of the placement on the volume.
In this way, for example, large, rarely used files (the so-called 'spacehogs') are excluded from other groups, by giving them a higher priority but placing them after all other zones on the volume. Local and global file groups Local file groups apply only to the script in which they are defined, global file groups can be used in multiple scripts. Thus, the group 'My Documents' can be defined once and several scripts can used it to always place the same files in a zone. Nevertheless, the priority of the group in each script determines how many files actually end up in the appropriate zone. If a global group is stored within a script file, it will be copied completely into it. If the script is opened again and the global group no longer exists, it can re-imported as a new global group or changed to local. If a global file group is changed and a script which contains an older version is loaded, you will be asked if, for example, the stored global group should be updated.
Each group has its own MyDefrag version. If a global file group is added to a script, it is automatically converted to the version of the script.
This conversion does not count as a change, so that the original and converted file group are still considered equal. When all file groups are created and the priorities are assigned, they can now be placed on the volume in the 'Zones' tab. Zones In the 'Zones' tab, the file groups are converted to the so-called 'zones', ie.
They get a permanent place on the volume. This depends on the chosen action and the previous zones. Placement By default, the zones in the list are read from top to bottom, i.e. The first zone is located at the top of the list, the last at the end. This list can also be adapted to the MyDefrag diskmap whereby the first zone is shown at the end (bottom) and the last zone at the beginning (top) of the list. For achieve this, the setting 'Flip zone placement view' in Edit Preferences must be checked.
This setting only affects the appearance of the list, not the order in which the zones are placed. New zones can be added to the list with the 'Add a new zone' button. Only so many zones can be added, as there are file groups. Each zone has a zone number, indicating the order in which it is processed. Usually, the first zone is located at the beginning of the volume, all other zones follow directly behind it. By adding settings before the zones, they can be placed at any point on the volume.
For example, the default MyDefrag scripts place the first two zones (MFT and directories) at 30% in the used space of the volume. The following zones will then be placed from the beginning of the volume. Note that once a zone is placed, it's files will no longer be moved, i.e. The first two zones in the above example are not affected by the subsequent zones. Instead of the two zones being moved again to make way for the subsequent zones, they will be placed around the two zones. Actions Once a zone has been added, different actions can be set for them. In the simple view, the most common actions are shown for a zone.
These are fairly self-explanatory. It should be noted here, however, that if only the action 'Defragment' is selected, the zone is not necessarily placed on one place of the volume but can be widely distributed over it. Here it is advised the the option 'Move files to zone' is also checked. If an action is selected, other options are automatically disabled because they are 'incompatible' to the chosen actions. If, for example, 'Sort by.'
Is selected, the 'Defragment' action is disabled, because the sorting already defragments files. In the Advanced and Custom View, there is no restriction on how the actions can be combined. The actions are executed strictly from top to bottom. Import and export of scripts If all zones were placed, they can be exported to a MyDefrag script by selecting Script - Export. If more than one action has been set up, all or a specific action can then be exported. If more than one action is exported, the action names are attached to both the file name and the title of the script. It is possible to import MyDefrag scripts by selecting Script - Import.
However, the representation of the imported script in MDSC is heavily dependent on it's complexity and the included comments. I recommend therefore, to not import the scripts created by MDSC again. The scripts should always be stored as a MDSC script instead.
I noticed that even if I set the priority of one application higher than another, if they both use the same drive (and both use the drive somewhat heavily) the first application running will keep drive priority. For instance, while defragging one partition on my EHDD (External Hard Disk Drive) if I then decide to play a video on that EHDD (whether it's the same partition or not) the video will load very slowly because (presumably) all the heads on the harddrive are focused on defragging and don't want to switch to playing videos. I've also noticed that even if I start my media player (VLC in this case) first when I'm done playing a video and start the next it's slowed (presumably because it was no longer using the disk for the brief period in between). What I want to know is if there's a way to to make my drive prioritize so say only 2 or 3 heads are dedicated to defragging (I'm assuming I have 4 heads and disc rotation isn't as much of a problem). The disk heads do not move independely of each other. You'll get terrible performance if you try to use any disk/partition while it is being defragged. JoeAlright, I didn't think about it that way.
I suppose it would be impossible for the heads to move separately. What about a way to make one program yield to another so if VLC needs to read the disk myDefrag will wait and allow it to do so then resume when disk use is minimal. At least as far as video goes I believe a large portion of the disk access is preloading, then it works from RAM which I have plenty of (3.5 accessible on my 32-bit system). Not sure if I'd have to adjust something in my settings to optimize preloading but, it's a thought. By execution priority do just mean via task manager? In that case I suppose it'll just have to do. So you understand why I'd want to run both things at once: I have a 2TB EHDD that's in major need of defragging.
![Scripts Scripts](/uploads/1/2/5/3/125397962/408670576.jpg)
Most of the opportunities I get to use the disk are opportunities I want or need to access it (Unfortunately since I share a room and have an early morning schedule it's extremely impractical to setup at night). MyDefrag doesn't give a time estimate (which is fine as I don't want it using any more power than need be) but, it could easily take 3 days straight which means a lot of stopping, waiting, and starting again. In my opinion, disk I/O programming is about the most complex aspect of modern computing. Even more complex than Ethernet stacks which is a well defined and documented architecture.
All computing is a many-layered subject of course. Typically easy to intellectually grasp in concept but with details that are mind boggling sometimes, at least for me.
In this thread, once the conversation went beyond the general discussion level at which it started out, I think the dialog began to require significant understanding of disk operating prinicples, I/O commands, the machine language of the chips involved, and the internals of the O/S to be fruitful. There is one thing I'll say with confidence as an old programmer, there is a lot going on at the lower programming layers / levels, beyond that which is apparent at ground level. This is especially true with disk defrag software where reacting to real time events plays a huge role in how the code must be written to work right and get the right things done. My point is that it follows that there are many I/O considerations that the user has no direct or even indirect control over. Regarding disk defrag software, just one area of concern and far from the entire scope of potential discussion, the disk defrag software itself may provide capabilities.
In the case of Diskeeper, the leading 3rd party alternative to the free Windows defrag tool, there is an internal 'priority' setting that would help somewhat in this scenario. With Diskeeper, one usually has it running all the time 'in the background' and Diskeeper (in just one example of the low level programming I'm talking about) interrupts I/O write requests (application and O/S requests to the O/S to write a record to the disk), buffers / caches individual requests, thereby to allow fragmentation avoidance on the fly. Obviously Diskeeper must be able to intercede, even when it is running at relatively lowered priority. To explain even conceptually how this occurs would be pages of the densest reading imaginable.
That is if Diskeeper would share with us which of course they won't as they have invested heavily to create this competitive differentiator. Just an aside, and after all that I've just said, it appears that the Diskeeper priority setting only works when a batch defrag process is manually invoked. In other words, the priority of real time processes can not be altered. Anyway, this is a very complex topic and I'm already beyond my (limited) knowledge regarding modern disk I/O programming so I need to stop typying. It is extremely rare for me to not be using my computer and since I'm mostly concerned with Defragging my 2TB External Hard Disk Drive which is far from a portable device (it requires a power outlet and it doesn't have as much shielding as a true portable hard drive) being able to do both at the same time is the only solution I can really think of. I should probably also mention that MyDefrag is a really good optimizer and not just a defrag program. The external hard drive gets a lot of use and thus fragments build rather quickly besides that I almost never have a chance to defrag it.
I like to use Optimization because it takes into account where new data will written and puts the largest files in the fastest part of the disk (smaller files don't need the speed boost as much). I realize the actual scripting capabilities of MyDefrag may also offer a solution but I'd rather just let the script work as it wants while placing restrictions on the outside. The reason I say this is because 1.) I like the default scripts and don't want to screw them up and 2.) I don't know nearly enough about the internal operation of my disk to write such a script (I know the basics and the theories). That being said: I have been trying the processLasso program kabluiii mentioned before and with very little configuration I've actually noticed a difference in responsiveness (I've been having issues with responsiveness in general lately but I just figured it was time to reformat and get rid of the old/extra crap). I should also mention that the drive I was defragging just broke.
The USB connector within the drive actually snapped and I'm currently looking to see what kind of support I can get (and I better get support since I paid an extra $10 for the extended warrenty). With any luck I'll be able to get all my data back (I really hope so since a few hundred Gigs was backup data and installers I'd rather not try to replace including my copy of Windows 7 Pro 32-bit installer and a couple versions of XP).