Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

  • Days Won


VistaLover last won the day on March 16

VistaLover had the most liked content!

Community Reputation

65 Excellent

1 Follower

About VistaLover

Profile Information

  • OS
    Vista Home Premium x86
  • Country

Recent Profile Visitors

1,359 profile views
  1. Server 2008 Updates on Windows Vista

    I don't get it ... Why having KB4019478 already installed prevented you from installing KB4019276 ??? (Unless this is a typo, of course... ) In my case, I always let "Installed Updates" completely finish populating the relevant entries, which can take a while on my system, and only then proceed with typing in the search bar the update ID, always including the KB characters (i.e. a search for KB4019276 will succeed, but a search for just 4019276 will fail! ) BTW, @JohnRichardTLH and @mike_shupp, welcome to the Vista Community of the MSFN forums ! The more we are, the merrier...
  2. Basilisk52/UXP, Basilisk55/Moebius and FirefoxESR 52.x.x all use the Australis GUI, while PaleMoon/NewMoon[fork] use a pre-Fx29.0a1 GUI PaleMoon/NewMoon have integrated code borrowed from the Status-4-Evar Firefox XUL extension; in your NewMoon screenshot one can see you have disabled the native Status Bar! Menu Bar -> View -> Toolbars -> tick "Status Bar" then you'll be able to (pre-)view links there... If you don't want the native status bar to be always present but still want the link preview info, then Menu Bar -> Tools -> Status Bar Preferences -> Status -> General -> Links -> Show links in: and change the default ("Status Bar") to "Pop-up" ; then Menu Bar -> View -> Toolbars -> untick "Status Bar" (... but I'm sure all this info could be found easily with a google search, or palemoon forum search... )
  3. taokaizen Browser: "Advanced Chrome" Issue

    @sdfox7 Thanks for your follow up/explanations I, for one, wouldn't do that, regardless of whether it's impacting AdvChrome or not, but everyone here is entitled to one's own free choice... That download comes with the extremely outdated PPAPI v21.0.0.213 (from Apr 6th 2016); does the browser still crash with only that specific version? More to the point, does the crash still occur with only a "pepflashplayer.dll" inside PepperFlash dir (and not a system32 PPAPI install)? You are correct and that detail did escape me ; presumably the developer was lazy and didn't recompile the .exe, although the all-important chrome.dll is of the correct version 54.20.6530.0; you can modify the version of chrome.exe to the correct string (52.15.5320.0 => 54.20.6530.0) using Resource Hacker If you and @heinoganda find this is an ongoing/reproducible XP issue when both the default PPAPI (inside AC's PepperFlash dir) and a system32 PPAPI are present, then, as suggested, better report it to the AdvChrome developer, else this issue will only linger... Best regards
  4. IE 8 in 2018?

    YouTube (read Google) have abandoned Adobe Flash Player on all browsers, period! ; to be able to watch YT, you'd have to use a HTML5 capable browser (MSE also needed for live streams); if the browser/OS doesn't support h264/aac decoding (the case of IE8/XP), then at least your browser should support VP8/VP9 decoding (Firefox e.a.); NB, not all live YT streams have VP8/9 flavours Google Chrome Frame uses the proprietary h264/aac decoders (whose licence costs are paid to patent holders) + free WebM decoders, that normally come bundled with Chrome, to enable html5 YT playback in IE8/XP. ==================================================== Trivia (possibly OT for you XP-ers ): On Vista SP2, IE9 can play on-demand YT (but not live YT streams) with the h264/aac decoders, because the OS (via Windows Media Foundation framework) has native support for these; there's also another project from Google, WebM Video for MSIE, which installs VP8/VP9 (only) decoding support to IE; unfortunately for you on XP, it requires IE9+/Vista+ When YT first disabled Flash on their main site, for a few weeks after it was possible to re-enable Flash and YT MP4 playback via some userscripts on Firefox, exploiting the fact that embedded YT vids could still call Flash; if you've got time to kill, you can read the following google (the irony!) forum thread: https://productforums.google.com/forum/?hl=en#!topic/youtube/CUaTWvKhAuE The now defunct userscript project: https://github.com/juneyourtech/GM_YT_Flash https://github.com/juneyourtech/GM_YT_Flash/issues/6
  5. taokaizen Browser: "Advanced Chrome" Issue

    AppVersion 52.15.5320.0 This is NOT the latest/current version of AdvancedChrome ; that one is v54.20.6530.0, released on Jan 5th 2018: http://browser.taokaizen.com/ ModName: pepflashplayer32_29_0_0_125.dll Is the system32\Macromed\Flash screenshot current? There you have v pepflashplayer32_29_0_0_113.dll which, presumably, it's not the one producing the Error (?); is the latest stable, while is beta; you shouldn't mix both... In your third screenshot, the path to "Pepperflash" directory indicates an "Advanced_Chrome_v54.20.6530.0" directory/installation, so what is your actually installed version? The error signature window points to version 52.15.5320.0 of the browser, that same window refers to PPAPI 29_0_0_125.dll erroring out, but your second screenshot shows an OS install of PPAPI 29_0_0_113.dll; OTOH, your third screenshot purports to version 54.20.6530.0 of the browser and v29_0_0_125.dll of pepflashplayer.dll (obviously manually put there...); I am really confused ; screenshots are supposed to help! In any case, update to just v54.20.6530.0 of AdvChr, removing from your system any previous version remnants; then open chrome://flash/ in a tab and inspect how many flash plugins are picked up by the browser; you'll see paths, too; then open chrome://plugins/ (in a tab) and scroll to the Adobe Flash Player section; the one linked to the browser (inside PepperFlash dir) will report a version string, you should be able to selectively disable the OS PPAPI version, if also present there... I am on Vista myself, so can't test on XP, but here AdvChrome 54.20.6530.0 only sees the locally installed (outdated) PPAPI pepflashplayer.dll v28.0.0.137, not the system-wide install of PPAPI (just installed as a test); I then uninstalled PPAPI 29.0.0125b from the system, keeping a back-up of both pepflashplayer32_29_0_0_125.dll + manifest.json; the .dll was renamed to just pepflashplayer.dll and then placed (+ new manifest.json) inside AdvChrome's Pepperflash dir - older version temporarily removed from there; relaunched browser does see the PPAPI.dll, http://get.adobe.com/flashplayer/about/ correctly reports a version and I can browse to chrome://settings/ without any issue whatsoever Maybe your issue stems from a combination of AdvChr+XP+betaPPAPI; I can't be sure whether Adobe really care about (/test on) XP+older Chromium code nowadays, though their plugins presumably still support XP/vista; for further reporting/troubleshooting, AdvChrome has a dedicated support forum here, maintained by the dev himself (though, if you're a newly registered member, it'll be a bit tricky to submit your first post, since the anti-spam filter there is very peculiar )... Regards
  6. ... Yes ; but only those I posted about at the time I posted Ooops! Apologies - my bad ; 5c6320c patches necko.properties file in Bk52, but I now see this patch already exists in snapshot 3da3c97 of your basilisk55 repo (that Bk55 2018-03-06 is built from); in my case, the error was due to my custom language pack (self-made EL locale). ... Good luck with that! Being many time zones behind Hong Kong, I must now go to sleep and hopefully test your new build over the weekend... Best wishes
  7. ... Just came across another page that does not render correctly (at least on my setup ) in Basilisk v55.0.0 (2018-03-06) 32-bit but does so correctly in previous build Basilisk v55.0.0 (2018-02-18) 32-bit In both screenshots, the browser was started in Safe Mode, under the same profile... The URL in question is http://oscar.go.com/red-carpet EDIT: Same issue is present in latest Basilisk52/UXP T2 (= v52.9.0 (2018-03-10) 32-bit)
  8. ... And while the Moonchild devs have said the Moebius fork has been deprecated, new commits found their way in the repo today: https://github.com/MoonchildProductions/moebius/compare/868d263...760f0f3 @roytam1 : You should consider adding this Basilisk52/UXP (T2) fix to Basilisk55/Moebius too, because it's also present there ... And I don't mean to pressure you in any way, but have you made any progress in discovering the cause of identical issues me and @404notfound have reported in both latest Bk52/Bk55? Perhaps, if you suspect new zlib, you could (?) compile new test builds with the older one (zlib) and let us test them ... As ever, your efforts for older WinOS users are priceless
  9. Latest Version of Software Running on XP

    I'm using the WinRAR Vista Ultimate Revamped theme by AmEagle (found in Official WinRar Themes) for more than a year myself (on Vista OS), so I won't be noticing the icons' change with v5.60b1 ... Or you can still update to v5.60b1 and then install WinRAR Classic theme by Francesco Indrio (link); how to install a theme I hear you ask? Enjoy!
  10. About HandBrake on Windows Vista: I have little interest myself in this app ; this old Vista laptop has a weak 2 Core CPU and an integrated graphics card with no hardware support for h264 encoding, hence I avoid transcoding like the plague In the few instances I do need to perform video transcoding (and usually for short video files), I find that FFmpeg (with --enable-libx264) is more than adequate for the task... Some trivia about HandBrake: 1. The last version to not require .NET Framework 4 is 0.9.5 2. The last XP compatible version is 0.9.9 3. The last version to incorporate the superior FDK-AAC encoder (for transcoding audio to HE-AAC/AAC LC) is 0.10.3 ; for legal reasons, this non-free encoder was later removed from HandBrake and the team removed all compiled Windows binaries from their download pages; background here OTOH, their downloads page clearly indicates "For Windows 7 to 10" The latest stable (current) version, again according to the downloads page, is 1.0.7; this is a 32-bit Vista SP2 machine with .NFW 4.6.1 (the last installable - but not officially supported - of the 4.x.x family), hence I downloaded and tested file HandBrake-1.0.7-i686-Win_GUI.exe ; I found I could open the GUI without any kernel errors: but I haven't attempted a video file transcode myself ; someone with a powerful Vista machine should properly test HB 1.0.7 and verify it performs as expected... Are you by any chance using a nightly build? There's a new one uploaded whenever the master branch is updated, right now the available build is HandBrake-20180314-c038876_x86_64-Win_GUI.exe; however, I couldn't test myself, because: So, IIUTC and if @burd 's findings are valid, next stable release of HandBrake will be 64-bit only, Win7+ only
  11. Hello again With much respect, you do realise not being able to reproduce both reported issues (ddg SE broken, mixcloud site provoking xul.dll crashes) doesn't mean these reports are not valid for the configurations found on affected members' machines, nor is it any consolation for said users... ; it does make it more difficult for you, though, to troubleshoot and discover root cause(s)... As an affected user (of your builds) and not being a coder myself, the best way I can contribute towards resolving those bugs is conduct extensive tests on my side, in the hope of further illuminating things... I've spent the better part of this afternoon (in my timezone) doing just that, following are my results: BAD indicates both the "ddg bug" / "mixcloud crash" are present, GOOD neither is; I can't say for sure they're not related, but in my tests I haven't found a build where only either one is present... =============================================== Platform: Moebius version Bk55 55.0.0 (2018.03.06) buildID 20180306151332 status: BAD version Bk55 55.0.0 (2018.02.18) buildID 20180218132219 status: GOOD Official Bk55 patched to run on Vista: version Bk55 55.0.2018.02.14 (2018.02.14) buildID 20180214105207 status: GOOD --------------------------------------------------------------------------- Platform: UXP T2 version Bk52 52.9.0 (2018.03.10) buildID 20180310101157 Status: BAD version Bk52 52.9.0 (2018.03.02) buildID 20180302124247 Status: Unusable browser, due to broken search service (Moonchild team's fault) version Bk52 52.9.0 (2018.02.24) buildID 20180224095320 Status: GOOD* *On mixcloud: Black screen on first attempt to load, with Windows message: "Display driver has stopped responding and has recovered" but subsequent loads are successful! --------------------------------------------------------------------------- Platform: Tycho (Official) Pale Moon 27 on Vista: version PM 27.9.0a1 (2018-03-10) (unstable channel) buildID 20180310180415 Status: GOOD New Moon (roytam1's XP Fork): version NM 27.9.0a1 (2018-03-10) buildID 20180310050429 Status: GOOD (screenshot below) =============================================== No, according to my tests and provided screengrab (new clear profile, no extensions) I had provided CPU info here but be my guest: "old (2007) Intel CPU Core2 Duo T5250 @ 1.50GHz, that can only go as far as SSSE3"; I wouldn't rule out zlib, but with Cloudflare's zlib in the past I wasn't able to even start your New Moon builds ; I suspected the libjpeg-turbo update for the breakages, but it is present in all three of NM 27.9.0a1 (2018-03-10) , Bk52 52.9.0 (2018.03.10) and Bk55 55.0.0 (2018.03.06) , of which only the Basilisk browsers are BAD . So, the mystery remains unsolved for me... I hope my tests will help...
  12. Another nasty surprise with v55.0.0 (2018-03-06) (32-bit) build : Simply trying to visit the mixcloud site: https://www.mixcloud.com/ and the whole browser crashes (two consecutive ones, both involving xul.dll) : Problem signature: Problem Event Name: APPCRASH Application Name: basilisk.exe Application Version: Application Timestamp: 5a9eb62d Fault Module Name: xul.dll Fault Module Version: Fault Module Timestamp: 5a9eb765 Exception Code: c0000005 Exception Offset: 023de445 OS Version: 6.0.6002. Locale ID: 1032 Additional Information 1: 33c3 Additional Information 2: b6e472db5d63ade87a587e7c386d3b3e Additional Information 3: d8c3 Additional Information 4: bab615fc255482957e351b6ebe080b1b Despite what I said, I am now going back to the previous, rock steady, 20180218132219 build @all : Do remember these are test builds; make frequent profile back-ups, because breakage is bound to happen with alpha/beta software; furthermore, this is only one developer here (albeit a very kind one ), who is probably not able to test every possible configuration in the wild and catch bugs; us testers can promptly report those with the hope of a fix...
  13. @roytam1 OS: Windows Vista SP2 Home Premium 32-bit (not a VM) Basilisk version: v55.0.0 (2018-03-06) (32-bit) from here (buildID=20180306151332) Even running in Safe Mode (with no addons enabled), I can confirm the issue reported by @404notfound, i.e. the DuckDuckGo search engine is broken, in the sense it doesn't show any results in the tab: Viewing the source of that search-results page, one can see there is content there, it just isn't displayed in the proper page itself... A test with some of my other search engines (Bing, Google, Yahoo, Wikipedia) shows they all display results correctly, so it appears the bug is particular to ddg (and as already reported, is not present in Bk v55.0.0 (2018.02.18) (32-bit) (buildID=20180218132219) ). In the changelog, as you said, nothing stands out easily as the culprit ; third party libs updated (zlib, nspr, nss, kiss_fft, libjpeg) and SecureConnectionStartHighRes code (???) ... This old Vista laptop doesn't/can't use gfx hardware acceleration (old proprietary Toshiba driver), perhaps this is somehow relevant? I'll use one of the "working" SE for now and won't downgrade to 20180218132219, hopefully this is something that can be identified and remedied in a future Bk55/moebius release of yours
  14. An .xpi file is just a renamed .zip file... After you've edited the install.rdf file, re-zip all files/folders (with your favourite archive manager) back to a zip file and simply change its .zip extension to .xpi; then install this file into New Moon via drag-n-drop in its addon-manager (about:addons); see previous post in this thread...