Search the Community
Showing results for tags 'file modifier'.
Found 1 result
Super Update! Now supports full console actions and running commands from a text file! Run fropmod ? for options. Using the GUI: Drag and drop a file to the dropbox at the top. To set a date/time pair to the current date and time, right mouse click the control and hit Set to Now. Hold Shift to use alternate options. Hash is a slightly trimmed MD5 of the entire file, so large files will take a bit to compute. Using the CmdLine: FropMod uses a linear-style command line interface. Commands are linked together to perform tasks. Files are loaded using fropmod f <filename> or, to be compatible with native Windows functionality, fropmod <filename>. * Note that this mode will only function if the only parameter is the filename. Avoid using wildcards in the filename, as they will not always act as excepted. If the working directory is changed, FropMod will correctly handle relative paths. Every command after f applies to the file passed to f. There is no save command, so each operation is applied immediately. If ? is used, the GUI is automatically suppressed and further actions are ignored. ? is not valid except as the first parameter. nogui may be used at any place in the command string, except within parameters of other commands. It will suppress the creation of the GUI, and cause FropMod to exit immediately after all commands are parsed. Attributes (a) use the following format: +-RASHOT (Read-Only, Archive, System, Hidden, Offline, Temporary). The attributes N, D, and C (Normal, Directory, Compressed) are documented, but read-only. The Offline attribute is not compatible with files on removable drives. Additionally, Normal only appears when all other attributes are removed. Dates (d[m|c|a]) use the following format: YYYYMMDDHHmmss. Use the 24hr clock. I think these are broken right now (?) but if they work for you, great. Opening the file as an archive (z) extracts dependencies into a temporary folder, then opens the file through it. Only 63 parameters can be passed through the command line (including both commands and their values) due to AutoIt limitations, but larger strings can be used in an .fm1 script, and be run fully. FropMod Scripts (.fm1) are run using the e command. Technically they can be of any extension, but I may add action verbs to these files to run on double click in the future. Format of an .fm1 script: [FMScript] ;comment command [parameter] ;comment command [parameter] ;comment ;comment ... In an .fm1 script, there is no limit to the number of commands that will be parsed. Limit one command per line, as the parser will break if they are stacked. Comments can be by themselves or in-line with commands, using a semicolon. All white space is trimmed off the end of a command, as well. Scripts may be called from other scripts. Used properly, this allows for complex building of batch processing. HOWEVER, DO NOT COMMIT A MAJOR PROGRAMMING SIN AND CALL A SCRIPT IN ITSELF! This will kick off an infinite recursion that will quickly drag your system down to a speed at which an Apple 2 could compete. Moral of the story: be careful. The sources use the WinAPIEx and Resources UDFs. Here's the updated source and dependencies: fropmodsrc0.2.zip Modifies timestamps and attributes of files and directory trees. Can be used to fix EPOCHed files in some cases. Supports Drag & Drop. Supports console actions and text file scripts. Included in the archive is the source, examples and compiled x86/x64 EXEs with icon. Previous versions: Changelog: Regards, Cyberbit