Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/10/2019 in all areas

  1. Direct links to official Adobe Flash Player distribution packages version 32.0.0.255 with SHA-1 signature released today (confirmed working with Windows XP SP3/Windows XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.255/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.255/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.255/install_flash_player_ppapi.exe
    3 points
  2. And they're back! I was never more glad to see an ad for QuickBooks. I almost thought this was part of another anti-NT 5 conspiracy.
    2 points
  3. Hi ; what you report is to be expected, not a surprise at all... ; let me explain: 1. SM 2.49.x is built on the Mozilla ESR 52 platform, same as Firefox ESR 52.x.x; for legal and cost reasons, Firefox doesn't come bundled with its own patented decoders (h264, aac), unlike Google Chrome (Google can afford the huge sums of money needed for the licenses payable to the MPEG group to bundle their patented decoders with the Chrome binaries). In order to decode HTML5 MP4 video, Firefox must access the OS-provided patented decoders (the cost of which is included in the price of the OS, i.e. Microsoft, rather than Mozilla, paid for it...) Unfortunately, the mechanism that gives access to these OS-provided decoders is Windows Media Foundation (WMF) framework, available only in Vista SP2 (with Platform Update + Platform Update Supplement) and higher, NOT in WinXP ; hence, SM 2.49.5 on XP can't decode HTML5 instagram video (or any other HTML5 mp4 video for that matter), as XP lacks WMF and associated M$ provided decoders. And no, installed codec packs won't do the job! If you like, you are faced with the same predicament as in the pinned thread below: This is just an educated guess on my part, but since SM 2.49.5 is FxESR 52.9.1 based, you could try and implement what is currently valid for enabling HTML5 MP4 playback in FxESR 52.9.1 under XP in the linked thread; not tested myself, SM 2.49.5 has no issues here (Vista SP2 x86) playing back [h264+aac] MP4 files... 2. The bnavigator fork has been built on the UXP application platform; but @roytam1 has long ago patched the platform to fallback to its own patented decoders when WMF is unavailable (the case of XP); the patented decoders in UXP, provided via FFmpeg libraries, are contained within a custom patched version of the ffvpx third party library; it's the same reason the other two UXP browsers, NM28 & St52, can also decode HTML5 MP4 files under XP... I hope it's clear now!
    2 points
  4. Well, you can remove the first mentioned issue about extended attributes. They are supported by wimgapi and wimlib since a while.
    1 point
  5. I've updated Beta 5 with command line option. It's similar to imagex.exe. WinNTSetup_x64 capture C:\ X:\install.wim "Name" "Description" -compress lzx -silent or a console version WinNTSetup_x64 capture-cli C:\ X:\install.wim "Name" "Description" -compress lzx -silent -silent switch will automatically close WinNTSetup after capture.
    1 point
×
×
  • Create New...