Jump to content
Ketarin forum


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,134 profile views

Rainie's Achievements


Newbie (1/14)

  1. Hello there! Looks like the problem with multi-segmented downloads still exists for some servers. Reproducing: Set "Settings > Connection > Number of segments per download" to more than 1 and try to download https://download.teamviewer.com/download/TeamViewer_Setup.exe At this moment the file size is 22 796 808 bytes. The downloaded file will be corrupted (no digital signature). I see duplicated PE header somewhere in the middle of the downloaded file — each segment contains data from the start of the uncorrupted file. Ketaring concatenates these chunks into a single file, making it useless. For example, Westbyte's Download Master tries to download in parallel, starts the second section, sees no 206 response, no Content-Range headers and drops this section, continuing to download in single thread from the beginning. GET /download/TeamViewer_Setup.exe HTTP/1.1 ... Range: bytes=12716479- ... -------------- HTTP/1.1 200 OK ... Content-Length: 22796808 ... Ketarin's logs: 01.06.2019 14:02:13: Update started with 1 application(s) 01.06.2019 14:02:13: TeamViewer [Win, Setup]: Using referer: https://www.teamviewer.com/en/download/windows/ 01.06.2019 14:02:14: TeamViewer [Win, Setup]: Server source file: /download/TeamViewer_Setup.exe 01.06.2019 14:02:14: TeamViewer [Win, Setup]: Replacing {version} in '{SoftDir}\TeamViewer\v{version}\' with '14.2.8352' 01.06.2019 14:02:14: TeamViewer [Win, Setup]: Determined target file name: D:\Soft\TeamViewer\v14.2.8352\TeamViewer_Setup.exe 01.06.2019 14:02:14: TeamViewer [Win, Setup]: Using referer: https://www.teamviewer.com/en/download/windows/ 01.06.2019 14:02:15: TeamViewer [Win, Setup]: Using referer: https://www.teamviewer.com/en/download/windows/ 01.06.2019 14:02:18: TeamViewer [Win, Setup]: Replacing {version} in '{version}' with '14.2.8352' 01.06.2019 14:02:18: Update finished I suggest that Ketarin could adopt DM's behavior or at least could notify user somehow (simply writing to log isn't enough).
  2. @shawn, what definitely helped me: erase GUID from the forum settings, save. Enter the same GUID to the forum's settings, save. Also, one of the programs has been sharing the name with one from another author, so I slightly changed name of mine. Thank you very much!
  3. Sorry for the such a delayed replay, but the problem is still there: modifications I made to local profiles don't show up in the online db.
  4. Hello! I have the same issue: online database doesn't reflect my updates to my shared apps. Also, despite entered author's GUID in my online profile, I see no my app profiles here (particularly in the profile section). Ketarin
  5. DB Updates is now working! I've just got updates for some app profiles.
  6. So, what does a user need to do to keep imported (from online DB through the Ketarin) profiles updated? Looks like he should go for https://ketarin.org/forum/apps/, check, download and manually update the profiles he uses. I tested "Check for updates in the online database" function on 20 July 2015, a year past the last db purge. It isn't working. I hope I'm wrong, but it looks like that. UPD: OK, I wish you good luck fixing it.
  7. Thanks for the reply! When did the latest purge happen? Ketarin 1.7.1 was released on 29 Jan 2015, quite a long time ago. I see all my profiles in the Applications forum section, they're made by an "Unregistered User". How do I supposed to keep them updated from now on? Considering that Ketarin has not been able to connect to online db for a few last days. UPD: Updated my profile, the App section got updated too. But I'm still wondering how this system is intended to work.
  8. I've already tried the positive lookaheads and conditionals for such purpose. You've done a good job, however, your regex won't work in some rare theoretical cases. The universal solution seems not achievable without using mathematical comparison. Thanks anyways.
  9. I used the following regex to extract version number of Opera Browser from their FTP (http://ftp.opera.com/pub/opera/desktop/) (I use the RTL mode, but adding .* prefix also works) <a href="([\d\.]+)/"> But they have an odd sorting algorithm so the build 30.0.1835.125 is located higher on the list than 30.0.1835.88 due to leading "1": <a href="28.0.1750.40/">28.0.1750.40/</a> <a href="28.0.1750.48/">28.0.1750.48/</a> <a href="28.0.1750.51/">28.0.1750.51/</a> <a href="29.0.1795.47/">29.0.1795.47/</a> <a href="29.0.1795.60/">29.0.1795.60/</a> <a href="30.0.1835.125/">30.0.1835.125/</a> <a href="30.0.1835.52/">30.0.1835.52/</a> <a href="30.0.1835.59/">30.0.1835.59/</a> <a href="30.0.1835.88/">30.0.1835.88/</a> The goal is to get the bottommost 3-digit-build version number if it exists and starts with .*<a href="([\d\.]{9})\. (== 30.0.1835 in this case), otherwise to get the bottommost 2-digit one. I've tried regexp methods alongside with Ketarin's functions and variables to no avail. There are many other sources for the version number, but I'm curious if there is a solution? I wanted to use a possessive quantifier (something like {ver}\.\d{2,3}+, where {ver}=30.0.1835, but it seems not supported by Ketarin. I will appreciate any suggestions. Thanks in advance!
  10. Hello! I've made a different Ketarin installation and noticed that imported (from online DB) application profile neither updates nor asks for it, even if I change the origin's name/variables in the main installation. However, the corresponding online db entry is updated as I press OK. Of course, in the origin installation I am able to freely turn on/off "share" checkbox. I remember I got messages like "Online app profile has been updated, would you like to update yours?" a long time ago. Is it broken atm? I care about possible subscribers aren't able to get the updated profiles. Regards.
  • 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.