Jump to content
Ketarin forum

All Activity

This stream auto-updates

  1. Last week
  2. Welcome aboard @Novae7 - great to have you here. Thank you for your contribution. With Bleeping Computer not every download has a version number, so I use the date ("{yyyy}.{MM}.{dd}") for the ones that don't, like FRST. I usually parse for the redirect, too. On the /dl/# page I use this regex pattern: "\d+;\s*url=([^"]+)" That captures the redirect from the download page so you can get the actual file URL. Finally, because Bleeping Computer uses these session/temporary download URLs, I then upload the file to one of my servers using a static URL so I can automate downloading it on client devices. I use curl & ftp for that with the following syntax in the "execute after downloading" command: curl --ssl-reqd -T "{file}" ftp://user:pass@server:port/path/
  3. Earlier
  4. Thanks for the info
  5. no, it's not you. Adobe sometimes has significant lags between their releases and updating their underlying version-checking stuff. in this case the release notes and the actual release download (from their own download page) are out of sync. again. this is their actual download page option right now, which remains the older version: i used to contact them every 3 or 4 months when their release notes and downloads were out of sync for different products and they eventually just removed the entire all-products releases page because they couldn't be bothered to maintain it. sadly, this is just a sign of why you should avoid adobe products: if they can't even figure out how to automate such a little thing (hook it into your build process guys!), who knows what else is screwed up in their software?
  6. Maybe I made myself misunderstand. This link presents an old version (20857) after this version was released at 2089x and the latest version is 20933 Acrobat Enterprise Release Notes — Acrobat-Acrobat Reader Release Notes (adobe.com)
  7. It's working fine for me. Maybe you experienced an Adobe website issue? Is it still having problems?
  8. This link dont show update version anymore How to fix it please? https://rdc.adobe.io/reader/products?lang=en&platformArch=64&site=landing&os=Windows 10&preInstalled=mss%2Cmsc&country=US&nativeOs=Windows 10&api_key=dc-get-adobereader-cdn
  9. I messed it up a bit. The link for the version number shows two versions. One is the full version number and the other is the shortened number which is needed for the download link. My bad!
  10. Works great thanks a lot Do you know the links for pro version? i only found for web_installer Download Acrobat installer for Enterprise term or VIP license (adobe.com)
  11. And these are the full Reader EXE installer URLs (for English): x64 https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/{dirtyversion}/AcroRdrDCx64{dirtyversion}_en_US.exe x86 https://ardownload3.adobe.com/pub/adobe/reader/win/AcrobatDC/{dirtyversion}/AcroRdrDC{dirtyversion}_en_US.exe
  12. With those URLs and the JSON response I would recommend just pulling the version number directly with (as {version}): "version":"([\d\.]+)" This avoids manually fiddling with numbers that might have issues. Today they describe 2024 as the major version and use 24 internally, but who knows what they'll do tomorrow.
  13. Big thanks It works, but i need to make change on {version} because will get 20 in being of URL. With i (?<=Reader\s)([0-9.]{2,})(?=\sEnghish) get ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/202400220857/AcrobatDCx64Upd202400220857.msp The correct link is ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2400220857/AcrobatDCx64Upd2400220857.msp
  14. Hi, I had the same problem but I had not invested much time in finding a solution. That's why I used an earlier option that still works today. The update versions for Acrobat and Reader are identical as far as I know. So this should also work here: For Adobe Reader Continuous/DC (en-US 32-bit) https://rdc.adobe.io/reader/products?lang=en&platformArch=86&site=landing&os=Windows%2010&preInstalled=mss%2Cmsc&country=US&nativeOs=Windows%2010&api_key=dc-get-adobereader-cdn For Adobe Reader Continuous/DC (en-US 64-bit) https://rdc.adobe.io/reader/products?lang=en&platformArch=64&site=landing&os=Windows%2010&preInstalled=mss%2Cmsc&country=US&nativeOs=Windows%2010&api_key=dc-get-adobereader-cdn From die above URL I get {version} using the following regular expression: (?<=Reader\s)([0-9.]{2,})(?=\sEnglish) This is these are the download links: Acrobat 32-bit https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/{dirtyversion}/AcrobatDCUpd{dirtyversion}.msp Acrobat 64-bit https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/{dirtyversion}/AcrobatDCx64Upd{dirtyversion}.msp Reader 32-bit & Reader 32-bit MUI https://ardownload3.adobe.com/pub/adobe/reader/win/AcrobatDC/{dirtyversion}/AcroRdrDCUpd{dirtyversion}.msp https://ardownload3.adobe.com/pub/adobe/reader/win/AcrobatDC/{dirtyversion}/AcroRdrDCUpd{dirtyversion}_MUI.msp Reader 64-bit & Reader 64-bit MUI https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/{dirtyversion}/AcroRdrDCx64Upd{dirtyversion}.msp https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/{dirtyversion}/AcroRdrDCx64Upd{dirtyversion}_MUI.msp Where {dirtyversion} results from the version number but without the separators: {version:replace:.:}
  15. Hello until sometime ago this configuration work ok but now says the operation timed out. If i follow the link the browser open with no problem. Can somone fix it please? Thanks <?xml version='1.0' encoding='utf-8'?> <Jobs> <ApplicationJob xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Guid="504f0468-119d-4dcc-822f-80f1bf385340"> <WebsiteUrl /> <UserAgent /> <UserNotes /> <LastFileSize>519847936</LastFileSize> <LastFileDate>2024-05-14T16:23:48.3104132</LastFileDate> <IgnoreFileInformation>false</IgnoreFileInformation> <DownloadBeta>Default</DownloadBeta> <DownloadDate xsi:nil="true" /> <CheckForUpdatesOnly>false</CheckForUpdatesOnly> <VariableChangeIndicator>releaselink</VariableChangeIndicator> <HashVariable /> <HashType>None</HashType> <CanBeShared>true</CanBeShared> <ShareApplication>false</ShareApplication> <ExclusiveDownload>false</ExclusiveDownload> <HttpReferer /> <SetupInstructions> <SetupInstruction xsi:type="StartProcessInstruction"> <EnvironmentVariables /> <FileName>{file}</FileName> <Parameters /> <WaitForExit>true</WaitForExit> </SetupInstruction> </SetupInstructions> <Variables> <item> <key> <string>releaselink</string> </key> <value> <UrlVariable> <RegexRightToLeft>false</RegexRightToLeft> <VariableType>RegularExpression</VariableType> <Regex>&lt;a class="reference internal" href="(?&lt;link&gt;continuous/[]!"#$%&amp;'()*+,./0-9:;&lt;=&gt;?@A-Z[\\_`a-z{|}~^-]+#[]!"#$%&amp;'()*+,./0-9:;&lt;=&gt;?@A-Z[\\_`a-z{|}~^-]+)"&gt;</Regex> <Url>https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/index.html</Url> <Name>releaselink</Name> </UrlVariable> </value> </item> <item> <key> <string>download</string> </key> <value> <UrlVariable> <RegexRightToLeft>false</RegexRightToLeft> <VariableType>RegularExpression</VariableType> <Regex>(?-i:href=")(?&lt;url&gt;(?-i:https://)[]!"#$%&amp;'()*+,./0-9:;&lt;=&gt;?@[\\_`a-z{|}~^-]+(?-i:\.adobe\.com)(?-i:/pub/adobe/acrobat/win/AcrobatDC/)[]!"#$%&amp;'()*+,./0-9:;&lt;=&gt;?@[\\_`a-z{|}~^-]+/AcrobatDCx64[]!"#$%&amp;'()*+,./0-9:;&lt;=&gt;?@[\\_`a-z{|}~^-]+(?-i:\.msp))"&gt;</Regex> <Url>https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/{releaselink}</Url> <Name>download</Name> </UrlVariable> </value> </item> </Variables> <ExecuteCommand /> <ExecutePreCommand>write-host $app.Name</ExecutePreCommand> <ExecuteCommandType>Batch</ExecuteCommandType> <ExecutePreCommandType>PowerShell</ExecutePreCommandType> <Category /> <SourceType>FixedUrl</SourceType> <PreviousLocation>D:\Backups\Tools\Adobe\Adobe Acrobat Pro\2. Update\AcrobatDCx64Upd2400220759.msp</PreviousLocation> <DeletePreviousFile>true</DeletePreviousFile> <Enabled>true</Enabled> <FileHippoId /> <LastUpdated>2024-05-14T16:23:48.3104132</LastUpdated> <TargetPath>D:\Backups\Tools\Adobe\Adobe Acrobat Pro\2. Update\</TargetPath> <FixedDownloadUrl>{download}</FixedDownloadUrl> <Name>Adobe Acrobat Pro Updates x64</Name> </ApplicationJob> </Jobs>
  16. Currently (Ketarin 1.8.11.0) there are four separate Event Commands available: 1) Before updating an application 2) After updating an application 3) After updating all applications 4) When application update fails These are great for pre-download validation and post-update & post-check failure documentation, but they don't address every scenario. I would like one more Event Command available: Before checking for updates for an application. When I have parallel downloads set to 1 then it's a safe bet that the next one in the list is responsible. When I have parallel set to 2 or 3 (or more) then it's a whole lot of guessing. This new event would trigger before any variables were parsed (other than the name) so that I can log the progress of "update all" or "check for updates" on a selection. This would allow me to write the pre-parse progress to a permanent log file so I can better troubleshoot errors. Currently, when Ketarin crashes (which isn't often, but is often enough that it's frustrating) I have to guess which application is responsible and which variable or URL it was within the application that might be causing the problem. I can work around some of this with special variables and the ":ps" function, but more difficult than it could be to figure out which one is responsible. Alternatively (or in addition to) there would be an option to write to a log file that mirrors the activity in the real-time log (CTRL+L). This could either be one massive file (ketarin.log), or based on the date, or based on variables (like "ketarin-{yyyy}{MM}{dd}{hh}{mm}.log" or "ketarin-{category}.log" or even based on the "save as" destination with an additional ".log" appended: "..\{category}\{appname:regexreplace:([\s\t\r\n\-\&]+):_}-{version}.{url:ext}.log" where as-yet-unparsed variables would be replaced with dashes or underscores). Each application should have the log file name preserved for the duration of the specific application, so if the log file name were "ketarin-{yyyy}{MM}{dd}T{hh}{mm}.log" at 20240414T1345 and it took 4 minutes to process the application, all log records relating to that application update would be written to that log even though the time were actually 20240414T1349 by the time it was done.
  17. Interesting issue with the SetDefaultBrowser and SetUserFTA programs: Microsoft broke them with a recent registry service "fix" to control the browser behavior and enforce "user choice". Evil bastards.
  18. thanks for the pointers! Aria works! https://imgur.com/a/FmsH6yC I have the version number set, along with previous (See also link above). At this point, have no idea why the other one isn't working.. but I have a working example, so thank you for that! EDIT: I noticed that aria works even without kuppet so I don't think it means that kuppet works.. In any case, even with kuppet, I still get the 405 error with Cheat Engine. At this point, I guess it would be best to stop bothering you guys, thank you for the support so far Cheat Engine.xml
  19. if you don't have a lot of requests or apps then changing the UA globally is unlikely to help. if you do, then you might want to change it and keep it relatively current. the format for the version string in Chrome UA is "Chrome/major.0.0.0" - it never includes the minor or build numbers. This is similar to all other modern browsers - they don't include anything but the major version dot zero, and sometimes an additional couple dot-zeroes. Change it to: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 That alone might help. If you haven't set the Version number column to display in the main interface you might want to do that first. This ensures that you can see when new versions are detected and might help you troubleshoot this one. Since this site is one of the ones that is really aggressive about spiders you might want to test with a different one. I've attached another one (aria2) that uses Kuppet. aria2.xml
  20. Yes, my global UA is the default one: Mozilla/4.0 (compatible; Ketarin; +https://ketarin.org/) is it a good practice to change it to something else? In any case, I copied the same UA, that I put in the kuppet.config file, in the app profile, which is the exact version stated in the browser About page: I tried to check the versionstub variable, but the problem seems to be that it cannot load the page? although I see it in the Chromium browser (it loads correctly after the 3 second Anti-Crawler IP checker page): https://imgur.com/a/Kz9g0Bv
  21. Is it detecting the version number correctly? Or is it just the download that's failing? You might also need to change the global user-agent (File, Settings, Connection, Default user agent) or at least assign one within the app profile at Advanced Settings, User-agent. By default the user-agent indicates it's Ketarin and might be getting blocked.
  22. hmm, I removed the old UAs and manually updated chromium and the string to match the latest v124. With Browser visible, this is what I see: but it still times out.. thank you all for the support kuppet.config
  23. I recommend removing the older user-agents from the userAgentArray variable. Firefox/65 and Chrome/100 are both *very* old and many security features on websites now block them by default. The next troubleshooting step is to change the chromeVisible value in your config to true. This will allow you to watch as Kuppet operates, which might be enough to see what is failing.
  24. Real Temp now works, thank you very much! regarding Kuppet, by looking at your output, I checked the config file included in the 0.8.7 release available on the forum and realized it needed setting up, so I modified that to make it look something similar to yours (see attached) and now I get a similar output: although Ketarin still times out before Kuppet can finish its job. What could be still missing here? thank you once again for your support! kuppet.config
  25. One more thing about Kuppet. It has a heavy-duty cache so it doesn't re-request pages unnecessarily, even if you think it should. If you ran it, cancelled, then ran it again you might have issues. Kill Kuppet and try again to make sure it purges it's own cache.
  26. Here's a working Real Temp that uses a PowerShell script to read the Location header from the POST response. Real Temp.xml SetDefaultBrowser works fine for me. Make sure you're not interfering with it! Kuppet has a built-in timeout that's higher than Ketarin alone, but this specific app uses an imposed 45 second delay *after the last activity*! This is important for anything that needs to bypass CloudFlare or Cloudfront CAPTCHA delays. This is the output I get in Kuppet with logging enabled: ---: Ketarin is playing with her puppet > Port:8080 Time: 3/13/2024 7:28:22 PM ===: KUPPET PARAMETERS ===: port : 8080 ===: kuppetTimeout : 360 ===: pageLoadTimeout : 90 ===: userAgent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 ===: verboseLogging : true ===: logging : true ===: chromeVisible : false ===: ----------------- ---: R01 | REQUEST : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: R01 | Post Data String: redirection-delay=45 ===: Chrome instance starting ===: The BROWSER user agent is : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/100.0.4889.0 Safari/537.36 ===: Opening new page ===: Set page-load timeout : 90 seconds ===: Setting PAGE user agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 ===: Set extra headers ===: Visiting : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: Rendering the javascript ===: Redirection-Delay for: 45 seconds ===: Rendering the Shadow DOM ===: Returning the rendered HTML - everything between <HTML>...</HTML> ===: 'Beautify' the HTML ===: Closing browser ---: R01 | RESPONSE : Cached:false : Duration:50.22 seconds ---: R02 | REQUEST : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: R02 | Post Data String: redirection-delay=45 ---: R02 | RESPONSE : Cached:true : Duration:0.004 seconds ---: R03 | REQUEST : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: R03 | Post Data String: redirection-delay=45 ---: R03 | RESPONSE : Cached:true : Duration:0.003 seconds ---: R04 | REQUEST : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: R04 | Post Data String: redirection-delay=45 ---: R04 | RESPONSE : Cached:true : Duration:0.003 seconds ---: R05 | REQUEST : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: R05 | Post Data String: redirection-delay=45 ---: R05 | RESPONSE : Cached:true : Duration:0.005 seconds ---: R06 | REQUEST : https://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ ===: R06 | Post Data String: redirection-delay=45 ---: R06 | RESPONSE : Cached:true : Duration:0.003 seconds
  1. Load more activity
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.