Jump to content

Search the Community

Showing results for tags 'properties'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements and Site News
    • Administration
  • AutoIt v3
    • AutoIt Help and Support
    • AutoIt Technical Discussion
    • AutoIt Example Scripts
  • Scripting and Development
    • Developer General Discussion
    • Language Specific Discussion
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office


  • AutoIt Team
    • Beta
    • MVP
  • AutoIt
    • Automation
    • Databases and web connections
    • Data compression
    • Encryption and hash
    • Games
    • GUI Additions
    • Hardware
    • Information gathering
    • Internet protocol suite
    • Maths
    • Media
    • PDF
    • Security
    • Social Media and other Website API
    • Windows
  • Scripting and Development
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Found 7 results

  1. Hi All, I'm not sure if its possible that I'm trying to achieve, I've looked into https://www.autoitscript.com/autoit3/scite/docs/SciTE4AutoIt3/AutoIt3Wrapper.html and such resources for help, but I cant really find the answer to my question. So upon compiling the script in SciTE, the exe file is given a Description under file Properties>Details. I understand, that one can enter info manually there and it can even implement the version automatically with each compilation. What I'm trying to achieve is to somehow include the "@ScriptName" in the Details>File Descrip
  2. Here is another WMIC script that parses properties from various alias classes. ie: COMPUTERSYSTEM, CDROM, IDECONTROLLER, DISKDRIVE, etc. Download: WMIC_GET.au3
  3. How to get the thrid number of a file version. Example: Let's say I have a file with below properties. I want only the third number like here it is 1941 as highlighted. Is there any built in function to get it??
  4. I have a custom configuration file which has key-value pairs as in below format. BuildLocation:C:\Build BuildExe:setup.exe Release:r9.64.02 Silent:No InstallPath:default Compare :No MartUpgrade :Yes Bit:64 ERwinUpgrade:No I need to change the value of "BuildExe" using my program. Is there any inbuilt function already available for these kind of files?. Can any one help me how to do this.
  5. I found a very old AutoIt script for obtaining file version information (Properties > Details items like the version string, product name, copyright, etc.). It didn't work very well, so I rewrote it after I discovered FileGetVersion(). The problem is that FileGetVersion() is returning outdated information that seems to belong to an old version of the file, long after the file has been deleted and recreated. Windows Explorer, on the other hand, shows up-to-date version info in the Properties > Details tab because (I think) it's accessing the cached file metadata and/or the latest ver
  6. 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 <filenam
  7. Just some experimental Scite properties files scanner code. Probably already done in some way somewhere around here. #cs | Name: Scite properties scanner. | Version: (2011.10.02) | Type: Experimental/Concept. | Language: AutoIt ( | Source: http://pastebin.com/Xs3Qw7Rv | Author: MvGulik. #ce | Warranty: No warranty of any kind given nor implied. (aka: "use at your own risk") E: ake -> aka (ergo: misspelling.) mmm, seems a bug crept into the User part scan. [fixed] Duplicate import hickup. "Scite properties locator" probably a better name for this. ...
  • Create New...