The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    are there command line options for ThrottleStop?

    Discussion in 'Hardware Components and Aftermarket Upgrades' started by ljwobker, Oct 31, 2018.

  1. ljwobker

    ljwobker Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    5
    I'm thinking about trying to automate some testing on my new machine (X1 gen6) and was wondering if there are any command-line arguments to ThrottleStop that would allow me to change various parameters directly from the CLI?

    If not, I can probably write a script that directly edits the throttlestop.ini file and kills/reloads the application, but direct variables in the CLI would likely be cleaner.

    Anyone else tried anything like this? Any suggestions or gotchas I should be aware of before I go poking around? I searched through the obvious places, but I'll admit to not having read through all 900+ pages of the main throttlestop thread! ;-)
     
    ljwobker, Oct 31, 2018
    #1
  2. unclewebb

    unclewebb ThrottleStop Author

    Reputations:
    7,815
    Messages:
    6,414
    Likes Received:
    6,728
    Trophy Points:
    681
    ThrottleStop does not use any command line arguments and no plans to add this in the future.

    Make sure you turn off and do not use the ThrottleStop system tray icons if you plan to kill the ThrottleStop.exe task.
     
    unclewebb, Oct 31, 2018
    #2
    Maleko48 likes this.
  3. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Bit late, but perhaps you could use this to get started:
    ThrottleStop .ini modifier startup scripts

    One odd thing I did run into was the combination ' =0'. Any other ' =*' is fine, but DOS treats this as a special null case (though undocumented). Trick was to use an escape for both the ' =' and the parameter's value, that way it works for both ' 0' and any other value.
     
    t456, Apr 28, 2019
    #3