Jump to content

VistaLover

Member
  • Posts

    2,245
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. Sure. Then again, he did warn people to use his "archive" link instead... ... For WinXP users, permanent links to Google Chrome v49.0.2623.112 (32bit) direct from Google servers; the download link template is of the form: <url>/release2/<string>/49.0.2623.112_chrome_installer.exe where <url> is one of the next four mirrors: http://cache.pack.google.com/edgedl http://redirector.gvt1.com/edgedl http://www.google.com/dl http://dl.google.com and <string> is: 14okehgrtfipvtyyd9pt7hf7ek7hhs7k47bc481jwgh8fz1ono51hw75dtgcm4j6kkei8h9clijoftygpga0q2kbey0o9n4ec6wd Uncertain for how long those links will remain live Maybe sdfox7 could also back up that file onto his server; that file has the added benefit of being extractable with WinRAR, 7zip and similar archivers, unlike "ChromeStandaloneSetup.exe" On Windows Vista SP2 32bit, Google Chrome 50, though officially unsupported, runs fine; in all probability, it'll be the last Google Chrome version to run on that OS; v51 (currently into beta & dev channels) will start up on Vista, but all browser tabs will be empty If anyone else on Vista is willing to give it a go, the "filename" for latest 50 version (currently on the stable channel) is "50.0.2661.87_chrome_installer.exe"; you can use the download link template posted above for v49, but replace given <string> with: euxv7s2geeridhk4gou5e0clgqqu7cbf5aaanm7jgzh5ymluyr5jzmqnsjwfttjaq2m795gcgpfshqw8m5mkbh5gvj35jo0rnpi and, obviously, replace "49" filename with the "50" one... Currently running v50.0.2661.87 in portable mode (PAF), on Vista Home Premium SP2 32bit:
  2. Hello all Vista users After reading the following comment: Google Chrome 50 Drops Windows XP and Vista I went ahead and downloaded v50.0.2661.75 (32bit) of Google Chrome Portable from page: Google Chrome 50 Portable (PAF) It extracted and installed fine (the portable NSIS setup apparently doesn't check for mininum OS required ). Once the portable launcher (GoogleChromePortable.exe) was run, the browser itself loaded fine and behaved flawlessly in every test I put it through (I was testing it for at least 45min after install). Unlike what was posted previously in this thread, all URLs tried loaded successfully and quickly. I only have 2GB of RAM on this 2007 Vista Home Premium 32bit SP2 laptop, yet Chrome 50 appears to be very responsive, as long as the number of opened tabs isn't excessive (max 8 tried...). Screengrab: Of course, as could be expected, Aero doesn't work; you all know it hasn't worked since v41 ... But the browser, in portable mode, is very usable on my system . I was never a true Chrome convert (I have used Firefox as my main browser since 2006), but I do want it for tests occasionally... I haven't bothered to try the installable version (to query if it does install to begin with), nor do I have an interest currently for the beta/dev channels, but Portable Chrome 50 (stable) does seem as a working option on the Vista OS. For XP users: Although it's not to be found on the PortableApps.com site anymore, you can download Google Chrome 49.0.2623.112 Portable from the following link: Google Chrome 49.0.2623.112 Portable (IFTW) This is an installer-from-the-web, aka stub/online NSIS setup, which fetches the 49.0.2623.112 files from Google servers... If you are interested, better download and install now; who knows if/when Google remove those files... Best regards
  3. Hello smeezekitty, many thanks for your reply If I understood correctly, K32EnumProcesses function is present on Vista in psapi.dll, but on Win7 (min OS requirement for Adobe Acrobat Reader DC) is to be found in kernel32.dll? Still, it's odd to me that the Adobe devs introduced that function only in the latest update, with so many continous-track updates having no need for it The good news, I guess, is that it's fixable, I am certainly not in a hurry, so take your time to provide a properly working fix... Let's hope Adobe don't introduce even more incompatible code with their next update I'll be keeping a watchful eye on this thread for the eventual appearance of your patched DLLs. Many thanks in anticipation PS: There's some issue with the quote tags in your previous post; as well as quoting me, you are also quoting yourself!
  4. Hello dencorso Please accept my apologies I wrote from memory, thus I failed miserably... Plus, my XP (SP2) box has been decommissioned since last November, so was not practical for me to test there, only tested on Vista SP2 without the PUS. So Fx 45.0.1 is definitely not working! But here are the full details: I used to frequent the mozillazine forums and it was there I became aware of the following bugzilla bug #1234099 ; it was this bug (and its title: Unhide Adobe GMP on Windows XP) I had in my mind when I posted here with regards to your issue... Sadly, I had not checked that bug's recent activity; it was "uplifted" to version 46, which brings us in turn to Bugzilla bug #1250766 ; comment 6 writes: ... and comment 12 writes: Today is/was a Sunday, so had some more spare time at hand; I decided to bring my XP SP2 x86 box out of storage and try myself - I installed first Firefox 46.0b9 portable and then Firefox Developer Edition (DevEd for brevity) 47.0a2[20160410] portable (both in PAF format, with separate profiles). In both Firefox versions, there is a "Primetime CDM provided by Adobe Systems Incorporated 17" entry in about:addons -> plugins, also in the profile folder exists a "gmp-eme-adobe" directory with "eme-adobe.dll". about:config has "media.gmp-eme-adobe.enabled;true". But about:preferences#content does not show a "Playback DRM content" section! I tried to play back some local MP4 files, first in Fx 46.0b9 and then in DevEd 47.0a2. In both cases, playback failed, in contrast to what is stated inside #1250766. In the case of DevEd 47.0a2, browser suffers a silent crash: Firefox 47.0a2 Crash Report [@ mozilla::gmp::GMPChild::ProcessingError ] everytime I try a new MP4/M4A file. Perhaps my failure stems from the fact I'm still on SP2 (32bit), but I did not care to debug this further... You don't stand to lose anything if you yourself try versions DevEd 47.0a2_x86 or even Nightly 48.0a1_x86 (you can use the portables without affecting your normal Fx install) - perhaps in your case, with SP3(/4) installed, you may have better results. Comment 12 only mentions a test on XP (SP2) x64, so 32bit XP is not explicitly covered in that comment... Since you are very keen on having this working (playback of h264/aac in MP4 in Firefox on XP), perhaps you should join referenced Bugzilla bug and share your findings there... It appears the Mozilla Devs want this as much as you... Anyhow, again sorry for the initial false info, I do hope you soon get this sorted ! Many regards
  5. Hello dencorso If you have latest (release channel) version of Mozilla Firefox (45.0.1), then please make sure you have the latest vesion of Adobe Primetime HTML5 Content Decryption Module installed inside Extensions -> Plugins. On systems which lack the native OS resources (XP, Vista without Platform Update Supplement) to play back patented H264+AAC, the CDM is being used as a fallback mechanism to play back un-encrypted (H264+AAC) MP4s (or audio M4As) delivered over HTML5. The main caveat is that Hardware Acceleration (GPU) can't be used with the CDM, only software one (CPU) ... HTH
  6. Hello smeezekitty The main reason I joined MSFN was to grab a copy of your compiled "user33.dll" in this thread (Google led me here), so I could preview/install Adobe Acrobat Reader DC on my Vista Home Premium SP2 32bit laptop - so, many thanks indeed Your DLL redirection method has worked flawlessly during all the continuous-track updates Adobe pushed, for the record those were: -- File Version -- 15.007.20033.02203 15.008.20082.15957 15.009.20069.28170 15.009.20077.29851 15.010.20056.36345 15.010.20059.40980 Sadly, the latest update, which was File Version: 15.010.20060.43353 somehow has broken things for me When I try to access the Preferences popup window, (Edit -> Preferences), I now get the error reported by 2008WindowsVista in: comment=1109941 which, much like his case, appears only once when you try to access Prefs; clicking OK makes it go away and Prefs pops up normally. But, much like 2008WindowsVista has already posted in: comment=1109943 the real deal-breaker is when trying to access the Tools tab (either directly or via Edit -> Manage Tools), when the error shown can't be clicked away and results in an endless loop, making it necessary to kill AcroRd32.exe process manually via Task manager. 2008WindowsVista is on Vista Ultimate 64bit and he already reported those glitches since first released version 2015.007.20033, but I am on Vista HP 32bit and only started having those after the latest update (version 2015.010.20060). I do realise Adobe's code is closed-source, but are you in any state to discern what was introduced in latest update that started causing me those issues? Could an updated version of your user33.dll be compiled so as to address those? As a workaround, I have downgraded to version 2015.010.20059 (which works totally fine on my system) and renamed \plug_ins\Updater.api (to Updater.api.BAK) so that it won't auto-update to 2015.010.20060... Of course I can stay put at that version, but it'll become less secure as time moves on... Anyhow, many thanks for your efforts so far... Most kind regards
×
×
  • Create New...