FDM 3.9.4 4i5e1k

[D. Yessa]

I suggest to you all if don't want to bother wasting your time, just let Total Uninstall does it for you.

But don't forget to report bugs here. If you need an uninstaller to make FDM work, then it's a bug.

[Usher]

wait a few days until the extension updates automatically.

Could you explain it more detaily?
I have many times explained why the extension should NOT be distributed separately as a standalone (it does NOT work standalone). Are you going to fix FDM updates?

[Usher]

The lines you want to ignore contain wrong version number. It's not 30a, it is 30.0a, for example see filename for current 30 beta "Firefox Setup 30.0b3.exe".

Will you attach the version numbers to the fdminst.exe in the future release?It's hard to find out the small updates such as 1472 and 1472 with extensions 1.6.0.7

I am only a FDM , not a developer, and I have already warned about problems with FDM versioning. In my opinion it should be bumped all FDM build, not only FDM plugin version.

[Usher]

Did not know the new version was 1.6.0.7. It still showed 1.6.0.6 for me. Had to remove the Firefox Extension then reinstall the FDM for it to show up. Could this be looked into and fix in the next version. For now the work around will be to remove the extension and then install the new version of FDM. Thanks for the heads up on the new version extension.

It was already made OK, but this change was reverted for unknown reasons. See step 8B in FDM FAQ for Firefox troubleshooting.

[Usher]

I never got any trouble in updating FDM because I always do uninstall with Total Uninstall. It will remove all single files and registries without any traces. I never uninstall using Windows uninstaller.

It's overkill. FDM developers follow Microsoft guidances for programmers and try to keep files and make changes where they are supposed to be. FDM uses well behaved Inno Setup to create installer so you don't need to use any cleaner, if developers don't make any error when fixing bug issues and you don't mess with FDM files.

I suggest to you all if don't want to bother wasting your time, just let Total Uninstall does it for you.

I suggest to NOT use Total Uninstall to remove all FDM service files and registry entries if you don't want to lose your s and waste your time for reconfiguring FDM again and again.

[Usher]

Now some bug report follows for current FDM build (1472 with 1.6.0.7):
1. FDM does NOT remove [email protected] file from Firefox profiles when turning off monitoring. That way Firefox still see FDM plugin active and you must disable/remove it manually in the browser.
2. FDM plugin for Firefox is still buggy:
- There are missing 2 lines for oldest Firefox versions in chrome.manifest:

Code: Select all

interfaces components/ivmsfdmff.xpt appversion<22
binary-component components/vmsfdmff.dll appversion<22

Some people still use Firefox 3.6 or 4 on their old PCs, some corporate s still use Firefox 17 ESR.
- There is still old, duplicated and unneeded chrome.manifest in components subdirectory.
- There still may be problems with proper FDM plugin in Firefox. If the path in [email protected] is unchanged, Firefox may not properly recognize the plugin version change and use old plugin components kept in Firefox startup cache.
3. There are inconsistent and different versions of context menu options, though they all seemed to be shortened in some older FDM version, if I correctly.
4. There are problems with history longer than 255 (?) entries. In this case there is garbage shown in Site Manager: temporary entries for current/history s are shown twice - before and after persistent entries. The first occurance is phantom and should not be edited/deleted, if you don't want to break FDM service files.

[Guest]

2. FDM plugin for Firefox is still buggy:
- There are missing 2 lines for oldest Firefox versions in chrome.manifest:

Code: Select all

interfaces components/ivmsfdmff.xpt appversion<22
binary-component components/vmsfdmff.dll appversion<22

these lines are not needed now for Firefox, because now is just:

Code: Select all

interfaces components/ivmsfdmff22.xpt appversion<30a
binary-component components/vmsfdmff22.dll appversion<30a

which mean, for Firefox v1.x to Firefox 29.x.

[Usher]

2. FDM plugin for Firefox is still buggy:
- There are missing 2 lines for oldest Firefox versions in chrome.manifest:

Code: Select all

interfaces components/ivmsfdmff.xpt appversion<22
binary-component components/vmsfdmff.dll appversion<22

these lines are not needed now for Firefox, because now is just:

Code: Select all

interfaces components/ivmsfdmff22.xpt appversion<30a
binary-component components/vmsfdmff22.dll appversion<30a

which mean, for Firefox v1.x to Firefox 29.x.

These lines are NOT just duplicated. Can you see that these lines contain different file names? Can you check that these files are really different? Do you know why they are different?

Do you know about changes introduced in Firefox 22 beta and 23 alpha?
Could you read older topics before posting, please? You can start here:
viewtopic.php?f=1&t=16172&start=45#p37005
viewtopic.php?f=1&t=16172&start=45#p37077

Have you tested current FDM build with Firefox 17 ESR or any older Firefox version? If it works OK, then developers should remove both ivmsfdmff.xpt and vmsfdmff.dll files, not only their description in manifest.

[Wihan Tan]

I suggest to you all if don't want to bother wasting your time, just let Total Uninstall does it for you.

I suggest to NOT use Total Uninstall to remove all FDM service files and registry entries if you don't want to lose your s and waste your time for reconfiguring FDM again and again.

That's not problem for me at least because I always did to finish all my s before using Total Uninstall. Also I wrote down the configuration settings in a paper so I got no problem in reconfiguring

[l.inc]

Good day. Could someone point me to the up to date source codes? The svn repository linked on the page was last modified in September 2013.

[Great update]

Thanks for this new update. I found in chrome what it's important for me chrome://plugins/ Always allowed

But, in chrome, freemanager not .msi file. Exe files not problems...

[D. Yessa]

But, in chrome, freemanager not .msi file. Exe files not problems...

Give a link example please. I've tried a few (e.g.) - it works.

Latest FDM Chrome extension v.1.0.7 (see chrome://extensions).
If you have an older version:
- you can update it manually: turn on "Developer mode" tick (chrome://extensions at top right), then click "Update extensions now";
- or, Chrome will update the extension automatically in a few days.

[Guest]

3.9.4 build 1472 with Firefox Extension ver.1.6.0.7 (2014-05-10)

Still have version 1.6.0.6

Not updated

Isn´t working

[Usher]

3.9.4 build 1472 with Firefox Extension ver.1.6.0.7 (2014-05-10)
Still have version 1.6.0.6
Not updated
Isn´t working

Read the FDM FAQ for Firefox troubleshooting, please.

[parkd1]

I all I did to get the new version was to remove the Firefox Extension and reinstall FDM and it install the new Firefox Extension. Give that a try.