Jump to content

VistaLover

Member
 View Profile  See their activity

  • Posts

    2,245

  • Joined

  • Last visited

  • Days Won

    93

  • Donations

    0.00 USD 

  • Country

    Greece

 Content Type 

Everything posted by VistaLover

  1. VistaLover
    @foxzzy First, I want to welcome you to the MSFN forums ... However, and any forum admin will probably agree with me, it's not polite or even compliant with forum rules to have your second post be a slightly reworded version of your first one, asking about the exact same thing... You made your first post here: <thread link invalidated because of thread merge: it's the 1st post on this thread, now> and @Mathwiz was kind enough to provide you with links to the main MSE thread, where your query should have been answered, beyond any doubt... Did you ever bother reading the relevant posts (found in the "last-ish" thread pages...) ? You obviously didn't like the answer you received and you opted to come back with this duplicate query/thread... This is a real faux pas... MSE/XP is dead; first, M$ made its engine non-XP compatible; an interim mitigation was applied, but the final end was imminent: M$ also changed the "format" (for lack of a better term) of the actual definitions to be only compatible with the updated (non-XP compatible) engine; any attempt to patch those files will invalidate their file signatures/HASHes and render them "corrupt", unable to be used even with the old engine... What you're asking is for someone to deeply patch official Microsoft files (both engine DLL and definition files); even if some able person manages this, it wouldn't be allowed to post here "hacked" Microsoft files... FWIW, MSE is kept going by M$ only for the sake of Windows 7 (and they are being gracious to those few Vista users, too); once Win7 reaches EoS in several months, the future is unclear for "legacy" MSE (replaced by updated WD in Win8+)...
  2. VistaLover
    Vista SP2 users can manually install provided patch(es) for WS2008SP2: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0948 https://support.microsoft.com/en-us/help/4503273/windows-server-2008-update-kb4503273 https://support.microsoft.com/en-us/help/4503287/windows-server-2008-update-kb4503287
  3. VistaLover
    Welcome to the MSFN forums Might I ask what this tutorial is all about? Since WD is a native/integral Windows OS feature first introduced in Vista (IIANM, on XP is a standalone/separate download...), perhaps posting it on the main Windows Vista forum looks appropriate ; but a forum admin may think otherwise...
  4. VistaLover
    ... Extremely grateful to you on both counts...
  5. VistaLover
    I can definitely report that on my 11 year old Vista SP2 32-bit install (with WS2008 updates up to Oct 2017 and .NET FW 4.6.1 manually installed), the app completes the scan successfully: I'd be much obliged if you forwarded this to your Malwarebytes connections/devs, so they could hopefully be prevented from taking a lighthearted and quick decision, based solely on one reported "issue"; we understand (but certainly not approve...) they don't want to support Vista anymore, but they should not artificially block the software from running on "compatible" (?) Vista configurations: If it works, don't break it! If it doesn't work to begin with, no support should be requested; then everyone's happy... Thanks in advance for alerting the Malwarebytes people... PS: Just a thought/question of mine I wanted to publicly voice: Why is it that "Security/Anti-Malware" software decide to jump the boat once dear ol' Microsoft terminates "official" support for one of their OSes? A sane, everyday, person would think that such software is rendered all the more necessary on said OS (one the vendor stopped patching); just look at what happened with XP: M$ killed for good its MSE solution, so die-hard XP users turned to third party paid apps still supporting XP (which means added profit for the authors of these apps...); but the conspiracy-theorist inside me mumbles that M$ actually bribes those third-party app authors to discontinue support, in order for Windows users to be forced to cough up their hard-earned money towards new hardware+WinOS...
  6. VistaLover
    This is not true: if by "official" site you mean https://noscript.net/ then change to the "get it!' tab and scroll down a bit:
  7. VistaLover
    ... by described behaviour you mean: From my 7.3.0 scan log, you can see that 27501 objects were scanned: # ------------------------------- # Malwarebytes AdwCleaner 7.3.0.0 # ------------------------------- # Build: 04-04-2019 # Database: 2019-05-27.1 (Cloud) # Support: https://www.malwarebytes.com/support # # ------------------------------- # Mode: Scan # ------------------------------- # Start: 06-13-2019 # Duration: 00:00:40 # OS: Windows Vista (TM) Home Premium # Scanned: 27501 # Detected: 39 As said already, I haven't moved on to "Clean & Repair", so am not in a position to verify it properly removes a selected "flag" (but I might experiment with when spare time permits...). ... We here at the Vista subforums really hate it when app authors impose artificial blocks to their setups/executables and cripple them on our favourite OS, Vista; I hope the devs review their decision by actually testing themselves on the OS, even without officially supporting it... You appear to be running Win10, have you yourself tested latest version 7.3.0 on Vista? I apologise for being a pest...
  8. VistaLover
    You seem to know a lot more about this program than my humble self, so am not questioning the validity of what you posted ; however, I conducted a simple test: I launched v6.047 (after declining the prompt to update it...), and then went through its settings to configure it to my liking; then I initiated a scan: granted it took slightly more time to complete the scan (but that may be due to its older engine), but in the end it found exactly the same Folders, Scheduled Tasks and Registry entries as version 7.3.0 did! I never proceeded to the "Clean" action in either version (at least not without first creating a System Restore point), as most "flags" were actually identified by me to be false positives (many related to Chinese browser UCBrowser... ) Regards
  9. VistaLover
    This doesn't appear to be true ; I have just downloaded version 7.2.6.0 from the repository you linked to, it had no issue launching, furthermore it prompted me to update it to latest version 7.3.0.0; the update went along fine, I have it successfully running here: So, while it is not officially supported anymore on XP/Vista, as per your link: latest version 7.3 appears to be functioning fine, at least on Vista SP2 (with .NET FW 4.6.1, if that matters at all)... Official download page: https://toolslib.net/downloads/viewdownload/1-adwcleaner/files/1920/ On-line documentation: https://toolslib.net/downloads/viewdownload/1-adwcleaner/pages/5-en-adwcleaner-documentation/ Off-line user guide (for v7.2.4): https://www.malwarebytes.com/pdf/guides/Malwarebytes-AdwCleaner-User-Guide.pdf OT: Doesn't it strike you as odd that Vista had more usage percentage at the time support was officially dropped than Windows XP?
  10. VistaLover
    To be frank, I don't think they ever intended this for a massive consumption outside of mainland China; their site does provide rudimentary English localisation and the app, once installed, does have the option of a (poorly translated) English locale, but, beyond that, the browser is heavily China-centered (pre-installed Chinese search engines, default links to their own proprietary extensions store*, NPAPI+PPAPI flash [older version 29] downloaded straight from Chinese servers[IIRC, these are specially modified versions to allow better user tracking by the regime ], pre-installed Quick Dial with popular Chinese sites, support forum in Chinese only, etc., etc.)... What little English support exists is probably targeting foreigners already in China, for whatever reasons... Just my 2c, of course (*): While you can install most extensions directly from the official Google Store when you're outside of China, do note that the installed extensions can't access it for update checks, so no auto-update for said extensions is possible ; for those ones that have such a feature, you should first export to file their configuration/settings, uninstall the outdated version and then install from Google Store the updated version (unlike addons.mozilla.org, Google don't offer previous versions of an extension, and the new, updated, version can't be installed on top of the outdated one, retaining already existing configuration ); finally, import previous settings from file...
  11. VistaLover
    ... Actually, stable build v1.1.453.59 has a digital signature of 2016-05-13 and is built on slightly fresher Chromium source (50.0.2661.102), whereas dev build v1.2.470.11 has a digital signature of 2016-05-04 and is built on older Chromium source (50.0.2661.89); so the snapshot build you're after is not more recent than the stable one I posted a link to... ... Yes, but only in (unsigned) ZIP format (which means you'll have to enable developer mode in vivaldi://extensions and install from unpacked folder; or, create yourself a .CRX file from within Vivaldi and permanently install that way... ). ... Knock yourself out Vivaldi.1.2.470.11.exe https://www15.zippyshare.com/v/bNiTojuc/file.html (Link availability at the discretion of forum admins... )
  12. VistaLover
    @artomberus ... Actually, the very last build of Vivaldi on the stable (release) branch that would run on Vista SP2 is 1.1.453.59, based on Chromium 50.0.2661.102 source code: The screengrab is actually from an unofficial portable installation (in PAF format); search for it on the web... Official link to the v1.1.453.59 (32-bit) installer: https://downloads.vivaldi.com/stable/Vivaldi.1.1.453.59.exe The very last build of Vivaldi on the snapshot (dev) channel that would run on Vista SP2 was indeed 1.2.470.11, based on Chromium 50.0.2661.89 source code: (... again, this is a portable installation in PAF format). The relevant vivaldi blog entry is: https://vivaldi.com/blog/snapshots/snapshot-1-2-470-11-editable-gestures-2/ but, as you found out, ALL binary links are 404'ed now... TBH, both builds date to May 2016, which means they are probably unsafe to browse today's web with, not to mention that many sites have dropped long ago Chromium 50 compatibility; YMMV, but poor site/page rendering is highly probable ; if you plan to install uB0, 1.16.18/1.16.20 is the last one (but hard to find as a .CRX file) that successfully works with those old builds... I only have on disk the 32-bit version of Vivaldi 1.2.470.11[dev] (file Vivaldi.1.2.470.11.exe, dig. sig. of Wed, May 4th 2016, 17:08:01), but I am unsure as to whether I am allowed to share it here... Don't have time currently to search exhaustively for an archived link for it (sadly, web.archive.org doesn't appear to have salvaged it )...
  13. VistaLover
    That's probably because your system lacks Eastern Asian Fonts (Chinese, Korean, Japanese, etc...); not saying you'd be able to understand the messages in Chinese (displayed by the installer) had you got them installed... Perhaps a native Chinese speaker could create an installation guide with screenshots for those wanting to install this Chinese Chromium 69 fork (myself, I'm using a Russian-made portable version in WinPenPack format, just search for it on line as it's not allowed here on MSFN to post links to "unofficial" packages... ).
  14. VistaLover
    ... As posted elsewhere, 45.9.0esr was the last 45esr version officially released by Mozilla (mid-April 2017): https://ftp.mozilla.org/pub/firefox/releases/45.9.0esr/win32/it/ 45.0esr (very similar to stable 45.0) was from March 2016; during an ESR branch update cycle, only security updates, chemspills (urgently needed fixes for various breakages) and some quality/performance updates are being backported from the main (stable/release) Firefox branch (with higher major version numbers...); system/CPU requirements don't change in the middle of an ESR cycle, when they do, it's always beginning with the next ESR cycle; e.g. all 45.x.xESR builds will run on max-SSE processors, none of the 52.x.xESR cycle will (likewise, all 52.x.xESR builds will run on XP/Vista, but none of the 60.x.xESR cycle will ) Simply put, 45.9.0esr has more than a year's worth of publicly disclosed security vulnerabilities patched; as to whether those put a perceivable dent to the whole browser performance, as suggested, I can't comment really ; test on your own particular setup and decide for yourself; if you ask me, though, I'd go for safer...
  15. VistaLover
    ... You "sound" surprised ; if you please read more carefully previous posts in this thread and/or inspect related commits in Roytam1's GitHub repository (as the result of Mathwiz's PRs), you'd realise ONLY NM28/UXP and (some of) Serpent52/UXP "Help" entries were altered... If, OTOH, you are truly asking for Mail News's "Help" entries to be modified, that's a different matter; AFAICT, @roytam1 hasn't published a forked Binary Outcast GitHub repository (unlike his UXP one!) one can then re-fork and submit the necessary PR... He, of course, can do this in his local BO repo, if he agrees to your requests... NB: I am NOT a user of any of the BO forks (nor will I choose to be )...
  16. VistaLover
    Actually, this is NOT accurate; Avast does provide 19.x versions of their Free Antivirus flavour; e.g. if you navigate to https://www.avast.com/download-thank-you.php?product=FAV-AVAST&locale=en-gb you will end up downloading from: https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_FULL/build_RELEASE which, once on disk (337 MB, off-line setup), can be verified to be of file version 19.4.4318.0. But versions 19.x require Win7+, the version you have installed (18.8) is the last supported one on Vista/Server2008 ... Cheers
  17. VistaLover
    ... I understand this was a change implemented on a platform level, so I'm not sure as to if/how what I suggest below is feasible, but what would be best, IMHO, is to implement the upstream change ONLY to New Moon (application/palemoon) and NOT implement it on Serpent (application/basilisk); removing the "force-enable e10s" feature on NM should be favourable, because force-enabling e10s on PM/NM, even for testing purposes, will produce a totally broken/unresponsive browser (as the internal e10s supporting code is non-existent in PM/NM); just my 2 eurocents, of course
  18. VistaLover
    If you have access to a Win7+ computer, then consider installing KAF19 (Kaspersky AntiVirus Free) on your off-line XP machines ( as suggested by @BTTB ) and then use latest Kaspersky Update Utility on the on-line Win7+ machine to download latest KAF19 definitions: The "def" files can be then transferred to the XP machines via, e.g., a USB flash stick and then installed via a process probably detailed in the Kaspersky Support Site (or just Google/Bing/DDG for it ). EDIT: Support link => https://support.kaspersky.com/11705 Unfortunately, latest KUU v3.2.0.153 is build on Qt 5.8 framework, which requires Win7+ (thus, I can't test it here on Vista... ). EDIT2: Last XP+Vista compatible version of KUU is v3.1.0.25 (built on Qt 4.6); official download link (retrieved via web.archive.org ): updateutility_win_3.1.0.25_release_en.zip Once run for the first time, start an update to populate the "Applications" list with latest KAF entries...
  19. VistaLover
    @Mathwiz's PRs have been now merged into @roytam1's custom UXP branch, expect to see the changes landing in tomorrow's NM28/St52 builds... On another note, the few (?) of you running Serpent 52.9.0 in forced multiprocess (e10s) mode ( @Mathwiz, still doing this? ), will soon be unable to continue this practice, considering the upstream dev has patched that loophole: https://github.com/MoonchildProductions/UXP/issues/1130 https://github.com/MoonchildProductions/UXP/commit/19c0f5e
  20. VistaLover
    @TechnoRelic I have already made my position very clear in the matter at hand, in previous posts of this thread: I feel totally indifferent to the whole re-branding issue, in fact I am quite alright with how things were/are now; @roytam1 is NOT compiling builds with the official branding, this is crystal clear; the whole re-branding argument has been always pushed by MCP and/or Matt A. Tobin; I am not confused in any way as to what I am using on my Vista laptop currently ; I might sound harsh, but Roy is NOT to blame whenever some NM/Serpent user knocks on MCP's door; the fault lies, IMHO, solely on those users, who can't tell their right hand from their left one (and, as said already, full rebranding won't relieve MCP of random NM users and/or make them think about us - maintainer+users - in another way; for them, we'll always remain XP+Vista freaks ) ... The recent PRs by @Mathwiz were submitted after you have, apparently, taken sides with MCP/M.A.T in your recent post ; you have yourself appointed only myself and Mathwiz as the users who should be consulted about your "re-branding" expectations, but this leaves out numerous other NM/St users who might not be as vocal in the forums here, but their own opinion should also carry weight... Mathwiz created his PRs as an interim and "easy" solution, with the hopeful aim of deterring additional NM users from seeking support at MCP's HQs; twice you said "is FINE with me", but it now becomes apparent, even after the PRs have been created, that you won't feel satisfied unless a full rebranding takes place: in other words, in your own subtle way, you are coercing @roytam1 to proceed into full re-branding, echoing MCP/M.A.T 's agenda... Roy shouldn't be forced to make any additional efforts, he's working wonders as it is, regularly providing browser builds for a plethora of older OSes/platforms... And this is my final say on this...
  21. VistaLover
    Nope ; the correct official avast forum topic with links to both off-line/on-line installers is: https://forum.avast.com/index.php?topic=220639.0
  22. VistaLover
    This is a tough one to solve ; selecting in Serpent 52.9.0 "Help => Keyboard Shortcuts" is, code-wise, contained in: https://github.com/roytam1/UXP/blob/master/application/basilisk/base/content/baseMenuOverlay.xul#L55-L56 <menuitem id="menu_keyboardShortcuts" oncommand="openHelpLink('keyboard-shortcuts')" The code to execute the command is contained within: https://github.com/roytam1/UXP/blob/master/application/basilisk/base/content/utilityOverlay.js#L818-L823 function getHelpLinkURL(aHelpTopic) { var url = Components.classes["@mozilla.org/toolkit/URLFormatterService;1"] .getService(Components.interfaces.nsIURLFormatter) .formatURLPref("app.support.baseURL"); return url + aHelpTopic; } The default value for app.support.baseURL is https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/ so the URL returned is https://support.mozilla.org/1/firefox/52.9.0/WINNT/en-US/keyboard-shortcuts which then auto-redirects to https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly?redirectlocale=en-US&as=u&redirectslug=Keyboard+shortcuts&utm_source=inproduct ... As for the browser.slowstartup.help.url, I merely proposed what appeared to me as a simple (but functional) enough solution, provided @dencorso obliges ; but, since this is basically your PR and your call, you are free to proceed as you see fit...
  23. VistaLover
    ... And why would you not link to this very MSFN thread? It would be consistent with what is already displayed in @roytam1's binary repository: https://o.rths.cf/palemoon/?sort=date&order=desc Index of /palemoon/ Welcome to New Moon (a.k.a. Pale Moon fork targetting XP) binary directory. These projects have no affiliation with any upstream community code sources or organizations. Please direct all support or related questions to disscussion thread in msfn.org. So, my recommendation would be: app.support.baseURL;https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/ WRT http://www.palemoon.org/support/slowstartup.shtml , this is just an adaptation from the corresponding Firefox guide: https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up Admittedly, the PM page is better tailored to New Moon users, but, again, that page is copyrighted to MCP and has references to official app name, logo and support forum, so... Perhaps @dencorso can somehow transplant the following text: as second post to this very thread, then the URI to that post could be used as value of pref browser.slowstartup.help.url ( I am against this myself, but one can supposedly disable a "slow start-up" page from appearing by toggling pref: browser.slowStartup.notificationDisabled; this will disable the notification and the access to the support page ).
  24. VistaLover
    Thanks. I'll make the necessary fix and create another pull request, probably tonight. ... Have you looked at my own post on this subject?
  25. VistaLover

    MITM Checker

    VistaLover replied to a topic in Windows XP

    Latest version 0.49b 1. Has rectified the oversized/elongated app window 2. App window can now be minimised to taskbar 3. App window can't be maximised or resized 4. There is no more a right "sidebar", but the test result is being displayed in the bottom "status bar" 5. As with previous versions, 200 sample hosts are being checked against... I ran the app on my Vista SP2 32-bit old laptop (so can't tell whether it runs under XP SP3 ), 0 detections and 7 handshake failures here...
×
×
  • Create New...