FDM 5.1 40195q

[oroville]

It looks like you have reinstalled old FDM build rather than the newest one. You should turn off off the browser monitoring in FDM, uninstall it and only then install the newest build. Read carefully my older message: viewtopic.php?f=1&t=16047&start=600#p45786 if you have still problems.

I wish I had an explanation for that mystewrious addon update, but I have only been using the latest FDM v5.1.37 [build 7258] since May, The only installer I have is for that, and all the other profiles, which I created on the same day as the one with the problem, had the correct addon version. Not a big deal really. I just updated the addon manually. Wierd.

FDM is now integrated into Firefox, and shows in the context menu, but still no FDM toolbar button. Do you have the button?

[oroville]

I mentioned that I was "using the latest FDM v5.1.37 [build 7258] since May".

That's because the FDM "check for updates" link was telling me that FDM was up to date.

I have since updated to 5.1.37 [build 7274, but still no toolbar button.

[oroville]

I read your other thread, but I'm still confused about which addon version I should have.

The latest version of FDM comes with 3.0.11, but the addon versioin page has 3.0.27?

[Clive Sorensson]

I use the latest versions of both portable Firefox quantum beta 63.013b and portable Google Chrome.

I can install the FDM addons on both, the FDM button appears on the taskbars of each browser, but FDM doesn't appear on the context menu and wont capture anything unless I copy the url and manually add it in the FDM interface.

The FDM browser integration settings say Firefox and Chrome are not installed. I assume the problem is because of they portable.

I know that in the past there has been a history of issues with browser integration, but I have always used portable versions of Firefox, and it has worked with FDM.

Eagleget integrates and works with bot Firefox and Chrome and no problem.

It looks like the problem is in the latest portable version. We'll work on it.

[hajj_3]

Trying to right click on youtube videos in chrome and select with free manager does nothing.

chrome v70 x64 and 3.0.27 extension.

[Clive Sorensson]

Trying to right click on youtube videos in chrome and select with free manager does nothing.

chrome v70 x64 and 3.0.27 extension.

What do you mean by "does nothing"?

[hajj_3]

Trying to right click on youtube videos in chrome and select with free manager does nothing.

chrome v70 x64 and 3.0.27 extension.

What do you mean by "does nothing"?

nothing happens, free manager doesn't open and even if i manually open it a is not added to free manager either.

[abdulhkeem]

fdm has been acting up since yesterday using 12-15 u and eating ram even restarting the app does not help!

just found the culprit for this it has something to do with chrome 70 FDM acting normal when chrome is closed but will start eating ram+u when chrome is running the u goes to 0 with the addon disable though and ram eating happens when it uses u "stops when u usage is 0".

PS. please add export list it would help a lot as i once lost mine don't why though.

[Clive Sorensson]

fdm has been acting up since yesterday using 12-15 u and eating ram even restarting the app does not help!

just found the culprit for this it has something to do with chrome 70 FDM acting normal when chrome is closed but will start eating ram+u when chrome is running the u goes to 0 with the addon disable though and ram eating happens when it uses u "stops when u usage is 0".

PS. please add export list it would help a lot as i once lost mine don't why though.

Thank you for the report, we'll look into it.

[Clive Sorensson]

fdm has been acting up since yesterday using 12-15 u and eating ram even restarting the app does not help!

just found the culprit for this it has something to do with chrome 70 FDM acting normal when chrome is closed but will start eating ram+u when chrome is running the u goes to 0 with the addon disable though and ram eating happens when it uses u "stops when u usage is 0".

PS. please add export list it would help a lot as i once lost mine don't why though.

Could you specify your FDM version?

[johnlgalt]

I came back after a long while - still trying to see if server time was fixed.

Noticed something - - the previous versions of FDM that I have ed and archived are at fdm5_x86_setup.exe (I've naturally added more to the name to distinguish the different versions I have ed).

However, when I went to the current build, there are both X86 and X64 builds.

I've had the devil of a time with the server time feature being broken in every build I have attempted to install after 5.1.34 build 6924 (which is also an X86 installer).

Alex / Clive / devs / Usher / anyone, I'm probably going to be cleaning installing Windows 10 shortly. I have the current X64 installer for 5.1.37 build 7174 ed to give it a try, along with the X86 installer (I have a 64 bit OS, and most of the browsers I am running are explicitly 64bit as well, but I will try both arch installers on the clean install to see if server time is only broken on a specific arch install, something I never considered before). If it is still broken in 7174, can anyone link me to the X64 installer for 5.1.34 build 6924, please?

Actually, never mind - what would be better would be if the hashes for the last few builds we posted in the first post so that I can the file I found online is actually the correct installer....

Hashes for current build (both arch for Windows) as well as Hashes for both 5.1.34 build 6924 arch installers would be great, thanks in advance!

[abdulhkeem]

fdm has been acting up since yesterday using 12-15 u and eating ram even restarting the app does not help!

just found the culprit for this it has something to do with chrome 70 FDM acting normal when chrome is closed but will start eating ram+u when chrome is running the u goes to 0 with the addon disable though and ram eating happens when it uses u "stops when u usage is 0".

PS. please add export list it would help a lot as i once lost mine don't why though.

Could you specify your FDM version?

Version 5.1.37.7258 (48533e2)

[johnlgalt]

I came back after a long while - still trying to see if server time was fixed.

Noticed something - - the previous versions of FDM that I have ed and archived are at fdm5_x86_setup.exe (I've naturally added more to the name to distinguish the different versions I have ed).

However, when I went to the current build, there are both X86 and X64 builds.

I've had the devil of a time with the server time feature being broken in every build I have attempted to install after 5.1.34 build 6924 (which is also an X86 installer).

Alex / Clive / devs / Usher / anyone, I'm probably going to be cleaning installing Windows 10 shortly. I have the current X64 installer for 5.1.37 build 7174 ed to give it a try, along with the X86 installer (I have a 64 bit OS, and most of the browsers I am running are explicitly 64bit as well, but I will try both arch installers on the clean install to see if server time is only broken on a specific arch install, something I never considered before). If it is still broken in 7174, can anyone link me to the X64 installer for 5.1.34 build 6924, please?

Actually, never mind - what would be better would be if the hashes for the last few builds we posted in the first post so that I can the file I found online is actually the correct installer....

Hashes for current build (both arch for Windows) as well as Hashes for both 5.1.34 build 6924 arch installers would be great, thanks in advance!

Server time is still broken on current build. Reverting back to 6924 again.

[Usher]

Hashes for current build (both arch for Windows) as well as Hashes for both 5.1.34 build 6924 arch installers would be great, thanks in advance!

Why do you need hashes? Installers are exe files digitally signed with certificate issued for Softdeluxe Ltd. I think that if any people are able to change content of installers and keep this certificate, they for sure won't forget to change also hash values.
And you can also easy check the build version, as installer uses Inno setup. Just and use Inno Setup unpacker (search for innounp on Sourceforge) to unpack installer, then check the FDM exe version.

[johnlgalt]

I didn't inspect the installer closely, and didn't know those details.

It's mostly for file verification purposes - that what I DL is actually what I am supposed to have. As I've done for decades now.