On 12/30/2014 12:38 AM, Ray_Net wrote: > NoOp wrote on 30/12/2014 02:52: >> On 12/28/2014 09:41 PM, HenriK wrote: >>> Thanks to all who commented. Unfortunately, I don't think I stated my >>> concerns >>> very carefully. >>> >>> My existing SM 2.24 is installed in a different hard drive partition (F) >>> than >>> the operating system (C). I seem to remember that picking a new copy of SM >>> will >>> try to install it only in the C partition. >>> >>> Is that correct or will pulling a copy of the v.2.30 installation file out >>> of >>> the SM version list successfully overwrite the files in my v.2.24 existing >>> installation without raising havoc with the existing profiles, mail >>> location, etc. >>> >>> If something goes terribly wrong, where are the instructions these days on >>> installing SM in a HD partition of a user's choice? >>> >>> Thanks, in advance, for any and all advice and assistance. >>> >>> >>> HenriK wrote: >>>> Is there someway to update an existing and older version of SM to a newer >>>> version other than the latest version? >>>> >>>> I want to go from v.2.24 to v.2.30 without changing anything else. The >>>> update >>>> screen appears to only allow going to the latest version, v.2.31, >>>> something I >>>> don't want to do at this time. >>>> >>>> Thanks, in advance, for any and all advice and assistance. >> <http://www.seamonkey-project.org/doc/install-and-uninstall> >> >> Download the zip file, extract to where you want to run it from, extract >> it, and double-click seamonkey.exe. It will open up to your existing >> profile. If not, then you adjust/move your profile: >> <http://kb.mozillazine.org/Moving_your_profile_folder> >> >> > He can download the exe file without going thru a zip file extraction :-)
Well yes of course he can. However, the .exe file is an installer file & if he merely wants to run SeaMonkey from a different partition, folder, drive, etc., then the easiest & obvious way is to simply extract the zip file to whatever folder/directory you want to run it from. Perhaps you should take time to read: <http://www.seamonkey-project.org/doc/install-and-uninstall> "To install SeaMonkey by downloading the .zip file and installing manually, follow these steps (normal users should NOT do that but use the installer as described above): " > > The 2.30 version can be found here: > http://www.seamonkey-project.org/releases/2.30 > Sure it is... but that won't provide the zip file. Instead try: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/ http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/ http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.30/ http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.30/win32/ "Warning! The SeaMonkey version available for download from this page is outdated and may suffer from known security vulnerabilities. This page is only available for historic reference. We strongly advise you to download the current release instead. " But why the OP wants to use 2.30 instead of 2.31 is beyond me: "SeaMonkey 2.30 Released October 15, 2014 Warning! The SeaMonkey version available for download from this page is outdated and may suffer from known security vulnerabilities. This page is only available for historic reference. We strongly advise you to download the current release instead. " https://www.mozilla.org/en-US/security/known-vulnerabilities/seamonkey/ Fixed in SeaMonkey 2.31 2014-91 Privileged access to security wrapped protected objects 2014-89 Bad casting from the BasicThebesLayer to BasicContainerLayer 2014-88 Buffer overflow while parsing media content 2014-87 Use-after-free during HTML5 parsing 2014-86 CSP leaks redirect data via violation reports 2014-85 XMLHttpRequest crashes with some input streams 2014-84 XBL bindings accessible via improper CSS declarations 2014-83 Miscellaneous memory safety hazards (rv:34.0 / rv:31.3) Three of those fixes are rated as *Critical*. For those that don't bother with security, *Critical* is: "Vulnerability can be used to run attacker code and install software, requiring no user interaction beyond normal browsing. " And for the record & for those that seem to think staying with SeaMonkey 2.26.1 is OK: # Fixed in SeaMonkey 2.30 2014-81 Inconsistent video sharing within iframe 2014-80 Key pinning bypasses 2014-79 Use-after-free interacting with text directionality 2014-78 Further uninitialized memory use during GIF rendering 2014-77 Out-of-bounds write with WebM video 2014-76 Web Audio memory corruption issues with custom waveforms 2014-75 Buffer overflow during CSS manipulation 2014-74 Miscellaneous memory safety hazards (rv:33.0 / rv:31.2) # Fixed in SeaMonkey 2.29.1 2014-73 RSA Signature Forgery in NSS # Fixed in SeaMonkey 2.29 2014-72 Use-after-free setting text directionality 2014-71 Profile directory file access through file: protocol 2014-70 Out-of-bounds read in Web Audio audio timeline 2014-69 Uninitialized memory use during GIF rendering 2014-68 Use-after-free during DOM interactions with SVG 2014-67 Miscellaneous memory safety hazards (rv:32.0 / rv:31.1 / rv:24.8) There are *ten* (10) *Critical* security fixes in those releases (you'll have to visit the link to see which ones). So y'all just keep on using 2.30 or 2.26.1 for whatever reason, but I'd much rather use security patched code than hold out for "Password Manager Fails to Fill-In Password When autocomplete=off"... et al. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
