Switch from FF 32-bit to FF 64-bit

[Manheim2]

I have been using Win32 Firefox forever. My question is: can I switch to Win64 Firefox without it causing any issues with my many bookmarks? I use Windows 10 Pro which is a 64-bit operating system and feel it's time to move to Win64 Firefox if it won't block and/or delete my bookmarks.

[Brummelchen]

uninstall current firefox, then reinstall desired build - this wont affect your profile(s)
https://www.mozilla.org/en-US/firefox/all/
but i would wait a day or two - firefox 58 is upcoming now. create a backup of current profile (which is recommended, regularly)

[BuddhaNature]

Your bookmarks should be fine on the switch. However, do make a backup of your profile before switching. If run into problems with your bookmarks after the switch then this thread is worth reading: [Solved] Problem Moving Profile from v56 to v57 In fact, I'd say read that thread before making the switch - you'll be informed ahead of potential pitfalls, all of with can be got round of course.

[Manheim2]

Brummelchen and BuddhaNature: thanks for your help. I successfully updated to Firefox ESR 52.6.0 (64-bit) without any issues or loss of my bookmarks.

[Brummelchen]

ofc i first missed you are using ESR
https://www.mozilla.org/en-US/firefox/o ... tions/all/

please remember that 52.6 is not official released, but the chance that the current build is no longer changed is high.

[Manheim2]

Brummelchen : going to https://ftp.mozilla.org/pub/firefox/releases seems to indicate that 52.6.0 ESR was officially released as of 19-Jan-2018 at 18:08 hours unless I'm reading it incorrectly. Anyway, it seems that the current build appears to be working properly with all my Bookmarks showing correctly.

[therube]

(It may be there physically, but it has not actually been "released", yet.)

[James]

Brummelchen : going to https://ftp.mozilla.org/pub/firefox/releases seems to indicate that 52.6.0 ESR was officially released as of 19-Jan-2018 at 18:08 hours unless I'm reading it incorrectly. Anyway, it seems that the current build appears to be working properly with all my Bookmarks showing correctly.

They need to list it there before they actually officially Release it right ;) Back when releases.mozilla.org mirrors was being used (before the CDN they use now) they had to list the Release even earlier on for the mirrors to get it and host it. So many unofficial download sites jumped the gun days early back then.

January 23 PST (in morning) is the Release date unless there is a delay or needing to be pulled as it can happen.

[Brummelchen]

to notice - there exist NO ftp.mozilla.org any longer since years.
its all archive.mozilla.org. and its a cdn farm, not a single one.

[James]

to notice - there exist NO ftp.mozilla.org any longer since years.
its all archive.mozilla.org. and its a cdn farm, not a single one.

http://ftp.mozilla.org/ and https://ftp.mozilla.org/ are still very much alive and archive.mozilla.org is not the only place as there are links like https://download.cdn.mozilla.net/ and I did not say the CDN was a single one.

You may be thinking of the ftp:// protocol which was turned off since Aug 5, 2015. Mozilla had a blog post about this change back in 2015 but removed it sometime back.

[Brummelchen]

trust me - sören hentzschel announced that http://ftp... is dead and redirected. i know that ftp:// is closed a decade ago.
https://www.soeren-hentzschel.at/firefo ... ichnis-ab/ (german article)

[therube]

Mozilla "ftp" is (long) dead .
But the "http" link with the word "ftp" in its URL is perfectly valid.

Code: Select all

 ftp://ftp.mozilla.org/ is an "ftp:"  site, & is dead
http://ftp.mozilla.org/ is an "http:" site, & is alive

Code: Select all

 ftp://ftp.adobe.com/, is valid, an actual ftp:  site
http://www.adobe.com/, is valid, an actual http: site

Note that typing "ftp.adobe.com" into the URLbar takes you to (rolls over to) http://download.adobe.com/ - because you did not tell it to use the ftp: protocol. (You told it to use the http: protocol. The URI you entered simply happened to have the characters "ftp" in its' name.)

[Brummelchen]

listen man - i did NOT wrote that http://ftp.mopzilla.org is not valid.
i wrote - and he wrote - that this server address is redirected to archive.mozilla.org which is the only valid server farm behind.

and ofc ftp://ftp was the ftp address of http://ftp.mopzilla.org but mozilla stopped it, whyever, i dont care.

[James]

trust me - sören hentzschel announced that http://ftp... is dead and redirected. i know that ftp:// is closed a decade ago.
https://www.soeren-hentzschel.at/firefo ... ichnis-ab/ (german article)

You misunderstood. Your article mentions the "FTP access (ftp://ftp.mozilla.org) is no longer possible since the beginning of August" (which was in 2015). Google English translation "Instead, explicitly enter "https://ftp.mozilla.org" or "http://ftp.mozilla.org" in the address bar. Although this URL will continue to work, users accessing the directory in the browser should instead use the https://archive.mozilla.org link in the future". If you translated this as http://ftp.mozilla.org will redierect to http://archive.mozilla.org then there is your problem.

The article you linked to was taking information from https://blog.mozilla.org/it/2015/07/27/ ... e-impacts/ which I would have linked to earlier to back my comments up but the blog post was removed some months ago.

Found article in Wayback Machine
https://web.archive.org/web/20161006070 ... e-impacts/

After 8/5/15, ftp protocol support for ftp.mozilla.org will be completely disabled and downloads can only be accessed through http/https.

Users will no longer be able to just enter “ftp.mozilla.org” into their browser, because this action defaults to the ftp protocol. Going forward, users should start using archive.mozilla.org. The old name will still work but needs to be entered in your browser as https://ftp.mozilla.org/

So nothing about redirecting https://ftp.mozilla.org to archive.mozilla.org and typing in ftp.mozilla.org in Location bar just loads http://ftp.mozilla.org/

[Brummelchen]

anyhow, its the same server farm
https://myip.ms/info/whois/13.32.219.252 (1200 12Th Avenue South, Seattle, WA, 98144, US)
https://myip.ms/info/whois/52.85.178.51 (1200 12Th Avenue South, Seattle, WA, 98144, US)

the funny thing is that when sometimes i relaod the address it may possible to get different results. this is due the load balancing when servers are going to be filled/synced in special while creating the different language builds. you can see the list growing.