FDM 3.9.4 4i5e1k

[Guest]

The people who uses Firefox 29.0.1 or 24.5.0ESR should do the following steps.

1)Open your FDM installdir (default is C:\Free Manager\)

2)Find Firefox\extension\chrome.manifest

3)Edit it with notepad.exe or other text-edit tools.you can just copy and paste the follow codes to overwrite the original ones

Code: Select all

content fdm_ffext chrome/content/

overlay chrome://browser/content/browser.xul chrome://fdm_ffext/content/fdm_ffext.xul
overlay   chrome://mozapps/content/s/unknownContentType.xul chrome://fdm_ffext/content/fdm_ffextDM.xul

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

interfaces components/ivmsfdmff22.xpt appversion>=22 appversion<30
binary-component components/vmsfdmff22.dll appversion>=22 appversion<30

interfaces components/ivmsfdmff30.xpt appversion>=30a
binary-component components/vmsfdmff30.dll appversion>=30a

4)Restart Firefox(or just start up Firefox) FDM extension work again.


PS:Sorry Usher for the rude reply again.

[Guest]

I've found a chrome.manifest and .aotureg in FDM installdir\Firefox\extension\components.

The chrome.manifest has the same contents with the one we've edited.It seems to be useless,even without it, FDM extension works fine.

But I don't know about the .aotureg file.I've also deleted it,and found FDM extension still works fine.

[Guest]

I wonder that Line 9 should be

Code: Select all

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

See https://developer.mozilla.org/en-US/docs/Chrome_Registration .

Multiple appversion flags may be included on a single line, in which case the line is applied if any of the flags match.

Your proposed code matches all versions (appversion<30 or appversion>22).

[MELERIX]

for Firefox 29.0.1 you only need to modify two lines:

C:\Program Files\Free Manager\Firefox\extensión\chrome.manifest

Code: Select all

interfaces components/ivmsfdmff22.xpt appversion>=22 appversion<30
binary-component components/vmsfdmff22.dll appversion>=22 appversion<30

[Guest]

I wonder that Line 9 should be

Code: Select all

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

See https://developer.mozilla.org/en-US/docs/Chrome_Registration .

Multiple appversion flags may be included on a single line, in which case the line is applied if any of the flags match.

Your proposed code matches all versions (appversion<30 or appversion>22).

You just don't know about a single line do you?

[Guest]

I wonder that Line 9 should be

Code: Select all

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

See https://developer.mozilla.org/en-US/docs/Chrome_Registration .

Multiple appversion flags may be included on a single line, in which case the line is applied if any of the flags match.

Your proposed code matches all versions (appversion<30 or appversion>22).

You just don't know about a single line do you?

Your interpretation is wrong.
First single line:

Code: Select all

interfaces components/ivmsfdmff22.xpt appversion<30 appversion>22

Second single line:

Code: Select all

binary-component components/vmsfdmff22.dll appversion<30 appversion>22

"appversion<30 appversion>22" is not "appversion<30 AND appversion>22" but "appversion<30 OR appversion>22".

[Usher]

for Firefox 29.0.1 you only need to modify two lines:

C:\Program Files\Free Manager\Firefox\extensión\chrome.manifest

Code: Select all

interfaces components/ivmsfdmff22.xpt appversion>=22 appversion<30
binary-component components/vmsfdmff22.dll appversion>=22 appversion<30

Wrong. These lines are already eplained in other postings.
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".

Do not post any UNTESTED proposition and stop ranting in many topics, please.

[Usher]

I've found a chrome.manifest and .aotureg in FDM installdir\Firefox\extension\components

Do NOT play with files if you don't understand their names. It is .autoreg as extension AUTOMATIC REGISTRATION.

But I don't know about the .aotureg file.I've also deleted it,and found FDM extension still works fine.

You will probably complain when you want to use a new Firefox profile.

[Guest]

New Firefox Extension ver.1.6.0.7 is released. (It is included in FDM newly ed from http://www.freemanager.cinevost.com/.htm )
1.6.0.7 works fine with Firefox 29.0.1.

Thank you.

[ddn2003]

Please add for Maxthon!!!

[parkd1]

New Firefox Extension ver.1.6.0.7 is released. (It is included in FDM newly ed from http://www.freemanager.cinevost.com/.htm )
1.6.0.7 works fine with Firefox 29.0.1.

Thank you.

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.

[Guest]

for Firefox 29.0.1 you only need to modify two lines:

C:\Program Files\Free Manager\Firefox\extensión\chrome.manifest

Code: Select all

interfaces components/ivmsfdmff22.xpt appversion>=22 appversion<30
binary-component components/vmsfdmff22.dll appversion>=22 appversion<30

Wrong. These lines are already eplained in other postings.
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".

Do not post any UNTESTED proposition and stop ranting in many topics, please.

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

[Guest]

I've found a chrome.manifest and .aotureg in FDM installdir\Firefox\extension\components

Do NOT play with files if you don't understand their names. It is .autoreg as extension AUTOMATIC REGISTRATION.

But I don't know about the .aotureg file.I've also deleted it,and found FDM extension still works fine.

You will probably complain when you want to use a new Firefox profile.

X:\Free Manager\Firefox\extension\components\chrome.manifest

This manifest file is still the same with 1.6.0.6, oops?

[D. Yessa]

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.

Seems like you didn't need to remove extension. Simply reinstall FDM from here or wait a few days until the extension updates automatically.

[Wihan Tan]

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.

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